[Kernel-packages] [Bug 1459957] Re: linux: 3.19.0-20.20 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.19.0-20.20 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:Friday, 29. May 2015 08:47 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:01 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:02 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 02. June 2015 08:01 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/1459957

Title:
  linux: 3.19.0-20.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-20.20 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:Friday, 29. May 2015 08:47 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:01 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Security-signoff-end:Tuesday, 02. June 2015 08:01 UTC

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

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

[Kernel-packages] [Bug 1460941] [NEW] arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

Public bug reported:


After running crash from trusty, the failure log in [1] can be observed.

Then I built crash from wily directly, the similar failure[2] can be
observed too.


[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux 

crash 7.0.3
Copyright (C) 2002-2013  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter help copying to see the conditions.
This program has absolutely no warranty.  Enter help warranty for details.
 

crash: invalid/unknown page size: 6144

[2] 
ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
[sudo] password for ubuntu: 

crash 7.0.8
Copyright (C) 2002-2014  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter help copying to see the conditions.
This program has absolutely no warranty.  Enter help warranty for details.
 

crash: invalid/unsupported page size: 6144

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

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

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  New

Bug description:
  
  After running crash from trusty, the failure log in [1] can be observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux 

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   

  crash: invalid/unknown page size: 6144

  [2] 
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
  [sudo] password for ubuntu: 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   

  crash: invalid/unsupported page size: 6144

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

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

[Kernel-packages] [Bug 1459937] Re: Support bluetooth device 0cf3:e007

[Jesse Sung]

** Changed in: hwe-next
 Assignee: (unassigned) = Jesse Sung (wenchien)

** Changed in: hwe-next
   Status: New = In Progress

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

Title:
  Support bluetooth device 0cf3:e007

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

Bug description:
  The firmware of this device is loaded by a new mechanism other than
  ath3k. At least these commits are required:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ace31982585a323afb194f56b9e0486f7bc6570c
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3267c884cefa86c6d48c4d7c5571c20435271ecf
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf906b3db3c2b4f5d4db1db5f35796629c531ac4
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2054111b107d9449393d96dce6b66731bbfea9ad

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

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

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

[bugproxy]

--- Comment From mainam...@in.ibm.com 2015-06-02 06:49 EDT---
Any update on this bug?

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

Title:
  ISST-LTE:Ubuntu15.04: task aio-stress:12277 blocked for more than 120
  seconds.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hemant Kumar hemantkba...@in.ibm.com - 2015-04-13 01:29:44 
==
  Defect Description:
  ===

  I am having one ubuntu 15.04 LE lpar running with regression
  run(BASE/IO/TCP). After some hours of run i was not able to get
  virtual terminal of lpar but i am able to login via ssh. I did ssh and
  i saw these stack traces in dmesg:

  [14889.385371] blk_update_request: critical target error, dev dm-10, sector 
13842352
  [14889.385389] dm-16: WRITE SAME failed. Manually zeroing.
  [16080.244960] INFO: task aio-stress:12275 blocked for more than 120 seconds.
  [16080.244976]   Not tainted 3.19.0-12-generic #12-Ubuntu
  [16080.244979] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [16080.244983] aio-stress  D 3fff7e420818 0 12275  12092 
0x0004
  [16080.244985] Call Trace:
  [16080.244989] [c007704633f0] [c0015a4c] __switch_to+0x1fc/0x350
  [16080.244992] [c00770463440] [c0a3601c] __schedule+0x37c/0x8d0
  [16080.244994] [c00770463670] [c0a3a8b4] 
schedule_timeout+0x254/0x2f0
  [16080.244996] [c00770463760] [c0a377dc] 
wait_for_common+0xec/0x240
  [16080.244998] [c007704637e0] [c02ff1c8] 
writeback_inodes_sb_nr+0xb8/0xe0
  [16080.245000] [c00770463880] [c02ffa78] 
try_to_writeback_inodes_sb_nr+0x98/0xd0
  [16080.245002] [c007704638c0] [c03774bc] 
ext4_nonda_switch+0xdc/0xf0
  [16080.245004] [c00770463900] [c037e340] 
ext4_da_write_begin+0x90/0x3d0
  [16080.245006] [c007704639c0] [c02134f4] 
generic_perform_write+0xf4/0x280
  [16080.245008] [c00770463a60] [c02159e0] 
__generic_file_write_iter+0x2a0/0x430
  [16080.245009] [c00770463ac0] [c0371428] 
ext4_file_write_iter+0x118/0x480
  [16080.245011] [c00770463b80] [c0329c78] aio_run_iocb+0x268/0x450
  [16080.245013] [c00770463ce0] [c032afc4] do_io_submit+0x294/0x670
  [16080.245015] [c00770463e30] [c0009258] syscall_exit+0x0/0x98
  [16080.245017] INFO: task aio-stress:12276 blocked for more than 120 seconds.
  [16080.245022]   Not tainted 3.19.0-12-generic #12-Ubuntu
  [16080.245025] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.

  
  I am running IO regression run from last many weeks but i have not seen this 
issue in any previous kernel. 

  root@riverlp1:~# cat /etc/issue
  Ubuntu Vivid Vervet (development branch) \n \l

  
  root@riverlp1:~# uname -a
  Linux riverlp1 3.19.0-12-generic #12-Ubuntu SMP Fri Apr 3 04:03:54 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
  root@riverlp1:~#

  
  Contact Info: hemantkba...@in.ibm.com

  == Comment: #1 - Hemant Kumar hemantkba...@in.ibm.com - 2015-04-13
  01:32:40 ==

  
  == Comment: #2 - Hemant Kumar hemantkba...@in.ibm.com - 2015-04-13 01:35:52 
==

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

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

[Kernel-packages] [Bug 1459957] onza (amd64) - tests ran: 346, failed: 87

[Brad Figg]

tests ran: 346, failed: 87;
  
http://kernel.ubuntu.com/testing/onza__3.19.0-18.18__2015-06-01_22-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/1459957

Title:
  linux: 3.19.0-20.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-20.20 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:Friday, 29. May 2015 08:47 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:01 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:02 UTC

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

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

[Kernel-packages] [Bug 1460985] [NEW] periodic find task slow ubuntu to death

[god]

Public bug reported:

Periodically something starts 'find' program in the background with
readdir smth in options and it slows down ubuntu to the point the music
and video got hiccups, mouse lags etc. I suspect it's smth related to
package or locatedb updates but can't pinpoint the culprit yet.

Anyway, the bugis in slowdown - background tasks should never-ever
affect the interactive programs running by user. Ideally they should be
started in dedicated, heavily policed systemd slice.

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

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

Title:
  periodic find task slow ubuntu to death

Status in linux package in Ubuntu:
  New

Bug description:
  Periodically something starts 'find' program in the background with
  readdir smth in options and it slows down ubuntu to the point the
  music and video got hiccups, mouse lags etc. I suspect it's smth
  related to package or locatedb updates but can't pinpoint the culprit
  yet.

  Anyway, the bugis in slowdown - background tasks should never-ever
  affect the interactive programs running by user. Ideally they should
  be started in dedicated, heavily policed systemd slice.

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

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

[Kernel-packages] [Bug 1458977] Re: linux-lts-utopic: 3.16.0-39.53~14.04.1 -proposed tracker

[John Johansen]

CVE-2015-0275

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0275

** Changed in: kernel-sru-workflow/security-signoff
   Status: Invalid = Fix Released

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Fix Released
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-39.53~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:Tuesday, 26. May 2015 19:00 UTC
  kernel-stable-master-bug:1458778
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

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

[Kernel-packages] [Bug 1458778] Re: linux: 3.16.0-39.53 -proposed tracker

[John Johansen]

CVE-2015-0275

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0275

** Changed in: kernel-sru-workflow/security-signoff
   Status: Invalid = 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/1458778

Title:
  linux: 3.16.0-39.53 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Utopic:
  New

Bug description:
  This bug is for tracking the 3.16.0-39.53 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, 26. May 2015 08:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

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

[Kernel-packages] [Bug 1459957] Re: linux: 3.19.0-20.20 -proposed tracker

[John Johansen]

Looks good

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress = Fix Released

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

Title:
  linux: 3.19.0-20.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-20.20 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:Friday, 29. May 2015 08:47 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:01 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:02 UTC

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

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

[Kernel-packages] [Bug 1460942] Re: crash: incompatible arguments: vmlinux is not SMP -- live system is SMP

[Ming Lei]

The problem can be fixed by applying the following commit:

commit db07dbf5a7e19806b1629bd4125e6643978c6f9f
Author: Dave Anderson ander...@redhat.com
Date:   Thu Feb 19 16:16:33 2015 -0500

Prepare for the future increment of Linux 3.x to 4.x.
(ander...@redhat.com)

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

Title:
  crash: incompatible arguments:   vmlinux is not SMP -- live system is
  SMP

Status in crash package in Ubuntu:
  New

Bug description:
  
  When I build crash from wily, the failure in [1] can be
  triggered if the kernel is 4.0+.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as aarch64-unknown-linux-gnu...

  WARNING: kernels compiled by different gcc versions:
/home/ubuntu/vmlinux: (unknown)
live system kernel: 4.8.2

  WARNING: kernel version inconsistency between vmlinux and live memory

  crash: incompatible arguments: 
 /home/ubuntu/vmlinux is not SMP -- live system is SMP

  Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
crash [OPTION]... [NAMELIST](live system form)

  Enter crash -h for details.
  ubuntu@am2:~/git/crash-wily$

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

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

[Kernel-packages] [Bug 1460088] Re: [Asus Zenbook Pro UX501JW] Backlight control via hotkeys does not work

[ishbalai]

As adviced in the mailing list the following boot parameter works!

acpi_osi=


I would like to reply to the person and thank him but I have no idea how, so if 
someone can tell me how to reply to those mailing lists please let me know.

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

Title:
  [Asus Zenbook Pro UX501JW] Backlight control via hotkeys does not work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When using the default open source drivers, backlight control does not
  work via keyboard hotkeys on Asus Zenbook Pro UX501JW.

  WORKAROUND: The backlight can be manually set while running on the
  integrated intel graphics (not with hotkeys).

  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2154 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2154 F pulseaudio
  CasperVersion: 1.360
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper 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
  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: 01/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  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.:bvrN501JW.203:bd01/14/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1460088/+subscriptions

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

[Kernel-packages] [Bug 1358704] Re: Atheros AR8161[1969:1091] and AR8162 [1969:1090] mac address would change after powered off for a while

[Liming Wang]

@Po-Hsu Lin

Does with adapter connected mean connecting cable to network card? If yes, so
In your #10 comment, I concluded that:
1. with adapter connected, the mac address is valid.
2. after disconnecting the adapter, the mac address is invalid. 

Is it right? If yes, I don't know what the problem of the bug means.

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

Title:
  Atheros AR8161[1969:1091] and AR8162 [1969:1090] mac address would
  change after powered off for a while

Status in HWE Next Project:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  New

Bug description:
  CID: 201202-10508 
  CID: 201202-10511
  CID: 201202-10527

  The MAC address would change after you power off the system for a
  while (few days)

  201202-10508 and 201202-10511 equipped with AR8162 [1969:1090]
  201202-10527 equipped with AR8161[1969:1091]

  I found this issue when trying to install 12.04.5 via PXE network 
installation.
  The MAC address changing pattern is interesting, there is a common address 
they will change into - 00:13:74:00:00:00

  This looks like a HW issue, but I'm not very confident about it.

  Maybe not a big deal, but this issue would prevent these system from
  being selected into our SRU pool, the worse scenario is that this
  system is attached to a MAC-address-registered network (my dormitory
  network back into university require users to register they MAC
  address)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Aug 19 06:00:11 2014
  InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1358704] Re: Atheros AR8161[1969:1091] and AR8162 [1969:1090] mac address would change after powered off for a while

[Po-Hsu Lin]

Hi Liming Wang,
the adapter here is the power adapter.

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

Title:
  Atheros AR8161[1969:1091] and AR8162 [1969:1090] mac address would
  change after powered off for a while

Status in HWE Next Project:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  New

Bug description:
  CID: 201202-10508 
  CID: 201202-10511
  CID: 201202-10527

  The MAC address would change after you power off the system for a
  while (few days)

  201202-10508 and 201202-10511 equipped with AR8162 [1969:1090]
  201202-10527 equipped with AR8161[1969:1091]

  I found this issue when trying to install 12.04.5 via PXE network 
installation.
  The MAC address changing pattern is interesting, there is a common address 
they will change into - 00:13:74:00:00:00

  This looks like a HW issue, but I'm not very confident about it.

  Maybe not a big deal, but this issue would prevent these system from
  being selected into our SRU pool, the worse scenario is that this
  system is attached to a MAC-address-registered network (my dormitory
  network back into university require users to register they MAC
  address)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Aug 19 06:00:11 2014
  InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1425270] Re: CVE-2015-0275

[John Johansen]

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New = Fix Committed

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New = Fix Committed

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

Title:
  CVE-2015-0275

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux-lts-vivid source package in Utopic:
  Invalid
Status in linux-mako source package in Utopic:
  Invalid
Status in linux-manta source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source 

[Kernel-packages] [Bug 1460942] [NEW] crash: incompatible arguments: vmlinux is not SMP -- live system is SMP

[Ming Lei]

Public bug reported:


When I build crash from wily, the failure in [1] can be
triggered if the kernel is 4.0+.


[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 

crash 7.0.8
Copyright (C) 2002-2014  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter help copying to see the conditions.
This program has absolutely no warranty.  Enter help warranty for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as aarch64-unknown-linux-gnu...

WARNING: kernels compiled by different gcc versions:
  /home/ubuntu/vmlinux: (unknown)
  live system kernel: 4.8.2

WARNING: kernel version inconsistency between vmlinux and live memory

crash: incompatible arguments: 
   /home/ubuntu/vmlinux is not SMP -- live system is SMP

Usage:

  crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
  crash [OPTION]... [NAMELIST]  (live system form)

Enter crash -h for details.
ubuntu@am2:~/git/crash-wily$

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

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

Title:
  crash: incompatible arguments:   vmlinux is not SMP -- live system is
  SMP

Status in crash package in Ubuntu:
  New

Bug description:
  
  When I build crash from wily, the failure in [1] can be
  triggered if the kernel is 4.0+.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as aarch64-unknown-linux-gnu...

  WARNING: kernels compiled by different gcc versions:
/home/ubuntu/vmlinux: (unknown)
live system kernel: 4.8.2

  WARNING: kernel version inconsistency between vmlinux and live memory

  crash: incompatible arguments: 
 /home/ubuntu/vmlinux is not SMP -- live system is SMP

  Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
crash [OPTION]... [NAMELIST](live system form)

  Enter crash -h for details.
  ubuntu@am2:~/git/crash-wily$

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

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

[Kernel-packages] [Bug 1460088] Re: [Asus Zenbook Pro UX501JW] Backlight control via hotkeys does not work

[ishbalai]

Here is the proper link to the mail archive:
http://www.spinics.net/lists/linux-input/msg38964.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/1460088

Title:
  [Asus Zenbook Pro UX501JW] Backlight control via hotkeys does not work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When using the default open source drivers, backlight control does not
  work via keyboard hotkeys on Asus Zenbook Pro UX501JW.

  WORKAROUND: The backlight can be manually set while running on the
  integrated intel graphics (not with hotkeys).

  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2154 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2154 F pulseaudio
  CasperVersion: 1.360
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper 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
  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: 01/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  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.:bvrN501JW.203:bd01/14/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1460088/+subscriptions

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

[Kernel-packages] [Bug 1129865] Re: [Broadcom Combo BT/Wifi Card] 21D3 21D7 Bluetooth does not detect anything at all

[Jeremy Rickard]

Same issue for Ubuntu 14.04 on HP Pavilion P228TX

Bus 001 Device 004: ID 0a5c:216c Broadcom Corp.  BCM43142

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

Title:
  [Broadcom Combo BT/Wifi Card] 21D3 21D7 Bluetooth does not detect
  anything at all

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Precise:
  Won't Fix
Status in linux source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Won't Fix
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Tried several attemtps to scan for new bluetooth devices (BT icon -
  Set up new device).  I tried this with three bluetooth headsets, a
  bluetooth mouse and a cellphone, in an environment where there are
  multiple active bluetooth targets that are discoverable.

  The bluetooth adapter on this system did not, at any time, detect ANY
  bluetooth device.  I verified MY devices by pairing them all with my
  own laptop and all three were pairable.

  rfkill indicates that there are no blocks

  ubuntu@201107-8317:~$ rfkill list
  0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
  1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  and syslog shows where the device entered discovery but it failed to
  detect anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-38-generic 3.2.0-38.60
  ProcVersionSignature: Ubuntu 3.2.0-38.60-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VB Analog [ALC269VB 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1769 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1769 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xa0344000 irq 52'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xa034 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,102804c3,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Tue Feb 19 01:50:56 2013
  HibernationDevice: RESUME=UUID=7cf2dba5-3ce7-4345-8773-ac7bd6078a79
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. Dell System Inspiron M4110
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic 
root=UUID=b677d5d5-25d4-4eae-b0c2-84a4e8c5dd92 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-38-generic N/A
   linux-backports-modules-3.2.0-38-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X19
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Q4E3A3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX19:bd07/22/2011:svnDellInc.:pnDellSystemInspironM4110:pvr:rvnDellInc.:rnQ4E3A3:rvrA11:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Inspiron M4110
  dmi.sys.vendor: Dell Inc.

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

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

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

[Brad Figg]

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

apport-collect 1460985

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

Title:
  periodic find task slow ubuntu to death

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Periodically something starts 'find' program in the background with
  readdir smth in options and it slows down ubuntu to the point the
  music and video got hiccups, mouse lags etc. I suspect it's smth
  related to package or locatedb updates but can't pinpoint the culprit
  yet.

  Anyway, the bugis in slowdown - background tasks should never-ever
  affect the interactive programs running by user. Ideally they should
  be started in dedicated, heavily policed systemd slice.

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

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

[Kernel-packages] [Bug 1460941] Re: arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

The issue can be fixed by the following upstream commit:

commit 7623eee9046015b65a1f63f6bf07ab7805c36eb4
Author: Dave Anderson ander...@redhat.com
Date:   Tue May 19 10:20:04 2015 -0400

Fix for the ARM64 page size determination on Linux 4.1 and later
kernels.  Without the patch, the crash session fails during
initialization with the message crash: invalid/unsupported page
size: 98304 on kernels with 64K pages.  On kernels with 4K pages,
the message is crash: invalid/unsupported page size: 6144.  In
addition, the -p page-size command line override option
had no effect on ARM64; that has been fixed as well.
(ander...@redhat.com)

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

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  New

Bug description:
  
  After running crash from trusty, the failure log in [1] can be observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux 

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   

  crash: invalid/unknown page size: 6144

  [2] 
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
  [sudo] password for ubuntu: 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   

  crash: invalid/unsupported page size: 6144

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

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

[Kernel-packages] [Bug 1442411] Re: Intel 3160 wireless card no longer able to connect to wifi networks

[Jason Gerard DeRose]

Okay, after some more careful testing,
afcee962b09842d0f4191beb4a2d08251b4c7705 does indeed fix the problem.

I was having some unrelated issues when connecting to 2.4GHz N when too
far away from the access point (lots of WiFi interference here at
System76 HQ).

But the important thing is that when running the 3.19.0-20-generic
kernel from proposed, I can at least *sometimes* connect over N when
bluetooth is enabled (assuming I'm close enough to the access point).
Whereas with 3.19.0-18-generic and earlier, I could *never* connect, not
even when only a few feet from the access point.

As such, I'm removing removing the verification-needed-vivid  tag,
adding verification-done-vivid.


** Tags removed: verification-needed-vivid
** Tags added: verification-done-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/1442411

Title:
  Intel 3160 wireless card no longer able to connect to wifi networks

Status in System76:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]

  Laptop: Lenovo Y70 Touch
  Wireless Card: Intel Corporation Wireless 3160 (rev 93)

  When running Ubuntu Gnome 14.10 (on a live USB drive) I am able to
  connect to wifi networks without any issue. When running Ubuntu Gnome
  15.04 (either on live USB or installed and fully updated) I am able to
  see the list of available wifi networks, but not able to connect.
  Selecting one and entering the password makes the network manager
  applet indicate that it is Connecting... but then it gives up after
  about a minute or so and reverts back to Not Connected. I have
  tested this without network encryption as well, and the same result
  occurs.

  [Test Case]

  I have ran a wifi debugging script, here is the output:

  For Ubuntu 14.10 - http://pastebin.com/aLUhTyrM
  For Ubuntu 15.04 - http://pastebin.com/f0yRjQUC

  Again, the card seems to work perfectly on 14.10, but is unable to
  connect to any networks on 15.04.

  [Fix]

  commit afcee962b09842d0f4191beb4a2d08251b4c7705 upstream

  [Workaround]

  Boot with bluetooth turned off. If the computer boots with the
  bluetooth turned on, the wifi will not work, even if you first turn
  off the bluetooth. A restart is needed.

  ---
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mboratko   1609 F pulseaudio
   /dev/snd/controlC1:  mboratko   1609 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-10 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: LENOVO 80DU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic.efi.signed 
root=UUID=0fb46cba-f7ac-4bc5-aa7d-5f6aa74636c1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/11/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN37WW(V2.01)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN37WW(V2.01):bd02/11/2015:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.name: 80DU
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[Chris J Arges]

Dave,
Working on this now. I tried a bisect between v3.12..v3.13 where it seemed that 
3.12 worked better, but it wasn't conclusive. I tried looking at dev_put 
dev_hold via systemtap, but that seems to modify the timing sufficiently. 
Looking at comments from Jordan Curzon to see if I can start instrumenting just 
those sections of the kernel to track down where we're failing to decrement the 
reference. I'm tracing the NETDEV_UNREGISTER notifier calls now to see if that 
leads to something conclusive.

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Confirmed

Bug description:
  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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

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

[Kernel-packages] [Bug 1459934] Re: Support bluetooth device 0cf3:e006

[Brad Figg]

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

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

** Changed in: linux (Ubuntu)
   Status: In Progress = Invalid

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

Title:
  Support bluetooth device 0cf3:e006

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  0cf3:e006 is one of the ath3k devices. One commit needs to be cherry-picked 
for supporting it.
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ca79f232054abd079648fdb4400c71a1310f7bc8

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

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

[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[Dave Richardson]

Sounds good, thanks Chris.

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Confirmed

Bug description:
  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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

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

[Kernel-packages] [Bug 1461174] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack)

[Joseph Salisbury]

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

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

Title:
  Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2
  (utopic LTS HWE stack)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240940,
  several users report  rtl8723be still have problem on recent version
  of Ubuntu ,
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240940/comments/82
  suggested open a new bug,

  the utopic LTS enablement stack (HWE), including 3.16 kernel. uname -a looked 
like this:
  Linux buchanan-probook-455 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 
09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  Also, with utopic kernel and module, some user report adding ips=N and
  fwlps=N does not help.

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

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

[Kernel-packages] [Bug 1434978] Re: HP Zbook 14 G2: systems restart after shutdown

[Luc Stroobant]

I was able to update to BIOS Version: M71 Ver. 01.05 downloaded on the
above link, but the issue is not resolved.

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

Title:
  HP Zbook 14 G2: systems restart after shutdown

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I use the shutdown option in the menu or run sudo poweroff on my new 
Zbook 14 G2, the system shuts down and powers up again right after the restart. 
I have to push the power button again during startup to avoid it to restart. 
The system is more or less supported by Ubuntu* and the BIOS is up to date, so 
I thought this is worth a bug report...
  (I don't have a preinstalled system by HP, since I can't buy these here, this 
is an Ubunutu 15.04)

  (*) http://www.ubuntu.com/certification/hardware/201411-16141/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-9-generic 3.19.0-9.9
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  luc2523 F pulseaudio
   /dev/snd/controlC0:  luc2523 F pulseaudio
  Date: Sun Mar 22 12:14:35 2015
  InstallationDate: Installed on 2015-03-14 (7 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306)
  MachineType: Hewlett-Packard HP ZBook 14 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic 
root=/dev/mapper/ubuntu--vg-root 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.19.0-9-generic N/A
   linux-backports-modules-3.19.0-9-generic  N/A
   linux-firmware1.143
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.04
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.54
  dmi.chassis.asset.tag: 5CG50946XJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPZBook14G2:pvrA3009FC18303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 14 G2
  dmi.product.version: A3009FC18303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1461216] [NEW] Unstable wifi connection

[szuki]

Public bug reported:

After a while surfing on internet I get

[  197.963230] ERROR @wl_cfg80211_set_power_mgmt : error (-22)
[  202.537596] ERROR @wl_cfg80211_set_power_mgmt : error (-22)
[  207.624125] ERROR @wl_cfg80211_disconnect : error (-22)
[  207.660718] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  209.034352] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  233.792671] ERROR @wl_cfg80211_set_power_mgmt : error (-22)
[  233.796739] ERROR @wl_cfg80211_scan : WLC_SET_PASSIVE_SCAN error (-22)
[  233.806077] ERROR @wl_cfg80211_scan : WLC_SET_PASSIVE_SCAN error (-22)
[  258.799926] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  258.819853] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  270.435576] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  273.797088] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  276.336516] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  301.802579] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  301.819160] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  326.900039] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  329.910940] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  352.974379] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  386.051841] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  429.123903] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  482.108538] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  545.119723] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  608.149249] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  671.194580] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  734.177865] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  797.184937] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  860.187819] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  923.204723] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[  986.261045] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[ 1049.312716] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[ 1112.347750] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[ 1175.377460] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
[ 1238.414115] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)


When I unload wl module and load it. The laptop freezes and there is no way to 
bring it back to life.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Tue Jun  2 20:47:45 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-30 (3 days ago)
InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  Unstable wifi connection

Status in bcmwl package in Ubuntu:
  New

Bug description:
  After a while surfing on internet I get

  [  197.963230] ERROR @wl_cfg80211_set_power_mgmt : error (-22)
  [  202.537596] ERROR @wl_cfg80211_set_power_mgmt : error (-22)
  [  207.624125] ERROR @wl_cfg80211_disconnect : error (-22)
  [  207.660718] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  209.034352] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  233.792671] ERROR @wl_cfg80211_set_power_mgmt : error (-22)
  [  233.796739] ERROR @wl_cfg80211_scan : WLC_SET_PASSIVE_SCAN error (-22)
  [  233.806077] ERROR @wl_cfg80211_scan : WLC_SET_PASSIVE_SCAN error (-22)
  [  258.799926] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  258.819853] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  270.435576] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  273.797088] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  276.336516] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  301.802579] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  301.819160] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  326.900039] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  329.910940] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  352.974379] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  386.051841] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  429.123903] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  482.108538] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  545.119723] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  608.149249] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  671.194580] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  734.177865] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  797.184937] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  [  860.187819] ERROR 

[Kernel-packages] [Bug 1408833] Re: broken postinst test for uvtool-libvirt

[Adam Stokes]

Enki,

Looks like you just need the enablement kernel: See here for more
information:

https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#LTS_Hardware_Enablement_Stack

You'll want to make sure you're on a 3.16-0-38.52 or higher

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

Title:
  broken postinst test for uvtool-libvirt

Status in AppArmor Linux application security framework:
  Confirmed
Status in Ubuntu OpenStack installer:
  Confirmed
Status in ubuntu virtualization tools:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Utopic:
  Fix Released

Bug description:
  Installing uvtool-libvirt *inside an lxc container* on utopic fails
  due to a test in the postinst script.

  It uses socat on the libvirt socket, which fails, despite libvirt
  being installed correctly.

  ubuntu@uoi-bootstrap:~$ sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libfreetype6 os-prober
  Use 'apt-get autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up uvtool-libvirt (0~bzr92-0ubuntu2) ...
  2015/01/08 13:01:34 socat[10184] E read(3, 0x13b2a30, 8192): Permission denied
  libvirtd does not appear to be listening on /var/run/libvirt/libvirt-sock.
  On Ubuntu, libvirtd is managed with the libvirt-bin upstart job.
  Repair libvirtd, then reconfigure uvtool-libvirt with:
  sudo apt-get -f install
  dpkg: error processing package uvtool-libvirt (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   uvtool-libvirt
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  ubuntu@uoi-bootstrap:~$ ps -ef | grep libvirt
  libvirt+  9556 1  0 09:52 ?00:00:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  root  9557  9556  0 09:52 ?00:00:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  root  9854 1  0 10:24 ?00:00:00 /usr/sbin/libvirtd -d
  ubuntu   10155 10120  0 12:56 pts/000:00:00 grep libvirt

  ubuntu@uoi-bootstrap:~$ groups
  ubuntu adm dialout cdrom floppy sudo audio dip video plugdev netdev libvirtd

  
  ubuntu@uoi-bootstrap:~$ virsh list
   IdName   State
  

  for a little more context, there are notes here:
  https://gist.github.com/mikemccracken/53c665e6094db21efc03

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

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

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Dave Chiluk]

I've integrated the 9a9324d396967 NO NCQ Trim fix into this ppa.

https://launchpad.net/~chiluk/+archive/ubuntu/samsungncqtrim

Please test it and report back here either way.  I'll remove the ppa
when the fix hits the kernels in -updates.

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1458839] Re: Poor Wi-Fi connectivity when connecting USB dock

[Jonas G. Drange]

I was wrong. Wi-Fi slowly dies after plugging in the USB dock.

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

Title:
  Poor Wi-Fi connectivity when connecting USB dock

Status in linux package in Ubuntu:
  New

Bug description:
  Reproduce:
  Insert USB dock (Kensington with usb sound card, ethernet card) cable into 
any USB port

  What happens:
  Wi-Fi connectivity worsens and eventually disconnects.
  Pinging an online target gives me 
  [1432638474.615293] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=11 ttl=54 time=1172 ms
  [1432638474.636669] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=12 ttl=54 time=185 ms
  [1432638475.496000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=13 ttl=54 time=44.3 ms
  [1432638477.638814] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=14 ttl=54 time=1185 ms
  [1432638477.644744] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=15 ttl=54 time=192 ms
  [1432638478.498248] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=16 ttl=54 time=44.4 ms
  [1432638479.662460] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=17 ttl=54 time=207 ms
  [1432638480.547434] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=18 ttl=54 time=90.9 ms
  [1432638482.597835] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=19 ttl=54 time=1140 ms
  [1432638482.601590] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=20 ttl=54 time=144 ms
  [1432638484.648946] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=21 ttl=54 time=1191 ms
  [1432638484.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=22 ttl=54 time=193 ms
  [1432638485.502967] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=23 ttl=54 time=45.1 ms
  [1432638487.301295] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=24 ttl=54 time=842 ms
  [1432638488.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=25 ttl=54 time=1191 ms
  [1432638488.662959] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=26 ttl=54 time=196 ms
  [1432638489.514683] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=27 ttl=54 time=46.7 ms
  [1432638491.653511] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=28 ttl=54 time=1183 ms
  [1432638491.655011] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=29 ttl=54 time=176 ms
  [1432638493.659119] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=30 ttl=54 time=1179 ms
  [1432638493.664250] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=31 ttl=54 time=177 ms
  [1432638494.534200] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=32 ttl=54 time=45.9 ms
  …

  Disconnecting the USB cable restores the connectivity:
  [1432638514.584374] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=52 ttl=54 time=48.5 ms
  [1432638515.577822] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=53 ttl=54 time=40.1 ms
  [1432638516.579000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=54 ttl=54 time=39.9 ms
  [1432638517.580760] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=55 ttl=54 time=40.5 ms
  [1432638518.583465] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=56 ttl=54 time=41.4 ms
  [1432638519.583923] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=57 ttl=54 time=40.1 ms
  …

  What should have happened:
  Connectivity should not be affected by a connected USB dock

  Steps taken to debug:
  * I've told NetworkManager not to manage the USB network card so that it 
appears unmanaged. This makes no difference.
  * I've tried older kernels, e.g. 3.14 with no luck
  * It does not matter what is connected to the dock

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  jonas  1514 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 26 13:08:44 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7b9cb658-95dd-4e13-a587-d6d0d59ae7e4
  InstallationDate: Installed on 2013-08-27 (637 days ago)
  InstallationMedia: 

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Poor Wi-Fi connectivity when connecting USB dock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  Insert USB dock (Kensington with usb sound card, ethernet card) cable into 
any USB port

  What happens:
  Wi-Fi connectivity worsens and eventually disconnects.
  Pinging an online target gives me 
  [1432638474.615293] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=11 ttl=54 time=1172 ms
  [1432638474.636669] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=12 ttl=54 time=185 ms
  [1432638475.496000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=13 ttl=54 time=44.3 ms
  [1432638477.638814] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=14 ttl=54 time=1185 ms
  [1432638477.644744] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=15 ttl=54 time=192 ms
  [1432638478.498248] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=16 ttl=54 time=44.4 ms
  [1432638479.662460] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=17 ttl=54 time=207 ms
  [1432638480.547434] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=18 ttl=54 time=90.9 ms
  [1432638482.597835] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=19 ttl=54 time=1140 ms
  [1432638482.601590] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=20 ttl=54 time=144 ms
  [1432638484.648946] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=21 ttl=54 time=1191 ms
  [1432638484.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=22 ttl=54 time=193 ms
  [1432638485.502967] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=23 ttl=54 time=45.1 ms
  [1432638487.301295] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=24 ttl=54 time=842 ms
  [1432638488.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=25 ttl=54 time=1191 ms
  [1432638488.662959] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=26 ttl=54 time=196 ms
  [1432638489.514683] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=27 ttl=54 time=46.7 ms
  [1432638491.653511] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=28 ttl=54 time=1183 ms
  [1432638491.655011] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=29 ttl=54 time=176 ms
  [1432638493.659119] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=30 ttl=54 time=1179 ms
  [1432638493.664250] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=31 ttl=54 time=177 ms
  [1432638494.534200] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=32 ttl=54 time=45.9 ms
  …

  Disconnecting the USB cable restores the connectivity:
  [1432638514.584374] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=52 ttl=54 time=48.5 ms
  [1432638515.577822] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=53 ttl=54 time=40.1 ms
  [1432638516.579000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=54 ttl=54 time=39.9 ms
  [1432638517.580760] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=55 ttl=54 time=40.5 ms
  [1432638518.583465] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=56 ttl=54 time=41.4 ms
  [1432638519.583923] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=57 ttl=54 time=40.1 ms
  …

  What should have happened:
  Connectivity should not be affected by a connected USB dock

  Steps taken to debug:
  * I've told NetworkManager not to manage the USB network card so that it 
appears unmanaged. This makes no difference.
  * I've tried older kernels, e.g. 3.14 with no luck
  * It does not matter what is connected to the dock

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  jonas  1514 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 26 13:08:44 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7b9cb658-95dd-4e13-a587-d6d0d59ae7e4
  InstallationDate: Installed on 2013-08-27 (637 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - 

[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/debian-installer/trusty-proposed

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

Title:
  devel: DTBs have moved into vendor specific directories on arm64

Status in debian-installer package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  In Progress
Status in flash-kernel source package in Trusty:
  In Progress
Status in linux source package in Trusty:
  Invalid

Bug description:
  The installed DTBs have moved into vendor specific directories.  We
  need to 1) make sure we are hoovering them up right, and 2) that the
  consumers thereof (d-i etc) are consuming them in the new locations.

  NOTE: this actually is only _installed_ into those new directories on
  arm64.

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

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

[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)

[Dave Chiluk]

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

** This bug has been marked a duplicate of bug 1338706
   Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set 
xfermode (err_mask=0x40) on upstream kernels = 3.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/1449005

Title:
  trim does not work with Samsung 840 EVO after firmware update
  (EXT0DB6Q)

Status in fstrim package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in fstrim source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in fstrim source package in Utopic:
  Invalid
Status in linux source package in Utopic:
  Confirmed
Status in fstrim source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Hi,
  after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the 
fstream command doesn't work anymore. Besides, there are a lot of file system 
errors and bad sectors reports. The problem is certainly caused by Samsung's 
firmware but I reported it as a bug because in Windows TRIM works normally 
after the upgrade. I have attached an image uploaded by a user who is 
experiencing the same problem. If you execute the command sudo fstrim / the  
console gets stuck. If you add that command in rc.local the boot is 
compromised. I really hope this problem could be solved.
  Thanks

  ===
  break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a
  break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81

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

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

[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64

[Adam Conrad]

** Description changed:

- The installed DTBs have moved into vendor specific directories.  We need
- to 1) make sure we are hoovering them up right, and 2) that the
- consumers thereof (d-i etc) are consuming them in the new locations.
+ [ SRU Justification ]
+ For trusty, the lts-vivid debian-installer builds install the lts-vivid 
kernel, which has the DTBs in the new location.  As such, both d-i and f-k need 
fixing to look for the correct locations.
+ 
+ [ Test Case ]
+ For d-i, the test case is to build d-i and ensure it's picking up the right 
DTBs for both old and new location builds.
+ 
+ For f-k, the test case is to do an installation of both lts-utopic and
+ lts-vivid on arm64 and ensure that flash-kernel is operating on the DTBs
+ without error in both cases.
+ 
+ [ Regression Potential ]
+ The d-i change has already been tested in a PPA and is known-good, while the 
f-k change is a straight cherry-pick from vivid, where it was known to work, so 
both should be minimally scary.
+ 
+ [ Original Report ]
+ The installed DTBs have moved into vendor specific directories.  We need to 
1) make sure we are hoovering them up right, and 2) that the consumers thereof 
(d-i etc) are consuming them in the new locations.
  
  NOTE: this actually is only _installed_ into those new directories on
  arm64.

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

Title:
  devel: DTBs have moved into vendor specific directories on arm64

Status in debian-installer package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  In Progress
Status in flash-kernel source package in Trusty:
  In Progress
Status in linux source package in Trusty:
  Invalid

Bug description:
  [ SRU Justification ]
  For trusty, the lts-vivid debian-installer builds install the lts-vivid 
kernel, which has the DTBs in the new location.  As such, both d-i and f-k need 
fixing to look for the correct locations.

  [ Test Case ]
  For d-i, the test case is to build d-i and ensure it's picking up the right 
DTBs for both old and new location builds.

  For f-k, the test case is to do an installation of both lts-utopic and
  lts-vivid on arm64 and ensure that flash-kernel is operating on the
  DTBs without error in both cases.

  [ Regression Potential ]
  The d-i change has already been tested in a PPA and is known-good, while the 
f-k change is a straight cherry-pick from vivid, where it was known to work, so 
both should be minimally scary.

  [ Original Report ]
  The installed DTBs have moved into vendor specific directories.  We need to 
1) make sure we are hoovering them up right, and 2) that the consumers thereof 
(d-i etc) are consuming them in the new locations.

  NOTE: this actually is only _installed_ into those new directories on
  arm64.

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

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

[Kernel-packages] [Bug 1292400] Re: task systemd-udevd:1906 blocked for more than 120 seconds.

[Kartik Subbarao]

Does anyone know the current status of this -- is a revised patch still
in the works?

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

Title:
  task systemd-udevd:1906 blocked for more than 120 seconds.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System log shows repeated incidents of task systemd-udevd:1906
  blocked for more than 120 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37 [modified: 
boot/vmlinuz-3.13.0-17-generic]
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Fri Mar 14 08:54:36 2014
  HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b
  InstallationDate: Installed on 2014-03-12 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed 
root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b
  InstallationDate: Installed on 2014-03-12 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed 
root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware

[Brad Figg]

** Changed in: linux (Ubuntu Utopic)
   Status: In Progress = Fix Committed

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

Title:
  backport request: include support for OpenPower hardware

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

Bug description:
  [Impact]
  This is a HWE SRU for OpenPower support in 3.16.

  [Fix]
  upstream commits:
  backported from commit 6a11e5c67a397e9a64cfde6961c83a7a64d7980c)
  backported from commit 608b286d1ddf38a7ceb624d2b689af095816d91c)
  cherry picked from commit 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2)
  cherry picked from commit 4c3b21686111e0ac6018469dacbc5549f9915cf8)
  cherry picked from commit a4bcbe6a41adcaa5e7f1830a7c1da8691d9d2b1d)
  backported from commit 08135139430fabdeaa990da8a9e0d436aad0672b)
  cherry picked from commit c1c3a526bb4ddbec7639a9fb3b84fede25b201d9)
  cherry picked from commit b921e90260cec1e04988bb3763491de885b67b51)
  backported from commit e8a51e1b51ee5730ad3913f3962e3099a5e19359)
  cherry picked from commit 5590f3196b293574a12be58d06d5e1120d8856ec)
  backported from commit 529d235a0e190ded1d21ccc80a73e625ebcad09b)

  [Test Case]
  Ensure kernel boots on specific OpenPower hardware.

  --

  We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11),
  which add OpenPower support to the Ubuntu kernel.

  The changes are available in the ubuntu/vivid branch of:

   https://github.com/open-power/linux.git

  (or I can attach them separately).

  Changelogs are as follows:

  commit 2f0190bd43764559b250a5bd11aca050f909aa21
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Fri Nov 14 16:13:50 2014 +1100

  powerpc/powernv: Support OPAL requested heartbeat

  If OPAL requests it, call it back via opal_poll_events() at a
  regular interval. Some versions of OPAL on some machines require
  this to operate some internal timeouts properly.

  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org

  Backport notes:
   cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2
   minor conflicts resolved
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit e1c89541e7163494ad091f3c2622649d91ac7597
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Mon Feb 16 14:59:08 2015 +1100

  device: Add dev_of_node() accessor

  Suggested by Arnd Bergmann, this gives a practical accessor for
  the of_node field of struct device while instructing the compiler
  that it will be NULL if CONFIG_OF is not set.

  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
  Acked-by: Rob Herring r...@kernel.org

  Backport notes:
   Submission to LKML at: https://patchwork.kernel.org/patch/5831161/
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit 2c242b30756f77528516a4e9e986818ac4e90490
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Wed Feb 18 11:25:18 2015 +1100

  drivers/core/of: Add symlink to device-tree from devices with an
  OF node

  So I've been annoyed lately with having a bunch of devices such as i2c
  eeproms (for use by VPDs, server world !) and other bits and pieces that
  I want to be able to identify from userspace, and possibly provide
  additional data about from FW.

  Basically, it boils down to correlating the sysfs device with the OF
  tree device node, so that user space can use device-tree info such as
  additional location or label (or whatever else we can come up with)
  propreties to identify a given device, or get some attributes of use
  about it, etc...

  Now, so far, we've done that in some subsystem in a fairly ad-hoc basis
  using devspec properties. For example, PCI creates them if it can
  correlate the probed device with a DT node. Some powerpc specific busses
  do that too.

  However, i2c doesn't and it would be nice to have something more generic
  since technically any device can have a corresponding device tree node.

  This patch adds an of_node symlink to devices that have a non-NULL
  dev-of_node pointer, the patch is pretty trivial and seems to work just
  fine for me.

  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
  Acked-by: Rob Herring r...@kernel.org

  Backport notes:
   Submission to LKML at: https://patchwork.kernel.org/patch/5842241/
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c
  Author: Michael Ellerman m...@ellerman.id.au
  Date:   Sat Mar 28 21:35:16 2015 +1100

  powerpc: Add a proper syscall for switching endianness

  We currently have a special syscall for switching endianness. This is
  syscall number 0x1ebe, which is handled 

[Kernel-packages] [Bug 1442411] Re: Intel 3160 wireless card no longer able to connect to wifi networks

[Michael Boratko]

The proposed kernel worked for me with bluetooth on.

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

Title:
  Intel 3160 wireless card no longer able to connect to wifi networks

Status in System76:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]

  Laptop: Lenovo Y70 Touch
  Wireless Card: Intel Corporation Wireless 3160 (rev 93)

  When running Ubuntu Gnome 14.10 (on a live USB drive) I am able to
  connect to wifi networks without any issue. When running Ubuntu Gnome
  15.04 (either on live USB or installed and fully updated) I am able to
  see the list of available wifi networks, but not able to connect.
  Selecting one and entering the password makes the network manager
  applet indicate that it is Connecting... but then it gives up after
  about a minute or so and reverts back to Not Connected. I have
  tested this without network encryption as well, and the same result
  occurs.

  [Test Case]

  I have ran a wifi debugging script, here is the output:

  For Ubuntu 14.10 - http://pastebin.com/aLUhTyrM
  For Ubuntu 15.04 - http://pastebin.com/f0yRjQUC

  Again, the card seems to work perfectly on 14.10, but is unable to
  connect to any networks on 15.04.

  [Fix]

  commit afcee962b09842d0f4191beb4a2d08251b4c7705 upstream

  [Workaround]

  Boot with bluetooth turned off. If the computer boots with the
  bluetooth turned on, the wifi will not work, even if you first turn
  off the bluetooth. A restart is needed.

  ---
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mboratko   1609 F pulseaudio
   /dev/snd/controlC1:  mboratko   1609 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-10 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: LENOVO 80DU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic.efi.signed 
root=UUID=0fb46cba-f7ac-4bc5-aa7d-5f6aa74636c1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/11/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN37WW(V2.01)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN37WW(V2.01):bd02/11/2015:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.name: 80DU
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1458839] Re: Poor Wi-Fi connectivity when connecting USB dock

[Christopher M. Penalver]

Jonas G. Drange, 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 XY 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 upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags removed: bios-outdated-a10
** Tags added: latest-bios-a10

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

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

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

Title:
  Poor Wi-Fi connectivity when connecting USB dock

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Reproduce:
  Insert USB dock (Kensington with usb sound card, ethernet card) cable into 
any USB port

  What happens:
  Wi-Fi connectivity worsens and eventually disconnects.
  Pinging an online target gives me 
  [1432638474.615293] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=11 ttl=54 time=1172 ms
  [1432638474.636669] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=12 ttl=54 time=185 ms
  [1432638475.496000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=13 ttl=54 time=44.3 ms
  [1432638477.638814] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=14 ttl=54 time=1185 ms
  [1432638477.644744] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=15 ttl=54 time=192 ms
  [1432638478.498248] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=16 ttl=54 time=44.4 ms
  [1432638479.662460] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=17 ttl=54 time=207 ms
  [1432638480.547434] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=18 ttl=54 time=90.9 ms
  [1432638482.597835] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=19 ttl=54 time=1140 ms
  [1432638482.601590] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=20 ttl=54 time=144 ms
  [1432638484.648946] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=21 ttl=54 time=1191 ms
  [1432638484.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=22 ttl=54 time=193 ms
  [1432638485.502967] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=23 ttl=54 time=45.1 ms
  [1432638487.301295] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=24 ttl=54 time=842 ms
  [1432638488.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=25 ttl=54 time=1191 ms
  [1432638488.662959] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=26 ttl=54 time=196 ms
  [1432638489.514683] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=27 ttl=54 time=46.7 ms
  [1432638491.653511] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=28 ttl=54 time=1183 ms
  [1432638491.655011] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=29 ttl=54 time=176 ms
  [1432638493.659119] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=30 ttl=54 time=1179 ms
  [1432638493.664250] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=31 ttl=54 time=177 ms
  [1432638494.534200] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=32 ttl=54 time=45.9 ms
  …

  Disconnecting the USB cable restores the connectivity:
  [1432638514.584374] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=52 ttl=54 time=48.5 ms
  [1432638515.577822] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=53 ttl=54 time=40.1 ms
  [1432638516.579000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): 
icmp_seq=54 ttl=54 time=39.9 ms
  

[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64

[Steve Langasek]

Hello Andy, or anyone else affected,

Accepted debian-installer into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu318.18 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  devel: DTBs have moved into vendor specific directories on arm64

Status in debian-installer package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Committed
Status in flash-kernel source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Invalid

Bug description:
  [ SRU Justification ]
  For trusty, the lts-vivid debian-installer builds install the lts-vivid 
kernel, which has the DTBs in the new location.  As such, both d-i and f-k need 
fixing to look for the correct locations.

  [ Test Case ]
  For d-i, the test case is to build d-i and ensure it's picking up the right 
DTBs for both old and new location builds.

  For f-k, the test case is to do an installation of both lts-utopic and
  lts-vivid on arm64 and ensure that flash-kernel is operating on the
  DTBs without error in both cases.

  [ Regression Potential ]
  The d-i change has already been tested in a PPA and is known-good, while the 
f-k change is a straight cherry-pick from vivid, where it was known to work, so 
both should be minimally scary.

  [ Original Report ]
  The installed DTBs have moved into vendor specific directories.  We need to 
1) make sure we are hoovering them up right, and 2) that the consumers thereof 
(d-i etc) are consuming them in the new locations.

  NOTE: this actually is only _installed_ into those new directories on
  arm64.

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

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

[Kernel-packages] [Bug 1461320] [NEW] first resume fails after suspend

[rob loranger]

Public bug reported:

Ever since I upgraded from 14.04 through to 15.04 I have had an issue
resuming from suspend. The login pops up for a second and then the
computer suspends again. Waking a second time resume is successful.

With kernel 3.13.0 wifi was typically 'broken' upon resume with the only
remedy being to select the network from the connect to hidden wireless
network dialogue. no networks were visible in the network tray menu.

With kernel 4.1.0 rc2 the wifi appears to resume normally but the double
wake is still required.

I will attach more info after i restart with the 3.13.0 kernel

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

** Attachment added: wake log
   https://bugs.launchpad.net/bugs/1461320/+attachment/4408853/+files/wakeup

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1461320] Re: first resume fails after suspend

[rob loranger]

apport information

** Tags added: apport-collected vivid

** Description changed:

  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.
  
  With kernel 3.13.0 wifi was typically 'broken' upon resume with the only
  remedy being to select the network from the connect to hidden wireless
  network dialogue. no networks were visible in the network tray menu.
  
  With kernel 4.1.0 rc2 the wifi appears to resume normally but the double
  wake is still required.
  
  I will attach more info after i restart with the 3.13.0 kernel
+ --- 
+ ApportVersion: 2.17.2-0ubuntu1.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  robbie 2556 F pulseaudio
+  /dev/snd/controlC0:  robbie 2556 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 15.04
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2014-09-03 (272 days ago)
+ InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
+ MachineType: Hewlett-Packard p6706f
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-48-generic N/A
+  linux-backports-modules-3.13.0-48-generic  N/A
+  linux-firmware 1.143.1
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  vivid
+ Uname: Linux 3.13.0-48-generic x86_64
+ UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
+ UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
+ _MarkForUpload: True
+ dmi.bios.date: 12/28/2011
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 6.11
+ dmi.board.name: 2AB1
+ dmi.board.vendor: FOXCONN
+ dmi.board.version: 1.00
+ dmi.chassis.asset.tag: MXX1020D7B
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
+ dmi.product.name: p6706f
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1461320/+attachment/4408854/+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/1461320

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

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

[rob loranger]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1461320/+attachment/4408855/+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/1461320

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1461320] JournalErrors.txt

[rob loranger]

apport information

** Attachment added: JournalErrors.txt
   
https://bugs.launchpad.net/bugs/1461320/+attachment/4408858/+files/JournalErrors.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/1461320

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1461320/+attachment/4408868/+files/WifiSyslog.txt

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

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1461320/+attachment/4408862/+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/1461320

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1461320/+attachment/4408857/+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/1461320

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[rob loranger]

apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/1461320/+attachment/4408865/+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/1461320

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Brad Figg]

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

apport-collect 1461320

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel

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

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

[Kernel-packages] [Bug 1461320] Re: first resume fails after suspend

[rob loranger]

** Tags added: resume

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

Title:
  first resume fails after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from 14.04 through to 15.04 I have had an issue
  resuming from suspend. The login pops up for a second and then the
  computer suspends again. Waking a second time resume is successful.

  With kernel 3.13.0 wifi was typically 'broken' upon resume with the
  only remedy being to select the network from the connect to hidden
  wireless network dialogue. no networks were visible in the network
  tray menu.

  With kernel 4.1.0 rc2 the wifi appears to resume normally but the
  double wake is still required.

  I will attach more info after i restart with the 3.13.0 kernel
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robbie 2556 F pulseaudio
   /dev/snd/controlC0:  robbie 2556 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-03 (272 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard p6706f
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.13.0-48-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1020D7B
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6706f
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1460265] Re: Suspend to RAM fails: (0 tasks refusing to freeze, wq_busy=1)

[Christopher M. Penalver]

al, please see
https://wiki.ubuntu.com/Kernel/MainlineBuilds#Does_the_kernel_team_support_the_mainline_kernel_builds.3F
.

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

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

Thank you for your understanding.

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

** Tags added: needs-reverse-bisect

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

Title:
  Suspend to RAM fails: (0 tasks refusing to freeze, wq_busy=1)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  version:   Ubuntu 3.19.0-16.16-generic 3.19.3
  Suspend worked fine in Kubuntu 14.04 LTS (kernel version 3.13.0-30)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilya   1718 F pulseaudio
   /dev/snd/controlC1:  ilya   1718 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat May 30 11:27:09 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-21 (8 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: System manufacturer P5Q DELUXE
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=5b07cbf3-c34c-4ff2-9c9d-2a990850fcc4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  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/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/10/2009:svnSystemmanufacturer:pnP5QDELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q DELUXE
  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/1460265/+subscriptions

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

[Kernel-packages] [Bug 1447331] Re: [Lenovo ThinkPad SL510] Will not resume from suspend

[Christopher M. Penalver]

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

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

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

Title:
  [Lenovo ThinkPad SL510] Will not resume from suspend

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 3.19.0-15.15-generic 3.19.3
  will not resume from suspend using both gui and systemctl suspend command
  this includes ubuntu-gnome 15.04, ubuntu 15.04, xubuntu 15.04. ubuntu-mate 
15.04

  1. ubuntu-gnome@ubuntu-gnome:~$ lsb_release -rd
   Description: Ubuntu 15.04
   Release: 15.04
  2. Linux ubuntu-gnome 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  3. I expected the laptop to resume from after using the systemctl suspend 
command from terminal
    expected the laptop to resume from suspend after closing lid then 
opening lid of laptop
    expected the laptop to resume from suspend after using the gui to go 
into suspend
  4. the laptop did not resume from suspend using three methods above to go 
into suspend
  the laptop light blinks rapidly, then laptop must be shutoff manually 
using the power button

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-gnome   1715 F pulseaudio
  CasperVersion: 1.360
  CurrentDesktop: GNOME
  Date: Wed Apr 22 19:14:27 2015
  LiveMediaBuild: Ubuntu-GNOME 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: LENOVO 2847CZU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  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
  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/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET94WW (1.52 )
  dmi.board.name: 2847CZU
  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:bvr6JET94WW(1.52):bd06/19/2012:svnLENOVO:pn2847CZU:pvrThinkPadSL510:rvnLENOVO:rn2847CZU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2847CZU
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error

[Alex Ng]

Hi Joseph,

Kernel with commits up to 7ce14f6ff26460819345fe8495cf2dd6538b7cdc are
also seeing this issue.

I'm can run my own bisect as well so we can save some time going back
and forth. Are you basing your bisect off of Linux-stable repository?

Thanks,
Alex

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

Title:
  [Hyper-V] Fiber Channel critical target error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System details:
  Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 
4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 
(Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3)

  Ubuntu 3.19.0-11
  Ubuntu Vivid 15.04 64bit custom kernel
  Platform: WS2012R2

  Using a fiber channel disk partition ( dev/sde1 in this example) outputs the 
following error:
  ​
  [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0
  [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0
  [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0

  Creating a partition works, reading too, but first time writing it
  hangs for around 20 seconds and after a couple more writes the
  partition goes into read-only mode:

  #echo test1  test1.txt
  *hangs for 30 seconds*
  blk_update_request: critical target error, dev sde, sector 0
  # echo test2  test2.txt
  blk_update_request: critical target error, dev sde, sector 289671192
  Aborting journal on device sde1-8.
  EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted 
journal
  EXT4-fs (sde1): Remounting filesystem read-only
  # echo test string  sample.txt
  -bash: sample.txt: Read-only file system

  
  Dmesg log:
  [  461.284362] blk_update_request: critical target error, dev sde, sector 0
  [  484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  548.988377] blk_update_request: critical target error, dev sde, sector 0
  [  609.216340] blk_update_request: critical target error, dev sde, sector 
289671192
  [  609.221812] Aborting journal on device sde1-8.
  [  612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: 
Detected aborted journal
  [  612.249529] EXT4-fs (sde1): Remounting filesystem read-only

  Additional info:

  cat /proc/version_signature
  Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3

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

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

[Kernel-packages] [Bug 1460736] Re: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11-ckt21-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/1460736

Title:
  package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The problem that I've encountered is that an incomplete Kernel update
  crashed my system.  I'm currently running in recovery mode. While my
  user password works for updates, it does not work in terminal at
  present.  My installed system is Ubantu 14.04.1 LTS with all updates
  added as of 06/01/2015.  I've installed and am currently using the KDE
  desktop.

  cat /proc/version_signature  version.log   Yielded:

  Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18

  
  sudo lspci -vnvn  lspci-vnvn.log  Yielded:

  
  00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Toshiba America Info Systems Device [1179:ff1e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR- INTx-
Latency: 0
Capabilities: access denied

  00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:fa20]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 42
Region 0: Memory at c800 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at c000 (64-bit, prefetchable) [size=128M]
Region 4: I/O ports at 3000 [size=64]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: i915

  00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Toshiba America Info Systems Device [1179:ff1e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 40
Region 0: Memory at c860 (64-bit, non-prefetchable) [size=64K]
Capabilities: access denied
Kernel driver in use: xhci_hcd

  00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 
Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:ff1e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 43
Region 0: Memory at c8614000 (64-bit, non-prefetchable) [size=16]
Capabilities: access denied
Kernel driver in use: mei_me

  00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI])
Subsystem: Toshiba America Info Systems Device [1179:ff1e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at c8619000 (32-bit, non-prefetchable) [size=1K]
Capabilities: access denied
Kernel driver in use: ehci-pci

  00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Toshiba America Info Systems Device 

[Kernel-packages] [Bug 1460985] Re: periodic find task slow ubuntu to death

[god]

No, I've got this issue for as long as I can remember.
Note: I've removed cron and installed systemd-cron instead but it didn't change 
anything.

Next time I see this issue I'll try to check which processes started it.
If I'll figure out a way to trigger it reliably I'll check upstream
kernel too. Thanks for looking into this.

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

Title:
  periodic find task slow ubuntu to death

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Periodically something starts 'find' program in the background with
  readdir smth in options and it slows down ubuntu to the point the
  music and video got hiccups, mouse lags etc. I suspect it's smth
  related to package or locatedb updates but can't pinpoint the culprit
  yet.

  Anyway, the bugis in slowdown - background tasks should never-ever
  affect the interactive programs running by user. Ideally they should
  be started in dedicated, heavily policed systemd slice.

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

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

[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error

[Joseph Salisbury]

I'll continue the bisect until I hear back.

I built the next test kernel, up to the following commit:
c5db6a3bdeb72f4238e1faefa4ce4eab7a64baea

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1439780

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  [Hyper-V] Fiber Channel critical target error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System details:
  Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 
4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 
(Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3)

  Ubuntu 3.19.0-11
  Ubuntu Vivid 15.04 64bit custom kernel
  Platform: WS2012R2

  Using a fiber channel disk partition ( dev/sde1 in this example) outputs the 
following error:
  ​
  [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0
  [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0
  [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0

  Creating a partition works, reading too, but first time writing it
  hangs for around 20 seconds and after a couple more writes the
  partition goes into read-only mode:

  #echo test1  test1.txt
  *hangs for 30 seconds*
  blk_update_request: critical target error, dev sde, sector 0
  # echo test2  test2.txt
  blk_update_request: critical target error, dev sde, sector 289671192
  Aborting journal on device sde1-8.
  EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted 
journal
  EXT4-fs (sde1): Remounting filesystem read-only
  # echo test string  sample.txt
  -bash: sample.txt: Read-only file system

  
  Dmesg log:
  [  461.284362] blk_update_request: critical target error, dev sde, sector 0
  [  484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  548.988377] blk_update_request: critical target error, dev sde, sector 0
  [  609.216340] blk_update_request: critical target error, dev sde, sector 
289671192
  [  609.221812] Aborting journal on device sde1-8.
  [  612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: 
Detected aborted journal
  [  612.249529] EXT4-fs (sde1): Remounting filesystem read-only

  Additional info:

  cat /proc/version_signature
  Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3

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

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

[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64

[Steve Langasek]

Hello Andy, or anyone else affected,

Accepted flash-kernel into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.0~rc.4ubuntu49.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: flash-kernel (Ubuntu Trusty)
   Status: In Progress = Fix Committed

** Tags added: verification-needed

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

Title:
  devel: DTBs have moved into vendor specific directories on arm64

Status in debian-installer package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  In Progress
Status in flash-kernel source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Invalid

Bug description:
  [ SRU Justification ]
  For trusty, the lts-vivid debian-installer builds install the lts-vivid 
kernel, which has the DTBs in the new location.  As such, both d-i and f-k need 
fixing to look for the correct locations.

  [ Test Case ]
  For d-i, the test case is to build d-i and ensure it's picking up the right 
DTBs for both old and new location builds.

  For f-k, the test case is to do an installation of both lts-utopic and
  lts-vivid on arm64 and ensure that flash-kernel is operating on the
  DTBs without error in both cases.

  [ Regression Potential ]
  The d-i change has already been tested in a PPA and is known-good, while the 
f-k change is a straight cherry-pick from vivid, where it was known to work, so 
both should be minimally scary.

  [ Original Report ]
  The installed DTBs have moved into vendor specific directories.  We need to 
1) make sure we are hoovering them up right, and 2) that the consumers thereof 
(d-i etc) are consuming them in the new locations.

  NOTE: this actually is only _installed_ into those new directories on
  arm64.

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

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

[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host

[Joseph Salisbury]

I built a Vivid test kernel with the requested commit.  There were some
pre-req commits that were needed as well.  The test kernel has the
following commits applied:

4c0d9e0 hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
2e16490 Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl()
b30dd3a Drivers: hv: vmbus: Suport an API to send pagebuffers with additional 
control
f93ca43 Drivers: hv: vmbus: Suport an API to send packet with additional control
068352e  hv_netvsc: Fix a bug in netvsc_start_xmit()
be93771  hv_netvsc: Implement partial copy into send buffer
888ec2b  hv_netvsc: Fix the packet free when it is in skb headroom
a0d749b  hv_netvsc: Eliminate memory allocation in the packet send path
ef9700b  hv_netvsc: Cleanup the test for freeing skb when we use sendbuf 
mechanism
929b8e8 hv_netvsc: Implement batching in send buffer

The Vivid test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1454892/


Can you test this kernel and see if it resolves the bug?  If it does, I'll 
build test kernels for all the other supported releases as well.

Thanks in advance!

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

Title:
  [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling
  the host

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Triaged
Status in linux source package in Wily:
  Triaged

Bug description:
  hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
  Based on the information given to this driver (via the xmit_more skb flag),
  we can defer signaling the host if more packets are on the way. This will help
  make the host more efficient since it can potentially process a larger batch 
of
  packets. Implement this optimization.

  Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem
  /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a

  This commit may imply other commits previously requested, for example
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074

  Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04,
  14.04 HWE, 12.02, and 12.02 HWE

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

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

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Dave Chiluk]

** Description changed:

+ [Impact]
+ 
+  * Users with Samsung 8** SSD drives see miscellaneous errors and
+ warning messages in the logs depending on the firmware level of the
+ drive while booting or after running trim.
+ 
+ [Test Case]
+ 
+  * Run this script, and then check logs for errors.
+ #!/bin/bash
+ 
+ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
+ for i in {0..10} ; do
+   cp linux linux$i
+ done
+ rm -rf linux
+ echo sudo fstrim requires your password
+ sudo fstrim ./
+ 
+ [Regression Potential]
+ 
+  * There is very little regression potential as this change simply
+ prevents NCQ trim from being used on Samsung 8** drives.
+ 
+ [Other Info]
+  
+  * Commit is upstream.
+  * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.
+ 
+ 
+ ===Original Bug description ==
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
  
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * Users with Samsung 8** SSD drives see miscellaneous errors and
  warning messages in the logs depending on the firmware level of the
  drive while booting or after running trim.

  [Test Case]

   * Run this script, and then check logs for errors.
  #!/bin/bash

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  for i in {0..10} ; do
   cp linux linux$i
  done
  rm -rf linux*
  echo sudo fstrim requires your password
  sudo fstrim ./

  [Regression Potential]

   * There is very little regression potential as this change simply
  prevents NCQ trim from being used on Samsung 8** drives.

  [Other Info]

   * Commit is upstream.
   * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.

  ===Original Bug description ==
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Dave Chiluk]

** Description changed:

  [Impact]
  
-  * Users with Samsung 8** SSD drives see miscellaneous errors and
+  * Users with Samsung 8** SSD drives see miscellaneous errors and
  warning messages in the logs depending on the firmware level of the
  drive while booting or after running trim.
  
  [Test Case]
  
-  * Run this script, and then check logs for errors.
+  * Run this script, and then check logs for errors.
  #!/bin/bash
  
  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  for i in {0..10} ; do
-   cp linux linux$i
+  cp linux linux$i
  done
- rm -rf linux
+ rm -rf linux*
  echo sudo fstrim requires your password
  sudo fstrim ./
  
  [Regression Potential]
  
-  * There is very little regression potential as this change simply
+  * There is very little regression potential as this change simply
  prevents NCQ trim from being used on Samsung 8** drives.
  
  [Other Info]
-  
-  * Commit is upstream.
-  * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.
  
+  * Commit is upstream.
+  * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.
  
  ===Original Bug description ==
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
  
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * Users with Samsung 8** SSD drives see miscellaneous errors and
  warning messages in the logs depending on the firmware level of the
  drive while booting or after running trim.

  [Test Case]

   * Run this script, and then check logs for errors.
  #!/bin/bash

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  for i in {0..10} ; do
   cp linux linux$i
  done
  rm -rf linux*
  echo sudo fstrim requires your password
  sudo fstrim ./

  [Regression Potential]

   * There is very little regression potential as this change simply
  prevents NCQ trim from being used on Samsung 8** drives.

  [Other Info]

   * Commit is upstream.
   * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.

  ===Original Bug description 

[Kernel-packages] [Bug 1452165] Re: currupted btrfs breaks both recovery and boot

[god]

I appreciate your help but I'm rather reluctant to corrupt my fs for the
sake of testing another kernel version.

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

Title:
  currupted btrfs breaks both recovery and boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If btrfs volume is corrupted (separate /home partition, not even /
  !!!) than not only booting ubuntu in normal AND recovery mode is
  impossible but even liveusb fails as well. The recovery drops to shell
  but it's impossible to fix btrfs - there's unkillable mount -t
  btrfs... process hanging and kernel regularly pukes with btrfs-
  transacti blocked for 120 seconds message.

  This is beyond horrible - the whole purpose of recovery mode is to fix
  errors like that, errors on partition which is not used to boot from
  (e. g. /home) should never ever break it. Alternatively you could add
  new mode to grub menu - smth like recovery which actually works or
  something like that.

  The workaround is to add 'break=premount' to grub command line and fix
  btrfs with 'btrfs check --repair /dev/dm-' from initramfs.

  Found on xubuntu 15.04 x86_64.

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

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

[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error

[Joseph Salisbury]

Thanks for the update, Alex.

I am performing a Reverse bisect between v4.1-rc4 and v4.1-rc5 using the 
master branch in the mainline repo:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

I'll continue the bisect unless you prefer to do it.  Here is the
current bisect log:

# good: [e26081808edadfd257c6c9d81014e3b25e9a6118] Linux 4.1-rc4
git bisect good e26081808edadfd257c6c9d81014e3b25e9a6118
# bad: [ba155e2d21f6bf05de86a78dbe5bfd8757604a65] Linux 4.1-rc5
git bisect bad ba155e2d21f6bf05de86a78dbe5bfd8757604a65
# good: [1d82b0baf9abd59ae6f53f3102f4e442043763a4] Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
git bisect good 1d82b0baf9abd59ae6f53f3102f4e442043763a4
# good: [0b6280c62026168f79ff4dd1437df131bdfd24f2] Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
git bisect good 0b6280c62026168f79ff4dd1437df131bdfd24f2
# good: [b0f155ada4c819f06aa32b4c906e7e76350c7ec1] drm/exynos: dp: Lower level 
of EDID read success message
git bisect good b0f155ada4c819f06aa32b4c906e7e76350c7ec1
# good: [7ce14f6ff26460819345fe8495cf2dd6538b7cdc] Merge branch 'for-linus-4.1' 
of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs
git bisect good 7ce14f6ff26460819345fe8495cf2dd6538b7cdc

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

Title:
  [Hyper-V] Fiber Channel critical target error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System details:
  Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 
4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 
(Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3)

  Ubuntu 3.19.0-11
  Ubuntu Vivid 15.04 64bit custom kernel
  Platform: WS2012R2

  Using a fiber channel disk partition ( dev/sde1 in this example) outputs the 
following error:
  ​
  [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0
  [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0
  [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0

  Creating a partition works, reading too, but first time writing it
  hangs for around 20 seconds and after a couple more writes the
  partition goes into read-only mode:

  #echo test1  test1.txt
  *hangs for 30 seconds*
  blk_update_request: critical target error, dev sde, sector 0
  # echo test2  test2.txt
  blk_update_request: critical target error, dev sde, sector 289671192
  Aborting journal on device sde1-8.
  EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted 
journal
  EXT4-fs (sde1): Remounting filesystem read-only
  # echo test string  sample.txt
  -bash: sample.txt: Read-only file system

  
  Dmesg log:
  [  461.284362] blk_update_request: critical target error, dev sde, sector 0
  [  484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  548.988377] blk_update_request: critical target error, dev sde, sector 0
  [  609.216340] blk_update_request: critical target error, dev sde, sector 
289671192
  [  609.221812] Aborting journal on device sde1-8.
  [  612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: 
Detected aborted journal
  [  612.249529] EXT4-fs (sde1): Remounting filesystem read-only

  Additional info:

  cat /proc/version_signature
  Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3

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

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

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Dave Chiluk]

** Changed in: linux (Ubuntu)
Milestone: None = trusty-updates

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Chris J Arges]

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

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

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

** Also affects: linux (Ubuntu Wily)
   Importance: High
 Assignee: Dave Chiluk (chiluk)
   Status: Incomplete

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  New
Status in linux source package in Utopic:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  Incomplete

Bug description:
  [Impact]

   * Users with Samsung 8** SSD drives see miscellaneous errors and
  warning messages in the logs depending on the firmware level of the
  drive while booting or after running trim.

  [Test Case]

   * Run this script, and then check logs for errors.
  #!/bin/bash

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  for i in {0..10} ; do
   cp linux linux$i
  done
  rm -rf linux*
  echo sudo fstrim requires your password
  sudo fstrim ./

  [Regression Potential]

   * There is very little regression potential as this change simply
  prevents NCQ trim from being used on Samsung 8** drives.

  [Other Info]

   * Commit is upstream.
   * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.

  ===Original Bug description ==
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1413741] Re: CVE-2014-8159

[Mathew Hodson]

Vivid and Wily are not affected according to http://people.canonical.com
/~ubuntu-security/cve/2014/CVE-2014-8159.html

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

Title:
  CVE-2014-8159

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux-lts-vivid source package in Utopic:
  Invalid
Status in linux-mako source package in Utopic:
  New
Status in linux-manta source package in Utopic:
  New
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in 

[Kernel-packages] [Bug 1461261] [NEW] 14.04 linux-generic-lts-vivid but no vivid firmware

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello

Within Ubuntu 14.04 its possible to install the vivid kernel, but, the
linux-firmware package is for an older kernel.

schreiner@xps13:~$ modinfo iwlwifi | grep 7265
firmware:   iwlwifi-7265D-10.ucode
firmware:   iwlwifi-7265-10.ucode

I had to install the vivid linux-firmware package to get the wireless
running again.

Is there a better solution?

Regards Dominik

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


** Tags: bot-comment
-- 
14.04 linux-generic-lts-vivid but no vivid firmware
https://bugs.launchpad.net/bugs/1461261
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-firmware 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 1437096] Re: soundcard not recognised after upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  soundcard not recognised after upgrade

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have an HP Pavillion dv7 and Kubuntu 12.04. I performed update and upgrade 
of the system and linux-generic, linux-headers, linux-image, linux-libc-dev 
changed from 3.2.0.77 to 3.2.0.79 version. After that my soundcard is not 
recognized (obviously I get no sound). I can not find a way to reverse this 
upgrade.
  --- 
  AlsaDevices:
   total 0
   crw-rw---T+ 1 root audio 116,  1 Mar 27 01:21 seq
   crw-rw---T+ 1 root audio 116, 33 Mar 27 01:21 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices: aplay: device_list:252: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  ArecordDevices: arecord: device_list:252: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=ea5f3b76-01df-4289-bb10-26a79247053d
  InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120423)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  MarkForUpload: True
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-79-generic 
root=UUID=d35afbe1-2cd1-4220-9b46-fb9869746c7e ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-79.115-generic 3.2.67
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-79-generic N/A
   linux-backports-modules-3.2.0-79-generic  N/A
   linux-firmware1.79.18
  StagingDrivers: rts_pstor mei
  Tags:  precise staging
  Uname: Linux 3.2.0-79-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  dmi.bios.date: 10/03/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1800
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.02:bd10/03/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1800:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1440197] Re: BUG: unable to handle kernel paging request at 00007f7097aaf120

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG: unable to handle kernel paging request at 7f7097aaf120

Status in linux package in Ubuntu:
  Expired

Bug description:
  After a reboot you see this issue

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-12-generic 3.19.0-12.12
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1173 F pulseaudio
christians   1901 F pulseaudio
   /dev/snd/controlC0:  lightdm1173 F pulseaudio
christians   1901 F pulseaudio
  CRDA:
   country EU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (N/A, 20), (N/A)
(5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
(5490 - 5710 @ 40), (N/A, 27), (0 ms), DFS
  Date: Fri Apr  3 22:43:14 2015
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location 0xc018bfd2
  Failure: oops
  HibernationDevice: RESUME=UUID=281eead9-36cf-412f-879b-45d0ed60f07a
  InstallationDate: Installed on 2015-04-03 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: LENOVO 20BX000TGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 7f7097aaf120
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET45WW (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET45WW(1.10):bd02/03/2015:svnLENOVO:pn20BX000TGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000TGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000TGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1426954] Re: [Dell Inc. Inspiron 3520] suspend/resume failure

[Launchpad Bug Tracker]

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

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

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

Title:
  [Dell Inc. Inspiron 3520] suspend/resume failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  During resume

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-13-generic 3.18.0-13.14 [modified: 
boot/vmlinuz-3.18.0-13-generic]
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  semaj811704 F pulseaudio
  Date: Sun Mar  1 15:03:00 2015
  DuplicateSignature: suspend/resume:Dell Inc. Inspiron 3520:A04
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=4aca09ef-164f-441b-b377-be094409778a
  InstallationDate: Installed on 2015-02-24 (5 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150222)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Inspiron 3520
  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-13-generic 
root=UUID=7cd8ae67-dc6a-4f10-aac5-14001153b91d 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-13-generic N/A
   linux-backports-modules-3.18.0-13-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 3520] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0G8TPV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd09/28/2012:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0G8TPV:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3520
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1439707] Re: Leap second added on 2015-03-31

[Launchpad Bug Tracker]

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

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

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

Title:
  Leap second added on 2015-03-31

Status in linux package in Ubuntu:
  Expired

Bug description:
  The following line was found in /var/log/syslog of several servers:

  2015-04-01T01:59:59.010179+02:00 hostname kernel: [724373.452000]
  Clock: inserting leap second 23:59:60 UTC

  ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.2 was also installed.

  https://twitter.com/sachar/status/583113639533490176 may be relevant.

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

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

[Kernel-packages] [Bug 979119] Re: 12.04: Resume Failure: Press any key to continue from suspend

[Launchpad Bug Tracker]

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

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

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

Title:
  12.04: Resume Failure: Press any key to continue from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Suspend (due to inactivity), by closing the laptop lid, or by manually
  selecting suspend does suspend correctly, but gets the error Resume
  Failure: Press any key to continue when waking up.  The machine will
  then reboot.

  This problem did exist intermittently on 9.10 and earlier systems.
  Since 10.04 it has not been a problem.  11.10 has been particularly
  good with no suspend issues at all.

  Hardware details:

  Machine: Toshiba Tecra A8, with CoreDuo (Genuine Intel® CPU T2300 @
  1.66GHz × 2)

  lspci entries related to graphics driver:

  00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express Memory Controller Hub (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03)
  00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)

  Just did an upgrade from 11.10 to 12.04 and the problem came about
  immediately.  32 bit install.  All updated applied (dist-upgrade)

  pm-utils version installed: 1.4.1-9

  I was recommended to submit this bug on pm-utils.  I was also told
  that I may want to mark it as kernel related, but am unsure how to do
  that.

  I have referenced the following bug on resume from suspend issues:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/962142

  but the problem seems slightly different (the other bug does not
  mention the display indicating the resume failure message).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pm-utils 1.4.1-9
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  ApportVersion: 2.0.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr 11 19:31:27 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110921.2)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: Upgraded to precise on 2012-04-11 (0 days ago)

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

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

[Kernel-packages] [Bug 1461261] Re: 14.04 linux-generic-lts-vivid but no vivid firmware

[Dominik Zogg]

** Package changed: ubuntu = linux-firmware (Ubuntu)

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

Title:
  14.04 linux-generic-lts-vivid but no vivid firmware

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hello

  Within Ubuntu 14.04 its possible to install the vivid kernel, but,
  the linux-firmware package is for an older kernel.

  schreiner@xps13:~$ modinfo iwlwifi | grep 7265
  firmware:   iwlwifi-7265D-10.ucode
  firmware:   iwlwifi-7265-10.ucode

  I had to install the vivid linux-firmware package to get the wireless
  running again.

  Is there a better solution?

  Regards Dominik

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

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

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

I have verified Linux kernel 3.16.0-39.53 and the right button works.

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

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

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

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

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
  Tested-by: Jason Ekstrand ja...@jlekstrand.net
  Signed-off-by: Jiri Kosina jkos...@suse.cz

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

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

[Kernel-packages] [Bug 1454013] Re: Booting takes very long time on Intel Braswell caused by eMMC

[Tsung-Han Lin]

Tested trusty, utopic and vivid kernels on the problematic platform,
they all work and solve the long boot time issue.

** Tags removed: verification-needed-utopic verification-needed-vivid
** Tags added: verification-done-utopic verification-done-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/1454013

Title:
  Booting takes very long time on Intel Braswell caused by eMMC

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  This patch could fix this issue, otherwise booting will take very long
  time.

  
  4e93b9a6abc0d028daf3c8a00cb77b679d8a4df4
  mmc: card: Don't access RPMB partitions for normal read/write
  During kernel boot, it will try to read some logical sectors
  of each block device node for the possible partition table.

  But since RPMB partition is special and can not be accessed
  by normal eMMC read / write CMDs, it will cause below error
  messages during kernel boot:
  ...
   mmc0: Got data interrupt 0x0002 even though no data operation was in 
progress.
   mmcblk0rpmb: error -110 transferring data, sector 0, nr 32, cmd response 
0x900, card status 0xb00
   mmcblk0rpmb: retrying using single block read
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   end_request: I/O error, dev mmcblk0rpmb, sector 0
   Buffer I/O error on device mmcblk0rpmb, logical block 0
   end_request: I/O error, dev mmcblk0rpmb, sector 8
   Buffer I/O error on device mmcblk0rpmb, logical block 1
   end_request: I/O error, dev mmcblk0rpmb, sector 16
   Buffer I/O error on device mmcblk0rpmb, logical block 2
   end_request: I/O error, dev mmcblk0rpmb, sector 24
   Buffer I/O error on device mmcblk0rpmb, logical block 3
  ...

  This patch will discard the access request in eMMC queue if
  it is RPMB partition access request. By this way, it avoids
  trigger above error messages.

  Fixes: 090d25fe224c (mmc: core: Expose access to RPMB partition)
  Signed-off-by: Yunpeng Gao yunpeng@intel.com
  Signed-off-by: Chuanxiao Dong chuanxiao.d...@intel.com
  Tested-by: Michael Shigorin m...@altlinux.org
  Signed-off-by: Ulf Hansson ulf.hans...@linaro.org

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

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

[Kernel-packages] [Bug 1292400] Re: task systemd-udevd:1906 blocked for more than 120 seconds.

[Dexuan Cui]

The patch has been in the mainline tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30467e0b3be83c286d60039f8267dd421128ca74

Can Ubuntu people please check if the patch has been included in Ubuntu?

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

Title:
  task systemd-udevd:1906 blocked for more than 120 seconds.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System log shows repeated incidents of task systemd-udevd:1906
  blocked for more than 120 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37 [modified: 
boot/vmlinuz-3.13.0-17-generic]
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Fri Mar 14 08:54:36 2014
  HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b
  InstallationDate: Installed on 2014-03-12 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed 
root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b
  InstallationDate: Installed on 2014-03-12 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed 
root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  

[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error

[Alex Ng]

Hi,

The issue also shows up in this kernel.

I can take over the bisect. My current bisect log is the same as yours.

I'm currently building the next test kernel up to following commit: 
74856fbf441929918c49ff262ace9835048e4e6a

Will let you know when I narrow it down further.

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

Title:
  [Hyper-V] Fiber Channel critical target error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System details:
  Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 
4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 
(Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3)

  Ubuntu 3.19.0-11
  Ubuntu Vivid 15.04 64bit custom kernel
  Platform: WS2012R2

  Using a fiber channel disk partition ( dev/sde1 in this example) outputs the 
following error:
  ​
  [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0
  [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0
  [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0

  Creating a partition works, reading too, but first time writing it
  hangs for around 20 seconds and after a couple more writes the
  partition goes into read-only mode:

  #echo test1  test1.txt
  *hangs for 30 seconds*
  blk_update_request: critical target error, dev sde, sector 0
  # echo test2  test2.txt
  blk_update_request: critical target error, dev sde, sector 289671192
  Aborting journal on device sde1-8.
  EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted 
journal
  EXT4-fs (sde1): Remounting filesystem read-only
  # echo test string  sample.txt
  -bash: sample.txt: Read-only file system

  
  Dmesg log:
  [  461.284362] blk_update_request: critical target error, dev sde, sector 0
  [  484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  548.988377] blk_update_request: critical target error, dev sde, sector 0
  [  609.216340] blk_update_request: critical target error, dev sde, sector 
289671192
  [  609.221812] Aborting journal on device sde1-8.
  [  612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: 
Detected aborted journal
  [  612.249529] EXT4-fs (sde1): Remounting filesystem read-only

  Additional info:

  cat /proc/version_signature
  Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3

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

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

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

I have verified Linux kernel 3.13.0-54.91 but the right button doesn't work.
In fact, the touchpad doesn't work at all.

** Tags removed: verification-needed-trusty
** Tags added: verification-failed-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/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

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

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
  Tested-by: Jason Ekstrand ja...@jlekstrand.net
  Signed-off-by: Jiri Kosina jkos...@suse.cz

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

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

[Kernel-packages] [Bug 1454253] [NEW] external usb breaks suspend

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After booting xubuntu 15.04 it's possible to suspend it the normal way
BUT - only until you've plugged external usb hard drive. After that
(even if it was unmounted and removed) it becomes impossible: the system
goes to suspend briefly (for bout 1 second) but immediately wakes up for
no apparent reason.

I suspect there's some weird bug in xfce power management - is there a
way to disable it alltogether and  rely on systemd directly instead?

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

-- 
external usb breaks suspend
https://bugs.launchpad.net/bugs/1454253
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 1454253] Re: external usb breaks suspend

[Martin Pitt]

Thanks for confirming! Reassigning to the kernel then.

** Package changed: systemd (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/1454253

Title:
  external usb breaks suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After booting xubuntu 15.04 it's possible to suspend it the normal way
  BUT - only until you've plugged external usb hard drive. After that
  (even if it was unmounted and removed) it becomes impossible: the
  system goes to suspend briefly (for bout 1 second) but immediately
  wakes up for no apparent reason.

  I suspect there's some weird bug in xfce power management - is there a
  way to disable it alltogether and  rely on systemd directly instead?

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

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

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

[Brad Figg]

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

apport-collect 1454253

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

Title:
  external usb breaks suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After booting xubuntu 15.04 it's possible to suspend it the normal way
  BUT - only until you've plugged external usb hard drive. After that
  (even if it was unmounted and removed) it becomes impossible: the
  system goes to suspend briefly (for bout 1 second) but immediately
  wakes up for no apparent reason.

  I suspect there's some weird bug in xfce power management - is there a
  way to disable it alltogether and  rely on systemd directly instead?

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

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

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended

[Jan Rathmann]

I did check it again yesterday and today using 'systemctl suspend'. The
bug does not always happen, e.g. yesterday I was able to suspend my
system 4 or 5 times in a row properly, but tomorrow after the first
attempt the PC woke up again by itself ~2 seconds after I suspended it.
So yes, the bug is still there unfortunately. I have used 'pm-suspend'
almost exclusively during the last two months and this bug never ever
has happened with 'pm-suspend' during that time (or in earlier Ubuntu
releases).

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

Title:
  Gigabyte P35-DS3: does not stay suspended

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

Bug description:
  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running cat /proc/acpi/wakeup | grep enabled if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like echo USB0  /proc/acpi/wakeup) had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as enabled.

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: needs suspend quirks

[Martin Pitt]

The main difference here is that under upstart we still run pm-suspend
with its quirks, while under systemd there are no quirks being run any
more. As suspend quirks have  supposed to be obsolete  for many years
and should be fixed properly in drivers/kernel, I add a linux task.

To find out which quirks you need, can you please run

  sudo pm-suspend --store-quirks-as-lkw

confirm that this actually still works properly (i. e. leave it
suspended for a few minuts), and then attach /var/cache/pm-
utils/last_known_working.quirkdb ? Thanks!

** Summary changed:

- Systemd prevents computer from staying suspended
+ Gigabyte P35-DS3: needs suspend quirks

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

** Summary changed:

- Gigabyte P35-DS3: needs suspend quirks
+ Gigabyte P35-DS3: does not stay suspended

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

Title:
  Gigabyte P35-DS3: does not stay suspended

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

Bug description:
  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running cat /proc/acpi/wakeup | grep enabled if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like echo USB0  /proc/acpi/wakeup) had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as enabled.

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1443888] Re: No sound on ThinkPad docking station

[madbiologist]

Fix has been released in Vivid kernel  3.19.0-18.18.

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

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

Title:
  No sound on ThinkPad docking station

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a Thinkpad T450s. The sound works normally unless it is plugged
  in to the docking station (a ThinkPad Ultra Dock). If speakers are
  plugged in to the dock, the internal speakers get disabled correctly,
  but the output of the docking station does not work. Speakers which
  are plugged in directly on the Laptop still work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-13-generic 3.19.0-13.13
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 1739 F pulseaudio
   /dev/snd/controlC1:  daniel 1739 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 14 12:58:35 2015
  HibernationDevice: RESUME=UUID=a67a91aa-8c15-4693-be37-7c177747bc39
  InstallationDate: Installed on 2015-04-04 (9 days ago)
  InstallationMedia: It
  MachineType: LENOVO 20BWS03E00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic 
root=UUID=1643390a-82a8-405a-b938-057879ff3c9c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-13-generic N/A
   linux-backports-modules-3.19.0-13-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-04 (9 days ago)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET41WW (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS03E00
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET41WW(1.06):bd12/23/2014:svnLENOVO:pn20BWS03E00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS03E00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1458351] Re: [ASUS UX305FA] Some Fn+ Keys Not Working

[Carlo Abelli]

Forgot to add a subject line but here is the thread:

http://www.spinics.net/lists/linux-input/msg38966.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/1458351

Title:
  [ASUS UX305FA] Some Fn+ Keys Not Working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Brightness control keys on my laptop not being recognized (including
  no output from acpi_listen). Running Ubuntu 14.04.2 LTS. Other
  function keys do work and are recognized ex. volume.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun May 24 12:59:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
  InstallationDate: Installed on 2015-05-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed 
root=UUID=246981b4-9b06-41f9-ac18-1e5ba27d4247 ro quiet splash acpi_osi=Linux 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun May 24 12:07:13 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8493 
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Kernel-packages] [Bug 1457807] Re: CVE-2015-4036

[John Johansen]

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New = Fix Committed

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

Title:
  CVE-2015-4036

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux-lts-vivid source package in Utopic:
  Invalid
Status in linux-mako source package in Utopic:
  New
Status in linux-manta source package in Utopic:
  New
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source 

[Kernel-packages] [Bug 1459985] Re: r8169 ethernet stops working after a while

[Ville Ranki]

I updated the bios to latest provided by Lenovo, but the problem
persists.


output of dmidecode -s bios-version  sudo dmidecode -s bios-release-date:
J9ET99WW (2.19 )
05/05/2015

This may also be a NetworkManager issue - i've filed bug #1461015 on nm
with a error message in journal.

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

** Tags removed: bios-outdated-2.19

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

Title:
  r8169 ethernet stops working after a while

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a lenovoE540  laptop with a r8169 wired onboard ethernet. When
  the computer is started, ethernet works fine for about 20-30 minutes.
  After that network stops working.

  dmesg shows that initially the link is up and stays up:

  [   41.806656] r8169 :04:00.0 eth0: link up

  There are no other networking related messages. Networking starts
  working again if I disconnect and connect again the cable. After this
  networking works until computer is shut down.

  This is reproducible and happens to me every day. There are also other
  reports on r8169 issues but I didn't find a matching bug report on
  launchpad. This happens only to this computer on network, so I doubt
  it's a DHCP or other network misconfiguration issue.

  http://askubuntu.com/questions/615423/ethernet-connection-randomly-
  disconnects-after-transmit-queue-0-timed-out

  http://forums.linuxmint.com/viewtopic.php?f=90t=177544

  https://bugs.launchpad.net/ubuntu/+source/linux-backports-
  modules-3.0.0/+bug/839393

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vranki 2683 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Fri May 29 12:48:08 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=71d76087-3fdf-4f57-a0f4-0b128be4d386
  InstallationDate: Installed on 2015-02-12 (105 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: LENOVO 20C600LLMS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=e114ca99-f1c7-450f-a4a5-553075d92b7c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-12 (16 days ago)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600LLMS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600LLMS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600LLMS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600LLMS
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1440329] Re: No Sound output with Lenovo T450s and ThinkPad Ultra Docking station

[madbiologist]

Fix has been released in Vivid kernel 3.19.0-18.18.

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

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

Title:
  No Sound output with Lenovo T450s and ThinkPad Ultra Docking station

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  When the T450s is docked into the Docking Station (40A20135EU) there
  is no sound output at the back off the Docking Station.

  [14308.190460] thinkpad_acpi: docked into hotplug port replicator
  [14309.170738] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd
  [14309.188134] usb 2-3: New USB device found, idVendor=17ef, idProduct=1010
  [14309.188142] usb 2-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [14309.188143] usb 2-3: Product: Lenovo ThinkPad Dock
  [14309.188146] usb 2-3: Manufacturer: LENOVO
  [14309.188907] hub 2-3:1.0: USB hub found
  [14309.189060] hub 2-3:1.0: 4 ports detected
  [14309.302638] usb 1-3: new high-speed USB device number 11 using xhci_hcd
  [14309.432610] usb 1-3: New USB device found, idVendor=17ef, idProduct=1010
  [14309.432615] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [14309.432617] usb 1-3: Product: Lenovo ThinkPad Dock
  [14309.432618] usb 1-3: Manufacturer: LENOVO
  [14309.433479] hub 1-3:1.0: USB hub found
  [14309.438541] hub 1-3:1.0: 4 ports detected
  [14309.695137] thinkpad_acpi: EC reports that Thermal Table has changed
  [14309.726708] usb 1-3.1: new full-speed USB device number 12 using xhci_hcd
  [14309.827655] usb 1-3.1: New USB device found, idVendor=13ba, idProduct=0018
  [14309.827658] usb 1-3.1: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [14309.827660] usb 1-3.1: Product: Barcode Reader
  [14309.910809] usb 1-3.4: new high-speed USB device number 13 using xhci_hcd
  [14310.011137] usb 1-3.4: New USB device found, idVendor=17ef, idProduct=100f
  [14310.011139] usb 1-3.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [14310.011140] usb 1-3.4: Product: Lenovo ThinkPad Dock
  [14310.011141] usb 1-3.4: Manufacturer: Lenovo
  [14310.011142] usb 1-3.4: SerialNumber: Rev1.2
  [14310.011757] hub 1-3.4:1.0: USB hub found
  [14310.011868] hub 1-3.4:1.0: 3 ports detected

  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller
  (rev 09)

  Any ideas?

  Cheers
  Christian
  ---
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   christians   2047 F...m pulseaudio
   /dev/snd/controlC1:  christians   2047 F pulseaudio
   /dev/snd/controlC0:  christians   2047 F pulseaudio
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=281eead9-36cf-412f-879b-45d0ed60f07a
  InstallationDate: Installed on 2015-04-03 (10 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: LENOVO 20BX000TGE
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-13.13-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-13-generic N/A
   linux-backports-modules-3.19.0-13-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 3.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET45WW (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET45WW(1.10):bd02/03/2015:svnLENOVO:pn20BX000TGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000TGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000TGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1460265] Re: Suspend to RAM fails: (0 tasks refusing to freeze, wq_busy=1)

[al]

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.0.4

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

Title:
  Suspend to RAM fails: (0 tasks refusing to freeze, wq_busy=1)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  version:   Ubuntu 3.19.0-16.16-generic 3.19.3
  Suspend worked fine in Kubuntu 14.04 LTS (kernel version 3.13.0-30)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilya   1718 F pulseaudio
   /dev/snd/controlC1:  ilya   1718 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat May 30 11:27:09 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-21 (8 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: System manufacturer P5Q DELUXE
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=5b07cbf3-c34c-4ff2-9c9d-2a990850fcc4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  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/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/10/2009:svnSystemmanufacturer:pnP5QDELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q DELUXE
  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/1460265/+subscriptions

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

[Kernel-packages] [Bug 1459985] Re: r8169 ethernet stops working after a while

[Christopher M. Penalver]

Ville Ranki, 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 XY 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 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-2.19

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

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

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

Title:
  r8169 ethernet stops working after a while

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a lenovoE540  laptop with a r8169 wired onboard ethernet. When
  the computer is started, ethernet works fine for about 20-30 minutes.
  After that network stops working.

  dmesg shows that initially the link is up and stays up:

  [   41.806656] r8169 :04:00.0 eth0: link up

  There are no other networking related messages. Networking starts
  working again if I disconnect and connect again the cable. After this
  networking works until computer is shut down.

  This is reproducible and happens to me every day. There are also other
  reports on r8169 issues but I didn't find a matching bug report on
  launchpad. This happens only to this computer on network, so I doubt
  it's a DHCP or other network misconfiguration issue.

  http://askubuntu.com/questions/615423/ethernet-connection-randomly-
  disconnects-after-transmit-queue-0-timed-out

  http://forums.linuxmint.com/viewtopic.php?f=90t=177544

  https://bugs.launchpad.net/ubuntu/+source/linux-backports-
  modules-3.0.0/+bug/839393

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vranki 2683 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Fri May 29 12:48:08 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=71d76087-3fdf-4f57-a0f4-0b128be4d386
  InstallationDate: Installed on 2015-02-12 (105 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: LENOVO 20C600LLMS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=e114ca99-f1c7-450f-a4a5-553075d92b7c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-12 (16 days ago)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600LLMS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600LLMS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600LLMS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600LLMS
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1417778] Re: ubuntu 14.10 Error while reading from descriptor: broken pipe

[Christopher M. Penalver]

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

Please feel free to subscribe me to it.

** Attachment removed: Screen after broken pipe error
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417778/+attachment/4364188/+files/photo.JPG

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

Title:
  ubuntu 14.10 Error while reading from descriptor: broken pipe

Status in linux package in Ubuntu:
  Expired

Bug description:
  Long time of boot. 
  ubuntu 14.10 Error while reading from descriptor: broken pipe
  usb 4-3: string descriptor 0 read error: -22

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andruwa1985   2670 F pulseaudio
   /dev/snd/controlC1:  andruwa1985   2670 F pulseaudio
   /dev/snd/pcmC0D0p:   andruwa1985   2670 F...m pulseaudio
   /dev/snd/controlC0:  andruwa1985   2670 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb  4 00:47:15 2015
  HibernationDevice: RESUME=UUID=f809c1c0-0fc9-4541-9075-0323c2f5a077
  InstallationDate: Installed on 2015-01-31 (3 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=15f3c6fb-ce3c-4f25-bfeb-ebe0f3259731 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0213
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0213:bd08/06/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.name: System Product Name
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended

[Jan Rathmann]

Martin, thanks for looking into this, I have attached the requested
file.

** Attachment added: last_known_working.quirkdb
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4408564/+files/last_known_working.quirkdb

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

Title:
  Gigabyte P35-DS3: does not stay suspended

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

Bug description:
  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running cat /proc/acpi/wakeup | grep enabled if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like echo USB0  /proc/acpi/wakeup) had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as enabled.

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware

[Chris J Arges]

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

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

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

Title:
  backport request: include support for OpenPower hardware

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  In Progress
Status in linux source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  This is a HWE SRU for OpenPower support in 3.16.

  [Fix]
  upstream commits:
  backported from commit 6a11e5c67a397e9a64cfde6961c83a7a64d7980c)
  backported from commit 608b286d1ddf38a7ceb624d2b689af095816d91c)
  cherry picked from commit 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2)
  cherry picked from commit 4c3b21686111e0ac6018469dacbc5549f9915cf8)
  cherry picked from commit a4bcbe6a41adcaa5e7f1830a7c1da8691d9d2b1d)
  backported from commit 08135139430fabdeaa990da8a9e0d436aad0672b)
  cherry picked from commit c1c3a526bb4ddbec7639a9fb3b84fede25b201d9)
  cherry picked from commit b921e90260cec1e04988bb3763491de885b67b51)
  backported from commit e8a51e1b51ee5730ad3913f3962e3099a5e19359)
  cherry picked from commit 5590f3196b293574a12be58d06d5e1120d8856ec)
  backported from commit 529d235a0e190ded1d21ccc80a73e625ebcad09b)

  [Test Case]
  Ensure kernel boots on specific OpenPower hardware.

  --

  We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11),
  which add OpenPower support to the Ubuntu kernel.

  The changes are available in the ubuntu/vivid branch of:

   https://github.com/open-power/linux.git

  (or I can attach them separately).

  Changelogs are as follows:

  commit 2f0190bd43764559b250a5bd11aca050f909aa21
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Fri Nov 14 16:13:50 2014 +1100

  powerpc/powernv: Support OPAL requested heartbeat

  If OPAL requests it, call it back via opal_poll_events() at a
  regular interval. Some versions of OPAL on some machines require
  this to operate some internal timeouts properly.

  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org

  Backport notes:
   cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2
   minor conflicts resolved
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit e1c89541e7163494ad091f3c2622649d91ac7597
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Mon Feb 16 14:59:08 2015 +1100

  device: Add dev_of_node() accessor

  Suggested by Arnd Bergmann, this gives a practical accessor for
  the of_node field of struct device while instructing the compiler
  that it will be NULL if CONFIG_OF is not set.

  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
  Acked-by: Rob Herring r...@kernel.org

  Backport notes:
   Submission to LKML at: https://patchwork.kernel.org/patch/5831161/
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit 2c242b30756f77528516a4e9e986818ac4e90490
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Wed Feb 18 11:25:18 2015 +1100

  drivers/core/of: Add symlink to device-tree from devices with an
  OF node

  So I've been annoyed lately with having a bunch of devices such as i2c
  eeproms (for use by VPDs, server world !) and other bits and pieces that
  I want to be able to identify from userspace, and possibly provide
  additional data about from FW.

  Basically, it boils down to correlating the sysfs device with the OF
  tree device node, so that user space can use device-tree info such as
  additional location or label (or whatever else we can come up with)
  propreties to identify a given device, or get some attributes of use
  about it, etc...

  Now, so far, we've done that in some subsystem in a fairly ad-hoc basis
  using devspec properties. For example, PCI creates them if it can
  correlate the probed device with a DT node. Some powerpc specific busses
  do that too.

  However, i2c doesn't and it would be nice to have something more generic
  since technically any device can have a corresponding device tree node.

  This patch adds an of_node symlink to devices that have a non-NULL
  dev-of_node pointer, the patch is pretty trivial and seems to work just
  fine for me.

  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
  Acked-by: Rob Herring r...@kernel.org

  Backport notes:
   Submission to LKML at: https://patchwork.kernel.org/patch/5842241/
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c
  Author: Michael Ellerman m...@ellerman.id.au
  Date:   Sat Mar 28 21:35:16 2015 +1100

  powerpc: Add a proper syscall for switching endianness

  We currently have a special syscall for switching 

[Kernel-packages] [Bug 1460434] Re: System Freeze On Low Memory

[Gökhan]

I had the same issue before upgrade. I tested latest kernel
(v4.1-rc6-unstable) today. Problem still exists. I wrote simple test
program to occupy some memory. It allocates bytes increasingly +50 MB at
a time. I can never see that unused memory goes under 200 MB and whole
machine gets almost fully blocked until I kill test program.

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

Title:
  System Freeze On Low Memory

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System freeze occurs when memory is almost full and there is no chance
  to kill processes. Everything is unresponsive, hdd is trashing, even
  ssh connection does not show any reaction. I set vm.swappiness = 1 to
  minimize swapping but those lock ups are still there. I think this
  could be related to disk caching. Few times I observed in iotop that
  several processes use %90+ disk I/O while memory is close to its
  limit. I increased vm.min_free_kbytes (default value was 65536) but
  not tested yet. Current disk scheduler is set to deadline.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2571 F pulseaudio
  CurrentDesktop: LXDE
  Date: Sun May 31 16:29:04 2015
  InstallationDate: Installed on 2014-11-15 (197 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Packard Bell ENNS44HR
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=88ea410e-70cc-49a6-b2b3-326fc63a4e7d ro quiet splash elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-04 (27 days ago)
  dmi.bios.date: 04/28/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.23
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: ENNS44HR
  dmi.board.vendor: Packard Bell
  dmi.board.version: V1.23
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.23
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.23:bd04/28/2011:svnPackardBell:pnENNS44HR:pvrV1.23:rvnPackardBell:rnENNS44HR:rvrV1.23:cvnPackardBell:ct9:cvrV1.23:
  dmi.product.name: ENNS44HR
  dmi.product.version: V1.23
  dmi.sys.vendor: Packard Bell

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

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

[Kernel-packages] [Bug 1458617] Re: Avoton server occasionally fails to boot when using SSD disks connected using ahci driver

[Rafael David Tinoco]

** Description changed:

+ SRU Justification:
+ 
+ Impact:   Intermittent OS failure due to SSD disk initialisation failure
+ Fix:  Upstream development
+ Testcase: About once per 5000 reboots on one server. 
+   If the user has several hundred servers, 
+   the frequency isn't negligible. 
+ 
+ -
+ 
  It was brought to my attention the following BUG:
  
- Avoton server occasionally fails to boot when using SSD disks 
- connected using ahci driver. When this problem occurs, the disk is 
- not recognized by the Linux kernel, and the server fails to boot. 
+ Avoton server occasionally fails to boot when using SSD disks
+ connected using ahci driver. When this problem occurs, the disk is
+ not recognized by the Linux kernel, and the server fails to boot.
  
  * Upstream acceptance information:
  
- Intel's patch has already been accepted upstream 
- commit dbfe8ef5599a5370abc441fcdbb382b656563eb4 
- Author: Dan Williams dan.j.willi...@intel.com 
- Date: Fri May 8 15:23:55 2015 -0400 
- ahci: avoton port-disable reset-quirk 
+ Intel's patch has already been accepted upstream
+ commit dbfe8ef5599a5370abc441fcdbb382b656563eb4
+ Author: Dan Williams dan.j.willi...@intel.com
+ Date: Fri May 8 15:23:55 2015 -0400
+ ahci: avoton port-disable reset-quirk
  
  Refer to
  http://permalink.gmane.org/gmane.linux.kernel.commits.head/524068
  
- * How reproducible: 
- About once per 5000 reboots on one server. However, if the customer 
- has several hundred servers, the frequency isn't negligible. 
+ * How reproducible:
+ About once per 5000 reboots on one server. However, if the customer
+ has several hundred servers, the frequency isn't negligible.
  
- * Steps to Reproduce: 
+ * Steps to Reproduce:
  Reboot server.

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

Title:
  Avoton server occasionally fails to boot when using SSD disks
  connected using ahci driver

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:

  Impact:   Intermittent OS failure due to SSD disk initialisation failure
  Fix:  Upstream development
  Testcase: About once per 5000 reboots on one server. 
If the user has several hundred servers, 
the frequency isn't negligible. 

  -

  It was brought to my attention the following BUG:

  Avoton server occasionally fails to boot when using SSD disks
  connected using ahci driver. When this problem occurs, the disk is
  not recognized by the Linux kernel, and the server fails to boot.

  * Upstream acceptance information:

  Intel's patch has already been accepted upstream
  commit dbfe8ef5599a5370abc441fcdbb382b656563eb4
  Author: Dan Williams dan.j.willi...@intel.com
  Date: Fri May 8 15:23:55 2015 -0400
  ahci: avoton port-disable reset-quirk

  Refer to
  http://permalink.gmane.org/gmane.linux.kernel.commits.head/524068

  * How reproducible:
  About once per 5000 reboots on one server. However, if the customer
  has several hundred servers, the frequency isn't negligible.

  * Steps to Reproduce:
  Reboot server.

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

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