date:20140804

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

Title:
  10ec:8179 [HP Pavilion 17-e171nr Notebook PC] RTL8188EE driver
  regression in 3.13.0-24.  Extremely slow network performance

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I'm experiencing excruciatingly slow wireless performance on upgrading
  to Trusty.  There are numerous reports of simlar symptoms on the
  forums, and the solution seems to be to download/install a newer or
  older kernel, or build a new version of the rtl8188ee driver.

  Here are some examples:

  http://ubuntuforums.org/showthread.php?t=2218096
  http://ubuntuforums.org/showthread.php?t=2218521
  http://ubuntuforums.org/showthread.php?t=2219896

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brenda 1725 F pulseaudio
   /dev/snd/controlC0:  brenda 1725 F pulseaudio
  Date: Wed May 21 20:47:12 2014
  HibernationDevice: RESUME=UUID=c076696b-2637-49fd-8981-21402ab2c94f
  InstallationDate: Installed on 2013-12-28 (144 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-05-07 (14 days ago)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097611405E0620180:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 097611405E0620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1307064] Re: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570

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

Title:
  Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Fresh install of 14.04 on my laptop cannot adjust brightness.  When
  fn+up arrow or fn+down arrow are used, the indicator in the upper
  right hand corner as if the brightness should change, but it does not.
  Also, if one tries to use the slider in the power applet, the
  brightness does not change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  will   2960 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 12 21:36:57 2014
  HibernationDevice: RESUME=UUID=dfa51f33-0f34-4383-8194-93656983323d
  InstallationDate: Installed on 2014-04-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: LENOVO 10249RU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=7420c61f-1836-4a44-84dc-71573190ff4c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN38WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pn10249RU:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: 10249RU
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1314628] Re: acpi-cpufreq incorrectly detect available frequency steps on Intel Core 2 6300 CPU

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

Title:
  acpi-cpufreq incorrectly detect available frequency steps on Intel
  Core 2 6300 CPU

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Intel Core 2 6300 CPU is clocked at 1.86 GHz, but under Ubuntu 14.04
  cpufreq-info report available frequency steps as 700 MHz and 600 MHz.

  Kernel is: Linux larch 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10
  19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1349020] Re: inline_data option on ext4 truncates symlinks

2014-08-04 Thread Claes Wallin

That fixes the bug. Even symlinks created by the faulty kernel will be
interpreted correctly by the fixed kernel, as the fault is in reading,
not in writing.

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

Title:
  inline_data option on ext4 truncates symlinks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  To replicate the bug, create two filesystems, one with `mkfs.ext4 -I
  256`, one with `mkfs.ext4 -I 256 -O inline_data`. An inode size of 256
  bytes is the default, but included here for clarity. To do this, you
  are going to need an `e2fsprogs` from trunk, or version 1.43 if it has
  been released.

  Mount the two filesystems, in each of them do:
  $ ln -s $(for i in {1..64}; do echo -n .; done) 64
  $ ln -s $(for i in {1..128}; do echo -n .; done) 128
  $ ln -s $(for i in {1..192}; do echo -n .; done) 192
  $ ls -l 64 128 192

  Both directory listings will show symlinks named `64`, `128` and
  `256`, each pointing to a filename with the corresponding amount of
  dots. This is the expected behavior.

  Unmount both filesystems, mount them again. Do the `ls -l` again.

  The default filesystem will show the same output as previously, the
  one with inline_data activated will show the `128` symlink pointing to
  a filename of only 64 dots.

  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:  clacke 3532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jul 27 00:47:06 2014
  EcryptfsInUse: Yes
  MachineType: LENOVO IdeaPad Z370
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/hostname-trusty_root 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.5
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4ACN35WW
  dmi.board.name: KL5
  dmi.board.vendor: LENOVO
  dmi.board.version: Rev 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr4ACN35WW:bd08/29/2011:svnLENOVO:pnIdeaPadZ370:pvrRev1.0:rvnLENOVO:rnKL5:rvrRev1.0:cvnLENOVO:ct10:cvrRev1.0:
  dmi.product.name: IdeaPad Z370
  dmi.product.version: Rev 1.0
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1303737] Re: [HP 242 G2] Wireless key events were not detected at all

2014-08-04 Thread Edward Lin

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1303737

Title:
  [HP 242 G2] Wireless key events were not detected at all

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  CID: 201309-14199 HP 242 G2

  The wireless key press / release events were not detected at all.

  Steps:
  1. Install 12.04.4 + update (3.11.0-19), boot to desktop
  2. Try to control the wireless by pressing the wireless hotkey

  Expected result:
  * Wireless functionality could be controlled by the wireless hotkey

  Actual result:
  * Wireless hotkey was not working at all, nothing captured by "xev" or "sudo 
showkey -k"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-19-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: 92HD99BXX Analog [92HD99BXX Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1729 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1729 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xb271 irq 47'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 21
 Simple ctrls  : 3
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xb2714000 irq 46'
 Mixer name : 'IDT 92HD99BXX'
 Components : 'HDA:111d76e5,103c2181,00100303'
 Controls  : 21
 Simple ctrls  : 10
  Date: Mon Apr  7 06:59:14 2014
  HibernationDevice: RESUME=UUID=b787b71e-2ec4-47b3-be20-9b6422c7be95
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Hewlett-Packard HP 242 G2 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic 
root=UUID=d0365656-031c-4231-9809-3bb9edb471f5 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-19-generic N/A
   linux-backports-modules-3.11.0-19-generic  N/A
   linux-firmware 1.79.11
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-lts-saucy
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 217A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 34.0E
  dmi.chassis.asset.tag: 738DIP10EI
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.0B:bd10/08/2013:svnHewlett-Packard:pnHP242G2NotebookPC:pvr099C200620100:rvnHewlett-Packard:rn217A:rvrKBCVersion34.0E:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 242 G2 Notebook PC
  dmi.product.version: 099C200620100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

This change was made by a bot.

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

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

Title:
  Oculus Rift "drifts" on recent kernels

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  When running Oculus Rift compatible software, the HMD rotation seen by
  software drifts by a few degrees per second, even when the HMD is not
  moving at all (ie, it's sitting perfectly still on the desk).

  This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24
  prevents the bug from happening.

  The bug happens after using the OR in hidraw mode (which is what the
  OVR SDK uses), and will even persist if you reboot into Windows
  without power cycling the device.

  OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD
  in libusb mode the problem does not happen, unless you have previously
  used some software which opens the OR in hidraw mode. OpenHMD can also
  be compiled to use hidraw, and if you do that it just shows a black
  screen with the example. If you then run it in libusb mode, the drift
  happens.

  This bug has been reported on the Oculus forums:
  https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689

  To me this looks like a HID bug. Something is messing up the state of
  the hardware so badly that it will continue to report bad data even
  when using software that works correctly after a power cycle. Looking
  at the commits between -24 and -27 kernels I see a bunch of commits to
  HID which look like they might be responsible for this.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  al 1999 F pulseaudio
   /dev/snd/controlC1:  al 1999 F pulseaudio
   /dev/snd/controlC0:  al 1999 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Jul  4 01:07:13 2014
  HibernationDevice: RESUME=UUID=cd4b4f29-2984-430a-8556-26b5fd58d903
  InstallationDate: Installed on 2014-06-29 (4 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=06500b4e-b446-411c-9a19-cfff649a7be4 ro quiet splash
  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: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0X
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X: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/1337641/+subscriptions

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

[Kernel-packages] [Bug 1337641] Re: Oculus Rift "drifts" on recent kernels

2014-08-04 Thread Alistair Buxton

This isn't a BIOS issue, it's been reproduced across multiple different
hardwares including by the oculus developers themselves, and is a
regression in the stable release. It's either a bug in the oculus driver
code, or it's a bug in the kernel.

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

Title:
  Oculus Rift "drifts" on recent kernels

Status in “linux” package in Ubuntu:
  New

Bug description:
  When running Oculus Rift compatible software, the HMD rotation seen by
  software drifts by a few degrees per second, even when the HMD is not
  moving at all (ie, it's sitting perfectly still on the desk).

  This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24
  prevents the bug from happening.

  The bug happens after using the OR in hidraw mode (which is what the
  OVR SDK uses), and will even persist if you reboot into Windows
  without power cycling the device.

  OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD
  in libusb mode the problem does not happen, unless you have previously
  used some software which opens the OR in hidraw mode. OpenHMD can also
  be compiled to use hidraw, and if you do that it just shows a black
  screen with the example. If you then run it in libusb mode, the drift
  happens.

  This bug has been reported on the Oculus forums:
  https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689

  To me this looks like a HID bug. Something is messing up the state of
  the hardware so badly that it will continue to report bad data even
  when using software that works correctly after a power cycle. Looking
  at the commits between -24 and -27 kernels I see a bunch of commits to
  HID which look like they might be responsible for this.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  al 1999 F pulseaudio
   /dev/snd/controlC1:  al 1999 F pulseaudio
   /dev/snd/controlC0:  al 1999 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Jul  4 01:07:13 2014
  HibernationDevice: RESUME=UUID=cd4b4f29-2984-430a-8556-26b5fd58d903
  InstallationDate: Installed on 2014-06-29 (4 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=06500b4e-b446-411c-9a19-cfff649a7be4 ro quiet splash
  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: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0X
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X: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/1337641/+subscriptions

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

[Kernel-packages] [Bug 1351966] Re: [Nokia Booklet 3G] Fresh install of Lubuntu 14.04.1 will not return from suspend

2014-08-04 Thread TEN

Before that (as I do need some usable system every once in a while),
installed the year-old elementaryOS.org Luna as a lightweight Ubuntu
12.04 LTS derivative.

Had to use both
https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo
/#Option_1_-_console.3Dtty1 and
https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo/#Fix_suspend
to avoid distorted video on boot & resume, but other than that things do
work (including lid switch) on that older LTS.

May return to Lubuntu 14.04.1 LTS for further testing soon if a plan is
in place indeed to actually debug these issues (rather than additionally
setting the hoops on fire, once anyone actually volunteered to jump
through them ;)).

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

Title:
  [Nokia Booklet 3G] Fresh install of Lubuntu 14.04.1 will not return
  from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After closing the lid, causing a suspend, and reopen all I see is a
  blank screen, with associated data loss due to required hard reboot.

  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 i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1501 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Sun Aug  3 20:13:22 2014
  HibernationDevice: RESUME=UUID=85e12fa3-8502-4b95-ad0a-067f59b08e36
  InstallationDate: Installed on 2014-08-03 (0 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Nokia Nokia Booklet 3G
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=85e5e6bc-f8c4-4b0e-a101-a1698e8f670c 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.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Nokia
  dmi.bios.version: 2.00.T01
  dmi.board.name: NYU00
  dmi.board.vendor: Nokia
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 8
  dmi.chassis.vendor: Nokia
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnNokia:bvr2.00.T01:bd03/05/2010:svnNokia:pnNokiaBooklet3G:pvr0040:rvnNokia:rnNYU00:rvrREFERENCE:cvnNokia:ct8:cvrN/A:
  dmi.product.name: Nokia Booklet 3G
  dmi.product.version: 0040
  dmi.sys.vendor: Nokia

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

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

[Kernel-packages] [Bug 1349572] Re: Wireless network disconnections on Dell XPS 13

2014-08-04 Thread Marcel Miguel

I had some disconnections 15 minuts ago:

wlan0: CTRL-EVENT-DISCONNECTED bssid=xx reason=4 locally_generated=1

I needed a restart to arrange it. After this everything seems to work
fine.

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

Title:
  Wireless network disconnections on Dell XPS 13

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With kernel 3.13.0.30 and 22.1.7.0, there are lots of wireless disconnections.
  Tested also with kernel 3.13.0.32 and 22.24.8.0 , also lots of wireles 
disconnections. 

  The AP is an ASL-26555 from Movistar(Spain). Firmware version:
  v2.0.0.51B_ESv6

  Seems that when the computer is working for some time it is more easy
  to reproduce this beahviour.

  Added this bug as sugested in #1293569, comment #91.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-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:  marcel 2611 F pulseaudio
   /dev/snd/controlC0:  marcel 2611 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 28 22:20:19 2014
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 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.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (101 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  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.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (103 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   li

[Kernel-packages] [Bug 1285708] Re: FreeBSD Guest crash on boot due to xsave instruction issue

$ git tag --contains 56c103ec040b1944c8866f79aa768265c0dd2986
v3.15-rc1

The patch in question is already in 3.16 / Utopic.

I can reproduce this easily in Trusty.

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

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Chris J Arges (arges)

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

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

** Changed in: linux (Ubuntu Precise)
 Assignee: (unassigned) => Chris J Arges (arges)

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

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

Title:
  FreeBSD Guest crash on boot due to xsave instruction issue

Status in QEMU:
  New
Status in qemu-kvm:
  New
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Precise:
  New
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  When trying to boot a working FreeBSD 9.1/9.2 guest on a kvm/qemu host
  with the following command:

  kvm -m 256 -cdrom FreeBSD-9.2-RELEASE-amd64-disc1.iso -drive
  file=FreeBSD-9.2-RELEASE-amd64.qcow2,if=virtio -net nic,model=virtio
  -net user -nographic -vnc :10 -enable-kvm -balloon virtio -cpu
  core2duo,+xsave

  The FreeBSD Guest will kernel crash on boot with the following error:

  panic: CPU0 does not support X87 or SSE: 0

  When launching the guest without the cpu flags, it works just fine.

  This bug has been resolved in source:
  https://lkml.org/lkml/2014/2/22/58

  Can this fix be included in Precise ASAP!

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

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

[Kernel-packages] [Bug 1347737] Re: Kernel nested kvm support

Glancing at this again it seems to be a guest kernel issue (3.4.0 series). 
I can clearly see the backtrace if I run the steps in #7 on my 3.16 x86_64 
utopic laptop; however the emulated guest seems to continue to run.

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

Title:
  Kernel nested kvm support

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Before we go barking up the tree of the Ubuntu Touch emulator on bare
  metal using MAAS and Juju, I wanted to make sure we tried nested kvm.
  I heard rumors that this was known not to work well, and sure enough
  if I run the touch emulator inside an i386 2G RAM trusty instance on
  Canonistack, I get the occasional kernel panic or OOPS.

  If it's not something we care to support, that's fine, but getting a
  statement from the kernel team to this effect would be helpful.

  Begin: Running /scripts/init-bottom ... done.
  [9.97] init: ureadahead-touch main process (263) terminated with 
status 5
  [   46.67] init: /dev/hw_random not found
  [   46.67] init: cannot open '/initlogo.rle'
  [   47.00] init: /dev/hw_random not found
  [   47.85] healthd: wakealarm_init: timerfd_create failed
  [   48.22] init: cannot find '/system/etc/install-recovery.sh', disabling 
'flash_recovery'
  [   48.22] init: cannot find '/system/bin/ubuntuappmanager.disabled', 
disabling 'ubuntuappmanager'
  [   49.37] Unable to handle kernel paging request at virtual address 
8030c164
  [   49.37] pgd = bf9dc000
  [   49.37] [8030c164] *pgd=3fffe801, *pte=0030c0cf, *ppte=0030c21e
  [   49.37] Internal error: Oops: 81f [#1] PREEMPT ARM
  [   49.37] Modules linked in:
  [   49.37] CPU: 0Not tainted  (3.4.0-3-goldfish #17-Ubuntu)
  [   49.37] PC is at __patch_text+0xc/0x24
  [   49.37] LR is at __jump_label_update+0x3c/0x58
  [   49.37] pc : [<80413d0c>]lr : [<8009c6c4>]psr: 80030013
  [   49.37] sp : be97df08  ip : 0900  fp : 001d
  [   49.37] r10: 0004  r9 : 0001  r8 : bb875380
  [   49.37] r7 : 0001  r6 : 806217ac  r5 : 805e8b7c  r4 : 806204c8
  [   49.37] r3 : 8030c164  r2 : 805e8064  r1 : ea5b  r0 : 8030c164
  [   49.37] Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment 
user
  [   49.37] Control: 10c5387d  Table: 3f9dc059  DAC: 0015
  [   49.37]
  [   49.37] PC: 0x80413c8c:
  [   49.37] 3c8c  e1a0200d ebf014ca e1a096ad e1a09689 e3a08000 eaefe8b6 
e281c01c e5923060
  [   49.37] 3cac  e8ac6ff0 ee0d3f70 e3a04000 ee0d4f50 e592700c e59f8020 
e59771ec e1a05000
  [   49.37] 3ccc  e282401c e59f0014 e3a01002 eb000553 e5887000 e1a5 
e894aff0 805e8048
  [   49.37] 3cec  806270ac e320f000 e320f000 e320f000 e320f000 e59f2018 
e92d4008 e1a03000
  [   49.37] 3d0c  e4831004 e1a01003 e5922010 e12fff32 e8bd8008 805e8064 
eaf5 e92d0fff
  [   49.37] 3d2c  e1ad ebf7 e1a0e000 e8bd0fff e1a0f00e e92d4037 
e1a04000 e5903014
  [   49.37] 3d4c  e59f20b4 e1530002 3a27 e59f20ac e1530002 3a22 
ea23 e593
  [   49.37] 3d6c  e1a01004 e28d3000 e5840030 e5a13034 eb0003e6 e351 
0a03 3a18
  [   49.37] LR: 0x8009c644:
  [   49.37] c644  3a02 93a0 83a1 e12fff1e e3e0 e12fff1e 
e5903000 e5902004
  [   49.37] c664  e353 e2020001 d3a03000 c3a03001 e1d32002 02233001 
0003 13a1
  [   49.37] c684  e12fff1e e92d40f8 e1a05000 e1a04001 e1a06002 e1a07003 
ea09 e594
  [   49.37] c6a4  e350 0a05 ebfe745a e350 0a02 e1a4 
e1a01007 ebfdd73c
  [   49.37] c6c4  e284400c e1540006 28bd80f8 e5943008 e1550003 0af0 
e8bd80f8 e92d47f0
  [   49.37] c6e4  e1a05000 e5908004 e1a07001 ebff005a e3a0a00c e3c88001 
e5954008 e1a06000
  [   49.37] c704  ea08 e5943008 e1a5 e5941004 e5932138 e5933134 
e022329a e1a03007
  [   49.37] c724  ebd7 e5944000 e354 1af4 e356 15962138 
13a0100c 15963134
  [   49.37]
  [   49.37] SP: 0xbe97de88:
  [   49.37] de88  0003 be97df08 76e4b000 800e94e8  800d95e0 
bf90b5e8 be97df08
  [   49.37] dea8   80413d0c 80030013  be97def4 80413898 
8030c164 ea5b
  [   49.37] dec8  805e8064 8030c164 806204c8 805e8b7c 806217ac 0001 
bb875380 0001
  [   49.37] dee8  0004 001d 0900 be97df08 8009c6c4 80413d0c 
80030013 
  [   49.37] df08  806204c8 8009c6c4 0001 805e8b7c  0001 
7e973898 8009cb24
  [   49.37] df28   bfb00040 0001 802ffe90 be97df90 800cebc0 
0041 c1b6
  [   49.37] df48  805e8a18 802fb078 0002 a1ec60e1 fff7 bb875380 
0001 0004
  [   49.37] df68  001d 7e973898 be97c000  76e4b000 802fc4f8 
0004 0001
  [   49.37]
  [   49.37] R0: 0x8030c0e4:
  [   49.37] c0e4  e59c200a e0

[Kernel-packages] [Bug 1345008] Re: WARNING: CPU: 0 PID: 71 at /build/buildd/linux-3.13.0/fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()

What I've found is that the USB audio device I am using doesn't properly
create a mixer which in turn causing these sysfs remove errors (due to
another patch that emits these WARNs).

If I try to quirk it (for example using a test patch like this):
https://lkml.org/lkml/2013/7/17/590 

However the following commits allow the mixer creation to be skipped without a 
quirk:
4d7b86c98 "ALSA: snd-usb: mixer: propagate errors up the call chain"
83ea5d18d "ALSA: snd-usb: mixer: ignore -EINVAL in snd_usb_mixer_controls()"
61ac51301 "ALSA: usb: Parse UAC2 extension unit like for UAC1"

Which renders that above patch unnecessary. So what's needed is a way to
properly remove those sysfs entries without causing a warn even if we
have a USB Audio device with a bogus UAC2 extensions.

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

Title:
  WARNING: CPU: 0 PID: 71 at
  /build/buildd/linux-3.13.0/fs/sysfs/group.c:214
  sysfs_remove_group+0xc6/0xd0()

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  New

Bug description:
  [Impact]

  This impacts 3.16 and 3.13 series kernels.

  When powering off a USB audio device that is plugged into the computer the 
following kernel WARNs are displayed:
  [  410.508315] usb 1-1.4: USB disconnect, device number 4
  [  410.510722] [ cut here ]
  [  410.510731] WARNING: CPU: 0 PID: 71 at 
/build/buildd/linux-3.13.0/fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
  [  410.510733] sysfs group 81cabae0 not found for kobject 'midiC3D0'
  [  410.510734] Modules linked in: xt_conntrack ipt_REJECT ip6table_filter 
ip6_tables ebtable_nat ebtables hid_logitech_dj hid_generic usbhid hid 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
iptable_filter ip_tables x_tables usb_storage dm_crypt gpio_ich intel_rapl 
x86_pkg_temp_thermal coretemp kvm_intel uvcvideo videobuf2_vmalloc kvm 
videobuf2_memops snd_usb_audio videobuf2_core videodev snd_usbmidi_lib 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POF) bnep rfcomm 
snd_hda_codec_hdmi aesni_intel bluetooth aes_x86_64 lrw gf128mul glue_helper 
ablk_helper snd_hda_codec_realtek cryptd serio_raw snd_seq_midi snd_hda_intel 
snd_seq_midi_event snd_hda_codec snd_hwdep snd_rawmidi snd_pcm mei_me snd_seq 
lpc_ich mei snd_page_alloc snd_seq_device snd_timer snd soundcore mac_hid wmi 
parport_pc ppdev binfmt_misc lp parport i915 video i2c_algo_bit ahci 
drm_kms_helper libahci firewire_ohci e1000e drm psmouse firewire_core ptp 
crc_itu_t pps_core
  [  410.510801] CPU: 0 PID: 71 Comm: khubd Tainted: PF  O 
3.13.0-32-generic #57-Ubuntu
  [  410.510803] Hardware name: LENOVO 7052B9U/, BIOS 9HKT47AUS 
01/10/2012
  [  410.510805]  0009 8804275b1990 8171bcb4 
8804275b19d8
  [  410.510809]  8804275b19c8 810676cd  
81cabae0
  [  410.510813]  880424710c10 88042471 880422c1bcf8 
8804275b1a28
  [  410.510816] Call Trace:
  [  410.510824]  [] dump_stack+0x45/0x56
  [  410.510829]  [] warn_slowpath_common+0x7d/0xa0
  [  410.510832]  [] warn_slowpath_fmt+0x4c/0x50
  [  410.510836]  [] ? sysfs_get_dirent_ns+0x4e/0x70
  [  410.510839]  [] sysfs_remove_group+0xc6/0xd0
  [  410.510844]  [] dpm_sysfs_remove+0x43/0x50
  [  410.510849]  [] device_del+0x45/0x1c0
  [  410.510852]  [] device_unregister+0x1e/0x60
  [  410.510856]  [] device_destroy+0x3c/0x50
  [  410.510866]  [] snd_unregister_device+0x4d/0xa0 [snd]
  [  410.510872]  [] snd_rawmidi_dev_disconnect+0xc6/0xf0 
[snd_rawmidi]
  [  410.510881]  [] snd_device_disconnect+0x6a/0xf0 [snd]
  [  410.510889]  [] snd_device_disconnect_all+0x4c/0x90 [snd]
  [  410.510896]  [] snd_card_disconnect+0x131/0x1e0 [snd]
  [  410.510904]  [] usb_audio_disconnect+0x80/0x1b0 
[snd_usb_audio]
  [  410.510909]  [] usb_unbind_interface+0x64/0x1c0
  [  410.510913]  [] __device_release_driver+0x7f/0xf0
  [  410.510916]  [] device_release_driver+0x23/0x30
  [  410.510918]  [] bus_remove_device+0x108/0x180
  [  410.510922]  [] device_del+0x129/0x1c0
  [  410.510925]  [] usb_disable_device+0xb0/0x290
  [  410.510929]  [] usb_disconnect+0xad/0x200
  [  410.510933]  [] hub_port_connect_change+0xd5/0xb50
  [  410.510937]  [] ? usb_control_msg+0xd4/0x110
  [  410.510941]  [] hub_events+0x4c4/0xa20
  [  410.510944]  [] hub_thread+0x35/0x160
  [  410.510950]  [] ? prepare_to_wait_event+0x100/0x100
  [  410.510953]  [] ? hub_events+0xa20/0xa20
  [  410.510957]  [] kthread+0xd2/0xf0
  [  410.510961]  [] ? kthread_create_on_node+0x1d0/0x1d0
  [  410.510966]  [] ret_from_fork+0x7c/0xb0
  [  410.510969]  [] ? kthread_create_on_node+0x1d0/0x1d0
  [  410.510971] ---[ end trace 68a53e3235c146ed ]---
  [  410.511060] [ cut here ]

  [ Test

[Kernel-packages] [Bug 1352567] Re: OOPS in cpufreq driver with AMD Kaveri CPU

2014-08-04 Thread post-factum

** Tags added: apport-collected trusty

** Description changed:

  Occasionally I get my machine hung completely. Fortunately, I've got and 
saved 
  oops listing using netconsole before hang, and here it is [1].
  
  Here is little piece of oops from the link above:
  
  ===
  [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4
  [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20
  …
  [15051.956205] Call Trace:
  [15051.980641]  [] ? __cpufreq_notify_transition+0x95/0x1e0
  [15052.005640]  [] cpufreq_notify_transition+0x3e/0x70
  [15052.030240]  [] cpufreq_freq_transition_begin+0xe8/0x130
  [15052.054522]  [] ? ucs2_strncmp+0x70/0x70
  [15052.078208]  [] __target_index+0xbf/0x1a0
  [15052.101348]  [] __cpufreq_driver_target+0xfc/0x160
  [15052.124250]  [] od_check_cpu+0xa4/0xb0
  [15052.146789]  [] dbs_check_cpu+0x16c/0x1c0
  [15052.168935]  [] od_dbs_timer+0x11d/0x180
  [15052.190607]  [] process_one_work+0x17f/0x4c0
  [15052.211825]  [] worker_thread+0x11b/0x3f0
  [15052.232490]  [] ? create_and_start_worker+0x80/0x80
  [15052.253127]  [] kthread+0xc9/0xe0
  [15052.273292]  [] ? flush_kthread_worker+0xb0/0xb0
  [15052.293487]  [] ret_from_fork+0x7c/0xb0
  [15052.313544]  [] ? flush_kthread_worker+0xb0/0xb0
  …
  ===
  
  Also here is my lspci [2] and cpuinfo [3] as well.
  
  Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13
  kernel.
  
  No visible reason to trigger the bug. After hang machine doesn't respond via 
  network, there's no disk IO, and also it doesn't respond to pressing power 
  button in order to perform soft off.
  
  And here is kernel bugzilla bugreport [4].
  
  [1] https://gist.github.com/085af9da81197faf6637
  [2] https://gist.github.com/318ebda5576b099590b8
  [3] https://gist.github.com/9c1307463c7ad6835b2d
  [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.3
+ Architecture: amd64
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2014-07-30 (5 days ago)
+ InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_US:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags:  trusty
+ Uname: Linux 3.16.0-031600-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

Title:
  OOPS in cpufreq driver with AMD Kaveri CPU

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Occasionally I get my machine hung completely. Fortunately, I've got and 
saved 
  oops listing using netconsole before hang, and here it is [1].

  Here is little piece of oops from the link above:

  ===
  [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4
  [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20
  …
  [15051.956205] Call Trace:
  [15051.980641]  [] ? __cpufreq_notify_transition+0x95/0x1e0
  [15052.005640]  [] cpufreq_notify_transition+0x3e/0x70
  [15052.030240]  [] cpufreq_freq_transition_begin+0xe8/0x130
  [15052.054522]  [] ? ucs2_strncmp+0x70/0x70
  [15052.078208]  [] __target_index+0xbf/0x1a0
  [15052.101348]  [] __cpufreq_driver_target+0xfc/0x160
  [15052.124250]  [] od_check_cpu+0xa4/0xb0
  [15052.146789]  [] dbs_check_cpu+0x16c/0x1c0
  [15052.168935]  [] od_dbs_timer+0x11d/0x180
  [15052.190607]  [] process_one_work+0x17f/0x4c0
  [15052.211825]  [] worker_thread+0x11b/0x3f0
  [15052.232490]  [] ? create_and_start_worker+0x80/0x80
  [15052.253127]  [] kthread+0xc9/0xe0
  [15052.273292]  [] ? flush_kthread_worker+0xb0/0xb0
  [15052.293487]  [] ret_from_fork+0x7c/0xb0
  [15052.313544]  [] ? flush_kthread_worker+0xb0/0xb0
  …
  ===

  Also here is my lspci [2] and cpuinfo [3] as well.

  Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13
  kernel.

  No visible reason to trigger the bug. After hang machine doesn't respond via 
  network, there's no disk IO, and also it doesn't respond to pressing power 
  button in order to perform soft off.

  And here is kernel bugzilla bugreport [4].

  [1] https://gist.github.com/085af9da81197faf6637
  [2] https://gist.github.com/318ebda5576b099590b8
  [3] https://gist.github.com/9c1307463c7ad6835b2d
  [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701
  --- 
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-07-30 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en

[Kernel-packages] [Bug 1320894] Re: 1395:0024 usbaudio issues when powering on and off the device

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

** This bug has been marked a duplicate of bug 1345008
   WARNING: CPU: 0 PID: 71 at /build/buildd/linux-3.13.0/fs/sysfs/group.c:214 
sysfs_remove_group+0xc6/0xd0()

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

Title:
  1395:0024 usbaudio issues when powering on and off the device

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  [157242.574746] WARNING: CPU: 4 PID: 71 at 
/build/buildd/linux-3.13.0/fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
  [157242.574748] sysfs group 81cab480 not found for kobject 'card3'
  [157242.574750] Modules linked in: nls_utf8 isofs nls_iso8859_1 
ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp 
bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat 
ebtables x_tables rfcomm bnep bluetooth dm_crypt binfmt_misc gpio_ich 
intel_rapl x86_pkg_temp_thermal snd_hda_codec_hdmi coretemp kvm_intel kvm 
snd_hda_codec_realtek crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel snd_hda_intel aes_x86_64 snd_hda_codec lrw gf128mul hid_logitech_dj 
glue_helper ablk_helper snd_usb_audio cryptd snd_usbmidi_lib snd_hwdep snd_pcm 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_page_alloc uvcvideo serio_raw 
videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd_seq 
snd_seq_device snd_timer snd mei_me lpc_ich mei soundcore parport_pc ppdev 
mac_hid lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx hid_generic usbhid hid xor usb_storage raid6_pq raid1 raid0 
multipath linear nouveau i915 mxm_wmi video ttm firewire_ohci i2c_algo_bit 
e1000e psmouse drm_kms_helper firewire_core drm ptp ahci libahci crc_itu_t 
pps_core wmi
  [157242.574822] CPU: 4 PID: 71 Comm: khubd Tainted: GW
3.13.0-24-generic #47-Ubuntu
  [157242.574824] Hardware name: LENOVO 7052B9U/, BIOS 9HKT47AUS 
01/10/2012
  [157242.574825]  0009 88042759fa60 81715ac4 
88042759faa8
  [157242.574829]  88042759fa98 810676bd  
81cab480
  [157242.574833]  880426baac10 880421cd3030  
88042759faf8
  [157242.574837] Call Trace:
  [157242.574841]  [] dump_stack+0x45/0x56
  [157242.574845]  [] warn_slowpath_common+0x7d/0xa0
  [157242.574848]  [] warn_slowpath_fmt+0x4c/0x50
  [157242.574852]  [] ? sysfs_get_dirent_ns+0x4e/0x70
  [157242.574855]  [] sysfs_remove_group+0xc6/0xd0
  [157242.574859]  [] dpm_sysfs_remove+0x43/0x50
  [157242.574863]  [] device_del+0x45/0x1c0
  [157242.574866]  [] device_unregister+0x1e/0x60
  [157242.574874]  [] snd_card_disconnect+0x14f/0x1e0 [snd]
  [157242.574881]  [] usb_audio_disconnect+0x80/0x1b0 
[snd_usb_audio]
  [157242.574886]  [] usb_unbind_interface+0x64/0x1c0
  [157242.574891]  [] __device_release_driver+0x7f/0xf0
  [157242.574895]  [] device_release_driver+0x23/0x30
  [157242.574899]  [] bus_remove_device+0x108/0x180
  [157242.574902]  [] device_del+0x129/0x1c0
  [157242.574906]  [] usb_disable_device+0xb0/0x290
  [157242.574909]  [] usb_disconnect+0xad/0x200
  [157242.574913]  [] hub_port_connect_change+0xd5/0xb50
  [157242.574917]  [] ? usb_control_msg+0xd4/0x110
  [157242.574920]  [] hub_events+0x4c4/0xa20
  [157242.574924]  [] hub_thread+0x35/0x160
  [157242.574928]  [] ? prepare_to_wait_event+0x100/0x100
  [157242.574931]  [] ? hub_events+0xa20/0xa20
  [157242.574935]  [] kthread+0xd2/0xf0
  [157242.574938]  [] ? kthread_create_on_node+0x1d0/0x1d0
  [157242.574942]  [] ret_from_fork+0x7c/0xb0
  [157242.574945]  [] ? kthread_create_on_node+0x1d0/0x1d0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 19 09:18:06 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-22 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 7052B9U
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=4e81f491-6a97-49a1-91f2-756b22da2b99 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT47AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.v

[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute

2014-08-04 Thread Tim Edwards

@Jackson
There's no need to downgrade the kernel anymore. The workaround, which I use on 
my C720 and it works is:
1. Open the file /etc/default/grub as root in a text editor with: gksu gedit 
/etc/default/grub
2. change the line: GRUB_CMDLINE_LINUX_DEFAULT="tpm_tis.force=1" and save 
changes
3. sudo update-grub

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

Title:
  Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when
  booting up, then resumes booting to the login screen, after 1 minute

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into 
Ubuntu.  Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 
minute or longer, then it resumes booting up to the login screen.  On Ubuntu 
13.10 it only takes about 7 seconds to get to the login screen, while it takes 
almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I 
hope this issue could be fixed.
   
  I have the Acer C720 (chromebook) that has been enabled to use legacy boot so 
I can use other OS's.  Other Acer C720 users have been faceing the same problem 
also.

  Video of Boot
  https://www.youtube.com/watch?v=PVkFTsEzS80

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

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

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

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

apport-collect 1352567

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

Title:
  OOPS in cpufreq driver with AMD Kaveri CPU

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Occasionally I get my machine hung completely. Fortunately, I've got and 
saved 
  oops listing using netconsole before hang, and here it is [1].

  Here is little piece of oops from the link above:

  ===
  [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4
  [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20
  …
  [15051.956205] Call Trace:
  [15051.980641]  [] ? __cpufreq_notify_transition+0x95/0x1e0
  [15052.005640]  [] cpufreq_notify_transition+0x3e/0x70
  [15052.030240]  [] cpufreq_freq_transition_begin+0xe8/0x130
  [15052.054522]  [] ? ucs2_strncmp+0x70/0x70
  [15052.078208]  [] __target_index+0xbf/0x1a0
  [15052.101348]  [] __cpufreq_driver_target+0xfc/0x160
  [15052.124250]  [] od_check_cpu+0xa4/0xb0
  [15052.146789]  [] dbs_check_cpu+0x16c/0x1c0
  [15052.168935]  [] od_dbs_timer+0x11d/0x180
  [15052.190607]  [] process_one_work+0x17f/0x4c0
  [15052.211825]  [] worker_thread+0x11b/0x3f0
  [15052.232490]  [] ? create_and_start_worker+0x80/0x80
  [15052.253127]  [] kthread+0xc9/0xe0
  [15052.273292]  [] ? flush_kthread_worker+0xb0/0xb0
  [15052.293487]  [] ret_from_fork+0x7c/0xb0
  [15052.313544]  [] ? flush_kthread_worker+0xb0/0xb0
  …
  ===

  Also here is my lspci [2] and cpuinfo [3] as well.

  Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13
  kernel.

  No visible reason to trigger the bug. After hang machine doesn't respond via 
  network, there's no disk IO, and also it doesn't respond to pressing power 
  button in order to perform soft off.

  And here is kernel bugzilla bugreport [4].

  [1] https://gist.github.com/085af9da81197faf6637
  [2] https://gist.github.com/318ebda5576b099590b8
  [3] https://gist.github.com/9c1307463c7ad6835b2d
  [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701
  --- 
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-07-30 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  trusty
  Uname: Linux 3.16.0-031600-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1341195] Re: KVM guests getting slow by time

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

** This bug has been marked a duplicate of bug 1346917
   Using KSM on NUMA capable machines can cause KVM guest performance and 
stability issues

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

Title:
  KVM guests getting slow by time

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  There is a post with very similar symptoms on serverfault:

  http://serverfault.com/questions/609881/windows-server-2012-on-kvm-on-
  ubuntu-14-04-runs-well-for-a-while-and-then-slows/612084#612084

  
  Basically all kind of KVM guests are getting slow by time, both windows or 
linux. The more running guests, it happens sooner.
  Switching back to Saucy kernel is a good workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: qemu-kvm 2.0.0+dfsg-2ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Jul 12 22:18:49 2014
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1325560] Re: kvm virtio netdevs lose network connectivity under "enough" load

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

** This bug has been marked a duplicate of bug 1346917
   Using KSM on NUMA capable machines can cause KVM guest performance and 
stability issues

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

Title:
  kvm virtio netdevs lose network connectivity under "enough" load

Status in libvirt virtualization API:
  New
Status in The Linux Kernel:
  Incomplete
Status in “linux” package in Ubuntu:
  Confirmed
Status in “qemu-kvm” package in Ubuntu:
  Incomplete

Bug description:
  Networking breaks after awhile in kvm guests using virtio networking.
  We run data intensive jobs on our virtual cluster (OpenStack Grizzly
  Installed on Ubuntu 12.04 Server).  The job runs fine on a single
  worker VM (no data transfer involved). As soon as I add more nodes
  where the workers need to exchange some data, one of the worker VM
  goes down. Ping responds with 'host unreachable'. Logging in via the
  serial console shows no problems: eth0 is up, can ping the local host,
  but no outside connectivity. Restart the network
  (/etc/init.d/networking restart) does nothing. Reboot the machine and
  it comes alive again.

  14/06/01 18:30:06 INFO YarnClientClusterScheduler: 
YarnClientClusterScheduler.postStartHook done
  14/06/01 18:30:06 INFO MemoryStore: ensureFreeSpace(190758) called with 
curMem=0, maxMem=308713881
  14/06/01 18:30:06 INFO MemoryStore: Block broadcast_0 stored as values to 
memory (estimated size 186.3 KB, free 294.2 MB)
  14/06/01 18:30:06 INFO FileInputFormat: Total input paths to process : 1
  14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: 
/default-rack/10.20.20.28:50010
  14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: 
/default-rack/10.20.20.23:50010
  14/06/01 18:30:06 INFO SparkContext: Starting job: count at hello_spark.py:15
  14/06/01 18:30:06 INFO DAGScheduler: Got job 0 (count at hello_spark.py:15) 
with 2 output partitions (allowLocal=false)
  14/06/01 18:30:06 INFO DAGScheduler: Final stage: Stage 0 (count at 
hello_spark.py:15)
  14/06/01 18:30:06 INFO DAGScheduler: Parents of final stage: List()
  14/06/01 18:30:06 INFO DAGScheduler: Missing parents: List()
  14/06/01 18:30:06 INFO DAGScheduler: Submitting Stage 0 (PythonRDD[2] at 
count at hello_spark.py:15), which has no missing parents
  14/06/01 18:30:07 INFO DAGScheduler: Submitting 2 missing tasks from Stage 0 
(PythonRDD[2] at count at hello_spark.py:15)
  14/06/01 18:30:07 INFO YarnClientClusterScheduler: Adding task set 0.0 with 2 
tasks
  14/06/01 18:30:08 INFO YarnClientSchedulerBackend: Registered executor: 
Actor[akka.tcp://sparkExecutor@host-10-20-20-28.novalocal:44417/user/Executor#-1352071582]
 with ID 1
  14/06/01 18:30:08 INFO TaskSetManager: Starting task 0.0:0 as TID 0 on 
executor 1: host-10-20-20-28.novalocal (PROCESS_LOCAL)
  14/06/01 18:30:08 INFO TaskSetManager: Serialized task 0.0:0 as 3123 bytes in 
14 ms
  14/06/01 18:30:09 INFO BlockManagerMasterActor$BlockManagerInfo: Registering 
block manager host-10-20-20-28.novalocal:42960 with 588.8 MB RAM
  14/06/01 18:30:16 INFO BlockManagerMasterActor$BlockManagerInfo: Added 
rdd_1_0 in memory on host-10-20-20-28.novalocal:42960 (size: 308.2 MB, free: 
280.7 MB)
  14/06/01 18:30:17 INFO YarnClientSchedulerBackend: Registered executor: 
Actor[akka.tcp://sparkExecutor@host-10-20-20-23.novalocal:58126/user/Executor#1079893974]
 with ID 2
  14/06/01 18:30:17 INFO TaskSetManager: Starting task 0.0:1 as TID 1 on 
executor 2: host-10-20-20-23.novalocal (PROCESS_LOCAL)
  14/06/01 18:30:17 INFO TaskSetManager: Serialized task 0.0:1 as 3123 bytes in 
1 ms
  14/06/01 18:30:17 INFO BlockManagerMasterActor$BlockManagerInfo: Registering 
block manager host-10-20-20-23.novalocal:56776 with 588.8 MB RAM
  fj14/06/01 18:31:20 WARN BlockManagerMasterActor: Removing BlockManager 
BlockManagerId(1, host-10-20-20-28.novalocal, 42960, 0) with no recent heart 
beats: 55828ms exceeds 45000ms
  14/06/01 18:42:23 INFO YarnClientSchedulerBackend: Executor 2 disconnected, 
so removing it
  14/06/01 18:42:23 ERROR YarnClientClusterScheduler: Lost executor 2 on 
host-10-20-20-23.novalocal: remote Akka client disassociated

  The same job finishes flawlessly on a single worker.

  System Information:
  ==

  Description: Ubuntu 12.04.4 LTS
  Release: 12.04

  Linux 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan 30 17:24:40 UTC
  2014 x86_64

  libvirt-bin:
  --
Installed: 1.1.1-0ubuntu8~cloud2
Candidate: 1.1.1-0ubuntu8.7~cloud1
Version table:
   1.1.1-0ubuntu8.7~cloud1 0
  500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ 
precise-updates/havana/main amd64 Packages
   *** 1.1.1-0ubuntu8~cloud2 0
  100 /var/lib/dpkg/status
   0.9.8-2ubuntu17.19 0
  500 http://se.archive.ubuntu.com/ubuntu/ precise-

[Kernel-packages] [Bug 1352567] [NEW] OOPS in cpufreq driver with AMD Kaveri CPU

2014-08-04 Thread post-factum

Public bug reported:

Occasionally I get my machine hung completely. Fortunately, I've got and saved 
oops listing using netconsole before hang, and here it is [1].

Here is little piece of oops from the link above:

===
[15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4
[15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20
…
[15051.956205] Call Trace:
[15051.980641]  [] ? __cpufreq_notify_transition+0x95/0x1e0
[15052.005640]  [] cpufreq_notify_transition+0x3e/0x70
[15052.030240]  [] cpufreq_freq_transition_begin+0xe8/0x130
[15052.054522]  [] ? ucs2_strncmp+0x70/0x70
[15052.078208]  [] __target_index+0xbf/0x1a0
[15052.101348]  [] __cpufreq_driver_target+0xfc/0x160
[15052.124250]  [] od_check_cpu+0xa4/0xb0
[15052.146789]  [] dbs_check_cpu+0x16c/0x1c0
[15052.168935]  [] od_dbs_timer+0x11d/0x180
[15052.190607]  [] process_one_work+0x17f/0x4c0
[15052.211825]  [] worker_thread+0x11b/0x3f0
[15052.232490]  [] ? create_and_start_worker+0x80/0x80
[15052.253127]  [] kthread+0xc9/0xe0
[15052.273292]  [] ? flush_kthread_worker+0xb0/0xb0
[15052.293487]  [] ret_from_fork+0x7c/0xb0
[15052.313544]  [] ? flush_kthread_worker+0xb0/0xb0
…
===

Also here is my lspci [2] and cpuinfo [3] as well.

Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13
kernel.

No visible reason to trigger the bug. After hang machine doesn't respond via 
network, there's no disk IO, and also it doesn't respond to pressing power 
button in order to perform soft off.

And here is kernel bugzilla bugreport [4].

[1] https://gist.github.com/085af9da81197faf6637
[2] https://gist.github.com/318ebda5576b099590b8
[3] https://gist.github.com/9c1307463c7ad6835b2d
[4] https://bugzilla.kernel.org/show_bug.cgi?id=81701

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1352567

Title:
  OOPS in cpufreq driver with AMD Kaveri CPU

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Occasionally I get my machine hung completely. Fortunately, I've got and 
saved 
  oops listing using netconsole before hang, and here it is [1].

  Here is little piece of oops from the link above:

  ===
  [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4
  [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20
  …
  [15051.956205] Call Trace:
  [15051.980641]  [] ? __cpufreq_notify_transition+0x95/0x1e0
  [15052.005640]  [] cpufreq_notify_transition+0x3e/0x70
  [15052.030240]  [] cpufreq_freq_transition_begin+0xe8/0x130
  [15052.054522]  [] ? ucs2_strncmp+0x70/0x70
  [15052.078208]  [] __target_index+0xbf/0x1a0
  [15052.101348]  [] __cpufreq_driver_target+0xfc/0x160
  [15052.124250]  [] od_check_cpu+0xa4/0xb0
  [15052.146789]  [] dbs_check_cpu+0x16c/0x1c0
  [15052.168935]  [] od_dbs_timer+0x11d/0x180
  [15052.190607]  [] process_one_work+0x17f/0x4c0
  [15052.211825]  [] worker_thread+0x11b/0x3f0
  [15052.232490]  [] ? create_and_start_worker+0x80/0x80
  [15052.253127]  [] kthread+0xc9/0xe0
  [15052.273292]  [] ? flush_kthread_worker+0xb0/0xb0
  [15052.293487]  [] ret_from_fork+0x7c/0xb0
  [15052.313544]  [] ? flush_kthread_worker+0xb0/0xb0
  …
  ===

  Also here is my lspci [2] and cpuinfo [3] as well.

  Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13
  kernel.

  No visible reason to trigger the bug. After hang machine doesn't respond via 
  network, there's no disk IO, and also it doesn't respond to pressing power 
  button in order to perform soft off.

  And here is kernel bugzilla bugreport [4].

  [1] https://gist.github.com/085af9da81197faf6637
  [2] https://gist.github.com/318ebda5576b099590b8
  [3] https://gist.github.com/9c1307463c7ad6835b2d
  [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701

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

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

[Kernel-packages] [Bug 1351353] Re: Kernel oops related to running kvm (?)

Hi, can you explain why you think this bug is related to KVM?
>From the backtrace it looks like an intel graphics issue.
Thanks

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

Title:
  Kernel oops related to running kvm (?)

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  My system suddently became unresponsive so I tried to SysRq s/u/b and
  I think that's what caused another problem.

  Either way, my system hard-locked.


  Aug  1 16:15:59 faire kernel: [31778.831601] [ cut here 
]
  Aug  1 16:15:59 faire kernel: [31778.831644] WARNING: CPU: 2 PID: 1834 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3313 
intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]()
  Aug  1 16:15:59 faire kernel: [31778.831646] Modules linked in: cdc_acm 
ums_cypress btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs 
libcrc32c veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr 
twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 
twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 
camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts 
serpent_generic blowfish_generic blowfish_x86_64 blowfish_common 
cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 
crypto_null af_key xfrm_algo arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm microcode snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi joydev binfmt_misc serio_raw iwlmvm 
mac80211 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep lpc_ich 
rtsx_pci_ms iwlwifi memstick snd_pcm cfg80211 uvcvideo videobuf2_vmalloc 
videobuf2_memops shpchp videobuf2_core v4l2_common mei_me videodev mei media 
thinkpad_acpi nvram btusb snd_seq_midi snd_seq_midi_event bluetooth snd_rawmidi 
6lowpan_iphc snd_seq snd_seq_device snd_timer snd intel_smartconnect soundcore 
cuse parport_pc mac_hid ppdev lp parport nls_iso8859_1 uas usb_storage 
hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp 
pps_core i2c_algo_bit drm_kms_helper wmi drm video
  Aug  1 16:15:59 faire kernel: [31778.831718] CPU: 2 PID: 1834 Comm: Xorg Not 
tainted 3.16.0-6-generic #11-Ubuntu
  Aug  1 16:15:59 faire kernel: [31778.831720] Hardware name: LENOVO 
20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014
  Aug  1 16:15:59 faire kernel: [31778.831721]  0009 
8800d6233c10 82755538 
  Aug  1 16:15:59 faire kernel: [31778.831724]  8800d6233c48 
8206bb0d  880308eed000
  Aug  1 16:15:59 faire kernel: [31778.831726]  880304108240 
8800da1e1000 8800da1e1000 8800d6233c58
  Aug  1 16:15:59 faire kernel: [31778.831729] Call Trace:
  Aug  1 16:15:59 faire kernel: [31778.831735]  [] 
dump_stack+0x45/0x56
  Aug  1 16:15:59 faire kernel: [31778.831739]  [] 
warn_slowpath_common+0x7d/0xa0
  Aug  1 16:15:59 faire kernel: [31778.831742]  [] 
warn_slowpath_null+0x1a/0x20
  Aug  1 16:15:59 faire kernel: [31778.831765]  [] 
intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]
  Aug  1 16:15:59 faire kernel: [31778.831769]  [] ? 
prepare_to_wait_event+0x100/0x100
  Aug  1 16:15:59 faire kernel: [31778.831787]  [] 
intel_crtc_disable_planes+0x33/0x1c0 [i915]
  Aug  1 16:15:59 faire kernel: [31778.831790]  [] ? 
__ww_mutex_lock+0x1b/0x97
  Aug  1 16:15:59 faire kernel: [31778.831807]  [] 
haswell_crtc_disable+0x55/0x2f0 [i915]
  Aug  1 16:15:59 faire kernel: [31778.831809]  [] ? 
mutex_lock+0x12/0x2f
  Aug  1 16:15:59 faire kernel: [31778.831823]  [] 
intel_crtc_update_dpms+0x67/0xa0 [i915]
  Aug  1 16:15:59 faire kernel: [31778.831835]  [] 
intel_connector_dpms+0x59/0x70 [i915]
  Aug  1 16:15:59 faire kernel: [31778.831848]  [] 
drm_mode_obj_set_property_ioctl+0x39f/0x3b0 [drm]
  Aug  1 16:15:59 faire kernel: [31778.831858]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
  Aug  1 16:15:59 faire kernel: [31778.831860]  [] ? 
ipv4_conntrack_defrag+0xb0/0x163 [nf_defrag_ipv4]
  Aug  1 16:15:59 faire kernel: [31778.831868]  [] 
drm_ioctl+0x1ec/0x660 [drm]
  Aug  1 16:15:59 faire kernel: [31778.831873]  [] 
do_vfs_ioctl+0x2e0/0x4c0
  Aug  1 16:15:59 faire kernel: [31778.831876]  [] ? 
vtime_account_user+0x54/0x60
  Aug  1 16:15:59 faire kernel: [31778.831878]  [] 
SyS_ioctl+0x81/0xa0
  Aug  1 16:15:59 faire kernel: [31778.831880]  [] 
tracesys+0xe1/0xe6
  Aug  1 16:15:59 faire kernel: [31778.831881] ---[ end trace bb931f1719ba6be2 
]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-ge

[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

2014-08-04 Thread Kamal Mostafa

Thanks David!  I've queued up your comment #8 backport for v3.13-stable
(it will appear in v3.13.11.6).

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

Title:
  Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” source package in Trusty:
  Triaged

Bug description:
  Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while
  expanding the grant table (usually when requested by blkfront, when
  booting).  See an example trace below.

  This is caused by calling functions that are unsafe in atomic context.

  The fix (which has been submitted to 3.16) is available here (also
  attached):

  https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable
  /for-linus-3.16&id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168

  The fix is applicable to all kernel since 2.6.39 but only appears to
  trigger with the 3.13 kernel in 14.04.

  [2.577876] [ cut here ]
  [2.577896] kernel BUG at 
/build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239!
  [2.577910] invalid opcode:  [#1] SMP 
  [2.577922] Modules linked in:
  [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [2.577946] task: ec058000 ti: ec09 task.ti: ec09
  [2.577955] EIP: 0061:[] EFLAGS: 00010002 CPU: 0
  [2.577973] EIP is at enter_lazy.part.1+0x3/0x5
  [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: 
  [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50
  [2.578001]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069
  [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660
  [2.578027] Stack:
  [2.578032]  ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff 
edc01000 c1a93018
  [2.578052]   edc00fff  c193ce80 edc01000  
 
  [2.578076]  ed3ef588 ed3ef588  c1b87b70 ec091ad0 edc01000 
c1b65310 1000
  [2.578096] Call Trace:
  [2.578111]  [] paravirt_enter_lazy_mmu+0x24/0x30
  [2.578127]  [] apply_to_page_range+0x1a3/0x310
  [2.578141]  [] arch_gnttab_map_status+0x38/0x60
  [2.578152]  [] ? map_pte_fn+0x70/0x70
  [2.578166]  [] gnttab_map_frames_v2+0xb0/0x100
  [2.578182]  [] gnttab_map+0x95/0x120
  [2.578198]  [] ? blk_update_request+0x190/0x340
  [2.578209]  [] get_free_entries+0xd3/0x280
  [2.578221]  [] gnttab_alloc_grant_references+0x13/0x30
  [2.578238]  [] do_blkif_request+0x535/0x6f0
  [2.578253]  [] ? _raw_spin_unlock_irqrestore+0x1c/0x40
  [2.578269]  [] __blk_run_queue+0x2e/0x40
  [2.578280]  [] blk_start_queue+0x25/0x40
  [2.578291]  [] kick_pending_request_queues+0x1e/0x30
  [2.578304]  [] blkif_interrupt+0x69f/0x740
  [2.578318]  [] ? xen_set_pte_at+0xbf/0xf0
  [2.578335]  [] handle_irq_event_percpu+0x35/0x1a0
  [2.578351]  [] ? radix_tree_lookup+0xa/0x10
  [2.578364]  [] handle_irq_event+0x31/0x50
  [2.578376]  [] handle_edge_irq+0x66/0x110
  [2.578389]  [] __xen_evtchn_do_upcall+0x1c6/0x2c0
  [2.578402]  [] xen_evtchn_do_upcall+0x20/0x40
  [2.578415]  [] xen_do_upcall+0x7/0xc
  [2.578427]  [] ? xen_hypercall_xen_version+0x7/0x20
  [2.578441]  [] ? xen_force_evtchn_callback+0xf/0x20
  [2.578454]  [] check_events+0x8/0xc
  [2.578464]  [] ? xen_restore_fl_direct_reloc+0x4/0x4
  [2.578480]  [] ? xen_batched_set_pte+0xb3/0x160
  [2.578493]  [] xen_set_pte_at+0x28/0xf0
  [2.578505]  [] ? __raw_callee_save_xen_pte_val+0x6/0x8
  [2.578521]  [] copy_pte_range+0x258/0x4c0
  [2.578534]  [] copy_page_range+0x1d7/0x2e0
  [2.578549]  [] dup_mm+0x28e/0x4f0
  [2.578561]  [] copy_process.part.33+0xfa6/0x10d0
  [2.578574]  [] do_fork+0xc1/0x2c0
  [2.578591]  [] ? SyS_rt_sigprocmask+0x76/0xa0
  [2.578604]  [] SyS_clone+0x25/0x30
  [2.578615]  [] sysenter_do_call+0x12/0x28
  [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba 
a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 <0f> 0b 
55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5
  [2.578745] EIP: [] enter_lazy.part.1+0x3/0x5 SS:ESP 
0069:ec091a50
  [2.578765] ---[ end trace ab5b5344be71ca3d ]---
  [2.578775] Kernel panic - not syncing: Fatal exception in interrupt

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

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

[Kernel-packages] [Bug 1208455] Re: general protection fault running apt-get inside double nested kvm VM

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

Title:
  general protection fault running apt-get inside double nested kvm VM

Status in “linux” package in Ubuntu:
  Fix Released
Status in “qemu-kvm” package in Ubuntu:
  Confirmed
Status in “linux” source package in Saucy:
  In Progress
Status in “qemu-kvm” source package in Saucy:
  Confirmed

Bug description:
  Attempting to run apt-get in a nested vm hosted in OpenStack results
  in a  general protection fault in the kernel in the nested VM.

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

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

[Kernel-packages] [Bug 1308341] Re: Multiple CPUs causes blue screen on Windows guest (14.04 regression)

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

** This bug has been marked a duplicate of bug 1307473
   guest hang due to missing clock interrupt

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

Title:
  Multiple CPUs causes blue screen on Windows guest (14.04 regression)

Status in QEMU:
  New
Status in “linux” package in Ubuntu:
  Confirmed
Status in “qemu” package in Ubuntu:
  Confirmed

Bug description:
  Configuring a Windows 7 guest using more than one CPU cases the guest to 
fail. This happens after a few hours after guest boot. This is the error on the 
blue screen:
  "A clock interrupt was not received on a secondary processor within the 
allocated time interval"

  After resetting, the guest will never boot and a new bluescreen with
  the error "STOP: 0x005c" appears. Shutting down the guest
  completely and restarting it will allow it to boot and run for a few
  hours again.

  The guest was created using virt-manager. The error happens with or
  without virtio devices and with both 32-bit and 64-bit Windows 7
  guests.

  I am using Ubuntu 14.04 release candidate.

  qemu-kvm version 2.0.0~rc1+dfsg-0ubuntu3

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

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

[Kernel-packages] [Bug 1325560] Re: kvm virtio netdevs lose network connectivity under "enough" load

I believe this is a duplicate of bug 1346917.
A test kernel has been built in comment #1 of that bug. 
Please test with this, if it fixes your issue mark this bug as a duplicate of 
1346917.
This fix will make it most likely into linux 3.13.0-33.
Thanks,

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

Title:
  kvm virtio netdevs lose network connectivity under "enough" load

Status in libvirt virtualization API:
  New
Status in The Linux Kernel:
  Incomplete
Status in “linux” package in Ubuntu:
  Confirmed
Status in “qemu-kvm” package in Ubuntu:
  Incomplete

Bug description:
  Networking breaks after awhile in kvm guests using virtio networking.
  We run data intensive jobs on our virtual cluster (OpenStack Grizzly
  Installed on Ubuntu 12.04 Server).  The job runs fine on a single
  worker VM (no data transfer involved). As soon as I add more nodes
  where the workers need to exchange some data, one of the worker VM
  goes down. Ping responds with 'host unreachable'. Logging in via the
  serial console shows no problems: eth0 is up, can ping the local host,
  but no outside connectivity. Restart the network
  (/etc/init.d/networking restart) does nothing. Reboot the machine and
  it comes alive again.

  14/06/01 18:30:06 INFO YarnClientClusterScheduler: 
YarnClientClusterScheduler.postStartHook done
  14/06/01 18:30:06 INFO MemoryStore: ensureFreeSpace(190758) called with 
curMem=0, maxMem=308713881
  14/06/01 18:30:06 INFO MemoryStore: Block broadcast_0 stored as values to 
memory (estimated size 186.3 KB, free 294.2 MB)
  14/06/01 18:30:06 INFO FileInputFormat: Total input paths to process : 1
  14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: 
/default-rack/10.20.20.28:50010
  14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: 
/default-rack/10.20.20.23:50010
  14/06/01 18:30:06 INFO SparkContext: Starting job: count at hello_spark.py:15
  14/06/01 18:30:06 INFO DAGScheduler: Got job 0 (count at hello_spark.py:15) 
with 2 output partitions (allowLocal=false)
  14/06/01 18:30:06 INFO DAGScheduler: Final stage: Stage 0 (count at 
hello_spark.py:15)
  14/06/01 18:30:06 INFO DAGScheduler: Parents of final stage: List()
  14/06/01 18:30:06 INFO DAGScheduler: Missing parents: List()
  14/06/01 18:30:06 INFO DAGScheduler: Submitting Stage 0 (PythonRDD[2] at 
count at hello_spark.py:15), which has no missing parents
  14/06/01 18:30:07 INFO DAGScheduler: Submitting 2 missing tasks from Stage 0 
(PythonRDD[2] at count at hello_spark.py:15)
  14/06/01 18:30:07 INFO YarnClientClusterScheduler: Adding task set 0.0 with 2 
tasks
  14/06/01 18:30:08 INFO YarnClientSchedulerBackend: Registered executor: 
Actor[akka.tcp://sparkExecutor@host-10-20-20-28.novalocal:44417/user/Executor#-1352071582]
 with ID 1
  14/06/01 18:30:08 INFO TaskSetManager: Starting task 0.0:0 as TID 0 on 
executor 1: host-10-20-20-28.novalocal (PROCESS_LOCAL)
  14/06/01 18:30:08 INFO TaskSetManager: Serialized task 0.0:0 as 3123 bytes in 
14 ms
  14/06/01 18:30:09 INFO BlockManagerMasterActor$BlockManagerInfo: Registering 
block manager host-10-20-20-28.novalocal:42960 with 588.8 MB RAM
  14/06/01 18:30:16 INFO BlockManagerMasterActor$BlockManagerInfo: Added 
rdd_1_0 in memory on host-10-20-20-28.novalocal:42960 (size: 308.2 MB, free: 
280.7 MB)
  14/06/01 18:30:17 INFO YarnClientSchedulerBackend: Registered executor: 
Actor[akka.tcp://sparkExecutor@host-10-20-20-23.novalocal:58126/user/Executor#1079893974]
 with ID 2
  14/06/01 18:30:17 INFO TaskSetManager: Starting task 0.0:1 as TID 1 on 
executor 2: host-10-20-20-23.novalocal (PROCESS_LOCAL)
  14/06/01 18:30:17 INFO TaskSetManager: Serialized task 0.0:1 as 3123 bytes in 
1 ms
  14/06/01 18:30:17 INFO BlockManagerMasterActor$BlockManagerInfo: Registering 
block manager host-10-20-20-23.novalocal:56776 with 588.8 MB RAM
  fj14/06/01 18:31:20 WARN BlockManagerMasterActor: Removing BlockManager 
BlockManagerId(1, host-10-20-20-28.novalocal, 42960, 0) with no recent heart 
beats: 55828ms exceeds 45000ms
  14/06/01 18:42:23 INFO YarnClientSchedulerBackend: Executor 2 disconnected, 
so removing it
  14/06/01 18:42:23 ERROR YarnClientClusterScheduler: Lost executor 2 on 
host-10-20-20-23.novalocal: remote Akka client disassociated

  The same job finishes flawlessly on a single worker.

  System Information:
  ==

  Description: Ubuntu 12.04.4 LTS
  Release: 12.04

  Linux 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan 30 17:24:40 UTC
  2014 x86_64

  libvirt-bin:
  --
Installed: 1.1.1-0ubuntu8~cloud2
Candidate: 1.1.1-0ubuntu8.7~cloud1
Version table:
   1.1.1-0ubuntu8.7~cloud1 0
  500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ 
precise-updates/havana/main amd64 Packages
   *** 1.1.1-0ubuntu8~cloud2 0
  100 /var/lib/dpkg/status
   0.9.8-2ubuntu17.19 0
  500 http://se.archive.ubuntu.com/

Re: [Kernel-packages] [Bug 1349572] Re: Wireless network disconnections on Dell XPS 13

2014-08-04 Thread Seth Forshee

On Mon, Aug 04, 2014 at 08:59:52PM -, Marcel Miguel wrote:
> Hi Seth,
> I had no disconnections, now for a 3h period (a fabolous improvement!)

Good!

> Speed seems to decrease, at least with a speedtest:
>   http://www.speedtest.net/my-result/3668258447
> 
> I know, it is not  a valid test, but maybe is a reference. I tested it
> with various servers and seems a limit at about 5Mbps.

I don't really think this change should affect your speed at all. A more
reliable test of performance would be to use iperf against a machine
with a wired connection to the same network, if possible, and make sure
that you're using the same network with all kernels. If it's a network
with multiple access points then you could get different results though
depending on the AP you happen to be connected to, channel, etc.

> Firmware  is 22.24.8.0.
> 
> With this versions I don't get an strange phenomenon where "System Load
> Indicator" showed equally separated peaks of infinity connection
> download speed.
> 
> Is there a method to know if there was a disconnection? I mean some kind
> of "dmesg | grep "

You could check /var/log/syslog for the string "disconnect", e.g. 'grep
-i disconnect /var/log/syslog', but that could contain logs from prior
boots so you could get false positivies. The particular problem I was
seeing (disconnection due to beacon loss) result in messages like this:

wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=4

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

Title:
  Wireless network disconnections on Dell XPS 13

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With kernel 3.13.0.30 and 22.1.7.0, there are lots of wireless disconnections.
  Tested also with kernel 3.13.0.32 and 22.24.8.0 , also lots of wireles 
disconnections. 

  The AP is an ASL-26555 from Movistar(Spain). Firmware version:
  v2.0.0.51B_ESv6

  Seems that when the computer is working for some time it is more easy
  to reproduce this beahviour.

  Added this bug as sugested in #1293569, comment #91.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-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:  marcel 2611 F pulseaudio
   /dev/snd/controlC0:  marcel 2611 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 28 22:20:19 2014
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 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.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (101 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  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.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (103 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/11/2013
  dmi.bios.vend

[Kernel-packages] [Bug 1348670] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010, set_nfsv4_acl_one+0x21/0xb0 [nfsd]

2014-08-04 Thread Harald Nordgård-Hansen

It would be nice if this bug could be given some priority, it is making
it hard to run precise as an nfs server.  I've just spent some hours
chasing down this on our systems, and can confirm that it also affects
kernels 3.8.0-44 and 3.13.0-32.

It is quite easy to trigger, a 'cp -a ...' on any nfs client will kill
one nfsd thread on the server.  Once all threads are gone, the server is
dead and must be rebooted.  Restarting the nfs-kernel-server service has
no effect.

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0010, set_nfsv4_acl_one+0x21/0xb0 [nfsd]

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

Bug description:
  I've seen this happen twice in the last 8 days on an NFS server
  running Ubuntu precise and kernels 3.2.0-65.98-generic (on the first
  occasion) and 3.2.0-67.101-generic (the second time), amd64. This
  never happened before in several months of operation; until 2014-07-01
  this server was running an older 3.2.0 kernel.

  When this error appears in the logs, the system stops answering NFS
  RPCs (e.g., "rpcinfo -u localhost nfs 3" hangs) and a reboot is
  necessary to restore NFS service. A more detailed stack trace follows.
  Looking at the source code (fs/nfsd/vfs.c:set_nfsv4_acl_one()) I see
  that the call posix_acl_xattr_size(pacl->a_count) is not preceded by a
  check that pacl != NULL. Could this be related to the following entry
  in the changelog for 3.2.0-65.98?

* NFSD: Call ->set_acl with a NULL ACL structure if no entries
  - LP: #1328154

  Jul 24 10:12:53 server kernel: [575939.742131] IP: [] 
set_nfsv4_acl_one+0x21/0xb0 [nfsd]
  Jul 24 10:12:53 server kernel: [575939.742131] PGD c243bb067 PUD c2400a067 
PMD 0
  Jul 24 10:12:53 server kernel: [575939.742131] Oops:  [#1] SMP
  Jul 24 10:12:53 server kernel: [575939.742131] CPU 3
  Jul 24 10:12:53 server kernel: [575939.742131] Modules linked in: usblp btrfs 
zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs 
reiserfs ext2 cts openafs(P) xt_tcpudp ipmi_si ipmi_devintf ipmi_msghandler 
iptable_filter ip_tables x_tables autofs4 bnep parport_pc rfcomm bluetooth 
ppdev binfmt_misc rpcsec_gss_krb5 nfsd nfs lockd fscache auth_rpcgss nfs_acl 
sunrpc xfs dm_crypt bridge stp psmouse hpilo sp5100_tco i2c_piix4 
amd64_edac_mod hpwdt edac_core k10temp edac_mce_amd joydev serio_raw 
acpi_power_meter mac_hid lp parport raid10 raid456 async_pq async_xor xor 
async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath linear 
radeon ttm drm_kms_helper drm osst usbhid hid st ch i2c_algo_bit pata_atiixp 
hpsa bnx2
  Jul 24 10:12:53 server kernel: [575939.742131]
  Jul 24 10:12:53 server kernel: [575939.742131] Pid: 2523, comm: nfsd Tainted: 
P O 3.2.0-67-generic #101-Ubuntu HP ProLiant DL385 G7
  Jul 24 10:12:53 server kernel: [575939.742131] RIP: 0010:[] 
[] set_nfsv4_acl_one+0x21/0xb0 [nfsd]
  Jul 24 10:12:53 server kernel: [575939.742131] RSP: 0018:880422085ce0 
EFLAGS: 00010282
  Jul 24 10:12:53 server kernel: [575939.742131] RAX: 4000 RBX: 
880e29b16cc0 RCX: 013cc2cc
  Jul 24 10:12:53 server kernel: [575939.742131] RDX: a0583374 RSI: 
 RDI: 880e29b16cc0
  Jul 24 10:12:53 server kernel: [575939.742131] RBP: 880422085d10 R08: 
ea002cdf3b80 R09: a055c4af
  Jul 24 10:12:53 server kernel: [575939.742131] R10: 880b37ceed00 R11: 
4004 R12: 
  Jul 24 10:12:53 server kernel: [575939.742131] R13: 8807f56418c0 R14: 
 R15: 880c2268d180
  Jul 24 10:12:53 server kernel: [575939.742131] FS: 7fafd700() 
GS:88103fc8() knlGS:
  Jul 24 10:12:53 server kernel: [575939.742131] CS: 0010 DS:  ES:  
CR0: 8005003b
  Jul 24 10:12:53 server kernel: [575939.742131] CR2: 0010 CR3: 
000c22d6c000 CR4: 06e0
  Jul 24 10:12:53 server kernel: [575939.742131] DR0:  DR1: 
 DR2: 
  Jul 24 10:12:53 server kernel: [575939.742131] DR3:  DR6: 
0ff0 DR7: 0400
  Jul 24 10:12:53 server kernel: [575939.742131] Process nfsd (pid: 2523, 
threadinfo 880422084000, task 880425964500)
  Jul 24 10:12:53 server kernel: [575939.742131] Stack:
  Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d040 
880e29b16cc0  8807f56418c0
  Jul 24 10:12:53 server kernel: [575939.742131]  
880c2268d180 880422085d50 a055d5e3
  Jul 24 10:12:53 server kernel: [575939.742131] 880b37cee840 
 880c22684000 880c2268d040
  Jul 24 10:12:53 server kernel: [575939.742131] Call Trace:
  Jul 24 10:12:53 server kernel: [575939.742131] []

[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute

2014-08-04 Thread Jackson

im new to fourms... so please excuse my errors... i just had a ubuntu one 
acount so i signed in just to tell
Hans Zaaijer (h-l-zaaijer) in case you didnt figure it out yet...(i know im 4 
months late...)(i love periods)

""Hello all,

Is it possible to describe step #1 in Suthars solution (= "downgrading the 
kernel") in more detail,
(step by step) for this beginner?
How do I download and install 3 new kernel files exactly?
(Steps 2 etc I can understand, only step #1 is too abstract).

Thanks in advance, I really want to use Ubuntu on my Acer C720,
but the boot (1 minute) indeed is too slow.

Regards and thanks from Hans""


follow these instruction they work nicley...
http://goo.gl/Onvd0H

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

Title:
  Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when
  booting up, then resumes booting to the login screen, after 1 minute

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into 
Ubuntu.  Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 
minute or longer, then it resumes booting up to the login screen.  On Ubuntu 
13.10 it only takes about 7 seconds to get to the login screen, while it takes 
almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I 
hope this issue could be fixed.
   
  I have the Acer C720 (chromebook) that has been enabled to use legacy boot so 
I can use other OS's.  Other Acer C720 users have been faceing the same problem 
also.

  Video of Boot
  https://www.youtube.com/watch?v=PVkFTsEzS80

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

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

[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute

2014-08-04 Thread Jackson

*EDIT*


im new to fourms... so please excuse my errors... i just had a ubuntu one 
acount so i signed in just to tell
Hans Zaaijer (h-l-zaaijer) in case you didnt figure it out yet...(i know im 4 
months late...)(i love periods)

""Hello all,

Is it possible to describe step #1 in Suthars solution (= "downgrading the 
kernel") in more detail,
(step by step) for this beginner?
How do I download and install 3 new kernel files exactly?
(Steps 2 etc I can understand, only step #1 is too abstract).

Thanks in advance, I really want to use Ubuntu on my Acer C720,
but the boot (1 minute) indeed is too slow.

Regards and thanks from Hans""

follow these instruction they work nicley...
http://goo.gl/Onvd0H
Did not mention to 
OPEN TERMINAL and use those commands 
Also the "$" must be removed to be used in 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/1308264

Title:
  Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when
  booting up, then resumes booting to the login screen, after 1 minute

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into 
Ubuntu.  Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 
minute or longer, then it resumes booting up to the login screen.  On Ubuntu 
13.10 it only takes about 7 seconds to get to the login screen, while it takes 
almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I 
hope this issue could be fixed.
   
  I have the Acer C720 (chromebook) that has been enabled to use legacy boot so 
I can use other OS's.  Other Acer C720 users have been faceing the same problem 
also.

  Video of Boot
  https://www.youtube.com/watch?v=PVkFTsEzS80

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

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

[Kernel-packages] [Bug 1279041] Re: /proc/sys/net/ipv4/ip_local_reserved_ports not writable because of apparmor

2014-08-04 Thread sailajay

Setting to confirmed as it happens on the  kernel 3.15.8

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

Title:
  /proc/sys/net/ipv4/ip_local_reserved_ports not writable because of
  apparmor

Status in “linux” package in Ubuntu:
  Confirmed
Status in “lxc” package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  arch: amd64
  Kernel: 3.13.0-8-generic #27-Ubuntu x86_64 GNU/Linux

  LXC container

  lxc-create --version
  1.0.0.beta4

  file: /proc/sys/net/ipv4/ip_local_reserved_port

  Does not exist and is not writable in a started container. Apparmor
  seems to block creating this file?

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

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

[Kernel-packages] [Bug 1349572] Re: Wireless network disconnections on Dell XPS 13

2014-08-04 Thread Marcel Miguel

Hi Seth,
I had no disconnections, now for a 3h period (a fabolous improvement!)

Speed seems to decrease, at least with a speedtest:
  http://www.speedtest.net/my-result/3668258447

I know, it is not  a valid test, but maybe is a reference. I tested it
with various servers and seems a limit at about 5Mbps.

Firmware  is 22.24.8.0.

With this versions I don't get an strange phenomenon where "System Load
Indicator" showed equally separated peaks of infinity connection
download speed.

Is there a method to know if there was a disconnection? I mean some kind
of "dmesg | grep "

Tomorrow I'll try it at other locations.

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

Title:
  Wireless network disconnections on Dell XPS 13

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With kernel 3.13.0.30 and 22.1.7.0, there are lots of wireless disconnections.
  Tested also with kernel 3.13.0.32 and 22.24.8.0 , also lots of wireles 
disconnections. 

  The AP is an ASL-26555 from Movistar(Spain). Firmware version:
  v2.0.0.51B_ESv6

  Seems that when the computer is working for some time it is more easy
  to reproduce this beahviour.

  Added this bug as sugested in #1293569, comment #91.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-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:  marcel 2611 F pulseaudio
   /dev/snd/controlC0:  marcel 2611 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 28 22:20:19 2014
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 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.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (101 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  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.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (103 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubun

[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

2014-08-04 Thread Andrey Kislyuk

Attaching a typical trace on one of our affected machines. This shows
the crash happening roughly 33 seconds after boot, which is where we
observe most of these. Some also happen much later after boot.

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

Title:
  Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” source package in Trusty:
  Triaged

Bug description:
  Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while
  expanding the grant table (usually when requested by blkfront, when
  booting).  See an example trace below.

  This is caused by calling functions that are unsafe in atomic context.

  The fix (which has been submitted to 3.16) is available here (also
  attached):

  https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable
  /for-linus-3.16&id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168

  The fix is applicable to all kernel since 2.6.39 but only appears to
  trigger with the 3.13 kernel in 14.04.

  [2.577876] [ cut here ]
  [2.577896] kernel BUG at 
/build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239!
  [2.577910] invalid opcode:  [#1] SMP 
  [2.577922] Modules linked in:
  [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [2.577946] task: ec058000 ti: ec09 task.ti: ec09
  [2.577955] EIP: 0061:[] EFLAGS: 00010002 CPU: 0
  [2.577973] EIP is at enter_lazy.part.1+0x3/0x5
  [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: 
  [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50
  [2.578001]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069
  [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660
  [2.578027] Stack:
  [2.578032]  ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff 
edc01000 c1a93018
  [2.578052]   edc00fff  c193ce80 edc01000  
 
  [2.578076]  ed3ef588 ed3ef588  c1b87b70 ec091ad0 edc01000 
c1b65310 1000
  [2.578096] Call Trace:
  [2.578111]  [] paravirt_enter_lazy_mmu+0x24/0x30
  [2.578127]  [] apply_to_page_range+0x1a3/0x310
  [2.578141]  [] arch_gnttab_map_status+0x38/0x60
  [2.578152]  [] ? map_pte_fn+0x70/0x70
  [2.578166]  [] gnttab_map_frames_v2+0xb0/0x100
  [2.578182]  [] gnttab_map+0x95/0x120
  [2.578198]  [] ? blk_update_request+0x190/0x340
  [2.578209]  [] get_free_entries+0xd3/0x280
  [2.578221]  [] gnttab_alloc_grant_references+0x13/0x30
  [2.578238]  [] do_blkif_request+0x535/0x6f0
  [2.578253]  [] ? _raw_spin_unlock_irqrestore+0x1c/0x40
  [2.578269]  [] __blk_run_queue+0x2e/0x40
  [2.578280]  [] blk_start_queue+0x25/0x40
  [2.578291]  [] kick_pending_request_queues+0x1e/0x30
  [2.578304]  [] blkif_interrupt+0x69f/0x740
  [2.578318]  [] ? xen_set_pte_at+0xbf/0xf0
  [2.578335]  [] handle_irq_event_percpu+0x35/0x1a0
  [2.578351]  [] ? radix_tree_lookup+0xa/0x10
  [2.578364]  [] handle_irq_event+0x31/0x50
  [2.578376]  [] handle_edge_irq+0x66/0x110
  [2.578389]  [] __xen_evtchn_do_upcall+0x1c6/0x2c0
  [2.578402]  [] xen_evtchn_do_upcall+0x20/0x40
  [2.578415]  [] xen_do_upcall+0x7/0xc
  [2.578427]  [] ? xen_hypercall_xen_version+0x7/0x20
  [2.578441]  [] ? xen_force_evtchn_callback+0xf/0x20
  [2.578454]  [] check_events+0x8/0xc
  [2.578464]  [] ? xen_restore_fl_direct_reloc+0x4/0x4
  [2.578480]  [] ? xen_batched_set_pte+0xb3/0x160
  [2.578493]  [] xen_set_pte_at+0x28/0xf0
  [2.578505]  [] ? __raw_callee_save_xen_pte_val+0x6/0x8
  [2.578521]  [] copy_pte_range+0x258/0x4c0
  [2.578534]  [] copy_page_range+0x1d7/0x2e0
  [2.578549]  [] dup_mm+0x28e/0x4f0
  [2.578561]  [] copy_process.part.33+0xfa6/0x10d0
  [2.578574]  [] do_fork+0xc1/0x2c0
  [2.578591]  [] ? SyS_rt_sigprocmask+0x76/0xa0
  [2.578604]  [] SyS_clone+0x25/0x30
  [2.578615]  [] sysenter_do_call+0x12/0x28
  [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba 
a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 <0f> 0b 
55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5
  [2.578745] EIP: [] enter_lazy.part.1+0x3/0x5 SS:ESP 
0069:ec091a50
  [2.578765] ---[ end trace ab5b5344be71ca3d ]---
  [2.578775] Kernel panic - not syncing: Fatal exception in interrupt

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

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

[Kernel-packages] [Bug 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels

2014-08-04 Thread Rafael David Tinoco

Since this is a test-only kernel you can install it directly:

# apt-get install linux-image-3.13.0-33

and it will get the kernel from the appropriate PPA:

inaddy@woodypecker:~$ apt-get install linux-image-3.13.0-33-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
  linux-headers-3.13.0-33-generic
The following NEW packages will be installed:
  linux-image-3.13.0-33-generic
0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded.
Need to get 15.1 MB of archives.
After this operation, 42.0 MB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/inaddy/sf00069767/ubuntu/ trusty/main 
linux-image-3.13.0-33-generic amd64 3.13.0-33.58hf00069767v20140730b1 [15.1 MB]
...

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

Title:
  0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work
  with 3.11 or 3.13 kernels

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  Impact: Bluetooth device stopped working. Device support regression.
  Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6
  Testcase: Comment #10

  Original Description:

  Bluetooth device stopped working after upgrading ubuntu to 13.10.

  ~$ lsusb:
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)

  ~$ hciconfig
  hci0: Type: BR/EDR  Bus: USB
   BD Address: 00:1B:10:00:0F:46  ACL MTU: 1017:8  SCO MTU: 64:0
   DOWN
   RX bytes:457 acl:0 sco:0 events:16 errors:0
   TX bytes:68 acl:0 sco:0 commands:16 errors:0
  ~$ hcitool dev
  Devices:

  device simply doesnt appear on bluetooth manager. blueman UI is
  broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-4-generic 3.11.0-4.9
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jorge  1954 F pulseaudio
   /dev/snd/controlC0:  jorge  1954 F pulseaudio
  Date: Fri Sep  6 22:32:45 2013
  HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: MEGAWARE MW-H61M-2H
  MarkForUpload: True
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-4-generic N/A
   linux-backports-modules-3.11.0-4-generic  N/A
   linux-firmware1.113
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago)
  dmi.bios.date: 08/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5 MW
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MW-H61M-2H
  dmi.board.vendor: MEGAWARE
  dmi.board.version: v1.3 - 17/07/2012 - MWX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEGAWARE
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MW-H61M-2H
  dmi.product.version: v1.3 - 17/07/2012 - MWX
  dmi.sys.vendor: MEGAWARE

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

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

[Kernel-packages] [Bug 1335795] Re: [Asus K55VM] It does not suspend after upgrading to 14.04

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

** This bug has been marked a duplicate of bug 1324697
   Suspend fails with kernel 3.13.0-27 and nouveau drivers

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

Title:
  [Asus K55VM] It does not suspend after upgrading to 14.04

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded to Ubuntu 14.04 from 13.10
  After that my laptop does not suspend. 
  The laptop has NVIDIA GEFORCE GT 630M Graphic card, with nouveau. It seems to 
fails when suspending.

  
  nisarg@nisarg:~$ cat /proc/version_signature
  Ubuntu 3.13.0-30.54-generic 3.13.11.2

  
  Here is the syslog. 

  Jun 30 14:52:22 nisarg kernel: [10157.974142] PM: Syncing filesystems ... 
done.
  Jun 30 14:52:22 nisarg kernel: [10158.308806] PM: Preparing system for mem 
sleep
  Jun 30 14:52:27 nisarg kernel: [10158.558616] Freezing user space processes 
... (elapsed 0.001 seconds) done.
  Jun 30 14:52:27 nisarg kernel: [10158.560394] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jun 30 14:52:27 nisarg kernel: [10158.561577] PM: Entering mem sleep
  Jun 30 14:52:27 nisarg kernel: [10158.561870] Suspending console(s) (use 
no_console_suspend to debug)
  Jun 30 14:52:27 nisarg kernel: [10158.562061] sd 0:0:0:0: [sda] Synchronizing 
SCSI cache
  Jun 30 14:52:27 nisarg kernel: [10158.562117] sd 0:0:0:0: [sda] Stopping disk
  Jun 30 14:52:27 nisarg kernel: [10158.580826] nouveau  [ DRM] suspending 
display...
  Jun 30 14:52:27 nisarg kernel: [10158.580828] nouveau  [ DRM] unpinning 
framebuffer(s)...
  Jun 30 14:52:27 nisarg kernel: [10158.580831] nouveau  [ DRM] evicting 
buffers...
  Jun 30 14:52:27 nisarg kernel: [10158.580832] nouveau  [ DRM] waiting for 
kernel channels to go idle...
  Jun 30 14:52:27 nisarg kernel: [10158.580876] nouveau  [ DRM] suspending 
client object trees...
  Jun 30 14:52:27 nisarg kernel: [10158.581164] nouveau  [ DRM] suspending 
kernel object tree...
  Jun 30 14:52:27 nisarg kernel: [10160.580652] nouveau E[   
PDISP][:01:00.0][0xc000857c][8802225fd700] fini timeout, 0xc2071008
  Jun 30 14:52:27 nisarg kernel: [10160.580654] nouveau E[   
PDISP][:01:00.0][0xc000857c][8802225fd700] failed suspend, -16
  Jun 30 14:52:27 nisarg kernel: [10160.580655] nouveau E[ DRM] 
0xd150:0xd15c7c00 suspend failed with -16
  Jun 30 14:52:27 nisarg kernel: [10160.580696] nouveau E[ DRM] 
0x:0xd150 suspend failed with -16
  Jun 30 14:52:27 nisarg kernel: [10160.580797] nouveau E[ DRM] 
0x:0x suspend failed with -16
  Jun 30 14:52:27 nisarg kernel: [10160.581459] nouveau E[ DRM] 
0x:0x suspend failed with -16
  Jun 30 14:52:27 nisarg kernel: [10160.581559] nouveau  [ DRM] resuming 
display...
  Jun 30 14:52:27 nisarg kernel: [10160.581578] nouveau E[ DRM] bo 
8801f711e800 pinned elsewhere: 0x0002 vs 0x0004
  Jun 30 14:52:27 nisarg kernel: [10160.581579] 
[drm:drm_helper_resume_force_mode] *ERROR* failed to set mode on crtc 
8800befd1000
  Jun 30 14:52:27 nisarg kernel: [10160.595633] pci_pm_suspend(): 
nouveau_pmops_suspend+0x0/0xb0 [nouveau] returns -16
  Jun 30 14:52:27 nisarg kernel: [10160.595638] dpm_run_callback(): 
pci_pm_suspend+0x0/0x150 returns -16
  Jun 30 14:52:27 nisarg kernel: [10160.595642] PM: Device :01:00.0 failed 
to suspend async: error -16
  Jun 30 14:52:27 nisarg kernel: [10160.595703] PM: Some devices failed to 
suspend, or early wake event detected

  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/controlC0:  nisarg 3437 F pulseaudio
nisarg19771 F pulseaudio
  CRDA:
   country IN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
  CurrentDesktop: Unity
  Date: Mon Jun 30 15:05:58 2014
  HibernationDevice: RESUME=UUID=8d9c6f2d-29cc-443a-8864-b5bdc278d3f5
  InstallationDate: Installed on 2014-01-08 (172 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUSTeK COMPUTER INC. K55VM
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=33430ee0-8da8-4984-9369-153bf9f4aa34 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
  SourcePackage

[Kernel-packages] [Bug 1324697] Re: Suspend fails with kernel 3.13.0-27 and nouveau drivers

** Summary changed:

- [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails with 
kernel 3.13.0-27
+ Suspend fails with kernel 3.13.0-27 and nouveau drivers

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

Title:
  Suspend fails with kernel 3.13.0-27 and nouveau drivers

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  See:

  http://askubuntu.com/questions/473214/laptop-suspend-broken-after-
  latest-kernel-update

  where it was suggested i file a kernel bug report.

  short version: after kernel upgrade to 3.13.0-27 my laptop will no
  longer suspend. Note that the apport bug report was generated while
  running 3.13.0-24 (had to switch back, this is my ever-day-use
  computer).

  I noted which log files changed before and after a suspend attempt,
  and those changes are attached (suspend.out). I compared these to a
  suspend with the -24 kernel and noted the changes in the referenced
  askubuntu post.

  Please let me know if i can provide any more details!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  conrad 2293 F pulseaudio
  Date: Thu May 29 17:20:15 2014
  HibernationDevice: RESUME=UUID=eb2b25c8-5489-484c-b3d1-b0db8834
  InstallationDate: Installed on 2013-02-14 (469 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=b2f1b8ee-6793-4070-8eb3-a07e52b30d03 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (41 days ago)
  dmi.bios.date: 10/03/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packard:rn181D:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 078F1020572620100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

This change was made by a bot.

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

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

[Kernel-packages] [Bug 1324697] Re: [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails with kernel 3.13.0-27

Oh, and I would rate this not as Medium, but as high. Suspend is a
really major feature nowadays in the workflow of people - if that dows
not work as a regression in a LTS kernel, I think this deserves a high
priority (just my 2 cents).

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

Title:
  [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails
  with kernel 3.13.0-27

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  See:

  http://askubuntu.com/questions/473214/laptop-suspend-broken-after-
  latest-kernel-update

  where it was suggested i file a kernel bug report.

  short version: after kernel upgrade to 3.13.0-27 my laptop will no
  longer suspend. Note that the apport bug report was generated while
  running 3.13.0-24 (had to switch back, this is my ever-day-use
  computer).

  I noted which log files changed before and after a suspend attempt,
  and those changes are attached (suspend.out). I compared these to a
  suspend with the -24 kernel and noted the changes in the referenced
  askubuntu post.

  Please let me know if i can provide any more details!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  conrad 2293 F pulseaudio
  Date: Thu May 29 17:20:15 2014
  HibernationDevice: RESUME=UUID=eb2b25c8-5489-484c-b3d1-b0db8834
  InstallationDate: Installed on 2013-02-14 (469 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=b2f1b8ee-6793-4070-8eb3-a07e52b30d03 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (41 days ago)
  dmi.bios.date: 10/03/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packard:rn181D:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 078F1020572620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1324697] Re: [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails with kernel 3.13.0-27

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

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

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

Title:
  [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails
  with kernel 3.13.0-27

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  See:

  http://askubuntu.com/questions/473214/laptop-suspend-broken-after-
  latest-kernel-update

  where it was suggested i file a kernel bug report.

  short version: after kernel upgrade to 3.13.0-27 my laptop will no
  longer suspend. Note that the apport bug report was generated while
  running 3.13.0-24 (had to switch back, this is my ever-day-use
  computer).

  I noted which log files changed before and after a suspend attempt,
  and those changes are attached (suspend.out). I compared these to a
  suspend with the -24 kernel and noted the changes in the referenced
  askubuntu post.

  Please let me know if i can provide any more details!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  conrad 2293 F pulseaudio
  Date: Thu May 29 17:20:15 2014
  HibernationDevice: RESUME=UUID=eb2b25c8-5489-484c-b3d1-b0db8834
  InstallationDate: Installed on 2013-02-14 (469 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=b2f1b8ee-6793-4070-8eb3-a07e52b30d03 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (41 days ago)
  dmi.bios.date: 10/03/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packard:rn181D:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 078F1020572620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1352379] Re: Network broken after resume

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  New

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

[Kernel-packages] [Bug 1350519] Re: [HP Pavilion dv6-1390ev] Could not force DPM to low

2014-08-04 Thread Mohd Imran Jamadar

I have gone thru the notes and noted that all this testing will take
time? to save time can you suggest a more speedy action?

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

Title:
  [HP Pavilion dv6-1390ev] Could not force DPM to low

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When resuming from suspend state to awake state, by pressing the power
  button of my laptop i see this message?

  
  Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] 
[drm:rv730_stop_dpm] *ERROR* Could not force DPM to low
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  imran  4208 F pulseaudio
   /dev/snd/controlC0:  imran  4208 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367
  InstallationDate: Installed on 2014-07-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.132~gd~t
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3628
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 18.51
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1348048] Re: [Nokia Nokia Booklet 3G] suspend/resume failure

2014-08-04 Thread JanneS

bug-exists-upstream

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

Title:
  [Nokia Nokia Booklet 3G] suspend/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  the computer doesn't wake up after suspend. (lubuntu 14.10)

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-5-generic 3.16.0-5.10
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  janne  1742 F lxpanel
  CRDA: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole: 'iw'
  Date: Wed Jul 23 13:32:29 2014
  DuplicateSignature: suspend/resume:Nokia Nokia Booklet 3G:2.00.T01
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=9606773e-45e2-40ab-9a71-740ccb9c916b
  InstallationDate: Installed on 2014-07-22 (2 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140705)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Nokia Nokia Booklet 3G
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-5-generic 
root=UUID=9ee73f4e-4d13-40d3-9f8a-db4b5b5a66b6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-5-generic N/A
   linux-backports-modules-3.16.0-5-generic  N/A
   linux-firmware1.132
  SourcePackage: linux
  Title: [Nokia Nokia Booklet 3G] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Nokia
  dmi.bios.version: 2.00.T01
  dmi.board.name: NYU00
  dmi.board.vendor: Nokia
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 8
  dmi.chassis.vendor: Nokia
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnNokia:bvr2.00.T01:bd03/05/2010:svnNokia:pnNokiaBooklet3G:pvr0040:rvnNokia:rnNYU00:rvrREFERENCE:cvnNokia:ct8:cvrN/A:
  dmi.product.name: Nokia Booklet 3G
  dmi.product.version: 0040
  dmi.sys.vendor: Nokia

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

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

[Kernel-packages] [Bug 362704] Re: nvidia-settings does not keep resolution that it is set too and xorg.conf is useless

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-settings does not keep resolution that it is set too and
  xorg.conf is useless

Status in “nvidia-settings” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nvidia-settings

  Hi there all.  I am on the fabulously new jaunty.  But I have a video
  problem.

  After a fresh install, I enabled the restricted nvidia drivers.  Then
  via nvidia-settings i set my resolution to 1280x1024.  This works well
  until I reboot, then ubuntu boots into some other low resolution that
  I do not know where it is getting this resolution from.

  I then tried to copy my old xorg.con from intrepid to jaunty but it
  bombs.

  I try to set the resolution via system -> preference -> display but no
  dice .. it forces me back to nvidia-settings.

  Exactly how is resolution setting handled in jaunty RC?

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: nvidia-settings 180.25-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/362704/+subscriptions

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

[Kernel-packages] [Bug 1228109] Re: [Lenovo ThinkCentre M91p] System freezes

2014-08-04 Thread Daniel Arnitz

Thank you stuart. I'm afraid your solution does not apply to me. My
freezes are instant, without any sluggish or strange mouse or keyboard
behavior, and the system locks completely, including low-level functions
such as Ethernet pings. I'm also not using an Nvidia card, nor any
proprietary driver, and my PCI express slot is empty.

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

Title:
  [Lenovo ThinkCentre M91p] System freezes

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  * Problem description: The system freezes completely. This includes
  screen, mouse, and keyboard including numlock light. Even after
  several weeks of testing I was not able to tie the freezes to a
  specific event, program, or behavior. There seem to be a few scenarios
  where freezes are more likely (see below), but they can essentially
  occur at any time. I have updated my bios and the system; this did not
  solve the problem. I have not yet tried the mainline kernel, since I
  am unsure which version to select.

  * Steps to reproduce: Run long-term measurement device remote control in 
Matlab (data collection; SCPI, low cpu load, some network, a couple GB RAM 
usage). The system typically freezes within 24 to 48 hours. I have also tried 
several other scenarios:
  - normal work with KDE (Kile, Thunderbird, Firefox, Inkscape, VLC, Dolphin): 
RARELY (~ once a month)
  - measurement device remote control in Matlab (memory, network).

  The following didn't seem to reproduce the problem:
  - running date + sleep in a bash loop.
  - running date + sleep in a bash loop within screen.
  - running ping constantly.
  - idle loop in Matlab (do nothing).
  - random data copying loop in Matlab (memory only).

  * Keeping CPU load high by inverting a some matrix in the data
  collection loop seems to prevent this problem.

  * Last working version: Kubuntu 11.10

  * Additional information:
  - memory test came back negative (no problems)
  - crash is reproducible on a text console
  - could not obtain trace dump (system does not react to keyboard)

  Neither of the following fixed the problem:
  xserver-xorg-lts-quantal libgl1-mesa-dri-lts-quantal:i386 
libgl1-mesa-glx-lts-quantal:i386

  or fixing the "*BAD*gran_size" issue described in:
  
http://my-fuzzy-logic.de/blog/index.php?/archives/41-Solving-linux-MTRR-problems.html

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-40-generic 3.5.0-40.62~precise1
  ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20
  Uname: Linux 3.5.0-40-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arnitz 2208 F pulseaudio
   /dev/snd/controlC0:  arnitz 2208 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 44'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0662,17aa3070,00100101 
HDA:80862805,17aa3070,0010'
     Controls  : 36
     Simple ctrls  : 16
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Plantronics Wireless Audio Plantronics Wireless Audio at 
usb-:00:1d.0-1.4, '
     Mixer name : 'USB Mixer'
     Components : 'USB047f:d955'
     Controls  : 4
     Simple ctrls  : 2
  Date: Fri Sep 20 08:13:34 2013
  HibernationDevice: RESUME=UUID=2f562564-0248-4280-a46b-9cd0f0e8e5e6
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: LENOVO 4524-AN4
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-40-generic 
root=UUID=af77f384-9007-4d2b-8395-5ada0dcfb93e ro quiet splash 
enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=64K mtrr_chunk_size=256M 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-40-generic N/A
   linux-backports-modules-3.5.0-40-generic  N/A
   linux-firmware1.79.6
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2013-06-20 (91 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT54AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524-AN4:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 4524-AN4
  dmi.product.version: ThinkCentre

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

This change was made by a bot.

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

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

Title:
  IRQ conflict disables wired network on cold (first) boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  On every cold boot the ethernet controller fails to load, leaving the wired 
network completely disabled.
  No interface /dev/eth0 is created.
  IRQ 49 is taken by snd_hda_intel.
   49:  29219  0  0  0   PCI-MSI-edge  
snd_hda_intel
  eth0 is not listed in /proc/interrupts
  The following log message is printed:
  e1000e: probe of :00:19.0 failed with error -3

  When rebooting the machine (without powering down), the ethernet controller 
loads normally and functions without problems.
  IRQ:s are now allocated differently:
   49: 155107  0  0  0   PCI-MSI-edge  eth0
   50:   1414 965740  0  0   PCI-MSI-edge  
snd_hda_intel

  The expected behaviour is that the ethernet controller will be
  assigned an IRQ on the first boot, and load normally.

  The network controller worked fine in Precise, until some upgrade in June.
  I did not diagnose the problem immeditaly, and don't know which upgrade 
caused the regression.
  Upgrading to Trusty (Ubuntu 14.04.1 LTS) did not solve the problem.

  The problem is not random: it occurs at every cold boot and
  the workaround of rebooting immediately after each cold boot works 
persistently.
  I tried, as a workaround, setting the following kernel parameters (one at a 
time): 
  pci=noacpi , pci=routeirq , noapic, acpi=off, pcie_pme=force and irqpoll
  None of the listed kernel parameters affected the problem.
  rmmod e1000e followed modprobe e1000e didn't help.

  
  The ethernet controller is a
  00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network 
Connection (rev 05)
  Kernel driver in use: e1000e

  The sound chip is a
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  Kernel driver in use: snd_hda_intel

  Both of the devices are on-board chips on the motherboard, so changing
  slots is not possible as a workaround.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gronsti5896 F pulseaudio
gronsti7728 F pulseaudio
  Date: Mon Aug  4 19:46:31 2014
  HibernationDevice: RESUME=UUID=a4491702-2d6a-4187-8756-1d7c48b9bbef
  InstallationDate: Installed on 2012-05-29 (797 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=UUID=a7af81dd-393a-4948-a371-6f54d5de589b ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
  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.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-30 (4 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-210
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-210:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1352461] Re: IRQ conflict disables wired network on cold (first) boot

2014-08-04 Thread Stig-Arne Grönroos

Attached additional information

** Attachment added: "/proc/interrupts after reboot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352461/+attachment/4169711/+files/interrupts_hot

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

Title:
  IRQ conflict disables wired network on cold (first) boot

Status in “linux” package in Ubuntu:
  New

Bug description:
  On every cold boot the ethernet controller fails to load, leaving the wired 
network completely disabled.
  No interface /dev/eth0 is created.
  IRQ 49 is taken by snd_hda_intel.
   49:  29219  0  0  0   PCI-MSI-edge  
snd_hda_intel
  eth0 is not listed in /proc/interrupts
  The following log message is printed:
  e1000e: probe of :00:19.0 failed with error -3

  When rebooting the machine (without powering down), the ethernet controller 
loads normally and functions without problems.
  IRQ:s are now allocated differently:
   49: 155107  0  0  0   PCI-MSI-edge  eth0
   50:   1414 965740  0  0   PCI-MSI-edge  
snd_hda_intel

  The expected behaviour is that the ethernet controller will be
  assigned an IRQ on the first boot, and load normally.

  The network controller worked fine in Precise, until some upgrade in June.
  I did not diagnose the problem immeditaly, and don't know which upgrade 
caused the regression.
  Upgrading to Trusty (Ubuntu 14.04.1 LTS) did not solve the problem.

  The problem is not random: it occurs at every cold boot and
  the workaround of rebooting immediately after each cold boot works 
persistently.
  I tried, as a workaround, setting the following kernel parameters (one at a 
time): 
  pci=noacpi , pci=routeirq , noapic, acpi=off, pcie_pme=force and irqpoll
  None of the listed kernel parameters affected the problem.
  rmmod e1000e followed modprobe e1000e didn't help.

  
  The ethernet controller is a
  00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network 
Connection (rev 05)
  Kernel driver in use: e1000e

  The sound chip is a
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  Kernel driver in use: snd_hda_intel

  Both of the devices are on-board chips on the motherboard, so changing
  slots is not possible as a workaround.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gronsti5896 F pulseaudio
gronsti7728 F pulseaudio
  Date: Mon Aug  4 19:46:31 2014
  HibernationDevice: RESUME=UUID=a4491702-2d6a-4187-8756-1d7c48b9bbef
  InstallationDate: Installed on 2012-05-29 (797 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=UUID=a7af81dd-393a-4948-a371-6f54d5de589b ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
  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.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-30 (4 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-210
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-210:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1352461] Re: IRQ conflict disables wired network on cold (first) boot

2014-08-04 Thread Stig-Arne Grönroos

Attached additional information


** Attachment added: "lshw -C network"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352461/+attachment/4169712/+files/lshw

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

Title:
  IRQ conflict disables wired network on cold (first) boot

Status in “linux” package in Ubuntu:
  New

Bug description:
  On every cold boot the ethernet controller fails to load, leaving the wired 
network completely disabled.
  No interface /dev/eth0 is created.
  IRQ 49 is taken by snd_hda_intel.
   49:  29219  0  0  0   PCI-MSI-edge  
snd_hda_intel
  eth0 is not listed in /proc/interrupts
  The following log message is printed:
  e1000e: probe of :00:19.0 failed with error -3

  When rebooting the machine (without powering down), the ethernet controller 
loads normally and functions without problems.
  IRQ:s are now allocated differently:
   49: 155107  0  0  0   PCI-MSI-edge  eth0
   50:   1414 965740  0  0   PCI-MSI-edge  
snd_hda_intel

  The expected behaviour is that the ethernet controller will be
  assigned an IRQ on the first boot, and load normally.

  The network controller worked fine in Precise, until some upgrade in June.
  I did not diagnose the problem immeditaly, and don't know which upgrade 
caused the regression.
  Upgrading to Trusty (Ubuntu 14.04.1 LTS) did not solve the problem.

  The problem is not random: it occurs at every cold boot and
  the workaround of rebooting immediately after each cold boot works 
persistently.
  I tried, as a workaround, setting the following kernel parameters (one at a 
time): 
  pci=noacpi , pci=routeirq , noapic, acpi=off, pcie_pme=force and irqpoll
  None of the listed kernel parameters affected the problem.
  rmmod e1000e followed modprobe e1000e didn't help.

  
  The ethernet controller is a
  00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network 
Connection (rev 05)
  Kernel driver in use: e1000e

  The sound chip is a
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  Kernel driver in use: snd_hda_intel

  Both of the devices are on-board chips on the motherboard, so changing
  slots is not possible as a workaround.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gronsti5896 F pulseaudio
gronsti7728 F pulseaudio
  Date: Mon Aug  4 19:46:31 2014
  HibernationDevice: RESUME=UUID=a4491702-2d6a-4187-8756-1d7c48b9bbef
  InstallationDate: Installed on 2012-05-29 (797 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=UUID=a7af81dd-393a-4948-a371-6f54d5de589b ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
  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.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-30 (4 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-210
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-210:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1352461] [NEW] IRQ conflict disables wired network on cold (first) boot

2014-08-04 Thread Stig-Arne Grönroos

Public bug reported:

On every cold boot the ethernet controller fails to load, leaving the wired 
network completely disabled.
No interface /dev/eth0 is created.
IRQ 49 is taken by snd_hda_intel.
 49:  29219  0  0  0   PCI-MSI-edge  
snd_hda_intel
eth0 is not listed in /proc/interrupts
The following log message is printed:
e1000e: probe of :00:19.0 failed with error -3

When rebooting the machine (without powering down), the ethernet controller 
loads normally and functions without problems.
IRQ:s are now allocated differently:
 49: 155107  0  0  0   PCI-MSI-edge  eth0
 50:   1414 965740  0  0   PCI-MSI-edge  
snd_hda_intel

The expected behaviour is that the ethernet controller will be assigned
an IRQ on the first boot, and load normally.

The network controller worked fine in Precise, until some upgrade in June.
I did not diagnose the problem immeditaly, and don't know which upgrade caused 
the regression.
Upgrading to Trusty (Ubuntu 14.04.1 LTS) did not solve the problem.

The problem is not random: it occurs at every cold boot and
the workaround of rebooting immediately after each cold boot works persistently.
I tried, as a workaround, setting the following kernel parameters (one at a 
time): 
pci=noacpi , pci=routeirq , noapic, acpi=off, pcie_pme=force and irqpoll
None of the listed kernel parameters affected the problem.
rmmod e1000e followed modprobe e1000e didn't help.


The ethernet controller is a
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network 
Connection (rev 05)
Kernel driver in use: e1000e

The sound chip is a
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Kernel driver in use: snd_hda_intel

Both of the devices are on-board chips on the motherboard, so changing
slots is not possible as a workaround.

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
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gronsti5896 F pulseaudio
  gronsti7728 F pulseaudio
Date: Mon Aug  4 19:46:31 2014
HibernationDevice: RESUME=UUID=a4491702-2d6a-4187-8756-1d7c48b9bbef
InstallationDate: Installed on 2012-05-29 (797 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=UUID=a7af81dd-393a-4948-a371-6f54d5de589b ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
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.5
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-07-30 (4 days ago)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10212-210
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-210:cvn:ct3:cvr:

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


** Tags: amd64 apport-bug trusty

** Attachment added: "/proc/interrupts after cold boot"
   
https://bugs.launchpad.net/bugs/1352461/+attachment/4169695/+files/interrupts_cold

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

Title:
  IRQ conflict disables wired network on cold (first) boot

Status in “linux” package in Ubuntu:
  New

Bug description:
  On every cold boot the ethernet controller fails to load, leaving the wired 
network completely disabled.
  No interface /dev/eth0 is created.
  IRQ 49 is taken by snd_hda_intel.
   49:  29219  0  0  0   PCI-MSI-edge  
snd_hda_intel
  eth0 is not listed in /proc/interrupts
  The following log message is printed:
  e1000e: probe of :00:19.0 failed with error -3

  When rebooting the machine (without powering down), the ethernet controller 
loads normally and functions without problems.
  IRQ:s are now allocated differently:
   49: 155107  0  0  0   PCI-MSI-edge  eth0
   50:   1414 965740  0  0   PCI-MSI-edge  
snd_hda_intel

  The expected behaviour is that the ethernet controller will be
  assigned an IRQ on the first boot, and load normally.

  The network controller worked fine in Pre

[Kernel-packages] [Bug 852190] Re: 7392:7811 Edimax EW-7811Un USB dongle won't connect to networks (rtl8192cu module)

2014-08-04 Thread ppjdee

i had hopes this would be fixed by 13.10. still an issue though on
14.04.

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

Title:
  7392:7811 Edimax EW-7811Un USB dongle won't connect to networks
  (rtl8192cu module)

Status in The Linux Kernel:
  Incomplete
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The networks around are visible, but when trying to connect, the NM
  repeatedly asks for the password. Connecting to an open network fails
  as well.

  lsusb
  Bus 001 Device 002: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n 
Wireless Adapter [Realtek RTL8188CUS]

  lsmod | grep 8192
  rtl8192cu 103210  0
  rtl8192c_common75767  1 rtl8192cu
  rtlwifi   110972  1 rtl8192cu
  mac80211  310872  3 rtl8192cu,rtl8192c_common,rtlwifi

  WORKAROUND: Use the drivers downloaded from Realtek's website.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-11-generic 3.0.0-11.18
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3937 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe978000 irq 43'
     Mixer name : 'Realtek ALC662 rev1'
     Components : 'HDA:10ec0662,1b352201,00100101'
     Controls  : 20
     Simple ctrls  : 12
  CasperVersion: 1.284
  Date: Fri Sep 16 20:53:04 2011
  LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915.1)
  MachineType: czc czc
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt 
cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed 
boot=casper initrd=/casper/initrd.lz quiet splash --
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-11-generic N/A
   linux-backports-modules-3.0.0-11-generic  N/A
   linux-firmware1.60
  RfKill:
   1: phy1: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: czc
  dmi.board.vendor: czc
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: czc
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd03/16/2010:svnczc:pnczc:pvr1.0:rvnczc:rnczc:rvr1.0:cvnczc:ct3:cvr1.0:
  dmi.product.name: czc
  dmi.product.version: 1.0
  dmi.sys.vendor: czc

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

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

[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader

2014-08-04 Thread cb

the issue still exist in 3.13.0-32-generic

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

Title:
  Support Realtek RTS5227 card reader

Status in HWE Next Project:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux” source package in Raring:
  Fix Released

Bug description:
  Support of Realtek RTS5227 card reader is currently missing in the
  kernel, though the support is already in upstream, we need to backport
  it from upstream to enable this device.

  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
  Device [10ec:5227] (rev 01)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1153618/+subscriptions

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

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

apport information

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1352379/+attachment/4169654/+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/1352379

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

[Kernel-packages] [Bug 1352379] WifiSyslog.txt

apport information

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

[Kernel-packages] [Bug 1352379] BootDmesg.txt

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1352379/+attachment/4169651/+files/BootDmesg.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/1352379

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

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

apport information

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1285 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
  InstallationDate: Installed on 2014-07-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0MN1TX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 7010
  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/1352379/+subscriptions

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

[Kernel-packages] [Bug 1352379] Re: Network broken after resume

apport information

** Tags added: apport-collected trusty

** Description changed:

  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine is
  resumed after a suspend. Because of the LDAP authentication, networking
  is required for authentication, thus we cannot login to the machine
  after a suspend. A "work-around" to restart network-manager is therefor
  not an option.
  
  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"
  
  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.
  
  * creating a file /etc/pm/sleep.d/network-resume with
  
   #!/bin/sh
  
  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac
  
  Outcome: Manually suspending works, resume only works when pressing the
  power button. Once resumed the networking is still disabled, and thus I
  cannot log in.
  
  
  * creating a file in /etc/pm/sleep.d with
  
  #!/bin/sh
  
  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac
  
- Outcome: Manually suspending works, resume only works when pressing the
- power button. Once resumed the networking is still disabled, and thus I
- cannot log in. After about a full minute networking is restored and I
- can log in.
+ Outcome: Manually suspending works, resume only works when pressing the power 
button. Once resumed the networking is still disabled, and thus I cannot log 
in. After about a full minute networking is restored and I can log in.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  lightdm1285 F pulseaudio
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f
+ InstallationDate: Installed on 2014-07-08 (27 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
+ IwConfig:
+  eth0  no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: Dell Inc. OptiPlex 7010
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ 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:
+  
+ Tags:  trusty
+ Uname: Linux 3.13.0-30-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 03/25/2013
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A13
+ dmi.board.name: 0MN1TX
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A01
+ dmi.chassis.type: 16
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr:
+ dmi.product.name: OptiPlex 7010
+ dmi.product.version: 01
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1352379/+attachment/4169650/+files/AlsaInfo.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/1352379

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false

[Kernel-packages] [Bug 1352358] Re: Kernel 3.13 freezes sometimes at startup

** Attachment added: "apport.linux-image-3.13.0-32-generic.3mS1YC.apport"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352358/+attachment/4169607/+files/apport.linux-image-3.13.0-32-generic.3mS1YC.apport

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

Title:
Kernel 3.13 freezes sometimes at startup

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at
startup. There is no kernelpanic. I can not use Systemrequest-Keys for
restart. The only key that gives Feedback is the Numlock-Key (LED
toggles). When i powercyle the Computer Grub has no countdown for
booting the first Kernel. When I press Enter the Kernel starts
normaly. I cannot find something in Syslog or somewhere else. I
deactivated the bootparameter quiet und added the Parameter
"console=tty0 console=ttyS0,115200n8". I connected the Computer via a
Nullmodemcable with another computer and logged the bootprocess with
minicom. The Logs are attached. I can not reproduce this Bug in Kernel
linux-image-3.11.0-13-generic

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

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

[Kernel-packages] [Bug 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels

2014-08-04 Thread Aditya

@Rafael,

I have uninstalled the mainline kernel v3.14.15 and booted into
v3.13.0-32, but still it only offers me to upgrade `linux-libc-dev` and
nothing else.

$ uname -a
Linux aditya-desktop 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:12 UTC 
2014 i686 athlon i686 GNU/Linux

$ dpkg -l | grep "linux\-[a-z]*\-" | awk '{print $2}'
linux-headers-3.13.0-32
linux-headers-3.13.0-32-generic
linux-headers-generic
linux-image-3.13.0-30-generic
linux-image-3.13.0-32-generic
linux-image-extra-3.13.0-30-generic
linux-image-extra-3.13.0-32-generic
linux-image-generic
linux-libc-dev:i386
linux-sound-base

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

Title:
  0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work
  with 3.11 or 3.13 kernels

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  Impact: Bluetooth device stopped working. Device support regression.
  Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6
  Testcase: Comment #10

  Original Description:

  Bluetooth device stopped working after upgrading ubuntu to 13.10.

  ~$ lsusb:
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)

  ~$ hciconfig
  hci0: Type: BR/EDR  Bus: USB
   BD Address: 00:1B:10:00:0F:46  ACL MTU: 1017:8  SCO MTU: 64:0
   DOWN
   RX bytes:457 acl:0 sco:0 events:16 errors:0
   TX bytes:68 acl:0 sco:0 commands:16 errors:0
  ~$ hcitool dev
  Devices:

  device simply doesnt appear on bluetooth manager. blueman UI is
  broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-4-generic 3.11.0-4.9
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jorge  1954 F pulseaudio
   /dev/snd/controlC0:  jorge  1954 F pulseaudio
  Date: Fri Sep  6 22:32:45 2013
  HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: MEGAWARE MW-H61M-2H
  MarkForUpload: True
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-4-generic N/A
   linux-backports-modules-3.11.0-4-generic  N/A
   linux-firmware1.113
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago)
  dmi.bios.date: 08/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5 MW
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MW-H61M-2H
  dmi.board.vendor: MEGAWARE
  dmi.board.version: v1.3 - 17/07/2012 - MWX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEGAWARE
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MW-H61M-2H
  dmi.product.version: v1.3 - 17/07/2012 - MWX
  dmi.sys.vendor: MEGAWARE

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

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

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

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

apport-collect 1352379

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

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in. After about a full minute networking is restored
  and I can log in.

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

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

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

2014-08-04 Thread bugproxy

--- Comment From cha...@us.ibm.com 2014-08-04 14:03 EDT---
*** Bug 114168 has been marked as a duplicate of this bug. ***

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

Title:
  Ubuntu14.10: CONFIG_SCSI_IPr_TRACE and CONFIG_SCSI_IPR_DUMP are not
  set in config file

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 Released

Bug description:
  Problem Description
  ---
  CONFIG_SCSI_IPR_TRACE and CONFIG_SCSI_IPR_DUMP are not set in config file in 
Ubuntu14.10

  ---uname output---
  ubuntu 14.10 
   
  Machine Type = P8 

  Steps to Reproduce
  
   In config file,

  # CONFIG_SCSI_IPR_TRACE is not set
  # CONFIG_SCSI_IPR_DUMP is not set

  They are not set. Ipr device driver couldn't generate dump and trace
  files for debugging.

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

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

[Kernel-packages] [Bug 1352379] Re: Network broken after resume

** Attachment added: "version.log"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352379/+attachment/4169576/+files/version.log

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

Title:
Network broken after resume

Status in “linux” package in Ubuntu:
New

Bug description:
We use Dell Optiplex 7010 machines in our student lab. These machines
are capable of suspending and resuming, so that we don't waste power
during the night. In our lab we also use LDAP authentication for the
students. The problem is that networking is disabled once the machine
is resumed after a suspend. Because of the LDAP authentication,
networking is required for authentication, thus we cannot login to the
machine after a suspend. A "work-around" to restart network-manager is
therefor not an option.

I have tried numerous things,
* creating a file /etc/pm/config.d/network-resume with the content
"SUSPEND_MODULE="e1000e"

Outcome: This seems to break the suspend functionality. When manually
entering "suspend" it goes directly to the lock screen. The networking
is still disabled, so I cannot log in.

* creating a file /etc/pm/sleep.d/network-resume with

#!/bin/sh

case ${1} in
resume|thaw)
nmcli nm sleep false
;;
esac

Outcome: Manually suspending works, resume only works when pressing
the power button. Once resumed the networking is still disabled, and
thus I cannot log in.

* creating a file in /etc/pm/sleep.d with

#!/bin/sh

case "${1}" in
resume|thaw)
restart network-manager
;;
esac

Outcome: Manually suspending works, resume only works when pressing
the power button. Once resumed the networking is still disabled, and
thus I cannot log in. After about a full minute networking is restored
and I can log in.

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

[Kernel-packages] [Bug 1352379] [NEW] Network broken after resume

Public bug reported:

We use Dell Optiplex 7010 machines in our student lab. These machines
are capable of suspending and resuming, so that we don't waste power
during the night. In our lab we also use LDAP authentication for the
students. The problem is that networking is disabled once the machine is
resumed after a suspend. Because of the LDAP authentication, networking
is required for authentication, thus we cannot login to the machine
after a suspend. A "work-around" to restart network-manager is therefor
not an option.

I have tried numerous things, 
* creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

Outcome: This seems to break the suspend functionality. When manually
entering "suspend" it goes directly to the lock screen. The networking
is still disabled, so I cannot log in.

* creating a file /etc/pm/sleep.d/network-resume with

 #!/bin/sh

case ${1} in
resume|thaw)
nmcli nm sleep false
;;
esac

Outcome: Manually suspending works, resume only works when pressing the
power button. Once resumed the networking is still disabled, and thus I
cannot log in.


* creating a file in /etc/pm/sleep.d with

#!/bin/sh

case "${1}" in
resume|thaw)
restart network-manager
;;
esac

Outcome: Manually suspending works, resume only works when pressing the
power button. Once resumed the networking is still disabled, and thus I
cannot log in. After about a full minute networking is restored and I
can log in.

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1352379/+attachment/4169575/+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/1352379

Title:
  Network broken after resume

Status in “linux” package in Ubuntu:
  New

Bug description:
  We use Dell Optiplex 7010 machines in our student lab. These machines
  are capable of suspending and resuming, so that we don't waste power
  during the night. In our lab we also use LDAP authentication for the
  students. The problem is that networking is disabled once the machine
  is resumed after a suspend. Because of the LDAP authentication,
  networking is required for authentication, thus we cannot login to the
  machine after a suspend. A "work-around" to restart network-manager is
  therefor not an option.

  I have tried numerous things, 
  * creating a file /etc/pm/config.d/network-resume with the content 
"SUSPEND_MODULE="e1000e"

  Outcome: This seems to break the suspend functionality. When manually
  entering "suspend" it goes directly to the lock screen. The networking
  is still disabled, so I cannot log in.

  * creating a file /etc/pm/sleep.d/network-resume with

   #!/bin/sh

  case ${1} in
resume|thaw)
nmcli nm sleep false
;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in.

  
  * creating a file in /etc/pm/sleep.d with

  #!/bin/sh

  case "${1}" in
  resume|thaw)
  restart network-manager
  ;;
  esac

  Outcome: Manually suspending works, resume only works when pressing
  the power button. Once resumed the networking is still disabled, and
  thus I cannot log in. After about a full minute networking is restored
  and I can log in.

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

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

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

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

apport-collect 1352358

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

Title:
  Kernel 3.13 freezes sometimes at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at
  startup. There is no kernelpanic. I can not use Systemrequest-Keys for
  restart. The only key that gives Feedback is the Numlock-Key (LED
  toggles). When i powercyle the Computer Grub has no countdown for
  booting the first Kernel. When I press Enter the Kernel starts
  normaly. I cannot find something in Syslog or somewhere else. I
  deactivated the bootparameter quiet und added the Parameter
  "console=tty0 console=ttyS0,115200n8". I connected the Computer via a
  Nullmodemcable with another computer and logged the bootprocess with
  minicom. The Logs are attached. I can not reproduce this Bug in Kernel
  linux-image-3.11.0-13-generic

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

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

[Kernel-packages] [Bug 1352358] Re: Kernel 3.13 freezes sometimes at startup

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352358/+attachment/4169531/+files/version.log

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

Title:
  Kernel 3.13 freezes sometimes at startup

Status in “linux” package in Ubuntu:
  New

Bug description:
  We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at
  startup. There is no kernelpanic. I can not use Systemrequest-Keys for
  restart. The only key that gives Feedback is the Numlock-Key (LED
  toggles). When i powercyle the Computer Grub has no countdown for
  booting the first Kernel. When I press Enter the Kernel starts
  normaly. I cannot find something in Syslog or somewhere else. I
  deactivated the bootparameter quiet und added the Parameter
  "console=tty0 console=ttyS0,115200n8". I connected the Computer via a
  Nullmodemcable with another computer and logged the bootprocess with
  minicom. The Logs are attached. I can not reproduce this Bug in Kernel
  linux-image-3.11.0-13-generic

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

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

[Kernel-packages] [Bug 1352358] Re: Kernel 3.13 freezes sometimes at startup

** Attachment added: "second-freeze.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352358/+attachment/4169528/+files/second-freeze.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/1352358

Title:
  Kernel 3.13 freezes sometimes at startup

Status in “linux” package in Ubuntu:
  New

Bug description:
  We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at
  startup. There is no kernelpanic. I can not use Systemrequest-Keys for
  restart. The only key that gives Feedback is the Numlock-Key (LED
  toggles). When i powercyle the Computer Grub has no countdown for
  booting the first Kernel. When I press Enter the Kernel starts
  normaly. I cannot find something in Syslog or somewhere else. I
  deactivated the bootparameter quiet und added the Parameter
  "console=tty0 console=ttyS0,115200n8". I connected the Computer via a
  Nullmodemcable with another computer and logged the bootprocess with
  minicom. The Logs are attached. I can not reproduce this Bug in Kernel
  linux-image-3.11.0-13-generic

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

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

[Kernel-packages] [Bug 1352358] Re: Kernel 3.13 freezes sometimes at startup

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352358/+attachment/4169529/+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/1352358

Title:
  Kernel 3.13 freezes sometimes at startup

Status in “linux” package in Ubuntu:
  New

Bug description:
  We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at
  startup. There is no kernelpanic. I can not use Systemrequest-Keys for
  restart. The only key that gives Feedback is the Numlock-Key (LED
  toggles). When i powercyle the Computer Grub has no countdown for
  booting the first Kernel. When I press Enter the Kernel starts
  normaly. I cannot find something in Syslog or somewhere else. I
  deactivated the bootparameter quiet und added the Parameter
  "console=tty0 console=ttyS0,115200n8". I connected the Computer via a
  Nullmodemcable with another computer and logged the bootprocess with
  minicom. The Logs are attached. I can not reproduce this Bug in Kernel
  linux-image-3.11.0-13-generic

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

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

[Kernel-packages] [Bug 1352358] Re: Kernel 3.13 freezes sometimes at startup

** Attachment added: "apt-cache_policy_linux-image-3.13.0-32-generic.log"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352358/+attachment/4169530/+files/apt-cache_policy_linux-image-3.13.0-32-generic.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/1352358

Title:
Kernel 3.13 freezes sometimes at startup

Status in “linux” package in Ubuntu:
New

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

[Kernel-packages] [Bug 1352358] [NEW] Kernel 3.13 freezes sometimes at startup

Public bug reported:

We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at
startup. There is no kernelpanic. I can not use Systemrequest-Keys for
restart. The only key that gives Feedback is the Numlock-Key (LED
toggles). When i powercyle the Computer Grub has no countdown for
booting the first Kernel. When I press Enter the Kernel starts normaly.
I cannot find something in Syslog or somewhere else. I deactivated the
bootparameter quiet und added the Parameter "console=tty0
console=ttyS0,115200n8". I connected the Computer via a Nullmodemcable
with another computer and logged the bootprocess with minicom. The Logs
are attached. I can not reproduce this Bug in Kernel linux-
image-3.11.0-13-generic

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


** Tags: i386 kernel-bug precise

** Attachment added: "first-freeze.log"
   
https://bugs.launchpad.net/bugs/1352358/+attachment/4169527/+files/first-freeze.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/1352358

Title:
  Kernel 3.13 freezes sometimes at startup

Status in “linux” package in Ubuntu:
  New

Bug description:
  We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at
  startup. There is no kernelpanic. I can not use Systemrequest-Keys for
  restart. The only key that gives Feedback is the Numlock-Key (LED
  toggles). When i powercyle the Computer Grub has no countdown for
  booting the first Kernel. When I press Enter the Kernel starts
  normaly. I cannot find something in Syslog or somewhere else. I
  deactivated the bootparameter quiet und added the Parameter
  "console=tty0 console=ttyS0,115200n8". I connected the Computer via a
  Nullmodemcable with another computer and logged the bootprocess with
  minicom. The Logs are attached. I can not reproduce this Bug in Kernel
  linux-image-3.11.0-13-generic

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

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

[Kernel-packages] [Bug 1349572] Re: Wireless network disconnections on Dell XPS 13

2014-08-04 Thread Seth Forshee

Marcel: That's fine. If you're getting connections with 3.16 we might
want to check later and see if those are the same or different than what
you're getting in 3.13, but for now you can continue testing the kernel
I built to see if it improves things for you at all.

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

Title:
  Wireless network disconnections on Dell XPS 13

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With kernel 3.13.0.30 and 22.1.7.0, there are lots of wireless disconnections.
  Tested also with kernel 3.13.0.32 and 22.24.8.0 , also lots of wireles 
disconnections. 

  The AP is an ASL-26555 from Movistar(Spain). Firmware version:
  v2.0.0.51B_ESv6

  Seems that when the computer is working for some time it is more easy
  to reproduce this beahviour.

  Added this bug as sugested in #1293569, comment #91.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-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:  marcel 2611 F pulseaudio
   /dev/snd/controlC0:  marcel 2611 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 28 22:20:19 2014
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 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.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (101 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  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.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (103 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Rel

[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

2014-08-04 Thread Stefan Bader

Thanks for the backport David. I build some test kernels with that and
put them to http://people.canonical.com/~smb/lp1350373/ (note that you
do *not* need linux-image-extra for ec2 installations). This should get
pulled in as stable patch but it would be even better if someone can
confirm the test kernels working. Thanks.

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

Title:
  Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” source package in Trusty:
  Triaged

Bug description:
  Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while
  expanding the grant table (usually when requested by blkfront, when
  booting).  See an example trace below.

  This is caused by calling functions that are unsafe in atomic context.

  The fix (which has been submitted to 3.16) is available here (also
  attached):

  https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable
  /for-linus-3.16&id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168

  The fix is applicable to all kernel since 2.6.39 but only appears to
  trigger with the 3.13 kernel in 14.04.

  [2.577876] [ cut here ]
  [2.577896] kernel BUG at 
/build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239!
  [2.577910] invalid opcode:  [#1] SMP 
  [2.577922] Modules linked in:
  [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [2.577946] task: ec058000 ti: ec09 task.ti: ec09
  [2.577955] EIP: 0061:[] EFLAGS: 00010002 CPU: 0
  [2.577973] EIP is at enter_lazy.part.1+0x3/0x5
  [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: 
  [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50
  [2.578001]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069
  [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660
  [2.578027] Stack:
  [2.578032]  ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff 
edc01000 c1a93018
  [2.578052]   edc00fff  c193ce80 edc01000  
 
  [2.578076]  ed3ef588 ed3ef588  c1b87b70 ec091ad0 edc01000 
c1b65310 1000
  [2.578096] Call Trace:
  [2.578111]  [] paravirt_enter_lazy_mmu+0x24/0x30
  [2.578127]  [] apply_to_page_range+0x1a3/0x310
  [2.578141]  [] arch_gnttab_map_status+0x38/0x60
  [2.578152]  [] ? map_pte_fn+0x70/0x70
  [2.578166]  [] gnttab_map_frames_v2+0xb0/0x100
  [2.578182]  [] gnttab_map+0x95/0x120
  [2.578198]  [] ? blk_update_request+0x190/0x340
  [2.578209]  [] get_free_entries+0xd3/0x280
  [2.578221]  [] gnttab_alloc_grant_references+0x13/0x30
  [2.578238]  [] do_blkif_request+0x535/0x6f0
  [2.578253]  [] ? _raw_spin_unlock_irqrestore+0x1c/0x40
  [2.578269]  [] __blk_run_queue+0x2e/0x40
  [2.578280]  [] blk_start_queue+0x25/0x40
  [2.578291]  [] kick_pending_request_queues+0x1e/0x30
  [2.578304]  [] blkif_interrupt+0x69f/0x740
  [2.578318]  [] ? xen_set_pte_at+0xbf/0xf0
  [2.578335]  [] handle_irq_event_percpu+0x35/0x1a0
  [2.578351]  [] ? radix_tree_lookup+0xa/0x10
  [2.578364]  [] handle_irq_event+0x31/0x50
  [2.578376]  [] handle_edge_irq+0x66/0x110
  [2.578389]  [] __xen_evtchn_do_upcall+0x1c6/0x2c0
  [2.578402]  [] xen_evtchn_do_upcall+0x20/0x40
  [2.578415]  [] xen_do_upcall+0x7/0xc
  [2.578427]  [] ? xen_hypercall_xen_version+0x7/0x20
  [2.578441]  [] ? xen_force_evtchn_callback+0xf/0x20
  [2.578454]  [] check_events+0x8/0xc
  [2.578464]  [] ? xen_restore_fl_direct_reloc+0x4/0x4
  [2.578480]  [] ? xen_batched_set_pte+0xb3/0x160
  [2.578493]  [] xen_set_pte_at+0x28/0xf0
  [2.578505]  [] ? __raw_callee_save_xen_pte_val+0x6/0x8
  [2.578521]  [] copy_pte_range+0x258/0x4c0
  [2.578534]  [] copy_page_range+0x1d7/0x2e0
  [2.578549]  [] dup_mm+0x28e/0x4f0
  [2.578561]  [] copy_process.part.33+0xfa6/0x10d0
  [2.578574]  [] do_fork+0xc1/0x2c0
  [2.578591]  [] ? SyS_rt_sigprocmask+0x76/0xa0
  [2.578604]  [] SyS_clone+0x25/0x30
  [2.578615]  [] sysenter_do_call+0x12/0x28
  [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba 
a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 <0f> 0b 
55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5
  [2.578745] EIP: [] enter_lazy.part.1+0x3/0x5 SS:ESP 
0069:ec091a50
  [2.578765] ---[ end trace ab5b5344be71ca3d ]---
  [2.578775] Kernel panic - not syncing: Fatal exception in interrupt

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

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

[Kernel-packages] [Bug 1326492] Re: BUG: Bad page map in process mozStorage #6 pte:24f2f965 pmd:124fc3067

2014-08-04 Thread tge

Now experimented more *with* XEN and found the the VT option was not
enabled in the BIOS. After doing this and rebooting (meanwhile also
updated kernel a few times and am now at 3.13.0-32-generic) no more
problems.

Looks as if the XEN-based kernel is not able to handle this under all
circumstances?

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

Title:
  BUG: Bad page map in process mozStorage #6  pte:24f2f965 pmd:124fc3067

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hello!
  I have a HP EliteBook 850 G1 which frequently crashes - will attach crash 
report.
  The system is brandnew, factory installed was Windows 7 (still in place as 
alternate boot option, rarely used), i.e. no earlier Linux on it yet. Most 
interesting detail is that this happens ONLY when running on batteries, if 
connected to power, no problems whatsoever), using batteries however 
reproducible within <= 30min (it just happens).
  Affected actual process (mozStorage in this example) varies, ultimately the 
OS hangs.
  Used memtest86 - nothing found.

  If there is any further info needed, pls let me know!
  Thx!!
tge

  PS: I used the GUI-based crash reporting function but have no clue where that 
data ended up and what to do next ... so possibly this already appears somewhere
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tge2939 F pulseaudio
tge9729 F pulseaudio
   /dev/snd/controlC1:  tge2939 F pulseaudio
tge9729 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=30d0fef1-3c3e-462e-953e-5f6557133900
  InstallationDate: Installed on 2014-05-20 (15 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 850 G1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic 
root=UUID=0f9bf6b7-e9be-42e9-a2aa-e66800536323 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/09/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.07
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.52
  dmi.chassis.asset.tag: CNU4109M6X
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.07:bd02/09/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.52:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1349462] Re: mw600 sony ericson doesnt work on ubuntu 14.04

2014-08-04 Thread Diego Carrera Gallego

** Description changed:

- 
  Ubuntu 14.04.1 LTS
  Release:  14.04
+ 64 bits
  
  2)bluez
  *** 4.101-0ubuntu13 0
  
  3) What you expected to happen
  I expect that audio output display mw600 in order to listen sound or music on 
my mw600 device.
  
  4) What happened instead
  Sound manager doesnt display mw600 as sound output device

** Description changed:

  Ubuntu 14.04.1 LTS
  Release:  14.04
  64 bits
  
  2)bluez
  *** 4.101-0ubuntu13 0
  
  3) What you expected to happen
- I expect that audio output display mw600 in order to listen sound or music on 
my mw600 device.
+ I expect that audio output display mw600 in order to select and listen sound 
or music on my mw600 device.
  
  4) What happened instead
  Sound manager doesnt display mw600 as sound output device

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

Title:
  mw600 sony ericson doesnt work on ubuntu 14.04

Status in “bluez” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.1 LTS
  Release:  14.04
  64 bits

  2)bluez
  *** 4.101-0ubuntu13 0

  3) What you expected to happen
  I expect that audio output display mw600 in order to select and listen sound 
or music on my mw600 device.

  4) What happened instead
  Sound manager doesnt display mw600 as sound output device

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

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

[Kernel-packages] [Bug 1352056] Re: kdump on Ubuntu 14.04 is not generating a dump.

2014-08-04 Thread Luciano Chavez

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

Title:
  kdump on Ubuntu 14.04 is not generating a dump.

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  kdump is not producing a dump on powerKVM LE P8 Ubuntu 14.04
   
  ---uname output---
  3.13.0-30-generic
   
  ---Additional Hardware Info---
  Power8 LE configuration. 
   
  ---Patches Installed---
  1324544 - kdump-config load fails with vmlinux kernel (vs. vmlinuz)
   
  Machine Type = 8247-22L 
   
  ---Steps to Reproduce---
  Installed kdump-tools 1.5.5-2ubuntu1 and crash 7.0.3-3ubuntu3.
  Updated /etc/default/kdump-tools, first I updated just USE_KDUMP=1. Rebooted 
the node and see:
  root=UUID=87986483-5fec-4b4d-b22e-bf2a72096df8 ro quiet splash 
crashkernel=384M-:128M
  root@c656f2n02:~# cat /proc/sys/kernel/sysrq
  1
  root@c656f2n02:~# cat /proc/sys/kernel/sysrq
  1
  root@c656f2n02:~# ^Cnd /proc | grep sysrq
  root@c656f2n02:~# kdump-config status
  current state   : ready to kdump
  root@c656f2n02:~# kdump-config show
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=87986483-5fec-4b4d-b22e-bf2a72096df8 ro quiet splash  
irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.13.0-30-generic 
/boot/vmlinux-3.13.0-30-generic

  root@c656f2n02:/boot/grub# cat /sys/kernel/kexec_crash_loaded
  1
  root@c656f2n02:/boot/grub# cat /sys/kernel/kexec_loaded
  0

  echo c > /proc/sysrq-trigger

  root@c656f2n02:/var/log# echo c > /proc/sysrq-trigger
  [ 1956.014243] SysRq : Trigger a crash
  [ 1956.014328] Unable to handle kernel paging request for data at address 
0x
  [ 1956.014404] Faulting instruction address: 0xc0586c2c
  [ 1956.014468] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1956.014518] SMP NR_CPUS=2048 NUMA PowerNV
  [ 1956.014570] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables autofs4 rdma_ucm(OF) 
ib_ucm(OF) rdma_cm(OF) iw_cm(OF) ib_ipoib(OF) ib_cm(OF) ib_uverbs(OF) 
ib_umad(OF) mlx5_ib(OF) mlx5_core(OF) mlx4_ib(OF) ib_sa(OF) ib_mad(OF) 
ib_core(OF) ib_addr(OF) mlx4_en(OF) mlx4_core(OF) compat(OF) nfsd auth_rpcgss 
nfs_acl nfs lockd sunrpc fscache rtc_generic powernv_rng ses enclosure ipr
  [ 1956.015306] CPU: 146 PID: 2522 Comm: bash Tainted: GF  O 
3.13.0-30-generic #54-Ubuntu
  [ 1956.015394] task: c03fcabda120 ti: c03fcac58000 task.ti: 
c03fcac58000
  [ 1956.015469] NIP: c0586c2c LR: c0587b8c CTR: 
c0586c00
  [ 1956.015543] REGS: c03fcac5b820 TRAP: 0300   Tainted: GF  O  
(3.13.0-30-generic)
  [ 1956.015617] MSR: 90009033   CR: 42422822  
XER: 2000
  [ 1956.015804] CFAR: c0009318 DAR:  DSISR: 4200 
SOFTE: 0
  GPR00: c0587b8c c03fcac5baa0 c162e840 0063
  GPR04: c2f45bd0 c2f564c8 00015ad0 c1827480
  GPR08: c0dfe840  0001 00015ad0
  GPR12: 42422822 c7e5ff00 01002fe90648 1016e008
  GPR16: 1013ad70 01002fe94648 1016fed0 1016e008
  GPR20: 100c31e0  10171fc8 1016f840
  GPR24: 0004  0001 c14b7dc8
  GPR28: c1974c90 0063 c148d9c0 c14b8188
  [ 1956.016794] NIP [c0586c2c] .sysrq_handle_crash+0x2c/0x40
  [ 1956.016858] LR [c0587b8c] .__handle_sysrq+0xfc/0x260
  [ 1956.016920] Call Trace:
  [ 1956.016948] [c03fcac5baa0] [10172a34] 0x10172a34 (unreliable)
  [ 1956.017025] [c03fcac5bb10] [c0587b8c] 
.__handle_sysrq+0xfc/0x260
  [ 1956.017101] [c03fcac5bbd0] [c0588324] 
.write_sysrq_trigger+0x74/0x90
  [ 1956.017190] [c03fcac5bc50] [c02dff1c] 
.proc_reg_write+0xac/0x110
  [ 1956.017266] [c03fcac5bcf0] [c0254c00] .vfs_write+0xe0/0x260
  [ 1956.017342] [c03fcac5bd90] [c02558f4] .SyS_write+0x64/0xe0
  [ 1956.017418] [c03fcac5be30] [c000a158] syscall_exit+0x0/0x98
  [ 1956.017492] Instruction dump:
  [ 1956.017530] 4bac 7c0802a6 f8010010 f821ff91 6000 6000 3d42001f 
392a8ca8
  [ 1956.017658] 3941 9149 7c0004ac 3920 <9949> 38210070 
e8010010 7c0803a6
  [ 1956.017894] ---[ end trace d163ff42366bde72 ]---
  [ 1956.017986]
  [ 1956.018042] Sending IPI to other CPUs
  [ 1956.019188] IPI complete
   -> smp_releas

[Kernel-packages] [Bug 1349572] Re: Wireless network disconnections on Dell XPS 13

2014-08-04 Thread Marcel Miguel

Seth, I couldn't test them very much.

Yesterday I updated the system to your 3.13.0.32, so far so good. But it
was only a 30 min test. Today I will test it more deeper.

As for 3.16 i was getting some disconenctions (but much better than with stock 
3.13.0.32), but also only a 30 min test.
Also I tested it at work (with fiber connection), and the cable modem (CBN Inc. 
CG6640E) got "hanged" every time I made a speedtest.net. Previous test with 
other kernels didn't hanged this cable modem.
I have not yet tested it with your new kernel, tomorrow I expect to bring my 
home computer to this location.

This night I expect to send you a report. 
I will only test with new 3.13.10.32.57 kernel, is it ok?

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

Title:
  Wireless network disconnections on Dell XPS 13

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With kernel 3.13.0.30 and 22.1.7.0, there are lots of wireless disconnections.
  Tested also with kernel 3.13.0.32 and 22.24.8.0 , also lots of wireles 
disconnections. 

  The AP is an ASL-26555 from Movistar(Spain). Firmware version:
  v2.0.0.51B_ESv6

  Seems that when the computer is working for some time it is more easy
  to reproduce this beahviour.

  Added this bug as sugested in #1293569, comment #91.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-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:  marcel 2611 F pulseaudio
   /dev/snd/controlC0:  marcel 2611 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 28 22:20:19 2014
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 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.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (101 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec
  InstallationDate: Installed on 2014-01-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  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.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (103 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcel 2644 F pulseaudio
   /dev/snd/controlC0:  marcel 2644 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec

[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

2014-08-04 Thread Fernando Sclavo

No luck. All server firmware upgraded to SUU 14.07 (newest), and Ubuntu
updated as well, but still not working. Some info:

dmesg:

[   35.012522] ixgbe :22:00.1: Multiqueue Enabled: Rx Queue count = 32, Tx 
Queue count = 32
[   35.012653] ixgbe :22:00.1: PCI Express bandwidth of 32GT/s available
[   35.012655] ixgbe :22:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
[   35.012990] ixgbe :22:00.1: MAC: 2, PHY: 15, SFP+: 6, PBA No: G18786-003
[   35.012992] ixgbe :22:00.1: 90:e2:ba:20:b8:05
[   35.014727] ixgbe :22:00.1: Intel(R) 10 Gigabit Network Connection
[   35.014908] ixgbe: probe of :23:00.0 failed with error -5
[   35.015031] ixgbe: probe of :23:00.1 failed with error -5

uname -a:
Linux suricata 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed
Status in “linux” source package in Trusty:
  Confirmed

Bug description:
  We have a server (Dell R715) with two Intel x520 NIC's. If we run
  Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel
  driver or with Intel compiled one), but if we upgrade release to
  12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel
  drivers fails with error:

  [  226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7
  [  226.395770] Copyright (c) 1999-2013 Intel Corporation.
  [  226.395980] ixgbe: probe of :22:00.0 failed with error -5
  [  226.396092] ixgbe: probe of :22:00.1 failed with error -5
  [  226.396203] ixgbe: probe of :23:00.0 failed with error -5
  [  226.396311] ixgbe: probe of :23:00.1 failed with error -5

  I contacted Intel developers and they responded:

  "Hey Fernando,
  We (ixgbe) only returns EIO (error 5) for a couple of reasons.
   1) When we fail to io map (ioremap)
   2) If the eeprom checksum is incorrect.
   3) If the MAC address from the checksum is invalid

  Reasons 2 and 3 are related to the NIC's eeprom so if they worked with 
another system they should still be fine now.  If you really wanted to verify 
you could try out the NIC's on a known good system again to see if the eeprom 
somehow got corrupted.
  That pretty much leaves us with ioremap returning an error.  I'm not at all 
sure why your Ubuntu release would not like the way we are calling ioremap, but 
it might give you a place to start looking in Ubuntu changes.
  Thanks,
  -Don"

  If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's
  works fine.

  Please let me know how can I help!

  Regards

  Fernando

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

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

[Kernel-packages] [Bug 1348832] Re: e1000e Detected Hardware Unit Hang

2014-08-04 Thread Christopher M. Penalver

Ryan Finnie, the next step is to fully reverse commit bisect the kernel
in order to identify the fix commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?

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

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

Title:
  e1000e Detected Hardware Unit Hang

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  e1000e device on a trusty router/server/etc, up for a few weeks,
  stopped responding and went into a "Detected Hardware Unit Hang" loop.
  At the time, the interface was under moderate load, about 60mbps
  inbound.

  [1871400.121801] e1000e :00:19.0 eth1: Detected Hardware Unit Hang:
  [1871400.121801]   TDH  <92>
  [1871400.121801]   TDT  
  [1871400.121801]   next_to_use  
  [1871400.121801]   next_to_clean<90>
  [1871400.121801] buffer_info[next_to_clean]:
  [1871400.121801]   time_stamp   <11be7959f>
  [1871400.121801]   next_to_watch<92>
  [1871400.121801]   jiffies  <11be79797>
  [1871400.121801]   next_to_watch.status <0>
  [1871400.121801] MAC Status <80083>
  [1871400.121801] PHY Status <796d>
  [1871400.121801] PHY 1000BASE-T Status  <7800>
  [1871400.121801] PHY Extended Status<3000>
  [1871400.121801] PCI Status <10>
  [1871402.120130] e1000e :00:19.0 eth1: Detected Hardware Unit Hang:
  [1871402.120130]   TDH  <92>
  [1871402.120130]   TDT  
  [1871402.120130]   next_to_use  
  [1871402.120130]   next_to_clean<90>
  [1871402.120130] buffer_info[next_to_clean]:
  [1871402.120130]   time_stamp   <11be7959f>
  [1871402.120130]   next_to_watch<92>
  [1871402.120130]   jiffies  <11be7998b>
  [1871402.120130]   next_to_watch.status <0>
  [1871402.120130] MAC Status <80083>
  [1871402.120130] PHY Status <796d>
  [1871402.120130] PHY 1000BASE-T Status  <7800>
  [1871402.120130] PHY Extended Status<3000>
  [1871402.120130] PCI Status <10>
  [1871404.118513] e1000e :00:19.0 eth1: Detected Hardware Unit Hang:
  [1871404.118513]   TDH  <92>
  [1871404.118513]   TDT  
  [1871404.118513]   next_to_use  
  [1871404.118513]   next_to_clean<90>
  [1871404.118513] buffer_info[next_to_clean]:
  [1871404.118513]   time_stamp   <11be7959f>
  [1871404.118513]   next_to_watch<92>
  [1871404.118513]   jiffies  <11be79b7f>
  [1871404.118513]   next_to_watch.status <0>
  [1871404.118513] MAC Status <80083>
  [1871404.118513] PHY Status <796d>
  [1871404.118513] PHY 1000BASE-T Status  <7800>
  [1871404.118513] PHY Extended Status<3000>
  [1871404.118513] PCI Status <10>
  [1871405.129366] [ cut here ]
  [1871405.129374] WARNING: CPU: 0 PID: 0 at 
/build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 
dev_watchdog+0x276/0x280()
  [1871405.129375] NETDEV WATCHDOG: eth1 (e1000e): transmit queue 0 timed out
  [1871405.129376] Modules linked in: ksplice_vijajns4_vmlinux_new(OF) 
ksplice_vijajns4(OF) ksplice_ax32i68r_vmlinux_new(OF) ksplice_ax32i68r(OF) 
ksplice_n4y5yx0j_vmlinux_new(OF) ksplice_n4y5yx0j(OF) nct6775(F) hwmon_vid(F) 
xt_nat vhost_net vhost macvtap macvlan ip6t_REJECT ipt_REJECT xt_LOG 
ipt_MASQUERADE xt_TCPMSS iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv6 
nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
xt_tcpudp ip6table_filter ip6_tables iptable_filter ip_tables x_tables sit 
tunnel4 ip_tunnel bridge stp llc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc 
fscache jfs dm_multipath scsi_dh x86_pkg_temp_thermal intel_powerclamp 
kvm_intel kvm ftdi_sio joydev usbserial parport_pc mei_me mei serio_raw ppdev 
acpi_pad mac_hid coretemp lp parport dm_crypt raid456 async_memcpy 
async_raid6_recov async_pq async_xor async_tx xor raid6_pq raid1 raid0 
multipath linear hid_generic raid10 usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 i915 lrw e1000e gf128mul glue_helper 
ablk_helper i2c_algo_bit cryptd psmouse ahci drm_kms_helper ptp libahci 
pps_core video drm [last unloaded: ksplice_vijajns4_vmlinux_old]
  [1871405.129434] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GF  O 
3.13.0-30-generic #54-Ubuntu
  [1871405.129435] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Pro3, BIOS P1.40 05/23/2014
  [1871405.129436]  0009 88081fa03d98 8171a324 
88081fa03de0
  [1871405.129440]  88081fa03dd0 810676bd  
8807eeb94000
  [1871405.129441]  8807ee867c80 0001  
88081fa03e30
  [1871405.129444] Ca

[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

2014-08-04 Thread Ben Howard

Raising the severity due to the impact on EC2.

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

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

Title:
  Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest

Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” source package in Trusty:
  Triaged

Bug description:
  Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while
  expanding the grant table (usually when requested by blkfront, when
  booting).  See an example trace below.

  This is caused by calling functions that are unsafe in atomic context.

  The fix (which has been submitted to 3.16) is available here (also
  attached):

  https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable
  /for-linus-3.16&id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168

  The fix is applicable to all kernel since 2.6.39 but only appears to
  trigger with the 3.13 kernel in 14.04.

  [2.577876] [ cut here ]
  [2.577896] kernel BUG at 
/build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239!
  [2.577910] invalid opcode:  [#1] SMP 
  [2.577922] Modules linked in:
  [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [2.577946] task: ec058000 ti: ec09 task.ti: ec09
  [2.577955] EIP: 0061:[] EFLAGS: 00010002 CPU: 0
  [2.577973] EIP is at enter_lazy.part.1+0x3/0x5
  [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: 
  [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50
  [2.578001]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069
  [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660
  [2.578027] Stack:
  [2.578032]  ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff 
edc01000 c1a93018
  [2.578052]   edc00fff  c193ce80 edc01000  
 
  [2.578076]  ed3ef588 ed3ef588  c1b87b70 ec091ad0 edc01000 
c1b65310 1000
  [2.578096] Call Trace:
  [2.578111]  [] paravirt_enter_lazy_mmu+0x24/0x30
  [2.578127]  [] apply_to_page_range+0x1a3/0x310
  [2.578141]  [] arch_gnttab_map_status+0x38/0x60
  [2.578152]  [] ? map_pte_fn+0x70/0x70
  [2.578166]  [] gnttab_map_frames_v2+0xb0/0x100
  [2.578182]  [] gnttab_map+0x95/0x120
  [2.578198]  [] ? blk_update_request+0x190/0x340
  [2.578209]  [] get_free_entries+0xd3/0x280
  [2.578221]  [] gnttab_alloc_grant_references+0x13/0x30
  [2.578238]  [] do_blkif_request+0x535/0x6f0
  [2.578253]  [] ? _raw_spin_unlock_irqrestore+0x1c/0x40
  [2.578269]  [] __blk_run_queue+0x2e/0x40
  [2.578280]  [] blk_start_queue+0x25/0x40
  [2.578291]  [] kick_pending_request_queues+0x1e/0x30
  [2.578304]  [] blkif_interrupt+0x69f/0x740
  [2.578318]  [] ? xen_set_pte_at+0xbf/0xf0
  [2.578335]  [] handle_irq_event_percpu+0x35/0x1a0
  [2.578351]  [] ? radix_tree_lookup+0xa/0x10
  [2.578364]  [] handle_irq_event+0x31/0x50
  [2.578376]  [] handle_edge_irq+0x66/0x110
  [2.578389]  [] __xen_evtchn_do_upcall+0x1c6/0x2c0
  [2.578402]  [] xen_evtchn_do_upcall+0x20/0x40
  [2.578415]  [] xen_do_upcall+0x7/0xc
  [2.578427]  [] ? xen_hypercall_xen_version+0x7/0x20
  [2.578441]  [] ? xen_force_evtchn_callback+0xf/0x20
  [2.578454]  [] check_events+0x8/0xc
  [2.578464]  [] ? xen_restore_fl_direct_reloc+0x4/0x4
  [2.578480]  [] ? xen_batched_set_pte+0xb3/0x160
  [2.578493]  [] xen_set_pte_at+0x28/0xf0
  [2.578505]  [] ? __raw_callee_save_xen_pte_val+0x6/0x8
  [2.578521]  [] copy_pte_range+0x258/0x4c0
  [2.578534]  [] copy_page_range+0x1d7/0x2e0
  [2.578549]  [] dup_mm+0x28e/0x4f0
  [2.578561]  [] copy_process.part.33+0xfa6/0x10d0
  [2.578574]  [] do_fork+0xc1/0x2c0
  [2.578591]  [] ? SyS_rt_sigprocmask+0x76/0xa0
  [2.578604]  [] SyS_clone+0x25/0x30
  [2.578615]  [] sysenter_do_call+0x12/0x28
  [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba 
a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 <0f> 0b 
55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5
  [2.578745] EIP: [] enter_lazy.part.1+0x3/0x5 SS:ESP 
0069:ec091a50
  [2.578765] ---[ end trace ab5b5344be71ca3d ]---
  [2.578775] Kernel panic - not syncing: Fatal exception in interrupt

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

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

[Kernel-packages] [Bug 1342645] Re: upgrade bcmwl-kernel-source to 6.30.223.248

This bug was fixed in the package bcmwl - 6.30.223.248+bdcom-0ubuntu1

---
bcmwl (6.30.223.248+bdcom-0ubuntu1) utopic; urgency=medium

  * New upstream release: (LP: #1342645)
- This is an official public release from Broadcom.
  * debian/dkms.conf.in:
- Drop patches for kernels 3.10 (now upstream)
 -- Robert AncellFri, 01 Aug 2014 11:09:43 
+1200

** Changed in: bcmwl (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  upgrade bcmwl-kernel-source to 6.30.223.248

Status in “bcmwl” package in Ubuntu:
  Fix Released

Bug description:
  The latest version from broadcom is 6.30.223.248
  http://www.broadcom.com/support/802.11/linux_sta.php

  Release notes:
  WHAT'S NEW IN RELEASE 6.30.223.23X
  -
  + Upgraded to Support 3.11 kernels
  + Added cfg80211 wowlan support for Magic Packets and Disconnect

  WHAT'S NEW IN RELEASE 6.30.223.126
  --
  + Upgraded to Support 3.8.x
  + Added 43142 support
  + Added 4352 support
  + Dropped WEXT support

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

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

[Kernel-packages] [Bug 1342645] Re: upgrade bcmwl-kernel-source to 6.30.223.248

** Branch linked: lp:ubuntu/utopic-proposed/bcmwl

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

Title:
  upgrade bcmwl-kernel-source to 6.30.223.248

Status in “bcmwl” package in Ubuntu:
  In Progress

Bug description:
  The latest version from broadcom is 6.30.223.248
  http://www.broadcom.com/support/802.11/linux_sta.php

  Release notes:
  WHAT'S NEW IN RELEASE 6.30.223.23X
  -
  + Upgraded to Support 3.11 kernels
  + Added cfg80211 wowlan support for Magic Packets and Disconnect

  WHAT'S NEW IN RELEASE 6.30.223.126
  --
  + Upgraded to Support 3.8.x
  + Added 43142 support
  + Added 4352 support
  + Dropped WEXT support

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

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

[Kernel-packages] [Bug 1342645] Re: upgrade bcmwl-kernel-source to 6.30.223.248

2014-08-04 Thread Alberto Milone

Uploaded. Thanks for your work, Robert!

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

Title:
  upgrade bcmwl-kernel-source to 6.30.223.248

Status in “bcmwl” package in Ubuntu:
  In Progress

Bug description:
  The latest version from broadcom is 6.30.223.248
  http://www.broadcom.com/support/802.11/linux_sta.php

  Release notes:
  WHAT'S NEW IN RELEASE 6.30.223.23X
  -
  + Upgraded to Support 3.11 kernels
  + Added cfg80211 wowlan support for Magic Packets and Disconnect

  WHAT'S NEW IN RELEASE 6.30.223.126
  --
  + Upgraded to Support 3.8.x
  + Added 43142 support
  + Added 4352 support
  + Dropped WEXT support

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

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

[Kernel-packages] [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event

2014-08-04 Thread Martin Pitt

Thanks. Reassigning to kernel then.

** Summary changed:

- [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
+ Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event

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

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

Title:
  Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev
  event

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Hello Community,

  It seems brightness keys don't work with latest Ubuntu 14.04 LTS for
  laptop Asus Zenbook UX32LN.

  sudo dmidecode -s bios-version
  UX32LN.203

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

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

[Kernel-packages] [Bug 1348890] [NEW] Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event