date:20150913

tests ran:  71, failed: 69;
  
http://kernel.ubuntu.com/testing/3.16.0-50.66~14.04.1/cavac__3.16.0-50.66~14.04.1__2015-09-13_06-02-00/results-index.html

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

Title:
  linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 10. September 2015 15:32 UTC
  kernel-stable-Prepare-package-end:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 11. September 2015 19:24 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Verification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Certification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-start:Friday, 11. September 2015 21:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. September 2015 08:01 UTC

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

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

[Kernel-packages] [Bug 1410384] tarf (i386) - tests ran: 153, failed: 0

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/tarf__3.13.0-64.104__2015-09-13_08-41-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1495116] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1495116/+attachment/4462934/+files/Dependencies.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/1495116

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64

[Kernel-packages] [Bug 1495116] IwConfig.txt

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus: Upgraded to

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus: Upgraded to

[Kernel-packages] [Bug 1495116] AlsaInfo.txt

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1495116/+attachment/4462931/+files/AlsaInfo.txt

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

The problem is also present after an upgrade to 15.04 (Vivid) with:

linux-image-3.19.0-28-generic:amd64
linux-image-extra-3.19.0-28-generic:amd64
systemd-219-7ubuntu6 (i386)

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Tags removed: third-party-packages
** Tags added: vivid

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A

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

This change was made by a bot.

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

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

Title:
  BUG: unable to handle kernel paging request at 34c03000

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System freez after upgrade, while browsing in firefox and shotr after
  removing of flashdrive.

  I can not determine what causr freez.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clon   1561 F pulseaudio
   /dev/snd/seq:timidity771 F timidity
  Date: Sun Sep 13 09:36:30 2015
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location __percpu_counter_add+0x14/0xa0 SS:ESP 0068:e75b5dc0
  Failure: oops
  HibernationDevice: RESUME=UUID=7487f502-5343-4e22-b4cf-6decd3b11281
  InstallationDate: Installed on 2013-03-16 (911 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=/dev/mapper/lubuntu-root ro plymouth:debug splash quiet drm.debug=0xe 
plymouth:debug=1=1
  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-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 34c03000
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2005
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: K8T800-8237
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/25/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnK8T800-8237:rvr1.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1495184] Re: BUG: unable to handle kernel paging request at 34c03000

2015-09-13 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/1495184

Title:
  BUG: unable to handle kernel paging request at 34c03000

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System freez after upgrade, while browsing in firefox and shotr after
  removing of flashdrive.

  I can not determine what causr freez.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clon   1561 F pulseaudio
   /dev/snd/seq:timidity771 F timidity
  Date: Sun Sep 13 09:36:30 2015
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location __percpu_counter_add+0x14/0xa0 SS:ESP 0068:e75b5dc0
  Failure: oops
  HibernationDevice: RESUME=UUID=7487f502-5343-4e22-b4cf-6decd3b11281
  InstallationDate: Installed on 2013-03-16 (911 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=/dev/mapper/lubuntu-root ro plymouth:debug splash quiet drm.debug=0xe 
plymouth:debug=1=1
  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-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 34c03000
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2005
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: K8T800-8237
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/25/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnK8T800-8237:rvr1.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1494371] larsen (i386) - tests ran: 153, failed: 0

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.16.0-50.66~14.04.1/larsen__3.16.0-50.66~14.04.1__2015-09-13_06-07-00/results-index.html

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

Title:
  linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 10. September 2015 15:32 UTC
  kernel-stable-Prepare-package-end:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 11. September 2015 19:24 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Verification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Certification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-start:Friday, 11. September 2015 21:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. September 2015 08:01 UTC

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

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

[Kernel-packages] [Bug 1488426] Re: High CPU usage of kworker/ksoftirqd

I'm also affected by this issue and it's very annoying as it sucks all my 
battery!
I have a Dell Inspiron  powered by an AMD A8-7410 and 4G of RAM (which is 
BTW certified for Ubuntu 14.04).


Here's the top output:

$ top -b -n1
top - 11:20:15 up 42 min,  2 users,  load average: 1,77, 1,72, 1,62
Tasks: 217 total,   2 running, 215 sleeping,   0 stopped,   0 zombie
%Cpu(s):  3,9 us, 22,2 sy,  0,0 ni, 70,5 id,  1,5 wa,  0,0 hi,  1,9 si,  0,0 st
KiB Mem:   3400808 total,  1822148 used,  1578660 free,64956 buffers
KiB Swap:  7812092 total,0 used,  7812092 free.   764228 cached Mem

  PID USER  PR  NIVIRTRESSHRS%CPU%MEM TIME+ 
COMMAND
   75 root 20   0   0   0 0R  56,7  
0,022:56.39  kworker/3:2
   29 root 20   0   0   0 0S  37,8  
0,016:05.42  ksoftirqd/3


And this is the perf report:

+   65,62% 0,00%  kworker/3:2  [kernel.kallsyms] [k] 
ret_from_fork ▒
+   65,62% 0,00%  kworker/3:2  [kernel.kallsyms] [k] 
kthread   ▒
+   65,51% 0,11%  kworker/3:2  [kernel.kallsyms] [k] 
worker_thread ▒
+   65,26% 0,67%  kworker/3:2  [kernel.kallsyms] [k] 
process_one_work  ▒
+   61,64% 0,78%  kworker/3:2  [kernel.kallsyms] [k] 
rpm_idle  ▒
+   60,01% 0,32%  kworker/3:2  [kernel.kallsyms] [k] 
pm_runtime_work   ▒
+   59,27% 0,99%  kworker/3:2  [kernel.kallsyms] [k] 
rpm_suspend   ▒
+   58,95% 0,14%  kworker/3:2  [kernel.kallsyms] [k] 
__rpm_callback▒
+   58,76% 0,22%  kworker/3:2  [kernel.kallsyms] [k] 
usb_runtime_idle  ▒
+   58,37% 0,24%  kworker/3:2  [kernel.kallsyms] [k] 
__pm_runtime_suspend  ▒
+   56,79% 0,24%  kworker/3:2  [kernel.kallsyms] [k] 
rpm_callback  ▒
+   56,41% 0,25%  kworker/3:2  [kernel.kallsyms] [k] 
usb_runtime_suspend   ▒
+   56,11% 0,75%  kworker/3:2  [kernel.kallsyms] [k] 
usb_suspend_both  ▒
+   42,00% 0,36%  kworker/3:2  [kernel.kallsyms] [k] 
usb_resume_interface.isra.6   ▒
+   41,69% 0,24%  kworker/3:2  [kernel.kallsyms] [k] 
hub_resume▒
+   41,30% 0,81%  kworker/3:2  [kernel.kallsyms] [k] 
hub_activate  ▒
+   37,38% 0,66%  kworker/3:2  [kernel.kallsyms] [k] 
hub_port_status   ▒
+   36,29% 0,49%  kworker/3:2  [kernel.kallsyms] [k] 
usb_control_msg   ▒
+   33,50% 0,50%  kworker/3:2  [kernel.kallsyms] [k] 
usb_start_wait_urb▒
+   26,53% 0,43%  kworker/3:2  [kernel.kallsyms] [k] 
usb_submit_urb▒
+   26,08% 2,32%  kworker/3:2  [kernel.kallsyms] [k] 
usb_submit_urb.part.6 ▒
+   22,69% 1,63%  kworker/3:2  [kernel.kallsyms] [k] 
usb_hcd_submit_urb▒
+   19,59% 0,00%  ksoftirqd/3  [kernel.kallsyms] [k] 
ret_from_fork ▒
+   19,59% 0,00%  ksoftirqd/3  [kernel.kallsyms] [k] 
kthread   ▒
+   18,21% 1,18%  ksoftirqd/3  [kernel.kallsyms] [k] 
smpboot_thread_fn ▒
+   15,07% 0,52%  kworker/3:2  [kernel.kallsyms] [k] 
usb_hcd_giveback_urb  ▒
+   14,08% 0,21%  kworker/3:2  [kernel.kallsyms] [k] 
wakeup_softirqd   ▒
+   13,67% 0,05%  kworker/3:2  [kernel.kallsyms] [k]

[Kernel-packages] [Bug 1495208] [NEW] linux: 4.2.0-10.10 -proposed tracker

Public bug reported:

This bug is for tracking the 4.2.0-10.10 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
kernel-phase:Prepare

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

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


** Tags: block-proposed kernel-release-tracking-bug wily

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

** Tags added: block-proposed

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

** Tags added: wily

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

Title:
  linux: 4.2.0-10.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source

[Kernel-packages] [Bug 1410384] fozzie (i386) - tests ran: 153, failed: 0

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/fozzie__3.13.0-64.104__2015-09-13_08-52-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1495184] [NEW] BUG: unable to handle kernel paging request at 34c03000

2015-09-13 Thread Clon

Public bug reported:

System freez after upgrade, while browsing in firefox and shotr after
removing of flashdrive.

I can not determine what causr freez.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-7-generic 4.2.0-7.7
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic i686
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.18.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  clon   1561 F pulseaudio
 /dev/snd/seq:timidity771 F timidity
Date: Sun Sep 13 09:36:30 2015
DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location __percpu_counter_add+0x14/0xa0 SS:ESP 0068:e75b5dc0
Failure: oops
HibernationDevice: RESUME=UUID=7487f502-5343-4e22-b4cf-6decd3b11281
InstallationDate: Installed on 2013-03-16 (911 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
IwConfig:
 lono wireless extensions.
 
 eth1  no wireless extensions.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=/dev/mapper/lubuntu-root ro plymouth:debug splash quiet drm.debug=0xe 
plymouth:debug=1=1
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-3ubuntu8
RfKill:
 
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 34c03000
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2005
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: K8T800-8237
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: 1.x
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/25/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnK8T800-8237:rvr1.x:cvn:ct3:cvr:

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


** Tags: apport-kerneloops i386 kernel-oops wily

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

Title:
  BUG: unable to handle kernel paging request at 34c03000

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System freez after upgrade, while browsing in firefox and shotr after
  removing of flashdrive.

  I can not determine what causr freez.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clon   1561 F pulseaudio
   /dev/snd/seq:timidity771 F timidity
  Date: Sun Sep 13 09:36:30 2015
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: location __percpu_counter_add+0x14/0xa0 SS:ESP 0068:e75b5dc0
  Failure: oops
  HibernationDevice: RESUME=UUID=7487f502-5343-4e22-b4cf-6decd3b11281
  InstallationDate: Installed on 2013-03-16 (911 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=/dev/mapper/lubuntu-root ro plymouth:debug splash quiet drm.debug=0xe 
plymouth:debug=1=1
  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-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 34c03000
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2005
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: K8T800-8237
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/25/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnK8T800-8237:rvr1.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1495187] Re: [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]

2015-09-13 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/1495187

Title:
  [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]

Status in linux package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic i686
  NonfreeKernelModules: nvidia
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  niccolo1385 F pulseaudio
  Date: Sun Sep 13 10:07:12 2015
  DuplicateSignature: hibernate/resume:TOSHIBA Satellite A100:6.00
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=322eb439-619d-4d68-bbe2-36275568ae02
  InstallationDate: Installed on 2015-09-11 (1 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite A100
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=5078147b-20a1-4c27-92ac-54ed592f3ebe ro quiet splash net.ifnames=0 
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-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  Title: [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/12/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  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/12/2007:svnTOSHIBA:pnSatelliteA100:pvrPSAA9E-0QF03WIT:rvnIntelCorporation:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Satellite A100
  dmi.product.version: PSAA9E-0QF03WIT
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1410384] tarf (amd64) - tests ran: 180, failed: 1

tests ran: 180, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/tarf__3.13.0-64.104__2015-09-13_06-32-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1416557] Re: [Acer Aspire V5-573G] suspend/resume failure

2015-09-13 Thread Maxim Kizub

See bisect for the same bug in

https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1483467

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

Title:
  [Acer Aspire V5-573G] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Black screen on resume after suspend

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-12-generic 3.18.0-12.13
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1668 F pulseaudio
    valeronm   2143 F pulseaudio
   /dev/snd/controlC0:  lightdm1668 F pulseaudio
    valeronm   2143 F pulseaudio
  Date: Fri Jan 30 23:39:37 2015
  DuplicateSignature: suspend/resume:Acer Aspire V5-573G:V2.29
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2b5c8acc-3a16-4e7f-97ba-5f4d5d564e7c
  InstallationDate: Installed on 2015-01-30 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Acer Aspire V5-573G
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic.efi.signed 
root=UUID=eca5cdef-c2d4-4af6-a5e2-a11289cc9cfc 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.18.0-12-generic N/A
   linux-backports-modules-3.18.0-12-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  Title: [Acer Aspire V5-573G] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 06/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Dazzle_HW
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.29:bd06/05/2014:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-573G
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

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

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

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

This change was made by a bot.

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

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

Title:
  [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic i686
  NonfreeKernelModules: nvidia
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  niccolo1385 F pulseaudio
  Date: Sun Sep 13 10:07:12 2015
  DuplicateSignature: hibernate/resume:TOSHIBA Satellite A100:6.00
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=322eb439-619d-4d68-bbe2-36275568ae02
  InstallationDate: Installed on 2015-09-11 (1 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite A100
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=5078147b-20a1-4c27-92ac-54ed592f3ebe ro quiet splash net.ifnames=0 
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-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  Title: [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/12/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  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/12/2007:svnTOSHIBA:pnSatelliteA100:pvrPSAA9E-0QF03WIT:rvnIntelCorporation:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Satellite A100
  dmi.product.version: PSAA9E-0QF03WIT
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1410384] ms10-35-mcdivittB0 (arm64) - tests ran: 153, failed: 4

tests ran: 153, failed: 4;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/ms10-35-mcdivittB0__3.13.0-64.104__2015-09-13_06-29-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1495116/+attachment/4462937/+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/1495116

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus: Upgraded to

[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

I was able to boot with the amd64 kernel from Vivid and upstart (but I
guess that the successes and failures are just random), and will now
collect the new information (for 15.04 (Vivid) system).

** Description changed:

  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so
  I added that architecture and apt-get-installed the amd64 linux-image
  and linux-image-extra (I learned this was possible thanks to the advice
  at http://askubuntu.com/a/635774/19753 ).
  
  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)
  
  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)
  
  I checked my suspection that  the video driver (nouveau) and X might be
  involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.
  
  Perhaps, I'd like to debug the upstart procedure step-by-step to detect
  which step makes the system crash and reboot, but I don't know how. As
  concerns the timing, the moment the reboot happens can be different: it
  can happen rather early (when I see the message about activating the
  swap) or much later.
  
  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/26/2008
  dmi.bios.vendor: Phoenix Technologies Ltd.

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1495116/+attachment/4462951/+files/WifiSyslog.txt

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus:

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus: Upgraded

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

apport information

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus: Upgraded

[Kernel-packages] [Bug 1410384] fozzie (amd64) - tests ran: 180, failed: 1

tests ran: 180, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/fozzie__3.13.0-64.104__2015-09-13_06-31-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1416557] Re: [Acer Aspire V5-573G] suspend/resume failure

2015-09-13 Thread Maxim Kizub

A temp fix is to add acpi_osi="!Windows 2013" to boot kernel params.

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

Title:
  [Acer Aspire V5-573G] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Black screen on resume after suspend

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-12-generic 3.18.0-12.13
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1668 F pulseaudio
    valeronm   2143 F pulseaudio
   /dev/snd/controlC0:  lightdm1668 F pulseaudio
    valeronm   2143 F pulseaudio
  Date: Fri Jan 30 23:39:37 2015
  DuplicateSignature: suspend/resume:Acer Aspire V5-573G:V2.29
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2b5c8acc-3a16-4e7f-97ba-5f4d5d564e7c
  InstallationDate: Installed on 2015-01-30 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Acer Aspire V5-573G
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic.efi.signed 
root=UUID=eca5cdef-c2d4-4af6-a5e2-a11289cc9cfc 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.18.0-12-generic N/A
   linux-backports-modules-3.18.0-12-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  Title: [Acer Aspire V5-573G] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 06/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Dazzle_HW
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.29:bd06/05/2014:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-573G
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1495187] [NEW] [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]

2015-09-13 Thread Niccolò Marchi

Public bug reported:

---

ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-7-generic 4.2.0-7.7
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic i686
NonfreeKernelModules: nvidia
Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
ApportVersion: 2.18.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  niccolo1385 F pulseaudio
Date: Sun Sep 13 10:07:12 2015
DuplicateSignature: hibernate/resume:TOSHIBA Satellite A100:6.00
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=322eb439-619d-4d68-bbe2-36275568ae02
InstallationDate: Installed on 2015-09-11 (1 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825)
InterpreterPath: /usr/bin/python3.4
MachineType: TOSHIBA Satellite A100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=5078147b-20a1-4c27-92ac-54ed592f3ebe ro quiet splash net.ifnames=0 
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-4.2.0-7-generic N/A
 linux-backports-modules-4.2.0-7-generic  N/A
 linux-firmware   1.147
SourcePackage: linux
Title: [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]
UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 07/12/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: CAPELL VALLEY(NAPA) CRB
dmi.board.vendor: Intel Corporation
dmi.board.version: Not Applicable
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/12/2007:svnTOSHIBA:pnSatelliteA100:pvrPSAA9E-0QF03WIT:rvnIntelCorporation:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Satellite A100
dmi.product.version: PSAA9E-0QF03WIT
dmi.sys.vendor: TOSHIBA

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


** Tags: apport-kerneloops hibernate i386 need-duplicate-check resume wily

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

Title:
  [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]

Status in linux package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic i686
  NonfreeKernelModules: nvidia
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  niccolo1385 F pulseaudio
  Date: Sun Sep 13 10:07:12 2015
  DuplicateSignature: hibernate/resume:TOSHIBA Satellite A100:6.00
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=322eb439-619d-4d68-bbe2-36275568ae02
  InstallationDate: Installed on 2015-09-11 (1 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite A100
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=5078147b-20a1-4c27-92ac-54ed592f3ebe ro quiet splash net.ifnames=0 
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-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  Title: [TOSHIBA Satellite A100] hibernate/resume failure [non-free: nvidia]
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/12/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable

[Kernel-packages] [Bug 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-13 Thread Colin Law

Have I missed something or has it not arrived yet?

I have gone back and confirmed that afb5abc262e962089e was good and
0dc553652102c55a4 is bad, just in case I had made a mistake.

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

Title:
  kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker
  takes 100% of one core of CPU due to GPE13 interrupt storm

  See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071

  The bug can be identified by repeatedly running 
  cat /sys/firmware/acpi/interrupts/gpe13
  where a rapidly increasing count will be seen.

  Workaround:
  sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13'
  disables it until reboot
  Using 
  sudo crontab -e
  and adding the line
  @reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13
  works around for subsequent boots.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1699 F pulseaudio
   /dev/snd/controlC1:  colinl 1699 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  2 16:03:19 2015
  InstallationDate: Installed on 2014-10-21 (316 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.147
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-08-31 (1 days ago)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.19
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1410384] onza (amd64) - tests ran: 180, failed: 2

tests ran: 180, failed: 2;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/onza__3.13.0-64.104__2015-09-13_06-31-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown

2015-09-13 Thread Roland Weber

I removed the bios-outdated tag. The guy who wrote about his BIOS update
in comment #9 has a completely different problem and commented off-
topic.

** Tags removed: bios-outdated-1.13

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

Title:
"lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on
shutdown

Status in linux package in Ubuntu:
Triaged

Bug description:
reproducible: always

Steps to reproduce:
- open a terminal
- sudo bash
- lsusb -v

In a virtual terminal, the command prints the name of the first device
it finds, then the system freezes completely. In a terminal of the
desktop, I don't even get the name of the device, the system freezes
immediately. Either way, I have to power off the machine. There is no
kernel oops. Nothing is written to the log. The magic sysreq key
yields no response, although I have verified that it works before
triggering the freeze.

I've narrowed down the problem by calling "lsusb -v -s ". The
system freezes on both devices of bus 3 (003:001 and 003:002). For all
other devices, it prints the expected output and continues to work.
When calling lsusb as a regular user, I get "Couldn't open device,
some information will be missing", then the regular output, and the
system keeps running. Therefore I assume that the problem is somewhere
in the kernel, when the devices are accessed.

This is a regression. It used to work in 14.10, and fails to work since 15.04.
It also used to work in 14.04.2, and fails in 14.04.3.
It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable,
4.1.0-rc2-vivid. (yeah, I've been trying for a while :-)

Incidentally, the shutdown sequence also freezes with the kernels that
exhibit the problem; but I cannot be sure that the cause is the same.
I decided to first chase the USB freeze, because it was easier to
gather information about that.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-25-generic 3.19.0-25.26
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rweber 1525 F pulseaudio
CurrentDesktop: XFCE
Date: Fri Aug 14 18:38:36 2015
HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a
InstallationDate: Installed on 2015-06-28 (46 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Acer Aspire ES1-111M
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic
root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash
crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.19.0-25-generic N/A
linux-backports-modules-3.19.0-25-generic N/A
linux-firmware 1.143.3
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago)
dmi.bios.date: 08/20/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: R2
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire ES1-111M
dmi.product.version: V1.08
dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1005832] Re: 8086:0085 Intel wifi frequent disconnects

2015-09-13 Thread Adrian Wilkins

If anyone wants a reliable place to test this, Ziferblat in Manchester
UK has no fewer than 7 access points all named 'Ziferblat' and this
almost completely jams my WiFi - I can't auth, I can't even use other
5Ghz portable hotspots, the only saviour is the 2.5Ghz hotspot on my
ageing Nexus.

This is on 15.04 with an Intel 6235.

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

Title:
  8086:0085 Intel wifi frequent disconnects

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

Bug description:
  Several people at Linaro Connect with Thinkpads and Intel wifi and
  experiencing, frequent disconnects and have to kill wpa_supplicant in
  order to reconnect.

  this seems to be related to having multiple ssid with the same name in
  close proximity see this reference:

  https://mail.gnome.org/archives/networkmanager-
  list/2012-February/msg00135.html

  I've had this happen on my x220 with both the precise and the "Q"
  kernel. I've upgraded my box to Q

  Here is a snippet of the log file when it happens:

  May 29 10:43:18 zorak wpa_supplicant[1155]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid
  =00:00:00:00:00:00 reason=3

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.4.0-3-generic 3.4.0-3.8
  ProcVersionSignature: Ubuntu 3.4.0-3.8-generic 3.4.0
  Uname: Linux 3.4.0-3-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.1-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgraner1844 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf152 irq 47'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f1506e,17aa21da,0012 
HDA:80862805,80860101,0010'
 Controls  : 26
 Simple ctrls  : 8
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
 Mixer name : 'ThinkPad EC (unknown)'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Tue May 29 18:05:11 2012
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=113c954a-7297-4617-b9e3-a64076beef2c
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 4286CTO
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-3-generic 
root=UUID=3d880a9e-f17b-4e2e-9499-6273ef2e37fb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.4.0-3-generic N/A
   linux-backports-modules-3.4.0-3-generic  N/A
   linux-firmware   1.80
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET50WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1494943] Re: module signing can fail if the module identifier starts with a 0 byte

** Summary changed:

- module signing can fail if the module identifier starts with a 0
+ module signing can fail if the module identifier starts with a 0 byte

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

Title:
  module signing can fail if the module identifier starts with a zero
  byte

Status in linux package in Ubuntu:
  In Progress

Bug description:
  module signing can fail if the module identifier starts with a 0.
  This occurs randomly.

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

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

[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

With systemd.crash_shell=true systemd.confirm_spawn=true (which is very
inconvenient to use), I've found out that the crash usually happens
somewhere around the start of udev services.

** Also affects: udev (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/1495116

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in udev package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A

[Kernel-packages] [Bug 1487113] Re: Unable to boot "Gave up waiting for root device" "Dropping to a shell"

** Tags added: latest-bios-f.34

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

Title:
  Unable to boot "Gave up waiting for root device" "Dropping to a shell"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install (and also reinstall due to the same problem) of the
  Linux (LXDE) the system fails to boot after a few days of booting up
  perfectly fine.

  I get an error message saying "Gave up waiting for root device" and
  then drops to the (initramfs) prompt.

  When this problem first occurred, simply typing "exit" at the prompt
  would resume the boot process. However, now I have to wait for almost
  90 seconds (I'm guessing) before the "exit" command is able to resume
  boot process.

  I have noticed that the time during which the system is unable to resume the 
boot up process, the /dev/disk/ folder does not exist. In my earlier attempts 
at diagnosing the problem I have tried:
  1. Reinstalling the grub
  2. Identifying disks using the UUID as well as sda/sdb in the Grub
  3. Updating the Linux kernel (previous install)

  On the bright side, once the system boots up it runs fine without a
  glitch. This is an old laptop with an unserviceable DVD drive plugged
  in that is disabled in the BIOS.

  I hope that you folks can help me find a solution for this annoying
  problem. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ankit  2464 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Thu Aug 20 21:26:51 2015
  HibernationDevice: RESUME=UUID=c8ee408d-05a2-44e9-aeaa-8db637bb
  InstallationDate: Installed on 2015-06-21 (60 days ago)
  InstallationMedia: LXLE 14.04 - Release amd64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1bcf:0005 Sunplus Innovation Technology Inc. 
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard V6604AU
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=04508ab2-a9c3-4206-b045-56f2029e23ba ro quiet splash rootdelay=10 
rootwait=10 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.name: 30CF
  dmi.board.vendor: Quanta
  dmi.board.version: 85.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd03/22/2011:svnHewlett-Packard:pnV6604AU:pvrRev1:rvnQuanta:rn30CF:rvr85.26:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: V6604AU
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1410384] larsen (i386) - tests ran: 153, failed: 0

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/larsen__3.13.0-64.104__2015-09-13_12-10-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1410384] larsen (amd64) - tests ran: 180, failed: 5

tests ran: 180, failed: 5;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/larsen__3.13.0-64.104__2015-09-13_09-01-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1471380] Re: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access

2015-09-13 Thread Abdul Rehman

I have fujitsu lifebook ah532 of serial YLKVx,
want to install ubuntu 15.04 without messing anything,
I have access to Boot menu and Bios,
Currently Running Windows 10 Pro,
Hard disk partitions are GPT based.
Bios version 1.09

Hardware specs
Intel Core-i7 3612qm
4 GB DDR3 RAM
Intel HD 4000m

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

Title:
  [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out
  firmware access

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been running pre-installed Windows 7 on a Fujitsu AH532 since
  2012.

  Two weeks back, I installed a Live-USB with Ubuntu 14.04. All working
  well, but I struggled getting it persistent, so I decided to do a full
  Ubuntu installation to another USB-drive. Leaving my Windows hard
  drive untouched.

  
  What I did:
  1) I entered my "BIOS" to change boot order, and booting from my Ubuntu 
Live-USB.

  2) I tried following the  installation guide 
https://help.ubuntu.com/community/Installation/UEFI-and-BIOS, but sizes were 
changed to: 
   - 1MB BIOS Boot (pretty sure I left this unformatted,but it now reports as 
Ext4)
   - 666MB EFI System, FAT32
   - 30GB Linux Filesystem, Ext4
   - 999MB Linux Swap, Swap

  3) I installed Ubuntu on a second USB-drive. Leaving my Windows hard-
  drive "intact" (?)

  
  The result:
  Now, I can only boot my machine by inserting my second 
full-installation-USB-drive. 
  I cannot boot Windows, and I cannot boot from my LiveUSB.

  If I boot without inserting my full-installation-USB-drive, I get the
  boot screen telling me I can press F2 or F12. However, none of these
  have any effect, apart from making the beep. Then the computer enters
  the "Boot menu" (as well as the second menu "Application menu").

  
  This bug feels very related to:
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387

  
  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-41-generic 3.16.0-41.55~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul  4 08:05:03 2015
  InstallationDate: Installed on 2015-06-18 (15 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   vegard 2045 F...m pulseaudio
   /dev/snd/controlC0:  vegard 2045 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=b7bfbfab-671b-471c-ba59-210445db2063
  InstallationDate: Installed on 2015-06-18 (16 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: FUJITSU LIFEBOOK AH532
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic.efi.signed 
root=UUID=b9d1f4be-275f-4b97-a68a-ccb2afa41781 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-41-generic N/A
   linux-backports-modules-3.16.0-41-generic  N/A
   linux-firmware 1.127.11
  Tags:  trusty
  Uname: Linux 3.16.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/22/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.09
  dmi.board.name: FJNBB1C
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK AH532
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1420290]

2015-09-13 Thread Meelis Roos

I am another reporter seeing the same problem, this time in
4.2.0-rc7-00071-g0bad909 with no kernel options for drm or i915, so
4.2-rc7 does not cure it.

I do not have dmesg with drm_debug yet, will see if I can reproduce it
at will (so fast I have seen it once).

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

Title:
  WARNING: CPU: 0 PID: 2517 at
  /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713
  intel_check_page_flip+0xe6/0xf0 [i915]()

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

Bug description:
  Running Vivid with kernel 3.19 (debs from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/v3.19-vivid/), I get the warning below in dmesg.

  I can't use "ubuntu-bug linux" because I get "It appears you are
  currently running a mainline kernel.  It would be better to report
  this bug upstream at http://bugzilla.kernel.org/ so that the upstream
  kernel developers are aware of the issue.  If you'd still like to file
  a bug against the Ubuntu kernel, please boot with an official Ubuntu
  kernel and re-file.". IMHO that last advice would be a DTO (Defeating
  The Objective), as this message does not appear in the 3.18.

  
  $ uname -a
  Linux superstreamer 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 
14:52:52 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  
  [ 2243.390997] [ cut here ]
  [ 2243.391046] WARNING: CPU: 0 PID: 2517 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 
intel_check_page_flip+0xe6/0xf0 [i915]()
  [ 2243.391049] Kicking stuck page flip: queued at 134027, now 134031
  [ 2243.391051] Modules linked in: hid_generic(E) hp_wmi(E) sparse_keymap(E) 
joydev(E) rfcomm(E) bnep(E) intel_rapl(E) intel_soc_dts_thermal(E) 
intel_powerclamp(E) snd_hda_codec_hdmi(E) coretemp(E) kvm_intel(E) 
snd_hda_codec_realtek(E) kvm(E) snd_hda_codec_generic(E) crct10dif_pclmul(E) 
crc32_pclmul(E) ghash_clmulni_intel(E) cryptd(E) arc4(E) rtl8723be(E) 
btcoexist(E) snd_hda_intel(E) usbhid(E) rtl8723_common(E) snd_hda_controller(E) 
rtl_pci(E) serio_raw(E) rtlwifi(E) snd_hda_codec(E) snd_intel_sst_acpi(E) 
nls_iso8859_1(E) snd_hwdep(E) snd_intel_sst_core(E) 
snd_soc_sst_mfld_platform(E) mac80211(E) rtsx_pci_ms(E) snd_seq_midi(E) 
memstick(E) snd_soc_rt5640(E) snd_soc_rl6231(E) snd_seq_midi_event(E) 
cfg80211(E) lpc_ich(E) i915(E) snd_soc_core(E) snd_rawmidi(E) snd_compress(E) 
wmi(E) hp_wireless(E) snd_pcm_dmaengine(E)
  [ 2243.391089]  snd_seq(E) dw_dmac(E) dw_dmac_core(E) int3400_thermal(E) 
snd_seq_device(E) snd_pcm(E) int3403_thermal(E) processor_thermal_device(E) 
acpi_thermal_rel(E) intel_smartconnect(E) video(E) drm_kms_helper(E) drm(E) 
i2c_hid(E) snd_timer(E) hid(E) snd(E) i2c_designware_platform(E) soundcore(E) 
i2c_designware_core(E) i2c_algo_bit(E) shpchp(E) parport_pc(E) 
snd_soc_sst_acpi(E) btusb(E) mei_txe(E) mei(E) rfkill_gpio(E) iosf_mbi(E) 
ppdev(E) spi_pxa2xx_platform(E) bluetooth(E) 8250_dw(E) pwm_lpss_platform(E) 
pwm_lpss(E) lp(E) parport(E) mac_hid(E) mmc_block(E) rtsx_pci_sdmmc(E) 
psmouse(E) rtsx_pci(E) sdhci_acpi(E) sdhci(E)
  [ 2243.391129] CPU: 0 PID: 2517 Comm: Chrome_IOThread Tainted: GE 
 3.19.0-031900-generic #201502091451
  [ 2243.391131] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, 
BIOS F.05 11/28/2014
  [ 2243.391134]  25f1 880076c03630 817c4c00 
0007
  [ 2243.391138]  880076c03680 880076c03670 81076e87 
0748a8c1
  [ 2243.391142]  880036b91000 8800700909a8 880070090800 

  [ 2243.391146] Call Trace:
  [ 2243.391149][] dump_stack+0x45/0x57
  [ 2243.391162]  [] warn_slowpath_common+0x97/0xe0
  [ 2243.391166]  [] warn_slowpath_fmt+0x46/0x50
  [ 2243.391192]  [] intel_check_page_flip+0xe6/0xf0 [i915]
  [ 2243.391214]  [] 
valleyview_pipestat_irq_handler+0x188/0x220 [i915]
  [ 2243.391236]  [] valleyview_irq_handler+0xaf/0x180 [i915]
  [ 2243.391242]  [] ? ip6_finish_output+0x95/0xd0
  [ 2243.391247]  [] handle_irq_event_percpu+0x5d/0x1e0
  [ 2243.391251]  [] ? ip6_xmit+0x22a/0x490
  [ 2243.391255]  [] handle_irq_event+0x48/0x70
  [ 2243.391258]  [] handle_edge_irq+0x7f/0x120
  [ 2243.391263]  [] handle_irq+0x22/0x40
  [ 2243.391267]  [] do_IRQ+0x5c/0x110
  [ 2243.391271]  [] common_interrupt+0x6d/0x6d
  [ 2243.391276]  [] ? tcp_queue_rcv+0x21/0x130
  [ 2243.391280]  [] ? __skb_checksum_complete+0x22/0xd0
  [ 2243.391284]  [] tcp_rcv_established+0x194/0x740
  [ 2243.391289]  [] tcp_v6_do_rcv+0x216/0x450
  [ 2243.391294]  [] ? security_sock_rcv_skb+0x16/0x20
  [ 2243.391298]  [] tcp_v6_rcv+0x796/0x7e0
  [ 2243.391304]  [] ? _rtl_pci_rx_interrupt+0x4af/0x680 
[rtl_pci]
  [ 2243.391309]  [] ip6_input_finish+0x140/0x420
  [ 2243.391313]  [] ip6_input+0x22/0x60
  [ 2243.391317]  [] ? tcp_v6_early_demux+0x58/0x70
  [ 2243.391321]  [] ip6_rcv_finish+0x78/0xb0

[Kernel-packages] [Bug 1486581] Re: Removed USB3 device from USB3 port causes S3 Resume to Fail

Kaarel, as per http://support.lenovo.com/us/en/products/laptops-and-
netbooks/lenovo-b-series-laptops/lenovo-b5400-notebook an update to your
computer's buggy and outdated BIOS is available (2.08). If you update to
this following https://help.ubuntu.com/community/BIOSUpdate does it
change anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then
please mark this report Status Confirmed.

Thank you for your understanding.

** Tags removed: usb
** Tags added: bios-outdated-2.08

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

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

Title:
  Removed USB3 device from USB3 port causes S3 Resume to Fail

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 15.04 with Mainline Kernel 4.2 RC7 on a Lenovo B5400
  laptop.

  When I plug an USB3 flash drive into either of the USB3 ports, then
  remove the flash drive and try to suspend (using the GUI), the
  computer will resume automatically from suspend in a second.

  The problem is not present when using a USB2 device in USB3 ports or when 
using a USB3 device in the USB2 port.
  If I do not remove the flash drive from the USB3 port suspend will work as 
expected.

  I've googled for this bug and found some guides in fixing a similar
  problem, but none of them worked.

  I'm not _sure_ what package is the cause of this problem, so acpid
  might be the wrong choice.

  Below is attached /proc/acpi/wakeup as suggested by the
  DebuggingKernelSuspend, please tell me if more information or logs are
  needed.

  NB! Please read #3 for more information!!!
  --- 
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaarel 1284 F...m pulseaudio
   /dev/snd/controlC1:  kaarel 1284 F pulseaudio
   /dev/snd/controlC0:  kaarel 1284 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-04-06 (136 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: LENOVO 80B6QB0
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=13bb1cd3-a667-4b84-b5ca-9ccd55e2dfdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-26-generic N/A
   linux-backports-modules-3.19.0-26-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  Uname: Linux 3.19.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/03/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J7ET61WW (2.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 80B6QB0
  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:bvrJ7ET61WW(2.06):bd03/03/2014:svnLENOVO:pn80B6QB0:pvrB5400:rvnLENOVO:rn80B6QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 80B6QB0
  dmi.product.version: B5400
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1061508] Re: System Boots Every Other Time

tjboadwa, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  System Boots Every Other Time

Status in linux package in Ubuntu:
  Expired

Bug description:
  After a fresh install of 12.04.1  the system boots every other time
  it's started or restarted.  When it doesn't boot the screen goes to
  sleep as the system hangs/freezes.  The system boots fine under
  10.04.4.

  Steps to reproduce:
  1)  Install using 12.04.1
  2)  Boot the system
  3)  If the system boots properly restart or shutdown the system

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-31-generic-pae 3.2.0-31.50
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  name   2478 F pulseaudio
   /dev/snd/pcmC0D0p:   name   2478 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 23'
     Mixer name : 'Realtek ALC888'
     Components : 'HDA:10ec0888,103c2a58,0011'
     Controls  : 40
     Simple ctrls  : 21
  Date: Thu Oct  4 06:05:55 2012
  HibernationDevice: RESUME=UUID=9d64ac90-738f-49eb-a637-ad5473e780b4
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423.2)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP-Pavilion GC384AV-ABA m8000e
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic-pae 
root=/dev/mapper/sda6_crypt ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-31-generic-pae N/A
   linux-backports-modules-3.2.0-31-generic-pae  N/A
   linux-firmware1.79.1
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UdevDb: Error: [Errno 2] No such file or directory
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.09
  dmi.board.name: NARRA
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd05/15/2007:svnHP-Pavilion:pnGC384AV-ABAm8000e:pvr:rvnASUSTekComputerINC.:rnNARRA:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: GC384AV-ABA m8000e
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1486896] Re: On Lenovo Thinkpad Edge E330, the screen backlight flickers badly.

** Tags added: bios-outdated-1.12

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

Title:
  On Lenovo Thinkpad Edge E330, the screen backlight flickers badly.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Behavior is the same on Ubuntu 14.04 -- 15.04.

  Steps were taken according to this:
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  With acpi_backlight=vendor, the flicker stops, and the brightness control 
doesn't work.
  However,
  echo 8 > /sys/class/backlight/intel_backlight/brightness
  dims the screen.

  thinkpad-acpi.brightness_enable = 1 does nothing.

  Workaround: If no changes are made to boot options, and
  echo 4437 > /sys/class/backlight/intel_backlight/brightness
  is done, the flicker stops and the GUI control / acpi_video0 works, but 
causes flicker again.

  Attaching the necessary files.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-26-generic 3.19.0-26.28
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mark   1391 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 20 11:21:39 2015
  HibernationDevice: RESUME=UUID=7a9e1f17-c57b-4e6f-bb0c-0b090b5d1405
  InstallationDate: Installed on 2014-08-22 (363 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 3354DGG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic 
root=UUID=b566feb2-5a5c-4573-8782-b78d130dbc45 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-26-generic N/A
   linux-backports-modules-3.19.0-26-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-08-20 (0 days ago)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H3ET72WW(1.09)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3354DGG
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98409 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:bvrH3ET72WW(1.09):bd02/25/2013:svnLENOVO:pn3354DGG:pvrThinkPadEdgeE330:rvnLENOVO:rn3354DGG:rvr0B98409Std:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3354DGG
  dmi.product.version: ThinkPad Edge E330
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1487525] Re: Dell 1525 wakes up on opening the lid, but keyboard takes ages to react

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

Please note, finding adjacent kernel versions is not fully commit
bisecting.

Thank you for your understanding.

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

** Tags added: kernel-fixed-upstream-4.2-rc8 latest-bios-a17 needs-
reverse-bisect

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

Title:
  Dell 1525 wakes up on opening the lid, but keyboard takes ages to
  react

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  What happens:
  When the lid is closed, ubuntu gets into a sleep state. 

  When I open the lid, the system recovers from sleep, the display shows
  the screensaver, but the keyboard does not react on any input. I'll
  have to wait several minutes, bevore the keyboard accepts input and I
  can log in again. Mouse works normal.

  What should happen:
  When I open the lid, the system should recover normally and the keyboard 
should accept input to let me log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-26-generic 3.19.0-26.28
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  midnatsol   1566 F pulseaudio
  Date: Fri Aug 21 17:49:41 2015
  HibernationDevice: RESUME=UUID=9b5d1018-92ac-4a6b-bcb4-ce8351e95de7
  MachineType: Dell Inc. Inspiron 1525
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=5887be20-c47d-41fc-ac15-d517cb5fc739 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-26-generic N/A
   linux-backports-modules-3.19.0-26-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1486581] Re: Removed USB3 device from USB3 port causes S3 Resume to Fail

2015-09-13 Thread Kaarel

Thank you very much for your response!

I would try updating my BIOS, but unfortunately it seems that under the
BIOS Update (Bootable ISO) is only a .exe file. Do I need to contact
Lenovo in order to get the .iso or is there some other way?

Thank you

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

Title:
  Removed USB3 device from USB3 port causes S3 Resume to Fail

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 15.04 with Mainline Kernel 4.2 RC7 on a Lenovo B5400
  laptop.

  When I plug an USB3 flash drive into either of the USB3 ports, then
  remove the flash drive and try to suspend (using the GUI), the
  computer will resume automatically from suspend in a second.

  The problem is not present when using a USB2 device in USB3 ports or when 
using a USB3 device in the USB2 port.
  If I do not remove the flash drive from the USB3 port suspend will work as 
expected.

  I've googled for this bug and found some guides in fixing a similar
  problem, but none of them worked.

  I'm not _sure_ what package is the cause of this problem, so acpid
  might be the wrong choice.

  Below is attached /proc/acpi/wakeup as suggested by the
  DebuggingKernelSuspend, please tell me if more information or logs are
  needed.

  NB! Please read #3 for more information!!!
  --- 
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaarel 1284 F...m pulseaudio
   /dev/snd/controlC1:  kaarel 1284 F pulseaudio
   /dev/snd/controlC0:  kaarel 1284 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-04-06 (136 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: LENOVO 80B6QB0
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=13bb1cd3-a667-4b84-b5ca-9ccd55e2dfdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-26-generic N/A
   linux-backports-modules-3.19.0-26-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  Uname: Linux 3.19.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/03/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J7ET61WW (2.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 80B6QB0
  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:bvrJ7ET61WW(2.06):bd03/03/2014:svnLENOVO:pn80B6QB0:pvrB5400:rvnLENOVO:rn80B6QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 80B6QB0
  dmi.product.version: B5400
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1495112] Re: Keyboard doesn't work for crypt passphrase on bootup

2015-09-13 Thread Max Waterman

I see exactly the same thing - I only upgraded on Friday (11-9-2015). To
successfully boot I manually select the previous kernel (-28) and then I
can enter a password.

Surely there are tests for this use-case?

I'm using a Lenovo X250.

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

Title:
  Keyboard doesn't work for crypt passphrase on bootup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have to hard reboot and then select a kernel. The keyboard does work
  for the text-based, i.e., not GUI, entry of the crypt passphrase, and
  then the boot proceeds.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   mash   1437 F...m pulseaudio
   /dev/snd/controlC1:  mash   1437 F pulseaudio
   /dev/snd/controlC0:  mash   1437 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Sep 12 11:57:56 2015
  HibernationDevice: RESUME=UUID=00c65b3f-bd60-4cf0-bf05-32e6709d92a1
  InstallationDate: Installed on 2015-08-06 (37 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1410384] onza (i386) - tests ran: 153, failed: 0

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-64.104/onza__3.13.0-64.104__2015-09-13_09-27-00/results-index.html

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

Title:
  linux: 3.13.0-45.74 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
  kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
  ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
  kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
  kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
  kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
  kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

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

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

[Kernel-packages] [Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware

2015-09-13 Thread Abdul Rehman

I have fujitsu lifebook ah532 of serial YLKVx,
want to install ubuntu 15.04 without messing anything,
I have access to Boot menu and Bios,
Currently Running Windows 10 Pro,
Hard disk partitions are GPT based.
Bios version 1.09

Hardware specs
Intel Core-i7 3612qm
4 GB DDR3 RAM
Intel HD 4000m

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

Title:
  Ubuntu UEFI install locks out UEFI firmware

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  4 16:57:39 2015
  InstallationDate: Installed on 2010-01-01 (1949 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rut1480 F pulseaudio
rut7079 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b
  InstallationDate: Installed on 2010-01-01 (1949 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: FUJITSU LIFEBOOK LH532
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.16.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.10
  dmi.board.name: FJNBB1F
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK LH532
  dmi.sys.vendor: FUJITSU
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rut2207 F pulseaudio
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=8fd2670c-4060-4d14-8f27-b9f806fe2ce7
  InstallationDate: Installed on 2015-05-06 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: FUJITSU LIFEBOOK LH532
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=3129a485-81a2-48ef-be95-ef9c9a57be3e ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.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.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.10
  dmi.board.name: FJNBB1F
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK LH532
  dmi.sys.vendor: FUJITSU

To manage notifications about

[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

Hi dino99,

I've upgraded to 15.04 (Vivid) and am testing it there (as reflected in
my posts here).

My goal is not multiarch libs/apps. I must not not need them really in
my config: they should stay i386. Only the kernel is amd64.

There are a lot of reports of doing this successfully in various distros
on the web...

And the fact that if the system passed the booting procedure, it is a
stable working system, gives me some encouragement in trying to catch
this bug somewhere in the base system (kernel+systemd+udev).

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in udev package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline:

[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

Soemthing to start with for catching the bug:

I've removed the corresponding linux-image-extra package, and now the
booting is stable.

But I don't have the needed drivers for video (nouveau) and network
then. (And possibly more.)

So loading one of the drivers from -extra caused the crash.

The plan would be to add the used drivers from -extra one by one (or to
remove all but one), and locate the problem in one of the drivers.

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in udev package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro

[Kernel-packages] [Bug 1486746] Re: ubuntu 15.04 after screen lock, laptop cant wake up and black screen seen

mehmet, could you please test the latest upstream kernel available from
the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow
additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into 
the OS) please make a comment in your report about this, and continue to test 
the next most recent kernel version until you can test to the issue. Once 
you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this bug is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this
bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-211

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

Title:
  ubuntu 15.04 after screen lock, laptop cant wake up and black screen
  seen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Asus laptop and i installed ubuntu 15.04 with all packages are 
up-to-date. When lock the screen and if locking takes long, my laptop cant wake 
up and black screen seen. Everytime I have to hard reset ( by pressing on 
button for ten seconds) .
  --- 
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mehmet 1245 F pulseaudio
   /dev/snd/controlC1:  mehmet 1245 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-08-24 (19 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: ASUSTeK Computer Inc. M51Vr
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=9bb3f21e-8737-45ba-83f1-2833fcbda2eb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-28-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/17/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Vr
  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.:bvr211:bd11/17/2008:svnASUSTeKComputerInc.:pnM51Vr:pvr1.0:rvnASUSTeKComputerInc.:rnM51Vr:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Vr
  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/1486746/+subscriptions

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

[Kernel-packages] [Bug 1487334] Re: Touchpad tap-event support broken since kernel 3.19.0-25

Samuli Kauranne, while booted into the Ubuntu kernel (not upstream), please 
execute the following in a terminal:
apport-collect 1487334

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

Title:
  Touchpad tap-event support broken since kernel 3.19.0-25

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release: Ubuntu 15.04
  Hardware:  Logitech TK820 wireless keyboard with touchpad

  I've been using the said hardware with ubuntu in all releases since
  13.10 without problems. All touchpad features were working fine until
  I received in 15.04 the automatic update to kernel version 3.19.0-22.
  This kernel introduced a condition in which, at times, the system
  started randomly registering keyboard input when pointing with the
  touchpad.

  The original bug got apparently fixed in kernel version 3.19.0-25, but
  as a result this kernel version broke completely all tap-events for my
  touchpad. They are not registering at all. Pointing and scrolling
  work, so do the mechanical click-switches in the corners, but tapping
  or sweeping with one or more fingers does not get registered even
  though the settings were never touched. I now got kernel update to
  3.19.0-26, but the bug persists in this version, too.

  At the moment I had to revert back to kernel version 3.19.0-16 in
  order to be able to use my touchpad normally.

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

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

[Kernel-packages] [Bug 1487524] Re: Broadcom BCM43602 not seeing 5Ghz range

Joe Barnett, https://bugzilla.kernel.org/show_bug.cgi?id=100201 has
nothing to do with the issue you are having.

Hence, you would want to follow the instructions noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487524/comments/6
to report this to the brcm80211-dev-l...@broadcom.com mailing list (not
bugzilla).

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

** Tags added: latest-bios

** Changed in: linux
   Importance: Unknown => Undecided

** Changed in: linux
   Status: Unknown => New

** Changed in: linux
 Remote watch: Linux Kernel Bug Tracker #100201 => None

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

Title:
  Broadcom BCM43602 not seeing 5Ghz range

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

Bug description:
  On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac
  on a wily install out of the box, but can't see any APs on the 5GHz
  range even though there are APs broadcasting on 5Ghz.

  03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless 
LAN SoC (rev 01)
Subsystem: Apple Inc. Device 0152
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: brcmfmac

  $ sudo iwlist wlp3s0 scan|grep Freq
  Frequency:2.412 GHz (Channel 1)
  Frequency:2.422 GHz (Channel 3)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: 
boot/vmlinuz-4.1.0-3-generic]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC2:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC1:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC0:  jbarnett   1545 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Aug 21 08:46:15 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945
  InstallationDate: Installed on 2015-08-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1494943] Re: module signing can fail if the module identifier starts with a zero byte

** Summary changed:

- module signing can fail if the module identifier starts with a 0 byte
+ module signing can fail if the module identifier starts with a zero byte

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

Title:
  module signing can fail if the module identifier starts with a zero
  byte

Status in linux package in Ubuntu:
  In Progress

Bug description:
  module signing can fail if the module identifier starts with a 0.
  This occurs randomly.

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

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

[Kernel-packages] [Bug 1061508] Re: System Boots Every Other Time

2015-09-13 Thread tjboadwa

I have this problem now with 14.04 LTS installed on a Lenovo B50-45.  If
I power the computer up there is a blank screen.  Then if I power down
and power up again I am successful.  So every other time.

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

Title:
  System Boots Every Other Time

Status in linux package in Ubuntu:
  Expired

Bug description:
  After a fresh install of 12.04.1  the system boots every other time
  it's started or restarted.  When it doesn't boot the screen goes to
  sleep as the system hangs/freezes.  The system boots fine under
  10.04.4.

  Steps to reproduce:
  1)  Install using 12.04.1
  2)  Boot the system
  3)  If the system boots properly restart or shutdown the system

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-31-generic-pae 3.2.0-31.50
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  name   2478 F pulseaudio
   /dev/snd/pcmC0D0p:   name   2478 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 23'
     Mixer name : 'Realtek ALC888'
     Components : 'HDA:10ec0888,103c2a58,0011'
     Controls  : 40
     Simple ctrls  : 21
  Date: Thu Oct  4 06:05:55 2012
  HibernationDevice: RESUME=UUID=9d64ac90-738f-49eb-a637-ad5473e780b4
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423.2)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP-Pavilion GC384AV-ABA m8000e
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic-pae 
root=/dev/mapper/sda6_crypt ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-31-generic-pae N/A
   linux-backports-modules-3.2.0-31-generic-pae  N/A
   linux-firmware1.79.1
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UdevDb: Error: [Errno 2] No such file or directory
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.09
  dmi.board.name: NARRA
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd05/15/2007:svnHP-Pavilion:pnGC384AV-ABAm8000e:pvr:rvnASUSTekComputerINC.:rnNARRA:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: GC384AV-ABA m8000e
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1488426] Re: High CPU usage of kworker/ksoftirqd

One more thing that it's worth mentioning.
My Dell laptop came with ubuntu 14.04 preinstalled.
I tried to install all the updates (around 600MB of packages), had some issues 
and decided to download and install the latest LTS image (14.04.3).
What I'm trying to say is that I only noticed this bug after I reinstalled 
Ubuntu so I'm not sure if it also affected the Dell preinstalled Ubuntu image 
which might have had some additional proprietary divers included.
At this point I'm unable to reinstall the Dell stock Ubuntu image because I 
didn't create a recovery disk.

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

Title:
  High CPU usage of kworker/ksoftirqd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  kworker consuming 71.5% cpu resource
  ksoftirqd consuming 28.9% cpu resource

  It leads to power consumption issue and sometimes leads to BT does not
  work.

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

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

[Kernel-packages] [Bug 1486378] Re: Linux kernel update (3.13.0-62) breaks system: can't boot to GUI or shut down cleanly

Pacific Seascape, could you please boot into 
http://cdimage.ubuntu.com/daily-live/current/ , don't install any packages (ex. 
nvidia proprietary drivers) and then execute the following in a terminal:
apport-collect 1486378

** Summary changed:

- Linux kernel update (3.13.0-62) breaks system: can't boot to GUI or shut down 
cleanly
+ Can't boot to GUI or shut down cleanly with kernel 3.13.0-62

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

Title:
  Can't boot to GUI or shut down cleanly with kernel 3.13.0-62

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

Bug description:
  I was prompted today to update to a new kernel, linux-
  image-3.13.0-62-generic, along with its accompanying headers.

  I install kernel updates frequently on my system without any problems.
  To date, Trusty 14.04.3 LTS has been very trusty. But after installing
  linux-image-3.13.0-62-generic, I found my system hanging as it tried
  to reboot. It gave me this message:

  ModemManager[833]:  Could not acquire the
  'org.freedesktop.ModemManager1' service name

  ModemManager[833]:  ModemManager is shut down

  It just sat there like that for a long time. Finally I powered it off.

  Upon restarting, the system refused to boot to the GUI. It normally
  flashes an NVDIA logo before showing the login prompt (I use Kubuntu).
  But this time it simply showed a black screen.

  I logged in to check for updates. There were none available.

  I tried rebooting. The system got stuck again. I got it unstuck; still
  it would not boot to the GUI or shut down cleanly.

  After several cycles of this I went into the recovery mode and
  selected the grub option. That allowed me to boot to the GUI. But
  still the system wouldn't shut down cleanly. It showed me a number of
  different messages during the various times I tested its capacity to
  reboot, some similar to the one above and others different. The
  messages were not consistent.

  The command sudo shutdown -r 0 sometimes prevented the system from
  hanging on reboot, but not always.

  At last my suspicion fell on the kernel, since it had just been
  updated and there hadn't been any other packages changed with it. The
  next go-around, I started up with the previous kernel, 3.13.0-61, by
  selecting it in grub on startup. Sure enough, after choosing this
  previous kernel, the system started with no fuss, and it shut down
  gracefully without hanging, too. I promptly uninstalled the kernel
  update and its associated headers so I wouldn't have to hold down the
  shift key on every boot cycle. With linux-image-3.13.0-62-generic
  gone, my system is back to normal operation.

  I can't understand why a kernel update pushed out to a long term
  support release would break my system so horribly. I specifically run
  the LTS release on my main systems to avoid these kinds of issues.

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

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

[Kernel-packages] [Bug 1486188] Re: hid_magicmouse freeze periodicaly and on rmmod

** Tags added: latest-bios-1305

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

Title:
  hid_magicmouse freeze periodicaly and on rmmod

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  hid_magicmouse freeze periodicaly and on rmmod

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: 
boot/vmlinuz-4.1.0-3-generic]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  svlad  3269 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 18 21:34:14 2015
  HibernationDevice: RESUME=UUID=4f6f6cec-e985-44ce-b7ba-e7afe11819e1
  InstallationDate: Installed on 2015-08-07 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150807)
  MachineType: System manufacturer P5K-E
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic 
root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K-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.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5K-E
  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/1486188/+subscriptions

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.10 -proposed tracker

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

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

** Description changed:

  This bug is for tracking the 4.2.0-10.10 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
+ kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 11:00 UTC

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

Title:
  linux: 4.2.0-10.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 11:00 UTC

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

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.10 -proposed tracker

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Fix Released

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.2.0-10.10 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 11:00 UTC
+ proposed-announcement-sent:True

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

Title:
  linux: 4.2.0-10.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 11:00 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1488426] Re: High CPU usage of kworker/ksoftirqd

As said before I'm willing to help with debugging and testing.
If someone knows how to debug this please let me know.

On my laptop I can easily reproduce it by following these steps:
- install chromium browser:
$ sudo apt-get install chromium-browser
- install the Adobe flash plugin (you might need to enable the Canonical 
Partners repo)
$ sudo apt-get install adobe-flashplugin
- open Chromium browser and go to youtube or any other website with flash videos

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

Title:
  High CPU usage of kworker/ksoftirqd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  kworker consuming 71.5% cpu resource
  ksoftirqd consuming 28.9% cpu resource

  It leads to power consumption issue and sometimes leads to BT does not
  work.

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

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

[Kernel-packages] [Bug 1485593] Re: My touchpad is not working.

yes998, as per http://us.acer.com/ac/en/US/content/drivers an update to
your computer's buggy and outdated BIOS is available (1.13). If you
update to this following https://help.ubuntu.com/community/BIOSUpdate
does it change anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then
please mark this report Status Confirmed.

Thank you for your understanding.

** Tags added: bios-outdated-1.13

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

Title:
  My touchpad is not working.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 14 and 15 on same laptop and both versions seems like
  they did not detect my touchpad. I am currently using Ubuntu 14. USB
  Wireless mouse works when plugged in.

  Laptop model: Acer Aspire E 11 ES1-111-C53P
  Touchpad Manufacturer: Synaptics
  When Symptom first appeared: At the start of the installation of Ubuntu 14 or 
15.

  dmesg: 
https://drive.google.com/file/d/0B8ZBu31DPC0kRHg4TGRRZExONGM/view?usp=sharing
  devices: 
https://drive.google.com/file/d/0B8ZBu31DPC0kSTljOUtjaXdzTGs/view?usp=sharing
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kintetsu   1995 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=32e10486-b083-4428-b023-cc22fca6eff8
  InstallationDate: Installed on 2015-08-17 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire ES1-111
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=eab56626-1778-439c-a6f8-b1722d464f0b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.127.15
  Tags:  trusty
  Uname: Linux 3.19.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnAspireES1-111:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire ES1-111
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

2015-09-13 Thread dino99

hi Ivan,

you are testing an usual config here; but if i can mind you some details:
- utopic has already reached EOL some times ago
- even Wily has not yet a complete multiarch portage; so many libs/apps still 
need some work on that side. Of course Utopic status is even worst.

I feel you are playing an old success : "mission impossible", and doubt
devs will waste their precious time about such an experience on a
deprecated release.

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

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

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in udev package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture:

[Kernel-packages] [Bug 1486188] Re: hid_magicmouse freeze periodicaly and on rmmod

SaNuke, now that the WIly kernel is rebased to the 4.2 series, could you
please advise if it is still reproducible with it?

** Tags added: kernel-fixed-upstream-4.2-rc7 needs-reverse-bisect

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

Title:
  hid_magicmouse freeze periodicaly and on rmmod

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  hid_magicmouse freeze periodicaly and on rmmod

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: 
boot/vmlinuz-4.1.0-3-generic]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  svlad  3269 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 18 21:34:14 2015
  HibernationDevice: RESUME=UUID=4f6f6cec-e985-44ce-b7ba-e7afe11819e1
  InstallationDate: Installed on 2015-08-07 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150807)
  MachineType: System manufacturer P5K-E
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic 
root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K-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.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5K-E
  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/1486188/+subscriptions

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

[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

2015-09-13 Thread dino99

i suggest to upgrade to Wily as it might be easier

As your experiment has catch my curiosity, i've searched around, and
found some threads; they mainly said  'yes that should be possible, with
lot of headaches'

So good luck :) :)

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in udev package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A

[Kernel-packages] [Bug 1494943] Re: module signing can fail if the module identifier starts with a zero byte

Identified issue in the kernel and pushed proposed fix upstream.

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

Title:
  module signing can fail if the module identifier starts with a zero
  byte

Status in linux package in Ubuntu:
  In Progress

Bug description:
  module signing can fail if the module identifier starts with a 0.
  This occurs randomly.

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

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

[Kernel-packages] [Bug 1494403] fozzie (amd64) - tests ran: 194, failed: 0

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

tests ran: 194, failed: 0;
  
http://kernel.ubuntu.com/testing/4.2.0-10.10/fozzie__4.2.0-10.10__2015-09-13_16-05-00/results-index.html

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

Title:
  linux: 4.2.0-10.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 10. September 2015 17:05 UTC
  kernel-phase-changed:Thursday, 10. September 2015 17:05 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Thursday, 10. September 2015 18:01 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.11 -proposed tracker

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Fix Released

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.2.0-10.11 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC
+ proposed-announcement-sent:True

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

Title:
  linux: 4.2.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.11 -proposed tracker

2015-09-13 Thread Launchpad Bug Tracker

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

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

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

Title:
  linux: 4.2.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC

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

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.11 -proposed tracker

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

** Description changed:

  This bug is for tracking the 4.2.0-10.11 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
+ kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC

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

Title:
  linux: 4.2.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC

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

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

[Kernel-packages] [Bug 1494403] Re: linux: 4.2.0-10.10 -proposed tracker

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

** This bug has been marked a duplicate of bug 1495208
   linux: 4.2.0-10.11 -proposed tracker

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

Title:
  linux: 4.2.0-10.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 10. September 2015 17:05 UTC
  kernel-phase-changed:Thursday, 10. September 2015 17:05 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Thursday, 10. September 2015 18:01 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1493357] Re: linux: 4.2.0-8.8 -proposed tracker

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

** This bug is no longer a duplicate of bug 1494403
   linux: 4.2.0-10.10 -proposed tracker
** This bug has been marked a duplicate of bug 1495208
   linux: 4.2.0-10.11 -proposed tracker

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

Title:
  linux: 4.2.0-8.8 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 08. September 2015 12:45 UTC
  kernel-Package-testing-start:Wednesday, 09. September 2015 21:00 UTC
  kernel-phase:Testing
  kernel-phase-changed:Wednesday, 09. September 2015 21:00 UTC
  kernel-Prepare-package-end:Wednesday, 09. September 2015 21:00 UTC

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

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

[Kernel-packages] [Bug 1493970] Re: linux: 4.2.0-9.9 -proposed tracker

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

** This bug is no longer a duplicate of bug 1494403
   linux: 4.2.0-10.10 -proposed tracker
** This bug has been marked a duplicate of bug 1495208
   linux: 4.2.0-10.11 -proposed tracker

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

Title:
  linux: 4.2.0-9.9 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Wednesday, 09. September 2015 18:57 UTC
  kernel-phase-changed:Wednesday, 09. September 2015 18:57 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Wednesday, 09. September 2015 19:00 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.11 -proposed tracker

** Summary changed:

- linux: 4.2.0-10.10 -proposed tracker
+ linux: 4.2.0-10.11 -proposed tracker

** Description changed:

- This bug is for tracking the 4.2.0-10.10 upload package. This bug will
+ This bug is for tracking the 4.2.0-10.11 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
- kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 11:00 UTC
- proposed-announcement-sent:True

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => New

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

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

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

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Fix Released => New

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Tim Gardner (timg-tpi) => Andy Whitcroft (apw)

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Tim Gardner (timg-tpi) => 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/1495208

Title:
  linux: 4.2.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC

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

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

[Kernel-packages] [Bug 1486746] Re: ubuntu 15.04 after screen lock, laptop cant wake up and black screen seen

2015-09-13 Thread mehmet

I installed the kernel 
"linux-image-4.2.0-040200rc7-generic_4.2.0-040200rc7.201508162030_i386.deb" as 
Joseph Salisbury (jsalisbury)  told. The deb file is downloaded from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc7-unstable/ .
 
I have booted without any problems and the kernel is:

uname -r
4.2.0-040200rc7-generic

I have marked the status as Confirmed.

I will test issue .

Thank you so much for your concern.

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

Title:
  ubuntu 15.04 after screen lock, laptop cant wake up and black screen
  seen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Asus laptop and i installed ubuntu 15.04 with all packages are 
up-to-date. When lock the screen and if locking takes long, my laptop cant wake 
up and black screen seen. Everytime I have to hard reset ( by pressing on 
button for ten seconds) .
  --- 
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mehmet 1245 F pulseaudio
   /dev/snd/controlC1:  mehmet 1245 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-08-24 (19 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: ASUSTeK Computer Inc. M51Vr
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=9bb3f21e-8737-45ba-83f1-2833fcbda2eb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-28-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/17/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Vr
  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.:bvr211:bd11/17/2008:svnASUSTeKComputerInc.:pnM51Vr:pvr1.0:rvnASUSTeKComputerInc.:rnM51Vr:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Vr
  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/1486746/+subscriptions

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.11 -proposed tracker

** Changed in: kernel-development-workflow/prepare-package
   Status: New => 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/1495208

Title:
  linux: 4.2.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC
  proposed-announcement-sent:True

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

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

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

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

apport-collect 1480190

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

Title:
  Python segmentation fault when using GPIO pins (Raspberry Pi 2)

Status in ubuntu-mate:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I noticed that there's a critical problem with using the GPIO pins on
  the Raspberry Pi 2 running Ubuntu Mate. Everytime I try enabling a pin
  with Python it crashes with the error message "Segmentation fault
  (core dumped)".

  It seems like a problem with the Kernel like it is explained here:
  http://stackoverflow.com/questions/30442719/getting-segmentation-
  fault-when-using-rpi-gpio-setup-on-raspberry-pi-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1480190/+subscriptions

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

[Kernel-packages] [Bug 1495208] Re: linux: 4.2.0-10.11 -proposed tracker

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => 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/1495208

Title:
  linux: 4.2.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC

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

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

[Kernel-packages] [Bug 1480190] [NEW] Python segmentation fault when using GPIO pins (Raspberry Pi 2)

2015-09-13 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

I noticed that there's a critical problem with using the GPIO pins on
the Raspberry Pi 2 running Ubuntu Mate. Everytime I try enabling a pin
with Python it crashes with the error message "Segmentation fault (core
dumped)".

It seems like a problem with the Kernel like it is explained here:
http://stackoverflow.com/questions/30442719/getting-segmentation-fault-
when-using-rpi-gpio-setup-on-raspberry-pi-2

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

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

-- 
Python segmentation fault when using GPIO pins (Raspberry Pi 2)
https://bugs.launchpad.net/bugs/1480190
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 1488426] Re: High CPU usage of kworker/ksoftirqd

Also tested and reproduced the bug with the following kernels:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1.6-unstable/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.9-wily/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-vivid/

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

Title:
  High CPU usage of kworker/ksoftirqd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  kworker consuming 71.5% cpu resource
  ksoftirqd consuming 28.9% cpu resource

  It leads to power consumption issue and sometimes leads to BT does not
  work.

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

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

[Kernel-packages] [Bug 1492331] Re: kernel crashes on boot (ubuntu as a Hyper-V guest)

2015-09-13 Thread Nils Schmidt

This one is 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/1492331

Title:
  kernel crashes on boot (ubuntu as a Hyper-V guest)

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

Bug description:
  My Ubuntu 14.04 VM (Hyper-V / Windows Server 2008 R2) crashes directly
  after the grub boot loader screen. Kernel packages linux-
  image-3.13.0-62-generic and linux-image-3.13.0-63-generic are affected
  while linux-image-3.13.0-61-generic works like all previous versions
  did. Unfortunatly no /var/log/kern.log is written at all with the
  affected kernels.

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

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

[Kernel-packages] [Bug 1480190] Re: Python segmentation fault when using GPIO pins (Raspberry Pi 2)

2015-09-13 Thread Matthias Klose

** Package changed: python2.7 (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/1480190

Title:
  Python segmentation fault when using GPIO pins (Raspberry Pi 2)

Status in ubuntu-mate:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I noticed that there's a critical problem with using the GPIO pins on
  the Raspberry Pi 2 running Ubuntu Mate. Everytime I try enabling a pin
  with Python it crashes with the error message "Segmentation fault
  (core dumped)".

  It seems like a problem with the Kernel like it is explained here:
  http://stackoverflow.com/questions/30442719/getting-segmentation-
  fault-when-using-rpi-gpio-setup-on-raspberry-pi-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1480190/+subscriptions

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

[Kernel-packages] [Bug 1483467] Re: [Acer Aspire V5-573G] suspend/resume failure

2015-09-13 Thread Launchpad Bug Tracker

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

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

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

Title:
  [Acer Aspire V5-573G] suspend/resume failure

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  It looks to be a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416557 bug
  (which was closed because it has expired).

  I made kernel bisection (log attached) as was requested in bug 1416557 and 
found
  # first bad commit: [faae404ebdc6bba744919d82e64c16448eb24a36] ACPICA: Add 
"Windows 2013" string to _OSI support.

  It appears that resume fails because ACPI OSI reports OS to be "Windows 2013".
  I added boot kernel parameter acpi_osi="!Windows 2013" and now able to 
suspend-resume normally (checked in kernels up to 3.16)

  I have no idea whar ACPI OSI means and why  "Windows 2013" prevents
  from normal resume (the problem seems to happen somwhere in nouveau
  driver). I just spend 3 days for this bisection and want others ubuntu
  users have this problem  fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-45-generic 3.16.0-45.60~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 04:48:58 2015
  InstallationDate: Installed on 2015-08-09 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1495208] fozzie (amd64) - tests ran: 194, failed: 0

tests ran: 194, failed: 0;
  
http://kernel.ubuntu.com/testing/4.2.0-10.11/fozzie__4.2.0-10.11__2015-09-13_19-26-00/results-index.html

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

Title:
  linux: 4.2.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Sunday, 13. September 2015 10:29 UTC
  kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

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

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

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


** Tags added: verification-needed-vivid

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

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

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

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

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

[Kernel-packages] [Bug 1486146] Re: recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU (MSG_PEEK|MSG_WAITALL)

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

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

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


** Tags added: verification-needed-trusty

** Tags added: verification-needed-vivid

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

Title:
  recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU
  (MSG_PEEK|MSG_WAITALL)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-utopic package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed

Bug description:
  In a multi-threaded pthreads process running on Ubuntu 14.04 AMD64
  (with over 1000 threads) which uses real time FIFO scheduling, we
  occasionally see calls to recv() with flags (MSG_PEEK | MSG_WAITALL)
  get stuck in an infinte loop or deadlock meaning the threads lock up
  chewing as much CPU as they can (due to FIFO scheduling) while stuck
  inside recv().

  Here's an example gdb back trace:

  [Switching to thread 4 (Thread 0x7f6040546700 (LWP 27251))]
  #0  0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, 
buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at 
../sysdeps/unix/sysv/linux/x86_64/recv.c:33
  33  ../sysdeps/unix/sysv/linux/x86_64/recv.c: No such file or directory.
  (gdb) bt
  #0  0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, 
buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at 
../sysdeps/unix/sysv/linux/x86_64/recv.c:33
  #1  0x00421945 in recv (__flags=258, __n=5, __buf=0x7f6040543600, 
__fd=146) at /usr/include/x86_64-linux-gnu/bits/socket2.h:44
  [snip]

  The socket is a TCP socket in blocking mode, the recv() call is inside
  an outer loop with a counter, and I've checked the counter with gdb
  and it's always at 1, meaning that I'm sure that the outer loop isn't
  the problem, the thread is indeed deadlocked inside the recv()
  internals.

  Other nodes:
  * There always seems to be 2 or more threads deadlocked in the same place 
(same recv() call but with distinct FDs)
  * The threads calling recv() have cancellation disbaled by previously 
executing: thread_setcancelstate(PTHREAD_CANCEL_DISABLE, NULL);

  I've even tried adding a poll() call for POLLRDNORM on the socket
  before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make
  sure there's data available on the socket before calling *recv()*, but
  it makes no difference.

  So, I don't know what is wrong here, I've read all the recv()
  documentation and believe that recv() is being used correctly, the
  only conclusion I can come to is that there is a bug in libc recv()
  when using flags MSG_PEEK | MSG_WAITALL with thousands of pthreads
  running.

  ===
  break-fix: - dfbafc995304ebb9a9b03f65083e6e9cea143b20

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

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

[Kernel-packages] [Bug 1469829] Re: ppc64el should use 'deadline' as default io scheduler

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

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

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

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

Title:
  ppc64el should use 'deadline' as default io scheduler

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

Bug description:
  [Impact]
  Using cfq instead of deadline as the default io scheduler starves certain 
workloads and causes performance issues. In addition every other arch we build 
uses deadline as the default scheduler.

  [Fix]
  Change the configuration to the following for ppc64el:
  CONFIG_DEFAULT_DEADLINE=y
  CONFIG_DEFAULT_IOSCHED="deadline"

  [Test Case]
  Boot and cat /sys/block/*/queue/scheduler to see if deadline is being used.

  --

  -- Problem Description --

  Firestone system given to DASD group failed HTX overnight test with 
miscompare error.
  HTX mdt.hdbuster was running on secondary drive and failed about 12 hours 
into test

  HTX miscompare analysis:
  -==

  Device under test: /dev/sdb
  Stanza running: rule_3
  miscompare offset: 0x40
  Transfer size: Random Size
  LBA number: 0x70fc
  miscompare length: all the blocks in the transfer size

  *- STANZA 3: Creates number of threads twice the queue depth. Each thread  -*
  *- doing 2 num_oper with RC operation with xfer size between 1 block   -*
  *- to 256K.-*

  This miscompare shows read operation is unable to get the expected
  data from the disk. The re-read buffer also shows the same data as the
  first read operation. Since the first read and next re-read shows same
  data, there could be a write operation (of previous rule stanza to
  initialize disk with pattern 007 ) failure on the disk. The same
  miscompare behavior shows for all the blocks in the transfer size.

  /dev/sdb  Jun  2 02:29:43 2015 err=03b6 sev=2 hxestorage  
<<===  device name (/dev/sdb)
  rule_3_13  numopers= 2  loop=   767  blk=0x70fc len=89088
   min_blkno=0 max_blkno=0x74706daf, RANDOM access
  Seed Values= 37303, 290, 23235
  Data Pattern Seed Values = 37303, 291, 23235
  BWRC LBA fencepost Detail:
  th_nummin_lba  max_lba  status
   0 01c9be3ffR
   1  1d1c1b6c3a3836d7F
   2  3a3836d857545243F
   3  5754524474706dafF
  Miscompare at buffer offset 64 (0x40) <<===   
miscompare offset (0x40)
  (Flags: badsig=0; cksum=0x6)  Maximum LBA = 0x74706daf
  wbuf (baseaddr 0x3ffe1c0e6600) b0ff
  rbuf (baseaddr 0x3ffe1c0fc400) 850100fc700200fd700300fe700400ff7005
  Write buffer saved in /tmp/htxsdb.wbuf1
  Read buffer saved in /tmp/htxsdb.rbuf1
  Re-read fails compare at offset64; buffer saved in /tmp/htxsdb.rerd1
  errno: 950(Unknown error 950)

  Asghar reproduced that HTX hang he is seeing. Looking in the kernel
  logs I see some messages from the kernel that there are user threads
  blocked on getting reads serviced. So likely HTX is seeing the same
  thing. I've asked Asghar to try using the deadline I/O scheduler
  rather than CFQ to see if that makes any difference. If that does not
  make any difference, the next thing to try is reducing the queue depth
  of the device. Right now its 31, which I think is pretty high.

  Step 1:

  echo deadline > /sys/block/sda/queue/scheduler
  echo deadline > /sys/block/sdb/queue/scheduler

  If that reproduces the issue, go to step 2:

  echo cfq > /sys/block/sda/queue/scheduler
  echo cfq > /sys/block/sdb/queue/scheduler
  echo 8 > /sys/block/sda/device/queue_depth
  echo 8 > /sys/block/sdb/device/queue_depth

  Breno - it looks like the default I/O scheduler + default queue depth
  for the SATA disks in Firestone is not optimal, in that when running a
  heavy I/O workload, we see read starvation occurring, which is making
  the system nearly unusable.

  Once we changed the I/O scheduler from cfq to deadline, all the issues
  went away and the system is able to run the same workload yet still be
  responsive. Suggest we either

[Kernel-packages] [Bug 1483320] Re: [BDW] VGA output regression on 4.2 (was: Migrate Broadwell to use i915_bpo)

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

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

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


** Tags added: verification-needed-vivid

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

Title:
  [BDW] VGA output regression on 4.2 (was: Migrate Broadwell to use
  i915_bpo)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  There are several bugs affecting Broadwell generation graphics in the
  vivid kernel (3.19), but not found in 4.2rc which i915_bpo module is
  based on. In order to support our OEM partners (and other BDW users)
  it would make sense to migrate BDW to use i915_bpo instead.

  The known (public) bugs this would fix are:

  - screen is black after xrandr rotate command
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446979

  - changing the VT causes flicker
  https://bugs.freedesktop.org/show_bug.cgi?id=85583
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450557

  - GPU hangs on resume
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468232
  (and dupes, which I believe there are several of)

  - and some OEM machines can't always hotplug the HDMI output (no
  public bug AIUI)

  the migration should not be too risky, since i915_bpo is already used
  for Braswell which is same generation as (=based on) BDW.

  UPDATE:

  Track VGA output regression here, found in 4.2 and fixed upstream by

  commit 6fa2d197936ba0b8936e813d0adecefac160062b
  Author: Ander Conselvan de Oliveira 
  Date:   Mon Aug 31 11:23:28 2015 +0300

  i915: Set ddi_pll_sel in DP MST path

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

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

[Kernel-packages] [Bug 1489501] Re: [i915_bpo] Sync to v4.2-rc8

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

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

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


** Tags added: verification-needed-vivid

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

Title:
  [i915_bpo] Sync to v4.2-rc8

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  A handful of fixes made it upstream. Need to revert a sauce commit
  first so that another revert can be applied.

   drm/i915: Avoid TP3 on CHV
   drm/i915: remove HBR2 from chv supported list
   Revert "drm/i915: Add eDP intermediate frequencies for CHV"
   Revert "drm/i915: Allow parsing of variable size child device entries from 
VBT"
   drm/i915: Flag the execlists context object as dirty after every use
   drm/i915: Commit planes on each crtc separately.
   drm/i915: calculate primary visibility changes instead of calling from 
set_config
   drm/i915: Only dither on 6bpc panels
   Revert "UBUNTU: SAUCE: i915_bpo: drm/i915: Allow parsing of variable size 
child device entries from VBT, addendum v2"

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

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

[Kernel-packages] [Bug 1488035] Re: OSDs Linked list corruption causes kernel BUG at /build/buildd/linux-3.13.0/net/ceph/osd_client.c:892!

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

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

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


** Tags added: verification-needed-trusty

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

Title:
  OSDs Linked list corruption causes kernel BUG at
  /build/buildd/linux-3.13.0/net/ceph/osd_client.c:892!

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

Bug description:
  [Impact]

  The node which mounts a ceph rbd volume causes a panic when all OSD
  daemons on the all ceph nodes are restarted.

  [642981.871592] [ cut here ]
  [642981.912255] kernel BUG at
  /build/buildd/linux-3.13.0/net/ceph/osd_client.c:892!
  [642981.994517] invalid opcode:  [#1] SMP
  [642982.037227] Modules linked in: xt_multiport iptable_mangle xt_nat
  xt_tcpudp veth xfs rbd libceph libcrc32c xt_addrtype xt_conntrack
  ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
  iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge aufs
  ipmi_devintf joydev gpio_ich x86_pkg_temp_thermal intel_powerclamp coretemp
  kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel
  aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd hid_generic mei_me
  ioatdma mei lpc_ich wmi ipmi_si 8021q garp stp mrp llc bonding
  acpi_power_meter mac_hid lp parport ixgbe usbhid dca tg3 ahci libahci hid
  ptp megaraid_sas mdio pps_core
  [642982.528519] CPU: 0 PID: 1062099 Comm: kworker/0:6 Not tainted
  3.13.0-45-generic #74-Ubuntu
  [642982.648057] Hardware name: NEC Express5800/R120f-1M
  [N8100-2203Y]/MS-S0901, BIOS 5.0.4016 12/17/2014
  [642982.775433] Workqueue: ceph-msgr con_work [libceph]
  [642982.841300] task: 881028444800 ti: 880d92374000 task.ti:
  880d92374000
  [642982.973255] RIP: 0010:[] []
  osd_reset+0x22e/0x2c0 [libceph]
  [642983.114484] RSP: 0018:880d92375d80 EFLAGS: 00010283
  [642983.188540] RAX: 8800197f2ca8 RBX: 882028194750 RCX:
  880036bcdc48
  [642983.334096] RDX: 8800197f2ca8 RSI: 8800197f2c10 RDI:
  0286
  [642983.485552] RBP: 880d92375dd8 R08:  R09:
  
  [642983.643277] R10: 8160afcf R11: ea00710cae00 R12:
  8800197f2c58
  [642983.805364] R13: 882028194810 R14: 880036bcdbf8 R15:
  880036bcdc18
  [642983.968728] FS: () GS:88103fa0()
  knlGS:
  [642984.135368] CS: 0010 DS:  ES:  CR0: 80050033
  [642984.220577] CR2: 7f60d4cb7868 CR3: 01c0e000 CR4:
  001407f0
  [642984.383051] Stack:
  [642984.459809] 8820281947a8 882028194760 8800197f2800
  8800197f2ca8
  [642984.618038] 880d92375da0 880d92375da0 8800197f2c10
  8800197f2830

  [Fix]

  A linked list to manage OSDs in the kernel was corrupted when restarting
  all OSD daemons on all ceph nodes at the almost same time.

  The issues must be fixed by the following.

  libceph: must use new tid when watch is resent
  http://tracker.ceph.com/issues/8806

  This includes two patched and they has been already released.

  http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/20878
  [PATCH 1/2] libceph: abstract out ceph_osd_request enqueue logic
  [PATCH 2/2] libceph: resend lingering requests with a new tid

  3.18 kernel adopts the fixes.

  libceph: abstract out ceph_osd_request enqueue logic
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f671b581f1dac61354186b7373af5f97fe420584
  libceph: resend lingering requests with a new tid
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2cc6128ab2afff7864dbdc33a73e2deaa935d9e0

  [Test Case]

  After setting up the ceph environment, repeatedly issued the following
  command from a node to all ceph nodes.

  rsh -i key -l ubuntu sn_hostname sudo service ceph-all restart

  And verify if there is panics.

  A test kernel with this fix was verified to fix this problem.

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

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

[Kernel-packages] [Bug 1476987] Re: Headset mic support for a Dell machine

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

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

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


** Tags added: verification-needed-vivid

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

Title:
  Headset mic support for a Dell machine

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  This bug is used for tracking only, please do not triage.

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

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

[Kernel-packages] [Bug 1487085] Re: Ubuntu 14.04.3 LTS Crash in notifier_call_chain after boot

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

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

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


** Tags added: verification-needed-vivid

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

Title:
  Ubuntu 14.04.3 LTS Crash in notifier_call_chain after boot

Status in linux package in Ubuntu:
  New
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Users of 3.19 kernel with power8 machines get a kernel crash on boot.

  [Test Case]
  Boot system.

  [Fix]
  commit 792f96e9a769b799a2944e9369e4ea1e467135b2 needed to be backported in 
addition to d7cf83fcaf1b1668201eae4cdd6e6fe7a2448654. Our 3.19 kernel had a 
partial backport of the first patch.

  --

  
  ---Problem Description---
  Installed Ubuntu 14.04.3 LTS on Palmetto and its crashing after booting to 
login.
  This happens every time I boot Ubuntu 14.04.3 LTS.  I've reinstalled Ubuntu 
and replaced the hard disk as well and re-installed.  Still crashing.

  ---uname output---
  Linux paul40 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:10:52 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Palmetto

  ---System Hang---
   Ubuntu OS crashes and cannot access host. Must reboot system

  ---Steps to Reproduce---
   Boot system

  Oops output:
   [   33.132376] Unable to handle kernel paging request for data at address 
0x200
  [   33.132565] Faulting instruction address: 0xc00dbc60
  [   33.133422] Oops: Kernel access of bad area, sig: 11 [#1]
  [   33.134410] SMP NR_CPUS=2048 NUMA PowerNV
  [   33.134478] Modules linked in: ast ttm drm_kms_helper joydev mac_hid 
drm hid_generic usbhid hid syscopyarea sysfillrect sysimgblt i2c_algo_bit 
ofpart cmdlinepart at24 uio_pdrv_genirq powernv_flash mtd ipmi_powernv 
powernv_rng opal_prd ipmi_msghandler uio uas usb_storage ahci libahci
  [   33.139112] CPU: 24 PID: 0 Comm: swapper/24 Not tainted 
3.19.0-26-generic #28~14.04.1-Ubuntu
  [   33.139943] task: c13cccb0 ti: c00fff70 task.ti: 
c1448000
  [   33.141642] NIP: c00dbc60 LR: c00dbd94 CTR: 

  [   33.142605] REGS: c00fff703980 TRAP: 0300   Not tainted  
(3.19.0-26-generic)
  [   33.143417] MSR: 90009033   CR: 
28002888  XER: 
  [   33.144244] CFAR: c0008468 DAR: 0200 DSISR: 
4000 SOFTE: 0
  GPR00: c00dbd94 c00fff703c00 c144cc00 c15f03c0
  GPR04: 0007 c15f03b8  
  GPR08:  0200 c006c394 90001003
  GPR12: 2200 cfb8d800 0058 
  GPR16: c1448000 c1448000 c1448080 c0e9a880
  GPR20: c1448080 0001 0002 0012
  GPR24: c00f1e432200   c15f03b8
  GPR28: 0007  c15f03c0 
  [   33.157013] NIP [c00dbc60] notifier_call_chain+0x70/0x100
  [   33.157818] LR [c00dbd94] atomic_notifier_call_chain+0x44/0x60
  [   33.162090] Call Trace:
  [   33.162845] [c00fff703c00] [0008] 0x8 (unreliable)
  [   33.163644] [c00fff703c50] [c00dbd94] 
atomic_notifier_call_chain+0x44/0x60
  [   33.164647] [c00fff703c90] [c006f2a8] 
opal_message_notify+0xa8/0x100
  [   33.165476] [c00fff703d00] [c00dbc88] 
notifier_call_chain+0x98/0x100
  [   33.167007] [c00fff703d50] [c00dbd94] 
atomic_notifier_call_chain+0x44/0x60
  [   33.167816] [c00fff703d90] [c006f654] 
opal_do_notifier.part.5+0x74/0xa0
  [   33.172166] [c00fff703dd0] [c006f6d8] 
opal_interrupt+0x58/0x70
  [   33.172997] [c00fff703e10] [c01273d0] 
handle_irq_event_percpu+0x90/0x2b0
  [   33.174507] [c00fff703ed0] [c0127658] 
handle_irq_event+0x68/0xd0
  [   33.175312] [c00fff703f00] [c012baf4] 
handle_fasteoi_irq+0xe4/0x240
  [   33.176124] [c00fff703f30] [c01265c8] 
generic_handle_irq+0x58/0x90
  [   33.176936] [c00fff703f60] [c0010f10] __do_irq+0x80/0x190
  [   33.182406] [c00fff703f90] [c002476c] call_do_irq+0x14/0x24
  [   33.183258] [c144ba30] [c00110c0]

[Kernel-packages] [Bug 1488395] Re: backport of driver for I2C on Sunrisepoint PCH