date:20140122

Yes - 10 CPU bound tasks fighting over the CPU would perform worse with
PREEMPT. But for a desktop tha's not an issue be cause you usually
perceive "perfomance" of the system as the systems responsivene instead
of its raw computing power.

I have no raw data. I'm just experiencing that running a lot of CPU
bound task while doing other thing feel slugish on trusty compared to
fx. to lowlatency-kernel which problably have CONFIG_PREEMPT set.

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

Title:
  CONFIG_PREEMPT is not set. Why?

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix

Bug description:
  Since the generic kernel is for generic desktop use CONFIG_PREEMPT
  should be set. CONFIG_NO_HZ is already there so it seems strange to me
  that preempt is not especially because recommendations for desktop
  system usually includes building a preemptible kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-tools-3.13.0-5-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2201 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 22 23:12:08 2014
  InstallationDate: Installed on 2013-12-24 (29 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1271742] Re: CONFIG_PREEMPT is not set. Why?

Yes - 10 CPU bound tasks fighting over the CPU would perform worse with
PREEMPT. But for a desktop tha's not an issue be cause you usually
perceive "perfomance" of the system as the systems responsivene instead
of its raw computing power.

I have no raw data. I'm just experiencing  that running a lot of CPU
bound task while doing other thing feel slugish on trusty compared to

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

Title:
  CONFIG_PREEMPT is not set. Why?

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix

Bug description:
  Since the generic kernel is for generic desktop use CONFIG_PREEMPT
  should be set. CONFIG_NO_HZ is already there so it seems strange to me
  that preempt is not especially because recommendations for desktop
  system usually includes building a preemptible kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-tools-3.13.0-5-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2201 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 22 23:12:08 2014
  InstallationDate: Installed on 2013-12-24 (29 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1271742] Re: CONFIG_PREEMPT is not set. Why?

This link shows that the in-kenrel documentation says that for a low-
latency desktop preemption is recommented.

http://www.linuxtopia.org/online_books/linux_kernel/kernel_configuration/ch09s03.html



Preemption
Systems running as servers have very different workload requirements from those 
being used as a desktop for video and audio applications. The kernel allows 
different modes of "preemption" in order to handle these different workloads. 
Preemption is the ability of the kernel to interrupt itself while it is doing 
something else, in order to work on something with a higher priority, such as 
updating a sound or video program.

To change to a different preemption model, use this menu:

Processor type and features
Preemption Model
(X) No Forced Preemption (Server)
( ) Voluntary Kernel Preemption (Desktop)
( ) Preemptible Kernel (Low-Latency Desktop)
If you wish to make the kernel even more responsive to higher priority tasks 
than the general preemption option provides, you can also allow interruptions 
to one of the main internal kernel locks:

Processor type and features
[*] Preempt The Big Kernel Lock
This option is able to be selected only if you have already selected either the 
Preemptible Kernel or Symmetric multi-processing support options.



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

Title:
  CONFIG_PREEMPT is not set. Why?

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix

Bug description:
  Since the generic kernel is for generic desktop use CONFIG_PREEMPT
  should be set. CONFIG_NO_HZ is already there so it seems strange to me
  that preempt is not especially because recommendations for desktop
  system usually includes building a preemptible kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-tools-3.13.0-5-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2201 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 22 23:12:08 2014
  InstallationDate: Installed on 2013-12-24 (29 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1271444] Re: CVE-2014-1445

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

** Changed in: linux-armadaxp (Ubuntu Quantal)
   Status: New => Fix Released

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

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

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

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

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Saucy)
   Status: New => Fix Committed

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

** Changed in: linux-ti-omap4 (Ubuntu Quantal)
   Status: New => Fix Committed

** Changed in: linux-ti-omap4 (Ubuntu Raring)
   Status: New => Fix Committed

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

** Description changed:

- wanxl: fix info leak in ioctl
+ The wanxl_ioctl function in drivers/net/wan/wanxl.c in the Linux kernel
+ before 3.11.7 does not properly initialize a certain data structure,
+ which allows local users to obtain sensitive information from kernel
+ memory via an ioctl call.
  
  Break-Fix: - 2b13d06c9584b4eb773f1e80bbaedab9a1c344e1

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

Title:
  CVE-2014-1445

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  Fix Committed
Status in “linux-lts-raring” source package in Precise:
  Fix Committed
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  Fix Committed
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Committed
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy

[Kernel-packages] [Bug 889953] Re: bandwidth allocation problems with external USB audio device

2014-01-22 Thread Benjamin McGough

Just found the same issue with Saucy and upstream kernel
3.12.0-0312000-generic. Also seen on default saucy kernel (3.11.0-15).

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

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

Title:
  bandwidth allocation problems with external USB audio device

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” package in Fedora:
  Unknown

Bug description:
  usb-audio with a Zoom H4N does not work.

  The Zoom H4N contains a USB hub and a usb-audio device. When connecting, it 
produces the following error in dmesg:
  cannot submit datapipe for urb 0, error -28: not enough bandwidth
  When attempting to use Jack in full-duplex, jackd attempts a 0x4142 ioctl 
(SNDRV_PCM_IOCTL_START), gets an EPIPE, and crashes; the kernel produces 
another 'cannot submit datapipe for urb 0, error -28: not enough bandwidth' 
message in dmesg.

  From reading various forums and lists, the problem seems related to a
  bug in bandwidth allocation in EHCI_HCD with respect to isochronous
  endpoints (audio devices), which happens particularly badly when these
  devices are behind hubs.

  Workaround: disable the EHCI controller to which the audio device is 
connected, e.g.
  echo -n ':00:1d.7' > /sys/bus/pci/drivers/ehci_hcd/unbind
  where :00:1d.7 is to be replaced by the correct PCI address. This will 
reconnect the device under USB 1.1.

  This problem has been going on for years in the Linux kernel and
  should definitely be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  2167 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 46'
 Mixer name : 'Intel Cantiga HDMI'
 Components : 'HDA:111d76b2,10280277,00100302 
HDA:80862802,80860101,0010'
 Controls  : 19
 Simple ctrls  : 11
  Date: Sun Nov 13 21:09:45 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ef890c0a-abf2-48af-b767-6c84d2fdf528
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: Dell Inc. Latitude E4200
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=238c0805-e3d7-41bb-bcc2-ee866f5734f3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (29 days ago)
  dmi.bios.date: 05/06/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 02GMRH
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/06/2010:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn02GMRH:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E4200
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 876099] Re: Multiple users hijack each others' windows in 11.10

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

Title:
  Multiple users hijack each others' windows in 11.10

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Under 11.04 using Gnome 2, I could have a Gnome session as one user,
  open Firefox, do business related browsing.  I could also open a
  terminal, xhost +, su to a different user, and open a different
  Firefox process for hobby related browsing, different set of
  bookmarks, different home directory and all that.  It was convenient.

  Now that I've upgraded to 11.10, the behavior is different and
  confusing.  User A opens a Firefox window, no problem.  Open a
  terminal, su to user B.  User B starts up a Firefox process from the
  command line.  Output of ps clearly shows two independent processes
  (i.e. one is not the parent of the other).  A new Firefox window
  appears, but gets User A's bookmarks and other configuration, as if
  user B were simply opening a new window in user A's original process.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  don6172 F pulseaudio
   /dev/snd/controlC0:  don6172 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfcff8000 irq 45'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,104382fe,00100101'
 Controls  : 41
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfe8fc000 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Sun Oct 16 19:04:32 2011
  HibernationDevice: RESUME=UUID=cdeebca2-1ee3-4df8-973e-68f2093c28c3
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer P5Q
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=15101579-e4b2-4044-8361-a1e72f822a70 ro 
all_generic_ide nopat
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (1 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 05/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0506
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0506:bd05/26/2008:svnSystemmanufacturer:pnP5Q:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q
  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/876099/+subscriptions

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

[Kernel-packages] [Bug 588046] Re: "task blocked for more than 120 seconds" freezes system in Lucid: xfs

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

Title:
  "task blocked for more than 120 seconds" freezes system in Lucid: xfs

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I get "INFO: task xfsdatad/0:3344 blocked for more than 120 seconds." with  
subsequent freeze when doing disk I/O on a single or two xfs partitions. 
  This is yet another variant of bug #494476, where emphasis is on ext4 and 
possible other processes causing the bug to appear. Reading this and bug 
#276476, my impression is that it is triggered by disk I/O, no matter the 
filesystem.

  In on instance, I tried to unrar a large file. After processing 80% of the 
archive, the process got stuck, the filesystem became unusable ("ls" on other 
console freezing as well), only reboot helped. Of course, the simple 'shutdown' 
commend doesn't finish, so that's actually a hard reset.
  The second instance was during a copy of several Gig from one xfs partition 
to another. Same symptoms.

  Given that only a reset resolves the situation, this might eventually
  lead to damaged file systems and data loss.

  This system has been upgraded to 10.04 via 9.10 from 9.04. The problem
  _did not_ occur under 9.04.

  ---
  ay 31 09:55:22 tirion kernel: [ 2160.252098] INFO: task xfsdatad/0:3344 
blocked for more than 120 seconds.
  May 31 09:55:22 tirion kernel: [ 2160.252108] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  May 31 09:55:22 tirion kernel: [ 2160.252117] xfsdatad/0D 0001674e 0  
3344  2 0x
  May 31 09:55:22 tirion kernel: [ 2160.252132]  f5205ec4 0046 f5d72000 
0001674e  c0846740 f605b5ec c0846740
  May 31 09:55:22 tirion kernel: [ 2160.252153]  6b8e4857 01d5 c0846740 
c0846740 f605b5ec c0846740 c0846740 f6668a80
  May 31 09:55:22 tirion kernel: [ 2160.252173]   01d5 f605b340 
f5205ef8 f605b340 f5b890e4 f5205ef0 c058b315
  May 31 09:55:22 tirion kernel: [ 2160.252192] Call Trace:
  May 31 09:55:22 tirion kernel: [ 2160.252215]  [] 
rwsem_down_failed_common+0x75/0x1a0
  May 31 09:55:22 tirion kernel: [ 2160.252228]  [] 
rwsem_down_write_failed+0x1d/0x30
  May 31 09:55:22 tirion kernel: [ 2160.252241]  [] 
call_rwsem_down_write_failed+0x6/0x10
  May 31 09:55:22 tirion kernel: [ 2160.252252]  [] ? 
down_write+0x24/0x30
  May 31 09:55:22 tirion kernel: [ 2160.252315]  [] 
xfs_ilock+0x70/0x90 [xfs]
  May 31 09:55:22 tirion kernel: [ 2160.252366]  [] 
xfs_setfilesize+0x30/0x70 [xfs]
  May 31 09:55:22 tirion kernel: [ 2160.252415]  [] 
xfs_end_bio_delalloc+0x13/0x20 [xfs]
  May 31 09:55:22 tirion kernel: [ 2160.252466]  [] 
run_workqueue+0x8e/0x150
  May 31 09:55:22 tirion kernel: [ 2160.252516]  [] ? 
xfs_end_bio_delalloc+0x0/0x20 [xfs]
  May 31 09:55:22 tirion kernel: [ 2160.252529]  [] 
worker_thread+0x84/0xe0
  May 31 09:55:22 tirion kernel: [ 2160.252542]  [] ? 
autoremove_wake_function+0x0/0x50
  May 31 09:55:22 tirion kernel: [ 2160.252554]  [] ? 
worker_thread+0x0/0xe0
  May 31 09:55:22 tirion kernel: [ 2160.252565]  [] kthread+0x74/0x80
  May 31 09:55:22 tirion kernel: [ 2160.252575]  [] ? kthread+0x0/0x80
  May 31 09:55:22 tirion kernel: [ 2160.252587]  [] 
kernel_thread_helper+0x7/0x10
  May 31 09:55:22 tirion kernel: [ 2160.252602] INFO: task loop1:4127 blocked 
for more than 120 seconds.
  May 31 09:55:22 tirion kernel: [ 2160.252609] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  May 31 09:55:22 tirion kernel: [ 2160.252617] loop1 D 004206d7 0  
4127  2 0x
  May 31 09:55:22 tirion kernel: [ 2160.252630]  d296bde8 0046 f5fa 
004206d7  c0846740 f605cf8c c0846740
  May 31 09:55:22 tirion kernel: [ 2160.252649]  94b6508d 01d5 c0846740 
c0846740 f605cf8c c0846740 c0846740 f6668a80
  May 31 09:55:22 tirion kernel: [ 2160.252669]   01d5 f605cce0 
c1c08740 f605cce0 d296be30 d296bdf8 c058998a
  May 31 09:55:22 tirion kernel: [ 2160.252688] Call Trace:
  May 31 09:55:22 tirion kernel: [ 2160.252699]  [] 
io_schedule+0x3a/0x60
  May 31 09:55:22 tirion kernel: [ 2160.252711]  [] 
sync_page+0x3d/0x50
  May 31 09:55:22 tirion kernel: [ 2160.252721]  [] 
__wait_on_bit+0x4d/0x70
  May 31 09:55:22 tirion kernel: [ 2160.252731]  [] ? 
sync_page+0x0/0x50
  May 31 09:55:22 tirion kernel: [ 2160.252742]  [] 
wait_on_page_bit+0x91/0xa0
  May 31 09:55:22 tirion kernel: [ 2160.252754]  [] ? 
wake_bit_function+0x0/0x50
  May 31 09:55:22 tirion kernel: [ 2160.252766]  [] 
wait_on_page_writeback_range+0xa1/0x110
  May 31 09:55:22 tirion kernel: [ 2160.252780]  [] 
filemap_write_and_wait_range+0x78/0x80
  May 31 09:55:22 tirion kernel: [ 2160.252795]  [] 
vfs_fsync_

[Kernel-packages] [Bug 1241582] Re: [Asus M4A88TD-V EVO/USB3] System freezes after suspend to RAM

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

Title:
  [Asus  M4A88TD-V EVO/USB3] System freezes after suspend to RAM

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Since saucy, system freezes after suspend to RAM. It really freezes. Not just 
X. No terminal switch with Ctrl+Alt+F1 possible or SSH login to machine 
possible. System was upgraded from Raring to Saucy after release, not in beta 
or other test phases.
  ---
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephan2481 F pulseaudio
   /dev/snd/controlC2:  stephan2481 F pulseaudio
   /dev/snd/controlC0:  stephan2481 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=2c3c9dcb-0fd6-4860-98d0-53c4dba319d8
  InstallationDate: Installed on 2011-10-18 (731 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=427dcfbf-6f4e-49e5-abe1-1b50a9d37e88 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create 
secure directory (/run/user/1000/pulse): Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  RfKill:

  Tags:  saucy
  Uname: Linux 3.11.0-12-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-V EVO/USB3
  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.:bvr2301:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3: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/1241582/+subscriptions

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

[Kernel-packages] [Bug 1226172] Re: iostat: Cannot open /proc/stat: Cannot allocate memory

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

Title:
  iostat: Cannot open /proc/stat: Cannot allocate memory

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I receive an intermittent error using iostat -k 5 : "Cannot open
  /proc/stat: Cannot allocate memory"

  This can also be simply reproduced by entering: "cat /proc/stat", one
  to several (~5-10) times.

  strace on the "cat /proc/stat" method:
  ...exclude typical run-up...

  fstat(3, {st_mode=S_IFREG|0644, st_size=1607664, ...}) = 0
  mmap(NULL, 1607664, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd755b77000
  close(3)= 0
  fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
  open("/proc/stat", O_RDONLY)= -1 ENOMEM (Cannot allocate memory)
  write(2, "cat: ", 5cat: )= 5
  write(2, "/proc/stat", 10/proc/stat)  = 10
  open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fd755d09000
  read(3, "# Locale name alias data base.\n#"..., 4096) = 2570
  read(3, "", 4096)   = 0
  close(3)= 0
  munmap(0x7fd755d09000, 4096)= 0
  open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 
ENOENT (No such file or directory)
  open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 
ENOENT (No such file or directory)

  ...exclude typical throw-error via LC_MESSAGES/libc.mo...

  
  /proc/meminfo detail:
  # cat /proc/meminfo 
  MemTotal:   32947584 kB
  MemFree:  302664 kB
  Buffers:  154064 kB
  Cached: 21284268 kB
  SwapCached:  1728840 kB
  Active: 12576792 kB
  Inactive:   17279896 kB
  Active(anon):5097984 kB
  Inactive(anon):  3320844 kB
  Active(file):7478808 kB
  Inactive(file): 13959052 kB
  Unevictable:   0 kB
  Mlocked:   0 kB
  SwapTotal:  187617276 kB
  SwapFree:   185330320 kB
  Dirty:   148 kB
  Writeback: 0 kB
  AnonPages:   7048592 kB
  Mapped:   104312 kB
  Shmem:   604 kB
  Slab:1947068 kB
  SReclaimable:1523288 kB
  SUnreclaim:   423780 kB
  KernelStack:8800 kB
  PageTables:38260 kB
  NFS_Unstable:  0 kB
  Bounce:0 kB
  WritebackTmp:  0 kB
  CommitLimit:204091068 kB
  Committed_AS:   15333712 kB
  VmallocTotal:   34359738367 kB
  VmallocUsed:  163292 kB
  VmallocChunk:   34359457992 kB
  HardwareCorrupted: 0 kB
  AnonHugePages: 38912 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  DirectMap4k:  333824 kB
  DirectMap2M:14313472 kB
  DirectMap1G:18874368 kB

  
  This only seems to happens on specific hardware: Intel Server System P4000CP 
/ S2600CP Motherboard, booted with kernel option: "pci=conf1"

  This does NOT happen on very similar hardware: Intel Server R2312GZ /
  S2600GZ Motherboard

  
  Is there a possible memory, or kernel memory sysctl configurable I'm missing 
here?
  --- 
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Aug 23 07:12 seq
   crw-rw---T 1 root audio 116, 33 Aug 23 07:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=98374fad-7836-4390-b311-614da0ca473c
  InstallationDate: Installed on 2013-02-17 (210 days ago)
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 
(20121017.2)
  Lsusb:
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
  MachineType: Intel Corporation S2600CP ..
  MarkForUpload: True
  Package: linux 3.8.0.30.48
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic 
root=/dev/mapper/h01vg-root ro pci=conf1 intel

[Kernel-packages] [Bug 878031] Re: Oneiric kernel 3.0.0-12-generic fails to start unless nolapic specified, ok in Natty

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

Title:
  Oneiric kernel 3.0.0-12-generic fails to start unless nolapic
  specified, ok in Natty

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  After upgrade from Natty to Oneiric, kernel fails to start. Using ro text 
debug photographed trace info, which shows
  Code: bad EIP value.
  acpi=off allows system to boot, as does nolapic but only one processor out of 
2 shows
  running Natty as live CD works, and shows 2 processors
  other noacpi parameters  failed.
  latest available BIOS installed
  removed sound card, changed video card and monitor no difference.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bill   1634 F pulseaudio
   /dev/snd/controlC1:  bill   1634 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with AD1985 at irq 3'
 Mixer name : 'Analog Devices AD1985'
 Components : 'AC97a:41445375'
 Controls  : 50
 Simple ctrls  : 35
  Card1.Amixer.info:
   Card hw:1 'Audigy'/'SB Audigy 1 ES [SB0160] (rev.3, serial:0x521102) at 
0xb800, irq 11'
 Mixer name : 'SigmaTel STAC9721,23'
 Components : 'AC97a:83847609'
 Controls  : 198
 Simple ctrls  : 34
  DistroRelease: Ubuntu 11.10
  HibernationDevice: RESUME=UUID=35f77834-f08c-4ee8-b6b3-b2cf20b97805
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=173b74ab-6232-45ed-861b-16fd44b7e4e0 ro ro nolapic quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  RfKill:
   
  Tags:  oneiric
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (3 days ago)
  UserGroups: adm admin audio cdrom dialout lp lpadmin mythtv plugdev 
sambashare video
  dmi.bios.date: 02/13/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RL86510A.86A.0089.P21.0502132202
  dmi.board.name: D865PERL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC27648-210
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRL86510A.86A.0089.P21.0502132202:bd02/13/2005:svn:pn:pvr:rvnIntelCorporation:rnD865PERL:rvrAAC27648-210:cvn:ct2:cvr:

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

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

[Kernel-packages] [Bug 758853] Re: WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90()

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

Title:
  WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53
  suspend_test_finish+0x86/0x90()

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  waking up from sleep

  ProblemType: KernelOops
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin  1641 F pulseaudio
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 46'
 Mixer name : 'IDT 92HD73C1X5'
 Components : 'HDA:111d7675,1028029f,00100103'
 Controls  : 16
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Tue Apr 12 11:06:36 2011
  Failure: oops
  HibernationDevice: RESUME=UUID=3f044ca0-44ca-443b-b166-e64dba1a40fb
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: Dell Inc. Studio 1537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=485a2d05-8d93-447c-ade3-10bd91f829b1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.50
  SourcePackage: linux
  Title: WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 
suspend_test_finish+0x86/0x90()
  UpgradeStatus: Upgraded to natty on 2011-04-11 (1 days ago)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0P132H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd11/10/2008:svnDellInc.:pnStudio1537:pvrA05:rvnDellInc.:rn0P132H:rvrA05:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Studio 1537
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 878879] Re: 056a:00df Oneiric doesn't recognize Wacom CTH 670

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

Title:
  056a:00df Oneiric doesn't recognize Wacom CTH 670

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I see the option for graphic tablets in the system settings but that
  doesn't recognize my Wacom CTH 670

  lsusb shows me:

  Bus 001 Device 004: ID 056a:00df Wacom Co., Ltd

  xinput -list doesn't show it

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic-pae 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steffen1851 F pulseaudio
   /dev/snd/controlC0:  steffen1851 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf3ff8000 irq 43'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,1043836c,0010'
 Controls  : 36
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf7efc000 irq 17'
 Mixer name : 'Nvidia GPU 12 HDMI/DP'
 Components : 'HDA:10de0012,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Thu Oct 20 16:17:44 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8b1aa6a2-b0b1-47e6-b60d-c055f8c5b9af
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae 
root=UUID=36d43556-cda5-44d6-ad2b-99bb2d7e6e38 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic-pae N/A
   linux-backports-modules-3.0.0-12-generic-pae  N/A
   linux-firmware1.60
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-09 (11 days ago)
  dmi.bios.date: 11/12/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55
  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.:bvr0901:bd11/12/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55: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/878879/+subscriptions

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

[Kernel-packages] [Bug 876854] Re: high power consumption on Asus X4GS(N43SN)

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

Title:
  high power consumption on Asus X4GS(N43SN)

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  This bug report is about the high power consumption. The battery time
  i get on Windows 7 Home Premium is between 3 and 4 hours. On Ubuntu
  Oneiric I get between 1,5 and 2 hours (with ca. 28-32W power
  consumption).

  When I install nvidia drivers (nvidia-current) the power consumption
  decreases to 22-25 W. But then the 3D mode isn't available and Unity
  2D starts. I don't know how to fix this, but this is another problem.

  When running Ubuntu the fan is always medium-fast to fast. When
  running windows 7 the fan is usually slow and sometimes medium-fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oziriz 1624 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xdf00 irq 43'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0269,104311a3,00100100 
HDA:80862805,80860101,0010'
     Controls  : 23
     Simple ctrls  : 13
  Date: Mon Oct 17 21:42:06 2011
  HibernationDevice: RESUME=UUID=8c761f94-6607-4a3a-9dac-ab042cc4e9f0
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2)
  MachineType: ASUSTeK Computer Inc. N43SN
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=f9150048-8ee4-45a6-ac88-3e6e3062ccc3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N43SN.412
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N43SN
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN43SN.412:bd09/21/2011:svnASUSTeKComputerInc.:pnN43SN:pvr1.0:rvnASUSTeKComputerInc.:rnN43SN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N43SN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 669261] Re: [VIA VT1702] Xubuntu does not sense headphones i.e. does not mute speakers

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

Title:
  [VIA VT1702] Xubuntu does not sense headphones i.e. does not mute
  speakers

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I have played around with the controls in alsamixer and I've found out
  that muting 'mic' cuts off all sound, even in headphones and speaker.

  Furthermore i can put it to liw levels to -almost- mute the speakers
  and have a audible output in the headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
  Uname: Linux 2.6.35-22-generic-pae i686
  NonfreeKernelModules: nvidia
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.23.
   Compiled on Oct 30 2010 for kernel 2.6.35-22-generic-pae (SMP).
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roobie 1865 F pulseaudio
roobie 1908 F xfce4-mixer-plu
roobie 3075 F xfce4-mixer
   /dev/snd/pcmC0D0p:   roobie 1865 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf340 irq 45'
 Mixer name : 'Nvidia MCP77/78 HDMI'
 Components : 'HDA:11061398,1025020a,00100100 
HDA:14f12c06,10250093,0010 HDA:10de0003,10de0101,0010'
 Controls  : 27
 Simple ctrls  : 14
  Date: Mon Nov  1 00:00:58 2010
  InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release i386 
(20101008.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/zsh
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [VIA VT1702] Playback problem
  dmi.bios.date: 03/24/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.09
  dmi.board.name: SJM50MV
  dmi.board.vendor: Packard Bell
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.09:bd03/24/2009:svnPackardBell:pnEasyNoteTR85:pvr0100:rvnPackardBell:rnSJM50MV:rvrRev:cvnPackardBell:ct10:cvrN/A:
  dmi.product.name: EasyNote TR85
  dmi.product.version: 0100
  dmi.sys.vendor: Packard Bell

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

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

[Kernel-packages] [Bug 876964] Re: Wireless does not connect after suspend/resume

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

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

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

Title:
  Wireless does not connect after suspend/resume

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Wireless (intel centrino wireless-n 1000) works on initial boot, but
  will not reconnect after suspend/resume.

  I can see a list of available networks including my own, but it will
  not connect.  It will try and then prompt me for the passphrase again.
  It never actually connects.

  Worked correctly in Ubuntu 11.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jimmyb 1562 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc650 irq 49'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:111d7605,103c1658,00100105 
HDA:80862805,80860101,0010'
 Controls  : 18
 Simple ctrls  : 10
  Date: Mon Oct 17 18:26:31 2011
  HibernationDevice: RESUME=UUID=99fb094b-c8c1-4d3a-9545-458783d7563d
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=9dc698e1-e082-46e3-b4ca-1da405210f27 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  StagingDrivers: rts_pstor mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1658
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1A:bd07/20/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058E1124471620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058E1124471620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1195493] Re: Realtek 8111F silently drops after some use

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

Title:
  Realtek 8111F silently drops after some use

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I have an Asus M5A97 LE R2.0 motherboard with an integrated Realtek
  8111F ethernet chipset, and after a period of time ( 10-20 minutes,
  although it seems shorter under heavy use ) the ethernet stops
  responding. The main symptoms of this are a lack of DNS responses
  (bind is installed locally and configured as recursive), and general
  internet access (e.g, "ping 8.8.8.8" or "ping 192.168.1.1"). I'm able
  to fix this with "ifconfig  down, ifconfig  up,
  dhclient -d", but the issue does come back.

  It's worth noting that some of my research suggested that this could
  possibly be related to IOMMU being enabled, although this is an
  unacceptable solution as disabling IOMMU seems to also disable USB.

  There are no obvious signs of error from the kernel in the "dmesg"
  output or the various system logs (kern.log, syslog), even with the
  verbose and debug options added to the kernel options from the grub
  boot screen.

  I was able to find someone with similar issues on the kernel mailing
  list, and there is a short patch [1] that does appear to fix the issue
  I had. I applied this patch to the raring kernel (via apt-get source
  linux-image) and ethernet has been uninterrupted for about a day now.
  However, this patch does not appear to be integrated into the 3.10
  linux kernel as of now [2].

  This has been tested on the most current raring kernel from the linux-
  image package as well as the mainline kernel that was current as of
  yesterday ( linux-
  image-3.10.0-999-generic_3.10.0-999.201306260405_amd64 ).

  [1] https://lkml.org/lkml/2013/4/10/549
  [2] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/realtek/r8169.c?id=refs/tags/v3.10-rc7#n4192

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-25-generic 3.8.0-25.37
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Thu Jun 27 15:24:54 2013
  HibernationDevice: RESUME=UUID=620dbcbf-ae16-47b7-b3d1-c868d3ad54e8
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic 
root=UUID=2b918b5d-084c-4d73-979b-e5d662ad0e36 ro splash quiet
  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.8.0-25-generic N/A
   linux-backports-modules-3.8.0-25-generic  N/A
   linux-firmware1.106
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-05-11 (47 days ago)
  WifiSyslog:
   Jun 27 08:21:36 yavin dhclient: DHCPREQUEST of 192.168.1.2 on p4p1 to 
192.168.1.1 port 67 (xid=0x7a9a1da7)
   Jun 27 08:21:36 yavin dhclient: DHCPACK of 192.168.1.2 from 192.168.1.1
   Jun 27 08:21:36 yavin dhclient: bound to 192.168.1.2 -- renewal in 37687 
seconds.
  dmi.bios.date: 01/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be f

[Kernel-packages] [Bug 876022] Re: linux perf tool doesn't work

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

Title:
  linux perf tool doesn't work

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  $ perf
  perf: error while loading shared libraries: libbfd-2.21.0-system.20110327.so: 
cannot open shared object file: No such file or directory

  This bug occured after upgrade to Oneric. The temporary fix is to
  create a symlink to the currently installed library.

  sudo ln -s /usr/lib/libbfd-2.21.53-system.20110810.so
  /usr/lib/libbfd-2.21.0-system.20110327.so

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-tools 3.0.0.12.14
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  francis2041 F pulseaudio
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 44'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:14f15069,17aa2155,00100302 
HDA:80862804,17aa21b5,0010'
 Controls  : 12
 Simple ctrls  : 6
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6QHT24WW-1.05'
 Mixer name : 'ThinkPad EC 6QHT24WW-1.05'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Sun Oct 16 18:06:47 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=faed384d-2c4c-464b-a5bf-2aa843e30d5f
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: LENOVO 3249CTO
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae 
root=UUID=3dbb0fe1-6d37-412c-88d6-28843d06e6ef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic-pae N/A
   linux-backports-modules-3.0.0-12-generic-pae  N/A
   linux-firmware1.60
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago)
  WifiSyslog: Oct 16 17:11:08 berta kernel: [74702.768353] dragonizer[21826]: 
segfault at 5f4c4dba ip b7e6ed9a sp b5ca6258 error 4 in 
libpthread-2.13.so[b7e67000+17000]
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET35WW (1.05 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1253951] Re: Intel wifi power save polling (PSP) causes connection issues with some access points

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

Title:
  Intel wifi power save polling (PSP) causes connection issues with some
  access points

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I got a new router (ASUS RT-AC66U) and wifi on my laptop started
  getting really slow, most noticeable in the way it dropped packets and
  had very long roundtrip times for 'ping 8.8.8.8'

  Searching online, I discovered that this might be due to a power
  saving feature, which says that some routers have a bug that makes
  power save polling not work. See
  http://www.intel.com/support/wireless/wlan/sb/cs-006205.htm for
  details.

  Sure enough, when I plugged my AC in, packet loss went away and
  everything was great. When I removed it, packet loss appeared again.
  When I ran "iwconfig wlan0 power off" while AC unplugged, that
  restored correct behaviour.

  Following the advice at http://blog.linuxjunkie.com/blog/2012/04/11
  /linux-and-the-intel-centrino-wireless-n-1030/ I edited /usr/lib/pm-
  utils/power.d/wireless and changed line 39 (standard Ubuntu 13.10
  config) from "power on” to “power off”.

  This fix "works" but obviously means the wifi will drain more power
  than it needs to. For me with this laptop, this is an acceptable
  trade-off.  In an ideal world it would only be off for broken routers.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jml2939 F pulseaudio
  Date: Fri Nov 22 09:04:37 2013
  HibernationDevice: RESUME=UUID=b85b0353-c88b-4a7b-93ca-aa6190b1ff4d
  InstallationDate: Installed on 2012-03-01 (630 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: LENOVO 1080
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=36faead1-a41c-4363-813a-2c4c56e715ef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (25 days ago)
  dmi.bios.date: 11/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 56CN38WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U300s
  dmi.board.vendor: LENOVO
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad U300s
  dmi.modalias: 
dmi:bvnLENOVO:bvr56CN38WW:bd11/21/2011:svnLENOVO:pn1080:pvrLenovoIdeaPadU300s:rvnLENOVO:rnU300s:rvr1.0:cvnLENOVO:ct10:cvrLenovoIdeaPadU300s:
  dmi.product.name: 1080
  dmi.product.version: Lenovo IdeaPad U300s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1199059] Re: PulseAudio doesn't load bluetooth modules automatically(orig.: A2DP audio sink devices failed to work with "bluetoothd : Unable to select SEP" in system log.)

2014-01-22 Thread Chorca

I'm not sure this is just bluez and not a little of pulseaudio, but i'm
still not an expert.

I pulled the source for bluez and recompiled without the  
enable_audio_sources.patch file using quilt:
apt-get source bluez
quilt pop -a
quilt delete enable_audio_sources.patch
quilt push -a
debuild -us -uc
dpkg -i *.deb

This gets me audio. I've commented out everything in
/etc/bluetooth/audio.conf to leave it all to defaults. Here's what I
currently have to do to get working audio (after installing the patch-
modified version as above):

1. Computer start
2. Attempt connection to paired A2DP device. Fails ("bluetoothd: Unable to 
select SEP" in syslog)
3. pactl load-module module-bluetooth-discover (endpoints registered in syslog)
4. Attempt connection to paired A2DP device. Success! Pulseaudio device created 
and available.
5. Open Pulseaudio volume control (to assign default audio output device). 
Pulseaudio crash!:
Jan 22 23:07:11 chrispad pulseaudio[1955]: [pulseaudio] 
module-bluetooth-device.c: Failed to acquire transport 
/org/bluez/999/hci0/dev_00_02_3C_41_CA_0D/fd0
Jan 22 23:07:11 chrispad pulseaudio[1955]: [pulseaudio] 
module-bluetooth-device.c: Assertion 'u->transport' failed at 
modules/bluetooth/module-bluetooth-device.c:363, function 
bt_transport_acquire(). Aborting.
6. Attempt connection to paired A2DP device. Fails ("bluetoothd: Unable to 
select SEP" in syslog)
7. pactl load-module module-bluetooth-discover (endpoints registered in syslog)
8. Attempt connection to paired A2DP device. Success! Pulseaudio device created 
and available.
9. Open Pulseaudio volume control (to assign default audio output device). Can 
finally open and assign output device.

Pulseaudio does seem to crash, as I receive a crash report notification
after step 5, and the Volume Control loses connection to the PA server.

All the while, blueman experiences connection issues to the server,
particularly after "Unable to select SEP", though that may be poor error
handling on blueman's side.

This is on 13.04. I could upgrade to 13.10, but not sure if that will do
anything for this.

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

Title:
  PulseAudio doesn't load bluetooth modules automatically(orig.: A2DP
  audio sink devices failed to work with "bluetoothd : Unable to select
  SEP" in system log.)

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “bluez” package in Debian:
  Fix Released

Bug description:
  All my A2DP profile devices can't create a audio device properly...
  My 2 13.04 machines both have this issue(1 notebook, 2 bluetooth dongles)
  UPDATE: Upgraded to 13.10, still reproducible

  Possible root cause & fix: Please refer #15

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Jul  9 01:01:38 2013
  InstallationDate: Installed on 2013-01-26 (162 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130126)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic 
root=UUID=9bce9679-da3a-44fd-84ec-b16339a84004 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to raring on 2013-03-01 (128 days ago)
  dmi.bios.date: 08/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55-M
  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.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 00:15:83:54:59:9F  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN ISCAN
    RX bytes:29508 acl:1270 sco:0 events:461 errors:0
    TX bytes:5249 acl:165 sco:0 commands:95 errors:0

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

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

[Kernel-packages] [Bug 1034002]

2014-01-22 Thread Hcb-o

This bug is really old and really annoying as it makes the laptops
unusable for suspend -- what kind of traces would be required to
understand the core of the problem, from what I can tell the display
engine is in a severely hosed state, but I lack documentation to
understand what is wrong.

Does setting out a bounty for this bug help? I'm willing to immediately
cash in at $300.

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

Title:
  1002:9641 [Lenovo ThinkPad E525] Screen black on resume

Status in Direct Rendering Infrastructure:
  Confirmed
Status in The Linux Kernel:
  Fix Released
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I did the kernel smoke test for the quantal kernel on precise.

  I can suspend and resume however when I resume I the screen stays
  black. It looks like the backlight isn't coming on, but it's noteable
  that I don't see anything on my external screen either. I can see
  consoles on my external monitor (over HDMI) and if I disconnect the
  HDMI cable and reconnect it then I am also able to see my Unity
  session on that screen. This issue is present with both the quantal
  kernel and the stock 12.04 one.

  WORKAROUND: Use fglrx.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tealeg 2861 F pulseaudio
   /dev/snd/controlC0:  tealeg 2861 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xf0b44000 irq 48'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 6
     Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0b4 irq 16'
     Mixer name : 'Conexant CX20590'
     Components : 'HDA:14f1506e,17aa21ea,0012'
     Controls  : 18
     Simple ctrls  : 10
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
     Mixer name : 'ThinkPad EC (unknown)'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  DistroRelease: Ubuntu 12.04
  HibernationDevice:
   # RESUME=/dev/sda5
   RESUME='UUID=61453936-e394-41de-8b00-5ee8f17023b3'
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029)
  MachineType: LENOVO 12002KG
  Package: linux 3.2.0.27.29
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-7-generic 
root=UUID=c2742c1e-158f-446d-9884-d6f037d7fa8c ro quiet splash elevator=deadline
  ProcVersionSignature: Ubuntu 3.5.0-7.7~precise1-generic 3.5.0
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-7-generic N/A
   linux-backports-modules-3.5.0-7-generic  N/A
   linux-firmware   1.79
  Tags:  precise running-unity
  Uname: Linux 3.5.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  WifiSyslog:

  dmi.bios.date: 07/28/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8IET34WW(1.07)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 12002KG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8IET34WW(1.07):bd07/28/2011:svnLENOVO:pn12002KG:pvrThinkPadE525:rvnLENOVO:rn12002KG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 12002KG
  dmi.product.version: ThinkPad E525
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1034002]

2014-01-22 Thread Adam Pigg

Same problem here running on a HP Laptop Pavillion G7 with AMD A6-3400M
CPU/GPU.

Currently running 3.12.5 kernel from openSuse Tumbleweed, though ive had
this problem for ages.

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

Title:
  1002:9641 [Lenovo ThinkPad E525] Screen black on resume

Status in Direct Rendering Infrastructure:
  Confirmed
Status in The Linux Kernel:
  Fix Released
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I did the kernel smoke test for the quantal kernel on precise.

  I can suspend and resume however when I resume I the screen stays
  black. It looks like the backlight isn't coming on, but it's noteable
  that I don't see anything on my external screen either. I can see
  consoles on my external monitor (over HDMI) and if I disconnect the
  HDMI cable and reconnect it then I am also able to see my Unity
  session on that screen. This issue is present with both the quantal
  kernel and the stock 12.04 one.

  WORKAROUND: Use fglrx.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tealeg 2861 F pulseaudio
   /dev/snd/controlC0:  tealeg 2861 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xf0b44000 irq 48'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 6
     Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0b4 irq 16'
     Mixer name : 'Conexant CX20590'
     Components : 'HDA:14f1506e,17aa21ea,0012'
     Controls  : 18
     Simple ctrls  : 10
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
     Mixer name : 'ThinkPad EC (unknown)'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  DistroRelease: Ubuntu 12.04
  HibernationDevice:
   # RESUME=/dev/sda5
   RESUME='UUID=61453936-e394-41de-8b00-5ee8f17023b3'
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029)
  MachineType: LENOVO 12002KG
  Package: linux 3.2.0.27.29
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-7-generic 
root=UUID=c2742c1e-158f-446d-9884-d6f037d7fa8c ro quiet splash elevator=deadline
  ProcVersionSignature: Ubuntu 3.5.0-7.7~precise1-generic 3.5.0
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-7-generic N/A
   linux-backports-modules-3.5.0-7-generic  N/A
   linux-firmware   1.79
  Tags:  precise running-unity
  Uname: Linux 3.5.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  WifiSyslog:

  dmi.bios.date: 07/28/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8IET34WW(1.07)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 12002KG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8IET34WW(1.07):bd07/28/2011:svnLENOVO:pn12002KG:pvrThinkPadE525:rvnLENOVO:rn12002KG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 12002KG
  dmi.product.version: ThinkPad E525
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1271442] Re: CVE-2014-1444

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

** Changed in: linux-armadaxp (Ubuntu Quantal)
   Status: New => Fix Released

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

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

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

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

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Saucy)
   Status: New => Fix Committed

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

** Changed in: linux-ti-omap4 (Ubuntu Quantal)
   Status: New => Fix Committed

** Changed in: linux-ti-omap4 (Ubuntu Raring)
   Status: New => Fix Committed

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

** Description changed:

- farsync: fix info leak in ioctl
+ The fst_get_iface function in drivers/net/wan/farsync.c in the Linux
+ kernel before 3.11.7 does not properly initialize a certain data
+ structure, which allows local users to obtain sensitive information from
+ kernel memory by leveraging the CAP_NET_ADMIN capability for an
+ SIOCWANDEV ioctl call.
  
  Break-Fix: - 96b340406724d87e4621284ebac5e059d67b2194

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

Title:
  CVE-2014-1444

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  Fix Committed
Status in “linux-lts-raring” source package in Precise:
  Fix Committed
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  Fix Committed
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Committed
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring”

[Kernel-packages] [Bug 1271742] Re: CONFIG_PREEMPT is not set. Why?

2014-01-22 Thread Tim Gardner

I think CONFIG_PREEMPT would have an adverse effect on CPU bound jobs,
though I welcome hard data.

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

** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

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

Title:
  CONFIG_PREEMPT is not set. Why?

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix

Bug description:
  Since the generic kernel is for generic desktop use CONFIG_PREEMPT
  should be set. CONFIG_NO_HZ is already there so it seems strange to me
  that preempt is not especially because recommendations for desktop
  system usually includes building a preemptible kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-tools-3.13.0-5-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2201 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 22 23:12:08 2014
  InstallationDate: Installed on 2013-12-24 (29 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1014350] Re: WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1960 skb_gso_segment+0x341/0x3b0()

2014-01-22 Thread Thiago Martins

Guys,

Please, ignore the following content from my previous post:

---
BTW, all my KVM Guests running behind this bnx2 NIC, have poor network 
performance. For example:

* From client-x to host: iperf shows ~900Mbits/s
* From client-x to guest-1 (ubuntu): iperf shows ~150Mbits/s
* From client-x to guest-2 (pfsense - e1000): iperf shows ~200Mbits/s
* From client-x to guest-2 (pfsense - virtio): iperf shows ~120MBtis/s

So, I starting to think that the bnx2 drivers for Linux is crap.

What do you guys think?!
---

Simple because it is not related to the topic and I'm doing more tests,
ubuntu guest is okay now, only pfsense guest still have poor network
performance and triggers the "bnx2" error on kern.log at host (every
single click on pfsense's webgui, triggers this error on host!). Sorry
about the buzz...

Best,
Thiago

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

Title:
  WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1960
  skb_gso_segment+0x341/0x3b0()

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  we have IBM 3650  with 12.04 amd64 server as a kvm virtualization and
  kern.log is suddenly fill at dramatic rate with this warning.  system
  work normaly for a while and problem start five days ago. any help?

  WORKAROUND: We have several freebsd 9 amd64 guests with virtio network
  drivers. After changing net drv to e1000 the problem disappears.

  [29955.815267] WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1980 
skb_gso_segment+0x341/0x3b0()
  [29955.815269] Hardware name: IBM System x3650 -[7979KPG]-
  [29955.815272] 802.1Q VLAN Support: caps=(0x30095823, 0x0) len=1925 
data_len=0 ip_summed=0
  [29955.815275] Modules linked in: ip6table_filter ip6_tables ebtable_nat 
ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 
xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp 
iptable_filter ip_tables x_tables kvm_intel kvm nfsd nfs lockd fscache 
auth_rpcgss nfs_acl sunrpc bridge 8021q garp stp radeon ttm ibmpex 
drm_kms_helper shpchp ibmaem ipmi_msghandler ics932s401 psmouse drm serio_raw 
i2c_algo_bit i5000_edac edac_core i5k_amb ioatdma mac_hid dca lp parport ses 
enclosure bnx2 aacraid
  [29955.815312] Pid: 7912, comm: kvm Tainted: GW3.2.0-25-generic 
#40-Ubuntu
  [29955.815314] Call Trace:
  [29955.815316][] warn_slowpath_common+0x7f/0xc0
  [29955.815322]  [] warn_slowpath_fmt+0x46/0x50
  [29955.815326]  [] skb_gso_segment+0x341/0x3b0
  [29955.815330]  [] ? update_curr+0x21e/0x230
  [29955.815335]  [] dev_hard_start_xmit+0x11a/0x580
  [29955.815341]  [] ? br_flood+0xc0/0xc0 [bridge]
  [29955.815345]  [] dev_queue_xmit+0x2aa/0x420
  [29955.815350]  [] br_dev_queue_push_xmit+0x6c/0xa0 [bridge]
  [29955.815356]  [] br_forward_finish+0x58/0x60 [bridge]
  [29955.815361]  [] __br_forward+0xab/0xd0 [bridge]
  [29955.815367]  [] br_forward+0x5d/0x70 [bridge]
  [29955.815372]  [] br_handle_frame_finish+0x182/0x2a0 
[bridge]
  [29955.815378]  [] br_handle_frame+0x1c8/0x270 [bridge]
  [29955.815384]  [] ? br_handle_frame_finish+0x2a0/0x2a0 
[bridge]
  [29955.815388]  [] __netif_receive_skb+0x1e2/0x520
  [29955.815391]  [] process_backlog+0xb1/0x190
  [29955.815395]  [] net_rx_action+0x134/0x290
  [29955.815399]  [] __do_softirq+0xa8/0x210
  [29955.815402]  [] call_softirq+0x1c/0x30
  [29955.815404][] do_softirq+0x65/0xa0
  [29955.815410]  [] netif_rx_ni+0x28/0x30
  [29955.815414]  [] tun_get_user+0x306/0x4a0
  [29955.815417]  [] tun_chr_aio_write+0x64/0x90
  [29955.815421]  [] ? tun_chr_aio_read+0xd0/0xd0
  [29955.815424]  [] do_sync_readv_writev+0xd3/0x110
  [29955.815428]  [] ? apparmor_file_permission+0x18/0x20
  [29955.815431]  [] ? security_file_permission+0x2c/0xb0
  [29955.815435]  [] ? rw_verify_area+0x61/0xf0
  [29955.815438]  [] do_readv_writev+0xd4/0x1d0
  [29955.815441]  [] ? eventfd_ctx_read+0x1a5/0x210
  [29955.815445]  [] vfs_writev+0x3c/0x50
  [29955.815447]  [] sys_writev+0x4a/0xb0
  [29955.815451]  [] system_call_fastpath+0x16/0x1b
  [29955.815453] ---[ end trace 33dfb9cf0396c073 ]---

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

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

[Kernel-packages] [Bug 1271742] Re: CONFIG_PREEMPT is not set. Why?

2014-01-22 Thread Tim Gardner

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

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

Title:
  CONFIG_PREEMPT is not set. Why?

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

Bug description:
  Since the generic kernel is for generic desktop use CONFIG_PREEMPT
  should be set. CONFIG_NO_HZ is already there so it seems strange to me
  that preempt is not especially because recommendations for desktop
  system usually includes building a preemptible kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-tools-3.13.0-5-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2201 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 22 23:12:08 2014
  InstallationDate: Installed on 2013-12-24 (29 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1267489] Re: linux-ti-omap4: 3.5.0-238.54 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

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

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

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

Title:
  linux-ti-omap4: 3.5.0-238.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “linux-ti-omap4” source package in Quantal:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 09. January 2014 14:38 UTC
  kernel-stable-master-bug:1266857
  kernel-stable-phase:ReadyToBePackaged
  kernel-stable-phase-changed:Friday, 10. January 2014 21:03 UTC
  kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:03 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267489/+subscriptions

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

[Kernel-packages] [Bug 1014350] Re: WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1960 skb_gso_segment+0x341/0x3b0()

2014-01-22 Thread Thiago Martins

Hi!

I'm facing this problem, it is very easy to reproduce.

1- Host: Ubuntu 12.04.3 (Linux 3.8 or 3.11);
2- KVM (1.5.0 from Ubuntu Cloud Archive, new KVM for LTS);
3- OpenVSwitch 2.0.0 compiled for Ubuntu LTS by me (using `dpkg-buildpackage` 
on the host itself);
4- Guest: PFSense 2.1 with VirtIO drivers;

Every time you access the PFSense web GUI, just every single click,
triggers the following error at host kern.log:

http://paste.ubuntu.com/6800489/

Also, this very same problem happens with Ubuntu 14.04 with Linux 3.13 /
KVM 1.7.0.

NOTE: You'll need to manuaaly enable VirtIO for your PFSense, follow it
here: https://doc.pfsense.org/index.php/VirtIO_Driver_Support

BTW, all my KVM Guests running behind this bnx2 NIC, have poor network
performance. For example:

* From client-x to host: iperf shows ~900Mbits/s
* From client-x to guest-1 (ubuntu): iperf shows ~150Mbits/s
* From client-x to guest-2 (pfsense - e1000): iperf shows ~200Mbits/s
* From client-x to guest-2 (pfsense - virtio): iperf shows ~120MBtis/s

So, I starting to think that the bnx2 drivers for Linux is crap.

What do you guys think?!

Tks!
Thiago

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

Title:
  WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1960
  skb_gso_segment+0x341/0x3b0()

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  we have IBM 3650  with 12.04 amd64 server as a kvm virtualization and
  kern.log is suddenly fill at dramatic rate with this warning.  system
  work normaly for a while and problem start five days ago. any help?

  WORKAROUND: We have several freebsd 9 amd64 guests with virtio network
  drivers. After changing net drv to e1000 the problem disappears.

  [29955.815267] WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1980 
skb_gso_segment+0x341/0x3b0()
  [29955.815269] Hardware name: IBM System x3650 -[7979KPG]-
  [29955.815272] 802.1Q VLAN Support: caps=(0x30095823, 0x0) len=1925 
data_len=0 ip_summed=0
  [29955.815275] Modules linked in: ip6table_filter ip6_tables ebtable_nat 
ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 
xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp 
iptable_filter ip_tables x_tables kvm_intel kvm nfsd nfs lockd fscache 
auth_rpcgss nfs_acl sunrpc bridge 8021q garp stp radeon ttm ibmpex 
drm_kms_helper shpchp ibmaem ipmi_msghandler ics932s401 psmouse drm serio_raw 
i2c_algo_bit i5000_edac edac_core i5k_amb ioatdma mac_hid dca lp parport ses 
enclosure bnx2 aacraid
  [29955.815312] Pid: 7912, comm: kvm Tainted: GW3.2.0-25-generic 
#40-Ubuntu
  [29955.815314] Call Trace:
  [29955.815316][] warn_slowpath_common+0x7f/0xc0
  [29955.815322]  [] warn_slowpath_fmt+0x46/0x50
  [29955.815326]  [] skb_gso_segment+0x341/0x3b0
  [29955.815330]  [] ? update_curr+0x21e/0x230
  [29955.815335]  [] dev_hard_start_xmit+0x11a/0x580
  [29955.815341]  [] ? br_flood+0xc0/0xc0 [bridge]
  [29955.815345]  [] dev_queue_xmit+0x2aa/0x420
  [29955.815350]  [] br_dev_queue_push_xmit+0x6c/0xa0 [bridge]
  [29955.815356]  [] br_forward_finish+0x58/0x60 [bridge]
  [29955.815361]  [] __br_forward+0xab/0xd0 [bridge]
  [29955.815367]  [] br_forward+0x5d/0x70 [bridge]
  [29955.815372]  [] br_handle_frame_finish+0x182/0x2a0 
[bridge]
  [29955.815378]  [] br_handle_frame+0x1c8/0x270 [bridge]
  [29955.815384]  [] ? br_handle_frame_finish+0x2a0/0x2a0 
[bridge]
  [29955.815388]  [] __netif_receive_skb+0x1e2/0x520
  [29955.815391]  [] process_backlog+0xb1/0x190
  [29955.815395]  [] net_rx_action+0x134/0x290
  [29955.815399]  [] __do_softirq+0xa8/0x210
  [29955.815402]  [] call_softirq+0x1c/0x30
  [29955.815404][] do_softirq+0x65/0xa0
  [29955.815410]  [] netif_rx_ni+0x28/0x30
  [29955.815414]  [] tun_get_user+0x306/0x4a0
  [29955.815417]  [] tun_chr_aio_write+0x64/0x90
  [29955.815421]  [] ? tun_chr_aio_read+0xd0/0xd0
  [29955.815424]  [] do_sync_readv_writev+0xd3/0x110
  [29955.815428]  [] ? apparmor_file_permission+0x18/0x20
  [29955.815431]  [] ? security_file_permission+0x2c/0xb0
  [29955.815435]  [] ? rw_verify_area+0x61/0xf0
  [29955.815438]  [] do_readv_writev+0xd4/0x1d0
  [29955.815441]  [] ? eventfd_ctx_read+0x1a5/0x210
  [29955.815445]  [] vfs_writev+0x3c/0x50
  [29955.815447]  [] sys_writev+0x4a/0xb0
  [29955.815451]  [] system_call_fastpath+0x16/0x1b
  [29955.815453] ---[ end trace 33dfb9cf0396c073 ]---

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

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

[Kernel-packages] [Bug 1271441] Re: CVE-2014-1438

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

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

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

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

** Description changed:

- missing CPU-state sanitation during task-switch causes DOS / privilege
- escalation
+ The restore_fpu_checking function in arch/x86/include/asm/fpu-internal.h
+ in the Linux kernel before 3.12.8 on the AMD K7 and K8 platforms does
+ not clear pending exceptions before proceeding to an EMMS instruction,
+ which allows local users to cause a denial of service (task kill) or
+ possibly gain privileges via a crafted application.
+ 
+ Break-Fix: - 26bef1318adc1b3a530ecc807ef99346db2aa8b0

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

Title:
  CVE-2014-1438

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  New
Status in “linux-armadaxp” source package in Precise:
  New
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  New
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  New
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  New
Status in “linux-lts-backport-natty” source package in Saucy:
  New
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “li

[Kernel-packages] [Bug 1267090] Re: CVE-2013-7271

** Changed in: linux-ec2 (Ubuntu Lucid)
   Status: New => Fix Committed

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

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

Title:
  CVE-2013-7271

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Committed
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Raring:
  Won't Fix
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  New
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in

[Kernel-packages] [Bug 1267469] Re: linux-ti-omap4: 3.2.0-1443.62 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

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

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

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

Title:
  linux-ti-omap4: 3.2.0-1443.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “linux-ti-omap4” source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 09. January 2014 13:46 UTC
  kernel-stable-master-bug:1266551
  kernel-stable-phase:ReadyToBePackaged
  kernel-stable-phase-changed:Friday, 10. January 2014 21:02 UTC
  kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267469/+subscriptions

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

[Kernel-packages] [Bug 1267087] Re: CVE-2013-7270

** Changed in: linux-ec2 (Ubuntu Lucid)
   Status: New => Fix Committed

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

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

Title:
  CVE-2013-7270

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Committed
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Raring:
  Won't Fix
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  New
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in

[Kernel-packages] [Bug 1267489] Re: linux-ti-omap4: 3.5.0-238.54 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

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

Title:
  linux-ti-omap4: 3.5.0-238.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “linux-ti-omap4” source package in Quantal:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 09. January 2014 14:38 UTC
  kernel-stable-master-bug:1266857
  kernel-stable-phase:ReadyToBePackaged
  kernel-stable-phase-changed:Friday, 10. January 2014 21:03 UTC
  kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:03 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267489/+subscriptions

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

[Kernel-packages] [Bug 1267469] Re: linux-ti-omap4: 3.2.0-1443.62 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

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

Title:
  linux-ti-omap4: 3.2.0-1443.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “linux-ti-omap4” source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 09. January 2014 13:46 UTC
  kernel-stable-master-bug:1266551
  kernel-stable-phase:ReadyToBePackaged
  kernel-stable-phase-changed:Friday, 10. January 2014 21:02 UTC
  kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267469/+subscriptions

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

[Kernel-packages] [Bug 1267085] Re: CVE-2013-7269

** Changed in: linux-ec2 (Ubuntu Lucid)
   Status: New => Fix Committed

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

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

Title:
  CVE-2013-7269

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Committed
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Raring:
  Won't Fix
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  New
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in

[Kernel-packages] [Bug 1267083] Re: CVE-2013-7268

** Changed in: linux-ec2 (Ubuntu Lucid)
   Status: New => Fix Committed

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

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

Title:
  CVE-2013-7268

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Committed
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Raring:
  Won't Fix
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  New
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in

[Kernel-packages] [Bug 1267082] Re: CVE-2013-7267

** Changed in: linux-ec2 (Ubuntu Lucid)
   Status: New => Fix Committed

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

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

Title:
  CVE-2013-7267

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Committed
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Raring:
  Won't Fix
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  New
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in

[Kernel-packages] [Bug 1267469] Re: linux-ti-omap4: 3.2.0-1443.62 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: Confirmed => Fix Released

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

Title:
  linux-ti-omap4: 3.2.0-1443.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “linux-ti-omap4” source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 09. January 2014 13:46 UTC
  kernel-stable-master-bug:1266551
  kernel-stable-phase:ReadyToBePackaged
  kernel-stable-phase-changed:Friday, 10. January 2014 21:02 UTC
  kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267469/+subscriptions

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

[Kernel-packages] [Bug 1267081] Re: CVE-2013-7266

** Changed in: linux-ec2 (Ubuntu Lucid)
   Status: New => Fix Committed

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

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

Title:
  CVE-2013-7266

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Committed
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Raring:
  Won't Fix
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  New
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

2014-01-22 Thread Dave Chiluk

As cking noted in #4 this would cause a performance impact for ext2/3.
That alone prevents it from moving into the stable saucy kernel.

Additionally this is a significant enough change that it would not satisfy the 
SRU requirements for pushing into the saucy kernel.  
Please see
https://wiki.ubuntu.com/StableReleaseUpdates#Why


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

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

Title:
  Please enable CONFIG_IMA in the ubuntu kernel

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

Bug description:
  I would be doubly happy if this also went into the raring backport
  kernel.

  I chatted with apw and kees on #ubuntu-kernel earlier in the week.
  From a security engineer on our team:

  so I was mistaken. if CONFIG_IMA=y, the default policy is NULL unless
  you boot with ima_tcb=on. without ima_tcb=y, nothing is measured,
  nothing is audited, no performance/memory hit is incurred.

  Same is true for CONFIG_IMA_APPRAISE, except with the
  ima_appraise_tcb=on commandline parameter. ima appraise gives us the
  ability to sign binaries at installation time and check the signature
  at runtime.

  So we are asking that you enable CONFIG_IMA, but to not enable it via
  the kernel command line options. IMA would boot with an empty policy
  and should incur no overhead. Enterprising folks who want to run IMA
  can enable it in grub at their option.

  CONFIG_IMA=y

  and possibly:

  CONFIG_IMA_MEASURE_PCR_IDX=10
  CONFIG_IMA_AUDIT=y
  CONFIG_IMA_LSM_RULES=y

  -A

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

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

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

Title:
  CONFIG_PREEMPT is not set. Why?

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Since the generic kernel is for generic desktop use CONFIG_PREEMPT
  should be set. CONFIG_NO_HZ is already there so it seems strange to me
  that preempt is not especially because recommendations for desktop
  system usually includes building a preemptible kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-tools-3.13.0-5-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2201 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 22 23:12:08 2014
  InstallationDate: Installed on 2013-12-24 (29 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1271669] Re: Move vmware related modules from extras into main kernel package

2014-01-22 Thread Stefan Bader

Test packages in people.cc/~smb/vmcitest.

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

Title:
  Move vmware related modules from extras into main kernel package

Status in “linux” package in Ubuntu:
  In Progress
Status in “open-vm-tools” package in Ubuntu:
  In Progress

Bug description:
  drivers/misc/vmw_vmci/vmw_vmci.ko,
  net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko
  are currently in linux-image-extra. Due to a sync of open-vm-tools and
  an open MIR on open-vm-tools, these modules are needed in the regular
  kernel.

  Bug #1220950 open-vm-tools

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

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

[Kernel-packages] [Bug 1254894] Re: CVE-2013-4563

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

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

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

Title:
  CVE-2013-4563

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Invalid
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Invalid
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-armadaxp” source package in Precise:
  Invalid
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Invalid
Status in “linux-lts-raring” source package in Precise:
  Invalid
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Invalid
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-armadaxp” source package in Quantal:
  Invalid
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  Invalid
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Raring:
  Won't Fix
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source p

[Kernel-packages] [Bug 1271742] [NEW] CONFIG_PREEMPT is not set. Why?

Public bug reported:

Since the generic kernel is for generic desktop use CONFIG_PREEMPT
should be set. CONFIG_NO_HZ is already there so it seems strange to me
that preempt is not especially because recommendations for desktop
system usually includes building a preemptible kernel.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-tools-3.13.0-5-generic (not installed)
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic i686
ApportVersion: 2.13.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sgh2201 F pulseaudio
CurrentDesktop: KDE
Date: Wed Jan 22 23:12:08 2014
InstallationDate: Installed on 2013-12-24 (29 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
MachineType: LENOVO 2356GCG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-5-generic N/A
 linux-backports-modules-3.13.0-5-generic  N/A
 linux-firmware1.122
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ET31WW (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2356GCG
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2356GCG
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

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


** Tags: apport-bug i386 trusty

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

Title:
  CONFIG_PREEMPT is not set. Why?

Status in “linux” package in Ubuntu:
  New

Bug description:
  Since the generic kernel is for generic desktop use CONFIG_PREEMPT
  should be set. CONFIG_NO_HZ is already there so it seems strange to me
  that preempt is not especially because recommendations for desktop
  system usually includes building a preemptible kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-tools-3.13.0-5-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2201 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 22 23:12:08 2014
  InstallationDate: Installed on 2013-12-24 (29 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1097932] Re: [Lenovo e335] - After suspend with FGLRX or WITHOUT - The system loses primary display.

2014-01-22 Thread davepc

The bug is confirmed present in Ubuntu Gnome 13.10.

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

Title:
  [Lenovo e335] - After suspend with FGLRX or WITHOUT - The system loses
  primary display.

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

Bug description:
  As mentioned in the topic - With the FGLRX driver installed or without
  - when the system suspends and resumes, the video never returns.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-29-generic 3.2.0-29.46
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1689 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1689 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xf0344000 irq 49'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf034 irq 16'
 Mixer name : 'Realtek ALC269VC'
 Components : 'HDA:10ec0269,17aa5104,00100202'
 Controls  : 17
 Simple ctrls  : 9
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
 Mixer name : 'ThinkPad EC (unknown)'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Wed Jan  9 15:19:38 2013
  HibernationDevice: RESUME=UUID=a9b51b7d-3218-4a59-9c88-f875297e1a3d
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: LENOVO 335520U
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=UUID=b3c3d525-fc7e-4846-b26f-e41d6e169949 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-29-generic N/A
   linux-backports-modules-3.2.0-29-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: rts_pstor
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HKET17WW(1.03)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 335520U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrHKET17WW(1.03):bd05/31/2012:svnLENOVO:pn335520U:pvrThinkpadEdgeE335:rvnLENOVO:rn335520U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 335520U
  dmi.product.version: Thinkpad Edge E335
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1079435] Re: Thinkpad Edge E335 not resuming from suspend

2014-01-22 Thread davepc

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

I confirm the bug is exactly as originally described on Ubuntu Gnome
13.10.

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

Title:
  Thinkpad Edge E335 not resuming from suspend

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  When I suspend my E335 to RAM, the system powers down and the Thinkpad-i-LED 
goes to its suspend-mode-blinking.
  Unfortunately, the notebook won't resume when being re-opened or power-button 
pushed.

  I've tried using a kernel from the PPA (https://launchpad.net/~kernel-
  ppa/+archive/ppa), but same behavior.

  I've also followed the "DebuggingKernelSuspend" steps
  (https://wiki.ubuntu.com/DebuggingKernelSuspend), but didn't receive
  any "hash matches" lines in the logs :(

  Any tips greatly appreciated.
  Thanks!

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

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

Re: [Kernel-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2014-01-22 Thread Steve Dodd

On Wed, Jan 22, 2014 at 04:13:19PM -, Max wrote:
> Steve Dodd:

> > Last time I did, my own problems were caused by dhclient and ureadahead..
> 
> It is not an ureadahead issue, it is an extra fork in upstart to launch
> shell for ureadahead if more than one partition mounted.

Yes, I know - I was summarizing!

On Wed, Jan 22, 2014 at 04:51:06PM -, Steve Langasek wrote:
> On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:

> > Lennert of systemd refers to this bug on google+. He outlines a fix for
> > the simple case:
> 
> The fix he outlines is not for this bug.  It's not for a bug we have in
> upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of
> all of upstart's library dependencies, which are finite and accounted for.

Good to know, thank you.

On Wed, Jan 22, 2014 at 06:21:52PM -, Steve Langasek wrote:

[..]
> There may be other failure scenarios that need to be addressed.  Part of the
> problem has been a lack of information about what's actually holding the
> root filesystem open in these cases.  There's a pending merge proposal on
> sysvinit that should help us gather this information.

I had been going to suggest this a while back - automated apport
reporting of unclean shutdowns, with as much cause information as
possible?

I will try to do something constructive like boot into trusty and make
sure my personal issues have been resolved (I've not looked at this for
a few months.) I'm updating my images as we speak.

Steve

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

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68

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

Title:
  IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel
  3.5.0-45.68

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-lts-quantal” source package in Precise:
  Confirmed
Status in “linux-lts-raring” source package in Precise:
  Fix Committed
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  Fix Committed
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux-lts-quantal” source package in Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid

Bug description:
  Something has changed in Ubuntu's Kernel 3.5.0-45 32 & 64-bit Intel,
  has prevented IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes. The IBM Domino Application Server's parent process
  "/opt/ibm/domino/notes/latest/linux/server" runs as a Service Account
  or a normal non-admin user, that launches "bindsock"and others like
  "http", "ldap"

  In the Live Domino Console we're seeing the Application Server report:
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  Another thing in the Live Domino Console, which is unusual is:
    "Error_CmdToDo_INVAL"... might be an IBM thang.

  A number of us have to hold back the kernel now and there's lots of 
scratching going on.
    
http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=485F5F092833BCBE85257C33006AC7A3

  It does seem to be limited to IBM Domino's "bindsock" binary and other
  things are just fine, such as Nginx.

  I have attached some files within the zip "ibm-domino-bindsock_strace.zip"
  >>bindsock_binary_strace.txt
  This is just running strace against the binary that isn't running in any 
process.

  >> domino-server-pid1052_strace-f.txt
  The IBM Domino Application Server 
("/opt/ibm/domino/notes/latest/linux/server") is running as PID 1052 so this is 
what I applied "strace -f" to and towards the end, I told "server" to start the 
"http" process ("l http") which would then try launch "bindsock" (I hope).

  Hopeully this first attempt at strace provides some good info for you
  kind folks :-)

  Many thanks
  MR

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-45-generic 3.5.0-45.68~precise1
  ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26
  Uname: Linux 3.5.0-45-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Date: Tue Jan 14 15:33:47 2014
  HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic 
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-45-generic N/A
   linux-backports-modules-3.5.0-45-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1265024] Re: TLS register TPIDRURW not preserved on context switch and fork

One more test kernel.  This is a patched precise test kernel, that I
built in a precise schroot:

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

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

Title:
  TLS register TPIDRURW not preserved on context switch and fork

Status in “linux-ti-omap4” package in Ubuntu:
  In Progress

Bug description:
  Please backport commit a4780adeefd042482f624f5e0d577bf9cdcbb760 (which
  is included in upstream kernel 3.11) to the ti-omap4 packages for
  ubuntu precise.

  I tried doing this manually, and when cherrypicking there's a minor pretty 
trivial conflict to resolve, and after cherrypicking it works just fine.
  --- 
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: armhf
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  Package: linux-image-omap4 3.2.0.1441.39
  PackageArchitecture: armhf
  ProcVersionSignature: Ubuntu 3.2.0-1442.61-omap4 3.2.53
  Tags:  precise
  Uname: Linux 3.2.0-1442-omap4 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

2014-01-22 Thread Chris J Arges

** Changed in: linux (Ubuntu Saucy)
 Assignee: Chris J Arges (arges) => Dave Chiluk (chiluk)

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

Title:
  Please enable CONFIG_IMA in the ubuntu kernel

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

Bug description:
  I would be doubly happy if this also went into the raring backport
  kernel.

  I chatted with apw and kees on #ubuntu-kernel earlier in the week.
  From a security engineer on our team:

  so I was mistaken. if CONFIG_IMA=y, the default policy is NULL unless
  you boot with ima_tcb=on. without ima_tcb=y, nothing is measured,
  nothing is audited, no performance/memory hit is incurred.

  Same is true for CONFIG_IMA_APPRAISE, except with the
  ima_appraise_tcb=on commandline parameter. ima appraise gives us the
  ability to sign binaries at installation time and check the signature
  at runtime.

  So we are asking that you enable CONFIG_IMA, but to not enable it via
  the kernel command line options. IMA would boot with an empty policy
  and should incur no overhead. Enterprising folks who want to run IMA
  can enable it in grub at their option.

  CONFIG_IMA=y

  and possibly:

  CONFIG_IMA_MEASURE_PCR_IDX=10
  CONFIG_IMA_AUDIT=y
  CONFIG_IMA_LSM_RULES=y

  -A

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

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

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

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Incomplete
Status in “linux” source package in Trusty:
  Confirmed

Bug description:
  bug report:
  Hi guys,

  I'm running ubuntu12.04 server on a HP DL380G7. 
  server01 ~ # lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  I've got 2 ethernet cards with 4x 10G interfaces.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  H

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2014-01-22 Thread Alexander List

I can reproduce the delay problem on Trusty.

machine is pingable after around 8s, which means that bonding, vlans and
bridges all work.

However, startup is delayed by ~120s for unknown reasons. After that,
startup resumes and all services come up.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996369/+attachment/3954680/+files/dmesg

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

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Incomplete
Status in “linux” source package in Trusty:
  Confirmed

Bug description:
  bug report:
  Hi guys,

  I'm running ubuntu12.04 server on a HP DL380G7. 
  server01 ~ # lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  I've got 2 ethernet cards with 4x 10G interfaces.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  M

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2014-01-22 Thread Alexander List

** Attachment added: "/etc/network/interfaces"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996369/+attachment/3954681/+files/interfaces

** Also affects: linux (Ubuntu Trusty)
   Importance: High
   Status: Incomplete

** Changed in: linux (Ubuntu Trusty)
   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/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Incomplete
Status in “linux” source package in Trusty:
  Confirmed

Bug description:
  bug report:
  Hi guys,

  I'm running ubuntu12.04 server on a HP DL380G7. 
  server01 ~ # lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  I've got 2 ethernet cards with 4x 10G interfaces.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame

[Kernel-packages] [Bug 1271540] Re: Random "Watchdog detected hard lockup" when resuming from suspend

I have just installed the latest upstream kernel. Everything is working
properly now.
I gonna test the suspend just after posting this post and I'll see if I got the
bug another time.

How much times (for suspend) or how long should I wait before
considering this kernel fixes the bug ?

Thanks by advance.

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

Title:
Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Hi,

I encounter a random bug when suspending my computer : everything suspends
properly when I press the sleep button on the keyboard, but sometimes the
computer freezes when I wake it up (by hitting the power button). So I have to
power off the computer by long press on the power button, or reset the computer.
I tried to suspend with the pm-suspend command, I got the same result.
I tried to suspend through a TTY, and here I was able to get some logs (I
took a photo of the log, attached to this bug report).
The error message was the watchdog detected a hard lockup on the cpu (8 core
cpu, so I got several times the message).
The faulty software seems to be systemd-udevd, according to the trace I got.
I googled a bit the problem, but wasn't able to very usefull information

I wasn't able to find anything about the message I saw on the screen
in the log files. No record at the time of the freeze. That really
surprised me.

I noticed also this problem related to suspend : I use virtualbox and
if I suspend computer, resume it and try to launch a VM after, I can't
get it running properly : it is very slow and I have to reboot the
compter to get it working properly. And I noticed also if I have used
a VM and after I suspend the computer, I am almost sure I'm gonna have
a freeze when I wake the computer up. Maybe is there something related
?

This problem happens randomly but I didn't find anything to reproduce it.
Here is the configuration of the computer :
-mother board : MSI h77ma-g43
-cpu : intel core i7 ivy bridge series
-ram : 16 gb
-using onboard soundcard and video card
-1 hdd 1.5 tb on sata 3
-another 1 tb hdd on sata 3
-bluray/dvd burner on sata

Using Kubuntu 13.10 x64 everything up to date.

Does anybody get the same or a similar problem ?
If any more information is needed, please feel free to ask.
---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: vincent2337 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
InstallationDate: Installed on 2012-06-02 (599 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120423)
IwConfig:
eth0 no wireless extensions.

lono wireless extensions.
MachineType: MSI MS-7756
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
RelatedPackageVersions:
linux-restricted-modules-3.11.0-15-generic N/A
linux-backports-modules-3.11.0-15-generic N/A
linux-firmware 1.116
RfKill:

Tags: saucy
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo
vboxusers wireshark
dmi.bios.date: 10/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H77MA-G43 (MS-7756)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7756
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1269210] Re: KernelCrash

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

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

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

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.


[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/


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

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

Title:
  KernelCrash

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  it happens on stage of configuring package, appear friezes and
  automatic restart

  ubuntu 14.04 with the last update (proposed repository)

  lsb_release -rd
  Description:Ubuntu Trusty Tahr (development branch)
  Release:14.04

  cat /proc/version
  Linux version 3.13.0-2-generic (buildd@komainu) (gcc version 4.8.2 
(Ubuntu/Linaro 4.8.2-12ubuntu2) ) #17-Ubuntu SMP Fri Jan 10 12:14:30 UTC 2014

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-2-generic 3.13.0-2.17
  ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
  Uname: Linux 3.13.0-2-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karma  2294 F pulseaudio
  CRDA:
   country RU:
    (2402 - 2482 @ 40), (N/A, 20)
    (5735 - 5835 @ 20), (N/A, 30)
  Date: Wed Jan 15 09:21:01 2014
  HibernationDevice: RESUME=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0
  InstallationDate: Installed on 2012-09-30 (471 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  MachineType: ASUSTeK Computer Inc. K53SD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic 
root=UUID=3a12bdbf-2c31-4f31-b854-e8f79e6888ad ro rootfstype=ext4 verbose 
resume=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0 crashkernel=384M-:128M
  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-2-generic N/A
   linux-backports-modules-3.13.0-2-generic  N/A
   linux-firmware1.121
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2013-11-10 (65 days ago)
  dmi.bios.date: 03/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53SD.205:bd03/06/2012:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1271669] Re: move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to linux-image-virtual

2014-01-22 Thread Ben Howard

Please make sure that vmxnet3 is included, not vmxnet

** Summary changed:

- move vmware modules (vmci, vsock, vxnet) from linux-image-extra to 
linux-image-virtual
+ move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to 
linux-image-virtual

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

Title:
  move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to
  linux-image-virtual

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  drivers/misc/vmw_vmci/vmw_vmci.ko,
  net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko
  are currently in linux-image-extra. Due to a sync of open-vm-tools and
  an open MIR on open-vm-tools, these modules are needed in the regular
  kernel.

  Bug #1220950 open-vm-tools

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

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

Re: [Kernel-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2014-01-22 Thread Bernd Schubert

On 01/22/2014 05:51 PM, Steve Langasek wrote:
> On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
>> Lennert of systemd refers to this bug on google+. He outlines a fix for
>> the simple case:
>
> The fix he outlines is not for this bug.  It's not for a bug we have in
> upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of
> all of upstart's library dependencies, which are finite and accounted for.

Why shouldn't switching to an independent file system (tmpfs/initramfs) 
and shutdown-init-process not help? That way you can kill all processes 
without exceptions. You can even entirely unmount the old root, no need 
for remounting it read-only anymore.

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

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1271540] Re: Random "Watchdog detected hard lockup" when resuming from suspend

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

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

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

If you are unable to test the mainline kernel, for example it will not boot,
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/

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

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

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

Title:
Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Hi,

I wasn't able to find anything about the message I saw on the screen
in the log files. No record at the time of the freeze. That really
surprised me.

Using Kubuntu 13.10 x64 everything up to date.

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

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

[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68

** Description changed:

  Something has changed in Ubuntu's Kernel 3.5.0-45 32 & 64-bit Intel, has
  prevented IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock"
  binary that runs as root (setuid) to get ports lower than 1024 for it's
  LDAP, SMTP, IMAP, POP3, and HTTP processes. The IBM Domino Application
  Server's parent process "/opt/ibm/domino/notes/latest/linux/server" runs
  as a Service Account or a normal non-admin user, that launches
  "bindsock"and others like "http", "ldap"
  
  In the Live Domino Console we're seeing the Application Server report:
-   "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."
+   "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."
  
  Another thing in the Live Domino Console, which is unusual is:
-   "Error_CmdToDo_INVAL"... might be an IBM thang.
+   "Error_CmdToDo_INVAL"... might be an IBM thang.
  
  A number of us have to hold back the kernel now and there's lots of 
scratching going on.
-   
http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=485F5F092833BCBE85257C33006AC7A3
 
+   
http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=485F5F092833BCBE85257C33006AC7A3
  
  It does seem to be limited to IBM Domino's "bindsock" binary and other
  things are just fine, such as Nginx.
  
  I have attached some files within the zip "ibm-domino-bindsock_strace.zip"
  >>bindsock_binary_strace.txt
  This is just running strace against the binary that isn't running in any 
process.
  
  >> domino-server-pid1052_strace-f.txt
  The IBM Domino Application Server 
("/opt/ibm/domino/notes/latest/linux/server") is running as PID 1052 so this is 
what I applied "strace -f" to and towards the end, I told "server" to start the 
"http" process ("l http") which would then try launch "bindsock" (I hope).
  
  Hopeully this first attempt at strace provides some good info for you
  kind folks :-)
  
  Many thanks
  MR
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-45-generic 3.5.0-45.68~precise1
  ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26
  Uname: Linux 3.5.0-45-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Date: Tue Jan 14 15:33:47 2014
  HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
-  Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  MarkForUpload: True
  ProcEnviron:
-  SHELL=/bin/bash
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
-  LANGUAGE=en_GB:en
+  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  LANGUAGE=en_GB:en
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic 
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
  RelatedPackageVersions:
-  linux-restricted-modules-3.5.0-45-generic N/A
-  linux-backports-modules-3.5.0-45-generic  N/A
-  linux-firmware1.79.9
+  linux-restricted-modules-3.5.0-45-generic N/A
+  linux-backports-modules-3.5.0-45-generic  N/A
+  linux-firmware1.79.9
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-quantal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
+ 
+ 
+ break-fix: - db31c55a6fb245fdbb752a2ca4aefec89afabb06

** Tags added: linux-break-fix

-- 
You received this bug notification because you are a member of Ke

[Kernel-packages] [Bug 1271669] Re: Move vmware related modules from extras into main kernel package

2014-01-22 Thread Ben Howard

Once these modules are enabled in the kernel, we should disable the
modules in open-vm-tools DKMS package. The only module that should be
built via the DKMS package is vmhgfs.

** Also affects: open-vm-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: open-vm-tools (Ubuntu)
 Assignee: (unassigned) => Robert Jennings (rcj)

** Changed in: open-vm-tools (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-14.04

** Changed in: open-vm-tools (Ubuntu)
Milestone: None => ubuntu-14.04

** Changed in: open-vm-tools (Ubuntu)
   Status: New => In Progress

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

Title:
  Move vmware related modules from extras into main kernel package

Status in “linux” package in Ubuntu:
  In Progress
Status in “open-vm-tools” package in Ubuntu:
  In Progress

Bug description:
  drivers/misc/vmw_vmci/vmw_vmci.ko,
  net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko
  are currently in linux-image-extra. Due to a sync of open-vm-tools and
  an open MIR on open-vm-tools, these modules are needed in the regular
  kernel.

  Bug #1220950 open-vm-tools

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

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

[Kernel-packages] [Bug 1270656] Re: Ubuntu 14.04 boots to blank console

2014-01-22 Thread Thomas Schweikle

** Attachment added: "dmesg-log from Ubuntu-Kernel, no driver blacklisted"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954637/+files/dmsg-201401221500.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/1270656

Title:
  Ubuntu 14.04 boots to blank console

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

Bug description:
  Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
  Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows 
/sbin/getty running on tty{1..6}:

  # ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
   4290 pts/1S+ 0:00  \_ grep --color=auto tty
   1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1

  
  Removing deprecated "vga=768" from kernel commandline => doesn't boot into 
800x600, keeps 640x480
  Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
  are ignored.

  Grub boots up with 800x600, switches back to 640x480 (setting
  GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back
  to 800x600.

  Adding deprecated "vga=768" back in:
  Grub boots up with 800x600, switches back to 640x480, kernel switches back to 
800x600, but doesn't use this console. No output at all. Keys are accepted (you 
can login, but you'll have to guess what is going on on the screen).

  Exactly the same error is found with debian. Switching to a self
  compiled kernel solves this error. Looks a lot like some necessary
  stuff for console resolution switching is missing in the debian
  -/ubuntu-kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 20 00:20:36 2014
  InstallationDate: Installed on 2012-12-12 (403 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)

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

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

[Kernel-packages] [Bug 1270656] Re: Ubuntu 14.04 boots to blank console

2014-01-22 Thread Thomas Schweikle

My fault: picked the wrong dmesg-files …!

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

Title:
  Ubuntu 14.04 boots to blank console

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

Bug description:
  Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
  Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows 
/sbin/getty running on tty{1..6}:

  # ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
   4290 pts/1S+ 0:00  \_ grep --color=auto tty
   1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1

  
  Removing deprecated "vga=768" from kernel commandline => doesn't boot into 
800x600, keeps 640x480
  Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
  are ignored.

  Grub boots up with 800x600, switches back to 640x480 (setting
  GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back
  to 800x600.

  Adding deprecated "vga=768" back in:
  Grub boots up with 800x600, switches back to 640x480, kernel switches back to 
800x600, but doesn't use this console. No output at all. Keys are accepted (you 
can login, but you'll have to guess what is going on on the screen).

  Exactly the same error is found with debian. Switching to a self
  compiled kernel solves this error. Looks a lot like some necessary
  stuff for console resolution switching is missing in the debian
  -/ubuntu-kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 20 00:20:36 2014
  InstallationDate: Installed on 2012-12-12 (403 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)

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

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

[Kernel-packages] [Bug 1270656] Re: Ubuntu 14.04 boots to blank console

2014-01-22 Thread Thomas Schweikle

** Attachment added: "dmesg-log from my own kernel, no driver blacklisted"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954635/+files/dmsg-201401221526.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/1270656

Title:
  Ubuntu 14.04 boots to blank console

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

Bug description:
  Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
  Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows 
/sbin/getty running on tty{1..6}:

  # ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
   4290 pts/1S+ 0:00  \_ grep --color=auto tty
   1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1

  
  Removing deprecated "vga=768" from kernel commandline => doesn't boot into 
800x600, keeps 640x480
  Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
  are ignored.

  Grub boots up with 800x600, switches back to 640x480 (setting
  GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back
  to 800x600.

  Adding deprecated "vga=768" back in:
  Grub boots up with 800x600, switches back to 640x480, kernel switches back to 
800x600, but doesn't use this console. No output at all. Keys are accepted (you 
can login, but you'll have to guess what is going on on the screen).

  Exactly the same error is found with debian. Switching to a self
  compiled kernel solves this error. Looks a lot like some necessary
  stuff for console resolution switching is missing in the debian
  -/ubuntu-kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 20 00:20:36 2014
  InstallationDate: Installed on 2012-12-12 (403 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)

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

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

[Kernel-packages] [Bug 1183804] Re: [Fujitsu LIFEBOOK U772] WARNING: at /build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:1028 intel_wait_for_pipe_off+0xe2/0x1a0 [i915]()

2014-01-22 Thread Bryce Harrington

[   20.095355] [ cut here ]
[   20.095385] WARNING: at 
/build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:1028 
intel_wait_for_pipe_off+0xe2/0x1a0 [i915]()
[   20.095387] Hardware name: 
[   20.095388] pipe_off wait timed out
[   20.095390] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek 
nfsv4(F) parport_pc(F) ppdev(F) bnep rfcomm bluetooth binfmt_misc(F) nfsd(F) 
auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) coretemp 
kvm_intel kvm ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) xts(F) lrw(F) 
gf128mul(F) ablk_helper(F) cryptd(F) snd_hda_intel snd_hda_codec snd_hwdep(F) 
snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) 
snd_rawmidi(F) snd_seq(F) i915 snd_seq_device(F) snd_timer(F) video(F) 
drm_kms_helper gpio_ich snd(F) drm soundcore(F) lpc_ich mac_hid psmouse(F) 
microcode(F) serio_raw(F) i2c_algo_bit mei lp(F) parport(F) hid_generic usbhid 
hid firewire_ohci firewire_core ahci(F) libahci(F) crc_itu_t(F) e1000e(F)
[   20.095440] Pid: 1194, comm: Xorg Tainted: GF3.8.0-19-generic 
#29-Ubuntu
[   20.095442] Call Trace:
[   20.095455]  [] warn_slowpath_common+0x7f/0xc0
[   20.095456]  [] warn_slowpath_fmt+0x4c/0x50
[   20.095463]  [] intel_wait_for_pipe_off+0xe2/0x1a0 [i915]
[   20.095469]  [] intel_disable_pipe+0x116/0x190 [i915]
[   20.095475]  [] ironlake_crtc_disable+0xdb/0x880 [i915]
[   20.095483]  [] ? drm_mode_create+0x4c/0x80 [drm]
[   20.095489]  [] intel_set_mode+0x36b/0xa30 [i915]
[   20.095496]  [] intel_crtc_set_config+0x716/0x950 [i915]
[   20.095502]  [] drm_mode_setcrtc+0x121/0x5a0 [drm]
[   20.095507]  [] drm_ioctl+0x4e9/0x5b0 [drm]
[   20.095513]  [] ? drm_mode_setplane+0x370/0x370 [drm]
[   20.095516]  [] do_vfs_ioctl+0x99/0x570
[   20.095517]  [] sys_ioctl+0x91/0xb0
[   20.095521]  [] system_call_fastpath+0x1a/0x1f
[   20.095522] ---[ end trace cf98203b2e7bf046 ]---

Looks like I'm getting this same stacktrace, on a PC with fresh 13.04
installed, booted with dual heads.

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

Title:
  [Fujitsu LIFEBOOK U772] WARNING: at
  /build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:1028
  intel_wait_for_pipe_off+0xe2/0x1a0 [i915]()

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I get the following warning in the dmesg:

  [   19.016094] WARNING: at
  /build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:1028
  intel_wait_for_pipe_off+0xe2/0x1a0 [i915]()

  Also newer kernel from kernel ppa gives this warning.

  I dont know if this is related but sometimes after a reboot during
  booting I get the following stuck message and X doesn't start then.

  May 24 14:28:27 kernel: [4.217459] [drm:intel_cpt_verify_modeset]
  *ERROR* mode set failed: pipe 0 stuck

  Full warning:

  [   19.016055] [ cut here ]
  [   19.016094] WARNING: at 
/build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:1028 
intel_wait_for_pipe_off+0xe2/0x1a0 [i915]()
  [   19.016096] Hardware name: LIFEBOOK U772
  [   19.016097] pipe_off wait timed out
  [   19.016097] Modules linked in: dm_crypt(F) ip6table_filter(F) 
ip6_tables(F) iptable_filter(F) ip_tables(F) ebtable_nat(F) ebtables(F) 
x_tables(F) deflate(F) zlib_deflate(F) ctr(F) twofish_generic(F) 
twofish_avx_x86_64(F) twofish_x86_64_3way(F) twofish_x86_64(F) 
twofish_common(F) camellia_generic(F) camellia_aesni_avx_x86_64(F) 
camellia_x86_64(F) serpent_avx_x86_64(F) serpent_sse2_x86_64(F) 
serpent_generic(F) glue_helper(F) blowfish_generic(F) blowfish_x86_64(F) 
blowfish_common(F) cast5_avx_x86_64(F) cast5_generic(F) cast_common(F) 
des_generic(F) xcbc(F) rmd160(F) crypto_null(F) af_key(F) xfrm_algo(F) 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev(F) tpm_infineon qmi_wwan 
hid_generic qcserial cdc_wdm usb_wwan usbnet usbserial uvcvideo kvm_intel 
videobuf2_vmalloc videobuf2_memops videobuf2_core kvm videodev 
ghash_clmulni_intel(F) usbhid hid usb_storage(F) aesni_intel(F) aes_x86_64(F) 
xts(F) lrw(F) gf128mul(F) ablk_helper(F) cryptd(F) btusb snd_hda_intel 
snd_hda_codec snd_hwdep(F) snd_pcm(F) tpm_tis snd_page_alloc(F) arc4(F) 
snd_seq_midi(F) snd_seq_midi_event(F) microcode(F) iwldvm psmouse(F) 
serio_raw(F) mac80211 snd_rawmidi(F) snd_seq(F) iwlwifi snd_seq_device(F) 
snd_timer(F) cfg80211 fujitsu_laptop mac_hid rtsx_pci_ms snd(F) i915 memstick 
parport_pc(F) lpc_ich video(F) drm_kms_helper ppdev(F) drm mei soundcore(F) 
i2c_algo_bit rfcomm bnep bluetooth coretemp lp(F) parport(F) binfmt_misc(F) 
nls_iso8859_1(F) rtsx_pci_sdmmc ahci(F) libahci(F) e1000e(F) rtsx_pci
  [   19.016144] Pid: 1784, comm: Xorg Tainted: GF   W3.8.0-22-generic 
#33-Ubuntu
  [   19.016145] Call Trace:
  [   19.016149]  [] warn_slowpath_common+0x7f/0xc0
  [   19.016151]  [] warn_slowpath_fmt+0x4c/0x50
  [   19.016163]  [] intel_wait_fo

[Kernel-packages] [Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Ethernet on USB3 port, dmesg flooded with errors

2014-01-22 Thread Christopher M. Penalver

gouri, the issue you are reporting is an upstream one. Could you please
report this problem through the appropriate channel by following the
instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel
?

Please provide a direct URL to your e-mail to the mailing list once you
have made it so that it may be tracked.

Thank you for your understanding.

** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-3.13

** Summary changed:

- 0b95:1790 [Asus N55SF] Bad performance of Ethernet on USB3 port, dmesg 
flooded with errors
+ 0b95:1790 [Asus N55SF] Bad performance of Ethernet-to-USB device on USB3 
port, dmesg flooded with errors

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

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

Title:
  0b95:1790 [Asus N55SF] Bad performance of Ethernet-to-USB device on
  USB3 port, dmesg flooded with errors

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in
  USB3 port yields slow performance, dmesg flooded with errors. Plugging
  on USB2 port, exact same situation otherwise, works well. This is
  reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the
  left, 2 USB2 ports on the right.

  ### When working (USB2 port)
  * ethernet auto-negociation is fast
  * mii-tool is fast (typical 0.05s)
  * few lines in dmesg
  * good performance

  ### When failing :
  * ethernet auto-negociation fails, then sometimes eventually works
  * mii-tool is slow (10s of seconds instead of 0.05s)

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m40.014s
  user  0m0.013s
  sys   0m0.006s

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m50.015s
  user  0m0.011s
  sys   0m0.011s

  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m10.051s
  user  0m0.000s
  sys   0m0.012s

  But on some attempts mii-tool is fast...
  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m0.057s
  user  0m0.011s
  sys   0m0.012s

  * DHCP eventually completes (after about 30 seconds) then ethernet works.
  * whole system behaviour feels a little sluggish (not very clear, though)
  * mii-tool still slow (10s of seconds instead of 0.05s)

  ## dmesg when failing

  Full dmesg attached.

  Specific lines with occurrence count at random point (obtained with
  "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ).

   50 ei_me :00:16.0: reset: wrong host start response
   51 ei_me :00:16.0: reset: unexpected enumeration response hbm.
   60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING
  141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Another attempt

   11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
   61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
   61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1
  925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD

    5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110
    6 net_ratelimit: 31 callbacks suppressed
    9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
   10 net_ratelimit: 30 callbacks suppressed
   14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
  232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd 000

[Kernel-packages] [Bug 1251065]

2014-01-22 Thread Daniel-ffwll

(In reply to comment #22)
> I tried today's  drm-intel-nightly  and all I get is a black screen,
> spinning CPU and I can't ssh in to see what's happening.

Ville went right away and created another regression in the load detect
code ;-) Patch should get merged soon.

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

Title:
  HP Mini 1000 fails to resume from suspend

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

Bug description:
  Booting various kernels including the mainline 3.12 kernel, HP Mini
  1000 does not resume from suspend. Problem seems to have begun
  following update to 13.10, including kernels 3.9, 3.10, 3.11.

  Ran steps on DebuggingKernelSuspend wiki page at
  https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume-
  trace.22_debugging_procedure_for_finding_buggy_drivers.

  Attached: dmesg.txt
  --- 
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  saucy
  Uname: Linux 3.12.0-031200-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Kernel-packages] [Bug 984127] Re: Hard drive ATA errors with latest 12.04 kernel

2014-01-22 Thread Christopher M. Penalver

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

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

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

Title:
  Hard drive ATA errors with latest 12.04 kernel

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  I started having freeze up/slow downs and very high loads. I'm not 100% sure 
this isn't a hardware related problem but my limited testing with the windows 
partition has not indicated the same issues. Here is the log from dmesg
  [  113.352633] ata1: EH complete
  [  303.840313] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0xd action 0x6 
frozen
  [  303.840459] ata1: SError: { PHYRdyChg CommWake 10B8B }
  [  303.840555] ata1.00: failed command: READ FPDMA QUEUED
  [  303.840656] ata1.00: cmd 60/20:00:00:84:71/00:00:3a:00:00/40 tag 0 ncq 
16384 in
  [  303.840660]  res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  303.840907] ata1.00: status: { DRDY }
  [  303.840975] ata1.00: failed command: READ FPDMA QUEUED
  [  303.841074] ata1.00: cmd 60/08:08:60:08:40/00:00:07:00:00/40 tag 1 ncq 
4096 in
  [  303.841077]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  303.841327] ata1.00: status: { DRDY }
  [  303.841395] ata1.00: failed command: READ FPDMA QUEUED
  [  303.841493] ata1.00: cmd 60/08:10:e8:d4:c5/00:00:23:00:00/40 tag 2 ncq 
4096 in
  [  303.841496]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  303.841741] ata1.00: status: { DRDY }
  [  303.841813] ata1: hard resetting link
  [  304.332326] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [  304.344513] ata1.00: configured for UDMA/133
  [  304.360371] ata1.00: device reported invalid CHS sector 0
  [  304.360382] ata1.00: device reported invalid CHS sector 0
  [  304.360388] ata1.00: device reported invalid CHS sector 0
  [  304.360410] ata1: EH complete
  [  937.824322] ata1.00: exception Emask 0x0 SAct 0x1fff SErr 0xd 
action 0x6 frozen
  [  937.824336] ata1: SError: { PHYRdyChg CommWake 10B8B }
  [  937.824346] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824361] ata1.00: cmd 61/00:00:00:7f:cc/01:00:09:00:00/40 tag 0 ncq 
131072 out
  [  937.824364]  res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824372] ata1.00: status: { DRDY }
  [  937.824378] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824391] ata1.00: cmd 61/48:08:00:c3:cc/00:00:09:00:00/40 tag 1 ncq 
36864 out
  [  937.824394]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824401] ata1.00: status: { DRDY }
  [  937.824407] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824419] ata1.00: cmd 61/08:10:18:a9:17/00:00:00:00:00/40 tag 2 ncq 
4096 out
  [  937.824422]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824429] ata1.00: status: { DRDY }
  [  937.824435] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824447] ata1.00: cmd 61/08:18:f0:35:20/00:00:3c:00:00/40 tag 3 ncq 
4096 out
  [  937.824450]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824456] ata1.00: status: { DRDY }
  [  937.824462] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824474] ata1.00: cmd 61/08:20:f8:4b:14/00:00:00:00:00/40 tag 4 ncq 
4096 out
  [  937.824477]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824484] ata1.00: status: { DRDY }
  [  937.824490] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824502] ata1.00: cmd 61/80:28:c8:84:cc/00:00:09:00:00/40 tag 5 ncq 
65536 out
  [  937.824505]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824511] ata1.00: status: { DRDY }
  [  937.824517] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824529] ata1.00: cmd 61/08:30:d8:49:20/00:00:00:00:00/40 tag 6 ncq 
4096 out
  [  937.824532]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824539] ata1.00: status: { DRDY }
  [  937.824545] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.824557] ata1.00: cmd 61/08:38:60:18:80/00:00:00:00:00/40 tag 7 ncq 
4096 out
  [  937.824560]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
  [  937.824566] ata1.00: status: { DRDY }
  [  937.824572] ata1.00: failed command: WRITE FPDMA QUEUED
  [  937.82

[Kernel-packages] [Bug 1268669] Re: Lenovo T440p (Haswell/NVidia optimus gfx) flaky unless I blacklist nouveau

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

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

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

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


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

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

Title:
  Lenovo T440p (Haswell/NVidia optimus gfx) flaky unless I blacklist
  nouveau

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I have a new Lenovo T440p laptop, which has a Haswell CPU and NVidia
  GPU in an "optimus" setup.  In a default 14.04 install, the system is
  quite flaky: suspend doesn't work and doing lspci apparently corrupts
  memory (the system hits random weird failures and then freezes about
  10 seconds after running lspci).  If I blacklist the nouveau module
  then the system seems to work fine (suspend/resume is good and lspci
  doesn't cause problems).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-2-generic 3.13.0-2.17
  ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
  Uname: Linux 3.13.0-2-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 2111 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 13 09:35:00 2014
  HibernationDevice: RESUME=UUID=af5ffc5d-f07d-48f1-8bab-636acd0359be
  InstallationDate: Installed on 2014-01-11 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
  MachineType: LENOVO 20ANCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-2-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug splash quiet drm.debug=0xe
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-2-generic N/A
   linux-backports-modules-3.13.0-2-generic  N/A
   linux-firmware1.121
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET43WW (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET43WW(1.18):bd12/04/2013:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1257501] Re: package linux-image-3.12.0-5-generic 3.12.0-5.13 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de erro

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

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

Title:
  package linux-image-3.12.0-5-generic 3.12.0-5.13 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 1

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  upgrading from Ubuntu Saucy to Ubuntu Trusty (development branch)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-5-generic 3.12.0-5.13
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  AptOrdering:
   linux-image-3.12.0-5-generic: Configure
   linux-image-extra-3.12.0-5-generic: Configure
   linux-image-generic: Configure
   linux-generic: Configure
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elhoir 3168 F pulseaudio
   /dev/snd/pcmC0D0c:   elhoir 3168 F...m pulseaudio
   /dev/snd/pcmC0D0p:   elhoir 3168 F...m pulseaudio
  Date: Tue Dec  3 22:58:45 2013
  DuplicateSignature: package:linux-image-3.12.0-5-generic:3.12.0-5.13:el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  HibernationDevice: RESUME=/dev/sda5
  InstallationDate: Installed on 2012-03-07 (636 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: ASUSTeK Computer INC. K50AF
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=cc60ee34-91c9-41a2-aaa2-d550098d29ff ro 
crashkernel=384M-2G:64M,2G-:128M splash nopat quiet radeon.dpm=1 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions: grub-pc 2.00-19ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.12.0-5-generic 3.12.0-5.13 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: Upgraded to trusty on 2013-10-05 (59 days ago)
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 213
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K50AF
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr213:bd07/21/2010:svnASUSTeKComputerINC.:pnK50AF:pvr1.0:rvnASUSTeKComputerINC.:rnK50AF:rvr1.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
  dmi.product.name: K50AF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Kernel-packages] [Bug 1268906] Re: cpu soft lockup running kvm

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when this regression was introduced.
If this is a regression, we can perform a kernel bisect to identify the
commit that introduced the problem.


** Tags added: kernel-da-key

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

Title:
  cpu soft lockup running kvm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “qemu-kvm” package in Ubuntu:
  New

Bug description:
  Ran twice - first time running kvm killed my system. The second time,
  I just got lots of kernel oops messages in dmesg.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-2-generic 3.13.0-2.17
  ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
  Uname: Linux 3.13.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  3250 F pulseaudio
   /dev/snd/controlC0:  james  3250 F pulseaudio
   /dev/snd/pcmC0D0p:   james  3250 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 14 10:29:20 2014
  HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
  InstallationDate: Installed on 2010-10-21 (1181 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: LENOVO 2516CTO
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-2-generic N/A
   linux-backports-modules-3.13.0-2-generic  N/A
   linux-firmware1.121
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1268833] Re: Wireless not working in 13.10 and 14.04 for rtl8192ce (RTL8188CE)/asus pce-n15

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

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

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

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


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

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

Title:
  Wireless not working in 13.10 and 14.04 for rtl8192ce (RTL8188CE)/asus
  pce-n15

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  in ubuntu / kubuntu 13.10/14.04 with kernel version lower than 3.12
  network manager asks the wifi password again and again.

  using the kernel 3.13rc7 or higher connection is successful, but no
  access to internet or the router, the ping command is not responding.

  obed@Kubuntu:~$ sudo lshw -C net
  [sudo] password for obed:
    *-network
     description: Ethernet interface
     product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:07:00.0
     logical name: eth0
     version: 06
     serial: 8c:89:a5:2a:27:e2
     size: 100Mbit/s
     capacity: 1Gbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 
ip=192.168.1.65 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
     resources: irq:51 ioport:d000(size=256) memory:d0004000-d0004fff 
memory:d000-d0003fff
    *-network
     description: Wireless interface
     product: RTL8188CE 802.11b/g/n WiFi Adapter
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlan0
     version: 01
     serial: f4:6d:04:a2:9f:dd
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=rtl8192ce 
driverversion=3.12.0-031200-generic firmware=N/A latency=0 link=no 
multicast=yes wireless=IEEE 802.11bgn
     resources: irq:19 ioport:c000(size=256) memory:fb30-fb303fff
  obed@Kubuntu:~$
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2014-01-10 (3 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: linux (not installed)
  Tags:  saucy
  Uname: Linux 3.13.0-999-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  --- 
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kubuntu4941 F pulseaudio
   /dev/snd/controlC2:  kubuntu4941 F pulseaudio
   /dev/snd/controlC1:  kubuntu4941 F pulseaudio
  CasperVersion: 1.336ubuntu1
  DistroRelease: Ubuntu 13.10
  LiveMediaBuild: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  MachineType: MSI MS-7681
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  saucy
  Uname: Linux 3.11.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/31/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68A-GD65 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.ve

[Kernel-packages] [Bug 1268880] Re: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:

v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/
If v3.12 final does not exhibit the bug, we should move on to testing some of 
the v3.13 release candidates.

v3.13-rc3: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-rc3-trusty/

If v3.13-rc3 does not exhibit the bug then test v3.13-rc6:
v3.13-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/

If v3.13-rc3 does exhibit the bug then test v3.13-rc2:
v3.13-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc2-trusty

You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!

** Tags added: performing-bisect

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

Title:
  unable to toggle microphone mute on T410 / unable to unload
  thinkpad_acpi module

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I recently pressed the physical microphone mute button on my Lenovo
  T410. However, I am now unable to unmute it. The orange light next to
  the mic mute button comes on when the kernel boots, but pressing it
  has no effect.

  Possibly related to this, I am now unable to unload the thinkpad_acpi
  kernel module (required to run the fan in disengaged mode to work
  around the long-standing bug 751689) as it seems to be permanently
  hooked into the sound drivers:

  $ sudo modprobe -r thinkpad_acpi
  modprobe: FATAL: Module thinkpad_acpi is in use.
  $ sudo lsmod|grep thinkpad_acpi
  thinkpad_acpi  69003  1 
  nvram  14027  1 thinkpad_acpi
  snd60871  23 
snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi
  $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi 
snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel 
thinkpad_acpi snd_seq_device snd_seq_midi
  modprobe: FATAL: Module thinkpad_acpi is in use.
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-2-generic 3.13.0-2.17
  ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
  Uname: Linux 3.13.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  3261 F pulseaudio
   /dev/snd/controlC0:  james  3261 F pulseaudio
   /dev/snd/pcmC0D0p:   james  3261 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 14 08:52:57 2014
  HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
  InstallationDate: Installed on 2010-10-21 (1181 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: LENOVO 2516CTO
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-2-generic N/A
   linux-backports-modules-3.13.0-2-generic  N/A
   linux-firmware1.121
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1271519] Re: Restore old recvmsg behavior after CVE-2013-7266 fix is applied

** Changed in: linux-lts-raring (Ubuntu Precise)
   Status: Invalid => Confirmed

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

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

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

Title:
  Restore old recvmsg behavior after CVE-2013-7266 fix is applied

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Confirmed
Status in “linux-lts-raring” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-lts-raring” source package in Saucy:
  Invalid

Bug description:
  After commit f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ("net: rework
  recvmsg handler msg_name and msg_namelen logic"), which fixes
  CVE-2013-7266 to CVE-2013-7271, we end up with a bug in the af_rose.

  Upstream commit f81152e35001e91997ec74a7b4e040e6ab0acccf restores the
  old behaviour in net/rose/af_rose.c and should get applied to all the
  series that got these CVEs fixed.

  break-fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c
  break-fix: f3d3342602f8bcbf37d7c46641cb9bca7618eb1c 
f81152e35001e91997ec74a7b4e040e6ab0acccf

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

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

[Kernel-packages] [Bug 1271669] Re: Move vmware related modules from extras into main kernel package

2014-01-22 Thread Stefan Bader

Came up with the same change mostly. just generically including
everything in net/vmw_vsock/*.

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

Title:
  Move vmware related modules from extras into main kernel package

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  drivers/misc/vmw_vmci/vmw_vmci.ko,
  net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko
  are currently in linux-image-extra. Due to a sync of open-vm-tools and
  an open MIR on open-vm-tools, these modules are needed in the regular
  kernel.

  Bug #1220950 open-vm-tools

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

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

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

apport information

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

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

Re: [Kernel-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2014-01-22 Thread Steve Langasek

On Wed, Jan 22, 2014 at 05:11:03PM -, Clint Byrum wrote:
> The other one is the one that would sweep up the mess we occasionally
> see when something misbehaves.

> I'd like to see Ubuntu's shutdown do more to protect against that
> failure mode.

I would, too, but I don't agree that the method he proposes actually does
this. Killing processes and unmounting devices in a loop is basically what
we do already; the key difference is that some filesystems - potentially
even including the root filesystem - may require additional daemon processes
for their operation. This is the case for example if you have network
filesystems mounted and are using NetworkManager, or if you use
gss-encrypted NFS, or iscsi. So "kill all processes and unmount all
filesystems in a loop" is not a reliable shutdown mechanism, it just moves
the problem cases somewhere that Lennart apparently isn't seeing them.

One of the problems we've seen repeatedly with trying to get clean shutdown
involves NetworkManager's child processes *being* killed while they're still
needed as part of managing the network. This is not a bug that's fixed by
killing more processes.

There may be other failure scenarios that need to be addressed. Part of the
problem has been a lack of information about what's actually holding the
root filesystem open in these cases. There's a pending merge proposal on
sysvinit that should help us gather this information.

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

Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
Confirmed
Status in “linux” package in Ubuntu:
Incomplete
Status in “network-manager” package in Ubuntu:
Triaged
Status in “upstart” package in Ubuntu:
Confirmed

Bug description:
1. Format and label a target Ext4 partion using Ubuntu 12.04
2. Install 64bit 12.10 OS using that target without reformatting it
3. Shut down
4. Boot an alternate copy of Ubuntu
5. Restart selecting the newly installed OS
6. Login then shutdown
6. Boot an alternate copy of Ubuntu
7.Fsck the newly installed OS allowing corrections to be made

Each time the the newly installed OS is executed and then shutdown,
even if execution only consists of logging on, a subsequent fsck will
FAIL.

I used Acronis True Image Home 2013 to create an image of the newly
installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
filesystem corruption 100% of the time by restoring from the image,
booting, logging on and shutting down.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: aguru 1871 F pulseaudio
/dev/snd/controlC0: aguru 1871 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Tue Oct 30 22:24:54 2012
HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
eth0 no wireless extensions.

lono wireless extensions.
MachineType: System manufacturer P5Q-E
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-17-generic N/A
linux-backports-modules-3.5.0-17-generic N/A
linux-firmware1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only Filesystem

2014-01-22 Thread Axel Pospischil

** Summary changed:

- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only
Filesystem

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

- Ubuntu 14 04 LTS (acutal development branch)
- linux-image-generic v. 3.13.x, mainline kernel 3.13.x (first testing the
standard kernel), last 3.12 mainline kernel
- lvm with trim support (batched discard)
- tlp (currently disabled for testing purpose)

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

The SSD randomly freezes with the following errors:
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
ata1.00: irq_stat 0x0800, interface fatal error
ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Probably affect other Thinkpad models too:

-
http://www.sevenforums.com/bsod-help-support/309288-bsod-after-few-minutes-5-55-minutes-samsung-ssd-840-evo.html
- [GERMAN]
http://thinkpad-forum.de/threads/168841-Freezes-nach-Einbau-einer-neuen-SSD?p=1698795#post1698795
-
http://www.howtoeverything.net/linux/hardware/ubuntu-freeze-issue-after-ssd-upgrade

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

-> not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic -> 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-generic 3.13.0.3.6
ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
Uname: Linux 3.13.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: apos 3069 F pulseaudio
/dev/snd/controlC0: apos 3069 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 16 12:35:13 2014
HibernationDevice: RESUME=UUID=7290992b-11df-4d5c-a9bc-579dafe5eb61
InstallationDate: Installed on 2014-01-08 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140105)
MachineT

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1271669] Re: Move vmware related modules from extras into main kernel package

2014-01-22 Thread Stefan Bader

Modified the title so this could include multiple modules. vmxnet3 is
already in the main package, but vsock.ko and
vmw_vsock_vmci_transport.ko are not but likely should. There is a vmwgfx
driver, too but the target is probably more  server type which does not
need accelerated gfx. Also right now there is no other drm driver in the
main package.

** Summary changed:

- move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to 
linux-image-virtual
+ Move vmware related modules from extras into main kernel package

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

Title:
  Move vmware related modules from extras into main kernel package

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  drivers/misc/vmw_vmci/vmw_vmci.ko,
  net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko
  are currently in linux-image-extra. Due to a sync of open-vm-tools and
  an open MIR on open-vm-tools, these modules are needed in the regular
  kernel.

  Bug #1220950 open-vm-tools

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

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

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1271540] Re: Random "Watchdog detected hard lockup" when resuming from suspend

I run the requested command so the missing logs are now attached to this bug.
Please feel free to ask more logs if needed

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1269717] Re: shutdown now does not shutdown

Did this issue occur in a previous version of Ubuntu, or is this a new
issue?

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

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

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

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.


[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/


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

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

Title:
  shutdown now does not shutdown

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  when typing in sudo shutdown now in a terminal, instead of shutting
  down, the computer shows a root prompt and never shuts down.

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

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

[Kernel-packages] [Bug 1268252] Re: Brightness settings stopped working after upgrade

** Tags added: needs-bisect

** Also affects: linux (Ubuntu Trusty)
   Importance: Medium
   Status: Confirmed

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

Title:
  Brightness settings stopped working after upgrade

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

Bug description:
  I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, 
both the physical key and the brightness settings in the gnome-control centre 
have stopped working. Whatever level of brightness i decrease it to, it always 
stays on maximum.
  I'm able to reproduce this only on kernel 3.13. Works as its supposed to on 
kernel 3.12

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu50
  ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
  Uname: Linux 3.13.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 12 09:17:00 2014
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2013-11-16 (56 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago)
  --- 
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  krishnan   3070 F pulseaudio
   /dev/snd/controlC0:  krishnan   3070 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c545b9da-fef4-4530-9051-29276dfd842c
  InstallationDate: Installed on 2013-11-16 (58 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO INVALID
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 simple
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic 
root=UUID=0b897d24-0c02-4f57-9596-5fcd681c5ed0 ro quiet splash nomodeset 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-2-generic N/A
   linux-backports-modules-3.13.0-2-generic  N/A
   linux-firmware1.121
  StagingDrivers: rts5139
  Tags:  trusty staging
  Uname: Linux 3.13.0-2-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-01-06 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83CN12WW(V1.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G505s
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G505s
  dmi.modalias: 
dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo G505s
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1263301] Re: Sinus 154 data II Wifi Adapter does not work

** Tags removed: trusty
** Tags added: saucy

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

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

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

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

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

Title:
  Sinus 154 data II Wifi Adapter does not work

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

Bug description:
  USB ID for the mentioned Wifi Usb adapter seems to be missing in the
  p54usb driver, so i need to recompile p54usb.c for each PC i setup or
  after every kernel update.

  can you please add the USB ID to the ubuntu/lubuntu/xubuntu kernel ?

  3.13-rc4, 3.12.6, 3.11.10, 3.4.75, 3.2.53 and 3.0.101 do all have
  support for this device

  despite other reports, this older device is wpa2 capable, it`s only a
  matter of the correct firmware if it works with recent wifi networks.

  https://lkml.org/lkml/2013/1/13/100

  from: Tomasz Guszkowski 

  commit 3194b7fcdf6caea338b5d2c72d76fed80437649c upstream.

  Added USB ID for T-Com Sinus 154 data II.

  Signed-off-by: Tomasz Guszkowski 
  Acked-by: Christian Lamparter 
  Signed-off-by: John W. Linville 
  Signed-off-by: Ben Hutchings 
  ---
   drivers/net/wireless/p54/p54usb.c |1 +
   1 file changed, 1 insertion(+)
  diff --git a/drivers/net/wireless/p54/p54usb.c 
b/drivers/net/wireless/p54/p54usb.c
  index e71c702..64b944b 100644
  --- a/drivers/net/wireless/p54/p54usb.c
  +++ b/drivers/net/wireless/p54/p54usb.c
  @@ -82,6 +82,7 @@ static struct usb_device_id p54u_table[] = {
{USB_DEVICE(0x06a9, 0x000e)},   /* Westell 802.11g USB (A90-211WG-01) */
{USB_DEVICE(0x06b9, 0x0121)},   /* Thomson SpeedTouch 121g */
{USB_DEVICE(0x0707, 0xee13)},   /* SMC 2862W-G version 2 */
  + {USB_DEVICE(0x083a, 0x4503)},   /* T-Com Sinus 154 data II */
{USB_DEVICE(0x083a, 0x4521)},   /* Siemens Gigaset USB Adapter 54 
version 2 */
{USB_DEVICE(0x083a, 0xc501)},   /* Zoom Wireless-G 4410 */
{USB_DEVICE(0x083a, 0xf503)},   /* Accton FD7050E ver 1010ec  */

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

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

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1267712] Re: ubuntu guest's file system becoming read only

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  ubuntu guest's file system becoming read only

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  9.3.189.114 (root/.pasroot) (Host Machine)
  Run the follwoing command to go to the guest victim machine from 
(/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G
  -nographic -nodefaults -monitor stdio -serial pty -append
  "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic
  -device spapr-vscsi -device spapr-
  vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev
  bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-
  ppc64el.img.qcow2

  after this command you will get the screen number.
  example:

  QEMU 1.6.0 monitor - type 'help' for more information
  (qemu) char device redirected to /dev/pts/16 (label serial0)

  Then open another host session and execute the below command

  # screen /dev/pts/16
  (qemu)

  Here the screen number is /dev/pts/16

  -->>Then you will get a blank screen so press ENTER key.

  The guest machine login: ubuntu/passw0rd

  Then do --->sudo -i

  Environment:
  ===
  Host: Power8
  Guest : ubuntu hosted on Power8

  The issue:
  ==
  After logging into the guest some times it becomes read - only file system.

  Description:
  ===

  Here i am not able to create directory or a file.

  root@ubuntu:/opt/ltp# cat /etc/issue
  Ubuntu Trusty Tahr (development branch) \n \l=>>ubuntu 
guest

  root@ubuntu:~# ifconfig
  eth0  Link encap:Ethernet  HWaddr 6c:ae:8b:69:16:15
inet addr:192.168.122.131  Bcast:192.168.122.255  Mask:255.255.255.0
inet6 addr: fe80::6eae:8bff:fe69:1615/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:72 errors:0 dropped:4 overruns:0 frame:0
TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6764 (6.7 KB)  TX bytes:3914 (3.9 KB)
Interrupt:22

  loLink encap:Local Loopback
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  
  root@ubuntu:/opt/ltp# ./runltp -f timers -p -l timers.log -o timers.out
  cat: /opt/ltp/Version: No such file or directory
  INFO: creating /opt/ltp/results directory
  mktemp: failed to create directory via template â/tmp/ltp-XXâ: 
Read-only file system==>>error
  FATAL: Unable to make temporary directory:

  root@ubuntu:/opt/ltp# df -k
  Filesystem 1K-blocksUsed Available Use% Mounted on
  /dev/sda51573372 1303052  47632556   3% /
  none   4   0 4   0% /sys/fs/cgroup
  devtmpfs 5161908 296   5161612   1% /dev
  none 1032440 184   1032256   1% /run
  none5120   0  5120   0% /run/lock
  none 5162192   0   5162192   0% /run/shm
  none  102400   0102400   0% /run/user

  root@ubuntu:/opt/ltp# mkdir -m 777 jagan
  mkdir: cannot create directory âjaganâ: Read-only file system>>error

  root@ubuntu:/opt/ltp# touch jagan
  touch: cannot touch âjaganâ: Read-only file system>>error

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

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

[Kernel-packages] [Bug 1269404] Re: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:546]

Does the linux-image package install?  That is the only one you should
need to test.  No need to install the headers package.

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

Title:
  BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:546]

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

Bug description:
  I'm using Ubuntu 14.04 Trusty Tahr 64 bit and my laptop (Dell XPS
  L702x using Nvidia Optimus) can't boot starting with kernel  3.13
  (I've tried all three updates: 3.13.0-1-generic, 3.13.0-2-generic and
  3.13.0-3-generic). When booting, I get this error: "BUG: soft lockup -
  CPU#2 stuck for 22s! [systemd-udevd:546]"

  Booting the old 3.12 (3.12.0-8-generic) kernel works.

  Here's the relevant part from syslog:

  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136613] BUG: soft lockup - 
CPU#2 stuck for 22s! [systemd-udevd:546]
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136638] Modules linked in: 
parport_pc ppdev rfcomm bnep uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core btusb videodev bluetooth snd_hda_codec_hdmi 
snd_hda_codec_realtek binfmt_misc joydev ip6t_REJECT xt_hl ip6t_rt 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG xt_limit xt_tcpudp 
xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 nvidia(POF) xt_conntrack 
ip6table_filter dell_wmi sparse_keymap ip6_tables nf_conntrack_netbios_ns arc4 
nf_conntrack_broadcast snd_hda_intel nf_nat_ftp nf_nat snd_hda_codec 
nf_conntrack_ftp nf_conntrack intel_rapl iwldvm iptable_filter snd_hwdep 
x86_pkg_temp_thermal dell_laptop ip_tables intel_powerclamp dcdbas snd_pcm 
mac80211 x_tables kvm_intel snd_page_alloc kvm snd_seq_midi snd_seq_midi_event 
snd_rawmidi i915 snd_seq crct10dif_pclmul crc32_pclmul iwlwifi 
ghash_clmulni_intel snd_seq_device aesni_intel snd_timer aes_x86_64 lrw 
gf128mul cfg80211 glue_helper ablk_helper drm_kms_helper snd cryptd mei_me drm 
mei i2c_algo_bit psmouse soundcore wmi lpc_ich serio_raw mac_hid video coretemp 
lp parport hid_generic usbhid hid microcode ahci r8169 libahci mii
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136678] CPU: 2 PID: 546 Comm: 
systemd-udevd Tainted: PF   W  O 3.13.0-3-generic #18-Ubuntu
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136679] Hardware name: Dell 
Inc.  Dell System XPS L702X/0XN71K, BIOS A18 06/18/2012
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136681] task: 880423d5e000 
ti: 880036b4a000 task.ti: 880036b4a000
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136682] RIP: 
0010:[]  [] 
smp_call_function_many+0x268/0x2d0
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136687] RSP: 
0018:880036b4bb78  EFLAGS: 0202
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136688] RAX: 0006 
RBX: 880036b4bb28 RCX: 88043e5981d0
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136689] RDX: 0006 
RSI: 0100 RDI: 
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136690] RBP: 880036b4bbc8 
R08: 88043e495348 R09: 0004
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136691] R10: 88043e495348 
R11: 29312e312e312820 R12: 81362dd4
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136692] R13: 880036b4bb40 
R14: 81ec810d R15: 81a5ef2d
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136693] FS:  
7f192e8ca880() GS:88043e48() knlGS:
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136694] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136695] CR2: 00f76068 
CR3: 36935000 CR4: 000407e0
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136697] Stack:
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136697]  88043e495368 
00015300  81059da0
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136700]  0101 
011b 81059da0 
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136702]  88043e5d08a8 
88043e5d0808 880036b4bbf0 810d9a8d
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136704] Call Trace:
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136708]  [] ? 
flush_tlb_func+0xc0/0xc0
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136710]  [] ? 
flush_tlb_func+0xc0/0xc0
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136712]  [] 
on_each_cpu+0x2d/0x60
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136715]  [] 
flush_tlb_kernel_range+0x4a/0x70
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136719]  [] 
__purge_vmap_area_lazy+0x335/0x430
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136722]  [] 
vm_unmap_aliases+0x162/0x180
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136724]  [] 
change_page_attr_set_clr+0xb7/0x470
  Jan 15 14:27:05 ubuntu-desktop kernel: [   36.136726]  []

[Kernel-packages] [Bug 1267345] Re: Laptop doesn't go to sleep when lid is closed

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Laptop doesn't go to sleep when lid is closed

Status in “linux-firmware” package in Ubuntu:
  Invalid

Bug description:
  When I upgraded to linux-firmware 1.116.1 from proposed
  The sleep with lid close, the screen only goes black, and computer stays on 
with fans on etc.. so something gets stuck. Going into Power settings doesn't 
do any difference.

  But when I revert back to older linux-firmware 1.116 lid trigger and
  sleep works correctly.

  I'm on an Samsung Ativ 9 Plus with  Intel Wireless 7260
  Checking the changelog for this package, there's a firmware for 7260. so it's 
somehow blocking sleeps.

  Let me know if you need logs etc... I didn't manually find much relevant at 
all at a first look.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Dependencies:
   
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-04 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: linux-firmware 1.116.1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Tags:  saucy package-from-proposed
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Dependencies:
   
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-04 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: linux-firmware 1.116
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=sv
   TERM=xterm
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Dependencies:
   
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-04 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: linux-firmware 1.116
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=sv
   TERM=xterm
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Dependencies:
   
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-04 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: linux-firmware 1.116.1
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=sv
   TERM=xterm
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Tags:  saucy package-from-proposed
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Kernel-packages] [Bug 1271519] Re: Restore old recvmsg behavior after CVE-2013-7266 fix is applied

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

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

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

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

Title:
  Restore old recvmsg behavior after CVE-2013-7266 fix is applied

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Confirmed
Status in “linux-lts-raring” source package in Precise:
  Invalid
Status in “linux” source package in Quantal:
  New
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  New
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-lts-raring” source package in Saucy:
  Invalid

Bug description:
  After commit f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ("net: rework
  recvmsg handler msg_name and msg_namelen logic"), which fixes
  CVE-2013-7266 to CVE-2013-7271, we end up with a bug in the af_rose.

  Upstream commit f81152e35001e91997ec74a7b4e040e6ab0acccf restores the
  old behaviour in net/rose/af_rose.c and should get applied to all the
  series that got these CVEs fixed.

  break-fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c
  break-fix: f3d3342602f8bcbf37d7c46641cb9bca7618eb1c 
f81152e35001e91997ec74a7b4e040e6ab0acccf

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

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

[Kernel-packages] [Bug 1271669] Re: move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to linux-image-virtual

2014-01-22 Thread Ben Howard

** Description changed:

- drivers/misc/vmw_vmci/vmw_vmci.ko is currently in linux-image-extra. Due
- to a sync of open-vm-tools and an open MIR on open-vm-tools, this module
- is needed in the regular kernel
+ drivers/misc/vmw_vmci/vmw_vmci.ko,
+ net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are
+ currently in linux-image-extra. Due to a sync of open-vm-tools and an
+ open MIR on open-vm-tools, these modules are needed in the regular
+ kernel.
  
  Bug #1220950 open-vm-tools

** Summary changed:

- move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to 
linux-image-virtual
+ move vmware modules (vmci, vsock, vxnet) from linux-image-extra to 
linux-image-virtual

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

Title:
  move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to
  linux-image-virtual

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  drivers/misc/vmw_vmci/vmw_vmci.ko,
  net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko
  are currently in linux-image-extra. Due to a sync of open-vm-tools and
  an open MIR on open-vm-tools, these modules are needed in the regular
  kernel.

  Bug #1220950 open-vm-tools

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

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

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1271540/+attachment/3954601/+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/1271540

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

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

apport information

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

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1271540/+attachment/3954603/+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/1271540

Title:
  Random "Watchdog detected hard lockup" when resuming from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I encounter a random bug when suspending my computer : everything suspends 
properly when I press the sleep button on the keyboard, but sometimes the 
computer freezes when I wake it up (by hitting the power button). So I have to 
power off the computer by long press on the power button, or reset the computer.
  I tried to suspend with the pm-suspend command, I got the same result.
  I tried to suspend through a TTY, and here I was able to get some logs (I 
took a photo of the log, attached to this bug report).
  The error message was the watchdog detected a hard lockup on the cpu (8 core 
cpu, so I got several times the message).
  The faulty software seems to be systemd-udevd, according to the trace I got. 
I googled a bit the problem, but wasn't able to very usefull information

  I wasn't able to find anything about the message I saw on the screen
  in the log files. No record at the time of the freeze. That really
  surprised me.

  I noticed also this problem related to suspend : I use virtualbox and
  if I suspend computer, resume it and try to launch a VM after, I can't
  get it running properly : it is very slow and I have to reboot the
  compter to get it working properly. And I noticed also if I have used
  a VM and after I suspend the computer, I am almost sure I'm gonna have
  a freeze when I wake the computer up. Maybe is there something related
  ?

  This problem happens randomly but I didn't find anything to reproduce it. 
  Here is the configuration of the computer : 
  -mother board : MSI h77ma-g43
  -cpu : intel core i7 ivy bridge series
  -ram : 16 gb
  -using onboard soundcard and video card
  -1 hdd 1.5 tb on sata 3
  -another 1 tb hdd on sata 3
  -bluray/dvd burner on sata

  Using Kubuntu 13.10 x64 everything up to date.

  Does anybody get the same or a similar problem ?
  If any more information is needed, please feel free to ask.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=f11f8578-3772-463c-b3ec-e7ec4307cbe3
  InstallationDate: Installed on 2012-06-02 (599 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7756
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/disque--lvm-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (95 days ago)
  UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo 
vboxusers wireshark
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd10/29/2013:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

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