date:20131212

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

Title:
  ASUS Taichi21 External screen doesn't work.

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This report is another entry for the bug#1205694 described
  here:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205694

  External screen on ASUS Taichi21 ultrabook doesn't show anything. The 
backlight is always off also.
  Both screens are being recognaized by OS, and can be managed, but external 
screen is off, no matter which options are chosen.

  Tested with 3.8 repository kernel, and with 3.13.0-0311300rc3 mainline
  kernel.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-34-generic 3.8.0-34.49
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  soimimozo   1844 F pulseaudio
  Date: Thu Dec 12 17:06:14 2013
  HibernationDevice: RESUME=UUID=76d4fac3-6b56-4dc2-b04b-1590849c4026
  InstallationDate: Installed on 2013-12-09 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. TAICHI21A
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=b0c6a357-cbe3-4ed0-8193-2d90569de03d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-34-generic N/A
   linux-backports-modules-3.8.0-34-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TAICHI21A.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TAICHI21A
  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.:bvrTAICHI21A.203:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnTAICHI21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTAICHI21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TAICHI21A
  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/1260214/+subscriptions

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

[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient

2013-12-12 Thread Daniel Richard G.

Agreed. It's not clear that there is *any* standard Ubuntu kernel
configuration that can boot in 64MB. And having that as a default is
worse than useless, because the crash-kernel's OOM prevents the system
from recovering automatically after a kernel crash.

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

Title:
  Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux
  is insufficient

Status in “grub2” package in Ubuntu:
  Confirmed
Status in “kexec-tools” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: grub-pc

  This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty.

  The /etc/grub.d/10_linux file contains this snippet:

  # add crashkernel option if we have the required tools
  if [ -x /usr/bin/makedumpfile ]  [ -x /sbin/kexec ]; then
  GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA 
crashkernel=384M-2G:64M,2G-:128M
  fi

  I am on a system with 2GB of RAM (reported as 2038MB), and according
  to the kernel startup messages, 64MB is reserved for the crash kernel.

  Unfortunately, this does not appear to be enough memory for the
  regular Ubuntu kernel to boot. I am attaching a kernel log obtained
  via serial cable; it shows the initial boot, a crash in the kernel's
  video-driver-related code, the subsequent crashkernel boot, and then
  an apparent out of memory kernel panic. (A side effect of the
  double crash is that the system is left unresponsive, requiring a
  manual reset instead of rebooting itself automatically.)

  If I double the memory numbers in the crashkernel=... argument, so
  that the reservation is 128MB, the system correctly goes on to attempt
  a vmcore dump and reboot.

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

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

[Kernel-packages] [Bug 1260225] Re: Crackling audio on HP / AMD Hudson machines when changing volume during playback

2013-12-12 Thread David Henningsson

While enabling these machines, we found we would sometimes lose an
interrupt if we change hardware volume during playback, and that
disabling msi fixed this issue. (Losing the interrupt caused underruns
and crackling audio, as the one second timeout is usually bigger than
the period size.)

The machines were all machines from HP, running AMD Hudson controller,
and Realtek ALC282 codec.

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1260225
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/hda_intel.c |4 
 1 file changed, 4 insertions(+)

diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index af86c71..440c355 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -3446,6 +3446,10 @@ static void check_probe_mask(struct azx *chip, int dev)
  * white/black-list for enable_msi
  */
 static struct snd_pci_quirk msi_black_list[] = {
+   SND_PCI_QUIRK(0x103c, 0x2191, HP, 0), /* AMD Hudson */
+   SND_PCI_QUIRK(0x103c, 0x2192, HP, 0), /* AMD Hudson */
+   SND_PCI_QUIRK(0x103c, 0x21f7, HP, 0), /* AMD Hudson */
+   SND_PCI_QUIRK(0x103c, 0x21fa, HP, 0), /* AMD Hudson */
SND_PCI_QUIRK(0x1043, 0x81f2, ASUS, 0), /* Athlon64 X2 + nvidia */
SND_PCI_QUIRK(0x1043, 0x81f6, ASUS, 0), /* nvidia */
SND_PCI_QUIRK(0x1043, 0x822d, ASUS, 0), /* Athlon64 X2 + nvidia MCP55 
*/
-- 
1.7.9.5


** Tags added: blocks-hwcert-enablement

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

Title:
  Crackling audio on HP / AMD Hudson machines when changing volume
  during playback

Status in HWE Next Project:
  New
Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  We discovered that for these machines we would sometimes lose an
  interrupt if we changed volume during playback and that enable_msi=0
  would fix this issue.

  This bug is for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1260230] [NEW] Memory leak in libcrypto.so\libssl.so

2013-12-12 Thread Alexander

Public bug reported:

I've found a bug in openssl 1.0.1-4ubuntu5.10. Was trying to use
libpq\libmysql.so to connect to database and did not specify sslmode so
it used ssl to connect to database, when i've checked with valgrind i've
detected some memory leak:

==25346== Memcheck, a memory error detector
==25346== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==25346== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==25346== Command: ./test
==25346==
==25346==
==25346== HEAP SUMMARY:
==25346== in use at exit: 81,152 bytes in 2,769 blocks
==25346==   total heap usage: 4,388 allocs, 1,619 frees, 281,833 bytes allocated
==25346==
==25346== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 229 of 279
==25346==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==25346==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
==25346==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
==25346==by 0x4EB6168: ???
==25346==by 0x4EB7B5C: ???
==25346==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
==25346==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
==25346==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
==25346==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
==25346==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
==25346==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
==25346==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
==25346==
==25346== LEAK SUMMARY:
==25346==definitely lost: 40 bytes in 1 blocks
==25346==indirectly lost: 120 bytes in 10 blocks
==25346==  possibly lost: 0 bytes in 0 blocks
==25346==still reachable: 80,992 bytes in 2,758 blocks
==25346== suppressed: 0 bytes in 0 blocks
==25346== Reachable blocks (those to which a pointer was found) are not shown.
==25346== To see them, rerun with: --leak-check=full --show-reachable=yes
==25346==
==25346== For counts of detected and suppressed errors, rerun with: -v
==25346== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)


with sslmode=disable i see this:
==28708== Memcheck, a memory error detector
==28708== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==28708== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==28708== Command: ./test
==28708==
==28708==
==28708== HEAP SUMMARY:
==28708== in use at exit: 160 bytes in 11 blocks
==28708==   total heap usage: 138 allocs, 127 frees, 46,314 bytes allocated
==28708==
==28708== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 11 of 11
==28708==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==28708==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
==28708==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
==28708==by 0x4EB6168: ???
==28708==by 0x4EB7B5C: ???
==28708==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
==28708==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
==28708==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
==28708==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
==28708==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
==28708==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
==28708==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
==28708==
==28708== LEAK SUMMARY:
==28708==definitely lost: 40 bytes in 1 blocks
==28708==indirectly lost: 120 bytes in 10 blocks
==28708==  possibly lost: 0 bytes in 0 blocks
==28708==still reachable: 0 bytes in 0 blocks
==28708== suppressed: 0 bytes in 0 blocks
==28708==
==28708== For counts of detected and suppressed errors, rerun with: -v
==28708== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

also test openssl program(attached) have a leak 47700 bytes

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

** Attachment added: Sample program to check connection to site with SSL
   https://bugs.launchpad.net/bugs/1260230/+attachment/3927970/+files/withssl.c

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

Title:
  Memory leak in libcrypto.so\libssl.so

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I've found a bug in openssl 1.0.1-4ubuntu5.10. Was trying to use
  libpq\libmysql.so to connect to database and did not specify sslmode
  so it used ssl to connect to database, when i've checked with valgrind
  i've detected some memory leak:

  ==25346== Memcheck, a memory error detector
  ==25346== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==25346== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==25346== Command: ./test
  ==25346==
  ==25346==
  ==25346== HEAP SUMMARY:
  ==25346== in use at exit: 81,152 bytes in 2,769 blocks
  ==25346==   total heap usage: 4,388

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

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

apport-collect 1260230

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

Title:
  Memory leak in libcrypto.so\libssl.so

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I've found a bug in openssl 1.0.1-4ubuntu5.10. Was trying to use
  libpq\libmysql.so to connect to database and did not specify sslmode
  so it used ssl to connect to database, when i've checked with valgrind
  i've detected some memory leak:

  ==25346== Memcheck, a memory error detector
  ==25346== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==25346== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==25346== Command: ./test
  ==25346==
  ==25346==
  ==25346== HEAP SUMMARY:
  ==25346== in use at exit: 81,152 bytes in 2,769 blocks
  ==25346==   total heap usage: 4,388 allocs, 1,619 frees, 281,833 bytes 
allocated
  ==25346==
  ==25346== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 229 of 279
  ==25346==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==25346==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==25346==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==25346==by 0x4EB6168: ???
  ==25346==by 0x4EB7B5C: ???
  ==25346==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==25346==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==25346==
  ==25346== LEAK SUMMARY:
  ==25346==definitely lost: 40 bytes in 1 blocks
  ==25346==indirectly lost: 120 bytes in 10 blocks
  ==25346==  possibly lost: 0 bytes in 0 blocks
  ==25346==still reachable: 80,992 bytes in 2,758 blocks
  ==25346== suppressed: 0 bytes in 0 blocks
  ==25346== Reachable blocks (those to which a pointer was found) are not shown.
  ==25346== To see them, rerun with: --leak-check=full --show-reachable=yes
  ==25346==
  ==25346== For counts of detected and suppressed errors, rerun with: -v
  ==25346== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)


  with sslmode=disable i see this:
  ==28708== Memcheck, a memory error detector
  ==28708== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==28708== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==28708== Command: ./test
  ==28708==
  ==28708==
  ==28708== HEAP SUMMARY:
  ==28708== in use at exit: 160 bytes in 11 blocks
  ==28708==   total heap usage: 138 allocs, 127 frees, 46,314 bytes allocated
  ==28708==
  ==28708== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 11 of 11
  ==28708==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==28708==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==28708==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==28708==by 0x4EB6168: ???
  ==28708==by 0x4EB7B5C: ???
  ==28708==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==28708==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==28708==
  ==28708== LEAK SUMMARY:
  ==28708==definitely lost: 40 bytes in 1 blocks
  ==28708==indirectly lost: 120 bytes in 10 blocks
  ==28708==  possibly lost: 0 bytes in 0 blocks
  ==28708==still reachable: 0 bytes in 0 blocks
  ==28708== suppressed: 0 bytes in 0 blocks
  ==28708==
  ==28708== For counts of detected and suppressed errors, rerun with: -v
  ==28708== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

  also test openssl program(attached) have a leak 47700 bytes

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

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

[Kernel-packages] [Bug 1235616] Re: linux-crashdump doesn't actually dump and reboot

2013-12-12 Thread Launchpad Bug Tracker

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

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

** Changed in: kexec-tools (Ubuntu)
   Status: New = Confirmed

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

Title:
  linux-crashdump doesn't actually dump and reboot

Status in “kexec-tools” package in Ubuntu:
  Confirmed

Bug description:
  In our infrastructure we have a large number of virtual machines running 
Ubuntu 12.04 (and some that are running 10.04), as well as a couple of CentOS 
machines.
  From time to time they will panic and we'll be left with nothing but a 
screenshot, which makes for poor debugging. I pushed forward to install 
linux-crashdump (or crash on CentOS) by default.
  Following this documentation on how to enable crash dumps: 
https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html I've done the 
testing myself, on both libvirt/qemu, virtualbox, but also on actual hardware 
(my laptop, which is the yet unreleased running Ubuntu 13.04).

  The results have been rather sobering. After initiating a panic, the machines 
shows a back-trace and then just hangs. As the documentation says that the 
crash-dump can take some time, I've left the machines for several hours in this 
state with no change.
  I've followed several cues, documenting my journey in this ask.ubuntu answer: 
http://askubuntu.com/questions/310885/kernel-dump-using-linux-crashdump-under-vmware
 — The testing on my own laptop has led to seeing the first bluescreen in over 
ten years: http://i.imgur.com/oAwEJZ8.jpg

  My final tests were with CentOS, since we only have a handful of machines 
running CentOS I put a lower priority on testing/implementing that. However, 
following RHEL's documentation ( 
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-kdump.html
 ) I managed to get crash/dump/reboot and crashdump on the very first try.
  By this token I'm assuming it's not entirely my fault or my systems' fault, 
but perhaps is more specific to Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1235616/+subscriptions

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

[Kernel-packages] [Bug 1260230] Re: Memory leak in libcrypto.so\libssl.so

2013-12-12 Thread Alexander

I can't run apport-collect from cli

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

Title:
  Memory leak in libcrypto.so\libssl.so

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I've found a bug in openssl 1.0.1-4ubuntu5.10. Was trying to use
  libpq\libmysql.so to connect to database and did not specify sslmode
  so it used ssl to connect to database, when i've checked with valgrind
  i've detected some memory leak:

  ==25346== Memcheck, a memory error detector
  ==25346== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==25346== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==25346== Command: ./test
  ==25346==
  ==25346==
  ==25346== HEAP SUMMARY:
  ==25346== in use at exit: 81,152 bytes in 2,769 blocks
  ==25346==   total heap usage: 4,388 allocs, 1,619 frees, 281,833 bytes 
allocated
  ==25346==
  ==25346== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 229 of 279
  ==25346==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==25346==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==25346==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==25346==by 0x4EB6168: ???
  ==25346==by 0x4EB7B5C: ???
  ==25346==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==25346==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==25346==
  ==25346== LEAK SUMMARY:
  ==25346==definitely lost: 40 bytes in 1 blocks
  ==25346==indirectly lost: 120 bytes in 10 blocks
  ==25346==  possibly lost: 0 bytes in 0 blocks
  ==25346==still reachable: 80,992 bytes in 2,758 blocks
  ==25346== suppressed: 0 bytes in 0 blocks
  ==25346== Reachable blocks (those to which a pointer was found) are not shown.
  ==25346== To see them, rerun with: --leak-check=full --show-reachable=yes
  ==25346==
  ==25346== For counts of detected and suppressed errors, rerun with: -v
  ==25346== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)


  with sslmode=disable i see this:
  ==28708== Memcheck, a memory error detector
  ==28708== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==28708== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==28708== Command: ./test
  ==28708==
  ==28708==
  ==28708== HEAP SUMMARY:
  ==28708== in use at exit: 160 bytes in 11 blocks
  ==28708==   total heap usage: 138 allocs, 127 frees, 46,314 bytes allocated
  ==28708==
  ==28708== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 11 of 11
  ==28708==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==28708==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==28708==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==28708==by 0x4EB6168: ???
  ==28708==by 0x4EB7B5C: ???
  ==28708==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==28708==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==28708==
  ==28708== LEAK SUMMARY:
  ==28708==definitely lost: 40 bytes in 1 blocks
  ==28708==indirectly lost: 120 bytes in 10 blocks
  ==28708==  possibly lost: 0 bytes in 0 blocks
  ==28708==still reachable: 0 bytes in 0 blocks
  ==28708== suppressed: 0 bytes in 0 blocks
  ==28708==
  ==28708== For counts of detected and suppressed errors, rerun with: -v
  ==28708== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

  also test openssl program(attached) have a leak 47700 bytes

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

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

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

This change was made by a bot.

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

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

Title:
  package linux-image-3.5.0-45-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Hit http://mirror.mirohost.net quantal-backports/multiverse Sources   
 
  Hit http://mirror.mirohost.net quantal-backports/main i386 Packages   
 
  Hit http://mirror.mirohost.net quantal-backports/restricted i386 Packages 
 
  Hit http://ua.archive.ubuntu.com precise-updates/restricted Translation-en
 
  Ign http://ua.archive.ubuntu.com precise-updates/main Translation-en_US   
 
  Get:29 http://ppa.launchpad.net quantal/main i386 Packages [9,654 B]  
 
  Ign http://ua.archive.ubuntu.com precise-updates/restricted Translation-en_US 
 
  Hit http://mirror.mirohost.net quantal-backports/universe i386 Packages   
 
  Hit http://mirror.mirohost.net quantal-backports/multiverse i386 Packages 
 
  Hit http://mirror.mirohost.net quantal-backports/main Translation-en  
 
  Hit http://mirror.mirohost.net quantal-backports/multiverse Translation-en
 
  Hit http://mirror.mirohost.net quantal-backports/restricted Translation-en
 
  Hit http://mirror.mirohost.net quantal-backports/universe Translation-en  
 
  Get:30 http://mirror.mirohost.net quantal-security/restricted Sources [1,833 
B]
  Get:31 http://mirror.mirohost.net quantal-security/main Sources [64.5 kB] 
 
  Ign http://extras.ubuntu.com quantal/main Translation-en_US   
 
  Ign http://archive.canonical.com quantal/partner Translation-en_US
 
  Ign http://archive.canonical.com quantal/partner Translation-en   
 
  Ign http://extras.ubuntu.com quantal/main Translation-en  
 
  Get:32 http://mirror.mirohost.net quantal-security/multiverse Sources [1,167 
B]
  Get:33 http://mirror.mirohost.net quantal-security/universe Sources [22.0 kB] 
 
  Get:34 http://mirror.mirohost.net quantal-security/main i386 Packages [184 
kB] 
  Get:35 http://mirror.mirohost.net quantal-security/restricted i386 Packages 
[3,531 B]
  Get:36 http://mirror.mirohost.net quantal-security/universe i386 Packages 
[65.1 kB]
  Get:37 http://mirror.mirohost.net quantal-security/multiverse i386 Packages 
[1,718 B]
  Hit http://mirror.mirohost.net quantal-security/main Translation-en   
 
  Hit http://mirror.mirohost.net quantal-security/multiverse Translation-en 
 
  Hit http://mirror.mirohost.net quantal-security/restricted Translation-en 
 
  Hit http://mirror.mirohost.net quantal-security/universe Translation-en   
 
  Get:38 http://mirror.mirohost.net quantal-proposed/restricted Sources [14 B]  
 
  Get:39 http://mirror.mirohost.net quantal-proposed/main Sources [13.7 kB] 
 
  Get:40 http://mirror.mirohost.net quantal-proposed/multiverse Sources [14 B]  
 
  Get:41 http://mirror.mirohost.net quantal-proposed/universe Sources [4,546 B] 
 
  Get:42 http://mirror.mirohost.net quantal-proposed/restricted i386 Packages 
[14 B]
  Get:43 http://mirror.mirohost.net quantal-proposed/main i386 Packages [47.9 
kB]
  Get:44 http://security.ubuntu.com precise-security/restricted i386 Packages 
[4,620 B]
  Get:45 http://mirror.mirohost.net quantal-proposed/multiverse i386 Packages 
[14 B]
  Get:46 http://mirror.mirohost.net quantal-proposed/universe i386 Packages 
[12.8 kB]
  Hit http://mirror.mirohost.net quantal-proposed/main Translation-en   
 
  Hit http://mirror.mirohost.net quantal-proposed/multiverse Translation-en 
 
  Hit http://mirror.mirohost.net quantal-proposed/restricted Translation-en 
 
  Hit http://mirror.mirohost.net quantal-proposed/universe Translation-en   
 
  Hit http://security.ubuntu.com precise-security/main Translation-en   
 
  Ign http://mirror.mirohost.net quantal/main Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal/multiverse Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal/restricted Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal/universe Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal-updates/main Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal-updates/multiverse Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal-updates/restricted Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal-updates/universe Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal-backports/main Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal-backports/multiverse Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal-backports/restricted Translation-en_US

[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

2013-12-12 Thread thomas955

Hi Joseph,
 
not working for me :-(
Linux production01 3.6.0-030600rc6-generic #201312111606 SMP Wed Dec 11 
21:09:39 UTC 2013 x86_64 GNU/Linux

dmesg | grep ixgbe
[1.997512] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 
3.9.15-k
[1.997515] ixgbe: Copyright (c) 1999-2012 Intel Corporation.
[1.997700] ixgbe: probe of :22:00.0 failed with error -5
[1.997815] ixgbe: probe of :22:00.1 failed with error -5

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

Title:
  Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

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

Bug description:
  We have a server (Dell R715) with two Intel x520 NIC's. If we run
  Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel
  driver or with Intel compiled one), but if we upgrade release to
  12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel
  drivers fails with error:

  [  226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7
  [  226.395770] Copyright (c) 1999-2013 Intel Corporation.
  [  226.395980] ixgbe: probe of :22:00.0 failed with error -5
  [  226.396092] ixgbe: probe of :22:00.1 failed with error -5
  [  226.396203] ixgbe: probe of :23:00.0 failed with error -5
  [  226.396311] ixgbe: probe of :23:00.1 failed with error -5

  I contacted Intel developers and they responded:

  Hey Fernando,
  We (ixgbe) only returns EIO (error 5) for a couple of reasons.
   1) When we fail to io map (ioremap)
   2) If the eeprom checksum is incorrect.
   3) If the MAC address from the checksum is invalid

  Reasons 2 and 3 are related to the NIC's eeprom so if they worked with 
another system they should still be fine now.  If you really wanted to verify 
you could try out the NIC's on a known good system again to see if the eeprom 
somehow got corrupted.
  That pretty much leaves us with ioremap returning an error.  I'm not at all 
sure why your Ubuntu release would not like the way we are calling ioremap, but 
it might give you a place to start looking in Ubuntu changes.
  Thanks,
  -Don

  If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's
  works fine.

  Please let me know how can I help!

  Regards

  Fernando

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

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

[Kernel-packages] [Bug 1107150] Re: B75 Chipset I/O Problems

2013-12-12 Thread Stijn Volckaert

This kernel has some other problems. it doesn't seem to contain the
graphics driver for my card and I can't reboot. However, over ssh I get:

stijn@rogue:~$ dd if=/dev/zero of=/home/stijn/test bs=1M count=1k
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 6.3337 s, 170 MB/s

This is most definitely fixed. Care to upload the source .deb file as
well?

Thanks

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

Title:
  B75 Chipset I/O Problems

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I built a new system and installed Ubuntu 12.10. The system has the
  following specifications:

  Samsung 840 Pro 128 GB 
  Gigabyte P75-D3
  Intel i7 3770
  32 GB Ram
  Western Digital 1 TB Black (mounted as /home)
  Western Digital 3 TB Green (mounted as /media/data_drive)

  The initial Ubuntu 12.10 install took almost 6 hours as transfer rates
  were very slow. After reboot everything appeared very fast. However
  when I did an apt-get update the download took 20 seconds and the
  processing of lists took 19 minutes.

  I had 12.10 installed on another computer which was working great
  (older Althon system) so I installed the drive and tested the new
  machine. It suffered the same performance problems.

  I installed Windows 7 and performed speeds tests, it reported great
  results.

  I installed 12.04 onto the 1 TB drive and it did not suffer the same
  performance problems. Everything ran great.

  I then upgraded 12.10 to 13.04 (January 27, 2013) and it too suffered
  from the performance issue.

  It appears that a change between 12.04 to 12.10 impacts AHCI based
  systems specifically running the Intel B75 chipset. I am not certain
  but I think that either the motherboard is misrepresenting something
  (that 12.04 ignores but it impacts 12.10) or the kernel is not
  detecting the system correctly.

  I created a couple of pastebins with data collected:

  12.10 Install: http://pastebin.ubuntu.com/1561660/
  12.04 Live Disk (was checked against installed version and data is mostly the 
same): http://paste.ubuntu.com/1565140/

  I have a thread on the ubuntu forums that may provide additional
  details: http://ubuntuforums.org/showthread.php?t=2104709

  I also started an e-mail thread to the ubuntu-users mailing list:
  http://ubuntu.5.n6.nabble.com/Seeking-Help-td5010422.html

  I have done a lot of troubleshooting and I feel that the problem must
  either be the kernel or the bios misrepresenting information. In
  either case I am stuck without any idea of where to go next with the
  debuging and diagnoses path.

  If any additional information needs to be collected, please let me know and I 
will work to assist.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bakers 1729 F pulseaudio
   /dev/snd/controlC0:  bakers 1729 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf711 irq 45'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,1458a002,00100302'
 Controls  : 39
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,14583553,00100100'
 Controls  : 18
 Simple ctrls  : 3
  DistroRelease: Ubuntu 12.04
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic-pae 
root=UUID=4f30252c-fa56-4d53-be78-117cddab55f4 ro quiet splash
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-36-generic-pae N/A
   linux-backports-modules-3.2.0-36-generic-pae  N/A
   linux-firmware1.79.1
  RfKill:
   
  StagingDrivers: mei
  Tags:  precise running-unity staging
  Uname: Linux 3.2.0-36-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P75-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3

[Kernel-packages] [Bug 1107150] Re: B75 Chipset I/O Problems

2013-12-12 Thread Stijn Volckaert

I reverted that same commit in my own kernel source and the problem is
back. This wasn't the root cause.

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

Title:
  B75 Chipset I/O Problems

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I built a new system and installed Ubuntu 12.10. The system has the
  following specifications:

  Samsung 840 Pro 128 GB 
  Gigabyte P75-D3
  Intel i7 3770
  32 GB Ram
  Western Digital 1 TB Black (mounted as /home)
  Western Digital 3 TB Green (mounted as /media/data_drive)

  The initial Ubuntu 12.10 install took almost 6 hours as transfer rates
  were very slow. After reboot everything appeared very fast. However
  when I did an apt-get update the download took 20 seconds and the
  processing of lists took 19 minutes.

  I had 12.10 installed on another computer which was working great
  (older Althon system) so I installed the drive and tested the new
  machine. It suffered the same performance problems.

  I installed Windows 7 and performed speeds tests, it reported great
  results.

  I installed 12.04 onto the 1 TB drive and it did not suffer the same
  performance problems. Everything ran great.

  I then upgraded 12.10 to 13.04 (January 27, 2013) and it too suffered
  from the performance issue.

  It appears that a change between 12.04 to 12.10 impacts AHCI based
  systems specifically running the Intel B75 chipset. I am not certain
  but I think that either the motherboard is misrepresenting something
  (that 12.04 ignores but it impacts 12.10) or the kernel is not
  detecting the system correctly.

  I created a couple of pastebins with data collected:

  12.10 Install: http://pastebin.ubuntu.com/1561660/
  12.04 Live Disk (was checked against installed version and data is mostly the 
same): http://paste.ubuntu.com/1565140/

  I have a thread on the ubuntu forums that may provide additional
  details: http://ubuntuforums.org/showthread.php?t=2104709

  I also started an e-mail thread to the ubuntu-users mailing list:
  http://ubuntu.5.n6.nabble.com/Seeking-Help-td5010422.html

  I have done a lot of troubleshooting and I feel that the problem must
  either be the kernel or the bios misrepresenting information. In
  either case I am stuck without any idea of where to go next with the
  debuging and diagnoses path.

  If any additional information needs to be collected, please let me know and I 
will work to assist.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bakers 1729 F pulseaudio
   /dev/snd/controlC0:  bakers 1729 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf711 irq 45'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,1458a002,00100302'
 Controls  : 39
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,14583553,00100100'
 Controls  : 18
 Simple ctrls  : 3
  DistroRelease: Ubuntu 12.04
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic-pae 
root=UUID=4f30252c-fa56-4d53-be78-117cddab55f4 ro quiet splash
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-36-generic-pae N/A
   linux-backports-modules-3.2.0-36-generic-pae  N/A
   linux-firmware1.79.1
  RfKill:
   
  StagingDrivers: mei
  Tags:  precise running-unity staging
  Uname: Linux 3.2.0-36-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P75-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Kernel-packages] [Bug 1259437] Re: No external mic can be detected on the machines with codec (Subsystem Id: 0x10280628)

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

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

Title:
  No external mic can be detected on the machines with codec (Subsystem
  Id: 0x10280628)

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  In Progress
Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  1. plug in a 3-ring headset
  2. go to sound settings  input tab
  3. check if external mic is detected

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

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

[Kernel-packages] [Bug 1260303] [NEW] No external microphone detected on the machines with codec Subsystem ID0x10280610

Public bug reported:

Steps:
1.  boot into OS
2. Plugin a 3-ring headset into the headset port
3. Go to sound setting  input tab and check if external mic is detected
4. Launch sound recorder and try to record sound from external mic

** Affects: hwe-next
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: Triaged

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: Triaged


** Tags: blocks-hwcert-enablement

** Tags added: blocks-hwcert-enablement

** Changed in: hwe-next
   Status: New = Triaged

** Changed in: hwe-next
   Importance: Undecided = High

** Changed in: hwe-next
 Assignee: (unassigned) = Hui Wang (hui.wang)

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

Title:
  No external microphone detected on the machines with codec Subsystem
  ID0x10280610

Status in HWE Next Project:
  Triaged
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Steps:
  1.  boot into OS
  2. Plugin a 3-ring headset into the headset port
  3. Go to sound setting  input tab and check if external mic is detected
  4. Launch sound recorder and try to record sound from external mic

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

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

[Kernel-packages] [Bug 1064236] Re: [SAMSUNG NP700Z5A-S01RU] suspend/resume failure [non-free: wl]

Mikhail S. Pobolovets, would you need a backport to a release prior to
Trusty, or may this be closed as 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/1064236

Title:
  [SAMSUNG NP700Z5A-S01RU] suspend/resume failure [non-free: wl]

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  [SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B]
  suspend/resume failure [non-free: wl]

  ProblemType: KernelOops
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.27
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  styx   1766 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct  9 08:48:20 2012
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac 
(20111012)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=3a529063-69ed-4dc0-bb94-d6a61dbc4b26 ro acpi_brightness=vendor 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.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.94
  SourcePackage: linux
  Title: [SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B] 
suspend/resume failure [non-free: wl]
  UpgradeStatus: Upgraded to quantal on 2012-10-02 (6 days ago)
  UserGroups:
   
  dmi.bios.date: 10/28/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 08FD
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr08FD:bd10/28/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3A/700Z4A/700Z5A/700Z5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn700Z3A/700Z4A/700Z5A/700Z5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1260306] [NEW] No external microphone detected on the machines with codec Subsystem ID0x1028063e

Public bug reported:

Steps:
1. boot into OS
2. Plugin a 3-ring headset into the headset port
3. Go to sound setting  input tab and check if external mic is detected
4. Launch sound recorder and try to record sound from external mic

** Affects: hwe-next
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: Triaged

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: Triaged


** Tags: blocks-hwcert-enablement

** Tags added: blocks-hwcert-enablement

** Changed in: hwe-next
   Status: New = Triaged

** Changed in: hwe-next
   Importance: Undecided = High

** Changed in: hwe-next
 Assignee: (unassigned) = Hui Wang (hui.wang)

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

Title:
  No external microphone detected on the machines with codec Subsystem
  ID0x1028063e

Status in HWE Next Project:
  Triaged
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Steps:
  1. boot into OS
  2. Plugin a 3-ring headset into the headset port
  3. Go to sound setting  input tab and check if external mic is detected
  4. Launch sound recorder and try to record sound from external mic

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

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

[Kernel-packages] [Bug 1260313] [NEW] No external microphone detected on the machines with codec Subsystem ID0x10280629

Public bug reported:

Steps:
1. boot into OS
2. Plugin a 3-ring headset into the headset port
3. Go to sound setting  input tab and check if external mic is detected
4. Launch sound recorder and try to record sound from external mic

** Affects: hwe-next
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: Triaged

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: Triaged


** Tags: blocks-hwcert-enablement

** Tags added: blocks-hwcert-enablement

** Changed in: hwe-next
   Status: New = Triaged

** Changed in: hwe-next
   Importance: Undecided = High

** Changed in: hwe-next
 Assignee: (unassigned) = Hui Wang (hui.wang)

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

Title:
  No external microphone detected on the machines with codec Subsystem
  ID0x10280629

Status in HWE Next Project:
  Triaged
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Steps:
  1. boot into OS
  2. Plugin a 3-ring headset into the headset port
  3. Go to sound setting  input tab and check if external mic is detected
  4. Launch sound recorder and try to record sound from external mic

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

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

[Kernel-packages] [Bug 1252945] Re: [HP Pavilion 15-e010ax Notebook PC] Unable to install Saucy

brianM, given the following information tested true:
git bisect bad e748a38596932af8632448f35e8b2bba714ae03d
git bisect good fffbdda4eee69f99b8c798d8eaca91c7e0513f08
Bisecting: 7223 revisions left to test after this (roughly 13 steps)

it would help immensely if the gap between the two commits could be
reduced as far as possible.

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

Title:
  [HP Pavilion 15-e010ax Notebook PC] Unable to install Saucy

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Tried to install U13.10 using the desktop installer on HP 15e010ax
  laptop. Goes thru splash screen to freeze with a black screen with no
  cursor. Unable to access terminal. Was using uefi boot with secure
  boot disabled. This is a regression as U13.04 works on this machine
  and has been used to gather the debug info attached due no terminal
  access in 13.10. This occurs when trying to boot to live session or
  straight to install. Appears installer cannot set up a satisfactory
  default video driver for this machine. Note VESA: KALINDI works on
  13.04 and probably should in 13.10.

  WORKAROUND: I installed saucy in this machine by a partition copy from
  another working pc. Found that a recovery boot works and installs
  video driver vesa:kalindi. Also installing fglrx works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-33-generic 3.8.0-33.48
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brian  1918 F pulseaudio
   /dev/snd/controlC0:  brian  1918 F pulseaudio
  CRDA:
   country AU:
    (2402 - 2482 @ 40), (N/A, 20)
    (5170 - 5250 @ 40), (3, 23)
    (5250 - 5330 @ 40), (3, 23), DFS
    (5735 - 5835 @ 40), (3, 30)
  Date: Wed Nov 20 14:35:58 2013
  HibernationDevice: RESUME=UUID=5aed68e6-feb5-4218-8672-ac3a1790bbbe
  InstallationDate: Installed on 2013-11-18 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  MarkForUpload: True
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic 
root=UUID=560ad8b8-e23f-4108-a24c-7e2bed8a81a6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-33-generic N/A
   linux-backports-modules-3.8.0-33-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 213A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 02.12
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/27/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr088410305A1620100:rvnHewlett-Packard:rn213A:rvr02.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 088410305A1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1260214] Re: ASUS Taichi21 External screen doesn't work.

SOIMiMozO, could you please test the latest upstream kernel available (not the 
daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will 
allow additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.13-rc2

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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-203 needs-upstream-testing regression-
potential

** Summary changed:

- ASUS Taichi21 External screen doesn't work.
+ [ASUS TAICHI 21] External screen doesn't work.

** Description changed:

- This report is another entry for the bug#1205694 described
- here:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205694
- 
- External screen on ASUS Taichi21 ultrabook doesn't show anything. The 
backlight is always off also.
- Both screens are being recognaized by OS, and can be managed, but external 
screen is off, no matter which options are chosen.
- 
- Tested with 3.8 repository kernel, and with 3.13.0-0311300rc3 mainline
- kernel.
- 
+ External screen on ASUS Taichi21 ultrabook doesn't show anything. The
+ backlight is always off also. Both screens are being recognized by OS,
+ and can be managed, but external screen is off, no matter which options
+ are chosen. Tested with 3.8 repository kernel, and with
+ 3.13.0-0311300rc3 mainline kernel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-34-generic 3.8.0-34.49
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  soimimozo   1844 F pulseaudio
  Date: Thu Dec 12 17:06:14 2013
  HibernationDevice: RESUME=UUID=76d4fac3-6b56-4dc2-b04b-1590849c4026
  InstallationDate: Installed on 2013-12-09 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. TAICHI21A
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=b0c6a357-cbe3-4ed0-8193-2d90569de03d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-34-generic N/A
   linux-backports-modules-3.8.0-34-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TAICHI21A.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TAICHI21A
  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.:bvrTAICHI21A.203:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnTAICHI21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTAICHI21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TAICHI21A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Summary changed:

- [ASUS TAICHI 21] External screen doesn't work.
+ 8086:0166 [ASUS TAICHI 21] External screen doesn't work.

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

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

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

Title:
  8086:0166 [ASUS TAICHI 21] External screen doesn't work.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  External screen on ASUS Taichi21 ultrabook doesn't show anything. The
  backlight is always off also. Both screens are being recognized by OS,
  and can be managed, but external screen is off, no matter which
  options are chosen. Tested with 3.8 repository kernel, and with
  3.13.0-0311300rc3 mainline kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-34-generic 3.8.0-34.49
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64

[Kernel-packages] [Bug 1062796] Re: 05e3:070e usb-storage devices don't work, unless plugged in after booting - happens when setting MODULES=dep in initramfs.conf

** Tags removed: bios-outdated-1204
** Tags added: bios-outdated-1301

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

Title:
  05e3:070e usb-storage devices don't work, unless plugged in *after*
  booting - happens when setting MODULES=dep in initramfs.conf

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Hopefully I have time to root-cause this.

  We have two Kubuntu 12.04 LTS machines.  One of them has a USB card
  reader, which we want to leave permanently attached.  We use it to
  upload photos to Digikam several times a month.

  Recently we noticed the card reader not working.  It showed up in
  lsusb, BUT ls /dev/sd* showed only one device (the internal hard
  drive).

  WORKAROUND: Unplugging the entire card reader and plugging it back in
  again fixes it.

  WORKAROUND: The following fixed it without re-plugging the cardreader:
  modprobe usb-storage

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-31-generic 3.2.0-31.50
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: VT1708S Analog [VT1708S Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   2413 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c1 irq 46'
     Mixer name : 'Intel PantherPoint HDMI'
     Components : 'HDA:11060397,10438415,0010 
HDA:80862806,80860101,0010'
     Controls  : 48
     Simple ctrls  : 23
  Date: Sat Oct  6 12:27:35 2012
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic 
root=UUID=a6efc5b5-c8c5-4ae1-9970-61943a7f9396 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-31-generic N/A
   linux-backports-modules-3.2.0-31-generic  N/A
   linux-firmware1.79.1
  RfKill:

  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B75-M LE
  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.:bvr0703:bd08/24/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-MLE: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/1062796/+subscriptions

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

[Kernel-packages] [Bug 1062796] Re: usb-storage devices don't work, unless plugged in after booting - happens when setting MODULES=dep in initramfs.conf

** Description changed:

  Hopefully I have time to root-cause this.
  
  We have two Kubuntu 12.04 LTS machines.  One of them has a USB card
  reader, which we want to leave permanently attached.  We use it to
  upload photos to Digikam several times a month.
  
  Recently we noticed the card reader not working.  It showed up in lsusb,
  BUT ls /dev/sd* showed only one device (the internal hard drive).
- Unplugging the entire card reader and plugging it back in again fixes
- it.
  
- Today, I confirmed that modprobe usb-storage fixed it without re-
- plugging the cardreader.
+ WORKAROUND: Unplugging the entire card reader and plugging it back in
+ again fixes it.
+ 
+ WORKAROUND: The following fixed it without re-plugging the cardreader:
+ modprobe usb-storage
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-31-generic 3.2.0-31.50
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
-   List of CAPTURE Hardware Devices 
-  card 0: PCH [HDA Intel PCH], device 0: VT1708S Analog [VT1708S Analog]
-Subdevices: 2/2
-Subdevice #0: subdevice #0
-Subdevice #1: subdevice #1
+   List of CAPTURE Hardware Devices 
+  card 0: PCH [HDA Intel PCH], device 0: VT1708S Analog [VT1708S Analog]
+    Subdevices: 2/2
+    Subdevice #0: subdevice #0
+    Subdevice #1: subdevice #1
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  alan   2413 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  alan   2413 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
-  Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c1 irq 46'
-Mixer name : 'Intel PantherPoint HDMI'
-Components : 'HDA:11060397,10438415,0010 
HDA:80862806,80860101,0010'
-Controls  : 48
-Simple ctrls  : 23
+  Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c1 irq 46'
+    Mixer name : 'Intel PantherPoint HDMI'
+    Components : 'HDA:11060397,10438415,0010 
HDA:80862806,80860101,0010'
+    Controls  : 48
+    Simple ctrls  : 23
  Date: Sat Oct  6 12:27:35 2012
  IwConfig:
-  lono wireless extensions.
-  
-  eth0  no wireless extensions.
+  lono wireless extensions.
+ 
+  eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  TERM=xterm
-  PATH=(custom, user)
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  TERM=xterm
+  PATH=(custom, user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic 
root=UUID=a6efc5b5-c8c5-4ae1-9970-61943a7f9396 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.2.0-31-generic N/A
-  linux-backports-modules-3.2.0-31-generic  N/A
-  linux-firmware1.79.1
+  linux-restricted-modules-3.2.0-31-generic N/A
+  linux-backports-modules-3.2.0-31-generic  N/A
+  linux-firmware1.79.1
  RfKill:
-  
+ 
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B75-M LE
  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.:bvr0703:bd08/24/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

** Summary changed:

- usb-storage devices don't work, unless plugged in *after* booting - happens 
when setting MODULES=dep in initramfs.conf
+ 05e3:070e usb-storage devices don't work, unless plugged in *after* booting - 
happens when setting MODULES=dep in initramfs.conf

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

Title:
  05e3:070e usb-storage devices don't work, unless plugged in *after*
  booting - happens when setting MODULES=dep in initramfs.conf

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Hopefully I have time to root-cause this.

  We have two Kubuntu 12.04 LTS machines.  One of them has a USB card
  reader, which we want to leave permanently attached.  We use it to
  upload photos to Digikam several times a month.

  Recently

[Kernel-packages] [Bug 1260330] [NEW] linux: 3.12.0-8.16 -proposed tracker

2013-12-12 Thread Tim Gardner

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Thursday, 12. December 2013 13:50 UTC
kernel-phase-changed:Thursday, 12. December 2013 13:50 UTC
kernel-phase:Prepare

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

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

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

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

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

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

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

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


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

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

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

** Tags added: trusty

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux: 3.12.0-8.16 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 12. December 2013 13:50 UTC
  kernel-phase-changed:Thursday, 12. December 2013 13:50 UTC
  kernel-phase:Prepare

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

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

[Kernel-packages] [Bug 1259570] Re: kexec should get a disabling sysctl

2013-12-12 Thread Mark Russell

More discussion (thanks to Louis Bouchard for link):
http://lists.infradead.org/pipermail/kexec/2013-December/010571.html

Patch v3:
http://lists.infradead.org/pipermail/kexec/2013-December/010606.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/1259570

Title:
  kexec should get a disabling sysctl

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

Bug description:
  To enable kexec makes sense for a generic distro kernel. But if your
  users have root in their virtual machines, and you want to make it
  hard for them to run code in ring 0, you commonly disable further
  module loading and you also want to disable kexec[1]. Kees Cook wrote
  up a patch[2] that we'd like to see applied to the Ubuntu kernel to
  avoid recompilation of the distro kernel.

  I'm marking this as a security issue on the ground that it's quite
  surprising that setting kernel.modules_disabled=1 as a hardening
  feature can be subverted by using kexec.

  [1] http://mjg59.dreamwidth.org/28746.html
  [2] https://lkml.org/lkml/2013/12/9/765

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

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

[Kernel-packages] [Bug 1057532] Re: Monitor goes black (no signal) after Grub, comes back to life when X starts

** Tags added: needs-kernel-logs needs-upstream-testing

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

Title:
  Monitor goes black (no signal) after Grub, comes back to life when X
  starts

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After selecting an entry from the Grub menu and booting starts, the screen 
goes blank, and the monitor displays no signal. When booting ends and X 
starts up, the screen comes back to life, and the LightDM login screen appears.
  I'm using a Radeon HD 6850 with the opensource driver.

  Kernel version: 3.5.0-15.23-generic 3.5.4

  This is a regression, as the issue wasn't present with an earlier 3.5 kernel.
  When I updated recently, I updated to kernel version 15.22, which exposed the 
issue. Updating to a newer version (.23) did nothing to fix the issue.

  Update: Installing the kernels did not fix the issue either:
  3.5.0-16.24, 3.5.0-16.25

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-13-generic 3.5.0-13.14
    3.5.0-14.15, 16, 17, 18, 19
    3.5.0-15.20, 21, 22, 23, 24
    3.5.0-16.25
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Thu Sep 27 15:25:08 2012
  InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20120913)
  ProcFB: 0 radeondrmfb
  SourcePackage: linux

  Update: Apparently the Ubuntu kernels can't handle the vt.handoff=7 option 
properly, which causes the black screen.
  See my comment below for how to fix it:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1057532/comments/38

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

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

[Kernel-packages] [Bug 1057532] Re: Monitor goes black (no signal) after Grub, comes back to life when X starts

Baokai Lei, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications-Accessories-Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux replace-with-bug-number

Also, could you please test the latest upstream kernel available (not the daily 
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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.

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

Title:
  Monitor goes black (no signal) after Grub, comes back to life when X
  starts

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After selecting an entry from the Grub menu and booting starts, the screen 
goes blank, and the monitor displays no signal. When booting ends and X 
starts up, the screen comes back to life, and the LightDM login screen appears.
  I'm using a Radeon HD 6850 with the opensource driver.

  Kernel version: 3.5.0-15.23-generic 3.5.4

  This is a regression, as the issue wasn't present with an earlier 3.5 kernel.
  When I updated recently, I updated to kernel version 15.22, which exposed the 
issue. Updating to a newer version (.23) did nothing to fix the issue.

  Update: Installing the kernels did not fix the issue either:
  3.5.0-16.24, 3.5.0-16.25

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-13-generic 3.5.0-13.14
    3.5.0-14.15, 16, 17, 18, 19
    3.5.0-15.20, 21, 22, 23, 24
    3.5.0-16.25
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Thu Sep 27 15:25:08 2012
  InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20120913)
  ProcFB: 0 radeondrmfb
  SourcePackage: linux

  Update: Apparently the Ubuntu kernels can't handle the vt.handoff=7 option 
properly, which causes the black screen.
  See my comment below for how to fix it:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1057532/comments/38

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

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

[Kernel-packages] [Bug 1259259] Re: linux: 3.11.0-15.23 -proposed tracker

2013-12-12 Thread Parameswaran Sivatharman

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Platform QA Team (canonical-platform-qa) = 
Parameswaran Sivatharman (psivaa)

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

Title:
  linux: 3.11.0-15.23 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.11.0-15.23 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:Monday, 09. December 2013 17:42 UTC
  kernel-stable-Prepare-package-end:Tuesday, 10. December 2013 01:11 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 10. December 2013 01:11 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 10. December 2013 04:04 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 10. December 2013 16:04 UTC
  kernel-stable-Verification-testing-start:Tuesday, 10. December 2013 16:04 UTC
  kernel-stable-Certification-testing-start:Tuesday, 10. December 2013 16:04 UTC
  kernel-stable-Security-signoff-start:Tuesday, 10. December 2013 16:04 UTC
  kernel-stable-Regression-testing-start:Tuesday, 10. December 2013 16:04 UTC
  kernel-stable-Certification-testing-end:Wednesday, 11. December 2013 16:04 UTC

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

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

[Kernel-packages] [Bug 1258631] Re: instances fails to register GPT partition entries on virtio devices

2013-12-12 Thread Stefan Bader

Oh dear, the answer is so simple after one finally realizes what is
going on... The problem here is that the virtio_blk driver has not been
changed to support more than 15 partitions per device. The partition
scanning is looking at the GPT partition table but only at the first 15
elements. Since the other two partitions are 127 and 128, they never get
added if the device is a virtio disk.

So this isn't exactly a bug but a limitation in virtio right now. I am
not sure whether the images could use number 14 and 15 for those two
partitions. Then they should be visible for emulated and virtual
devices... Otherwise this would be some development work which one had
to discuss upstream.

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

Title:
  instances fails to register GPT partition entries on virtio devices

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  When booting via KVM and using the VirtIO interface, GPT partition
  entries are not shown properly.

  ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print
  Model: Virtio Block Device (virtblk)
  Disk /dev/vda: 10.7GB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt

  Number  Start   EndSize File system Name  
Flags
  127 1049kB  2097kB  1049kB   BIOS boot partition  
bios_grub
  128 2097kB  89.1MB  87.0MB  fat32   EFI System
  boot
  1  89.1MB  10.7GB  10.6GB   ext4 Linux filesystem

  Booting with -hda disk.img
  [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5
  [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [2.644685]  sda: sda1 sda127 sda128
  [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk

  Booting with -drive if=virtio,file=disk.img or -drive 
if=scsi,file=disk.img:
  [2.411933] brd: module loaded
  [2.422616] loop: module loaded
  [2.442178]  vda: vda1
  [2.49] scsi0 : ata_piix
  [2.456868] scsi1 : ata_piix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Fri Dec  6 18:49:57 2013
  Ec2AMI: ami-0632
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0548
  Ec2Ramdisk: ari-0548
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic 
root=LABEL=cloudimg-rootfs console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.1.3
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient

2013-12-12 Thread Bryan Quigley

@Daniel
I'm wrong, not fixed in 13.04+

I ran some tests:
@Chiluk first up vm images do only need 64 mb reserved:
Trusty 512 MB (m1.tiny) image on OpenStack:   allocted 64 MB of ram for 
crashdump and it worked. (dump size of 23 mb)

Desktop images fail 
Trusty 2047 MB (Vagrant/Virtualbox desktop image) - allocated 64 MB of ram for 
crashdump and hung.
Reran with 100MB for crashdump, worked (dump size of 32 mb)

Is there any way to not be guessing here and generate the right number
for the kernel you are using and modules that have been loaded?  (In
other words, get current kernel size and add percentage buffer).   Per
another private case we may have situations where 128 MB is not enough.

If we can't auto-detect this (building upon chiluk's' comment), I would suggest 
something like (the numbers can change but I think we do need more levels):
 1.5 GB of RAM:  is it virtual kernel?  then do 64 mb, if not do 128 mb
1.5 GB to 4 GB: everything do 192 mb
4 GB+:  256 mb
12 GB+: 512 mb (is there a point when we should stop?)

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

Title:
  Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux
  is insufficient

Status in “grub2” package in Ubuntu:
  Confirmed
Status in “kexec-tools” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: grub-pc

  This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty.

  The /etc/grub.d/10_linux file contains this snippet:

  # add crashkernel option if we have the required tools
  if [ -x /usr/bin/makedumpfile ]  [ -x /sbin/kexec ]; then
  GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA 
crashkernel=384M-2G:64M,2G-:128M
  fi

  I am on a system with 2GB of RAM (reported as 2038MB), and according
  to the kernel startup messages, 64MB is reserved for the crash kernel.

  Unfortunately, this does not appear to be enough memory for the
  regular Ubuntu kernel to boot. I am attaching a kernel log obtained
  via serial cable; it shows the initial boot, a crash in the kernel's
  video-driver-related code, the subsequent crashkernel boot, and then
  an apparent out of memory kernel panic. (A side effect of the
  double crash is that the system is left unresponsive, requiring a
  manual reset instead of rebooting itself automatically.)

  If I double the memory numbers in the crashkernel=... argument, so
  that the reservation is 128MB, the system correctly goes on to attempt
  a vmcore dump and reboot.

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

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

[Kernel-packages] [Bug 1259645] Re: cgroup cpu capping via cpu.cfs_quota can cause tasks to not be scheduled on the runque

2013-12-12 Thread Chris J Arges

** Description changed:

  SRU Justification:
  
  Impact:
  When using cgroup's cpu capping features via the cpu.cfs_quota setting a race 
condition can occur such that a task has its timer disabled and no longer gets 
scheduled on the runqueue.
- This has been observed when setting cpu capping on VMs started with libvirt.
+ This has been observed when setting cgroup cpu capping on VMs started and 
restarted with libvirt.
  
  Fix:
  Commit f9f9ffc237dd924f048204e8799da74f9ecf40cf upstream fixes this issue. It 
fixes throttle_cfs_rq by checking if the timer is not active. If it isn't then 
it calls __start_cfs_bandwidth which will put the task back on the runqueue.
  
  Testcase:
  From the patch: make a run/sleep task in a cgroup, loop switching the cgroup
  between 1ms/100ms quota and unlimited, checking for timer_active=0 and
  throttled=1 as a failure. With the throttle_cfs_rq() change commented out
  this fails, with the full patch it passes.

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

Title:
  cgroup cpu capping via cpu.cfs_quota can cause tasks to not be
  scheduled on the runque

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Precise:
  In Progress
Status in “linux” source package in Quantal:
  In Progress
Status in “linux” source package in Raring:
  In Progress
Status in “linux” source package in Saucy:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  SRU Justification:

  Impact:
  When using cgroup's cpu capping features via the cpu.cfs_quota setting a race 
condition can occur such that a task has its timer disabled and no longer gets 
scheduled on the runqueue.
  This has been observed when setting cgroup cpu capping on VMs started and 
restarted with libvirt.

  Fix:
  Commit f9f9ffc237dd924f048204e8799da74f9ecf40cf upstream fixes this issue. It 
fixes throttle_cfs_rq by checking if the timer is not active. If it isn't then 
it calls __start_cfs_bandwidth which will put the task back on the runqueue.

  Testcase:
  From the patch: make a run/sleep task in a cgroup, loop switching the cgroup
  between 1ms/100ms quota and unlimited, checking for timer_active=0 and
  throttled=1 as a failure. With the throttle_cfs_rq() change commented out
  this fails, with the full patch it passes.

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

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

[Kernel-packages] [Bug 1049101] Re: Radeon tool does not work with a Radeon HD 6320

Santiago Gala, as per 
http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_1225B/#support an update is 
available for your BIOS (207). If you update to this following 
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

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

Thank you for your understanding.

** Tags added: bios-outdated-207

** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream-v3.6-rc5 needs-upstream-testing

** Summary changed:

- Radeon tool does not work with a Radeon HD 6320
+ 1002:9806 Radeon tool does not work with a Radeon HD 6320

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

Title:
  1002:9806 Radeon tool does not work with a Radeon HD 6320

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  $ sudo radeontool 
  cannot find ctrl region
  $ apt-cache policy radeontool 
  radeontool:
Instalados: 1.6.2-1.1
Candidato:  1.6.2-1.1
Tabla de versión:
   *** 1.6.2-1.1 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status
  $ sudo lsmod | grep rad
  radeon804426  3 
  ttm76949  1 radeon
  drm_kms_helper 46978  1 radeon
  drm   242038  5 radeon,ttm,drm_kms_helper
  i2c_algo_bit   13423  1 radeon
  $ uname -a
  Linux morel 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.04
  DISTRIB_CODENAME=precise
  DISTRIB_DESCRIPTION=Ubuntu 12.04.1 LTS
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sgala  2825 F pulseaudio
   /dev/snd/pcmC1D0c:   sgala  2825 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sgala  2825 F...m pulseaudio
   /dev/snd/controlC0:  sgala  2825 F pulseaudio
  CRDA:
   country ES:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 45'
 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 'SB'/'HDA ATI SB at 0xfeb4 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,1043103b,00100100'
 Controls  : 16
 Simple ctrls  : 9
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=3e732aad-0a6d-4900-8c8e-b3619e2d0b25
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: ASUSTeK Computer Inc. 1225B
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic 
root=UUID=613f96aa-754a-4da8-a33d-41fef58a4940 ro splash i8042.nomux=1 
i8042.reset usbcore.autosuspend=1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-31-generic N/A
   linux-backports-modules-3.2.0-31-generic  N/A
   linux-firmware1.79.1
  Tags:  precise running-unity
  Uname: Linux 3.2.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  dmi.bios.date: 02/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1225B
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 205
  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.:bvr205:bd02/20/2012:svnASUSTeKComputerInc.:pn1225B:pvr1.0:rvnASUSTeKComputerInc.:rn1225B:rvr205:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: 1225B

[Kernel-packages] [Bug 49052] Re: no hfs+ journal write support by default (gets mounted as read only)

2013-12-12 Thread bj-rn

Is there any way to get the driver (Ubuntu 13.10  saucy / Kernel
3.13-rc1) without having to compile it myself?

tia
b

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

Title:
  no hfs+ journal write support by default (gets mounted as read only)

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-source-2.6.15” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: linux-686

  Dapper Drake does not appear to support a HFS+ journaled file system. This 
manifests when I connect my ipod mini, and dmesg warns that:
  'HFS+-fs: write access to a jounaled filesystem is not supported, use the 
force option at your own risk, mounting read-only.'
  Using force appears to work to mount the device read/write. This was not a 
problem under Breezy, which makes me think that it's a kernel compilation issue.

  This occurs while running kernel linux-686 2.6.15.22

  Thanks! :-)

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

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

[Kernel-packages] [Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name

2013-12-12 Thread Ritesh Khadgaray

 Did this issue occur in a previous version of Ubuntu, or is this a new
issue?

This is a new disk, with the latest firmware ( purchased on 25th Nov).
This issue was first seen when I tried to build libreoffice ( the build
goes from 256mb to 32gb , and goes down to 18gb) .

Worked fine when building mozilla/firefox, and other packages.


 If this bug is fixed in the mainline kernel, please add the following tag 
 'kernel-fixed-upstream'.
I have tested this with mainline kernel (3.13 rc3), and 3.12 from trusty. The 
issue is reproducible on both with discard option enabled.


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

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

Title:
   htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm
  rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0),
  inode=1667681412, rec_len=45654, name_len=39

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  fs goes into read-only mode while build lo

  $ dmesg
  ...
  [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state
  [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready
  [10660.961381] perf samples too long (2505  2500), lowering 
kernel.perf_event_max_sample_rate to 5
  [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=1667681412, rec_len=45654, name_len=39
  [11822.935896] Aborting journal on device dm-1-8.
  [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only
  [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629605: block 214443466: comm rm: bad entry in directory: directory entry 
across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162
  [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=512948573, rec_len=8858, name_len=176
  [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=160939375, rec_len=26085, name_len=126
  [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=2322664969, rec_len=33791, name_len=132
  [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=954332768, rec_len=21653, name_len=30
  [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629074: block 214443433: comm rm: bad entry in directory: directory entry 
across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3
  [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=3523041938, rec_len=53167, name_len=41
  [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=4225920287, rec_len=35138, name_len=75
  [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=923253145, rec_len=44001, name_len=144
  [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=1892288796, rec_len=55247, name_len=58
  [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629300: block 214443450: comm rm: bad entry in directory: directory entry 
across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195
  [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=4223616103, rec_len=36326, name_len=130
  [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - 
offset=0(0), inode=415237227, rec_len=24702, name_len=59
  [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629101: block 214443437: comm rm: bad entry in directory: directory entry 
across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135
  [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode 
#53629543: block 214443457: comm

[Kernel-packages] [Bug 1260264] Re: package linux-image-3.5.0-45-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

You may need to run the following:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package.

If that does not resolve your issue, please mark the bug as Confirmed

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

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

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

Title:
  package linux-image-3.5.0-45-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hit http://mirror.mirohost.net quantal-backports/multiverse Sources   
 
  Hit http://mirror.mirohost.net quantal-backports/main i386 Packages   
 
  Hit http://mirror.mirohost.net quantal-backports/restricted i386 Packages 
 
  Hit http://ua.archive.ubuntu.com precise-updates/restricted Translation-en
 
  Ign http://ua.archive.ubuntu.com precise-updates/main Translation-en_US   
 
  Get:29 http://ppa.launchpad.net quantal/main i386 Packages [9,654 B]  
 
  Ign http://ua.archive.ubuntu.com precise-updates/restricted Translation-en_US 
 
  Hit http://mirror.mirohost.net quantal-backports/universe i386 Packages   
 
  Hit http://mirror.mirohost.net quantal-backports/multiverse i386 Packages 
 
  Hit http://mirror.mirohost.net quantal-backports/main Translation-en  
 
  Hit http://mirror.mirohost.net quantal-backports/multiverse Translation-en
 
  Hit http://mirror.mirohost.net quantal-backports/restricted Translation-en
 
  Hit http://mirror.mirohost.net quantal-backports/universe Translation-en  
 
  Get:30 http://mirror.mirohost.net quantal-security/restricted Sources [1,833 
B]
  Get:31 http://mirror.mirohost.net quantal-security/main Sources [64.5 kB] 
 
  Ign http://extras.ubuntu.com quantal/main Translation-en_US   
 
  Ign http://archive.canonical.com quantal/partner Translation-en_US
 
  Ign http://archive.canonical.com quantal/partner Translation-en   
 
  Ign http://extras.ubuntu.com quantal/main Translation-en  
 
  Get:32 http://mirror.mirohost.net quantal-security/multiverse Sources [1,167 
B]
  Get:33 http://mirror.mirohost.net quantal-security/universe Sources [22.0 kB] 
 
  Get:34 http://mirror.mirohost.net quantal-security/main i386 Packages [184 
kB] 
  Get:35 http://mirror.mirohost.net quantal-security/restricted i386 Packages 
[3,531 B]
  Get:36 http://mirror.mirohost.net quantal-security/universe i386 Packages 
[65.1 kB]
  Get:37 http://mirror.mirohost.net quantal-security/multiverse i386 Packages 
[1,718 B]
  Hit http://mirror.mirohost.net quantal-security/main Translation-en   
 
  Hit http://mirror.mirohost.net quantal-security/multiverse Translation-en 
 
  Hit http://mirror.mirohost.net quantal-security/restricted Translation-en 
 
  Hit http://mirror.mirohost.net quantal-security/universe Translation-en   
 
  Get:38 http://mirror.mirohost.net quantal-proposed/restricted Sources [14 B]  
 
  Get:39 http://mirror.mirohost.net quantal-proposed/main Sources [13.7 kB] 
 
  Get:40 http://mirror.mirohost.net quantal-proposed/multiverse Sources [14 B]  
 
  Get:41 http://mirror.mirohost.net quantal-proposed/universe Sources [4,546 B] 
 
  Get:42 http://mirror.mirohost.net quantal-proposed/restricted i386 Packages 
[14 B]
  Get:43 http://mirror.mirohost.net quantal-proposed/main i386 Packages [47.9 
kB]
  Get:44 http://security.ubuntu.com precise-security/restricted i386 Packages 
[4,620 B]
  Get:45 http://mirror.mirohost.net quantal-proposed/multiverse i386 Packages 
[14 B]
  Get:46 http://mirror.mirohost.net quantal-proposed/universe i386 Packages 
[12.8 kB]
  Hit http://mirror.mirohost.net quantal-proposed/main Translation-en   
 
  Hit http://mirror.mirohost.net quantal-proposed/multiverse Translation-en 
 
  Hit http://mirror.mirohost.net quantal-proposed/restricted Translation-en 
 
  Hit http://mirror.mirohost.net quantal-proposed/universe Translation-en   
 
  Hit http://security.ubuntu.com precise-security/main Translation-en   
 
  Ign http://mirror.mirohost.net quantal/main Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal/multiverse Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal/restricted Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal/universe Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal-updates/main Translation-en_US 
 
  Ign http://mirror.mirohost.net quantal-updates/multiverse Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal-updates/restricted Translation-en_US   
 
  Ign http://mirror.mirohost.net quantal-updates/universe Translation-en_US 
 
  Ign

[Kernel-packages] [Bug 1260112] Re: CPU stuck on minimum frequency after resume from suspend and unplugged

Did this issue occur in a previous version of Ubuntu, or is this a new
issue?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.12 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-rc3-trusty/

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

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

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

Title:
  CPU stuck on minimum frequency after resume from suspend and unplugged

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This happens on a Dell Latitude E6540 (4th gen core i7 CPU).

  Steps to reproduce:

  1) normally boot the computer and make sure  everything works as expected (i 
use the ondemand governor)
  2) suspend
  3) make the computer is unplugged and resume

  Expected behavior: cpu should work normally
  Actual behavior: cpu always stays at minimum frequency (in my case 800 MHz)

  If i resume from suspend while plugged to the AC charger, everything works as 
expected.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gjm2337 F pulseaudio
   /dev/snd/controlC0:  gjm2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=98df70b7-f534-4ef6-8647-8e98200ccd64
  InstallationDate: Installed on 2013-12-06 (4 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed 
root=UUID=22510d0e-a296-4b0f-a97a-27cb89a65419 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0725FP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/03/2013:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1260230] Re: Memory leak in libcrypto.so\libssl.so

** Package changed: linux (Ubuntu) = openssl (Ubuntu)

** Changed in: openssl (Ubuntu)
   Status: Confirmed = 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/1260230

Title:
  Memory leak in libcrypto.so\libssl.so

Status in “openssl” package in Ubuntu:
  New

Bug description:
  I've found a bug in openssl 1.0.1-4ubuntu5.10. Was trying to use
  libpq\libmysql.so to connect to database and did not specify sslmode
  so it used ssl to connect to database, when i've checked with valgrind
  i've detected some memory leak:

  ==25346== Memcheck, a memory error detector
  ==25346== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==25346== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==25346== Command: ./test
  ==25346==
  ==25346==
  ==25346== HEAP SUMMARY:
  ==25346== in use at exit: 81,152 bytes in 2,769 blocks
  ==25346==   total heap usage: 4,388 allocs, 1,619 frees, 281,833 bytes 
allocated
  ==25346==
  ==25346== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 229 of 279
  ==25346==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==25346==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==25346==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==25346==by 0x4EB6168: ???
  ==25346==by 0x4EB7B5C: ???
  ==25346==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==25346==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==25346==
  ==25346== LEAK SUMMARY:
  ==25346==definitely lost: 40 bytes in 1 blocks
  ==25346==indirectly lost: 120 bytes in 10 blocks
  ==25346==  possibly lost: 0 bytes in 0 blocks
  ==25346==still reachable: 80,992 bytes in 2,758 blocks
  ==25346== suppressed: 0 bytes in 0 blocks
  ==25346== Reachable blocks (those to which a pointer was found) are not shown.
  ==25346== To see them, rerun with: --leak-check=full --show-reachable=yes
  ==25346==
  ==25346== For counts of detected and suppressed errors, rerun with: -v
  ==25346== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)


  with sslmode=disable i see this:
  ==28708== Memcheck, a memory error detector
  ==28708== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==28708== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==28708== Command: ./test
  ==28708==
  ==28708==
  ==28708== HEAP SUMMARY:
  ==28708== in use at exit: 160 bytes in 11 blocks
  ==28708==   total heap usage: 138 allocs, 127 frees, 46,314 bytes allocated
  ==28708==
  ==28708== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 11 of 11
  ==28708==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==28708==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==28708==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==28708==by 0x4EB6168: ???
  ==28708==by 0x4EB7B5C: ???
  ==28708==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==28708==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==28708==
  ==28708== LEAK SUMMARY:
  ==28708==definitely lost: 40 bytes in 1 blocks
  ==28708==indirectly lost: 120 bytes in 10 blocks
  ==28708==  possibly lost: 0 bytes in 0 blocks
  ==28708==still reachable: 0 bytes in 0 blocks
  ==28708== suppressed: 0 bytes in 0 blocks
  ==28708==
  ==28708== For counts of detected and suppressed errors, rerun with: -v
  ==28708== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

  also test openssl program(attached) have a leak 47700 bytes

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

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

[Kernel-packages] [Bug 1252266] Re: Corrupted low memory after resume from suspend after updating to saucy

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

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

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

Title:
  Corrupted low memory after resume from suspend after updating to saucy

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to saucy and Linux 3.11 my Gigabyte 965P-DS3 board no longer 
properly resumes from suspend.
  The desktop still works fine after resume, but the ethernet interface won't 
come up again.
  dmesg after resume warns about corrupted low memory:

  [40560.864036] [ cut here ]
  [40560.864044] WARNING: CPU: 0 PID: 24687 at 
/build/buildd/linux-3.11.0/arch/x86/kernel/check.c:140 
check_for_bios_corruption+0x10f/0x120()
  [40560.864046] Memory corruption detected in low memory
  [40560.864048] Modules linked in: pci_stub vboxpci(OF) vboxnetadp(OF) 
vboxnetflt(OF) vboxdrv(OF) cuse ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) 
nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_conntrack(F) 
nf_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) 
bridge(F) stp(F) llc(F) ip6table_filter(F) ip6_tables(F) iptable_filter(F) 
ip_tables(F) ebtable_nat(F) ebtables(F) x_tables(F) joydev(F) xpad ff_memless 
hid_generic usbhid hid rfcomm bnep bluetooth binfmt_misc(F) kvm_intel(F) kvm(F) 
gpio_ich ppdev(F) ir_lirc_codec lirc_dev ir_sanyo_decoder ir_mce_kbd_decoder 
ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder 
e4000 rtl2832 usb_storage(F) snd_usb_audio snd_usbmidi_lib uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dvb_usb_rtl28xxu 
rtl2830 dvb_usb_v2 dvb_core rc_core snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) 
snd_seq_midi_event(F) microcode(F) pcspkr serio_raw(F) snd_rawmidi(F) 
snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) lpc_ich soundcore(F) 
nvidia(POF) parport_pc(F) drm mac_hid it87 hwmon_vid coretemp lp(F) parport(F) 
pata_acpi sky2 pata_jmicron ahci(F) libahci(F)
  [40560.864148] CPU: 0 PID: 24687 Comm: kworker/0:1 Tainted: PF   W  O 
3.11.0-13-generic #20-Ubuntu
  [40560.864151] Hardware name: Gigabyte Technology Co., Ltd. 
965P-DS3/965P-DS3, BIOS F14d 12/18/2008
  [40560.864155] Workqueue: events check_corruption
  [40560.864158]  0009 880064be9d30 816e54ba 
880064be9d78
  [40560.864162]  880064be9d68 81061dbd  
8801
  [40560.864166]  81ea73b0 0001 8800 
880064be9dc8
  [40560.864171] Call Trace:
  [40560.864178]  [816e54ba] dump_stack+0x45/0x56
  [40560.864183]  [81061dbd] warn_slowpath_common+0x7d/0xa0
  [40560.864187]  [81061e2c] warn_slowpath_fmt+0x4c/0x50
  [40560.864191]  [8104e5bf] check_for_bios_corruption+0x10f/0x120
  [40560.864195]  [8104e5de] check_corruption+0xe/0x40
  [40560.864200]  [8107d05c] process_one_work+0x17c/0x430
  [40560.864204]  [8107dcac] worker_thread+0x11c/0x3c0
  [40560.864208]  [8107db90] ? manage_workers.isra.24+0x2a0/0x2a0
  [40560.864212]  [810847b0] kthread+0xc0/0xd0
  [40560.864217]  [810846f0] ? kthread_create_on_node+0x120/0x120
  [40560.864221]  [816f51ec] ret_from_fork+0x7c/0xb0
  [40560.864225]  [810846f0] ? kthread_create_on_node+0x120/0x120
  [40560.864228] ---[ end trace a5d0e3f4744a1e9d ]---

  This did not happen with raring/Linux 3.8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  benpicco   3071 F pulseaudio
   /dev/snd/controlC0:  benpicco   3071 F pulseaudio
  Date: Mon Nov 18 14:12:08 2013
  HibernationDevice: RESUME=UUID=81e8d3af-3d5b-4a61-a550-702a919449c5
  InstallationDate: Installed on 2012-02-27 (629 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5b216424-8d68-4640-9d4c-494eb0e00e9d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A

[Kernel-packages] [Bug 1257102] Re: linux: 3.8.0-35.50 -proposed tracker

** Description changed:

  This bug is for tracking the 3.8.0-35.50 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:Monday, 02. December 2013 22:51 UTC
  kernel-stable-Prepare-package-end:Tuesday, 03. December 2013 04:42 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 03. December 2013 04:42 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 03. December 2013 06:02 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 03. December 2013 08:01 UTC
  kernel-stable-Verification-testing-start:Tuesday, 03. December 2013 08:01 UTC
  kernel-stable-Certification-testing-start:Tuesday, 03. December 2013 08:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 03. December 2013 08:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 03. December 2013 08:02 UTC
  kernel-stable-Regression-testing-end:Thursday, 05. December 2013 12:01 UTC
+ kernel-stable-Certification-testing-end:Thursday, 12. December 2013 17: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/1257102

Title:
  linux: 3.8.0-35.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
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:
  Invalid
Status in “linux” source package in Raring:
  New

Bug description:
  This bug is for tracking the 3.8.0-35.50 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:Monday, 02. December 2013 22:51 UTC
  kernel-stable-Prepare-package-end:Tuesday, 03. December 2013 04:42 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 03. December 2013 04:42 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 03. December 2013 06:02 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 03. December 2013 08:01 UTC
  kernel-stable-Verification-testing-start:Tuesday, 03. December 2013 08:01 UTC
  kernel-stable-Certification-testing-start:Tuesday, 03. December 2013 08:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 03. December 2013 08:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 03. December 2013 08:02 UTC
  kernel-stable-Regression-testing-end:Thursday, 05. December 2013 12:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 12. December 2013 17:01 UTC

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

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

[Kernel-packages] [Bug 1260112] Re: CPU stuck on minimum frequency after resume from suspend and unplugged

2013-12-12 Thread Gonçalo Marrafa

I can't say if the issue occurs in other versions since the laptop is
new and i just installed 13.10 on it. Will test the kernel and update
with the results.

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

Title:
  CPU stuck on minimum frequency after resume from suspend and unplugged

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This happens on a Dell Latitude E6540 (4th gen core i7 CPU).

  Steps to reproduce:

  1) normally boot the computer and make sure  everything works as expected (i 
use the ondemand governor)
  2) suspend
  3) make the computer is unplugged and resume

  Expected behavior: cpu should work normally
  Actual behavior: cpu always stays at minimum frequency (in my case 800 MHz)

  If i resume from suspend while plugged to the AC charger, everything works as 
expected.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gjm2337 F pulseaudio
   /dev/snd/controlC0:  gjm2337 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=98df70b7-f534-4ef6-8647-8e98200ccd64
  InstallationDate: Installed on 2013-12-06 (4 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed 
root=UUID=22510d0e-a296-4b0f-a97a-27cb89a65419 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0725FP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/03/2013:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

Looks like I built the wrong branch from 
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git


I'll build it again, this time using branch: for-pci-3.14

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

Title:
  Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

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

Bug description:
  We have a server (Dell R715) with two Intel x520 NIC's. If we run
  Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel
  driver or with Intel compiled one), but if we upgrade release to
  12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel
  drivers fails with error:

  [  226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7
  [  226.395770] Copyright (c) 1999-2013 Intel Corporation.
  [  226.395980] ixgbe: probe of :22:00.0 failed with error -5
  [  226.396092] ixgbe: probe of :22:00.1 failed with error -5
  [  226.396203] ixgbe: probe of :23:00.0 failed with error -5
  [  226.396311] ixgbe: probe of :23:00.1 failed with error -5

  I contacted Intel developers and they responded:

  Hey Fernando,
  We (ixgbe) only returns EIO (error 5) for a couple of reasons.
   1) When we fail to io map (ioremap)
   2) If the eeprom checksum is incorrect.
   3) If the MAC address from the checksum is invalid

  Reasons 2 and 3 are related to the NIC's eeprom so if they worked with 
another system they should still be fine now.  If you really wanted to verify 
you could try out the NIC's on a known good system again to see if the eeprom 
somehow got corrupted.
  That pretty much leaves us with ioremap returning an error.  I'm not at all 
sure why your Ubuntu release would not like the way we are calling ioremap, but 
it might give you a place to start looking in Ubuntu changes.
  Thanks,
  -Don

  If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's
  works fine.

  Please let me know how can I help!

  Regards

  Fernando

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

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

[Kernel-packages] [Bug 975724] Re: 045e:071d External mouse horizontal scrolling no longer works

Val, so your hardware may be tracked, could you please file a new report by 
executing the following in a terminal while booted into a Ubuntu repository 
kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: 
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: 
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: 
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

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

Title:
  045e:071d External mouse horizontal scrolling no longer works

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using a microsoft 7000 wireless desktop mouse (ID 045e:071d) -- the
  mouse has a 4 way scroll wheel; worked perfect in 11.10 but with 12.04
  beta2 the horizontal scroll now is seen as normal up/down scrolling
  instead of left/right.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-22-generic 3.2.0-22.35
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 00:29:55 2012
  HibernationDevice: RESUME=UUID=2164a001-0008-4d63-8be3-70b52dce6ae0
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: System76, Inc. Gazelle Professional
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic 
root=UUID=0a3757f8-285c-4621-af39-1735173628af ro quiet splash vt.handoff=7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp6
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp6
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1260431] [NEW] update-grub hangs under 3.11.0-3-generic

2013-12-12 Thread LaMont Jones

Public bug reported:

I have a saucy/amd64 instance that was booted using the 20130822 image
(checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on
2013-08-29, which I finally updated today.  During the upgrade, modprobe
btrfs hung in init_module().  If I kill modprobe, the upgrade finishes.
The apport gathering is on the new kernel, since apport declined to file
a bug with the 3.11.0-3-generic kernel running.

filing here for historical purposes, I expect.  The problem does not
reproduce on a current machine running 3.11.0-14-generic.

lamont

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Dec 12 17:45 seq
 crw-rw 1 root audio 116, 33 Dec 12 17:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDmesg: [   10.105412] init: plymouth-stop pre-start process (1008) 
terminated with status 1
Date: Thu Dec 12 17:45:40 2013
Ec2AMI: ami-0005
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
MarkForUpload: True
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic 
root=UUID=25707b7a-3d31-4823-831f-ed5306116706 ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.4:cvnBochs:ct1:cvr:
dmi.product.name: OpenStack Nova
dmi.product.version: 2013.1.4
dmi.sys.vendor: OpenStack Foundation

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


** Tags: amd64 apport-bug ec2-images saucy

** Attachment added: ps and strace output at the time of the hang.
   https://bugs.launchpad.net/bugs/1260431/+attachment/3928207/+files/3.11.0-3

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

Title:
  update-grub hangs under 3.11.0-3-generic

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have a saucy/amd64 instance that was booted using the 20130822 image
  (checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on
  2013-08-29, which I finally updated today.  During the upgrade,
  modprobe btrfs hung in init_module().  If I kill modprobe, the upgrade
  finishes.  The apport gathering is on the new kernel, since apport
  declined to file a bug with the 3.11.0-3-generic kernel running.

  filing here for historical purposes, I expect.  The problem does not
  reproduce on a current machine running 3.11.0-14-generic.

  lamont

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-14-generic 3.11.0-14.21
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 12 17:45 seq
   crw-rw 1 root audio 116, 33 Dec 12 17:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [   10.105412] init: plymouth-stop pre-start process (1008) 
terminated with status 1
  Date: Thu Dec 12 17:45:40 2013
  Ec2AMI: ami-0005
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001

[Kernel-packages] [Bug 975724] Re: 045e:071d External mouse horizontal scrolling no longer works

Christopher, please can you clarify your terminology? I know what the
mainline kernel is but I am not sure what you mean when you say
repository kernel. Which repository?

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

Title:
  045e:071d External mouse horizontal scrolling no longer works

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using a microsoft 7000 wireless desktop mouse (ID 045e:071d) -- the
  mouse has a 4 way scroll wheel; worked perfect in 11.10 but with 12.04
  beta2 the horizontal scroll now is seen as normal up/down scrolling
  instead of left/right.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-22-generic 3.2.0-22.35
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 00:29:55 2012
  HibernationDevice: RESUME=UUID=2164a001-0008-4d63-8be3-70b52dce6ae0
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: System76, Inc. Gazelle Professional
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic 
root=UUID=0a3757f8-285c-4621-af39-1735173628af ro quiet splash vt.handoff=7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp6
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp6
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1260431] Re: update-grub hangs under 3.11.0-3-generic

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

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

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

Title:
  update-grub hangs under 3.11.0-3-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I have a saucy/amd64 instance that was booted using the 20130822 image
  (checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on
  2013-08-29, which I finally updated today.  During the upgrade,
  modprobe btrfs hung in init_module().  If I kill modprobe, the upgrade
  finishes.  The apport gathering is on the new kernel, since apport
  declined to file a bug with the 3.11.0-3-generic kernel running.

  filing here for historical purposes, I expect.  The problem does not
  reproduce on a current machine running 3.11.0-14-generic.

  lamont

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-14-generic 3.11.0-14.21
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 12 17:45 seq
   crw-rw 1 root audio 116, 33 Dec 12 17:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [   10.105412] init: plymouth-stop pre-start process (1008) 
terminated with status 1
  Date: Thu Dec 12 17:45:40 2013
  Ec2AMI: ami-0005
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  MarkForUpload: True
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic 
root=UUID=25707b7a-3d31-4823-831f-ed5306116706 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-14-generic N/A
   linux-backports-modules-3.11.0-14-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.4:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.1.4
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1208988] Re: AppArmor no longer mediates access to path-based AF_UNIX socket files

2013-12-12 Thread Jamie Strandboge

This was fixed in at least 25.0.1+build1-0ubuntu0.13.10.1

** Changed in: firefox (Ubuntu Saucy)
   Status: Fix Committed = Fix Released

** Changed in: apparmor
   Status: Triaged = Fix Committed

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

Title:
  AppArmor no longer mediates access to path-based AF_UNIX socket files

Status in AppArmor Linux application security framework:
  Fix Committed
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “firefox” package in Ubuntu:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-grouper” package in Ubuntu:
  Fix Released
Status in “linux-maguro” package in Ubuntu:
  Fix Released
Status in “linux-mako” package in Ubuntu:
  Fix Released
Status in “linux-manta” package in Ubuntu:
  Fix Released
Status in “apparmor” source package in Saucy:
  Fix Released
Status in “apparmor-easyprof-ubuntu” source package in Saucy:
  Fix Released
Status in “firefox” source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * AppArmor removed unix domain socket mediation as part of the 2.4
  (karmic) rewrite to the security_path hooks so that it could be
  upstreamed into the main kernel. The result being apparmor no longer
  mediates access to AF_UNIX socket files. Or more specifically it does
  not mediation connections between sockets, creation of a socket within
  the filesystem is mediated

   * Confined applications can currently read from and write to any AF_UNIX
     socket files

   * Existing AppArmor profiles that contain file rules granting write access to
     AF_UNIX socket files are effectively being ignored

   * The move from the vfs hooks patches (old, out-of-tree) AppArmor and the 
security_path hooks
     apparmor incorporated into mainline in 2.6.36 were the cause of this 
regression.

     apparmor 2.4 (version in karmic) also removed other features are part of 
the rewrite to
     security_path hooks/upstreaming effort.

   * For Ubuntu, Karmic 9.10  and all newer, releases are affected.
     8.04 LTS used the vfs patches and was not affected.

  * Mediation of unix domain filesystem based sockets is needed for
  13.10 click apps confinement

  [Test Case]

   * Confining dbus-send and sending a message to the system bus is an easy
     manual testing method. Load a profile for dbus-send:

  $ cat  EOF | sudo apparmor_parser -r
  #include tunables/global

  /usr/bin/dbus-send {
    #include abstractions/base
    /usr/bin/dbus-send r,
  #  /var/run/dbus/system_bus_socket rw,
  }
  EOF

   * Note that the system_bus_socket rule is commented out. Now, run dbus-send
     under strace and see if the connect() fails. Here's the unexpected output,
     taken from an Ubuntu Saucy system:

  $ strace -e connect -- \
   dbus-send --system --dest=org.freedesktop.DBus \
   /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  connect(3, {sa_family=AF_LOCAL, sun_path=/var/run/dbus/system_bus_socket}, 
33) = 0
  +++ exited with 0 +++

   * Here's the expected output, taken from an 8.04 LTS system:

  $ strace -e connect -- \
   dbus-send --system --dest=org.freedesktop.DBus \
   /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  connect(3, {sa_family=AF_FILE, path=/var/run/dbus/system_bus_socket}, 33) = 
-1 EACCES (Permission denied)
  Failed to open connection to system message bus: Failed to connect to socket 
/var/run/dbus/system_bus_socket: Permission denied

   * Or, you can apply the AppArmor regression test suite patch attached to this
     bug and run the automated tests:

  $ cd tests/regression/apparmor
  $ make unix_fd_{server,client} unix_socket_file{,_client} /dev/null
  $ sudo bash unix_fd_server.sh
  $ sudo bash unix_socket_file.sh

  [Regression Potential]

   * Profiles developed with affected kernels aren't likely to have the 
necessary
     rules because the proper LSM hook was not implemented in those kernels, so
     the policy writer didn't need to grant access to AF_UNIX socket files

   * The profiles shipped with AppArmor can, and will, be updated to grant 
access
     to AF_UNIX socket files, but local policy modifications cannot be addressed
     by upstream/distros. Once updated kernels begin enforcing mediation of
     AF_UNIX socket files, rules in local profiles may no longer be sufficient,
     resulting in new AppArmor denials for AF_UNIX socket files.

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

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

[Kernel-packages] [Bug 1208988] Re: AppArmor no longer mediates access to path-based AF_UNIX socket files

2013-12-12 Thread Jamie Strandboge

Trusty firefox has the fix as well.

** Changed in: firefox (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  AppArmor no longer mediates access to path-based AF_UNIX socket files

Status in AppArmor Linux application security framework:
  Fix Committed
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “firefox” package in Ubuntu:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-grouper” package in Ubuntu:
  Fix Released
Status in “linux-maguro” package in Ubuntu:
  Fix Released
Status in “linux-mako” package in Ubuntu:
  Fix Released
Status in “linux-manta” package in Ubuntu:
  Fix Released
Status in “apparmor” source package in Saucy:
  Fix Released
Status in “apparmor-easyprof-ubuntu” source package in Saucy:
  Fix Released
Status in “firefox” source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * AppArmor removed unix domain socket mediation as part of the 2.4
  (karmic) rewrite to the security_path hooks so that it could be
  upstreamed into the main kernel. The result being apparmor no longer
  mediates access to AF_UNIX socket files. Or more specifically it does
  not mediation connections between sockets, creation of a socket within
  the filesystem is mediated

   * Confined applications can currently read from and write to any AF_UNIX
     socket files

   * Existing AppArmor profiles that contain file rules granting write access to
     AF_UNIX socket files are effectively being ignored

   * The move from the vfs hooks patches (old, out-of-tree) AppArmor and the 
security_path hooks
     apparmor incorporated into mainline in 2.6.36 were the cause of this 
regression.

     apparmor 2.4 (version in karmic) also removed other features are part of 
the rewrite to
     security_path hooks/upstreaming effort.

   * For Ubuntu, Karmic 9.10  and all newer, releases are affected.
     8.04 LTS used the vfs patches and was not affected.

  * Mediation of unix domain filesystem based sockets is needed for
  13.10 click apps confinement

  [Test Case]

   * Confining dbus-send and sending a message to the system bus is an easy
     manual testing method. Load a profile for dbus-send:

  $ cat  EOF | sudo apparmor_parser -r
  #include tunables/global

  /usr/bin/dbus-send {
    #include abstractions/base
    /usr/bin/dbus-send r,
  #  /var/run/dbus/system_bus_socket rw,
  }
  EOF

   * Note that the system_bus_socket rule is commented out. Now, run dbus-send
     under strace and see if the connect() fails. Here's the unexpected output,
     taken from an Ubuntu Saucy system:

  $ strace -e connect -- \
   dbus-send --system --dest=org.freedesktop.DBus \
   /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  connect(3, {sa_family=AF_LOCAL, sun_path=/var/run/dbus/system_bus_socket}, 
33) = 0
  +++ exited with 0 +++

   * Here's the expected output, taken from an 8.04 LTS system:

  $ strace -e connect -- \
   dbus-send --system --dest=org.freedesktop.DBus \
   /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  connect(3, {sa_family=AF_FILE, path=/var/run/dbus/system_bus_socket}, 33) = 
-1 EACCES (Permission denied)
  Failed to open connection to system message bus: Failed to connect to socket 
/var/run/dbus/system_bus_socket: Permission denied

   * Or, you can apply the AppArmor regression test suite patch attached to this
     bug and run the automated tests:

  $ cd tests/regression/apparmor
  $ make unix_fd_{server,client} unix_socket_file{,_client} /dev/null
  $ sudo bash unix_fd_server.sh
  $ sudo bash unix_socket_file.sh

  [Regression Potential]

   * Profiles developed with affected kernels aren't likely to have the 
necessary
     rules because the proper LSM hook was not implemented in those kernels, so
     the policy writer didn't need to grant access to AF_UNIX socket files

   * The profiles shipped with AppArmor can, and will, be updated to grant 
access
     to AF_UNIX socket files, but local policy modifications cannot be addressed
     by upstream/distros. Once updated kernels begin enforcing mediation of
     AF_UNIX socket files, rules in local profiles may no longer be sufficient,
     resulting in new AppArmor denials for AF_UNIX socket files.

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

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

[Kernel-packages] [Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa

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

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

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

Title:
  Boot failure with saucy kernel 3.11 probing eisa

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have an old laptop that I upgraded to saucy and it will only boot the 
earlier 3.8 kernel.  The 3.11, 3 versions tried including the proposed, hangs 
on Platform eisa.0: Probing EISA bus 0 
   
  I also tried the 3.12.0-999 kernel at 
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ and it 
hangs as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-generic 3.11.0.14.15
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cp 1926 F pulseaudio
  CRDA:
   country CO:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 23), DFS
(5735 - 5835 @ 40), (3, 30)
  CurrentDmesg:
   [  114.938323] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
   [  115.026165] XFS (sdb6): Mounting Filesystem
   [  119.437397] XFS (sdb6): Ending clean mount
   [  119.878267] EXT4-fs (sdb1): mounted filesystem with ordered data mode. 
Opts: (null)
  Date: Fri Nov 15 23:18:27 2013
  HibernationDevice: RESUME=UUID=33c5f08a-8efc-4eb2-b6ec-497bb57df899
  Lsusb:
   Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA 
Technology Corp. JM20337 Hi-Speed USB to SATA  PATA Combo Bridge
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: sag168168 Apollo Pro133AX
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=5658ed45-be8e-4c39-b0e3-1944d7a303b0 ro quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-32-generic N/A
   linux-backports-modules-3.8.0-32-generic  N/A
   linux-firmware1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to saucy on 2013-11-01 (14 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 10/18/2001
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: 694x686a
  dmi.board.vendor: VIA
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Apollo Pro133AX
  dmi.product.version: 8500V
  dmi.sys.vendor: sag168168

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

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

[Kernel-packages] [Bug 1037718] Re: 8086:4222 [Dell Precision M4300] Intel wifi led is off after resuming from suspend

Cas, could you please test the latest upstream kernel available (not the daily 
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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.

** Summary changed:

- Intel wifi led is off after resuming from suspend
+ 8086:4222 [Dell Precision M4300] Intel wifi led is off after resuming from 
suspend

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

Title:
  8086:4222 [Dell Precision M4300] Intel wifi led is off after resuming
  from suspend

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

Bug description:
  I have set the wifi options iwlegacy led_mode=1 in
  /etc/modprobe.d/wlan.conf to stop the led blinking, which works as
  expected. The problem I have found is that if I suspend the laptop
  then upon resuming the wifi led is permanently off yet the wifi still
  works properly.

  Also it is not just suspend that affects the LED, disabling wifi from
  network menu or using the hardware wifi switch on the laptop results
  it the same problem that the LED is permanently off after turning wifi
  back on.

  This is regression going from kernel 2.6.38 (Natty) to 2.6.39
  (Oneiric).

  Note: I am not sure if it was clear enough that when the led is set to
  blinking there is no issue with it being off upon resume etc.

  WORKAROUND: To get the LED back on without rebooting reload the module:
  rmmod iwl3945  modprobe iwl3945

  WORKAROUND: For the suspend issue is to add to /etc/pm/config.d/modules :
  SUSPEND_MODULES=iwl3945

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-10-generic 3.5.0-10.10
  ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
  Uname: Linux 3.5.0-10-generic x86_64
  ApportVersion: 2.4-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  calum  1921 F pulseaudio
  CRDA:
   country GB:
    (2402 - 2482 @ 40), (N/A, 20)
    (5170 - 5250 @ 40), (N/A, 20)
    (5250 - 5330 @ 40), (N/A, 20), DFS
    (5490 - 5710 @ 40), (N/A, 27), DFS
  CheckboxSubmission: beb20350994a383f56f97def0e07bae1
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Thu Aug 16 19:23:53 2012
  HibernationDevice: RESUME=UUID=3f279429-3482-4734-86b6-cc41fa7ce020
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120223.1)
  MachineType: Dell Inc. Precision M4300
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-10-generic 
root=UUID=64e61881-95ee-4b3c-8714-c08c940f4966 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-10-generic N/A
   linux-backports-modules-3.5.0-10-generic  N/A
   linux-firmware1.89
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-08-12 (3 days ago)
  dmi.bios.date:  06/19/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0UY141
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/20/2010:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M4300
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

I rebuilt the test kernel from upstream:

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

Can you test that kernel and report back if it has the bug or not?

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

Title:
  Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

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

Bug description:
  We have a server (Dell R715) with two Intel x520 NIC's. If we run
  Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel
  driver or with Intel compiled one), but if we upgrade release to
  12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel
  drivers fails with error:

  [  226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7
  [  226.395770] Copyright (c) 1999-2013 Intel Corporation.
  [  226.395980] ixgbe: probe of :22:00.0 failed with error -5
  [  226.396092] ixgbe: probe of :22:00.1 failed with error -5
  [  226.396203] ixgbe: probe of :23:00.0 failed with error -5
  [  226.396311] ixgbe: probe of :23:00.1 failed with error -5

  I contacted Intel developers and they responded:

  Hey Fernando,
  We (ixgbe) only returns EIO (error 5) for a couple of reasons.
   1) When we fail to io map (ioremap)
   2) If the eeprom checksum is incorrect.
   3) If the MAC address from the checksum is invalid

  Reasons 2 and 3 are related to the NIC's eeprom so if they worked with 
another system they should still be fine now.  If you really wanted to verify 
you could try out the NIC's on a known good system again to see if the eeprom 
somehow got corrupted.
  That pretty much leaves us with ioremap returning an error.  I'm not at all 
sure why your Ubuntu release would not like the way we are calling ioremap, but 
it might give you a place to start looking in Ubuntu changes.
  Thanks,
  -Don

  If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's
  works fine.

  Please let me know how can I help!

  Regards

  Fernando

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

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

[Kernel-packages] [Bug 1034132] Re: Macbook touchpad cursor moving in steps

dp, this bug was reported a while ago and there hasn't been any activity
in it recently. We were wondering if this is still an issue? If so,
could you please test for this with the latest development release of
Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-
live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications-Accessories-Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux replace-with-bug-number

Also, could you please test the latest upstream kernel available (not the daily 
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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: needs-upstream-testing quantal raring

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

** Summary changed:

- Macbook touchpad cursor moving in steps
+ [MacBook2,1] Touchpad cursor moving in steps

** Description changed:

  I'm on a MacBook2,1, running a fully updated Ubuntu 12.04. When using
  the internal Touchpad (appletouch driver), the cursor only moves
  horizontally or vertically. When dragging a diagonal line, the cursor
  will move in steps, basically rendering the builtin touchpad unusable.
- 
  This issue is also described in a forum thread:
  http://ubuntuforums.org/showthread.php?t=813884page=6
  
- In the second post on page 6 describes a solution. In the linux kernel,
- in appletouch.c, change the following two defines:
- 
+ In the second post on page 6 describes a solution. In the linux kernel, in 
appletouch.c, change the following two defines and recompile:
  Original:
- 
  #define ATP_FUZZ 16
- 
  #define ATP_THRESHOLD 5
  
  New:
- 
  #define ATP_FUZZ 0
- 
  #define ATP_THRESHOLD 3
- 
- and recompile.
  
  I tried this and can confirm that the touchpad is now fully usable.
  However, recompiling the kernel takes several hours and *all* of the
  disk space on my laptop. Doing this on every kernel update is just not
- practical.
- 
- I would therefore like to ask that this be applied as a patch to the default 
ubuntu kernel.
- At the very least, please make an optional package containing the patched 
appletouch driver that can be selectively installed by people having this issue.
+ practical. I would therefore like to ask that this be applied as a patch
+ to the default ubuntu kernel. At the very least, please make an optional
+ package containing the patched appletouch driver that can be selectively
+ installed by people having this issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-generic 3.2.0.27.29
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  damian 1778 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  damian 1778 F pulseaudio
  CRDA:
-  country AW:
-   (2402 - 2482 @ 40), (N/A, 20)
-   (5170 - 5250 @ 40), (N/A, 20)
-   (5250 - 5330 @ 40), (N/A, 20), DFS
-   (5490 - 5710 @ 40), (N/A, 27), DFS
+  country AW:
+   (2402 - 2482 @ 40), (N/A, 20)
+   (5170 - 5250 @ 40), (N/A, 20)
+   (5250 - 5330 @ 40), (N/A, 20), DFS
+   (5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
-  Card hw:0 'Intel'/'HDA Intel at 0x9044 irq 43'
-Mixer name : 'SigmaTel STAC9221 A1'
-Components : 'HDA:83847680,106b2200,00103401'
-Controls  : 25
-Simple ctrls  : 13
+  Card hw:0 'Intel'/'HDA Intel at 0x9044 irq 43'
+    Mixer name : 'SigmaTel STAC9221 A1'
+    Components : 'HDA:83847680,106b2200,00103401'
+    Controls  : 25
+    Simple ctrls  : 13
  Date: Tue Aug  7 21:35:12 2012
  HibernationDevice: RESUME=UUID=a7716e7d-8718-4fe9-988f-958519d6a2c2
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release

[Kernel-packages] [Bug 1025283] Re: [Dell Precision T7600] LiveCD/USB will not boot in UEFI mode

** Summary changed:

- LiveCD/USB will not boot in UEFI mode
+ [Dell Precision T7600] LiveCD/USB will not boot in UEFI mode

** Tags added: bios-outdated-a10

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

Title:
  [Dell Precision T7600] LiveCD/USB will not boot in UEFI mode

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

Bug description:
  I tried to boot from the LiveCD in UEFI mode as I wished to install my
  UEFI capable workstation in UEFI + GPT mode.

  If I boot in legacy mode, it boots up without a problem but of course,
  does not allow me to install in UEFI mode.

  I get the following error over and over:

  udevd[114]: timeout: killing `/sbin/modprobe -bv
  pci:v1000d0073sv1028sd1F78bc01sc04i00' [182]

  Then finally:

  udevadm settle - timeout of 120 seconds reached, the event queue contains:
/sys/devices/pci:00/:00:03.0/:06:00.0 (1588)
/sys/devices/pci:00/:00:03.0/:06:00.0/host6 (1588)
/sys/devices/pci:00/:00:03.0/:06:00.0/host6/scsi_host/host6 
(1588)

  Seems to perhaps indicate that the disk controller is having a
  problem. It's a Dell PERC H310. Seems strange given that it boots up
  in legacy BIOS mode fine.

  I'm attaching a lspci -v.

  I can provide whatever additional information is required.

  Thanks
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dpwrussell   2620 F pulseaudio
   /dev/snd/controlC0:  dpwrussell   2620 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc652 irq 113'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,10280495,00100100'
 Controls  : 27
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xc608 irq 36'
 Mixer name : 'Nvidia GPU 10 HDMI/DP'
 Components : 'HDA:10de0010,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=cdfdf9db-4a25-4043-9e85-53fab27f04f3
  InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120423)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=50fb1960-a04d-4af4-8db5-e63b5c373eed ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: mei
  Tags:  precise staging precise staging
  Uname: Linux 3.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/06/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0VHRW1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd06/06/2012:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn0VHRW1:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1025283] Re: [Dell Precision T7600] LiveCD/USB will not boot in UEFI mode

2013-12-12 Thread Douglas Russell

I will test the A10 bios update ASAP.

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

Title:
  [Dell Precision T7600] LiveCD/USB will not boot in UEFI mode

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

Bug description:
  I tried to boot from the LiveCD in UEFI mode as I wished to install my
  UEFI capable workstation in UEFI + GPT mode.

  If I boot in legacy mode, it boots up without a problem but of course,
  does not allow me to install in UEFI mode.

  I get the following error over and over:

  udevd[114]: timeout: killing `/sbin/modprobe -bv
  pci:v1000d0073sv1028sd1F78bc01sc04i00' [182]

  Then finally:

  udevadm settle - timeout of 120 seconds reached, the event queue contains:
/sys/devices/pci:00/:00:03.0/:06:00.0 (1588)
/sys/devices/pci:00/:00:03.0/:06:00.0/host6 (1588)
/sys/devices/pci:00/:00:03.0/:06:00.0/host6/scsi_host/host6 
(1588)

  Seems to perhaps indicate that the disk controller is having a
  problem. It's a Dell PERC H310. Seems strange given that it boots up
  in legacy BIOS mode fine.

  I'm attaching a lspci -v.

  I can provide whatever additional information is required.

  Thanks
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dpwrussell   2620 F pulseaudio
   /dev/snd/controlC0:  dpwrussell   2620 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc652 irq 113'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,10280495,00100100'
 Controls  : 27
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xc608 irq 36'
 Mixer name : 'Nvidia GPU 10 HDMI/DP'
 Components : 'HDA:10de0010,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=cdfdf9db-4a25-4043-9e85-53fab27f04f3
  InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120423)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=50fb1960-a04d-4af4-8db5-e63b5c373eed ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: mei
  Tags:  precise staging precise staging
  Uname: Linux 3.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/06/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0VHRW1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd06/06/2012:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn0VHRW1:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1260225] Re: Crackling audio on HP / AMD Hudson machines when changing volume during playback

2013-12-12 Thread David Henningsson

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

Title:
  Crackling audio on HP / AMD Hudson machines when changing volume
  during playback

Status in HWE Next Project:
  New
Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  We discovered that for these machines we would sometimes lose an
  interrupt if we changed volume during playback and that enable_msi=0
  would fix this issue.

  This bug is for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 975724] Re: 045e:071d External mouse horizontal scrolling no longer works

Val, a Ubuntu repository kernel is one that comes by default 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/975724

Title:
  045e:071d External mouse horizontal scrolling no longer works

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using a microsoft 7000 wireless desktop mouse (ID 045e:071d) -- the
  mouse has a 4 way scroll wheel; worked perfect in 11.10 but with 12.04
  beta2 the horizontal scroll now is seen as normal up/down scrolling
  instead of left/right.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-22-generic 3.2.0-22.35
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 00:29:55 2012
  HibernationDevice: RESUME=UUID=2164a001-0008-4d63-8be3-70b52dce6ae0
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: System76, Inc. Gazelle Professional
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic 
root=UUID=0a3757f8-285c-4621-af39-1735173628af ro quiet splash vt.handoff=7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp6
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp6
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa

2013-12-12 Thread Charles Peters II

This kernel has the 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/1251816

Title:
  Boot failure with saucy kernel 3.11 probing eisa

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have an old laptop that I upgraded to saucy and it will only boot the 
earlier 3.8 kernel.  The 3.11, 3 versions tried including the proposed, hangs 
on Platform eisa.0: Probing EISA bus 0 
   
  I also tried the 3.12.0-999 kernel at 
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ and it 
hangs as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-generic 3.11.0.14.15
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cp 1926 F pulseaudio
  CRDA:
   country CO:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 23), DFS
(5735 - 5835 @ 40), (3, 30)
  CurrentDmesg:
   [  114.938323] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
   [  115.026165] XFS (sdb6): Mounting Filesystem
   [  119.437397] XFS (sdb6): Ending clean mount
   [  119.878267] EXT4-fs (sdb1): mounted filesystem with ordered data mode. 
Opts: (null)
  Date: Fri Nov 15 23:18:27 2013
  HibernationDevice: RESUME=UUID=33c5f08a-8efc-4eb2-b6ec-497bb57df899
  Lsusb:
   Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA 
Technology Corp. JM20337 Hi-Speed USB to SATA  PATA Combo Bridge
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: sag168168 Apollo Pro133AX
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=5658ed45-be8e-4c39-b0e3-1944d7a303b0 ro quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-32-generic N/A
   linux-backports-modules-3.8.0-32-generic  N/A
   linux-firmware1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to saucy on 2013-11-01 (14 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 10/18/2001
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: 694x686a
  dmi.board.vendor: VIA
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Apollo Pro133AX
  dmi.product.version: 8500V
  dmi.sys.vendor: sag168168

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

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

[Kernel-packages] [Bug 1259861] Re: 5-10 second delay in kernel boot

Sure, it would be good to know if this is related to an Ubuntu specific
patch.  Can you test the upstream 3.12.4 kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12.4-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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

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

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

[Kernel-packages] [Bug 1239572] Re: TCP Tail Loss Probe problem in Ubuntu 13.10 kernel

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) = (unassigned)

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

Title:
  TCP Tail Loss Probe problem in Ubuntu 13.10 kernel

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Bug of type net/tcp in  linux kernel 3.10

  Please Refer to 
  http://article.gmane.org/gmane.linux.network/286793/match=
  AND
  https://bugzilla.redhat.com/show_bug.cgi?id=989251

  
   We are planing to widely deploy Ubuntu 13.10 in our frontend server for  
advanced TCP enhancement in the latest linux kernel and Tail Loss Probe is 
considered as one of the most important features, so do please fix this bug.

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

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

[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress = Fix Released

** Changed in: linux (Ubuntu Raring)
   Status: In Progress = Fix Released

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

Title:
  kernels following version 3.8.0-27 do not start

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

Bug description:
  All kernel updates on ubuntu following kernel 3.8.0-27 result in an
  empty screen with no indication of startup, no response to the
  keyboard. I can only start up using kernel version 3.8.0-27-generic.
  All following numbers (up to and including 3.8.0-31-generic) do not
  result in a running system. Also, the display no message at all when
  starting up (after grub).

  I checked the logfiles with grep -n Linux version 3.8.0- * and
  found only 27 to be logged, nothing for the other kernels. I am at a
  loss how to continue.

  I am running the most recent version of Ubuntu server.

  Two days ago I reinstalled Ubuntu with essentially the same result.
  The installation kernel version 3.8.0-19 works fine. The updated
  kernel 3.8.0-31 does not work.

  The following is the situation:

  When I let the machine start on itself I get no output at all.
  When I manually tell ubuntu to start the most recent kernel, I get 2 
lines:

  Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ...

  that's it.

  When I manually start the recovery kernel, I get a lot of
  information. Finally it drops to a terminal and indicates it could not
  load the LVM partition /dev/mapper/Server-Root. This is why I never
  see any result in my message or dmesg on disk.

  The problem seems to be with the Areca Raid controller. It does a
  reset of the scsi bus eh until it finally gives up and drops to a
  terminal. A while after the system goes berserk with messages of non
  responding scsi bus.

  As I cannot reach my harddisk, is there a way to find out what is
  wrong? Why does everything work fine up to and including kernel 27 and
  starts to malfunction after that? Did the Areca software change in
  some way?

  P.S. When I start kernel version 3.8.0-19, everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubuntu-release-upgrader-core 1:0.192.13
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Oct  9 14:53:03 2013
  InstallationDate: Installed on 2013-10-07 (1 days ago)
  InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1208532] Re: put_page failures with 3.8.0-27.40

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

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

Title:
  put_page failures with 3.8.0-27.40

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Since update to 3.8.0-27.40 kernel I have been seeing these errors on
  an almost daily basis. I run two Windows Server 2012 instances under
  KVM. One or both of the Windows instances will disconnect from the
  network when this error happens and will not reconnect until I reboot
  Windows. Linux seems to recover silently on its own.

  Running on an HP Z600 Workstation with ECC RAM (memory issue is very
  unlikely). Scanned the boot/swap HDD for errors with Seagate SeaTools,
  no issues found.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-27-generic 3.8.0-27.40
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   3352 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Aug  5 09:44:31 2013
  HibernationDevice: RESUME=UUID=94c635e6-8245-4fe1-8c93-432c8d10dbd1
  InstallationDate: Installed on 2012-02-14 (538 days ago)
  InstallationMedia: Ubuntu-Server 11.10 Oneiric Ocelot - Release amd64 
(20111011)
  MachineType: Hewlett-Packard HP Z600 Workstation
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic 
root=/dev/mapper/mizuno-root ro
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-25 (101 days ago)
  dmi.bios.date: 11/02/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G4 v03.54
  dmi.board.asset.tag: 2UA00605JK
  dmi.board.name: 0AE8h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: C
  dmi.chassis.asset.tag: 2UA00605JK
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G4v03.54:bd11/02/2011:svnHewlett-Packard:pnHPZ600Workstation:pvr:rvnHewlett-Packard:rn0AE8h:rvrC:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z600 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1234662] Re: Ubuntu-lts-3.8.0 kernels corrupt ext[234] filesystems with 1k block size in Xen guests

Fixed in raring by commit:

commit 3901878b563fbdcbb21ac63cfd096b8d1df0b08b
Author: Roger Pau Monne roger@citrix.com
Date:   Thu May 2 10:58:50 2013 +0200

xen-blkfront: use a different scatterlist for each request


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

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

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

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

Title:
  Ubuntu-lts-3.8.0 kernels corrupt ext[234] filesystems with 1k block
  size in Xen guests

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Raring:
  Fix Released

Bug description:
  We observed a problem with a Postfix database file created by postmap 
becoming corrupted in a Xen guest when the file was on an ext4 filesystem with 
a 1kb block size.  This was reported to the linux-ext4 list in 
http://marc.info/?t=13801802833r=1w=2.  The subsequent investigation 
identified the git commit 7b2b160da7661bb2ade3f924b1bd3e3084e53341 as solving 
the problem.  We have applied this on top of tag Ubuntu-lts-3.8.0-13.22 and 
confirmed that it resolves the problem we are seeing.
  --- 
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Oct  4 19:28 seq
   crw-rw---T 1 root audio 116, 33 Oct  4 19:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=1d79e306-bed4-4cd4-8dbc-24a727ef8db6
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MarkForUpload: True
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: root=/dev/mapper/ejbca0_systemvg-rootlv ro 
rootflags=subvol=@   splash quiet tmem $vt_handoff
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Kernel-packages] [Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa

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

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

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

Title:
  Boot failure with saucy kernel 3.11 probing eisa

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have an old laptop that I upgraded to saucy and it will only boot the 
earlier 3.8 kernel.  The 3.11, 3 versions tried including the proposed, hangs 
on Platform eisa.0: Probing EISA bus 0 
   
  I also tried the 3.12.0-999 kernel at 
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ and it 
hangs as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-generic 3.11.0.14.15
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cp 1926 F pulseaudio
  CRDA:
   country CO:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 23), DFS
(5735 - 5835 @ 40), (3, 30)
  CurrentDmesg:
   [  114.938323] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
   [  115.026165] XFS (sdb6): Mounting Filesystem
   [  119.437397] XFS (sdb6): Ending clean mount
   [  119.878267] EXT4-fs (sdb1): mounted filesystem with ordered data mode. 
Opts: (null)
  Date: Fri Nov 15 23:18:27 2013
  HibernationDevice: RESUME=UUID=33c5f08a-8efc-4eb2-b6ec-497bb57df899
  Lsusb:
   Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA 
Technology Corp. JM20337 Hi-Speed USB to SATA  PATA Combo Bridge
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: sag168168 Apollo Pro133AX
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=5658ed45-be8e-4c39-b0e3-1944d7a303b0 ro quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-32-generic N/A
   linux-backports-modules-3.8.0-32-generic  N/A
   linux-firmware1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to saucy on 2013-11-01 (14 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 10/18/2001
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: 694x686a
  dmi.board.vendor: VIA
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Apollo Pro133AX
  dmi.product.version: 8500V
  dmi.sys.vendor: sag168168

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

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

[Kernel-packages] [Bug 1259727] Re: Crashes under load

2013-12-12 Thread Benjamin Drung

I can't test the mainline kernel builds, because they are only built for
i386 and amd64, but not for armhf.

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

Title:
  Crashes under load

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The Wandboard Quad crashes under load. This can be triggered by
  running apt-get upgrade or a scripts that converts a git repository
  to bzr, for example. It does not crash every time, but often enough to
  reproduce the crash. Attached the output of dmesg after the crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic armv7l
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  1  1970 seq
   crw-rw 1 root audio 116, 33 Jan  1  1970 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.12.0-7-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg:
   
  Date: Tue Dec 10 23:38:45 2013
  HibernationDevice: RESUME=UUID=174445a8-0f41-440c-a1c4-9d6e6657b834
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: ro quiet splash 
root=UUID=5b2e9784-4869-4303-a512-a7f29dde7cf1
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1259727] Re: Crashes under load

2013-12-12 Thread Benjamin Drung

I can run apport-collect after the crash, but this command stalls. I
will now try to test the upstream kernels.

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

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

** Tags added: kernel-unable-to-test-upstream

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

Title:
  Crashes under load

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The Wandboard Quad crashes under load. This can be triggered by
  running apt-get upgrade or a scripts that converts a git repository
  to bzr, for example. It does not crash every time, but often enough to
  reproduce the crash. Attached the output of dmesg after the crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic armv7l
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  1  1970 seq
   crw-rw 1 root audio 116, 33 Jan  1  1970 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.12.0-7-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg:
   
  Date: Tue Dec 10 23:38:45 2013
  HibernationDevice: RESUME=UUID=174445a8-0f41-440c-a1c4-9d6e6657b834
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: ro quiet splash 
root=UUID=5b2e9784-4869-4303-a512-a7f29dde7cf1
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1260513] [NEW] horizontal scrolling is broken with some external mouse devices

Public bug reported:

Submitting my hardware info in a sequel to LP #975724.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.12.0-7-generic 3.12.0-7.15 [modified: 
boot/vmlinuz-3.12.0-7-generic]
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  val2055 F pulseaudio
 /dev/snd/controlC1:  val2055 F pulseaudio
 /dev/snd/controlC0:  val2055 F pulseaudio
CurrentDesktop: Unity
CurrentDmesg:
 [   18.719163] r8169 :04:00.0 eth0: link down
 [   18.719209] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [   18.719405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [   20.803774] r8169 :04:00.0 eth0: link up
 [   20.803781] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Thu Dec 12 17:03:45 2013
HibernationDevice: RESUME=UUID=ac145c0d-f41b-4f64-9a96-1ca3b10a8b72
InstallationDate: Installed on 2013-12-12 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131212)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: Gateway DX4860
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic.efi.signed 
root=UUID=e0d98c7c-d44d-4f1c-9754-aac8b034e434 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-7-generic N/A
 linux-backports-modules-3.12.0-7-generic  N/A
 linux-firmware1.117
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-A3
dmi.board.name: DX4860
dmi.board.vendor: Gateway
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd04/19/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnDX4860:rvr:cvnGateway:ct3:cvr:
dmi.product.name: DX4860
dmi.sys.vendor: Gateway

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


** Tags: amd64 apport-bug 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/1260513

Title:
  horizontal scrolling is broken with some external mouse devices

Status in “linux” package in Ubuntu:
  New

Bug description:
  Submitting my hardware info in a sequel to LP #975724.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15 [modified: 
boot/vmlinuz-3.12.0-7-generic]
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  val2055 F pulseaudio
   /dev/snd/controlC1:  val2055 F pulseaudio
   /dev/snd/controlC0:  val2055 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   [   18.719163] r8169 :04:00.0 eth0: link down
   [   18.719209] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   18.719405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   20.803774] r8169 :04:00.0 eth0: link up
   [   20.803781] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Thu Dec 12 17:03:45 2013
  HibernationDevice: RESUME=UUID=ac145c0d-f41b-4f64-9a96-1ca3b10a8b72
  InstallationDate: Installed on 2013-12-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131212)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gateway DX4860
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic.efi.signed 
root=UUID=e0d98c7c-d44d-4f1c-9754-aac8b034e434 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A3
  dmi.board.name: DX4860
  dmi.board.vendor: Gateway
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd04/19/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnDX4860:rvr:cvnGateway:ct3:cvr:
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 975724] Re: 045e:071d External mouse horizontal scrolling no longer works

Christopher, my hardware information is in LP #1260513.

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

Title:
  045e:071d External mouse horizontal scrolling no longer works

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using a microsoft 7000 wireless desktop mouse (ID 045e:071d) -- the
  mouse has a 4 way scroll wheel; worked perfect in 11.10 but with 12.04
  beta2 the horizontal scroll now is seen as normal up/down scrolling
  instead of left/right.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-22-generic 3.2.0-22.35
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 00:29:55 2012
  HibernationDevice: RESUME=UUID=2164a001-0008-4d63-8be3-70b52dce6ae0
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: System76, Inc. Gazelle Professional
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic 
root=UUID=0a3757f8-285c-4621-af39-1735173628af ro quiet splash vt.handoff=7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp6
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp6
  dmi.sys.vendor: System76, Inc.

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

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

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

This change was made by a bot.

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

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

Title:
  horizontal scrolling is broken with some external mouse devices

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Submitting my hardware info in a sequel to LP #975724.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15 [modified: 
boot/vmlinuz-3.12.0-7-generic]
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  val2055 F pulseaudio
   /dev/snd/controlC1:  val2055 F pulseaudio
   /dev/snd/controlC0:  val2055 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   [   18.719163] r8169 :04:00.0 eth0: link down
   [   18.719209] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   18.719405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   20.803774] r8169 :04:00.0 eth0: link up
   [   20.803781] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Thu Dec 12 17:03:45 2013
  HibernationDevice: RESUME=UUID=ac145c0d-f41b-4f64-9a96-1ca3b10a8b72
  InstallationDate: Installed on 2013-12-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131212)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gateway DX4860
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic.efi.signed 
root=UUID=e0d98c7c-d44d-4f1c-9754-aac8b034e434 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A3
  dmi.board.name: DX4860
  dmi.board.vendor: Gateway
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd04/19/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnDX4860:rvr:cvnGateway:ct3:cvr:
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1256638] Re: Realtek driver v8.036.00-ppa1-precise1 doesn't build

2013-12-12 Thread rusibla

I had the same problem, here is the log from the dkms build process

** Attachment added: make.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256638/+attachment/3928342/+files/make.log

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

Title:
  Realtek driver v8.036.00-ppa1-precise1 doesn't build

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I'm sorry, but Launchpad wouldn't let me attach this bug to package
  realtek-r8168-dkms, because it's PPA-only.

  I'm running Xubuntu 12.04.3 on a HP ProBook 4530s.
  The wired network doesn't work, and the driver loaded out-of-the-box is r8169 
- but lspci says it's actually a RTL8111/8168/8411.

  There's a PPA by Arturo Casal, providing the r8168 driver:
  https://launchpad.net/~berfenger/+archive/realtek

  Installing Arturo's realtek-r8168-dkms package from PPA fails to
  build:

  [quote]
  make -C src/ clean
  make[1]: Entering directory `/var/lib/dkms/realtek-r8168/8.036.00/build/src'
  make -C /lib/modules/3.2.0-40-generic/build 
SUBDIRS=/var/lib/dkms/realtek-r8168/8.036.00/build/src clean
  make[2]: Entering directory `/usr/src/linux-headers-3.2.0-40-generic'
  make[2]: Leaving directory `/usr/src/linux-headers-3.2.0-40-generic'
  make[1]: Leaving directory `/var/lib/dkms/realtek-r8168/8.036.00/build/src'
  make -C src/ modules
  make[1]: Entering directory `/var/lib/dkms/realtek-r8168/8.036.00/build/src'
  make -C /lib/modules/3.2.0-40-generic/build 
SUBDIRS=/var/lib/dkms/realtek-r8168/8.036.00/build/src modules
  make[2]: Entering directory `/usr/src/linux-headers-3.2.0-40-generic'
CC [M]  /var/lib/dkms/realtek-r8168/8.036.00/build/src/r8168_n.o
  /var/lib/dkms/realtek-r8168/8.036.00/build/src/r8168_n.c: In function 
‘rtl8168_get_rx_csum’:
  /var/lib/dkms/realtek-r8168/8.036.00/build/src/r8168_n.c:2103:24: error: 
‘RxChkS1um’ undeclared (first use in this function)
  /var/lib/dkms/realtek-r8168/8.036.00/build/src/r8168_n.c:2103:24: note: each 
undeclared identifier is reported only once for each function it appears in
  make[3]: *** [/var/lib/dkms/realtek-r8168/8.036.00/build/src/r8168_n.o] Error 
1
  make[2]: *** [_module_/var/lib/dkms/realtek-r8168/8.036.00/build/src] Error 2
  make[2]: Leaving directory `/usr/src/linux-headers-3.2.0-40-generic'
  make[1]: *** [modules] Error 2
  make[1]: Leaving directory `/var/lib/dkms/realtek-r8168/8.036.00/build/src'
  make: *** [modules] Error 2
  [/quote]

  Same goes for most recent available packaged kernel v3.2.0-57-generic.

  I have replaced the source in /usr/src/realtek-r8168-8.036.00/ with the most 
recent version (8.037.00) from Realtek's driver site:
  
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PNid=13PFid=5Level=5Conn=4DownTypeID=3GetDown=false#2

  
  Compiling v8.037.00 worked fine. The generated module (r8168) installs and 
loads fine.
  The wired network problem however, persists.

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

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

[Kernel-packages] [Bug 1260513] Re: horizontal scrolling is broken with some external mouse devices

Val, could you please unplug all USB devices from your computer, plug in only 
the problematic USB device, immediately place the following in a terminal and 
attach the uncompressed results:
lsusb -v  lsusb-v.log

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

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

** Summary changed:

- horizontal scrolling is broken with some external mouse devices
+ horizontal scrolling is broken with specific external mouse device

** Description changed:

- Submitting my hardware info in a sequel to LP #975724.
+ horizontal scrolling is broken with specific external mouse device.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15 [modified: 
boot/vmlinuz-3.12.0-7-generic]
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  val2055 F pulseaudio
-  /dev/snd/controlC1:  val2055 F pulseaudio
-  /dev/snd/controlC0:  val2055 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  val2055 F pulseaudio
+  /dev/snd/controlC1:  val2055 F pulseaudio
+  /dev/snd/controlC0:  val2055 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
-  [   18.719163] r8169 :04:00.0 eth0: link down
-  [   18.719209] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
-  [   18.719405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
-  [   20.803774] r8169 :04:00.0 eth0: link up
-  [   20.803781] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
+  [   18.719163] r8169 :04:00.0 eth0: link down
+  [   18.719209] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
+  [   18.719405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
+  [   20.803774] r8169 :04:00.0 eth0: link up
+  [   20.803781] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Thu Dec 12 17:03:45 2013
  HibernationDevice: RESUME=UUID=ac145c0d-f41b-4f64-9a96-1ca3b10a8b72
  InstallationDate: Installed on 2013-12-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131212)
  IwConfig:
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
+  eth0  no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: Gateway DX4860
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic.efi.signed 
root=UUID=e0d98c7c-d44d-4f1c-9754-aac8b034e434 ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-3.12.0-7-generic N/A
-  linux-backports-modules-3.12.0-7-generic  N/A
-  linux-firmware1.117
+  linux-restricted-modules-3.12.0-7-generic N/A
+  linux-backports-modules-3.12.0-7-generic  N/A
+  linux-firmware1.117
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A3
  dmi.board.name: DX4860
  dmi.board.vendor: Gateway
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd04/19/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnDX4860:rvr:cvnGateway:ct3:cvr:
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway

** Summary changed:

- horizontal scrolling is broken with specific external mouse device
+ [Gateway DX4860] Horizontal scrolling is broken with specific external mouse 
device

** Tags added: needs-upstream-testing regression-potential

** Tags added: needs-lsusbv

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

Title:
  [Gateway DX4860] Horizontal scrolling is broken with specific external
  mouse device

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  horizontal scrolling is broken with specific external mouse device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15 [modified: 
boot/vmlinuz-3.12.0-7-generic]
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  val2055 F pulseaudio
   /dev/snd/controlC1:  val2055 F pulseaudio
   /dev/snd/controlC0:  val2055 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   [   18.719163] r8169 :04:00.0 eth0: link down
   [   18.719209] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   18.719405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   20.803774] r8169 :04:00.0 eth0: link up
   [   20.803781] IPv6: ADDRCONF(NETDEV_CHANGE): eth0

[Kernel-packages] [Bug 975724] Re: 045e:071d [System76 gazp6] External mouse horizontal scrolling no longer works

** Summary changed:

- 045e:071d External mouse horizontal scrolling no longer works
+ 045e:071d [System76 gazp6] External mouse horizontal scrolling no longer 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/975724

Title:
  045e:071d [System76 gazp6] External mouse horizontal scrolling no
  longer works

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using a microsoft 7000 wireless desktop mouse (ID 045e:071d) -- the
  mouse has a 4 way scroll wheel; worked perfect in 11.10 but with 12.04
  beta2 the horizontal scroll now is seen as normal up/down scrolling
  instead of left/right.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-22-generic 3.2.0-22.35
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 00:29:55 2012
  HibernationDevice: RESUME=UUID=2164a001-0008-4d63-8be3-70b52dce6ae0
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: System76, Inc. Gazelle Professional
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic 
root=UUID=0a3757f8-285c-4621-af39-1735173628af ro quiet splash vt.handoff=7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp6
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp6
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1025283] Re: [Dell Precision T7600] LiveCD/USB will not boot in UEFI mode

Douglas Russell, as per 
http://www.dell.com/support/drivers/us/en/19/Product/precision-t7600 an update 
is available for your BIOS (A10). If you update to this following 
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

Thank you for your understanding.

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

** Tags added: saucy

** Attachment removed: AcpiTables.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472736/+files/AcpiTables.txt

** Attachment removed: AplayDevices.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472738/+files/AplayDevices.txt

** Attachment removed: AlsaDevices.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472737/+files/AlsaDevices.txt

** Attachment removed: ArecordDevices.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472739/+files/ArecordDevices.txt

** Attachment removed: BootDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472740/+files/BootDmesg.txt

** Attachment removed: Card0.Amixer.values.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472741/+files/Card0.Amixer.values.txt

** Attachment removed: Card1.Amixer.values.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472743/+files/Card1.Amixer.values.txt

** Attachment removed: Card0.Codecs.codec.0.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472742/+files/Card0.Codecs.codec.0.txt

** Attachment removed: Card1.Codecs.codec.0.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472744/+files/Card1.Codecs.codec.0.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472745/+files/CurrentDmesg.txt

** Attachment removed: Lspci.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472746/+files/Lspci.txt

** Attachment removed: Lsusb.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472747/+files/Lsusb.txt

** Attachment removed: PciMultimedia.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472748/+files/PciMultimedia.txt

** Attachment removed: ProcCpuinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472749/+files/ProcCpuinfo.txt

** Attachment removed: ProcInterrupts.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472750/+files/ProcInterrupts.txt

** Attachment removed: ProcModules.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472751/+files/ProcModules.txt

** Attachment removed: UdevDb.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472752/+files/UdevDb.txt

** Attachment removed: UdevLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472753/+files/UdevLog.txt

** Attachment removed: WifiSyslog.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3472754/+files/WifiSyslog.txt

** Attachment removed: lspci-output.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025283/+attachment/3225014/+files/lspci-output.txt

** Description changed:

- I tried to boot from the LiveCD in UEFI mode as I wished to install my
- UEFI capable workstation in UEFI + GPT mode.
- 
- If I boot in legacy mode, it boots up without a problem but of course,
- does not allow me to install in UEFI mode.
- 
- I get the following error over and over:
- 
- udevd[114]: timeout: killing `/sbin/modprobe -bv
- pci:v1000d0073sv1028sd1F78bc01sc04i00' [182]
+ I tried to boot from the LiveCD in UEFI mode as I wished to install my UEFI 
capable workstation in UEFI + GPT mode. If I boot in legacy mode, it boots up 
without a problem but of course, does not allow me to install in UEFI mode. 
Seems to perhaps indicate that the disk controller is having a problem. It's a 
Dell PERC H310. I get the following error over and over:
+ udevd[114]: timeout: killing `/sbin/modprobe -bv 
pci:v1000d0073sv1028sd1F78bc01sc04i00' [182]
  
  Then finally:
+ udevadm settle - timeout of 120 seconds reached, the event queue contains:
+   /sys/devices/pci:00/:00:03.0/:06:00.0 (1588)
+   /sys/devices/pci:00/:00:03.0/:06:00.0/host6 (1588)
+   /sys/devices/pci:00/:00:03.0/:06:00.0/host6/scsi_host/host6 
(1588)
  
- udevadm settle - timeout of 120 seconds reached, the event queue contains:
-   /sys/devices/pci:00/:00:03.0/:06:00.0 (1588)
-   /sys/devices/pci:00/:00:03.0/:06:00.0/host6 (1588)
-

[Kernel-packages] [Bug 1024507] Re: [Radeon HD 4670] 12.10 quantal boots to black screen on iMac

Peter T Hayward, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For
example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next
to the word Tags located at the bottom of the bug description. As well, please
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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.

** Description changed:

Running 12.10, updated today, on iMac 11,2 (mid 2010) with AMD Radeon 4670.
- Using kernel radeon driver (lsmod shows it running).
- Normal boot results in black screen. Ctl-Alt-Del reboots; indicating that
system did boot.
- If I place 'nomodeset' on kernel command line, main screen can be seen and
unity desktop runs normally.
+ Using kernel radeon driver (lsmod shows it running). Normal boot results in
black screen. Ctl-Alt-Del reboots; indicating that system did boot. This
appears to be a regression in the kernel, similar to bug 597070 (ubuntu 11.04 -
used fglrx to get video to work) and to bug 863969 (ubuntu 11.10 - where an
upgrade to the 3.2 kernel seemed to improve video detection). Suspend and
resume does not work either, not turning off the system, only the video, and
resuming to a black screen. I think the problem is in KMS, because the black
screen happens even if I boot into text mode and using nomodeset fixes it.
Hence filing this against xorg but expect it to go to kernel developers.

- This appears to be a regression in the kernel, similar to bug 597070 (ubuntu
11.04 - used fglrx to get video to work) and to bug 863969 (ubuntu 11.10 -
where an upgrade to the 3.2 kernel seemed to improve video detection).
- Suspend and resume does not work either, not turning off the system, only the
video, and resuming to a black screen.
-
- I think the problem is in KMS, because the black screen happens even if
- I boot into text mode and using nomodeset fixes it. Hence filing this
- against xorg but expect it to go to kernel developers.
+ WORKAROUND: Use kernel parameter nomodeset.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
.tmp.unity.support.test.1:

ApportVersion: 2.3-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jul 13 19:12:16 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes,
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI RV730 XT [Mobility Radeon HD 4670]
[1002:9488] (prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device [106b:00b6]
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64+mac (20120509)
MachineType: Apple Inc. iMac11,2
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: vmlinuz-3.5.0-4-generic
root=UUID=268e7eb7-d871-478c-a906-b719eea881ea ro nosplash nomodeset
initrd=EFI\ubuntu\initrd.img-3.5.0-4-generic
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/11
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM112.88Z.0057.B01.1112090906
dmi.board.name: Mac-F2238AC8
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F2238AC8
dmi.modalias:
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B01.1112090906:bd12/09/11:svnAppleInc.:pniMac11,2:pvr1.0:rvnAppleInc.:rnMac-F2238AC8:rvr:cvnAppleInc.:ct13:cvrMac-F2238AC8:
dmi.product.name: iMac11,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2:

[Kernel-packages] [Bug 1016457] Re: Ctrl+Alt+F1 doesn't show virtual terminal

** Tags added: bios-outdated-306

** Summary changed:

- Ctrl+Alt+F1 doesn't show virtual terminal
+ 10de:0405 [Asus M51Sn] Ctrl+Alt+F1 doesn't show virtual terminal

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

Title:
  10de:0405 [Asus M51Sn] Ctrl+Alt+F1 doesn't show virtual terminal

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Normally, Ctrl+Alt+F1, Ctrl+Alt+F2, etc... would switch to a virtual
  terminal or console or whatever it is called.

  Starting from recently, it only shows a black screen.

  Ctrl+Alt+F7 switch back to xorg as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-26-generic 3.2.0-26.41
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo2443 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
 Mixer name : 'Realtek ALC660-VD'
 Components : 'HDA:10ec0660,1043,0011 
HDA:10573055,10431316,00100700'
 Controls  : 28
 Simple ctrls  : 16
  Date: Fri Jun 22 11:59:58 2012
  HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-26-generic N/A
   linux-backports-modules-3.2.0-26-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to precise on 2012-05-17 (35 days ago)
  UserAsoundrc:
   pcm.!default { type pulse }
   ctl.!default { type pulse }
   pcm.pulse { type pulse }
   ctl.pulse { type pulse }
  WifiSyslog:
   
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  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/1016457/+subscriptions

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

[Kernel-packages] [Bug 1045813] Re: SONY Vaio VGN-CS11S touchpad primary button not working with lm-sensors and nvidia-current / nouveau

2013-12-12 Thread Khlood Elsayed

I no longer have access to this laptop. Hence, as the original reporter
I consider this report closed.

** No longer affects: xorg (Ubuntu)

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

Title:
  SONY Vaio VGN-CS11S touchpad primary button not working with lm-
  sensors and nvidia-current / nouveau

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu quantal (development branch)
  Release:  12.10

  2) apt-cache policy xorg
  xorg:
    Installed: 1:7.7+1ubuntu3
    Candidate: 1:7.7+1ubuntu3
    Version table:
   *** 1:7.7+1ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy nvidia-current
  nvidia-current:
    Installed: (none)
    Candidate: 304.43-0ubuntu2
    Version table:
   304.43-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ quantal/restricted i386 
Packages
  100 /var/lib/dpkg/status

  xserver-xorg-video-nouveau:
    Installed: 1:1.0.1-4~ubuntu1
    Candidate: 1:1.0.1-4~ubuntu1
    Version table:
   *** 1:1.0.1-4~ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
  100 /var/lib/dpkg/status

  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98
  [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller])

  3) What is expected to happen is when one:
  + installs nvidia-current, restarts, and login
  + uses xserver-xorg-video-nouveau

  the touchpad works.

  4) What happens instead is:
  + with nivida-current the primary button does not work at all,
  + with xserver-xorg-video-nouveau the primary button stops working after a 
period of inactivity or until Firefox is open (especially with flash content).

  Neither is resolved using an external mouse. The cursor may be moved
  around with the touchpad or the external mouse, and the secondary
  button works as well.

  Hence, this touchpad problem is correlated to a bug in X. THe problem
  in nouveau was also present in Precise.

  All attachments are provided when nvidia-current was still installed
  and my following https://wiki.ubuntu.com/DebuggingTouchpadDetection .

  cat /proc/bus/input/devices :
  I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
  N: Name=SynPS/2 Synaptics TouchPad
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input11
  U: Uniq=
  H: Handlers=mouse2 event11
  B: PROP=1
  B: EV=b
  B: KEY=420 0 3 0 0 0 0 0 0 0 0
  B: ABS=1103

  xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sony Vaio Keys  id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ UVC Camera (05ca:183f)  id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]

  Reproducible in mainline kernel:
  uname -a
  Linux computer 3.6.0-030600rc4-generic #201209011435 SMP Sat Sep 1 18:42:50 
UTC 2012 i686 i686 i686 GNU/Linux

  WORKAROUND: Uninstall lm-sensors.
  apt-cache policy lm-sensors
  lm-sensors:
    Installed: (none)
    Candidate: 1:3.3.1-2ubuntu1
    Version table:
   1:3.3.1-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ quantal/universe i386 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: i386
  Date: Tue Sep  4 08:50:37 2012
  InstallationMedia: Xubuntu 12.04 Precise Pangolin - Alpha i386 (20120131.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to quantal on 2012-09-04 (0 days ago)
  --- 
  AcpiTables: Error: command ['pkexec', 
'/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error 
executing /usr/share/apport/dump_acpi_tables.py: Permission denied
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:

[Kernel-packages] [Bug 1010854] Re: linux-crashdump not producing coredump nor rebooting

Christoph Paasch, as per 
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/?sp4ts.oid=4096169spf_p.tpst=swdMainspf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D4060%257CswLang%253D%257Caction%253DlistDriverjavax.portlet.begCacheTok=com.vignette.cachetokenjavax.portlet.endCacheTok=com.vignette.cachetoken#BIOS
 an update is available for your BIOS (F.0F). If you update to this following 
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

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

Thank you for your understanding.

** Tags added: bios-outdated-f.0f

** Tags removed: quantal

** Tags added: raring

** Attachment removed: AlsaInfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626585/+files/AlsaInfo.txt

** Attachment removed: BootDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626586/+files/BootDmesg.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626588/+files/CurrentDmesg.txt

** Attachment removed: CRDA.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626587/+files/CRDA.txt

** Attachment removed: IwConfig.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626589/+files/IwConfig.txt

** Attachment removed: Lspci.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626590/+files/Lspci.txt

** Attachment removed: ProcInterrupts.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626592/+files/ProcInterrupts.txt

** Attachment removed: ProcCpuinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626591/+files/ProcCpuinfo.txt

** Attachment removed: ProcModules.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626593/+files/ProcModules.txt

** Attachment removed: UdevDb.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626595/+files/UdevDb.txt

** Attachment removed: RfKill.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626594/+files/RfKill.txt

** Attachment removed: UdevLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626596/+files/UdevLog.txt

** Attachment removed: WifiSyslog.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1010854/+attachment/3626597/+files/WifiSyslog.txt

** Tags added: regression-release

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

** Summary changed:

- linux-crashdump not producing coredump nor rebooting
+ [HP EliteBook 8540p] linux-crashdump not producing coredump nor rebooting

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

Title:
  [HP EliteBook 8540p] linux-crashdump not producing coredump nor
  rebooting

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  since Ubuntu Precise, linux-crashdump isn't working anymore for me.
  When I trigger a crash with
  echo 'c'  /proc/sysrq-trigger

  the machine freezes. I see the disk-light blinking for a short time.
  But then, the host does not reboot automatically, and no dump-file is
  in /var/crash.

  With Oneiric everything worked as expected.

  
  How can I provide more debugging info to you?

  Thanks,
  Christoph
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu9
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christoph   3120 F pulseaudio
   /dev/snd/controlC0:  christoph   3120 F pulseaudio
  CRDA:
   country BE:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd752 irq 54'
 Mixer name : 'IDT 92HD75B3X5'
 Components : 'HDA:111d7603,103c1521,00100202 
HDA:11c11040,103c3066,00100200'
 Controls  : 19
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 16'
 Mixer name : 'Nvidia GPU 0a HDMI/DP'
 Components : 'HDA:10de000a,10de0101,00100100'

[Kernel-packages] [Bug 1005804] Re: [R210 II] Deadlock in hid_reset when Dell iDRAC is reset

Sven Hoexter, the upstream fix patch noted in 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670398#141 has been applied to 
Lucid-Trusty:
Trusty 
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commit;h=e22bee782b3b00bd4534ae9b1c5fb2e8e6573c5c

Please reopen if this is still an issue for you.

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

Title:
  [R210 II] Deadlock in hid_reset when Dell iDRAC is reset

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

Bug description:
  Hi,

  thanks to the help of Ben Hutchings we've found an issue with several
  low end Dell servers which is beeing tracked in Debian bug
  http://bugs.debian.org/670398

  Since we see the same issue on Dell R210 II with Ubuntu 10.04 (which
  is aswell Linux 2.6.32 based) and
  http://www.ubuntu.com/certification/hardware/201107-8313/ claims
  that's supported hardware, it would be great if you could take a look
  at the proposed fix aswell.

  
  You can reproduce the issue easily when issuing a 'racadm racreset' via SSH 
on the included iDRAC 6 KVM card. You'll afterwards
  see one of the [events/$x] processes of the kernel in state D and interaktive 
logins on the operating system will no longer
  work. You can still connect with 'ssh -T'.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-41-server 2.6.32-41.89
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-41.89-server 2.6.32.59+drm33.24
  Uname: Linux 2.6.32-41-server x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [6.801456] bnx2: eth0 NIC Copper Link is Up, 100 Mbps full duplex, 
receive  transmit flow control ON
   [6.801756] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   17.757322] eth0: no IPv6 routers present
  Date: Tue May 29 10:07:24 2012
  MachineType: Dell Inc. PowerEdge R210 II
  PciMultimedia:
   
  ProcCmdLine: root=/dev/mapper/vg0-root ro rootdelay=300
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux
  dmi.bios.date: 07/21/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09T7VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd07/21/2011:svnDellInc.:pnPowerEdgeR210II:pvr:rvnDellInc.:rn09T7VV:rvrA02:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R210 II
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 999946] Re: Kernel outputs lots of warning of the form [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 10.

agenkin, This bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please just make a comment to this.

** Description changed:

  On a Supermicro X7SB4 based system the kernel outputs a host of error
  messages of the form:
  
  [  713.444010] ghes_read_estatus: 11 callbacks suppressed
  [  713.444014] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 10.
  [  713.520005] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 10.
  [  713.836007] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 9.
  [  714.476007] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 10.
  [  714.556005] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 10.
  [  715.236008] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 9.
  [  715.444005] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 10.
  [  715.556005] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 10.
  [  715.756006] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 9.
  [  716.236007] [Firmware Warn]: GHES: Failed to read error status block 
address for hardware error source: 9.
  
- This happens with 32-bit kernels (both -pae and non-pae).
+ This happens with 32-bit kernels (both -pae and non-pae). This may or
+ may not be a duplicate of bug 881164 (this is for a Precise kernel and
+ the hardware is not Dell PowerEdge).
  
- This may or may not be a duplicate of bug 881164 (this is for a Precise
- kernel and the hardware is not Dell PowerEdge).
+ WORKAROUND: Use kernel parameter:
+ ghes.disable=1
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  AlsaDevices:
-  total 0
-  crw-rw---T 1 root audio 116,  1 May 15 17:12 seq
-  crw-rw---T 1 root audio 116, 33 May 15 17:12 timer
+  total 0
+  crw-rw---T 1 root audio 116,  1 May 15 17:12 seq
+  crw-rw---T 1 root audio 116, 33 May 15 17:12 timer
  AplayDevices: aplay: device_list:252: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: arecord: device_list:252: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue May 15 17:20:09 2012
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro X7SB4/E
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm
-  SHELL=/bin/bash
+  TERM=xterm
+  SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: root=/dev/sda1 ro
  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.2.0-24-generic-pae N/A
-  linux-backports-modules-3.2.0-24-generic-pae  N/A
-  linux-firmware1.79
+  linux-restricted-modules-3.2.0-24-generic-pae N/A
+  linux-backports-modules-3.2.0-24-generic-pae  N/A
+  linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.2a
  dmi.board.name: X7SB4/E
  dmi.board.vendor: Supermicro
  dmi.board.version: PCB Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.2a:bd12/19/2008:svnSupermicro:pnX7SB4/E:pvr0123456789:rvnSupermicro:rnX7SB4/E:rvrPCBVersion:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: X7SB4/E
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

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

Title:
  Kernel outputs lots of warning of the form [Firmware Warn]: GHES:
  Failed to read error status block address for hardware error source:
  10.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  On a Supermicro X7SB4 based system the kernel outputs a

[Kernel-packages] [Bug 1005063] Re: [Toshiba Satellite A205-S5000] USB headset crashes X

Chip VanDan, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications-Accessories-Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux replace-with-bug-number

Also, could you please test the latest upstream kernel available (not the daily 
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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.

** Summary changed:

- USB headset crashes X
+ [Toshiba Satellite A205-S5000] USB headset crashes X

** Tags added: latest-bios-2.60 needs-lsusbv needs-upstream-testing

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

Title:
  [Toshiba Satellite A205-S5000] USB headset crashes X

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This originally happened with my USB mouse, but somehow it doesn't
  happen anymore, but the exact same thing still happens when I plug in
  a Plantronics USB headset.

  When I plug in the USB headset everything quits out and I'm left with
  a black screen that lists a few things about setting IRQ priorities,
  but most importantly it states Stopping System V Runlevel
  compatibilit[OK]

  Once I remove the device it lists a bunch of identical error messages
  about generic-usb, with the hardware address, and states that it can't
  reset the device.

  If I try to boot with the USB headset plugged in I see the boot splash
  image, then it kicks me back to TTY1.

  In all cases I'm able to restart XFCE with sudo service lightdm
  restart but everything I was running at the time of the crash has
  been closed.  There are no logs in /var/crash, and .xsession-errors
  doesn't list anything new after the crash, and dmesg has no new output
  during the crash.  The only trace that anything has crashed was found
  in /var/log/syslog, which I've pasted here:
  http://pastebin.com/cNTrYBG1

  A little background, I recently wiped 10.04 from my Toshiba Satellite
  A205 to install 12.04, the USB headset was working well before the
  upgrade.  The LiveDVD will not run with the headset plugged in either.
  After the crash I am able to switch to TTY1 and run lsusb and see that
  Plantronics IS listed there.  Help troubleshooting this problem would
  be appreciated as I'm out of ideas.  I tried asking the question on
  AskUbuntu at Stack Exchange, but was referred to Launchpad:
  http://askubuntu.com/questions/124042/plugging-in-usb-mouse-or-usb-
  headset-crashes-xserver-in-fresh-install-of-12-04

  I'm not entirely convinced this is a bug since I'm unable to find anybody 
else having similar symptoms.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  airlynx1780 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 48'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,1179ff02,0013 
HDA:11c11040,11790001,00100200'
 Controls  : 16
 Simple ctrls  : 9
  Card1.Amixer.info:
   Card hw:1 'Interface'/'M-Audio

[Kernel-packages] [Bug 994560] Re: unknown screen mutations raised from language charset

Jiří Podvolecký, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily 
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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: needs-upstream-testing regression-potential

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

Title:
  unknown screen mutations raised from language charset

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  There are unknown pictures after useing dosbox. Sometime system shows
  bad language charset ( my is Czech ). More info in picture in
  attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', 'env', '-u', 
'LANGUAGE', 'LC_MESSAGES=C', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 255:
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jirka  1765 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'CA0106'/'MSI K8N Diamond MB [SB0438] at 0xde00 irq 16'
 Mixer name : 'CA0106'
 Components : ''
 Controls  : 30
 Simple ctrls  : 18
  Date: Fri May  4 14:41:56 2012
  HibernationDevice: RESUME=UUID=11ebc19e-940f-46d9-aa79-6fba5ccbe684
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 003: ID 13fe:3800 Kingston Technology Company Inc. Rage XT 
Flash Drive
   Bus 002 Device 002: ID 045e:0083 Microsoft Corp. Basic Optical Mouse
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100
  ProcEnviron:
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=57895cf7-c98b-4dbd-8225-e16dc7f690f8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/17/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr:
  dmi.product.name: MS-7100
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 993245] Re: Hard Disk cycles on and off

** Description changed:

  I just installed Xubuntu 12.04 (i386) (fresh install) on my Toshiba Satellite 
Pro L-350 (Canadian).
  I noticed that when the laptop is running on the battery alone, the Hard 
Drive turns on and off every 30 seconds. This happens continously and doesn't 
stop. I can actually hear the click of the hard drive turning on, and it 
coincides with a spike in System Monitor for the Hard Drive being written 
once.
  On A/C power the hard drive doesn't turn on and off and it remains ON all the 
time. But the 30 second write spike in System Monitor still happens.
  I just installed Xubuntu and this is observable by me not doing anything to 
the computer and just watching the System Monitor and hearing the HDD after 
boot.
  In Power Management, the option for Spin down hard disk is ticked off for 
both On AC and On Battery.
  
  Please let me know if more information needs to be provided and the means 
through which I can provide it.
  Cheers!
- --- 
+ ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
-   List of PLAYBACK Hardware Devices 
-  card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
-Subdevices: 1/1
-Subdevice #0: subdevice #0
+   List of PLAYBACK Hardware Devices 
+  card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
+    Subdevices: 1/1
+    Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices:
-   List of CAPTURE Hardware Devices 
-  card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
-Subdevices: 1/1
-Subdevice #0: subdevice #0
+   List of CAPTURE Hardware Devices 
+  card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
+    Subdevices: 1/1
+    Subdevice #0: subdevice #0
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  shape  1575 F xfce4-volumed
-   shape  1592 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  shape  1575 F xfce4-volumed
+   shape  1592 F pulseaudio
  Card0.Amixer.info:
-  Card hw:0 'Intel'/'HDA Intel at 0x9640 irq 46'
-Mixer name : 'Realtek ALC268'
-Components : 'HDA:10ec0268,1179ff64,0013 
HDA:11c11040,11790001,00100200'
-Controls  : 16
-Simple ctrls  : 9
+  Card hw:0 'Intel'/'HDA Intel at 0x9640 irq 46'
+    Mixer name : 'Realtek ALC268'
+    Components : 'HDA:10ec0268,1179ff64,0013 
HDA:11c11040,11790001,00100200'
+    Controls  : 16
+    Simple ctrls  : 9
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0d808d75-7d23-4961-9088-4e2d9ed531cf
  InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MachineType: TOSHIBA Satellite L350
  Package: linux (not installed)
  ProcEnviron:
-  LANGUAGE=en_CA:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_CA.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_CA:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=87cd5825-1aea-441d-b413-dabf255f6586 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  RelatedPackageVersions:
-  linux-restricted-modules-3.2.0-24-generic N/A
-  linux-backports-modules-3.2.0-24-generic  N/A
-  linux-firmware1.79
+  linux-restricted-modules-3.2.0-24-generic N/A
+  linux-backports-modules-3.2.0-24-generic  N/A
+  linux-firmware1.79
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  Tags:  precise precise
  Uname: Linux 3.2.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL350:pvrPSLD0C-03N08C:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Satellite L350
  dmi.product.version: PSLD0C-03N08C
  dmi.sys.vendor: TOSHIBA
- --- 
- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
- AplayDevices:
-   List of PLAYBACK Hardware Devices 
-  card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
-Subdevices: 1/1
-Subdevice #0: subdevice #0
- ApportVersion: 2.0.1-0ubuntu7
- Architecture: i386
- ArecordDevices:
-

[Kernel-packages] [Bug 993245] Re: Hard Disk cycles on and off

Gigel Vecina, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily 
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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-1.50 needs-upstream-testing

** Summary changed:

- Hard Disk cycles on and off
+ [Toshiba Satellite L350] Hard Disk cycles on and off

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

Title:
  [Toshiba Satellite L350] Hard Disk cycles on and off

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I just installed Xubuntu 12.04 (i386) (fresh install) on my Toshiba Satellite 
Pro L-350 (Canadian).
  I noticed that when the laptop is running on the battery alone, the Hard 
Drive turns on and off every 30 seconds. This happens continously and doesn't 
stop. I can actually hear the click of the hard drive turning on, and it 
coincides with a spike in System Monitor for the Hard Drive being written 
once.
  On A/C power the hard drive doesn't turn on and off and it remains ON all the 
time. But the 30 second write spike in System Monitor still happens.
  I just installed Xubuntu and this is observable by me not doing anything to 
the computer and just watching the System Monitor and hearing the HDD after 
boot.
  In Power Management, the option for Spin down hard disk is ticked off for 
both On AC and On Battery.

  Please let me know if more information needs to be provided and the means 
through which I can provide it.
  Cheers!
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shape  1575 F xfce4-volumed
    shape  1592 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9640 irq 46'
     Mixer name : 'Realtek ALC268'
     Components : 'HDA:10ec0268,1179ff64,0013 
HDA:11c11040,11790001,00100200'
     Controls  : 16
     Simple ctrls  : 9
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0d808d75-7d23-4961-9088-4e2d9ed531cf
  InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MachineType: TOSHIBA Satellite L350
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=87cd5825-1aea-441d-b413-dabf255f6586 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  Tags:  precise precise
  Uname: Linux 3.2.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/10/2008

[Kernel-packages] [Bug 980925] Re: load avg is near to 1.00 even in case of idle

LGB [Gábor Lénárt], as per 
http://www.gigabyte.com/products/product-page.aspx?pid=3773#bios an update is 
available for your BIOS (F10). If you update to this following 
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

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

Thank you for your understanding.

** Tags added: bios-outdated-f10

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

Title:
  load avg is near to 1.00 even in case of idle

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Cpu(s):  0.6%us,  0.2%sy,  0.0%ni, 99.2%id,  0.0%wa,  0.0%hi,  0.0%si,
  0.0%st

  Still, the load average is always near to 1.00. in long term being
  idle-state too.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-23-generic-pae 3.2.0-23.36
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC889 Analog [ALC889 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lgb1896 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfbff8000 irq 43'
 Mixer name : 'Realtek ALC889'
 Components : 'HDA:10ec0889,1458a002,0014'
 Controls  : 37
 Simple ctrls  : 20
  CurrentDmesg:
   [   31.945406] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   35.415818] init: plymouth-stop pre-start process (1565) terminated with 
status 1
   [   42.912366] eth0: no IPv6 routers present
  Date: Fri Apr 13 17:28:04 2012
  HibernationDevice: RESUME=UUID=ef613937-3143-4b4f-9abd-a0daa53ac12f
  InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 
(20100816.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 003: ID 1267:0213 Logic3 / SpectraVideo plc
  MachineType: Gigabyte Technology Co., Ltd. H61M-D2-B3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic-pae 
root=UUID=4781446b-537b-4ed1-8e36-707369788c63 ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic-pae N/A
   linux-backports-modules-3.2.0-23-generic-pae  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: Upgraded to precise on 2012-03-01 (42 days ago)
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H61M-D2-B3
  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.:bvrF4:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-D2-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-D2-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H61M-D2-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1260313] Re: No external microphone detected on the machines with codec Subsystem ID0x10280629

Set this bug to invalid since we use #1260303 to track the same problem.

** Changed in: hwe-next
   Status: Triaged = Invalid

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

** Tags removed: blocks-hwcert-enablement

** Changed in: hwe-next
 Assignee: Hui Wang (hui.wang) = (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Hui Wang (hui.wang) = (unassigned)

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

Title:
  No external microphone detected on the machines with codec Subsystem
  ID0x10280629

Status in HWE Next Project:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Steps:
  1. boot into OS
  2. Plugin a 3-ring headset into the headset port
  3. Go to sound setting  input tab and check if external mic is detected
  4. Launch sound recorder and try to record sound from external mic

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

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

[Kernel-packages] [Bug 1260306] Re: No external microphone detected on the machines with codec Subsystem ID0x1028063e

We close this defect since we use the #1260303 to track the same
problem.

** Changed in: hwe-next
   Status: Triaged = Invalid

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

** Changed in: hwe-next
 Assignee: Hui Wang (hui.wang) = (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Hui Wang (hui.wang) = (unassigned)

** Tags removed: blocks-hwcert-enablement

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

Title:
  No external microphone detected on the machines with codec Subsystem
  ID0x1028063e

Status in HWE Next Project:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Steps:
  1. boot into OS
  2. Plugin a 3-ring headset into the headset port
  3. Go to sound setting  input tab and check if external mic is detected
  4. Launch sound recorder and try to record sound from external mic

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

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

[Kernel-packages] [Bug 1260303] Re: No external microphone detected on the machines with codec Subsystem ID0x10280610

The machine Subsystem ID is: 0x10280610, 0x1028063e, 0x10280629

** Summary changed:

- No external microphone detected on the machines with codec Subsystem 
ID0x10280610 
+ No external microphone detected on the machines with codec alc269 family

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

Title:
  No external microphone detected on the machines with codec alc269
  family

Status in HWE Next Project:
  Triaged
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Steps:
  1.  boot into OS
  2. Plugin a 3-ring headset into the headset port
  3. Go to sound setting  input tab and check if external mic is detected
  4. Launch sound recorder and try to record sound from external mic

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

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

[Kernel-packages] [Bug 1260513] Re: [Gateway DX4860] Horizontal scrolling is broken with specific external mouse device

Christopher,

My USB listing is attached. As you requested, I unplugged all USB
devices first, then plugged in the mouse device (note important details
below) and then executed lsusb -v, with sudo of course.

Please note that this problem is specific to the mouse, not to Gateway
DX4860. This computer system came with its own two-button mouse which I
immediately replaced with 9-button Microsoft Wireless Laser Mouse 5000.
To be precise, this mouse is part of a mouse+keyboard combo. The
accompanying keyboard device is Microsoft Wireless Comfort Keyboard
4000. Both mouse and keyboard are wirelessly connected to the same USB
transceiver. It is the USB transceiver device that I unplugged and then
plugged back before executing lsusb -v.

I should perhaps note again, just for the record under this bug report,
that the proposed fix in LP: # 926917 worked perfectly for me on LTS
12.04, completely fixing the problem with horizontal scrolling.

** Attachment added: lsusb-v.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260513/+attachment/3928466/+files/lsusb-v.log

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

Title:
  [Gateway DX4860] Horizontal scrolling is broken with specific external
  mouse device

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  horizontal scrolling is broken with specific external mouse device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15 [modified: 
boot/vmlinuz-3.12.0-7-generic]
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  val2055 F pulseaudio
   /dev/snd/controlC1:  val2055 F pulseaudio
   /dev/snd/controlC0:  val2055 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   [   18.719163] r8169 :04:00.0 eth0: link down
   [   18.719209] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   18.719405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   20.803774] r8169 :04:00.0 eth0: link up
   [   20.803781] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Thu Dec 12 17:03:45 2013
  HibernationDevice: RESUME=UUID=ac145c0d-f41b-4f64-9a96-1ca3b10a8b72
  InstallationDate: Installed on 2013-12-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131212)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gateway DX4860
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic.efi.signed 
root=UUID=e0d98c7c-d44d-4f1c-9754-aac8b034e434 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A3
  dmi.board.name: DX4860
  dmi.board.vendor: Gateway
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd04/19/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnDX4860:rvr:cvnGateway:ct3:cvr:
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.

2013-12-12 Thread Paulo Andres Jara Santibanez

using the series 3.2.0-xx of kernel on my Ubuntu 12.04.03 the system
just get stuck at ubuntu's dots screen every 4 or 5 boot, nothing works,
not even keyboard  just it is posible turn off by a hard reset.

My system also uses  :compiz-fusion- 0.9.7.0~bzr9-0 transitional dummy package.
   :compiz 1:0.9.7.12-0ub OpenGL 
window and compositing manager

After upgrade the kernel to  3.5.0-37-generic #58~precise1-Ubuntu SMP Wed Jul 
10 17:48:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux, 
all things was going better...  
from this upgrade,  system run well and don't stuck at boot or hangs.

all machine specs:

descripción: Computer
anchura: 64 bits
capacidades: vsyscall32
  *-core
   descripción: Motherboard
   id físico: 0
 *-memory
  descripción: Memoria de sistema
  id físico: 0
  tamaño: 7881MiB
 *-cpu
  producto: Intel(R) Core(TM) i3-2328M CPU @ 2.20GHz
  fabricante: Intel Corp.
  id físico: 1
  información del bus: cpu@0
  tamaño: 800MHz
  capacidad: 800MHz
  anchura: 64 bits
  capacidades: fpu fpu_exception wp 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 x86-64 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 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
xsave avx lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority 
ept vpid cpufreq
 *-pci
  descripción: Host bridge
  producto: 2nd Generation Core Processor Family DRAM Controller
  fabricante: Intel Corporation
  id físico: 100
  información del bus: pci@:00:00.0
  versión: 09
  anchura: 32 bits
  reloj: 33MHz
*-display
 descripción: VGA compatible controller
 producto: 2nd Generation Core Processor Family Integrated Graphics 
Controller
 fabricante: Intel Corporation
 id físico: 2
 información del bus: pci@:00:02.0
 versión: 09
 anchura: 64 bits
 reloj: 33MHz
 capacidades: vga_controller bus_master cap_list rom
 configuración: driver=i915 latency=0
 recursos: irq:43 memoria:5200-523f 
memoria:4000-4fff ioport:4000(size=64)
*-communication
 descripción: Communication controller
 producto: 7 Series/C210 Series Chipset Family MEI Controller #1
 fabricante: Intel Corporation
 id físico: 16
 información del bus: pci@:00:16.0
 versión: 04
 anchura: 64 bits
 reloj: 33MHz
 capacidades: bus_master cap_list
 configuración: driver=mei latency=0
 recursos: irq:44 memoria:52604000-5260400f
*-usb:0
 descripción: USB controller
 producto: 7 Series/C210 Series Chipset Family USB Enhanced Host 
Controller #2
 fabricante: Intel Corporation
 id físico: 1a
 información del bus: pci@:00:1a.0
 versión: 04
 anchura: 32 bits
 reloj: 33MHz
 capacidades: ehci bus_master cap_list
 configuración: driver=ehci_hcd latency=0
 recursos: irq:16 memoria:52609000-526093ff
*-multimedia
 descripción: Audio device
 producto: 7 Series/C210 Series Chipset Family High Definition 
Audio Controller
 fabricante: Intel Corporation
 id físico: 1b
 información del bus: pci@:00:1b.0
 versión: 04
 anchura: 64 bits
 reloj: 33MHz
 capacidades: bus_master cap_list
 configuración: driver=snd_hda_intel latency=0
 recursos: irq:45 memoria:5260-52603fff
*-pci:0
 descripción: PCI bridge
 producto: 7 Series/C210 Series Chipset Family PCI Express Root 
Port 1
 fabricante: Intel Corporation
 id físico: 1c
 información del bus: pci@:00:1c.0
 versión: c4
 anchura: 32 bits
 reloj: 33MHz
 capacidades: pci normal_decode bus_master cap_list
 configuración: driver=pcieport
 recursos: irq:17 memoria:5250-525f
   *-network DESACTIVADO
descripción: Interfaz inalámbrica
producto: Ralink corp.
fabricante: Ralink corp.
id físico: 0
información del bus: pci@:01:00.0
nombre lógico: wlan3
versión: 00
serie: b8:76:3f:83:a5:a5
anchura: 32 bits
reloj: 33MHz
capacidades:

Re: [Kernel-packages] [Bug 49052] Re: no hfs+ journal write support by default (gets mounted as read only)

2013-12-12 Thread michael

Just updated for kernel 3.11 api I should be uploading new packing within
the week. These are actually source packages which dkms compiles and
installs. Any system with at least kernel 3.2 should be able to use any
package.

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

Title:
  no hfs+ journal write support by default (gets mounted as read only)

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-source-2.6.15” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: linux-686

  Dapper Drake does not appear to support a HFS+ journaled file system. This 
manifests when I connect my ipod mini, and dmesg warns that:
  'HFS+-fs: write access to a jounaled filesystem is not supported, use the 
force option at your own risk, mounting read-only.'
  Using force appears to work to mount the device read/write. This was not a 
problem under Breezy, which makes me think that it's a kernel compilation issue.

  This occurs while running kernel linux-686 2.6.15.22

  Thanks! :-)

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

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

Re: [Kernel-packages] [Bug 1064236] Re: [SAMSUNG NP700Z5A-S01RU] suspend/resume failure [non-free: wl]

2013-12-12 Thread Mikhail S. Pobolovets

Let's close it as invalid.

--
Sincerely,
Mikhail S. Pobolovets
styx...@gmail.com | skype: styx.mp | http://gplus.to/styx.mp


2013/12/12 Christopher M. Penalver christopher.m.penal...@gmail.com

 Mikhail S. Pobolovets, would you need a backport to a release prior to
 Trusty, or may this be closed as Invalid?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1064236

 Title:
   [SAMSUNG NP700Z5A-S01RU] suspend/resume failure [non-free: wl]

 Status in “linux” package in Ubuntu:
   Incomplete

 Bug description:
   [SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B]
   suspend/resume failure [non-free: wl]

   ProblemType: KernelOops
   DistroRelease: Ubuntu 12.10
   Package: linux-image-3.5.0-17-generic 3.5.0-17.27
   ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
   Uname: Linux 3.5.0-17-generic x86_64
   NonfreeKernelModules: wl
   Annotation: This occured during a previous suspend and prevented it from
 resuming properly.
   ApportVersion: 2.6.1-0ubuntu1
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  styx   1766 F pulseaudio
   CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1:
 nl80211 not found.
   Date: Tue Oct  9 08:48:20 2012
   ExecutablePath: /usr/share/apport/apportcheckresume
   Failure: suspend/resume
   InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac
 (20111012)
   InterpreterPath: /usr/bin/python3.2mu
   MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B
   ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
   ProcEnviron:
TERM=linux
PATH=(custom, no user)
   ProcFB:
0 radeondrmfb
1 inteldrmfb
   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic
 root=UUID=3a529063-69ed-4dc0-bb94-d6a61dbc4b26 ro acpi_brightness=vendor
 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.5.0-17-generic N/A
linux-backports-modules-3.5.0-17-generic  N/A
linux-firmware1.94
   SourcePackage: linux
   Title: [SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B]
 suspend/resume failure [non-free: wl]
   UpgradeStatus: Upgraded to quantal on 2012-10-02 (6 days ago)
   UserGroups:

   dmi.bios.date: 10/28/2011
   dmi.bios.vendor: Phoenix Technologies Ltd.
   dmi.bios.version: 08FD
   dmi.board.asset.tag: Base Board Asset Tag
   dmi.board.name: 700Z3A/700Z4A/700Z5A/700Z5B
   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
   dmi.board.version: FAB1
   dmi.chassis.asset.tag: Asset Tag
   dmi.chassis.type: 9
   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
   dmi.chassis.version: 0.1
   dmi.modalias:
 dmi:bvnPhoenixTechnologiesLtd.:bvr08FD:bd10/28/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3A/700Z4A/700Z5A/700Z5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn700Z3A/700Z4A/700Z5A/700Z5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
   dmi.product.name: 700Z3A/700Z4A/700Z5A/700Z5B
   dmi.product.version: 0.1
   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

Title:
  [SAMSUNG NP700Z5A-S01RU] suspend/resume failure [non-free: wl]

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  [SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B]
  suspend/resume failure [non-free: wl]

  ProblemType: KernelOops
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.27
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  styx   1766 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct  9 08:48:20 2012
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac 
(20111012)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=3a529063-69ed-4dc0-bb94-d6a61dbc4b26 ro acpi_brightness=vendor quiet 
splash vt.handoff=7

[Kernel-packages] [Bug 1260214] Re: 8086:0166 [ASUS TAICHI 21] External screen doesn't work.

2013-12-12 Thread SOIMiMozO

As I wrote in my first post, I did test it with 3.13-rc3 mainline
kernel. It is the latest one presented.

** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.13-rc3

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

Title:
  8086:0166 [ASUS TAICHI 21] External screen doesn't work.

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  External screen on ASUS Taichi21 ultrabook doesn't show anything. The
  backlight is always off also. Both screens are being recognized by OS,
  and can be managed, but external screen is off, no matter which
  options are chosen. Tested with 3.8 repository kernel, and with
  3.13.0-0311300rc3 mainline kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-34-generic 3.8.0-34.49
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  soimimozo   1844 F pulseaudio
  Date: Thu Dec 12 17:06:14 2013
  HibernationDevice: RESUME=UUID=76d4fac3-6b56-4dc2-b04b-1590849c4026
  InstallationDate: Installed on 2013-12-09 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. TAICHI21A
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=b0c6a357-cbe3-4ed0-8193-2d90569de03d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-34-generic N/A
   linux-backports-modules-3.8.0-34-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TAICHI21A.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TAICHI21A
  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.:bvrTAICHI21A.203:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnTAICHI21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTAICHI21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TAICHI21A
  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/1260214/+subscriptions

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

[Kernel-packages] [Bug 1165433] Re: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect

2013-12-12 Thread eccerr0r

Anyone running into this bug on Ubuntu, please test Linux kernel
3.12-release or newer, if you can compile it (or if there is a package
available...)  This kernel should have the BT DUN fixes.

I really cannot say anything in these forums as I am not running Ubuntu
(I have the same bug posted on Gentoo's bugtracker,
https://bugs.gentoo.org/show_bug.cgi?id=474432 ) but there are not
enough Gentoo users using BT DUN/NetworkManager for me to collaborate
with...  My observations is that with the 3.12 vanilla kernel the crash
goes away if I manually set up an rfcomm link and detach it, but
NetworkManager no longer finds BT DUN as a valid dialup device.
Reverting back to 3.5.7 or 3.6.11 restores operation with the same
userspace.


** Bug watch added: Gentoo Bugzilla #474432
   https://bugs.gentoo.org/show_bug.cgi?id=474432

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

Title:
  Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Issue is obviously in the kernel that should not panic in any circumnstances.
  This bug is seen on quantal using the kernel from PPA mainline. Tested with 
3.8.0 to 3.8.6.
  Since 3.8.x is going to be the raring kernel I believe that this should 
definitely be fixed before raring is shipped.

  Seen on:

  DELL E6500 with kubuntu quantal 12.10 64 bit and as said, kernel 3.8.6 from 
the mainline ppa.
  The machine has a Dell Computer Corp. Wireless 370 Bluetooth Mini-card 
(connected via an internal usb connection).

  The issue is shown when connecting to the internet via a Samsung Galaxy S 
plus phone, using a bluetooth DUN connection.
  It is reproducible every time.

  How to reproduce:

  1) Use the bluetooth applet to discover the phone and associate to it.
  2) Use network manager to setup a DUN connection with the phone through your 
APN
  3) Connect to the internet via bluetooth DUN (connection works perfectly)
  4) Disconnect from the network manager.

  At the same time you disconnect, the GUI session is terminated and the
  kernel panics, briefly showing a panic log on the screen.

  Note that:

  a) The issue is not present using the standard ubuntu quantal kernel
  b) The issue is not present using kernels from the mainline ppa before 3.8 
(e.g., 3.7.x is fine for all x)
  c) The issue is not present when connecting to the internet using a USB 
mobile dongle (e.g. Huawei usb key)

  This looks pretty serious to me: kernel does not sync when panicing
  and there is a serious risk of data loss; connecting to the internet
  via a smart phone using bluetooth DUN seems to be something that one
  should take for granted on any modern OS. Furthermore, points a) and
  b) above show that this is a *regression* over previous kernels.

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

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

[Kernel-packages] [Bug 1252417] Re: CVE-2013-4270

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

** Description changed:

- [net: permissions flaw in /proc/sys/net]
+ The net_ctl_permissions function in net/sysctl_net.c in the Linux kernel
+ before 3.11.5 does not properly determine uid and gid values, which
+ allows local users to bypass intended /proc/sys/net restrictions via a
+ crafted application.
  
  Break-Fix: cff109768b2d9c03095848f4cd4b0754117262aa
  2433c8f094a008895e66f25bd1773cdb01c91d01

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

Title:
  CVE-2013-4270

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Invalid
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Invalid
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-armadaxp” source package in Precise:
  Invalid
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  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:
  Fix Committed
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Invalid
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-armadaxp” source package in Quantal:
  Invalid
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  Fix Committed
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  New
Status in “linux-lts-backport-natty” source package in Saucy:
  New
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in

[Kernel-packages] [Bug 1241769] Re: CVE-2013-4299

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

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

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

Title:
  CVE-2013-4299

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

[Kernel-packages] [Bug 1226497] Re: CVE-2013-4350

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

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

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

Title:
  CVE-2013-4350

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

[Kernel-packages] [Bug 1235136] Re: CVE-2013-4387

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

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

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

Title:
  CVE-2013-4387

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

[Kernel-packages] [Bug 1248703] Re: CVE-2013-4470

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

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

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

Title:
  CVE-2013-4470

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

[Kernel-packages] [Bug 1256094] Re: CVE-2013-6383

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

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

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

Title:
  CVE-2013-6383

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

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

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

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

Title:
  CVE-2013-4563

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Invalid
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Invalid
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-armadaxp” source package in Precise:
  Invalid
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  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:
  New
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Invalid
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-armadaxp” source package in Quantal:
  Invalid
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  Invalid
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  New
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  New
Status in “linux-lts-backport-natty” source package in Saucy:
  New
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  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-mvl-dove” source

[Kernel-packages] [Bug 1256919] Re: CVE-2013-6405