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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  BUG: unable to handle kernel paging request at 8801a1ac07f8

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Trusty Tahr 14.04 beta amd64, running in VMWare Fusion under
  MacOSX Mavericks.

  The crash happens when VMWare Fusion's VM settings have 3D graphics
  accelleration enabled. It is not needed to have full retina display
  support enabled, only 3D accelleration.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1649 F pulseaudio
zsombor2549 F pulseaudio
  Date: Fri Mar  7 08:48:56 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location kmem_cache_alloc+0x65/0x140
  Failure: oops
  HibernationDevice: RESUME=UUID=4780411a-7bc8-4f47-a9ce-acd60dd61c61
  InstallationDate: Installed on 2014-01-07 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140107)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=3174a93b-3860-4630-a07d-eb898398541e ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 8801a1ac07f8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Kernel-packages] [Bug 1289194] [NEW] BUG: unable to handle kernel paging request at ffff8801a1ac07f8

2014-03-07 Thread Zsombor Egri
Public bug reported:

Ubuntu Trusty Tahr 14.04 beta amd64, running in VMWare Fusion under
MacOSX Mavericks.

The crash happens when VMWare Fusion's VM settings have 3D graphics
accelleration enabled. It is not needed to have full retina display
support enabled, only 3D accelleration.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lightdm1649 F pulseaudio
  zsombor2549 F pulseaudio
Date: Fri Mar  7 08:48:56 2014
DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location kmem_cache_alloc+0x65/0x140
Failure: oops
HibernationDevice: RESUME=UUID=4780411a-7bc8-4f47-a9ce-acd60dd61c61
InstallationDate: Installed on 2014-01-07 (58 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140107)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=3174a93b-3860-4630-a07d-eb898398541e ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 8801a1ac07f8
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-kerneloops kernel-oops 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/1289194

Title:
  BUG: unable to handle kernel paging request at 8801a1ac07f8

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Trusty Tahr 14.04 beta amd64, running in VMWare Fusion under
  MacOSX Mavericks.

  The crash happens when VMWare Fusion's VM settings have 3D graphics
  accelleration enabled. It is not needed to have full retina display
  support enabled, only 3D accelleration.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1649 F pulseaudio
zsombor2549 F pulseaudio
  Date: Fri Mar  7 08:48:56 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location kmem_cache_alloc+0x65/0x140
  Failure: oops
  HibernationDevice: RESUME=UUID=4780411a-7bc8-4f47-a9ce-acd60dd61c61
  InstallationDate: Installed on 2014-01-07 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140107)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=3174a93b-3860-4630-a07d-eb898398541e ro 

[Kernel-packages] [Bug 1289194] Re: BUG: unable to handle kernel paging request at ffff8801a1ac07f8

2014-03-07 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  BUG: unable to handle kernel paging request at 8801a1ac07f8

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Trusty Tahr 14.04 beta amd64, running in VMWare Fusion under
  MacOSX Mavericks.

  The crash happens when VMWare Fusion's VM settings have 3D graphics
  accelleration enabled. It is not needed to have full retina display
  support enabled, only 3D accelleration.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1649 F pulseaudio
zsombor2549 F pulseaudio
  Date: Fri Mar  7 08:48:56 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location kmem_cache_alloc+0x65/0x140
  Failure: oops
  HibernationDevice: RESUME=UUID=4780411a-7bc8-4f47-a9ce-acd60dd61c61
  InstallationDate: Installed on 2014-01-07 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140107)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=3174a93b-3860-4630-a07d-eb898398541e ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 8801a1ac07f8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


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

2014-03-07 Thread dino99
** Tags added: trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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=set
   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 1289208] [NEW] [Dell Inc. Latitude E6420] suspend/resume failure [non-free: wl]

2014-03-07 Thread Raimond Hol
Public bug reported:

Happened at reboot, all worked, no issues found, just the system error.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  raimond1972 F pulseaudio
Date: Fri Mar  7 09:08:50 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=ca393250-0446-4c9e-ae79-f6cabbedabdd
InstallationDate: Installed on 2014-03-05 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140304)
InterpreterPath: /usr/bin/python3.4
MachineType: Dell Inc. Latitude E6420
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=d8f1c982-0053-46b1-bee1-5bbae198178e ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-16-generic N/A
 linux-backports-modules-3.13.0-16-generic  N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 07/11/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0K0DNP
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6420
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-kerneloops resume suspend trusty

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

Title:
  [Dell Inc. Latitude E6420] suspend/resume failure [non-free: wl]

Status in “linux” package in Ubuntu:
  New

Bug description:
  Happened at reboot, all worked, no issues found, just the system
  error.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raimond1972 F pulseaudio
  Date: Fri Mar  7 09:08:50 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=ca393250-0446-4c9e-ae79-f6cabbedabdd
  InstallationDate: Installed on 2014-03-05 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140304)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E6420
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=d8f1c982-0053-46b1-bee1-5bbae198178e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0K0DNP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  [Dell Inc. Latitude E6420] suspend/resume failure [non-free: wl]

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Happened at reboot, all worked, no issues found, just the system
  error.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raimond1972 F pulseaudio
  Date: Fri Mar  7 09:08:50 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=ca393250-0446-4c9e-ae79-f6cabbedabdd
  InstallationDate: Installed on 2014-03-05 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140304)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E6420
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=d8f1c982-0053-46b1-bee1-5bbae198178e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0K0DNP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1274479] Re: Call Traces found while executing fsracer tests

2014-03-07 Thread Abdul
Hello,

On beta1 ( ubuntu 3.13.0-14-generic),  the problem is no more
reproducible.

I repeated the similar test scenarios + a few new test scenarios. but no
more call traces are seen in dmesg

fsracer and stressaptest are running fine in parallel with no issues.

we can close this bug for now and can reopen if we see the traces again
in future.

Thanks for all your support

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

Title:
  Call Traces found while executing fsracer tests

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:

  Host machine : 9.3.189.114(roo/.pasroot)

  run virsh console harini   to get the console access

  Description:
  -

  fs racer test from ltp test suite was being run on ubuntu alpha 1
  guest.  After couple of hours of testing got some errors on the
  command prompt along with call trace in dmesg.

  Location for fsracer test : /root/ltp-
  full-20140115/testcases/kernel/fs/racer/

  Ran :

   nohup /root/ltp-full-20140115/testcases/kernel/fs/racer/fs_racer.sh
  -t 1000  

  
=
  On command prompt:
  -
  root@ubuntu:~# [88680.412397] INFO: task ln:16792 blocked for more than 120 
seconds.
  [88680.412527]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.412595] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.412992] INFO: task mkdir:16801 blocked for more than 120 seconds.
  [88680.413079]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.413145] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.413290] INFO: task dd:17882 blocked for more than 120 seconds.
  [88680.413401]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.413468] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.413625] INFO: task fs_racer_file_c:29630 blocked for more than 120 
seconds.
  [88680.413726]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.413793] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.414025] INFO: task fs_racer_file_c:29631 blocked for more than 120 
seconds.
  [88680.414127]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.414196] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.414341] INFO: task ln:29635 blocked for more than 120 seconds.
  [88680.414425]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.414491] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.414632] INFO: task ln:29637 blocked for more than 120 seconds.
  [88680.414715]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.414782] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.415139] INFO: task fs_racer_file_c:29641 blocked for more than 120 
seconds.
  [88680.415243]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.415311] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.415456] INFO: task mkdir:29646 blocked for more than 120 seconds.
  [88680.415539]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.415605] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.415748] INFO: task mkdir:29647 blocked for more than 120 seconds.
  [88680.415835]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.415983] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.

  
  ==

  Call trace:
  -

  [88680.412397] INFO: task ln:16792 blocked for more than 120 seconds.
  [88680.412527]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.412595] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [88680.412696] ln  D 3fff9b89ea68 0 16792  25258 
0x0004
  [88680.412703] Call Trace:
  [88680.412732] [c00c76ad74b0] [c00c765eeae0] 0xc00c765eeae0 
(unreliable)
  [88680.412852] [c00c76ad7680] [c00154c0] .__switch_to+0x1d0/0x340
  [88680.412917] [c00c76ad7730] [c0abd968] .__schedule+0x368/0x8c0
  [88680.412922] [c00c76ad79b0] [c0abe498] 
.schedule_preempt_disabled+0x18/0x30
  [88680.412926] [c00c76ad7a20] [c0ac078c] 
.__mutex_lock_slowpath+0x18c/0x2c0
  [88680.412930] [c00c76ad7af0] [c0ac0924] .mutex_lock+0x64/0x68
  [88680.412975] [c00c76ad7b70] [c02303e0] 
.kern_path_create+0xb0/0x1e0
  [88680.412979] [c00c76ad7cd0] [c0232a48] 
.user_path_create+0x68/0xa0
  [88680.412983] [c00c76ad7d60] [c0233c88] .SyS_symlinkat+0x78/0x140
  [88680.412989] [c00c76ad7e30] [c0009e58] syscall_exit+0x0/0x98

  

[Kernel-packages] [Bug 1269600] Re: [Macmini5, 1] Kernel Panic when using Magic Touchpad

2014-03-07 Thread Gerrit Addiks
Update #2:

The patch mentioned above solved the problem for me. The patch was
applied to the kernel in v3.14-RC4. I am now using that kernel with
14.04 for some weeks without any trouble. From my point of view, this
can be closed. I just hope 14.04 gets released with at least v3.14 so i
dont need to use a custom kernel after release.

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

Title:
  [Macmini5,1] Kernel Panic when using Magic Touchpad

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Using an Apple Magic Touchpad from 13.04 upward is not possible
  because of a kernel panic. The Touchpad also works in 12.10, but i
  prefer LTS. In 13.04 the error is triggered randomly but quickly by
  dragging on the touchpad with two fingers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
  Uname: Linux 3.13.0-3-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:

  Date: Wed Jan 15 21:48:33 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-3-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00e6]
  InstallationDate: Installed on 2014-01-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140115)
  MachineType: Apple Inc. Macmini5,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-3-generic 
root=UUID=384b5ac6-745f-45e0-a93c-f3d7e045ab6a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.name: Macmini5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.50-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Wed Jan 15 21:46:51 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 219
   vendor ACR
  xserver.version: 2:1.14.5-1ubuntu2

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

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


[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users

2014-03-07 Thread Colin King
thermald is the defacto solution to this in Trusty+, I've added a
Wikipage to describe how to install and configure this daemon:

https://wiki.ubuntu.com/Kernel/PowerManagement/ThermalIssues

I think this addresses the bug, so I'm going to close it.

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

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

Title:
  Ubuntu should handle hot CPUs by taking preemptive action and
  warning users

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  If the kernel detects your CPU(s) is/are too hot currently (see bug
  751689), the kernel calls /sbin/poweroff. This will provide a
  graceful system shutdown. If /sbin/poweroff fails, the kernel just
  forcibly shuts the system down. However, both strategies are last
  resorts and are called when the system temperature has reached a
  critical level.

  However, the kernel seems to emit an ACPI event when it detects the
  CPU(s) are merely hot. I suggest we consider adding an acpi hook to
  attempt to avoid a critical scenario.

  Currently, the user experience when critical gets hit is not good -
  the system just shuts down with no warning whatsoever. This is
  alarming in the extreme to users.

  Ideas:

  - proactively attempt to kill off power hogging processes (use powertop?)
  - ramp fans to maximum and present the user with a warning window explaining 
what is happening.
  - present the user with a window of high-power processes and ask *them* to 
select the processes they'd like to kill off in an effort
to avoid a system shutdown.

  Problems:

  - it is unclear (to me atleast) how close (in terms of degrees
  centigrade) hot and critical are (is it different for all CPUs ?)
  As such, it is unclear how long (time) it might take for a system that
  is hot to go critical and just shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: acpi-support 0.140
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 14 17:22:09 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  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/controlC1:  james  3788 F pulseaudio
   /dev/snd/controlC0:  james  3788 F pulseaudio
james 10267 F alsamixer
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,17aa214c,00100302 
HDA:14f12c06,17aa2122,0010'
 Controls  : 9
 Simple ctrls  : 6
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6IHT37WW-1.12'
 Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
 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=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: LENOVO 2516CTO
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs 
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-18-generic-pae N/A
   linux-backports-modules-3.2.0-18-generic-pae  N/A
   linux-firmware1.71
  StagingDrivers: mei
  Tags:  precise staging
  Uname: Linux 3.2.0-18-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
  

[Kernel-packages] [Bug 1289223] [NEW] [ASUSTeK Computer Inc. K53SD] suspend/resume failure

2014-03-07 Thread Karma Dorje
*** This bug is a duplicate of bug 1287587 ***
https://bugs.launchpad.net/bugs/1287587

Public bug reported:

 cat /proc/version_signature 
Ubuntu 3.13.0-16.36-generic 3.13.5

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  karma  2344 F pulseaudio
CRDA:
 country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
Date: Fri Mar  7 17:15:19 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0
InstallationDate: Installed on 2012-09-30 (523 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120817.1)
InterpreterPath: /usr/bin/python3.4
MachineType: ASUSTeK Computer Inc. K53SD
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-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-16-generic N/A
 linux-backports-modules-3.13.0-16-generic  N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure
UpgradeStatus: Upgraded to trusty on 2013-11-10 (116 days ago)
UserGroups:
 
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.

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


** Tags: amd64 apport-kerneloops resume suspend trusty

** This bug has been marked a duplicate of bug 1287587
   [ASUSTeK Computer Inc. K53SD] suspend/resume failure

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

Title:
  [ASUSTeK Computer Inc. K53SD] suspend/resume failure

Status in “linux” package in Ubuntu:
  New

Bug description:
   cat /proc/version_signature 
  Ubuntu 3.13.0-16.36-generic 3.13.5

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karma  2344 F pulseaudio
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Fri Mar  7 17:15:19 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0
  InstallationDate: Installed on 2012-09-30 (523 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120817.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: ASUSTeK Computer Inc. K53SD
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-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-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2013-11-10 (116 days ago)
  UserGroups:
   
  dmi.bios.date: 03/06/2012
  

[Kernel-packages] [Bug 1287587] Re: [ASUSTeK Computer Inc. K53SD] suspend/resume failure

2014-03-07 Thread Karma Dorje
** 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/1287587

Title:
  [ASUSTeK Computer Inc. K53SD] suspend/resume failure

Status in “linux” package in Ubuntu:
  Confirmed

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

  cat /proc/version_signature 
  Ubuntu 3.13.0-14.34-generic 3.13.5

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-14-generic 3.13.0-14.34
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karma  2367 F pulseaudio
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue Mar  4 16:00:38 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0
  InstallationDate: Installed on 2012-09-30 (520 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120817.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: ASUSTeK Computer Inc. K53SD
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-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-14-generic N/A
   linux-backports-modules-3.13.0-14-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2013-11-10 (113 days ago)
  UserGroups:
   
  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/1287587/+subscriptions

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


[Kernel-packages] [Bug 1286866] Re: BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461, period size = 2730

2014-03-07 Thread Ruben Grimm
I tried again since I figured out, that the mainline kernel did boot. It
just couldn't start GDM / the xserver.

But I could log in on the tty and the kern.log didn't show the bug
message. It is of course possible, that the bug didn't occur  because
the xserver didn't start, but maybe it is fixed upstream.

I'm not that sure, that I would change the tags to fixed-upstream, but
I thought you should know that. Maybe you can figure it out.

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

Title:
  BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461, period size = 2730

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This bug occured on Ubuntu GNOME14.04 after logging in. I didn't
  notice any strange behaviour.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-13-generic 3.13.0-13.33
  ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5
  Uname: Linux 3.13.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar  2 18:49:28 2014
  Failure: oops
  HibernationDevice: RESUME=UUID=76bd987a-c237-4475-9243-a429b1b555af
  InstallationDate: Installed on 2014-01-27 (34 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-13-generic 
root=UUID=9aa2e401-5117-48b4-93dc-36d6c24332f9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu4
  SourcePackage: linux
  Title: BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461, period size = 2730
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0310
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87-PLUS
  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.:bvr0310:bd04/07/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users

2014-03-07 Thread James Hunt
Hi Colin - thanks, yes running thermald has improved the situation
immensely! I do still very occasionally see overheats, although they are
extremely rare now and I suspect may be more related to my fans needing
a clean :-)

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

Title:
  Ubuntu should handle hot CPUs by taking preemptive action and
  warning users

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  If the kernel detects your CPU(s) is/are too hot currently (see bug
  751689), the kernel calls /sbin/poweroff. This will provide a
  graceful system shutdown. If /sbin/poweroff fails, the kernel just
  forcibly shuts the system down. However, both strategies are last
  resorts and are called when the system temperature has reached a
  critical level.

  However, the kernel seems to emit an ACPI event when it detects the
  CPU(s) are merely hot. I suggest we consider adding an acpi hook to
  attempt to avoid a critical scenario.

  Currently, the user experience when critical gets hit is not good -
  the system just shuts down with no warning whatsoever. This is
  alarming in the extreme to users.

  Ideas:

  - proactively attempt to kill off power hogging processes (use powertop?)
  - ramp fans to maximum and present the user with a warning window explaining 
what is happening.
  - present the user with a window of high-power processes and ask *them* to 
select the processes they'd like to kill off in an effort
to avoid a system shutdown.

  Problems:

  - it is unclear (to me atleast) how close (in terms of degrees
  centigrade) hot and critical are (is it different for all CPUs ?)
  As such, it is unclear how long (time) it might take for a system that
  is hot to go critical and just shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: acpi-support 0.140
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 14 17:22:09 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  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/controlC1:  james  3788 F pulseaudio
   /dev/snd/controlC0:  james  3788 F pulseaudio
james 10267 F alsamixer
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,17aa214c,00100302 
HDA:14f12c06,17aa2122,0010'
 Controls  : 9
 Simple ctrls  : 6
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6IHT37WW-1.12'
 Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
 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=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: LENOVO 2516CTO
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs 
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-18-generic-pae N/A
   linux-backports-modules-3.2.0-18-generic-pae  N/A
   linux-firmware1.71
  StagingDrivers: mei
  Tags:  precise staging
  Uname: Linux 3.2.0-18-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  

[Kernel-packages] [Bug 1272777] Re: Elantech touchpads not fully supported for some Gigabyte laptops

2014-03-07 Thread Martin Pitak
I think lightweight need to change the status to confirmed, but i bought
a mouse :D but still it annoys me most when i am typing or i am lazy to
plug in the mouse :)

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

Title:
  Elantech touchpads not fully supported for some Gigabyte laptops

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This bug report is in addition to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442 - the
  fixes suggested there (which work for others) have been tried but do
  not work for a small subset of laptops, particularly the Gigabyte
  U2442 series.

  Description of the situation for my Gigabyte U2442V most recently
  running 3.11.0-12-generic on Linux Mint.

  I tried the updated module mentioned in the above bug report (1166442). It 
compiles and it detects an Elantech trackpad of *indeterminate version*.  I get 
this in dmesg:
  [859697.496141] psmouse serio1: elantech: assuming hardware version 3 (with 
firmware version 0x450f01)
  [859697.526011] psmouse serio1: elantech: Synaptics capabilities query result 
0x58, 0x17, 0x0c.
  [859697.765917] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
  [859698.470556] psmouse serio1: elantech: retrying ps2 command 0x0b (1).

  I get no Synaptics driver functionality, and only basic touchpad
  behaviour (motion and tap-to-click for left click, no scroll or
  disabling the pad when typing, etc.).

  It seems I don't have a v9 or v10 trackpad, I've never been able to
  get a definitive indication of which version I have got.

  The only thing that has remedied this problem for me in the past was
  the one described in the original bug report (for elantech-v6 -
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64)... but it no longer applies to newer
  kernels...

  With the 3.11.0-12-generic kernel, my Touchpad *is* detected, i.e. xinput 
shows:
↳ PS/2 Elantech Touchpad id=16 [slave pointer (2)]
  and dmesg shows:
   input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input14

  There are no useful touchpads settings evident in the normal Cinnamon
  settings utility (gnome-control-center - Mouse  Touchpads).  I see a
  touchpad settings option with the gpointing-device-settings app and
  I can turn on vertical and horizontal scrolling in the interface, but
  doing so does not in any way affect that actual touchpad behaviour.

  I've also tried installing the elantech-v7 module via dkms (see 
http://ubuntuforums.org/showthread.php?t=2111236p=12850603#post12850603) and 
it compiles, but it too fails to provide the desired functionality.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=29b0358f-f728-4aea-bce5-e233816f27b1
  InstallationDate: Installed on 2013-12-11 (46 days ago)
  InstallationMedia: Linux Mint 16 petra - Release amd64 20131126
  MachineType: GIGABYTE U2442
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=83fd94b8-53eb-4e68-9eeb-cf2e017cbe0d ro quiet splash vt.handoff=7
  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:  petra
  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: 10/26/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U2442.F306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U2442
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU2442.F306:bd10/26/2012:svnGIGABYTE:pnU2442:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU2442:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: U2442
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

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


[Kernel-packages] [Bug 1276739] Re: partman-crypto uses xts by default, yet xts.ko kernel module is not present in 3.2 (original-point-zero stack) crypto-modules-udeb

2014-03-07 Thread Dimitri John Ledkov
** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: debian-installer (Ubuntu)
   Status: New = Invalid

** Changed in: debian-installer (Ubuntu Precise)
   Status: New = Triaged

** Changed in: debian-installer (Ubuntu Precise)
 Assignee: (unassigned) = Dimitri John Ledkov (xnox)

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

Title:
  partman-crypto uses xts by default, yet xts.ko kernel module is not
  present in 3.2 (original-point-zero stack) crypto-modules-udeb

Status in “debian-installer” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “partman-crypto” package in Ubuntu:
  Invalid
Status in “debian-installer” source package in Precise:
  Triaged
Status in “linux” source package in Precise:
  Fix Released
Status in “partman-crypto” source package in Precise:
  Invalid

Bug description:
  [Impact]

   * Performing automatic encrypted LVM installation using Kubuntu and
  Xubuntu 12.04.4 alternate installer images results in a failure to
  configure encrypted volumes. Please either use manual partitioning to
  create encrypted volumes with any non-default IV algorithm setting
  or use 12.04.3 media to complete the installation.

  [Error Message]
  Configuration of encrypted volumes failed.
  An error occurred while configuring encrypted volumes.
  The configuration has been aborted.

  [Cause of the bug]

   * xts.ko kernel module is missing from 3.2 crypto-modules-udeb

  [Working (older) media]

   * Kubuntu
  http://cdimages.ubuntu.com/kubuntu/releases/12.04.3/release/

   * Xubuntu
  http://cdimages.ubuntu.com/xubuntu/releases/12.04.3/release/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1276739/+subscriptions

-- 
Mailing list: https://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 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users

2014-03-07 Thread Colin King
On 07/03/14 10:23, James Hunt wrote:
 Hi Colin - thanks, yes running thermald has improved the situation
 immensely! I do still very occasionally see overheats, although they are
 extremely rare now and I suspect may be more related to my fans needing
 a clean :-)
 
One can tweak the default thermald config to start throttling back at a
lower temperature if required. So it may need some machine specific
modification if it keeps on occurring.

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

Title:
  Ubuntu should handle hot CPUs by taking preemptive action and
  warning users

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  If the kernel detects your CPU(s) is/are too hot currently (see bug
  751689), the kernel calls /sbin/poweroff. This will provide a
  graceful system shutdown. If /sbin/poweroff fails, the kernel just
  forcibly shuts the system down. However, both strategies are last
  resorts and are called when the system temperature has reached a
  critical level.

  However, the kernel seems to emit an ACPI event when it detects the
  CPU(s) are merely hot. I suggest we consider adding an acpi hook to
  attempt to avoid a critical scenario.

  Currently, the user experience when critical gets hit is not good -
  the system just shuts down with no warning whatsoever. This is
  alarming in the extreme to users.

  Ideas:

  - proactively attempt to kill off power hogging processes (use powertop?)
  - ramp fans to maximum and present the user with a warning window explaining 
what is happening.
  - present the user with a window of high-power processes and ask *them* to 
select the processes they'd like to kill off in an effort
to avoid a system shutdown.

  Problems:

  - it is unclear (to me atleast) how close (in terms of degrees
  centigrade) hot and critical are (is it different for all CPUs ?)
  As such, it is unclear how long (time) it might take for a system that
  is hot to go critical and just shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: acpi-support 0.140
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 14 17:22:09 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  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/controlC1:  james  3788 F pulseaudio
   /dev/snd/controlC0:  james  3788 F pulseaudio
james 10267 F alsamixer
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,17aa214c,00100302 
HDA:14f12c06,17aa2122,0010'
 Controls  : 9
 Simple ctrls  : 6
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6IHT37WW-1.12'
 Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
 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=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: LENOVO 2516CTO
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs 
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-18-generic-pae N/A
   linux-backports-modules-3.2.0-18-generic-pae  N/A
   linux-firmware1.71
  StagingDrivers: mei
  Tags:  precise staging
  Uname: Linux 3.2.0-18-generic-pae i686
  UpgradeStatus: Upgraded 

[Kernel-packages] [Bug 1282696] Re: hyper-v: screen corruption on resume

2014-03-07 Thread Andy Whitcroft
** Tags added: hyper-v

** Tags removed: hyper-v
** Tags added: kernel-hyper-v

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

Title:
  hyper-v: screen corruption on resume

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  d) Patch to fix screen corruption during suspend/resume of virtual machine
  https://patchwork.kernel.org/patch/3481181/

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

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


[Kernel-packages] [Bug 1287398] Re: hyper-v: frame buffer driver not loading in Generation 2 mode

2014-03-07 Thread Andy Whitcroft
** Tags added: hyper-v

** Tags removed: hyper-v
** Tags added: kernel-hyper-v

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

Title:
  hyper-v: frame buffer driver not loading in Generation 2 mode

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Hi folks,

  It appears that Hyper-V frame buffer driver may not load while booting
  on UEFI based Generation 2 VMs. The following patches address the
  problem. Please include:

  1) vmbus: use resource for hyperv mmio region
  
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=90eedf0cbe4ba2a316633d6547d331c8b30517e7

  2) Drivers: hv: vmbus: Extract the mmio information from DSDT
  
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=90f3453585479d5beb75058da46eb573ced0e6ac

  3) hyperv-fb: kick off efifb early
  
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/video/hyperv_fb.c?id=e5bb7425e5bae76c8950089a946edcba3e0540ab

  4) hyperv-fb: add support for generation 2 virtual machines.
  
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/video/hyperv_fb.c?id=9069fd54960304a7c941909cbccdf8df9c42b488

  Thanks,
  Abhishek

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

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


[Kernel-packages] [Bug 1274752] Re: Hyper-V Submissions for 14.04

2014-03-07 Thread Andy Whitcroft
** Tags added: hyper-v

** Tags removed: hyper-v
** Tags added: kernel-hyper-v

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

Title:
  Hyper-V Submissions for 14.04

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  There are a few bug fixes and features that need to be added for
  Hyper-V:

  a) Time synchronization related patch

  https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ

  (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693)

  b) Patches to ensure that kdump works correctly when multiple vCPUs
  are assigned to the virtual machine:

  https://lkml.org/lkml/2014/1/16/431
  https://lkml.org/lkml/2014/1/15/793

  (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694)

  c) Patch to use large receive side buffers. Will improve Linux VM
  networking performance:

  http://git.kernel.org/cgit/linux/kernel/git/next/linux-
  
next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3

  (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695)

  d) Patch to fix screen corruption during suspend/resume of virtual machine
  https://patchwork.kernel.org/patch/3481181/

  (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696)

  e) Patch to address Keyboard driver bug
  https://lkml.org/lkml/2014/1/11/194

  (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699)

  f) Patch for File copy from host to guest feature
  http://www.spinics.net/lists/kernel/msg1673437.html

  http://www.gossamer-threads.com/lists/linux/kernel/1869534

  (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700)

  ===
  a)
  b)
  Break-Fix: - e28bab4828354583bb66ac09021ca69b341a7db4
  Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c
  c)
  Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3
  d)
  e)
  Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6
  f)

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

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


[Kernel-packages] [Bug 1282693] Re: hyper-v: Time synchronization related patch

2014-03-07 Thread Andy Whitcroft
** Tags added: hyper-v

** Tags removed: hyper-v
** Tags added: kernel-hyper-v

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

Title:
  hyper-v: Time synchronization related patch

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  a) Time synchronization related patch

  https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ

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

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


[Kernel-packages] [Bug 1282700] Re: hyper-v: file copy host to guest support

2014-03-07 Thread Andy Whitcroft
** Tags added: hyper-v

** Tags removed: hyper-v
** Tags added: kernel-hyper-v

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

Title:
  hyper-v: file copy host to guest support

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  f) Patch for File copy from host to guest feature
  http://www.spinics.net/lists/kernel/msg1673437.html

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

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


[Kernel-packages] [Bug 1285434] Re: hyper-v: Keyboard dysfunctional while booting 14.04 Generation 2 virtual machines on Hyper-V

2014-03-07 Thread Andy Whitcroft
** Tags added: hyper-v

** Tags removed: hyper-v
** Tags added: kernel-hyper-v

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

Title:
  hyper-v: Keyboard dysfunctional while booting 14.04 Generation 2
  virtual machines on Hyper-V

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Hi folks,

  While booting in to Generation 2 virtual machine mode, I noticed that
  the keyboard stops functioning. It appears that the keyboard is
  operational during the Grub 2 menu (see attached picture) but when we
  get to the screen to select a language, the keyboard stops responding.
  Is it feasible for you to check if the Hyper-V keyboard driver has
  been included from here:

  http://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/tree/drivers/input/serio/hyperv-keyboard.c?id=HEAD

  Please let me know.
  Thanks,
  Abhishek

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

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


[Kernel-packages] [Bug 1289311] [NEW] kerneloops is waking up relatively frequently to check for kernel oops which contributes to keeping system from deep sleep

2014-03-07 Thread Colin King
Public bug reported:

Currently kerneloops is polling every 10 seconds to find a kernel oops
message.  I think this is a little excessive for something that occurs
infrequently.  How about increading the poll timeout to every 60
seconds?

** Affects: kerneloops (Ubuntu)
 Importance: Low
 Assignee: Colin King (colin-king)
 Status: In Progress

** Changed in: kerneloops (Ubuntu)
   Importance: Undecided = Low

** Changed in: kerneloops (Ubuntu)
   Status: New = In Progress

** Changed in: kerneloops (Ubuntu)
 Assignee: (unassigned) = Colin King (colin-king)

** Description changed:

  Currently kerneloops is polling every 10 seconds to find a kernel oops
  message.  I think this is a little excessive for something that occurs
- infrequently.  How about reducing this to every 60 seconds?
+ infrequently.  How about increading the poll timeout to every 60
+ seconds?

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

Title:
  kerneloops is waking up relatively frequently to check for kernel oops
  which contributes to keeping system from deep sleep

Status in “kerneloops” package in Ubuntu:
  In Progress

Bug description:
  Currently kerneloops is polling every 10 seconds to find a kernel oops
  message.  I think this is a little excessive for something that occurs
  infrequently.  How about increading the poll timeout to every 60
  seconds?

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

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


[Kernel-packages] [Bug 1275116] Re: lowlatency-flavour crashes and locks up alot

2014-03-07 Thread Jaime Pérez
I have upgraded to 14.04 again. I'll download rc5, rc4 etc

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

Title:
  lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-lowlatency” package in Ubuntu:
  Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

  I will add crashdumps when I get crashes that do not just lockup the
  machine but currently I have only seem complete lockups with 3.13

  So the essense is :

  3.11-lowlatency crashed 10 time today most of the crashes reached the console 
so I could see the panic text.
  3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. 
During next reboot it also locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2176 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 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-6-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic  N/A
   linux-firmware1.123
  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/1275116/+subscriptions

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


[Kernel-packages] [Bug 1275116] Re: lowlatency-flavour crashes and locks up alot

2014-03-07 Thread Jaime Pérez
Well, first I will test 3.13.0-16-lowlatency

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

Title:
  lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-lowlatency” package in Ubuntu:
  Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

  I will add crashdumps when I get crashes that do not just lockup the
  machine but currently I have only seem complete lockups with 3.13

  So the essense is :

  3.11-lowlatency crashed 10 time today most of the crashes reached the console 
so I could see the panic text.
  3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. 
During next reboot it also locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2176 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 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-6-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic  N/A
   linux-firmware1.123
  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/1275116/+subscriptions

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


[Kernel-packages] [Bug 1276739] Re: partman-crypto uses xts by default, yet xts.ko kernel module is not present in 3.2 (original-point-zero stack) crypto-modules-udeb

2014-03-07 Thread Dimitri John Ledkov
debian-installer rebuild against 3.2.0-60 is in precise-proposed
unapproved queue.

** Changed in: debian-installer (Ubuntu Precise)
   Status: Triaged = Fix Committed

** Changed in: debian-installer (Ubuntu Precise)
   Status: Fix Committed = In Progress

** Changed in: debian-installer (Ubuntu Precise)
   Importance: Undecided = High

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

Title:
  partman-crypto uses xts by default, yet xts.ko kernel module is not
  present in 3.2 (original-point-zero stack) crypto-modules-udeb

Status in “debian-installer” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “partman-crypto” package in Ubuntu:
  Invalid
Status in “debian-installer” source package in Precise:
  In Progress
Status in “linux” source package in Precise:
  Fix Released
Status in “partman-crypto” source package in Precise:
  Invalid

Bug description:
  [Impact]

   * Performing automatic encrypted LVM installation using Kubuntu and
  Xubuntu 12.04.4 alternate installer images results in a failure to
  configure encrypted volumes. Please either use manual partitioning to
  create encrypted volumes with any non-default IV algorithm setting
  or use 12.04.3 media to complete the installation.

  [Error Message]
  Configuration of encrypted volumes failed.
  An error occurred while configuring encrypted volumes.
  The configuration has been aborted.

  [Cause of the bug]

   * xts.ko kernel module is missing from 3.2 crypto-modules-udeb

  [Working (older) media]

   * Kubuntu
  http://cdimages.ubuntu.com/kubuntu/releases/12.04.3/release/

   * Xubuntu
  http://cdimages.ubuntu.com/xubuntu/releases/12.04.3/release/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1276739/+subscriptions

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


[Kernel-packages] [Bug 1288112] Re: kerneloops assert failure: kerneloops: dmesg.c:86: fill_lineinfo: Assertion `c9' failed.

2014-03-07 Thread Apport retracing service
*** This bug is a duplicate of bug 1026300 ***
https://bugs.launchpad.net/bugs/1026300

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1026300, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1288112/+attachment/4007839/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1288112/+attachment/4007841/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1288112/+attachment/4007842/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1288112/+attachment/4007843/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1288112/+attachment/4007844/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1288112/+attachment/4007845/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1288112/+attachment/4007846/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1026300
   kerneloops crashed with SIGABRT in __assert_fail_base()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  kerneloops assert failure: kerneloops: dmesg.c:86: fill_lineinfo:
  Assertion `c9' failed.

Status in “kerneloops” package in Ubuntu:
  New

Bug description:
  the error appears after logon

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: kerneloops-daemon 0.12+git20090217-3ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AssertionMessage: kerneloops: dmesg.c:86: fill_lineinfo: Assertion `c9' 
failed.
  Date: Wed Mar  5 09:20:06 2014
  ExecutablePath: /usr/sbin/kerneloops
  ExecutableTimestamp: 1392331929
  InstallationDate: Installed on 2014-02-19 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  ProcCmdline: /usr/sbin/kerneloops
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: kerneloops
  StacktraceTop:
   __assert_fail_base (fmt=0x7fe32ef674b8 %s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n, assertion=assertion@entry=0x403f0b c9, file=file@entry=0x403ee4 
dmesg.c, line=line@entry=86, function=function@entry=0x40420e 
fill_lineinfo) at assert.c:92
   __GI___assert_fail (assertion=0x403f0b c9, file=0x403ee4 dmesg.c, 
line=86, function=0x40420e fill_lineinfo) at assert.c:101
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: kerneloops assert failure: kerneloops: dmesg.c:86: fill_lineinfo: 
Assertion `c9' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Kernel-packages] [Bug 1289378] [NEW] rt2800 crash on skb_push, apparently underflows the skb area

2014-03-07 Thread Antti S. Lankila
Public bug reported:

I have RT2800-based 5 GHz wireless card that serves as access point with
hostapd. The hardware has served me well for years, but just yesterday
on the 6th, the system has started crashing random. The system is
headless, so I have no images of the prior crashes, but I connected up
LCD last night and when I woke up, I saw a crash on the screen which I
photographed. None of the crashes seem to be logged in dmesg. Based on
experience so far, the system crashes unpredictably, the shortest
interval that I've seen it crash is 20 minutes and the longest may be
about 10 hours. Typically it won't last more than an hour, though.

I found Tuomas Räsänen complaining about a crash that smells like the
same issue to me:
http://permalink.gmane.org/gmane.linux.drivers.rt2x00.user/2460

Tuomas mentions that the crash occurs on hostapd version 2.x only.
According to my dpkg.log, hostapd updated from version 1:1.0-3ubuntu4 to
1:2.1.0ubuntu1 on 6th 09:00, and the first hard crash was sometime
between 18:18 and 19:20 that day. I am currently running with rt2800pci
removed from kernel, which seems to have worked around the crash. My
other wlan card, ath9k, seems to produce no problems.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar  7 10:11 seq
 crw-rw 1 root audio 116, 33 Mar  7 10:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA:
 country EU:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Date: Fri Mar  7 15:47:11 2014
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
 
ProcEnviron:
 TERM=screen-256color-bce
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=f71305f7-0fa2-4521-b633-87103dab6ace ro cgroup_disable=memory 
elevator=cfq
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-16-generic N/A
 linux-backports-modules-3.13.0-16-generic  N/A
 linux-firmware 1.126
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2011-04-29 (1042 days ago)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10212-210
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-210:cvn:ct3:cvr:

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


** Tags: amd64 apport-bug trusty

** Attachment added: Digital camera shot of the oops
   
https://bugs.launchpad.net/bugs/1289378/+attachment/4011896/+files/IMG_20140307_090626.jpg

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

Title:
  rt2800 crash on skb_push, apparently underflows the skb area

Status in “linux” package in Ubuntu:
  New

Bug description:
  I have RT2800-based 5 GHz wireless card that serves as access point
  with hostapd. The hardware has served me well for years, but just
  yesterday on the 6th, the system has started crashing random. The
  system is headless, so I have no images of the prior crashes, but I
  connected up LCD last night and when I woke up, I saw a crash on the
  screen which I photographed. None of the crashes seem to be logged in
  dmesg. Based on experience so far, the system crashes unpredictably,
  the shortest interval that I've seen it crash is 20 minutes and the
  longest may be about 10 hours. Typically it won't last more than an
  hour, though.

  I found Tuomas Räsänen complaining about a crash that smells like the
  same issue to me:
  http://permalink.gmane.org/gmane.linux.drivers.rt2x00.user/2460

  Tuomas mentions that the crash occurs on hostapd version 2.x only.
  According to my dpkg.log, hostapd updated from version 1:1.0-3ubuntu4
  to 1:2.1.0ubuntu1 on 6th 09:00, and the first hard crash was sometime
  between 18:18 and 19:20 that day. I am currently running with
  rt2800pci removed from kernel, which seems to have worked around the
  crash. My other wlan card, ath9k, seems to produce no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  

Re: [Kernel-packages] [Bug 1160346] Re: do-release-upgrade from Ubuntu 12.04 on Pentium-M fails, breaks system without any warning (This kernel does not support a non-PAE CPU)

2014-03-07 Thread lampeoneon
Thanks
On Mar 3, 2014 5:40 AM, Chris Bainbridge chris.bainbri...@gmail.com
wrote:

 I'm attaching a patch for DistUpgradeQuirks.py that aborts the upgrade
 if the pae flag  is not in /proc/cpuinfo (the same check as used by the
 kernel package on install). It would be a good idea to release this fix
 before the 14.04 LTS is released in order to save thousands of people
 from ending up with a broken system when they try to upgrade from 12.04
 LTS to 14.04 LTS

 ** Patch added: update_manager_quirks_pae.patch

 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1160346/+attachment/4004690/+files/update_manager_quirks_pae.patch

 ** Tags added: patch

 ** Tags removed: quantal

 ** Tags added: pae

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1103208).
 https://bugs.launchpad.net/bugs/1160346

 Title:
   do-release-upgrade from Ubuntu 12.04 on Pentium-M fails, breaks system
   without any warning (This kernel does not support a non-PAE CPU)

 Status in linux package in Ubuntu:
   Invalid
 Status in ubuntu-release-upgrader package in Ubuntu:
   Triaged

 Bug description:
   Attempting to upgrade from Precise with a non-PAE kernel will result
   in a failed upgrade. do-release-upgrade should check whether the user
   is using a non-PAE kernel and refuse to run, rather than upgrading to
   a broken system with no installed kernel.

   After downloading 1.5GB+ of data and over 1000 new packages, the
   upgrade will eventually report failure. Looking through the logs there
   is no kernel installed because of the error This kernel does not
   support a non-PAE CPU.:

   Selecting previously unselected package linux-image-3.5.0-26-generic.^M
   Unpacking linux-image-3.5.0-26-generic (from
 .../linux-image-3.5.0-26-generic_3.5.0-26.42_i386.deb) ...^M
   This kernel does not support a non-PAE CPU.^M
   dpkg: error processing
 /var/cache/apt/archives/linux-image-3.5.0-26-generic_3.5.0-26.42_i386.deb
 (--unpack):^M
subprocess new pre-installation script returned error exit status 1^M
   No apport report written because MaxReports is reached already

   Related bugs:

   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897786 Kernel is
 dropping non-PAE flavour
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068862 upgrade
 from 12.04 to 12.10 on a sans-pae CPU leaves kernel broken

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


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

Title:
  do-release-upgrade from Ubuntu 12.04 on Pentium-M fails, breaks system
  without any warning (This kernel does not support a non-PAE CPU)

Status in Ubuntu Release Upgrader:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “ubuntu-release-upgrader” package in Ubuntu:
  Fix Released

Bug description:
  Attempting to upgrade from Precise with a non-PAE kernel will result
  in a failed upgrade. do-release-upgrade should check whether the user
  is using a non-PAE kernel and refuse to run, rather than upgrading to
  a broken system with no installed kernel.

  After downloading 1.5GB+ of data and over 1000 new packages, the
  upgrade will eventually report failure. Looking through the logs there
  is no kernel installed because of the error This kernel does not
  support a non-PAE CPU.:

  Selecting previously unselected package linux-image-3.5.0-26-generic.^M
  Unpacking linux-image-3.5.0-26-generic (from 
.../linux-image-3.5.0-26-generic_3.5.0-26.42_i386.deb) ...^M
  This kernel does not support a non-PAE CPU.^M
  dpkg: error processing 
/var/cache/apt/archives/linux-image-3.5.0-26-generic_3.5.0-26.42_i386.deb 
(--unpack):^M
   subprocess new pre-installation script returned error exit status 1^M
  No apport report written because MaxReports is reached already

  Related bugs:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897786 Kernel is 
dropping non-PAE flavour
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068862 upgrade from 
12.04 to 12.10 on a sans-pae CPU leaves kernel broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1160346/+subscriptions

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


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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  rt2800 crash on skb_push, apparently underflows the skb area

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have RT2800-based 5 GHz wireless card that serves as access point
  with hostapd. The hardware has served me well for years, but just
  yesterday on the 6th, the system has started crashing random. The
  system is headless, so I have no images of the prior crashes, but I
  connected up LCD last night and when I woke up, I saw a crash on the
  screen which I photographed. None of the crashes seem to be logged in
  dmesg. Based on experience so far, the system crashes unpredictably,
  the shortest interval that I've seen it crash is 20 minutes and the
  longest may be about 10 hours. Typically it won't last more than an
  hour, though.

  I found Tuomas Räsänen complaining about a crash that smells like the
  same issue to me:
  http://permalink.gmane.org/gmane.linux.drivers.rt2x00.user/2460

  Tuomas mentions that the crash occurs on hostapd version 2.x only.
  According to my dpkg.log, hostapd updated from version 1:1.0-3ubuntu4
  to 1:2.1.0ubuntu1 on 6th 09:00, and the first hard crash was sometime
  between 18:18 and 19:20 that day. I am currently running with
  rt2800pci removed from kernel, which seems to have worked around the
  crash. My other wlan card, ath9k, seems to produce no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:11 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country EU:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Date: Fri Mar  7 15:47:11 2014
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color-bce
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=f71305f7-0fa2-4521-b633-87103dab6ace ro cgroup_disable=memory 
elevator=cfq
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2011-04-29 (1042 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-210
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-210:cvn:ct3:cvr:

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

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


[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)

2014-03-07 Thread PierreF
If it help, I've done another change (against git hash 786235ee):

diff --git a/kernel/kthread.c b/kernel/kthread.c
index b5ae3ee..25a4780 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -298,7 +298,7 @@ struct task_struct *kthread_create_on_node(int 
(*threadfn)(void *data),
 * that thread.
 */
if (xchg(create-done, NULL))
-   return ERR_PTR(-ENOMEM);
+   return ERR_PTR(-42);
/*
 * kthreadd (or new kernel thread) will call complete()
 * shortly.


So, depending on error (-12 / -ENOMEM or -42) we could know which return 
triggered the bug.

Result is:

[   37.607981] scsi4: error handler thread failed to spawn, error = -42


To make sure the race condition do not affect which error is returned, I've 
booted 5 times that kernel. Each time I get error = -42.

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

Title:
  Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  We have recently upgraded an Dell R300 server to Trusty (was running
  fine in precise), and after upgrade it fail to boot.

  It is an issue with the SAS controller during the initilisation. It
  fail to detect the disk, we have the following error in console log:

  [   36.539955] scsi4: error handler thread failed to spawn, error = -12
  [   36.552694] mptsas: ioc0: WARNING - Unable to register controller with 
SCSI subsystem

  After this error, initramfs drop to a shell complaining that rootfs is
  not found. No disk is seen at all (cat /proc/partition only show sr0 -
  cdrom drive).

  We have this issue with two different server (both R300, both Dell SAS
  6/iR controller and same hardware).

  We don't have this issue with another Dell server (R310, Dell PERC
  H200).

  We also tester with old kernel (generic, 3.2.0-58.88), it is working.

  Those server need a greater rootdelay (probably #579572), so we have
  rootdelay=45. If we remove rootdelay=45, then disk are correctly
  recognized ! (but few second too late, initramfs dropped to a shell.
  Pressing control-D resume normal boot)

  So the issue is that with the (mandatory) rootdelay greater that 30
  (default value I think), the disk are not detected due to the error
  shown above. This is a regression since those server worked in precise
  (and work with precise old kernel).

  
  System information

  * Dell R300 with Dell SAS 6/iR controller
  * Ubuntu Trusty Tahr (14.04)
  * Running arch: x86_64
  * Kernel version: 3.13.0-7-generic  (dpkg version : 3.13.0-7.25)
  * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic 
root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 
console=ttyS1,57600 quiet
  * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 
10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  
  Attached files:

  * console output when error occure.
  * dmesg when system boot (no rootdelay, need to press control-d during 
initramfs boot)
  * lspci -vnn

  
  Tell me if you need more informations.

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

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


[Kernel-packages] [Bug 1289128] [NEW] External laptop speakers work only for several minutes then shut off

2014-03-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Linux Mint 16 Petra  Ubuntu 13.04 and 13.10
Toshiba Satellite L655-S5150
Running lates version of BIOS

I can't get my laptop speakers to stay running.

What happens is that when I first start up my laptop, sound will come out of 
the speakers for 2-3 minutes and then stop. If I reboot it will come back on 
for 2-3 minutes again. My headphones work fine for as long as I want them to 
play. I also tried the Auto Mute - disable idea that is mentioned in many of 
the posts by people with the same problem.
One weird thing is that if I close my laptop and let it go into suspend then 
open it back up, the sound comes back on for 2-3 minutes. I tested the power 
settings on this. If I have my laptop set up to go into suspend when I close 
the lid (Under the “When Plugged In” settings) , the sound comes back on. If I 
have my power setting for “When the Lid is Closed” set to “Do Nothing” (under 
the “When Plugged In” settings) and close the lid, the sound does NOT come back 
on. Same scenario if I go onto battery power (comes back on if set to suspend). 
This issue seems to be tied to the suspend / power settings somehow. Just now I 
shut the lid and re-opend it and the sound played for 1 minutes and 27 seconds 
before cutting off again.

On another note, this system is dual boot so I started up Windows and
ran Media Player for about an hour and the sound played the entire time.
This would rule out a true hardware fault.

I have run the command wget http://www.alsa-project.org/alsa-info.sh -O
alsa-info.sh  bash alsa-info.sh and saved the information locally. It
creates a folder with sub folders so I'm not sure what I should upload.

I tried installing DKMS under Mint 16 but it didn't appear to work and I
don't have Ubuntu installed on my system any longer.

I'm willing to try any troubleshooting steps you need to assist in
fixing this problem. Here is some more information below.


Info from sudo aplay -l
 List of PLAYBACK Hardware Devices 
card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
***
Output from lspci -v | grep -A7 -i audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
Subsystem: Toshiba America Info Systems Device fd50
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at d640 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 1 (rev 05) (prog-if 00 [Normal decode])

This page (https://help.ubuntu.com/community/SoundTroubleshooting) said to run 
modprobe on my sound driver. I couldn't figure out what my driver was so I was 
never able to do that step.

sudo modprobe snd-[NAME OF YOUR SOUNDCARD'S DRIVER]
**
ubuntu-bug -s audio returns the following error

*** Error: Unknown symptom

The symptom audio is not known.


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


** Tags: bot-comment
-- 
External laptop speakers work only for several minutes then shut off
https://bugs.launchpad.net/bugs/1289128
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1289128] Re: External laptop speakers work only for several minutes then shut off

2014-03-07 Thread Brian Murray
** Package changed: ubuntu = linux (Ubuntu)

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

Title:
  External laptop speakers work only for several minutes then shut off

Status in “linux” package in Ubuntu:
  New

Bug description:
  Linux Mint 16 Petra  Ubuntu 13.04 and 13.10
  Toshiba Satellite L655-S5150
  Running lates version of BIOS

  I can't get my laptop speakers to stay running.

  What happens is that when I first start up my laptop, sound will come out of 
the speakers for 2-3 minutes and then stop. If I reboot it will come back on 
for 2-3 minutes again. My headphones work fine for as long as I want them to 
play. I also tried the Auto Mute - disable idea that is mentioned in many of 
the posts by people with the same problem.
  One weird thing is that if I close my laptop and let it go into suspend then 
open it back up, the sound comes back on for 2-3 minutes. I tested the power 
settings on this. If I have my laptop set up to go into suspend when I close 
the lid (Under the “When Plugged In” settings) , the sound comes back on. If I 
have my power setting for “When the Lid is Closed” set to “Do Nothing” (under 
the “When Plugged In” settings) and close the lid, the sound does NOT come back 
on. Same scenario if I go onto battery power (comes back on if set to suspend). 
This issue seems to be tied to the suspend / power settings somehow. Just now I 
shut the lid and re-opend it and the sound played for 1 minutes and 27 seconds 
before cutting off again.

  On another note, this system is dual boot so I started up Windows and
  ran Media Player for about an hour and the sound played the entire
  time. This would rule out a true hardware fault.

  I have run the command wget http://www.alsa-project.org/alsa-info.sh
  -O alsa-info.sh  bash alsa-info.sh and saved the information
  locally. It creates a folder with sub folders so I'm not sure what I
  should upload.

  I tried installing DKMS under Mint 16 but it didn't appear to work and
  I don't have Ubuntu installed on my system any longer.

  I'm willing to try any troubleshooting steps you need to assist in
  fixing this problem. Here is some more information below.

  
  Info from sudo aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  ***
  Output from lspci -v | grep -A7 -i audio
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
Subsystem: Toshiba America Info Systems Device fd50
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at d640 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
  
  This page (https://help.ubuntu.com/community/SoundTroubleshooting) said to 
run modprobe on my sound driver. I couldn't figure out what my driver was so I 
was never able to do that step.

  sudo modprobe snd-[NAME OF YOUR SOUNDCARD'S DRIVER]
  **
  ubuntu-bug -s audio returns the following error

  *** Error: Unknown symptom

  The symptom audio is not known.
  

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

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


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

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

apport-collect 1289128

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  External laptop speakers work only for several minutes then shut off

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Linux Mint 16 Petra  Ubuntu 13.04 and 13.10
  Toshiba Satellite L655-S5150
  Running lates version of BIOS

  I can't get my laptop speakers to stay running.

  What happens is that when I first start up my laptop, sound will come out of 
the speakers for 2-3 minutes and then stop. If I reboot it will come back on 
for 2-3 minutes again. My headphones work fine for as long as I want them to 
play. I also tried the Auto Mute - disable idea that is mentioned in many of 
the posts by people with the same problem.
  One weird thing is that if I close my laptop and let it go into suspend then 
open it back up, the sound comes back on for 2-3 minutes. I tested the power 
settings on this. If I have my laptop set up to go into suspend when I close 
the lid (Under the “When Plugged In” settings) , the sound comes back on. If I 
have my power setting for “When the Lid is Closed” set to “Do Nothing” (under 
the “When Plugged In” settings) and close the lid, the sound does NOT come back 
on. Same scenario if I go onto battery power (comes back on if set to suspend). 
This issue seems to be tied to the suspend / power settings somehow. Just now I 
shut the lid and re-opend it and the sound played for 1 minutes and 27 seconds 
before cutting off again.

  On another note, this system is dual boot so I started up Windows and
  ran Media Player for about an hour and the sound played the entire
  time. This would rule out a true hardware fault.

  I have run the command wget http://www.alsa-project.org/alsa-info.sh
  -O alsa-info.sh  bash alsa-info.sh and saved the information
  locally. It creates a folder with sub folders so I'm not sure what I
  should upload.

  I tried installing DKMS under Mint 16 but it didn't appear to work and
  I don't have Ubuntu installed on my system any longer.

  I'm willing to try any troubleshooting steps you need to assist in
  fixing this problem. Here is some more information below.

  
  Info from sudo aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  ***
  Output from lspci -v | grep -A7 -i audio
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
Subsystem: Toshiba America Info Systems Device fd50
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at d640 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
  
  This page (https://help.ubuntu.com/community/SoundTroubleshooting) said to 
run modprobe on my sound driver. I couldn't figure out what my driver was so I 
was never able to do that step.

  sudo modprobe snd-[NAME OF YOUR SOUNDCARD'S DRIVER]
  **
  ubuntu-bug -s audio returns the following error

  *** Error: Unknown symptom

  The symptom audio is not known.
  

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

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


[Kernel-packages] [Bug 1281213] Re: Ubuntu goes into standby mode instead of powering off

2014-03-07 Thread hon
** Tags added: kernel-fixed-upstream

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

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

Title:
  Ubuntu goes into standby mode instead of powering off

Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  Steps to demonstrate the problem:
  1. Order Ubuntu shut down the GUI or sudo poweroff.
  2. When you see the Ubuntu logo on a purple background close the laptop lid. 
Ubuntu suspend powering off and go into standby mode.
  3. Open the lid of the laptop and Ubuntu will continue powering off.

  What should be do:
  Closing laptop lid not affect on powering off process.

  My system: Ubuntu 12.04 x64
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-36-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  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/controlC1:  alex   2701 F pulseaudio
   /dev/snd/controlC0:  alex   2701 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xdff0 irq 51'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,104313c7,00100100'
 Controls  : 22
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xdfe4 irq 52'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MachineType: ASUSTeK Computer Inc. K54LY
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-36-generic 
root=UUID=2cbbc362-11bb-4970-ba77-b45b6531f0f5 ro splash quiet
  ProcVersionSignature: Ubuntu 3.8.0-36.52~precise1-generic 3.8.13.14
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-36-generic N/A
   linux-backports-modules-3.8.0-36-generic  N/A
   linux-firmware1.79.9
  Tags:  precise
  Uname: Linux 3.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm debian-tor lpadmin sambashare sudo
  WifiSyslog:
   
  dmi.bios.date: 12/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54LY.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54LY
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54LY.208:bd12/21/2011:svnASUSTeKComputerInc.:pnK54LY:pvr1.0:rvnASUSTeKComputerInc.:rnK54LY:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K54LY
  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/1281213/+subscriptions

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


[Kernel-packages] [Bug 1266900] Re: kernel panic ubuntu daily image AMD 64

2014-03-07 Thread Jonathan Brier
New attempt of daily image from March 6, 2014 fully patched for the day
at 8:42pm Eastern time  Panic still occurs

Includes last of the dmesg and call trace from exit

** Attachment added: March 6 Image test - drm_kms_helper panic
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266900/+attachment/4011999/+files/IMG_20140306_204239.jpg

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

Title:
  kernel panic ubuntu daily image AMD 64

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have yet been able to boot using a USB to the daily build for 14.04 on this 
computer while it runs with 13.10 (with some graphical corruption at this 
time). I have tried booting via one time boot with a single monitor and with 
all three monitors.  I only see the initramfs dialogue:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266900/+attachment/3942803/+files/IMG_20140107_140409.jpg

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jonathan   3384 F pulseaudio
   /dev/snd/controlC3:  jonathan   3384 F pulseaudio
   /dev/snd/controlC2:  jonathan   3384 F pulseaudio
   /dev/snd/controlC0:  jonathan   3384 F pulseaudio
  Date: Tue Jan  7 15:14:54 2014
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5aba1ebe-fee7-4527-b2a4-ac022892d6fd
  InstallationDate: Installed on 2012-11-29 (403 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
   2 radeondrmfb
   3 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=c4ec6b3f-ea2f-479a-9ad4-f1eab2c84e9c ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  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:

  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-09-28 (101 days ago)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Crosshair IV Formula
  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:bd09/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIVFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1289410] [NEW] Xorg freeze

2014-03-07 Thread Barry Warsaw
Public bug reported:

This may be a kernel bug, and I'll add a bug task for that.

% uname -a
Linux anarchist 3.13.0-15-generic #35-Ubuntu SMP Mon Mar 3 15:54:59 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

With this kernel, I can log in just fine.  With -16 however, after I
type my password, the screen flashes but my desktop never comes up.
I've left it like this for a few hours and it's a true hang on login.
However, I *can* ssh into the machine, which is how I reboot it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Mar  7 10:23:03 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2013-12-06 (90 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-15-generic 
root=UUID=94d2915e-fb19-4acc-a25c-72a220adc614 ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.11+14.04.20140305-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Mar  7 10:20:31 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVMware VMware Virtual USB Mouse MOUSE, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.errors: No surface to present from.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputVirtual2 
   Virtual3Virtual4Virtual5Virtual6Virtual7 
   Virtual8
xserver.version: 2:1.15.0-1ubuntu6
xserver.video_driver: vmware

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

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


** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu

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

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

Title:
  Xorg freeze

Status in “linux-meta” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  This may be a kernel bug, and I'll add a bug task for that.

  % uname -a
  Linux anarchist 3.13.0-15-generic #35-Ubuntu SMP Mon Mar 3 15:54:59 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  With this kernel, I can log in just fine.  With -16 however, after I
  type my password, the screen flashes but my desktop never comes up.
  I've left it like this for a few hours and it's a true 

[Kernel-packages] [Bug 1289410] Re: Xorg freeze

2014-03-07 Thread Barry Warsaw
% dpkg-query -W linux-image-generic
linux-image-generic 3.13.0.16.20

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

Title:
  Xorg freeze

Status in “linux-meta” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  This may be a kernel bug, and I'll add a bug task for that.

  % uname -a
  Linux anarchist 3.13.0-15-generic #35-Ubuntu SMP Mon Mar 3 15:54:59 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  With this kernel, I can log in just fine.  With -16 however, after I
  type my password, the screen flashes but my desktop never comes up.
  I've left it like this for a few hours and it's a true hang on login.
  However, I *can* ssh into the machine, which is how I reboot it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
  Uname: Linux 3.13.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar  7 10:23:03 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-12-06 (90 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-15-generic 
root=UUID=94d2915e-fb19-4acc-a25c-72a220adc614 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar  7 10:20:31 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors: No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: vmware

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

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


[Kernel-packages] [Bug 1289418] [NEW] [System manufacturer System Product Name] suspend/resume failure [non-free: fglrx]

2014-03-07 Thread Jeremiah Corbin
Public bug reported:

Activated Suspend and it never completed.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelModules: fglrx
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jdc3139 F pulseaudio
 /dev/snd/controlC0:  jdc3139 F pulseaudio
Date: Fri Mar  7 08:31:15 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=7f40e0c3-bcf7-42be-8d78-20672cdb52b2
InstallationDate: Installed on 2014-02-05 (29 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140204)
InterpreterPath: /usr/bin/python3.4
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic.efi.signed 
root=UUID=70a96916-ca8b-4158-b114-ad2c46e9e380 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
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-16-generic N/A
 linux-backports-modules-3.13.0-16-generic  N/A
 linux-firmware 1.126
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: [System manufacturer System Product Name] suspend/resume failure 
[non-free: fglrx]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 05/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85-V PRO
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.:bvr6104:bd05/08/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-kerneloops resume suspend trusty

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

Title:
  [System manufacturer System Product Name] suspend/resume failure [non-
  free: fglrx]

Status in “linux” package in Ubuntu:
  New

Bug description:
  Activated Suspend and it never completed.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jdc3139 F pulseaudio
   /dev/snd/controlC0:  jdc3139 F pulseaudio
  Date: Fri Mar  7 08:31:15 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=7f40e0c3-bcf7-42be-8d78-20672cdb52b2
  InstallationDate: Installed on 2014-02-05 (29 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140204)
  InterpreterPath: /usr/bin/python3.4
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic.efi.signed 
root=UUID=70a96916-ca8b-4158-b114-ad2c46e9e380 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  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-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [System manufacturer System Product Name] suspend/resume failure 
[non-free: fglrx]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/08/2013
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1289429] [NEW] rtl8192ce kernel panic on bootup

2014-03-07 Thread DustWolf
Public bug reported:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION=Ubuntu 12.04.4 LTS
Fully updated.

Linux 3.8.0-37-generic AMD64 kernel, the rtl8192ce driver sometimes
causes a kernel panic on system startup of my Lenovo Thinkpad X230.
Restarting many times results in some sucessful boots, but the problem
can be persistant. The problem does not occur on the Linux
3.8.0-36-generic AMD64 kernel.

Unfortunately the dump I get on the screen durring such crashed boots,
does not appear to be in the logs.

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

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

Title:
  rtl8192ce kernel panic on bootup

Status in “linux-firmware” package in Ubuntu:
  New

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.04
  DISTRIB_CODENAME=precise
  DISTRIB_DESCRIPTION=Ubuntu 12.04.4 LTS
  Fully updated.

  Linux 3.8.0-37-generic AMD64 kernel, the rtl8192ce driver sometimes
  causes a kernel panic on system startup of my Lenovo Thinkpad X230.
  Restarting many times results in some sucessful boots, but the problem
  can be persistant. The problem does not occur on the Linux
  3.8.0-36-generic AMD64 kernel.

  Unfortunately the dump I get on the screen durring such crashed boots,
  does not appear to be in the logs.

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

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


[Kernel-packages] [Bug 1287587] Re: [ASUSTeK Computer Inc. K53SD] suspend/resume failure

2014-03-07 Thread Karma Dorje
that's what I see in the output of dmesg:

[ 6794.800715] PM: Entering mem sleep
[ 6794.800802] Suspending console(s) (use no_console_suspend to debug)
[ 6794.801006] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 6794.801319] sd 0:0:0:0: [sda] Stopping disk
[ 6794.844864] [ cut here ]
[ 6794.844929] WARNING: CPU: 1 PID: 20197 at 
/build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_uncore.c:125 
gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915]()
[ 6794.844931] MMIO read or write has been dropped 
[ 6794.844989] Modules linked in: nls_iso8859_1 bbswitch(OF) ctr ccm bnep 
rfcomm bluetooth ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ipt_REJECT xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
iptable_filter ip_tables x_tables uvcvideo videobuf2_vmalloc arc4 
videobuf2_memops videobuf2_core iwldvm videodev hid_generic usb_storage usbhid 
mac80211 hid asus_nb_wmi intel_rapl asus_wmi i915 joydev x86_pkg_temp_thermal 
intel_powerclamp sparse_keymap mxm_wmi snd_hda_codec_hdmi iwlwifi 
snd_hda_codec_realtek snd_hda_intel kvm_intel kvm snd_hda_codec snd_hwdep 
snd_pcm snd_page_alloc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel cfg80211 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq atl1c 
drm_kms_helper aes_x86_64 drm snd_seq_device snd_timer lrw gf128mul mei_me snd 
psmouse glue_helper mei video soundcore mac_hid i2c_algo_bit lpc_ich wmi 
ablk_helper cryptd serio_raw coretemp lp parport ahci libahci
[ 6794.845004] CPU: 1 PID: 20197 Comm: kworker/u32:4 Tainted: GF   W  O 
3.13.0-16-generic #36-Ubuntu
[ 6794.845004] Hardware name: ASUSTeK Computer Inc. K53SD/K53SD, BIOS K53SD.205 
03/06/2012
[ 6794.845016] Workqueue: i915 gen6_force_wake_work [i915]
[ 6794.845018]  0009 880092debd38 81710b65 
880092debd80
[ 6794.845020]  880092debd70 810662cd 88023de98020 
88023de98028
[ 6794.845022]  0246  0400 
880092debdd0
[ 6794.845022] Call Trace:
[ 6794.845026]  [81710b65] dump_stack+0x45/0x56
[ 6794.845029]  [810662cd] warn_slowpath_common+0x7d/0xa0
[ 6794.845030]  [8106633c] warn_slowpath_fmt+0x4c/0x50
[ 6794.845042]  [a03fcd48] gen6_gt_check_fifodbg.isra.9+0x38/0x50 
[i915]
[ 6794.845051]  [a03fcd88] __gen6_gt_force_wake_put+0x28/0x30 [i915]
[ 6798.276925] ata1.00: configured for UDMA/133
[ 6798.291180] sd 0:0:0:0: [sda] Starting disk
[ 6798.324634] PM: resume of devices complete after 1909.439 msecs
[ 6798.324832] PM: Finishing wakeup.

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

Title:
  [ASUSTeK Computer Inc. K53SD] suspend/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

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

  cat /proc/version_signature 
  Ubuntu 3.13.0-14.34-generic 3.13.5

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-14-generic 3.13.0-14.34
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karma  2367 F pulseaudio
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue Mar  4 16:00:38 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0
  InstallationDate: Installed on 2012-09-30 (520 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120817.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: ASUSTeK Computer Inc. K53SD
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-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-14-generic N/A
   linux-backports-modules-3.13.0-14-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure
  

[Kernel-packages] [Bug 1240731] Re: Mouse middle wheel not working on Hyper-V

2014-03-07 Thread Chris Valean
Using the image  trusty-desktop-amd64.iso   built on 07-Mar-2014 07:52,
I'm not able to reproduce the cursor springs when scrolling.

From our side the mouse scroll and mouse scroll click are working fine,
just as on the Server build.

OS: Windows Server 2012 R2
VM Ubuntu 14.04 daily build, using VM Connection interface.

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

Title:
  Mouse middle wheel not working on Hyper-V

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  It appears that the mouse middle wheel is not working on Ubuntu 13.10.
  This used to work on past distributions but something seems to have
  regressed it in Ubuntu 13.10. Please triage and fix the problem.

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

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


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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  [System manufacturer System Product Name] suspend/resume failure [non-
  free: fglrx]

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Activated Suspend and it never completed.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jdc3139 F pulseaudio
   /dev/snd/controlC0:  jdc3139 F pulseaudio
  Date: Fri Mar  7 08:31:15 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=7f40e0c3-bcf7-42be-8d78-20672cdb52b2
  InstallationDate: Installed on 2014-02-05 (29 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140204)
  InterpreterPath: /usr/bin/python3.4
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic.efi.signed 
root=UUID=70a96916-ca8b-4158-b114-ad2c46e9e380 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  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-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [System manufacturer System Product Name] suspend/resume failure 
[non-free: fglrx]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/08/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-V PRO
  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.:bvr6104:bd05/08/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-VPRO: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/1289418/+subscriptions

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


[Kernel-packages] [Bug 1289410] Re: Xorg freeze

2014-03-07 Thread Brad Figg
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)

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

Title:
  Xorg freeze

Status in “linux” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  This may be a kernel bug, and I'll add a bug task for that.

  % uname -a
  Linux anarchist 3.13.0-15-generic #35-Ubuntu SMP Mon Mar 3 15:54:59 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  With this kernel, I can log in just fine.  With -16 however, after I
  type my password, the screen flashes but my desktop never comes up.
  I've left it like this for a few hours and it's a true hang on login.
  However, I *can* ssh into the machine, which is how I reboot it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
  Uname: Linux 3.13.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar  7 10:23:03 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-12-06 (90 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-15-generic 
root=UUID=94d2915e-fb19-4acc-a25c-72a220adc614 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar  7 10:20:31 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors: No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: vmware

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

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


[Kernel-packages] [Bug 1287351] Re: kerneloops crashed with SIGSEGV in _int_malloc()

2014-03-07 Thread Brian Murray
This may be fixed with kernel-oops version 0.12+git20090217-3ubuntu5.

** Information type changed from Private to Public

** Changed in: kerneloops (Ubuntu)
   Status: New = Incomplete

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

Title:
  kerneloops crashed with SIGSEGV in _int_malloc()

Status in “kerneloops” package in Ubuntu:
  Incomplete

Bug description:
  when ejecting a flash drive

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: kerneloops-daemon 0.12+git20090217-3ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Mar  3 21:26:30 2014
  ExecutablePath: /usr/sbin/kerneloops
  InstallationDate: Installed on 2014-02-14 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  ProcCmdline: /usr/sbin/kerneloops
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f899491a231 _int_malloc+2337: mov
%r13,(%rax,%r13,1)
   PC (0x7f899491a231) ok
   source %r13 ok
   destination (%rax,%r13,1) (0x6b736964227bbcf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: kerneloops
  StacktraceTop:
   _int_malloc (av=0x7f8994c58760 main_arena, bytes=16000) at malloc.c:3740
   __GI___libc_malloc (bytes=16000) at malloc.c:2891
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: kerneloops crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Kernel-packages] [Bug 1289439] [NEW] Precise update to v3.8.13.19 stable release

2014-03-07 Thread Joseph Salisbury
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from Linus' tree or in a minimally
   backported form of that patch. The v3.8.13.19 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches are in the v3.8.13.19 stable release:
Linux 3.8.13.19
kvm: x86: fix apic_base enable check
EDAC: Correct workqueue setup path
EDAC: Poll timeout cannot be zero, p2
IB/qib: Add missing serdes init sequence
lockd: send correct lock when granting a delayed lock.
x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off
x86, smap: Don't enable SMAP if CONFIG_X86_SMAP is disabled
compiler/gcc4: Make quirk for asm_volatile_goto() unconditional
md/raid5: Fix CPU hotplug callback registration
block: add cond_resched() to potentially long running ioctl discard loop
ftrace/x86: Use breakpoints for converting function graph caller
usb: option: blacklist ZTE MF667 net interface
ring-buffer: Fix first commit on sub-buffer having non-zero delta
xen: install xen/gntdev.h and xen/gntalloc.h
genirq: Add missing irq_to_desc export for CONFIG_SPARSE_IRQ=n
fs/file.c:fdtable: avoid triggering OOMs from alloc_fdmem
Modpost: fixed USB alias generation for ranges including 0x9 and 0xA
xen-blkfront: handle backend CLOSED without CLOSING
staging: comedi: adv_pci1710: fix analog output readback value
tty: n_gsm: Fix for modems with brk in modem status control
raw: test against runtime value of max_raw_minors
Drivers: hv: vmbus: Don't timeout during the initial connection with host
VME: Correct read/write alignment algorithm
ALSA: hda - Fix mic capture on Sony VAIO Pro 11
time: Fix overflow when HZ is smaller than 60
mac80211: fix fragmentation code, particularly for encryption
mac80211: Fix IBSS disconnect
mac80211: release the channel in error path in start_ap
mac80211: move roc cookie assignment earlier
USB: ftdi_sio: add Tagsys RFID Reader IDs
usb: qcserial: add Netgear Aircard 340U
of: fix PCI bus match for PCIe slots
of: Fix address decoding on Bimini and js2x machines
usb-storage: enable multi-LUN scanning when needed
usb-storage: add unusual-devs entry for BlackBerry 9000
usb-storage: restrict bcdDevice range for Super Top in Cypress ATACB
usb: ftdi_sio: add Mindstorms EV3 console adapter
spi: nuc900: Set SPI_LSB_FIRST for master-mode_bits if hw-pdata-lsb is true
ath9k: Do not support PowerSave by default
ar5523: fix usb id for Gigaset.
ath9k_htc: Do not support PowerSave by default
ath9k_htc: make -sta_rc_update atomic for most calls
s390/dump: Fix dump memory detection
power: max17040: Fix NULL pointer dereference when there is no platform_data
block: __elv_next_request() shouldn't call into the elevator if bypassing
KVM: return an error code in kvm_vm_ioctl_register_coalesced_mmio()
staging:iio:ad799x fix error_free_irq which was freeing an irq that may not 
have been requested
mm: __set_page_dirty uses spin_lock_irqsave instead of spin_lock_irq
mm: __set_page_dirty_nobuffers() uses spin_lock_irqsave() instead of 
spin_lock_irq()
mm/swap: fix race on swap_info reuse between swapoff and swapon
x86, hweight: Fix BUG when booting with CONFIG_GCOV_PROFILE_ALL=y
drm/mgag200,ast,cirrus: fix regression with drm_can_sleep conversion
SELinux:  Fix kernel BUG on empty security contexts.
arm64: vdso: update wtm fields for CLOCK_MONOTONIC_COARSE
arm64: vdso: fix coarse clock handling
arm64: Invalidate the TLB when replacing pmd entries during boot
arm64: add DSB after icache flush in __flush_icache_all()
arm64: vdso: prevent ld from aligning PT_LOAD segments to 64k
[media] af9035: add ID [2040:f900] Hauppauge WinTV-MiniStick 2
[media] mxl111sf: Fix compile when CONFIG_DVB_USB_MXL111SF is unset
[media] mxl111sf: Fix unintentional garbage stack read
crypto: s390 - fix des and des3_ede ctr concurrency issue
crypto: s390 - fix des and des3_ede cbc concurrency issue
crypto: s390 - fix concurrency issue in aes-ctr mode
xfs: underflow bug in xfs_attrlist_by_handle()
crypto: ansi_cprng - Fix off by one error in non-block size request
netfilter: nf_nat: fix access to uninitialized buffer in IRC NAT helper

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

** Affects: linux (Ubuntu Precise)
 Importance: Medium
 Status: New


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for 

[Kernel-packages] [Bug 1289458] [NEW] BUG: unable to handle kernel paging request at 7371b5a3

2014-03-07 Thread ionash.
Public bug reported:

jDownloader was launching, when everything frozen, and I have to reset
my computer by hand.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic i686
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  janusz 1929 F pulseaudio
 /dev/snd/seq:timidity   1104 F timidity
  janusz 2088 F timidity
Date: Fri Mar  7 17:11:41 2014
DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location mmap_region+0x1/0x530 SS:ESP 0068:f01e5f24
Failure: oops
HibernationDevice: RESUME=UUID=a979e454-ec70-403b-8cd9-604aeae87307
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=23985ff5-112f-4dab-9da1-5c21397013fe ro splash quiet vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
RfKill:
 
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 7371b5a3
UpgradeStatus: Upgraded to trusty on 2013-11-26 (100 days ago)
dmi.bios.date: 11/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.9
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 785G-E53 (MS-7576)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd11/27/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785G-E53(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7576
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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


** Tags: apport-kerneloops i386 kernel-oops 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/1289458

Title:
  BUG: unable to handle kernel paging request at 7371b5a3

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  jDownloader was launching, when everything frozen, and I have to reset
  my computer by hand.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  janusz 1929 F pulseaudio
   /dev/snd/seq:timidity   1104 F timidity
janusz 2088 F timidity
  Date: Fri Mar  7 17:11:41 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location mmap_region+0x1/0x530 SS:ESP 0068:f01e5f24
  Failure: oops
  HibernationDevice: RESUME=UUID=a979e454-ec70-403b-8cd9-604aeae87307
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=23985ff5-112f-4dab-9da1-5c21397013fe ro splash quiet vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 7371b5a3
  UpgradeStatus: Upgraded to trusty on 2013-11-26 (100 days ago)
  dmi.bios.date: 11/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785G-E53 (MS-7576)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd11/27/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785G-E53(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7576
  dmi.product.version: 

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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  Xorg freeze

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

Bug description:
  This may be a kernel bug, and I'll add a bug task for that.

  % uname -a
  Linux anarchist 3.13.0-15-generic #35-Ubuntu SMP Mon Mar 3 15:54:59 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  With this kernel, I can log in just fine.  With -16 however, after I
  type my password, the screen flashes but my desktop never comes up.
  I've left it like this for a few hours and it's a true hang on login.
  However, I *can* ssh into the machine, which is how I reboot it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
  Uname: Linux 3.13.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar  7 10:23:03 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-12-06 (90 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-15-generic 
root=UUID=94d2915e-fb19-4acc-a25c-72a220adc614 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar  7 10:20:31 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors: No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: vmware

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

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


[Kernel-packages] [Bug 1289458] Re: BUG: unable to handle kernel paging request at 7371b5a3

2014-03-07 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  BUG: unable to handle kernel paging request at 7371b5a3

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  jDownloader was launching, when everything frozen, and I have to reset
  my computer by hand.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  janusz 1929 F pulseaudio
   /dev/snd/seq:timidity   1104 F timidity
janusz 2088 F timidity
  Date: Fri Mar  7 17:11:41 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location mmap_region+0x1/0x530 SS:ESP 0068:f01e5f24
  Failure: oops
  HibernationDevice: RESUME=UUID=a979e454-ec70-403b-8cd9-604aeae87307
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=23985ff5-112f-4dab-9da1-5c21397013fe ro splash quiet vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 7371b5a3
  UpgradeStatus: Upgraded to trusty on 2013-11-26 (100 days ago)
  dmi.bios.date: 11/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785G-E53 (MS-7576)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd11/27/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785G-E53(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7576
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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


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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  BUG: unable to handle kernel paging request at 7371b5a3

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  jDownloader was launching, when everything frozen, and I have to reset
  my computer by hand.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  janusz 1929 F pulseaudio
   /dev/snd/seq:timidity   1104 F timidity
janusz 2088 F timidity
  Date: Fri Mar  7 17:11:41 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location mmap_region+0x1/0x530 SS:ESP 0068:f01e5f24
  Failure: oops
  HibernationDevice: RESUME=UUID=a979e454-ec70-403b-8cd9-604aeae87307
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=23985ff5-112f-4dab-9da1-5c21397013fe ro splash quiet vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 7371b5a3
  UpgradeStatus: Upgraded to trusty on 2013-11-26 (100 days ago)
  dmi.bios.date: 11/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785G-E53 (MS-7576)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd11/27/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785G-E53(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7576
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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


[Kernel-packages] [Bug 1253100] [NEW] Intel Centrino Adv. N 6230 Wireless doesn't wake up again after suspend-to-RAM since Upgrade to 13.10

2014-03-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since I upgraded from Ubuntu 13.04 to Ubuntu 13.10, Wireless isn't working any 
more after suspend-to-RAM.
I'm using the amd64 version of Ubuntu on my Samsung NP900X3A-B03CH Ultrabook.
The Wireless-device is a (according to lspci)

Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak]

This is what /var/log/syslog shows:

Nov 20 15:08:07 900X3A kernel: [   32.372384] samsung_laptop: detected SABI 
interface: SwSmi@
Nov 20 15:08:07 900X3A kernel: [   32.372390] samsung_laptop: Backlight 
controlled by ACPI video driver
Nov 20 15:08:07 900X3A NetworkManager[1851]: info rfkill2: found WiFi radio 
killswitch (at /sys/devices/platform/samsung/rfkill/rfkill2) (platform driver 
(unknown))
Nov 20 15:08:09 90X03A NetworkManager[1851]: info (wlan0): IP6 addrconf timed 
out or failed.
Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 4 
of 5 (IPv6 Configure Timeout) scheduled...
Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 4 
of 5 (IPv6 Configure Timeout) started...
Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 4 
of 5 (IPv6 Configure Timeout) complete.

I'm rather surprised though, about this message  rfkill2: found WiFi radio 
killswitch (at /sys/devices/platform/samsung/rfkill/rfkill2) (platform driver 
(unknown))
as the Computer doesn't have any hardware wifi-switch...?

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


** Tags: bot-comment samsung wifi wireless
-- 
Intel Centrino Adv. N 6230 Wireless doesn't wake up again after suspend-to-RAM 
since Upgrade to 13.10
https://bugs.launchpad.net/bugs/1253100
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1253032] [NEW] Bluetooth file transfer fails everytime.Shows an error message like: GDBus.Error:org.openobex.Error.Failed:Unable to request session

2014-03-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The bluetooth service can add devices, view the files in the device
using FTP and even can delete files from it (paired/connected device).
But the system bluetooth fails to send or receive files from a device.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: evince 3.6.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
Uname: Linux 3.8.0-33-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
Date: Wed Nov 20 15:27:58 2013
InstallationDate: Installed on 2013-10-28 (22 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to raring on 2013-11-12 (8 days ago)

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


** Tags: amd64 apparmor apport-bug raring
-- 
Bluetooth file transfer fails everytime.Shows an error message like:  
GDBus.Error:org.openobex.Error.Failed:Unable to request session 
https://bugs.launchpad.net/bugs/1253032
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

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


[Kernel-packages] [Bug 1289474] [NEW] [Hewlett-Packard HP Compaq 6720s] suspend/resume failure [non-free: wl]

2014-03-07 Thread Jayendra Sharan
Public bug reported:

everytime i login, i see an error System detected a Problem

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-15-generic 3.13.0-15.35
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic i686
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lightdm1643 F pulseaudio
  jayen  2187 F pulseaudio
CurrentDmesg:
 [   31.052842] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO
 [   31.052877] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [   32.361431] init: plymouth-stop pre-start process (1348) terminated with 
status 1
 [   93.105026] NET: Registered protocol family 24
Date: Fri Mar  7 22:10:08 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=6eb6b1bb-88ed-47ad-be96-7042c100975e
InstallationDate: Installed on 2014-03-01 (6 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 
(20140204)
InterpreterPath: /usr/bin/python3.4
MachineType: Hewlett-Packard HP Compaq 6720s
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic 
root=UUID=6cebd255-aaf3-4984-b242-04b2b8fe3b0a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-15-generic N/A
 linux-backports-modules-3.13.0-15-generic  N/A
 linux-firmware 1.125
SourcePackage: linux
Title: [Hewlett-Packard HP Compaq 6720s] suspend/resume failure [non-free: wl]
UpgradeStatus: Upgraded to trusty on 2014-03-05 (2 days ago)
UserGroups:
 
dmi.bios.date: 09/04/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MDU Ver. F.03
dmi.board.name: 30D8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 83.0C
dmi.chassis.asset.tag: CNU73822D3
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.03:bd09/04/2007:svnHewlett-Packard:pnHPCompaq6720s:pvrF.03:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0C:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6720s
dmi.product.version: F.03
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-kerneloops i386 resume suspend 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/1289474

Title:
  [Hewlett-Packard HP Compaq 6720s] suspend/resume failure [non-free:
  wl]

Status in “linux” package in Ubuntu:
  New

Bug description:
  everytime i login, i see an error System detected a Problem

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-15-generic 3.13.0-15.35
  ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
  Uname: Linux 3.13.0-15-generic i686
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1643 F pulseaudio
jayen  2187 F pulseaudio
  CurrentDmesg:
   [   31.052842] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO
   [   31.052877] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   32.361431] init: plymouth-stop pre-start process (1348) terminated with 
status 1
   [   93.105026] NET: Registered protocol family 24
  Date: Fri Mar  7 22:10:08 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6eb6b1bb-88ed-47ad-be96-7042c100975e
  InstallationDate: Installed on 2014-03-01 (6 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 
(20140204)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Hewlett-Packard HP Compaq 6720s
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic 
root=UUID=6cebd255-aaf3-4984-b242-04b2b8fe3b0a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-15-generic N/A
   linux-backports-modules-3.13.0-15-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
 

[Kernel-packages] [Bug 1253100] Re: Intel Centrino Adv. N 6230 Wireless doesn't wake up again after suspend-to-RAM since Upgrade to 13.10

2014-03-07 Thread John Kim
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

** Package changed: ubuntu = linux (Ubuntu)

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

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

Title:
  Intel Centrino Adv. N 6230 Wireless doesn't wake up again after
  suspend-to-RAM since Upgrade to 13.10

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Since I upgraded from Ubuntu 13.04 to Ubuntu 13.10, Wireless isn't working 
any more after suspend-to-RAM.
  I'm using the amd64 version of Ubuntu on my Samsung NP900X3A-B03CH Ultrabook.
  The Wireless-device is a (according to lspci)

  Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak]

  This is what /var/log/syslog shows:

  Nov 20 15:08:07 900X3A kernel: [   32.372384] samsung_laptop: detected SABI 
interface: SwSmi@
  Nov 20 15:08:07 900X3A kernel: [   32.372390] samsung_laptop: Backlight 
controlled by ACPI video driver
  Nov 20 15:08:07 900X3A NetworkManager[1851]: info rfkill2: found WiFi radio 
killswitch (at /sys/devices/platform/samsung/rfkill/rfkill2) (platform driver 
(unknown))
  Nov 20 15:08:09 90X03A NetworkManager[1851]: info (wlan0): IP6 addrconf 
timed out or failed.
  Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 
4 of 5 (IPv6 Configure Timeout) scheduled...
  Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 
4 of 5 (IPv6 Configure Timeout) started...
  Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 
4 of 5 (IPv6 Configure Timeout) complete.

  I'm rather surprised though, about this message  rfkill2: found WiFi radio 
killswitch (at /sys/devices/platform/samsung/rfkill/rfkill2) (platform driver 
(unknown))
  as the Computer doesn't have any hardware wifi-switch...?

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

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


[Kernel-packages] [Bug 1253032] Re: Bluetooth file transfer fails everytime.Shows an error message like: GDBus.Error:org.openobex.Error.Failed:Unable to request session

2014-03-07 Thread John Kim
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop ISO of the
development release - Trusty Tahr. It would help us greatly if you could
test with it so we can work on getting it fixed in the next release of
Ubuntu. You can find out more about the development release at
http://www.ubuntu.com/testing/ . Thanks again and we appreciate your
help.

** Description changed:

  The bluetooth servie can add devices, view the files in the device using
- FTP and also it even can delete files from it(paired/connected device)
- also. But the system bluetooth fails to send or receive files from a
- device.
+ FTP and even can delete files from it (paired/connected device). But the
+ system bluetooth fails to send or receive files from a device.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Wed Nov 20 15:27:58 2013
  InstallationDate: Installed on 2013-10-28 (22 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_IN
+  SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to raring on 2013-11-12 (8 days ago)

** Description changed:

- The bluetooth servie can add devices, view the files in the device using
- FTP and even can delete files from it (paired/connected device). But the
- system bluetooth fails to send or receive files from a device.
+ The bluetooth service can add devices, view the files in the device
+ using FTP and even can delete files from it (paired/connected device).
+ But the system bluetooth fails to send or receive files from a device.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Wed Nov 20 15:27:58 2013
  InstallationDate: Installed on 2013-10-28 (22 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to raring on 2013-11-12 (8 days ago)

** Package changed: ubuntu = bluez (Ubuntu)

** Changed in: bluez (Ubuntu)
   Status: New = Incomplete

** Tags added: needs-reassignment

** Tags added: derivatives

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

Title:
  Bluetooth file transfer fails everytime.Shows an error message like: 
  GDBus.Error:org.openobex.Error.Failed:Unable to request session 

Status in “bluez” package in Ubuntu:
  Incomplete

Bug description:
  The bluetooth service can add devices, view the files in the device
  using FTP and even can delete files from it (paired/connected device).
  But the system bluetooth fails to send or receive files from a device.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Wed Nov 20 15:27:58 2013
  InstallationDate: Installed on 2013-10-28 (22 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to raring on 2013-11-12 (8 days ago)

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

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


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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  [Hewlett-Packard HP Compaq 6720s] suspend/resume failure [non-free:
  wl]

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  everytime i login, i see an error System detected a Problem

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-15-generic 3.13.0-15.35
  ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
  Uname: Linux 3.13.0-15-generic i686
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1643 F pulseaudio
jayen  2187 F pulseaudio
  CurrentDmesg:
   [   31.052842] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO
   [   31.052877] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   32.361431] init: plymouth-stop pre-start process (1348) terminated with 
status 1
   [   93.105026] NET: Registered protocol family 24
  Date: Fri Mar  7 22:10:08 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6eb6b1bb-88ed-47ad-be96-7042c100975e
  InstallationDate: Installed on 2014-03-01 (6 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 
(20140204)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Hewlett-Packard HP Compaq 6720s
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic 
root=UUID=6cebd255-aaf3-4984-b242-04b2b8fe3b0a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-15-generic N/A
   linux-backports-modules-3.13.0-15-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  Title: [Hewlett-Packard HP Compaq 6720s] suspend/resume failure [non-free: wl]
  UpgradeStatus: Upgraded to trusty on 2014-03-05 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 09/04/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MDU Ver. F.03
  dmi.board.name: 30D8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 83.0C
  dmi.chassis.asset.tag: CNU73822D3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.03:bd09/04/2007:svnHewlett-Packard:pnHPCompaq6720s:pvrF.03:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6720s
  dmi.product.version: F.03
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1289494] [NEW] Trackpad not working on Chromebook pixel running Chrubuntu from a usb drive after kernel upgrade to version 3.11.0-18

2014-03-07 Thread Alberto Elias
Public bug reported:

After running the upgrade and restarting, my touchpad stopped working
but a USB mouse does work. If I run cat /proc/bus/input/devices,
touchpad doesn't appear. I'm attaching that output, dmesg and my Xorg
log.

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


** Tags: touchpad

** Attachment added: Zip including dmesg, devices and Xorg log
   
https://bugs.launchpad.net/bugs/1289494/+attachment/4012299/+files/touchpadbuglogs.zip

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

Title:
  Trackpad not working on Chromebook pixel running Chrubuntu from a usb
  drive after kernel upgrade to version 3.11.0-18

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After running the upgrade and restarting, my touchpad stopped working
  but a USB mouse does work. If I run cat /proc/bus/input/devices,
  touchpad doesn't appear. I'm attaching that output, dmesg and my Xorg
  log.

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

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


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

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

apport-collect 1289494

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Trackpad not working on Chromebook pixel running Chrubuntu from a usb
  drive after kernel upgrade to version 3.11.0-18

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After running the upgrade and restarting, my touchpad stopped working
  but a USB mouse does work. If I run cat /proc/bus/input/devices,
  touchpad doesn't appear. I'm attaching that output, dmesg and my Xorg
  log.

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

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


[Kernel-packages] [Bug 1219368] Re: 14e4:4320 Airport Extreme (Broadcom BCM4306) not working on iMac G5

2014-03-07 Thread Nikolai Alexihof
I was planning on reinstalling, and I left my iMac on while I went and
got install media, and it decided to boot all the way up.

With the installed kernel, I'm getting:

[  210.709352] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
[  210.783377] ADDRCONF(NETDEV_UP): wlan0: link is not ready

and the WLAN never enables.

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

Title:
  14e4:4320 Airport Extreme (Broadcom BCM4306) not working on iMac G5

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  wlan0 worked approximately 3 months ago, when I last booted this
  system, but upon updating and rebooting, my wireless NIC stopped
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-52-powerpc64-smp 3.2.0-52.78
  ProcVersionSignature: Ubuntu 3.2.0-52.78-powerpc64-smp 3.2.48
  Uname: Linux 3.2.0-52-powerpc64-smp ppc64
  AcpiTables:

  AlsaDevices:
   total 0
   crw-rw---T+ 1 root audio 116,  1 Aug 31 22:51 seq
   crw-rw---T+ 1 root audio 116, 33 Aug 31 22:51 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices: aplay: device_list:252: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: powerpc
  ArecordDevices: arecord: device_list:252: no soundcards found...
  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
  CurrentDmesg: [  146.992985] [drm] nouveau :f0:10.0: Pixel clock 
comparison table not found
  Date: Sat Aug 31 22:54:17 2013
  HibernationDevice: RESUME=UUID=b408cf63-ff5f-4a59-936e-86a765d55f66
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release powerpc 
(20120423.1)
  MarkForUpload: True
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=d0b20cde-d75e-45ce-8b9c-c958416c59bd ro quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-52-powerpc64-smp N/A
   linux-backports-modules-3.2.0-52-powerpc64-smp  N/A
   linux-firmware  1.79.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1253155] Re: Failure to validate module signature at boot time

2014-03-07 Thread Andy Whitcroft
** Also affects: linux-lts-raring (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Failure to validate module signature at boot time

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  New
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux-lts-raring” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux-lts-raring” source package in Trusty:
  New

Bug description:
  When booting under secureboot and using a signed kernel, it's expected
  that all modules shipped alongside the kernel should validate and load
  successfully without tainting the kernel.

  Unfortunately it doesn't seem to always be the case. Looking through
  my kernel logs, I see:

  Nov 15 10:35:24 castiana kernel: [1.635132] video: module
  verification failed: signature and/or required key missing - tainting
  kernel

  or

  Nov 12 12:58:48 castiana kernel: [213981.753326] Request for unknown
  module key 'Magrathea: Glacier signing key:
  f440a253eb498df923d438caa09b3b5d99308405' err -11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stgraber   2721 F pulseaudio
   /dev/snd/controlC0:  stgraber   2721 F pulseaudio
   /dev/snd/pcmC0D0c:   stgraber   2721 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stgraber   2721 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 20 11:59:57 2013
  InstallationDate: Installed on 2013-04-21 (213 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420)
  MachineType: LENOVO 2306CT0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic.efi.signed 
root=UUID=14de4e20-b139-488e-863f-ec710f776851 ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CT0
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET96WW(2.56):bd08/27/2013:svnLENOVO:pn2306CT0:pvrThinkPadX230:rvnLENOVO:rn2306CT0:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CT0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1245081] Re: macbook keyboard layout maps the tilde key to something else

2014-03-07 Thread Daryl Tucker
The workaround posted by Yaun worked for me on my 13.10 installation on
my Macbook Air 6,2 (2013).  Thank you very much.

 sudo su -
 echo 0  /sys/module/hid_apple/parameters/iso_layout

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

Title:
  macbook keyboard layout maps the tilde key to something else

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  1. install ubuntu on Macbook Air 6,2
  2. press the key with the tilde ('~') written on it.
  3. see that is prints '§' instead.

  This is particularly annoying since the way to switch between windows uses 
the tilde.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms1491 F pulseaudio
   /dev/snd/controlC1:  kms1491 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=9e7b2d0e-6a44-4ad7-9725-f9a3f5f39c33
  InstallationDate: Installed on 2013-10-25 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64+mac 
(20131016.1)
  MachineType: Apple Inc. MacBookAir6,2
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux 3.11.0.12.13
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=079cbe6b-6488-4e57-85d3-c3e3e2fcbe40 ro quiet splash vt.handoff=7
  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
  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: 07/12/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B01.1307121317
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B01.1307121317:bd07/12/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.name: MacBookAir6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1253155] Re: Failure to validate module signature at boot time

2014-03-07 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Quantal)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-raring (Ubuntu Quantal)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-lts-raring (Ubuntu Saucy)
   Status: New = Invalid

** Changed in: linux-lts-raring (Ubuntu)
   Status: New = Invalid

** Changed in: linux-lts-raring (Ubuntu Quantal)
   Status: New = Invalid

** Changed in: linux-lts-raring (Ubuntu Precise)
   Status: New = In Progress

** Changed in: linux-lts-raring (Ubuntu Precise)
 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/1253155

Title:
  Failure to validate module signature at boot time

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  In Progress
Status in “linux” source package in Quantal:
  New
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux-lts-raring” source package in Trusty:
  Invalid

Bug description:
  When booting under secureboot and using a signed kernel, it's expected
  that all modules shipped alongside the kernel should validate and load
  successfully without tainting the kernel.

  Unfortunately it doesn't seem to always be the case. Looking through
  my kernel logs, I see:

  Nov 15 10:35:24 castiana kernel: [1.635132] video: module
  verification failed: signature and/or required key missing - tainting
  kernel

  or

  Nov 12 12:58:48 castiana kernel: [213981.753326] Request for unknown
  module key 'Magrathea: Glacier signing key:
  f440a253eb498df923d438caa09b3b5d99308405' err -11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stgraber   2721 F pulseaudio
   /dev/snd/controlC0:  stgraber   2721 F pulseaudio
   /dev/snd/pcmC0D0c:   stgraber   2721 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stgraber   2721 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 20 11:59:57 2013
  InstallationDate: Installed on 2013-04-21 (213 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420)
  MachineType: LENOVO 2306CT0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic.efi.signed 
root=UUID=14de4e20-b139-488e-863f-ec710f776851 ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CT0
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET96WW(2.56):bd08/27/2013:svnLENOVO:pn2306CT0:pvrThinkPadX230:rvnLENOVO:rn2306CT0:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CT0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1275794] Re: Lenovo T440s freezes when connected to docking station

2014-03-07 Thread Corey Bryant
Tested successfully on 3.14.0-031400rc4-generic.

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

Title:
  Lenovo T440s freezes when connected to docking station

Status in The Linux Kernel:
  Fix Released
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  This bug report looks to be for the same issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=71267

  I came across the above bug report here:
  https://bbs.archlinux.org/viewtopic.php?pid=1374408

  I'm running with a Thinkpad T440s and ultra dock with hdmi-hdmi.  In
  my case if I dock when hdmi is connected to the dock, the mouse and
  keyboard freeze once connected.  When I undock they unfreeze.  If I
  dock when hdmi is not connected to the dock, the mouse and keyboard
  don't freeze.

  Ubuntu release: 14.04 Trusty Tahr (development branch)
  --- 
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  corey  2385 F pulseaudio
   /dev/snd/controlC0:  corey  2385 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=12d1435c-d652-4aab-8da6-3b043f3da722
  InstallationDate: Installed on 2014-01-31 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140130)
  MachineType: LENOVO 20AQCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-5-generic.efi.signed 
root=UUID=d17999de-2672-48e5-b628-403d311d3251 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-5-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/10/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET67WW (2.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1253155] Re: Failure to validate module signature at boot time

2014-03-07 Thread Andy Whitcroft
This support does not exist before v3.7 and therefore does not affect
quantal or precise.

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

** Changed in: linux (Ubuntu Quantal)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

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

Title:
  Failure to validate module signature at boot time

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-raring” source package in Precise:
  In Progress
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux-lts-raring” source package in Trusty:
  Invalid

Bug description:
  When booting under secureboot and using a signed kernel, it's expected
  that all modules shipped alongside the kernel should validate and load
  successfully without tainting the kernel.

  Unfortunately it doesn't seem to always be the case. Looking through
  my kernel logs, I see:

  Nov 15 10:35:24 castiana kernel: [1.635132] video: module
  verification failed: signature and/or required key missing - tainting
  kernel

  or

  Nov 12 12:58:48 castiana kernel: [213981.753326] Request for unknown
  module key 'Magrathea: Glacier signing key:
  f440a253eb498df923d438caa09b3b5d99308405' err -11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stgraber   2721 F pulseaudio
   /dev/snd/controlC0:  stgraber   2721 F pulseaudio
   /dev/snd/pcmC0D0c:   stgraber   2721 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stgraber   2721 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 20 11:59:57 2013
  InstallationDate: Installed on 2013-04-21 (213 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420)
  MachineType: LENOVO 2306CT0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic.efi.signed 
root=UUID=14de4e20-b139-488e-863f-ec710f776851 ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CT0
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET96WW(2.56):bd08/27/2013:svnLENOVO:pn2306CT0:pvrThinkPadX230:rvnLENOVO:rn2306CT0:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CT0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1253155] Re: Failure to validate module signature at boot time

2014-03-07 Thread Andy Whitcroft
** Changed in: linux-lts-raring (Ubuntu Precise)
   Importance: Undecided = Medium

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

Title:
  Failure to validate module signature at boot time

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-raring” source package in Precise:
  In Progress
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux-lts-raring” source package in Trusty:
  Invalid

Bug description:
  When booting under secureboot and using a signed kernel, it's expected
  that all modules shipped alongside the kernel should validate and load
  successfully without tainting the kernel.

  Unfortunately it doesn't seem to always be the case. Looking through
  my kernel logs, I see:

  Nov 15 10:35:24 castiana kernel: [1.635132] video: module
  verification failed: signature and/or required key missing - tainting
  kernel

  or

  Nov 12 12:58:48 castiana kernel: [213981.753326] Request for unknown
  module key 'Magrathea: Glacier signing key:
  f440a253eb498df923d438caa09b3b5d99308405' err -11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stgraber   2721 F pulseaudio
   /dev/snd/controlC0:  stgraber   2721 F pulseaudio
   /dev/snd/pcmC0D0c:   stgraber   2721 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stgraber   2721 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 20 11:59:57 2013
  InstallationDate: Installed on 2013-04-21 (213 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420)
  MachineType: LENOVO 2306CT0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic.efi.signed 
root=UUID=14de4e20-b139-488e-863f-ec710f776851 ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CT0
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET96WW(2.56):bd08/27/2013:svnLENOVO:pn2306CT0:pvrThinkPadX230:rvnLENOVO:rn2306CT0:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CT0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1275116] Re: lowlatency-flavour crashes and locks up alot

2014-03-07 Thread Jaime Pérez
3.13.0-16-lowlatency seems to be working fine

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

Title:
  lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-lowlatency” package in Ubuntu:
  Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

  I will add crashdumps when I get crashes that do not just lockup the
  machine but currently I have only seem complete lockups with 3.13

  So the essense is :

  3.11-lowlatency crashed 10 time today most of the crashes reached the console 
so I could see the panic text.
  3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. 
During next reboot it also locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgh2176 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 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-6-generic 
root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic  N/A
   linux-firmware1.123
  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/1275116/+subscriptions

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


[Kernel-packages] [Bug 1289518] [NEW] Hotplug of virtio(block/net) devices not detected inside ppc64el guest

2014-03-07 Thread Steve Langasek
Public bug reported:

On ppc64el, a kernel patch and a userspace patch are needed to have
hotplugging of devices via e.g. 'virsh attach-interface' properly
detected by a guest kernel.

  http://sourceforge.net/p/powerpc-utils/mailman/message/32064992/
  http://patchwork.ozlabs.org/patch/327089/

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

** Affects: powerpc-ibm-utils (Ubuntu)
 Importance: High
 Assignee: Adam Conrad (adconrad)
 Status: Triaged

** Affects: linux (Ubuntu Trusty)
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

** Affects: powerpc-ibm-utils (Ubuntu Trusty)
 Importance: High
 Assignee: Adam Conrad (adconrad)
 Status: Triaged

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)

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

** Also affects: powerpc-ibm-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: powerpc-ibm-utils (Ubuntu)
   Status: New = Triaged

** Changed in: powerpc-ibm-utils (Ubuntu)
   Importance: Undecided = High

** Changed in: powerpc-ibm-utils (Ubuntu)
 Assignee: (unassigned) = Adam Conrad (adconrad)

** Also affects: powerpc-ibm-utils (Ubuntu Trusty)
   Importance: High
 Assignee: Adam Conrad (adconrad)
   Status: Triaged

** Also affects: linux (Ubuntu Trusty)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: 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/1289518

Title:
  Hotplug of virtio(block/net) devices not detected inside ppc64el guest

Status in “linux” package in Ubuntu:
  Triaged
Status in “powerpc-ibm-utils” package in Ubuntu:
  Triaged
Status in “linux” source package in Trusty:
  Triaged
Status in “powerpc-ibm-utils” source package in Trusty:
  Triaged

Bug description:
  On ppc64el, a kernel patch and a userspace patch are needed to have
  hotplugging of devices via e.g. 'virsh attach-interface' properly
  detected by a guest kernel.

http://sourceforge.net/p/powerpc-utils/mailman/message/32064992/
http://patchwork.ozlabs.org/patch/327089/

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

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


[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore

2014-03-07 Thread zeeeeee
juanmanuel,
No matter who found the latest/better solution, you are truly a hero.
After reading all the associated bug reports, I decided to use your script 
because I don't know how to compile the kernel, and I presume I would have to 
redo it every time the kernel got an update.

My laptop model is NP530U4C, finally with a normal behavior.
Gracias!

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

Title:
  [Samsung NP530U3C-A01] LID close, AC, and battery status events not
  produced anymore

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery
  status events not produced anymore. The situation is the same (tested
  with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where
  I can put all the information related to this bug here:
  http://zenstep.com.ar/samsung-linux/

  In summary, after a suspend sleep with many events (8 plug/unplug, or
  battery dropping or increasing about 16%, maybe less), the Embedded
  Controller accumulates those events and stops producing GPE 0x17.
  Neither Windows nor Linux query those accumulated events, because the
  EC doesn't produce GPE 0x17 anymore. The issue persists between
  restarts and shutdowns, and even after re-suspending/re-resuming.
  Hitting the reset button through the hole in the back fixes the
  problem temporarily. That is, until the next unlucky suspend.

  IMPORTANT: if the laptop is never ever suspended, the issue never
  comes back.

  To force the issue to happen, you can either:
  1) Sleep the computer in linux (by closing the lid or any other means).
  2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 
actions or more).
  3) Resume from sleep. You'll note that the battery icon is fixed, and 
unplugging or plugging doesn't update battery status anymore. Also note that 
the ability to suspend by closing the LID is lost.

  OR:
  1) echo disable  /sys/firmware/acpi/interrupts/gpe17
  2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
  3) echo enable  /sys/firmware/acpi/interrupts/gpe17

  WORKAROUND: Turn off the computer, unplug it, hit the reset button in
  the back of the laptop, and then plug it again.

  WORKAROUND (kernel patch 1):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133

  BETTER WORKAROUND (kernel patch 2):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-11-generic 3.13.0-11.31
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2546 F pulseaudio
  CasperVersion: 1.337
  Date: Sat Feb 22 22:57:34 2014
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  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-11-generic N/A
   linux-backports-modules-3.13.0-11-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1289561] [NEW] [TOSHIBA PORTEGE R200] suspend/resume failure

2014-03-07 Thread Frog
Public bug reported:

error to resume  TOSHIBA PORTEGE...

Help Me!

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic i686
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lightdm1208 F pulseaudio
  michele2009 F pulseaudio
Date: Fri Mar  7 09:38:20 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=618a3cd3-759c-47c0-87da-341aa09b7a95
InstallationDate: Installed on 2014-03-01 (6 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
InterpreterPath: /usr/bin/python3.4
MachineType: TOSHIBA PORTEGE R200
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=4644c69d-2931-4155-ae85-485bfcd3f148 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-16-generic N/A
 linux-backports-modules-3.13.0-16-generic  N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [TOSHIBA PORTEGE R200] suspend/resume failure
UpgradeStatus: Upgraded to trusty on 2014-03-01 (5 days ago)
UserGroups:
 
dmi.bios.date: 10/04/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.10
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.10:bd10/04/2006:svnTOSHIBA:pnPORTEGER200:pvrPPR21E-00M00TIT:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE R200
dmi.product.version: PPR21E-00M00TIT
dmi.sys.vendor: TOSHIBA

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


** Tags: apport-kerneloops i386 resume suspend 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/1289561

Title:
  [TOSHIBA PORTEGE R200] suspend/resume failure

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  error to resume  TOSHIBA PORTEGE...

  Help Me!

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1208 F pulseaudio
michele2009 F pulseaudio
  Date: Fri Mar  7 09:38:20 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=618a3cd3-759c-47c0-87da-341aa09b7a95
  InstallationDate: Installed on 2014-03-01 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA PORTEGE R200
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=4644c69d-2931-4155-ae85-485bfcd3f148 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [TOSHIBA PORTEGE R200] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2014-03-01 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 10/04/2006
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.10
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 

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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  [TOSHIBA PORTEGE R200] suspend/resume failure

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  error to resume  TOSHIBA PORTEGE...

  Help Me!

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1208 F pulseaudio
michele2009 F pulseaudio
  Date: Fri Mar  7 09:38:20 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=618a3cd3-759c-47c0-87da-341aa09b7a95
  InstallationDate: Installed on 2014-03-01 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA PORTEGE R200
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=4644c69d-2931-4155-ae85-485bfcd3f148 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [TOSHIBA PORTEGE R200] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2014-03-01 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 10/04/2006
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.10
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.10:bd10/04/2006:svnTOSHIBA:pnPORTEGER200:pvrPPR21E-00M00TIT:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE R200
  dmi.product.version: PPR21E-00M00TIT
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

2014-03-07 Thread Luke
Yeah Thank you devs, thank you Roland, thank you Chris and all of you.
Ok, now I'm gonna try and download the iso...

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

Title:
  Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
  x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Status in “linux” package in Ubuntu:
  Fix Released
Status in “syslinux” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
  loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
  message about missing PAE feature in CPU, but *the same* *Ubuntu
  12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
  kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
  with GRUB boot loader, like Multisystem
  (http://liveusb.info/dotclear/index.php?pages/install ) is used!

  The error message is:
  This kernel requires the following features not present on the CPU: pae.
  Unable to boot - please use a kernel appropriate for you CPU.

  THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully 
use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with 
Pentium M 1700Mhz processor, but the bug in syslinux (or something related) 
forbids Ubuntu 12.04 installation.
  This bug is reproducible on lots of computers, there are several log files 
and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen 
this bug.

  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  MachineType: IBM 2373PPU
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373PPU
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373PPU
  dmi.product.version: ThinkPad T42
  dmi.sys.vendor: IBM

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

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


[Kernel-packages] [Bug 1289559] [NEW] BUG: unable to handle kernel paging request at ffff88006bdcc490

2014-03-07 Thread 188236
Public bug reported:

?

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  christian   1344 F pulseaudio
Date: Fri Mar  7 19:51:21 2014
DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location 0x88006bdcc490
Failure: oops
HibernationDevice: RESUME=UUID=e5d9494f-325a-48a5-9160-59321c4496b1
InstallationDate: Installed on 2014-03-07 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301)
MachineType: Acer Aspire 1810TZ
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=2aea0916-81b0-46c4-8caf-e682fa5eeb2c ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 88006bdcc490
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: v1.3314
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM11-MS
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Aspire 1810TZ
dmi.product.version: v1.3314
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-kerneloops kernel-oops 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/1289559

Title:
  BUG: unable to handle kernel paging request at 88006bdcc490

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1344 F pulseaudio
  Date: Fri Mar  7 19:51:21 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location 0x88006bdcc490
  Failure: oops
  HibernationDevice: RESUME=UUID=e5d9494f-325a-48a5-9160-59321c4496b1
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301)
  MachineType: Acer Aspire 1810TZ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=2aea0916-81b0-46c4-8caf-e682fa5eeb2c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 88006bdcc490
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1289559] Re: BUG: unable to handle kernel paging request at ffff88006bdcc490

2014-03-07 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  BUG: unable to handle kernel paging request at 88006bdcc490

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1344 F pulseaudio
  Date: Fri Mar  7 19:51:21 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location 0x88006bdcc490
  Failure: oops
  HibernationDevice: RESUME=UUID=e5d9494f-325a-48a5-9160-59321c4496b1
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301)
  MachineType: Acer Aspire 1810TZ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=2aea0916-81b0-46c4-8caf-e682fa5eeb2c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 88006bdcc490
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1289559] Re: BUG: unable to handle kernel paging request at ffff88006bdcc490

2014-03-07 Thread 188236
Crashed right at startup

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

Title:
  BUG: unable to handle kernel paging request at 88006bdcc490

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1344 F pulseaudio
  Date: Fri Mar  7 19:51:21 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location 0x88006bdcc490
  Failure: oops
  HibernationDevice: RESUME=UUID=e5d9494f-325a-48a5-9160-59321c4496b1
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301)
  MachineType: Acer Aspire 1810TZ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=2aea0916-81b0-46c4-8caf-e682fa5eeb2c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 88006bdcc490
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

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


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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  BUG: unable to handle kernel paging request at 88006bdcc490

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1344 F pulseaudio
  Date: Fri Mar  7 19:51:21 2014
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location 0x88006bdcc490
  Failure: oops
  HibernationDevice: RESUME=UUID=e5d9494f-325a-48a5-9160-59321c4496b1
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301)
  MachineType: Acer Aspire 1810TZ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=2aea0916-81b0-46c4-8caf-e682fa5eeb2c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 88006bdcc490
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1253155] Re: Failure to validate module signature at boot time

2014-03-07 Thread Andy Whitcroft
Patch for linux-lts-raring  pushed to kernel-team@ for review for SRU.

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

Title:
  Failure to validate module signature at boot time

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-raring” source package in Precise:
  In Progress
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux-lts-raring” source package in Trusty:
  Invalid

Bug description:
  When booting under secureboot and using a signed kernel, it's expected
  that all modules shipped alongside the kernel should validate and load
  successfully without tainting the kernel.

  Unfortunately it doesn't seem to always be the case. Looking through
  my kernel logs, I see:

  Nov 15 10:35:24 castiana kernel: [1.635132] video: module
  verification failed: signature and/or required key missing - tainting
  kernel

  or

  Nov 12 12:58:48 castiana kernel: [213981.753326] Request for unknown
  module key 'Magrathea: Glacier signing key:
  f440a253eb498df923d438caa09b3b5d99308405' err -11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stgraber   2721 F pulseaudio
   /dev/snd/controlC0:  stgraber   2721 F pulseaudio
   /dev/snd/pcmC0D0c:   stgraber   2721 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stgraber   2721 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 20 11:59:57 2013
  InstallationDate: Installed on 2013-04-21 (213 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420)
  MachineType: LENOVO 2306CT0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic.efi.signed 
root=UUID=14de4e20-b139-488e-863f-ec710f776851 ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CT0
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET96WW(2.56):bd08/27/2013:svnLENOVO:pn2306CT0:pvrThinkPadX230:rvnLENOVO:rn2306CT0:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CT0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1289518] Re: Hotplug of virtio(block/net) devices not detected inside ppc64el guest

2014-03-07 Thread Joseph Salisbury
** Tags added: kernel-key ppc64el 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/1289518

Title:
  Hotplug of virtio(block/net) devices not detected inside ppc64el guest

Status in “linux” package in Ubuntu:
  Triaged
Status in “powerpc-ibm-utils” package in Ubuntu:
  Triaged
Status in “linux” source package in Trusty:
  Triaged
Status in “powerpc-ibm-utils” source package in Trusty:
  Triaged

Bug description:
  On ppc64el, a kernel patch and a userspace patch are needed to have
  hotplugging of devices via e.g. 'virsh attach-interface' properly
  detected by a guest kernel.

http://sourceforge.net/p/powerpc-utils/mailman/message/32064992/
http://patchwork.ozlabs.org/patch/327089/

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

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


[Kernel-packages] [Bug 1272777] Re: Elantech touchpads not fully supported for some Gigabyte laptops

2014-03-07 Thread nicobrainless
I have a mouse too, but when you're on the go it is frustrating not to
get scrolling... sigh.

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

Title:
  Elantech touchpads not fully supported for some Gigabyte laptops

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This bug report is in addition to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442 - the
  fixes suggested there (which work for others) have been tried but do
  not work for a small subset of laptops, particularly the Gigabyte
  U2442 series.

  Description of the situation for my Gigabyte U2442V most recently
  running 3.11.0-12-generic on Linux Mint.

  I tried the updated module mentioned in the above bug report (1166442). It 
compiles and it detects an Elantech trackpad of *indeterminate version*.  I get 
this in dmesg:
  [859697.496141] psmouse serio1: elantech: assuming hardware version 3 (with 
firmware version 0x450f01)
  [859697.526011] psmouse serio1: elantech: Synaptics capabilities query result 
0x58, 0x17, 0x0c.
  [859697.765917] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
  [859698.470556] psmouse serio1: elantech: retrying ps2 command 0x0b (1).

  I get no Synaptics driver functionality, and only basic touchpad
  behaviour (motion and tap-to-click for left click, no scroll or
  disabling the pad when typing, etc.).

  It seems I don't have a v9 or v10 trackpad, I've never been able to
  get a definitive indication of which version I have got.

  The only thing that has remedied this problem for me in the past was
  the one described in the original bug report (for elantech-v6 -
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64)... but it no longer applies to newer
  kernels...

  With the 3.11.0-12-generic kernel, my Touchpad *is* detected, i.e. xinput 
shows:
↳ PS/2 Elantech Touchpad id=16 [slave pointer (2)]
  and dmesg shows:
   input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input14

  There are no useful touchpads settings evident in the normal Cinnamon
  settings utility (gnome-control-center - Mouse  Touchpads).  I see a
  touchpad settings option with the gpointing-device-settings app and
  I can turn on vertical and horizontal scrolling in the interface, but
  doing so does not in any way affect that actual touchpad behaviour.

  I've also tried installing the elantech-v7 module via dkms (see 
http://ubuntuforums.org/showthread.php?t=2111236p=12850603#post12850603) and 
it compiles, but it too fails to provide the desired functionality.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=29b0358f-f728-4aea-bce5-e233816f27b1
  InstallationDate: Installed on 2013-12-11 (46 days ago)
  InstallationMedia: Linux Mint 16 petra - Release amd64 20131126
  MachineType: GIGABYTE U2442
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=83fd94b8-53eb-4e68-9eeb-cf2e017cbe0d ro quiet splash vt.handoff=7
  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:  petra
  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: 10/26/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U2442.F306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U2442
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU2442.F306:bd10/26/2012:svnGIGABYTE:pnU2442:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU2442:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: U2442
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

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


[Kernel-packages] [Bug 1289587] [NEW] [FUJITSU LIFEBOOK AH531] suspend/resume failure

2014-03-07 Thread Chris H
Public bug reported:

blank screen, doesn't wake up

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  harsesus   2608 F pulseaudio
Date: Fri Mar  7 15:53:16 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=fa2ca9ea-f2d2-4c29-8a4f-de4e5296f1f4
InstallationDate: Installed on 2014-01-01 (65 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/python3.4
MachineType: FUJITSU LIFEBOOK AH531
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=f86a2792-35fb-47e4-8e6c-671043d612a6 ro plymouth:splash quiet 
plymouth: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.13.0-16-generic N/A
 linux-backports-modules-3.13.0-16-generic  N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [FUJITSU LIFEBOOK AH531] suspend/resume failure
UpgradeStatus: Upgraded to trusty on 2014-03-06 (1 days ago)
UserGroups:
 
dmi.bios.date: 05/05/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: 1.20
dmi.board.name: FJNBB0F
dmi.board.vendor: FUJITSU
dmi.chassis.type: 9
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr1.20:bd05/05/2011:svnFUJITSU:pnLIFEBOOKAH531:pvr:rvnFUJITSU:rnFJNBB0F:rvr:cvnFUJITSU:ct9:cvr:
dmi.product.name: LIFEBOOK AH531
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-kerneloops resume suspend third-party-packages trusty

** Attachment added: lspci-vnvn.log
   
https://bugs.launchpad.net/bugs/1289587/+attachment/4012535/+files/lspci-vnvn.log

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

Title:
  [FUJITSU LIFEBOOK AH531] suspend/resume failure

Status in “linux” package in Ubuntu:
  New

Bug description:
  blank screen, doesn't wake up

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  harsesus   2608 F pulseaudio
  Date: Fri Mar  7 15:53:16 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=fa2ca9ea-f2d2-4c29-8a4f-de4e5296f1f4
  InstallationDate: Installed on 2014-01-01 (65 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK AH531
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=f86a2792-35fb-47e4-8e6c-671043d612a6 ro plymouth:splash quiet 
plymouth: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.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK AH531] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2014-03-06 (1 days ago)
  UserGroups:
   
  dmi.bios.date: 05/05/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB0F
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 9
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr1.20:bd05/05/2011:svnFUJITSU:pnLIFEBOOKAH531:pvr:rvnFUJITSU:rnFJNBB0F:rvr:cvnFUJITSU:ct9:cvr:
  dmi.product.name: LIFEBOOK AH531
  dmi.sys.vendor: FUJITSU

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

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

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

2014-03-07 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  [FUJITSU LIFEBOOK AH531] suspend/resume failure

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  blank screen, doesn't wake up

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  harsesus   2608 F pulseaudio
  Date: Fri Mar  7 15:53:16 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=fa2ca9ea-f2d2-4c29-8a4f-de4e5296f1f4
  InstallationDate: Installed on 2014-01-01 (65 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK AH531
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=f86a2792-35fb-47e4-8e6c-671043d612a6 ro plymouth:splash quiet 
plymouth: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.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK AH531] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2014-03-06 (1 days ago)
  UserGroups:
   
  dmi.bios.date: 05/05/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB0F
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 9
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr1.20:bd05/05/2011:svnFUJITSU:pnLIFEBOOKAH531:pvr:rvnFUJITSU:rnFJNBB0F:rvr:cvnFUJITSU:ct9:cvr:
  dmi.product.name: LIFEBOOK AH531
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1272777] Re: Elantech touchpads not fully supported for some Gigabyte laptops

2014-03-07 Thread Martin Pitak
i says Incomplete for me

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

Title:
  Elantech touchpads not fully supported for some Gigabyte laptops

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This bug report is in addition to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442 - the
  fixes suggested there (which work for others) have been tried but do
  not work for a small subset of laptops, particularly the Gigabyte
  U2442 series.

  Description of the situation for my Gigabyte U2442V most recently
  running 3.11.0-12-generic on Linux Mint.

  I tried the updated module mentioned in the above bug report (1166442). It 
compiles and it detects an Elantech trackpad of *indeterminate version*.  I get 
this in dmesg:
  [859697.496141] psmouse serio1: elantech: assuming hardware version 3 (with 
firmware version 0x450f01)
  [859697.526011] psmouse serio1: elantech: Synaptics capabilities query result 
0x58, 0x17, 0x0c.
  [859697.765917] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
  [859698.470556] psmouse serio1: elantech: retrying ps2 command 0x0b (1).

  I get no Synaptics driver functionality, and only basic touchpad
  behaviour (motion and tap-to-click for left click, no scroll or
  disabling the pad when typing, etc.).

  It seems I don't have a v9 or v10 trackpad, I've never been able to
  get a definitive indication of which version I have got.

  The only thing that has remedied this problem for me in the past was
  the one described in the original bug report (for elantech-v6 -
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64)... but it no longer applies to newer
  kernels...

  With the 3.11.0-12-generic kernel, my Touchpad *is* detected, i.e. xinput 
shows:
↳ PS/2 Elantech Touchpad id=16 [slave pointer (2)]
  and dmesg shows:
   input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input14

  There are no useful touchpads settings evident in the normal Cinnamon
  settings utility (gnome-control-center - Mouse  Touchpads).  I see a
  touchpad settings option with the gpointing-device-settings app and
  I can turn on vertical and horizontal scrolling in the interface, but
  doing so does not in any way affect that actual touchpad behaviour.

  I've also tried installing the elantech-v7 module via dkms (see 
http://ubuntuforums.org/showthread.php?t=2111236p=12850603#post12850603) and 
it compiles, but it too fails to provide the desired functionality.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=29b0358f-f728-4aea-bce5-e233816f27b1
  InstallationDate: Installed on 2013-12-11 (46 days ago)
  InstallationMedia: Linux Mint 16 petra - Release amd64 20131126
  MachineType: GIGABYTE U2442
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=83fd94b8-53eb-4e68-9eeb-cf2e017cbe0d ro quiet splash vt.handoff=7
  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:  petra
  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: 10/26/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U2442.F306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U2442
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU2442.F306:bd10/26/2012:svnGIGABYTE:pnU2442:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU2442:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: U2442
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

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


[Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

2014-03-07 Thread Christiansen
This is absolutly amasing news guyes, had lost any hope that this status
on this bug would ever change. Thankyou to the most persistent advocats
arguing this bug should be solved, and not least to Chris and others
involved in figuring out howto...

After reciving these great news, the first thing I did was to download the 
Kubuntu Trusty daily image (2014.03.06) from cdimages.ubunut.com. Used a 
12.04.4 box an flashed the Trusty ISO to an USB stick, using the Start Disk 
Creator a so often before. Booting my good old ThinkPad R51 from the USB 
stick, just to eksperience the your CPU i not supported ... no PAE. Restarded 
the R51 and added the kernel forcepae parameter to the syslinux parameter 
line.
Things looked excactly the same as so often before, installing any sort of 
12.04 ubuntu flavors. Back to the other ubuntu box, re-fdisk and format the 
USB, Start Disk Creator and then ever so often used grub2 installation to USB 
when creating 12.04.x USBs for older hardware: 

 sudo grub-install --recheck --boot-directory /media/usb-stick/boot /dev/sdX
 nano /media/usb-stick/boot/grub.cfg

menuentry 'Start Kubuntu' --class ubuntu --class gnu-linux --class gnu --class 
os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
echo'Indlaeser Linux 3.13.0-16-generic-pae ...'
linux   /casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper 
maybe-ubiquity quiet splash --
echo'Indlaeser startramdisk ...'
initrd  /casper/initrd.lz
}

Returned the stick to the good old R51, at it just booted from the USB
like a charm - just amasing. So right now upgrades from Precise to
Trusty should work correct ?, but the old syslinux original of this
bug still persist right ?.

So new users, and users unaware of this bug, will still experienc
problems booting CDs or USB sticks created from ISOs, which with all the
good work and all the posting above seems almost unbearable to me...

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

Title:
  Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
  x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Status in “linux” package in Ubuntu:
  Fix Released
Status in “syslinux” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
  loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
  message about missing PAE feature in CPU, but *the same* *Ubuntu
  12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
  kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
  with GRUB boot loader, like Multisystem
  (http://liveusb.info/dotclear/index.php?pages/install ) is used!

  The error message is:
  This kernel requires the following features not present on the CPU: pae.
  Unable to boot - please use a kernel appropriate for you CPU.

  THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully 
use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with 
Pentium M 1700Mhz processor, but the bug in syslinux (or something related) 
forbids Ubuntu 12.04 installation.
  This bug is reproducible on lots of computers, there are several log files 
and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen 
this bug.

  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  MachineType: IBM 2373PPU
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373PPU
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373PPU
  dmi.product.version: ThinkPad T42
  dmi.sys.vendor: IBM

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

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


[Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

2014-03-07 Thread roland aus köln
Restarded the R51 and added the kernel forcepae parameter to the syslinux 
parameter line.
Things looked excactly the same as so often before, installing any sort of 
12.04 ubuntu flavors.
but the old syslinux original of this bug still persist right ?.

No, it shouldn`t.

If booted via syslinux and adding forcepae as a bootparam, it should
boot - regardless if being botted via grub 16-bit mode or via syslinux
or whatever.

could you please re-check if you typed it correctly?

does your method of creating a bootable iso really use the kernel from
the recent cd-image, or maybe there`s an older kernel in place?

if that fails for you and if you are that your cpu does have pae, please
post the contents of /proc/cpuinfo.

you may attach an usb cd-rom to your r51 and try to directly boot from
that.

i´m curious what`s going wrong here.

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

Title:
  Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
  x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Status in “linux” package in Ubuntu:
  Fix Released
Status in “syslinux” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
  loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
  message about missing PAE feature in CPU, but *the same* *Ubuntu
  12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
  kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
  with GRUB boot loader, like Multisystem
  (http://liveusb.info/dotclear/index.php?pages/install ) is used!

  The error message is:
  This kernel requires the following features not present on the CPU: pae.
  Unable to boot - please use a kernel appropriate for you CPU.

  THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully 
use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with 
Pentium M 1700Mhz processor, but the bug in syslinux (or something related) 
forbids Ubuntu 12.04 installation.
  This bug is reproducible on lots of computers, there are several log files 
and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen 
this bug.

  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  MachineType: IBM 2373PPU
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373PPU
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373PPU
  dmi.product.version: ThinkPad T42
  dmi.sys.vendor: IBM

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

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


[Kernel-packages] [Bug 1272777] Re: Elantech touchpads not fully supported for some Gigabyte laptops

2014-03-07 Thread lightweight
** 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/1272777

Title:
  Elantech touchpads not fully supported for some Gigabyte laptops

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This bug report is in addition to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442 - the
  fixes suggested there (which work for others) have been tried but do
  not work for a small subset of laptops, particularly the Gigabyte
  U2442 series.

  Description of the situation for my Gigabyte U2442V most recently
  running 3.11.0-12-generic on Linux Mint.

  I tried the updated module mentioned in the above bug report (1166442). It 
compiles and it detects an Elantech trackpad of *indeterminate version*.  I get 
this in dmesg:
  [859697.496141] psmouse serio1: elantech: assuming hardware version 3 (with 
firmware version 0x450f01)
  [859697.526011] psmouse serio1: elantech: Synaptics capabilities query result 
0x58, 0x17, 0x0c.
  [859697.765917] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
  [859698.470556] psmouse serio1: elantech: retrying ps2 command 0x0b (1).

  I get no Synaptics driver functionality, and only basic touchpad
  behaviour (motion and tap-to-click for left click, no scroll or
  disabling the pad when typing, etc.).

  It seems I don't have a v9 or v10 trackpad, I've never been able to
  get a definitive indication of which version I have got.

  The only thing that has remedied this problem for me in the past was
  the one described in the original bug report (for elantech-v6 -
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64)... but it no longer applies to newer
  kernels...

  With the 3.11.0-12-generic kernel, my Touchpad *is* detected, i.e. xinput 
shows:
↳ PS/2 Elantech Touchpad id=16 [slave pointer (2)]
  and dmesg shows:
   input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input14

  There are no useful touchpads settings evident in the normal Cinnamon
  settings utility (gnome-control-center - Mouse  Touchpads).  I see a
  touchpad settings option with the gpointing-device-settings app and
  I can turn on vertical and horizontal scrolling in the interface, but
  doing so does not in any way affect that actual touchpad behaviour.

  I've also tried installing the elantech-v7 module via dkms (see 
http://ubuntuforums.org/showthread.php?t=2111236p=12850603#post12850603) and 
it compiles, but it too fails to provide the desired functionality.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=29b0358f-f728-4aea-bce5-e233816f27b1
  InstallationDate: Installed on 2013-12-11 (46 days ago)
  InstallationMedia: Linux Mint 16 petra - Release amd64 20131126
  MachineType: GIGABYTE U2442
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=83fd94b8-53eb-4e68-9eeb-cf2e017cbe0d ro quiet splash vt.handoff=7
  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:  petra
  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: 10/26/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U2442.F306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U2442
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU2442.F306:bd10/26/2012:svnGIGABYTE:pnU2442:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU2442:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: U2442
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

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


[Kernel-packages] [Bug 1252422] Re: CVE-2013-4579

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

Title:
  CVE-2013-4579

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:
  Fix Released
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:
  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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:
  Invalid
Status in “linux-ti-omap4” source package in Trusty:
  Invalid

Bug description:
  The 

[Kernel-packages] [Bug 1261564] Re: CVE-2013-4587

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

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

Title:
  CVE-2013-4587

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 Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
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 Released
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:
  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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:

[Kernel-packages] [Bug 703180] Re: 197b:2391 SD card reader inaccessible without pci bus rescan

2014-03-07 Thread Daniel Kessel
This seems to be fixed in the currenty trusty daily image. It just works
out-of-the-box.

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

Title:
  197b:2391 SD card reader inaccessible without pci bus rescan

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

Bug description:
  This is a Dell XPS L501X laptop (the new ones with USB3 etc:
  http://www.dell.com/us/p/xps-15/pd.aspx)

  The card reader neither shows up in lspci nor in lsusb (only device
  connected via USB seems to be the internal webcam which works), so I
  can't even figure out which model it is…

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-2.6.35-24-generic-pae 2.6.35-24.42
  Regression: No
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
  Uname: Linux 2.6.35-24-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC665 Analog [ALC665 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal 1777 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf090 irq 49'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0665,1028046e,0013 
HDA:80862804,80860101,0010'
 Controls  : 29
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xadefc000 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Sat Jan 15 05:06:50 2011
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=e7d13dad-6e7f-4320-8b4f-98e29cfde6f0
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0408:2fb1 Quanta Computer, Inc. 
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS L501X
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic-pae 
root=UUID=b8eb30a4-6bd4-4d52-b356-8cb3431ba849 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: linux-firmware 1.38.3
  SourcePackage: linux
  dmi.bios.date: 11/26/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 00CKNG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/26/2010:svnDellInc.:pnXPSL501X:pvrA04:rvnDellInc.:rn00CKNG:rvrA04:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: XPS L501X
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1276725] Re: package firmware-b43-installer 1:017-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 zurück

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

** Changed in: b43-fwcutter (Ubuntu)
   Status: New = Confirmed

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

Title:
  package firmware-b43-installer 1:017-2 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  8 zurück

Status in “b43-fwcutter” package in Ubuntu:
  Confirmed

Bug description:
  My Wificard is a
  05:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g 
LP-PHY [14e4:4315] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04b5]
Kernel driver in use: b43-pci-bridge

  The firmware-b43-installer should make it work. Unfortunately it brakes the 
installation with
  firmware-b43-installer (1:017-2) wird eingerichtet ...
  No chroot environment found. Starting normal installation
  --2014-02-05 18:48:24--  
http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
  Verbindungsaufbau zu 192.168.0.1:3142... verbunden.
  Proxy-Anforderung gesendet, warte auf Antwort... 403 Sorry, not allowed to 
fetch that type of file: broadcom-wl-5.100.138.tar.bz2
  2014-02-05 18:48:24 FEHLER 403: Sorry, not allowed to fetch that type of 
file: broadcom-wl-5.100.138.tar.bz2.
  dpkg: Fehler beim Bearbeiten von firmware-b43-installer (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 
zurück
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I think it depends on the apt-cacher-ng on my server.
  I will try to install it without the proxy.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: firmware-b43-installer 1:017-2
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  AptOrdering:
   b43-fwcutter: Install
   firmware-b43-installer: Install
   b43-fwcutter: Configure
   firmware-b43-installer: Configure
  Architecture: i386
  Date: Wed Feb  5 18:48:24 2014
  DuplicateSignature: package:firmware-b43-installer:1:017-2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 8 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 8 zurück
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: b43-fwcutter
  Title: package firmware-b43-installer 1:017-2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1276725/+subscriptions

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


[Kernel-packages] [Bug 1276725] Re: package firmware-b43-installer 1:017-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 zurück

2014-03-07 Thread Jernej Jakob
Exact same problem here. Only APT is set to use the proxy in 
/etc/apt/apt.conf.d/01proxy:
Acquire::http::Proxy http://apt-cacher.lan:3142/;;
System-wide proxy is disabled.

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

Title:
  package firmware-b43-installer 1:017-2 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  8 zurück

Status in “b43-fwcutter” package in Ubuntu:
  Confirmed

Bug description:
  My Wificard is a
  05:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g 
LP-PHY [14e4:4315] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04b5]
Kernel driver in use: b43-pci-bridge

  The firmware-b43-installer should make it work. Unfortunately it brakes the 
installation with
  firmware-b43-installer (1:017-2) wird eingerichtet ...
  No chroot environment found. Starting normal installation
  --2014-02-05 18:48:24--  
http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
  Verbindungsaufbau zu 192.168.0.1:3142... verbunden.
  Proxy-Anforderung gesendet, warte auf Antwort... 403 Sorry, not allowed to 
fetch that type of file: broadcom-wl-5.100.138.tar.bz2
  2014-02-05 18:48:24 FEHLER 403: Sorry, not allowed to fetch that type of 
file: broadcom-wl-5.100.138.tar.bz2.
  dpkg: Fehler beim Bearbeiten von firmware-b43-installer (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 
zurück
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I think it depends on the apt-cacher-ng on my server.
  I will try to install it without the proxy.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: firmware-b43-installer 1:017-2
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  AptOrdering:
   b43-fwcutter: Install
   firmware-b43-installer: Install
   b43-fwcutter: Configure
   firmware-b43-installer: Configure
  Architecture: i386
  Date: Wed Feb  5 18:48:24 2014
  DuplicateSignature: package:firmware-b43-installer:1:017-2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 8 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 8 zurück
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: b43-fwcutter
  Title: package firmware-b43-installer 1:017-2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1276725/+subscriptions

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


[Kernel-packages] [Bug 1261566] Re: CVE-2013-6367

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

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

Title:
  CVE-2013-6367

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 Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
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 Released
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:
  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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:

[Kernel-packages] [Bug 1261568] Re: CVE-2013-6368

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

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

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

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

Title:
  CVE-2013-6368

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:
  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:
  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 Released
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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in 

[Kernel-packages] [Bug 1253100] Re: Intel Centrino Adv. N 6230 Wireless doesn't wake up again after suspend-to-RAM since Upgrade to 13.10

2014-03-07 Thread Tobias Vogel
Yes, absolutely - this happens always after a suspend-to-ram. 
I don't really know how this bug could be fixed when you can't reproduce the 
bug on your side; what additional information can I provide?

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

Title:
  Intel Centrino Adv. N 6230 Wireless doesn't wake up again after
  suspend-to-RAM since Upgrade to 13.10

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Since I upgraded from Ubuntu 13.04 to Ubuntu 13.10, Wireless isn't working 
any more after suspend-to-RAM.
  I'm using the amd64 version of Ubuntu on my Samsung NP900X3A-B03CH Ultrabook.
  The Wireless-device is a (according to lspci)

  Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak]

  This is what /var/log/syslog shows:

  Nov 20 15:08:07 900X3A kernel: [   32.372384] samsung_laptop: detected SABI 
interface: SwSmi@
  Nov 20 15:08:07 900X3A kernel: [   32.372390] samsung_laptop: Backlight 
controlled by ACPI video driver
  Nov 20 15:08:07 900X3A NetworkManager[1851]: info rfkill2: found WiFi radio 
killswitch (at /sys/devices/platform/samsung/rfkill/rfkill2) (platform driver 
(unknown))
  Nov 20 15:08:09 90X03A NetworkManager[1851]: info (wlan0): IP6 addrconf 
timed out or failed.
  Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 
4 of 5 (IPv6 Configure Timeout) scheduled...
  Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 
4 of 5 (IPv6 Configure Timeout) started...
  Nov 20 15:08:09 900X3A NetworkManager[1851]: info Activation (wlan0) Stage 
4 of 5 (IPv6 Configure Timeout) complete.

  I'm rather surprised though, about this message  rfkill2: found WiFi radio 
killswitch (at /sys/devices/platform/samsung/rfkill/rfkill2) (platform driver 
(unknown))
  as the Computer doesn't have any hardware wifi-switch...?

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

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


[Kernel-packages] [Bug 1256091] Re: CVE-2013-6382

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

Title:
  CVE-2013-6382

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 Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
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 Released
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:
  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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Committed
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:
  Invalid
Status in “linux-ti-omap4” source package in Trusty:
  Invalid

Bug description:
  

[Kernel-packages] [Bug 1172755] Re: 13.04 Kernel Panic Not Syncing - Attempted to kill init - error code= 0x0000009

2014-03-07 Thread Timothy J. Niblett
** Changed in: linux (Ubuntu)
   Status: Invalid = 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/1172755

Title:
  13.04 Kernel Panic Not Syncing - Attempted to kill init - error code=
  0x009

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm having an issue booting 13.04. I did a search on the forum but
  nothing popped up. Basically, it installs fine but upon a reboot into
  the installation I get a kernel panic: not syncing: Attempted to kill
  exitcode=0x0009.

  Hardware:

  Processor Quad-Core AMD A8-4500M processor (1.9 GHz, 2.8 GHz with 
Turboboost, 4 MB L2 cache)
  Operating System  Windows 8
  RAM   8 GB (2 x 4 GB)
  Graphics card AMD Radeon HD 7640G Discrete-Class
  up to 4.98 GB of dedicated RAM
  Screen type   HD BrightView LED-backlit
  Screen resolution 1366 x 768
  Screen size   15.6
  Screen features   LED backlit
  Hard drive1 TB (SATA, 5400 rpm)
  Optical disk driveSuperMulti DVD±R/RW with double layer support
  Memory card readerDigital media card reader
  USB   2 x USB 2.0
  1 x USB 3.0
  FireWire  No
  Modem/EthernetIntegrated 10/100 BASE-T Ethernet LAN
  WiFi  802.11b/g/n
  Bluetooth No
  TV output VGA
  HDMI
  Expansion card slot   No
  Sound Altec Lansing speakers with Dolby Advanced Audio
  Dolby Advanced Audio

  Thanks

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

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


[Kernel-packages] [Bug 1267078] Re: CVE-2013-7264

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

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

Title:
  CVE-2013-7264

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 Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
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 Released
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:
  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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:

[Kernel-packages] [Bug 1267075] Re: CVE-2013-7263

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

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

Title:
  CVE-2013-7263

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 Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
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 Released
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:
  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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:

[Kernel-packages] [Bug 1267079] Re: CVE-2013-7265

2014-03-07 Thread John Johansen
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

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

Title:
  CVE-2013-7265

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 Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
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 Released
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:
  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:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
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:
  Fix Released
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” source package in Saucy:
  Fix Released
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:
  Fix Released
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 Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:

[Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

2014-03-07 Thread Christiansen
@roland #291

Booting Kubuntu Trusty from either USB or DVD (Kubuntu  700MB):
Daily ISO 2014.03.06 = Kernel: Linux kubuntu 3.13.0-15-generic #35-Ubuntu SMP  
= not working
Daily ISO 2014.03.07 = Kernel: Linux kubuntu 3.13.0-16-generic #36-Ubuntu SMP  
= working (without grub BL)

I'm very sorry for this mistake, reported 1 day to soon then...

Just downloaded the Kubuntu Trusty 2014.03.07, and it boots just fine
with syslinux + forcepae (with the 3.13.0-16-generic #36 kernel). Even
though booting (and installing) theese old boxes from buildin IDE-DVD
takes forever compared to USB stik (less than 2 minutes boot).

Thanks for the very fast response, and sorry for not dobbelt checking
the kernel version. We (users) are no even precentet with instructions
on how to boot these Pentium boxes, if omitting the forcepae parameter -
very polished indeed.

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

Title:
  Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
  x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Status in “linux” package in Ubuntu:
  Fix Released
Status in “syslinux” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
  loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
  message about missing PAE feature in CPU, but *the same* *Ubuntu
  12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
  kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
  with GRUB boot loader, like Multisystem
  (http://liveusb.info/dotclear/index.php?pages/install ) is used!

  The error message is:
  This kernel requires the following features not present on the CPU: pae.
  Unable to boot - please use a kernel appropriate for you CPU.

  THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully 
use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with 
Pentium M 1700Mhz processor, but the bug in syslinux (or something related) 
forbids Ubuntu 12.04 installation.
  This bug is reproducible on lots of computers, there are several log files 
and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen 
this bug.

  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  MachineType: IBM 2373PPU
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373PPU
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373PPU
  dmi.product.version: ThinkPad T42
  dmi.sys.vendor: IBM

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

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


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

2014-03-07 Thread Pops
apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1289128/+attachment/4012866/+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/1289128

Title:
  External laptop speakers work only for several minutes then shut off

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 16 Petra  Ubuntu 13.04 and 13.10
  Toshiba Satellite L655-S5150
  Running lates version of BIOS

  I can't get my laptop speakers to stay running.

  What happens is that when I first start up my laptop, sound will come out of 
the speakers for 2-3 minutes and then stop. If I reboot it will come back on 
for 2-3 minutes again. My headphones work fine for as long as I want them to 
play. I also tried the Auto Mute - disable idea that is mentioned in many of 
the posts by people with the same problem.
  One weird thing is that if I close my laptop and let it go into suspend then 
open it back up, the sound comes back on for 2-3 minutes. I tested the power 
settings on this. If I have my laptop set up to go into suspend when I close 
the lid (Under the “When Plugged In” settings) , the sound comes back on. If I 
have my power setting for “When the Lid is Closed” set to “Do Nothing” (under 
the “When Plugged In” settings) and close the lid, the sound does NOT come back 
on. Same scenario if I go onto battery power (comes back on if set to suspend). 
This issue seems to be tied to the suspend / power settings somehow. Just now I 
shut the lid and re-opend it and the sound played for 1 minutes and 27 seconds 
before cutting off again.

  On another note, this system is dual boot so I started up Windows and
  ran Media Player for about an hour and the sound played the entire
  time. This would rule out a true hardware fault.

  I have run the command wget http://www.alsa-project.org/alsa-info.sh
  -O alsa-info.sh  bash alsa-info.sh and saved the information
  locally. It creates a folder with sub folders so I'm not sure what I
  should upload.

  I tried installing DKMS under Mint 16 but it didn't appear to work and
  I don't have Ubuntu installed on my system any longer.

  I'm willing to try any troubleshooting steps you need to assist in
  fixing this problem. Here is some more information below.

  
  Info from sudo aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  ***
  Output from lspci -v | grep -A7 -i audio
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
Subsystem: Toshiba America Info Systems Device fd50
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at d640 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
  
  This page (https://help.ubuntu.com/community/SoundTroubleshooting) said to 
run modprobe on my sound driver. I couldn't figure out what my driver was so I 
was never able to do that step.

  sudo modprobe snd-[NAME OF YOUR SOUNDCARD'S DRIVER]
  **
  ubuntu-bug -s audio returns the following error

  *** Error: Unknown symptom

  The symptom audio is not known.
  
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pops   1634 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=727b1e07-0e76-4ff5-8dae-72ee7fd3e405
  InstallationDate: Installed on 2014-01-06 (60 days ago)
  InstallationMedia: Linux Mint 16 petra - Release amd64 20131126
  MachineType: TOSHIBA Satellite L655
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=663d6c75-af4d-4f5d-8b09-21f0bf1ecbda 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: Home directory not 
accessible: 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.2
  RfKill:
   0: phy0: Wireless LAN
 

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

2014-03-07 Thread Pops
apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1289128/+attachment/4012871/+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/1289128

Title:
  External laptop speakers work only for several minutes then shut off

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 16 Petra  Ubuntu 13.04 and 13.10
  Toshiba Satellite L655-S5150
  Running lates version of BIOS

  I can't get my laptop speakers to stay running.

  What happens is that when I first start up my laptop, sound will come out of 
the speakers for 2-3 minutes and then stop. If I reboot it will come back on 
for 2-3 minutes again. My headphones work fine for as long as I want them to 
play. I also tried the Auto Mute - disable idea that is mentioned in many of 
the posts by people with the same problem.
  One weird thing is that if I close my laptop and let it go into suspend then 
open it back up, the sound comes back on for 2-3 minutes. I tested the power 
settings on this. If I have my laptop set up to go into suspend when I close 
the lid (Under the “When Plugged In” settings) , the sound comes back on. If I 
have my power setting for “When the Lid is Closed” set to “Do Nothing” (under 
the “When Plugged In” settings) and close the lid, the sound does NOT come back 
on. Same scenario if I go onto battery power (comes back on if set to suspend). 
This issue seems to be tied to the suspend / power settings somehow. Just now I 
shut the lid and re-opend it and the sound played for 1 minutes and 27 seconds 
before cutting off again.

  On another note, this system is dual boot so I started up Windows and
  ran Media Player for about an hour and the sound played the entire
  time. This would rule out a true hardware fault.

  I have run the command wget http://www.alsa-project.org/alsa-info.sh
  -O alsa-info.sh  bash alsa-info.sh and saved the information
  locally. It creates a folder with sub folders so I'm not sure what I
  should upload.

  I tried installing DKMS under Mint 16 but it didn't appear to work and
  I don't have Ubuntu installed on my system any longer.

  I'm willing to try any troubleshooting steps you need to assist in
  fixing this problem. Here is some more information below.

  
  Info from sudo aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  ***
  Output from lspci -v | grep -A7 -i audio
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
Subsystem: Toshiba America Info Systems Device fd50
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at d640 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
  
  This page (https://help.ubuntu.com/community/SoundTroubleshooting) said to 
run modprobe on my sound driver. I couldn't figure out what my driver was so I 
was never able to do that step.

  sudo modprobe snd-[NAME OF YOUR SOUNDCARD'S DRIVER]
  **
  ubuntu-bug -s audio returns the following error

  *** Error: Unknown symptom

  The symptom audio is not known.
  
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pops   1634 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=727b1e07-0e76-4ff5-8dae-72ee7fd3e405
  InstallationDate: Installed on 2014-01-06 (60 days ago)
  InstallationMedia: Linux Mint 16 petra - Release amd64 20131126
  MachineType: TOSHIBA Satellite L655
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=663d6c75-af4d-4f5d-8b09-21f0bf1ecbda 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: Home directory not 
accessible: 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.2
  RfKill:
   0: phy0: Wireless LAN
Soft 

  1   2   >