[Kernel-packages] [Bug 1396470] Re: please enable CONFIG_VIRTIO_MMIO on armmp

[Paolo Pisati]

** Description changed:

+ [Impact]
+ Degraded performance during network and disk activity in a kvm guest.
+ 
+ [Test case]
+ Try booting a vm and do some disk/net activity with and without this driver.
+ 
+ [Regression potential]
+ In case of regressions, it will just hit people using kvm on 32bit armhf 
hardware (the lpae variant in particular): we already had this driver on in the 
past, it's on by default on every arch, it's widely used and upstream is very 
active - i say it's a low potential regression.
+ 
+ --
  Hi,
  
  The current armmp (linux-image-3.16.0-26-generic_3.16.0-26.34_armhf.deb)
  could have virtio-mmio enabled for faster vm guests. Currenlty it seems
  to have:
  
  CONFIG_NET_9P_VIRTIO=m
  CONFIG_VIRTIO_BLK=y
  CONFIG_SCSI_VIRTIO=m
  CONFIG_VIRTIO_NET=y
  CONFIG_CAIF_VIRTIO=m
  CONFIG_VIRTIO_CONSOLE=y
  CONFIG_HW_RANDOM_VIRTIO=m
  CONFIG_VIRTIO=y
  CONFIG_VIRTIO_PCI=y
  # CONFIG_VIRTIO_BALLOON is not set
  # CONFIG_VIRTIO_MMIO is not set
  
  Now using virtio net and block is not possible, and you have to revert
  to emulated devices.

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

Title:
  please enable CONFIG_VIRTIO_MMIO on armmp

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  Degraded performance during network and disk activity in a kvm guest.

  [Test case]
  Try booting a vm and do some disk/net activity with and without this driver.

  [Regression potential]
  In case of regressions, it will just hit people using kvm on 32bit armhf 
hardware (the lpae variant in particular): we already had this driver on in the 
past, it's on by default on every arch, it's widely used and upstream is very 
active - i say it's a low potential regression.

  --
  Hi,

  The current armmp (linux-
  image-3.16.0-26-generic_3.16.0-26.34_armhf.deb) could have virtio-mmio
  enabled for faster vm guests. Currenlty it seems to have:

  CONFIG_NET_9P_VIRTIO=m
  CONFIG_VIRTIO_BLK=y
  CONFIG_SCSI_VIRTIO=m
  CONFIG_VIRTIO_NET=y
  CONFIG_CAIF_VIRTIO=m
  CONFIG_VIRTIO_CONSOLE=y
  CONFIG_HW_RANDOM_VIRTIO=m
  CONFIG_VIRTIO=y
  CONFIG_VIRTIO_PCI=y
  # CONFIG_VIRTIO_BALLOON is not set
  # CONFIG_VIRTIO_MMIO is not set

  Now using virtio net and block is not possible, and you have to revert
  to emulated devices.

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

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

[Kernel-packages] [Bug 1398118] Re: linux: 3.16.0-26.35 -proposed tracker

[Parameswaran Sivatharman]

** Tags added: qa-testing-passed

** Changed in: kernel-sru-workflow/regression-testing
   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/1398118

Title:
  linux: 3.16.0-26.35 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-26.35 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, 01. December 2014 18:19 UTC
  kernel-stable-Prepare-package-end:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 02. December 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. December 2014 17:05 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Verification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 02. December 2014 19:02 UTC

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

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

[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3

[Fastguy]

What about supporting the real thing, ie connected standby or
InstantGO function. Isn't it yet supported by linux kernel?  Without
this and without real S3 state, linux won't be really useful on a SP3
I'm afraid.

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

Title:
  Can't suspend on Surface Pro 3

Status in linux package in Ubuntu:
  Incomplete
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Suspend on surface pro 3 from GUI does not work. (Nothing happens)

  Doing it manually also fails, and nothing appears in dmesg:
  #echo mem  /sys/power/state

  Error while writing to stdout
  write_loop: Invalid argument

  And, more interestingly,
  #cat /sys/power/state

  freeze disk

  Using the not-so-good-and-apparently-unsupported
  #echo freeze  /sys/power/state

  does seem to successfully suspend, however I cannot resume from this
  (assumed to be a separate issue). Likewise, pm-hibernate seems
  somewhat functional.

  I am using a the utopic unicorn kernel compiled from git at
  kernel.ubuntu.com, with a tiny patch that is required for my keyboard
  to work (hard to file bug reports without a keyboard). The official
  kernel behaves identically, as does vanilla 3.17 from the mainline
  folder of kernel-ppa.

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

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

[Kernel-packages] [Bug 1398118] Re: linux: 3.16.0-26.35 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.16.0-26.35 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, 01. December 2014 18:19 UTC
  kernel-stable-Prepare-package-end:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 02. December 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. December 2014 17:05 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Verification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 02. December 2014 19:02 UTC
+ kernel-stable-Regression-testing-end:Thursday, 04. December 2014 10:02 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/1398118

Title:
  linux: 3.16.0-26.35 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-26.35 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, 01. December 2014 18:19 UTC
  kernel-stable-Prepare-package-end:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 02. December 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. December 2014 17:05 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Verification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-end:Thursday, 04. December 2014 10:02 UTC

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

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

[Kernel-packages] [Bug 1387865] Re: [Aorus X3+] Touchpad not working in Ubuntu 14.04 and 14.10

[Maximilien Levesque]

** Tags removed: kernel-bug-exists-upstream-3.18-rc6
** Tags added: kernel-bug-exists-upstream-3.18-rc7

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

Title:
  [Aorus X3+] Touchpad not working in Ubuntu 14.04 and 14.10

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Touchpad not working. I don't see the mouse pointer. Laptop is exactly
  the same as without the touchpad.

  I can plug a USB Mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  levesque   2822 F pulseaudio
   /dev/snd/controlC1:  levesque   2822 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 30 21:21:08 2014
  HibernationDevice: RESUME=UUID=41f05731-4d43-4531-8579-69f950969e48
  InstallationDate: Installed on 2014-10-16 (14 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: GIGABYTE X3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=1ab1195f-fc7d-4896-81a7-59d1f67b50c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (5 days ago)
  dmi.bios.date: 07/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD04
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X3
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD04:bd07/04/2014:svnGIGABYTE:pnX3:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnX3:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: X3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1386393] Re: CVE-2014-3688

[John Johansen]

** Description changed:

- net: sctp: remote memory pressure from excessive queueing
+ The SCTP implementation in the Linux kernel before 3.17.4 allows remote
+ attackers to cause a denial of service (memory consumption) by
+ triggering a large number of chunks in an association's output queue, as
+ demonstrated by ASCONF probes, related to net/sctp/inqueue.c and
+ net/sctp/sm_statefuns.c.
  
  Break-Fix: 2e3216cd54b142ba605e87522e15f42e0c4e3996
  26b87c7881006311828bb0ab271a551a62dcceb4

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

Title:
  CVE-2014-3688

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:
  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 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:
  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:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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:
  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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

Bug description:
  The SCTP implementation in the Linux kernel before 3.17.4 allows
  remote attackers to cause a denial of service (memory consumption) by
  triggering a large number of chunks in an association's output queue,
  as demonstrated by ASCONF 

[Kernel-packages] [Bug 1335313] Re: CVE-2014-4608

[John Johansen]

** Description changed:

  ** DISPUTED ** Multiple integer overflows in the lzo1x_decompress_safe
  function in lib/lzo/lzo1x_decompress_safe.c in the LZO decompressor in
  the Linux kernel before 3.15.2 allow context-dependent attackers to
  cause a denial of service (memory corruption) via a crafted Literal Run.
  NOTE: the author of the LZO algorithms says the Linux kernel is *not*
  affected; media hype.
  
  Break-Fix: 64c70b1cf43de158282bc1675918d503e5b15cc1 
72cf90124e87d975d0b2114d930808c58b4c05e4
  Break-Fix: 64c70b1cf43de158282bc1675918d503e5b15cc1 
af958a38a60c7ca3d8a39c918c1baa2ff7b6b233
- Break-Fix: 64c70b1cf43de158282bc1675918d503e5b15cc1 
72cf90124e87d975d0b2114d930808c58b4c05e4

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

Title:
  CVE-2014-4608

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:
  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 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:
  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 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:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Fix Released
Status in linux-lts-raring source package in Precise:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  Fix Released
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Saucy:
  New
Status in linux-lts-backport-natty source package in Saucy:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source 

[Kernel-packages] [Bug 1398795] Re: CVE-2014-9090

[John Johansen]

** Description changed:

- x86_64, traps: Stop using IST for #SS
+ The do_double_fault function in arch/x86/kernel/traps.c in the Linux
+ kernel through 3.17.4 does not properly handle faults associated with
+ the Stack Segment (SS) segment register, which allows local users to
+ cause a denial of service (panic) via a modify_ldt system call, as
+ demonstrated by sigreturn_32 in the linux-clock-tests test suite.
  
  Break-Fix: - 6f442be2fb22be02cafa606f1769fa1e6f894441

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

Title:
  CVE-2014-9090

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:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  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:
  New
Status in linux source package in Trusty:
  New
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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

Bug description:
  The do_double_fault function in arch/x86/kernel/traps.c in the Linux
  kernel through 3.17.4 does not properly handle faults associated with
  the Stack Segment (SS) segment register, which allows local users to
  cause a denial of service (panic) via a modify_ldt system call, as
  demonstrated by sigreturn_32 in the linux-clock-tests test 

[Kernel-packages] [Bug 1392826] Re: CVE-2014-7843

[John Johansen]

** Description changed:

- copying from /dev/zero causes local DoS
+ The __clear_user function in arch/arm64/lib/clear_user.S in the Linux
+ kernel before 3.17.4 on the ARM64 platform allows local users to cause a
+ denial of service (system crash) by reading one byte beyond a /dev/zero
+ page boundary.
  
  Break-Fix: 0aea86a2176c22647a5b683768f858d880d5e05b
  97fc15436b36ee3956efad83e22a557991f7d19d

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

Title:
  CVE-2014-7843

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:
  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 Trusty:
  New
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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

Bug description:
  The __clear_user function in arch/arm64/lib/clear_user.S in the Linux
  kernel before 3.17.4 on the ARM64 platform allows local users to cause
  a denial of service (system crash) by reading one byte beyond a
  /dev/zero page boundary.

  Break-Fix: 0aea86a2176c22647a5b683768f858d880d5e05b
  97fc15436b36ee3956efad83e22a557991f7d19d

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1395189] Re: CVE-2014-8989

[John Johansen]

** Description changed:

- [Linux user namespaces can bypass group-based restrictions]
+ The Linux kernel through 3.17.4 does not properly restrict dropping of
+ supplemental group memberships in certain namespace scenarios, which
+ allows local users to bypass intended file permissions by leveraging a
+ POSIX ACL containing an entry for the group category that is more
+ restrictive than the entry for the other category, aka a negative
+ groups issue, related to kernel/groups.c, kernel/uid16.c, and
+ kernel/user_namespace.c.

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

Title:
  CVE-2014-8989

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  New
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

Bug description:
  The Linux kernel through 3.17.4 does not properly restrict dropping of
  supplemental group memberships in certain namespace scenarios, which
  allows local users to bypass intended file permissions by leveraging a
  POSIX ACL containing an entry for the group category that is more
  restrictive than the 

[Kernel-packages] [Bug 1392820] Re: CVE-2014-7841

[John Johansen]

** Description changed:

- net: sctp: NULL pointer dereference in af-from_addr_param on malformed
- packet
+ The sctp_process_param function in net/sctp/sm_make_chunk.c in the SCTP
+ implementation in the Linux kernel before 3.17.4, when ASCONF is used,
+ allows remote attackers to cause a denial of service (NULL pointer
+ dereference and system crash) via a malformed INIT chunk.
  
  Break-Fix: d6de3097592b7ae7f8e233a4dafb088e2aa8170f
  e40607cbe270a9e8360907cb1e62ddf0736e4864

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

Title:
  CVE-2014-7841

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:
  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:
  New
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:
  Fix Committed
Status in linux source package in Trusty:
  New
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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

Bug description:
  The sctp_process_param function in net/sctp/sm_make_chunk.c in the
  SCTP implementation in the Linux kernel before 3.17.4, when ASCONF is
  used, allows remote attackers to cause a denial of service (NULL
  pointer dereference and system crash) via a malformed INIT chunk.

  

[Kernel-packages] [Bug 1395187] Re: CVE-2014-8884

[John Johansen]

** Description changed:

- [ttusb-dec: overflow by descriptor]
+ Stack-based buffer overflow in the
+ ttusbdecfe_dvbs_diseqc_send_master_cmd function in drivers/media/usb
+ /ttusb-dec/ttusbdecfe.c in the Linux kernel before 3.17.4 allows local
+ users to cause a denial of service (system crash) or possibly gain
+ privileges via a large message length in an ioctl call.
  
  Break-Fix: - f2e323ec96077642d397bb1c355def536d489d16

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

Title:
  CVE-2014-8884

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:
  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:
  New
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:
  Fix Committed
Status in linux source package in Trusty:
  New
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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

Bug description:
  Stack-based buffer overflow in the
  ttusbdecfe_dvbs_diseqc_send_master_cmd function in drivers/media/usb
  /ttusb-dec/ttusbdecfe.c in the Linux kernel before 3.17.4 allows local
  users to cause a denial of service (system crash) or possibly gain
  privileges via a large message length in an ioctl call.

  Break-Fix: - 

[Kernel-packages] [Bug 1392823] Re: CVE-2014-7842

[John Johansen]

** Description changed:

- kvm: reporting emulation failures to userspace
+ Race condition in arch/x86/kvm/x86.c in the Linux kernel before 3.17.4
+ allows guest OS users to cause a denial of service (guest OS crash) via
+ a crafted application that performs an MMIO transaction or a PIO
+ transaction to trigger a guest userspace emulation error report, a
+ similar issue to CVE-2010-5313.
  
  Break-Fix: fc3a9157d3148ab91039c75423da8ef97be3e105
  a2b9e6c1a35afcc0973acb72e591c714e78885ff

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

Title:
  CVE-2014-7842

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:
  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:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  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:
  New
Status in linux source package in Trusty:
  New
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 package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

Bug description:
  Race condition in arch/x86/kvm/x86.c in the Linux kernel before 3.17.4
  allows guest OS users to cause a denial of service (guest OS crash)
  via a crafted application that performs an MMIO transaction or a PIO
  transaction to trigger a guest userspace emulation error report, a
  similar issue to 

[Kernel-packages] [Bug 1399142] [NEW] CVE-2010-5313

[John Johansen]

*** This bug is a security vulnerability ***

Public security bug reported:

Race condition in arch/x86/kvm/x86.c in the Linux kernel before 2.6.38
allows L2 guest OS users to cause a denial of service (L1 guest OS
crash) via a crafted instruction that triggers an L2 emulation failure
report, a similar issue to CVE-2014-7842.

Break-Fix: - fc3a9157d3148ab91039c75423da8ef97be3e105

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-mvl-dove (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Lucid)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu Lucid)
 Importance: Medium
 Status: New

** Affects: linux-fsl-imx51 (Ubuntu Lucid)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Lucid)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Lucid)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu Lucid)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Lucid)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Lucid)
 Importance: Medium
 Status: Invalid

** Affects: linux-mvl-dove (Ubuntu Lucid)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Lucid)
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux-ec2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

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

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

** Affects: linux-mvl-dove (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-mvl-dove (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Utopic)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu Utopic)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu Utopic)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Utopic)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Utopic)
 Importance: Undecided
 Status: New

** Affects: 

[Kernel-packages] [Bug 1399142] Re: CVE-2010-5313

[John Johansen]

CVE-2010-5313

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Also affects: linux-fsl-imx51 (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: linux-mvl-dove (Ubuntu Lucid)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-maverick (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Lucid)
   Importance: Undecided
   Status: New

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

** Changed in: linux-armadaxp (Ubuntu Lucid)
   Status: New = Invalid

** Changed in: linux-armadaxp (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: linux-armadaxp (Ubuntu Utopic)
   Status: New = Invalid

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

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

** Changed in: linux-ec2 (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: linux-ec2 (Ubuntu Utopic)
   Status: New = Invalid

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

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

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

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

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

** Changed in: linux-mvl-dove (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: linux-mvl-dove (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: linux-mvl-dove (Ubuntu Utopic)
   Status: New = Invalid

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

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

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

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

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

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

** Changed in: 

Re: [Kernel-packages] [Bug 1398318] Re: bay trail efi install failed

[hoshi]

I have to make an modified iso with this kernel, or with a patch available
from link above. Not sure where to start, may i mount the iso, uncompress
kernel from mainline to replace the old one and then make a new iso? will
try to find out how to do that

2014-12-03 20:38 GMT+01:00 Joseph Salisbury joseph.salisb...@canonical.com
:

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

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

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1398318

 Title:
   bay trail efi install failed

 Status in linux package in Ubuntu:
   Incomplete

 Bug description:
   can t install ubuntu on baytrail platform with efi32 and amd64 cpu

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: ubiquity 2.18.8
   ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
   Uname: Linux 3.13.0-32-generic x86_64
   ApportVersion: 2.14.1-0ubuntu3.2
   Architecture: amd64
   CasperVersion: 1.340
   Date: Tue Dec  2 09:53:49 2014
   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
 file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --
   LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64
 (20140722.2)
   ProcEnviron:
LANGUAGE=fr_FR.UTF-8
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
   SourcePackage: grub-installer
   UpgradeStatus: No upgrade log present (probably fresh install)

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398318/+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/1398318

Title:
  bay trail efi install failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  can t install ubuntu on baytrail platform with efi32 and amd64 cpu

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.18.8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CasperVersion: 1.340
  Date: Tue Dec  2 09:53:49 2014
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --
  LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
  ProcEnviron:
   LANGUAGE=fr_FR.UTF-8
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1358949] Re: arm64 iperf performance suboptimal

[Andy Whitcroft]

Note these patches have been found to cause crashes and have been
reverted under Bug #1398596.

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

Title:
  arm64 iperf performance suboptimal

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal. 
Optimized implementations have been submitted upstream and have shown a 
significant improvement in network performance.

  Iperf performance increase:
  -l (size)   1 core result
  Optimized   64B 44-51Mb/s
  1500B   4.9Gb/s
  3B  16.2Gb/s
  Original64B 34-50.7Mb/s
  1500B   4.7Gb/s
  3B  14.5Gb/s

  [Test Case]
  Generate traffic from one node to another using iperf (see above for config).

  [Regression Risk]
  These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. This risk is mitigated by using an 
implementation heavily based on the linaro string libraries (which are used in 
other places already, e.g. glibc), and through active testing of this patch on 
real hardware using a trusty-kernel base.

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

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

[Kernel-packages] [Bug 1398596] Re: [Revert] arm64: optimized copy_to_user and copy_from_user assembly code

[Andy Whitcroft]

This reverts fixes applied in Bug #1358949.

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

Title:
  [Revert] arm64: optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  [Impact]
  Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.

  http://www.spinics.net/lists/arm-kernel/msg381811.html

  [Test Case]
  Put the system under memory pressure.

  [Regression Potential]
  It will cause a performance regression on certain workloads on arm64 systems.

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

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

[Kernel-packages] [Bug 1363600] Re: ThinkPad Ultrabay HDD not detected

[Maui Muc]

'Expired' what a joke! Just because nothing was done about it the bug didn't 
disappear. 
Really, when plugging a ultrabay HDD it does not get detected, no kidding!

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

Title:
  ThinkPad Ultrabay HDD not detected

Status in linux package in Ubuntu:
  Expired

Bug description:
  On my ThinkPad T60 Ubuntu 14.04 running the generic kernel does not
  detect Ultrabay hard disks. Switching to the 3.14.1 mainline kernel
  solves the problem. In particular this problem occurs not having any
  drive in the swappable slot during startup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-35-generic 3.13.0-35.62
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mauerberger   2000 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Aug 31 10:29:59 2014
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=79faaca0-0c51-460a-b027-0e31496ce202
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-08-05 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: LENOVO 2007WX1
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=87ffb319-a06f-476b-804e-447d5593aaf5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-35-generic N/A
   linux-backports-modules-3.13.0-35-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   10:30:15.956: The udisks-daemon is running (name-owner :1.72).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE7WW (2.27 )
  dmi.board.name: 2007WX1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE7WW(2.27):bd03/21/2011:svnLENOVO:pn2007WX1:pvrThinkPadT60:rvnLENOVO:rn2007WX1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2007WX1
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1398318] Re: bay trail efi install failed

[hoshi]

ok, squashfs and chroot method on the way... Trying with a vivid daily and
the kernel v3.18-rc7-vivid... and try to figure out how to patch the kernel
if needed from dev-nell.com


2014-12-04 12:45 GMT+01:00 hoshi nagama hosh...@gmail.com:

 I have to make an modified iso with this kernel, or with a patch available
 from link above. Not sure where to start, may i mount the iso, uncompress
 kernel from mainline to replace the old one and then make a new iso? will
 try to find out how to do that

 2014-12-03 20:38 GMT+01:00 Joseph Salisbury 
 joseph.salisb...@canonical.com:

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

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

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1398318

 Title:
   bay trail efi install failed

 Status in linux package in Ubuntu:
   Incomplete

 Bug description:
   can t install ubuntu on baytrail platform with efi32 and amd64 cpu

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: ubiquity 2.18.8
   ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
   Uname: Linux 3.13.0-32-generic x86_64
   ApportVersion: 2.14.1-0ubuntu3.2
   Architecture: amd64
   CasperVersion: 1.340
   Date: Tue Dec  2 09:53:49 2014
   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
 file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --
   LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64
 (20140722.2)
   ProcEnviron:
LANGUAGE=fr_FR.UTF-8
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
   SourcePackage: grub-installer
   UpgradeStatus: No upgrade log present (probably fresh install)

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398318/+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/1398318

Title:
  bay trail efi install failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  can t install ubuntu on baytrail platform with efi32 and amd64 cpu

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.18.8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CasperVersion: 1.340
  Date: Tue Dec  2 09:53:49 2014
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --
  LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
  ProcEnviron:
   LANGUAGE=fr_FR.UTF-8
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1395827] Re: linux: 2.6.32-69.136 -proposed tracker

[John Johansen]

Looks good

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

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

Title:
  linux: 2.6.32-69.136 -proposed tracker

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

Bug description:
  This bug is for tracking the 2.6.32-69.136 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, 24. November 2014 18:42 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 25. November 2014 22:50 UTC
  kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 00:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 00:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 00:01 UTC
  kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 00:01 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Monday, 01. December 2014 16:00 UTC
  kernel-stable-Verification-testing-end:Monday, 01. December 2014 16:00 UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 11:00 UTC

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

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

[Kernel-packages] [Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers

[Koen Roggemans]

No, I don't know the ways to get it upstream. Suppose I could send a
message to Tim Gardner.

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

Title:
  Elantech touchpad locks cursor when touching with 2 or more fingers

Status in The Linux Kernel:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 14.04.1, Unity desktop, kernel 3.13.0-35 generic on
  Intel Classmate, MG Pupil 109

  The touchpad is identified in dmesg as
  [1.539535] mousedev: PS/2 mouse device common for all mice
  [2.528608] psmouse serio4: elantech: assuming hardware version 3 (with 
firmware version 0x354f01)
  [2.541184] psmouse serio4: elantech: Synaptics capabilities query result 
0x39, 0x16, 0x09.

  The cursor locks when you touch the touchpad with 2 or more fingers.
  The only way I found to get it loose is reboot or suspend and resume.

  modprobe -r psmouse
  modprobe psmouse doesn' t work, also not with proto=auto  

  In systemsettings I disabled 2 finger scrolling without result

  In dmesg I see messages like psmouse serio4: Touchpad at
  isa0060/serio4/input0 lost synchronization, throwing 5 bytes away
  during normal operation. The number of bytes can be 4 too. When the
  cursor locks up, I don't see such a message. Nothing is reported in
  dmesg.

  Doing some research, I've learned that the touchpad should support
  multi touch. Off course that doesn't work, since touching the pad with
  more fingers makes it lock.

  Any help much appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-35-generic 3.13.0-35.62
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   1474 F pulseaudio
  Date: Mon Sep 15 20:00:38 2014
  HibernationDevice: RESUME=UUID=6f2e0704-c6a4-4f89-b357-c8e46ff9d0ec
  InstallationDate: Installed on 2014-09-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Intel Corporation Intel powered classmate PC
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=40917190-7ade-42d5-a5d2-91f8c497278e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-35-generic N/A
   linux-backports-modules-3.13.0-35-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: MPBYT10A.90A.0029.2014.0421.1908
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Clamshell
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 11
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrMPBYT10A.90A.0029.2014.0421.1908:bd04/21/2014:svnIntelCorporation:pnIntelpoweredclassmatePC:pvrClamshell:rvnIntelCorporation:rnIntelpoweredclassmatePC:rvrClamshell:cvnIntelCorporation:ct11:cvr0.1:
  dmi.product.name: Intel powered classmate PC
  dmi.product.version: Clamshell
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1395827] Re: linux: 2.6.32-69.136 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 2.6.32-69.136 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, 24. November 2014 18:42 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 25. November 2014 22:50 UTC
  kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 00:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 00:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 00:01 UTC
  kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 00:01 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Monday, 01. December 2014 16:00 UTC
  kernel-stable-Verification-testing-end:Monday, 01. December 2014 16:00 UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 11:00 UTC
+ kernel-stable-Security-signoff-end:Thursday, 04. December 2014 13:00 UTC

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

Title:
  linux: 2.6.32-69.136 -proposed tracker

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

Bug description:
  This bug is for tracking the 2.6.32-69.136 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, 24. November 2014 18:42 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 25. November 2014 22:50 UTC
  kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 00:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 00:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 00:01 UTC
  kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 00:01 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Monday, 01. December 2014 16:00 UTC
  kernel-stable-Verification-testing-end:Monday, 01. December 2014 16:00 UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 11:00 UTC
  kernel-stable-Security-signoff-end:Thursday, 04. December 2014 13:00 UTC

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

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

[Kernel-packages] [Bug 1206880] Re: Mouse clicks not detected in JAVA after touching eGalax touchscreen

[Nyyr]

OK, tried version http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.18-rc7-vivid/, the problem persists, but now event the
Always trust content from this publisher checkbox is not clickable
after trying to use the touchscreen (not even with a mouse). I can only
close the JAVA window by clicking on the X icon at the upper right
corner of the window - even with the touchscreen.

Edit: Hm, strange. After playing with it for a while, I can sometimes
click on the checkbox (but not on the butons).

Anyway, after Xorg restart, mouse 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/1206880

Title:
  Mouse clicks not detected in JAVA after touching eGalax touchscreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have all-in-one PC terminal with touchscreen with Ubuntu 10.10 and
  JAVA application on Oracle JAVA JRE with some buttons. Working fine.

  After I did a minimal clean install from Ubuntu Server 12.04 CD (just with 
fluxbox WM) and Oracle JAVA JRE I run the JAVA application via javaws. I can 
click the buttons in the JAVA application using mouse, but when I try the same 
with touchscreen, the mouse pointer moves to the place I touched but the button 
is not pressed. After that when trying to use the mouse again even the mouse 
clicks are not detected !!!
  At first I thought it is the application problem but the same applies to the 
javaws laucher windows as well.

  Configuration of X11 in both versions of Ubuntu seems to be the same
  (no xorg.conf, just calibration.conf), no other adjustments.

  Touchscreen in Fluxbox is working fine in both versions. Since the
  JAVA version is the same in both versions of Ubuntu it cannot be
  problem of JAVA.

  To me it seems that in Ubuntu 12.04 the touchscreen/mouse events are passed 
to the JAVA VM differently than in Ubuntu 10.10.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-40-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', 
'/dev/snd/pcmC0D4p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [  630.974265] perf samples too long (5026  5000), lowering 
kernel.perf_event_max_sample_rate to 25000
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=6d3a7fc5-93df-46a4-9dd2-4aa18bb16551
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
i386 (20140204)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: PhoenixAward 945GSE
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.13.0-40-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/01/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GSE
  dmi.board.vendor: PhoenixAward
  dmi.board.version: 6.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/01/2009:svnPhoenixAward:pn945GSE:pvr6.0:rvnPhoenixAward:rn945GSE:rvr6.0:cvn:ct3:cvr:
  dmi.product.name: 945GSE
  dmi.product.version: 6.0
  dmi.sys.vendor: PhoenixAward

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

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

[Kernel-packages] [Bug 1206880] Re: Mouse clicks not detected in JAVA after touching eGalax touchscreen

[Nyyr]

Sorry, the bugs.launchpad.net GUI is not intuitive enough for me to find
out, how to add a tag.

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

Title:
  Mouse clicks not detected in JAVA after touching eGalax touchscreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have all-in-one PC terminal with touchscreen with Ubuntu 10.10 and
  JAVA application on Oracle JAVA JRE with some buttons. Working fine.

  After I did a minimal clean install from Ubuntu Server 12.04 CD (just with 
fluxbox WM) and Oracle JAVA JRE I run the JAVA application via javaws. I can 
click the buttons in the JAVA application using mouse, but when I try the same 
with touchscreen, the mouse pointer moves to the place I touched but the button 
is not pressed. After that when trying to use the mouse again even the mouse 
clicks are not detected !!!
  At first I thought it is the application problem but the same applies to the 
javaws laucher windows as well.

  Configuration of X11 in both versions of Ubuntu seems to be the same
  (no xorg.conf, just calibration.conf), no other adjustments.

  Touchscreen in Fluxbox is working fine in both versions. Since the
  JAVA version is the same in both versions of Ubuntu it cannot be
  problem of JAVA.

  To me it seems that in Ubuntu 12.04 the touchscreen/mouse events are passed 
to the JAVA VM differently than in Ubuntu 10.10.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-40-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', 
'/dev/snd/pcmC0D4p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [  630.974265] perf samples too long (5026  5000), lowering 
kernel.perf_event_max_sample_rate to 25000
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=6d3a7fc5-93df-46a4-9dd2-4aa18bb16551
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
i386 (20140204)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: PhoenixAward 945GSE
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.13.0-40-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/01/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GSE
  dmi.board.vendor: PhoenixAward
  dmi.board.version: 6.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/01/2009:svnPhoenixAward:pn945GSE:pvr6.0:rvnPhoenixAward:rn945GSE:rvr6.0:cvn:ct3:cvr:
  dmi.product.name: 945GSE
  dmi.product.version: 6.0
  dmi.sys.vendor: PhoenixAward

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

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

[Kernel-packages] [Bug 1396112] Re: linux: 3.13.0-41.70 -proposed tracker

[John Johansen]

Looks good

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

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

Title:
  linux: 3.13.0-41.70 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 12:01 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 22:56 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 22:56 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 22:56 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 16:56 
UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 26. November 2014 16:55 UTC
  kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 16:56 
UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 16:01 UTC

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

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

[Kernel-packages] [Bug 1396072] Re: linux: 3.2.0-73.108 -proposed tracker

[John Johansen]

Looks good

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

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

Title:
  linux: 3.2.0-73.108 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 10:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 15:10 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 15:10 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 15:10 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 25. November 2014 19:55 UTC
  kernel-stable-Verification-testing-start:Tuesday, 25. November 2014 21:01 UTC
  kernel-stable-Certification-testing-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Monday, 01. December 2014 16:01 UTC
  kernel-stable-Verification-testing-end:Monday, 01. December 2014 16:01 UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 11:01 UTC

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

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

[Kernel-packages] [Bug 1396188] Re: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker

[John Johansen]

Looks good

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow package-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 15:03 UTC
  kernel-stable-master-bug:1396072
  kernel-stable-Certification-testing-end:Wednesday, 26. November 2014 21:02 UTC
  kernel-stable-Prepare-package-end:Thursday, 27. November 2014 14:02 UTC
  kernel-stable-Promote-to-proposed-start:Thursday, 27. November 2014 14:02 UTC
  ppa-package-testing-start:Thursday, 27. November 2014 14:02 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 27. November 2014 21:17 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Security-signoff-start:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Verification-testing-start:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Regression-testing-start:Thursday, 27. November 2014 23:02 UTC

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

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

[Kernel-packages] [Bug 1396840] Re: Module nouveau systematically crashes after a few minutes, whereas module nvidia from nvidia-331-updates crashes only after several hours of work

[Christopher M. Penalver]

Etienne URBAH, one may gather a system crash via
https://help.ubuntu.com/community/DebuggingSystemCrash . It needs to
contain the verbage call trace (for kernel crash) or backtrace (for
xorg crash).

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

Title:
  Module nouveau systematically crashes after a few minutes, whereas
  module nvidia from nvidia-331-updates crashes only after several hours
  of work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Module 'nouveau' systematically crashes after a few minutes, whereas
  module 'nvidia' from 'nvidia-331-updates' crashes only after several
  hours of work.

  $ uname -r
  3.16.0-25-generic

  $ dpkg-query -W 'linux-*image-*3.16.0-25*'
  linux-image-3.16.0-25-generic 3.16.0-25.33
  linux-image-extra-3.16.0-25-generic   3.16.0-25.33
  linux-signed-image-3.16.0-25-generic  3.16.0-25.33

  $ lsmod | head -1 ;  lsmod | grep '^nouveau'  
  Module  Size  Used by
  nouveau  1234845  3 

  $ sudo lspci -nn -vv -s 03:00.0
  03:00.0 VGA compatible controller [0300]: NVIDIA Corporation C79 [GeForce 
9400] [10de:0867] (rev b1) (prog-if 00 [VGA controller])
Subsystem: Apple Inc. iMac 9,1 [106b:00ad]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 256 bytes
Interrupt: pin A routed to IRQ 45
Region 0: Memory at d200 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at c000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at d000 (64-bit, prefetchable) [size=32M]
Region 5: I/O ports at 1000 [size=128]
Expansion ROM at d300 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0300c  Data: 4152
Kernel driver in use: nouveau

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-extra-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  urbah  3073 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov 27 02:05:32 2014
  HibernationDevice: RESUME=UUID=d78e46a2-825e-4ad0-8f14-c7d2935c33c7
  InstallationDate: Installed on 2014-11-03 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  MachineType: Apple Inc. iMac9,1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=b587542c-4076-491a-ae4d-21942b20daf6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM91.88Z.008D.B08.0904271717
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F2218FC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2218FC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM91.88Z.008D.B08.0904271717:bd04/27/09:svnAppleInc.:pniMac9,1:pvr1.0:rvnAppleInc.:rnMac-F2218FC8:rvr:cvnAppleInc.:ct13:cvrMac-F2218FC8:
  dmi.product.name: iMac9,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1398118] Re: linux: 3.16.0-26.35 -proposed tracker

[John Johansen]

Looks good

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

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

Title:
  linux: 3.16.0-26.35 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-26.35 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, 01. December 2014 18:19 UTC
  kernel-stable-Prepare-package-end:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 02. December 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. December 2014 17:05 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Verification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-end:Thursday, 04. December 2014 10:02 UTC

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

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

[Kernel-packages] [Bug 1289961] Re: 8086:08b2 [Lenovo ThinkPad T440s] Power management causes Intel wifi 7260 slowness

[Christopher M. Penalver]

** Tags removed: kernel-bug-exists-upstream-v3.15-rc2
** Tags added: firmware-fixed-upstream

** Package changed: linux (Ubuntu) = linux-firmware (Ubuntu)

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

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

Title:
  8086:08b2 [Lenovo ThinkPad T440s] Power management causes Intel wifi
  7260 slowness

Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu Trusty (Gnome) with my ThinkPad T440s using Intel 7260 ac
  wireless the download speed reaches an upper limit 400 kB/s instead of
  the normal 1500 kB/s I get with some other PC connected to my network.
  The speed often slows down very very low, especially when I'm far away
  from my AP. Removing N mode does not solve the issue.

  WORKAROUND: Remove wireless interface's power management via Powertop

  ---
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ft 1884 F pulseaudio
   /dev/snd/controlC0:  ft 1884 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=54b265b9-4433-42d4-8d0f-fac028ee7030
  InstallationDate: Installed on 2014-03-05 (46 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20AQCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=b1cbc034-b66f-4f6c-9d61-507b8cb23ffe ro quiet
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET75WW (2.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET75WW(2.25):bd03/28/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1387865] Re: [Aorus X3+] Touchpad not working in Ubuntu 14.04 and 14.10

[Christopher M. Penalver]

** Description changed:

  Touchpad not working. I don't see the mouse pointer. Laptop is exactly
  the same as without the touchpad.
  
- I can plug a USB Mouse.
+ WORKAROUND: I can plug a USB Mouse.
+ 
+ Upstream URL: http://www.spinics.net/lists/linux-input/msg34324.html
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  levesque   2822 F pulseaudio
-  /dev/snd/controlC1:  levesque   2822 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  levesque   2822 F pulseaudio
+  /dev/snd/controlC1:  levesque   2822 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 30 21:21:08 2014
  HibernationDevice: RESUME=UUID=41f05731-4d43-4531-8579-69f950969e48
  InstallationDate: Installed on 2014-10-16 (14 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: GIGABYTE X3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=1ab1195f-fc7d-4896-81a7-59d1f67b50c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.16.0-24-generic N/A
-  linux-backports-modules-3.16.0-24-generic  N/A
-  linux-firmware 1.138
+  linux-restricted-modules-3.16.0-24-generic N/A
+  linux-backports-modules-3.16.0-24-generic  N/A
+  linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (5 days ago)
  dmi.bios.date: 07/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD04
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X3
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD04:bd07/04/2014:svnGIGABYTE:pnX3:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnX3:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: X3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

Title:
  [Aorus X3+] Touchpad not working in Ubuntu 14.04 and 14.10

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Touchpad not working. I don't see the mouse pointer. Laptop is exactly
  the same as without the touchpad.

  WORKAROUND: I can plug a USB Mouse.

  Upstream URL: http://www.spinics.net/lists/linux-input/msg34324.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  levesque   2822 F pulseaudio
   /dev/snd/controlC1:  levesque   2822 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 30 21:21:08 2014
  HibernationDevice: RESUME=UUID=41f05731-4d43-4531-8579-69f950969e48
  InstallationDate: Installed on 2014-10-16 (14 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: GIGABYTE X3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=1ab1195f-fc7d-4896-81a7-59d1f67b50c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (5 days ago)
  dmi.bios.date: 07/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD04
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X3
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD04:bd07/04/2014:svnGIGABYTE:pnX3:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnX3:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: X3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

-- 
Mailing 

[Kernel-packages] [Bug 1399142] Re: CVE-2010-5313

[John Johansen]

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

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Medium

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

Title:
  CVE-2010-5313

Status in linux package in Ubuntu:
  New
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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  New
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
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-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick 

[Kernel-packages] [Bug 1399200] [NEW] Qualcomm Atheros AR9485 (Asus R512C) - disabled in hardware at login

[Kaj Ailomaa]

Public bug reported:

To enable Qualcomm Atheros AR9485 Wireless Network Adapter I need to put
the computer in sleep mode, then wake it up. Voila! The wifi adapter is
activated.

This is a Asus R512C laptop. The function key for enabling/disabling
Wifi is not working, but I noticed waking up from sleep would
automatically activate the Wifi device.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-40-generic 3.13.0-40.69
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  infoglob   1609 F pulseaudio
CurrentDesktop: Unity
Date: Thu Dec  4 14:50:50 2014
HibernationDevice: RESUME=UUID=e0b9cb80-a840-4679-be18-b5b6fc3098ce
InstallationDate: Installed on 2014-12-04 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: ASUSTeK COMPUTER INC. X551CAP
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4bddae4-299f-4ecc-8f46-918a55db2024 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-40-generic N/A
 linux-backports-modules-3.13.0-40-generic  N/A
 linux-firmware 1.127.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X551CAP.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X551CAP
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.:bvrX551CAP.201:bd07/15/2013:svnASUSTeKCOMPUTERINC.:pnX551CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X551CAP
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

Title:
  Qualcomm Atheros AR9485 (Asus R512C) - disabled in hardware at login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To enable Qualcomm Atheros AR9485 Wireless Network Adapter I need to
  put the computer in sleep mode, then wake it up. Voila! The wifi
  adapter is activated.

  This is a Asus R512C laptop. The function key for enabling/disabling
  Wifi is not working, but I noticed waking up from sleep would
  automatically activate the Wifi device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-40-generic 3.13.0-40.69
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  infoglob   1609 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec  4 14:50:50 2014
  HibernationDevice: RESUME=UUID=e0b9cb80-a840-4679-be18-b5b6fc3098ce
  InstallationDate: Installed on 2014-12-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. X551CAP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4bddae4-299f-4ecc-8f46-918a55db2024 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551CAP.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551CAP
  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.:bvrX551CAP.201:bd07/15/2013:svnASUSTeKCOMPUTERINC.:pnX551CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551CAP
  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/1399200/+subscriptions

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Qualcomm Atheros AR9485 (Asus R512C) - disabled in hardware at login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To enable Qualcomm Atheros AR9485 Wireless Network Adapter I need to
  put the computer in sleep mode, then wake it up. Voila! The wifi
  adapter is activated.

  This is a Asus R512C laptop. The function key for enabling/disabling
  Wifi is not working, but I noticed waking up from sleep would
  automatically activate the Wifi device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-40-generic 3.13.0-40.69
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  infoglob   1609 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec  4 14:50:50 2014
  HibernationDevice: RESUME=UUID=e0b9cb80-a840-4679-be18-b5b6fc3098ce
  InstallationDate: Installed on 2014-12-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. X551CAP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4bddae4-299f-4ecc-8f46-918a55db2024 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551CAP.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551CAP
  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.:bvrX551CAP.201:bd07/15/2013:svnASUSTeKCOMPUTERINC.:pnX551CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551CAP
  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/1399200/+subscriptions

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

[Kernel-packages] [Bug 1398118] Re: linux: 3.16.0-26.35 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.16.0-26.35 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, 01. December 2014 18:19 UTC
  kernel-stable-Prepare-package-end:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 02. December 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. December 2014 17:05 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Verification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-end:Thursday, 04. December 2014 10:02 UTC
+ kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:03 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/1398118

Title:
  linux: 3.16.0-26.35 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-26.35 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, 01. December 2014 18:19 UTC
  kernel-stable-Prepare-package-end:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 02. December 2014 04:03 UTC
  ppa-package-testing-start:Tuesday, 02. December 2014 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. December 2014 17:05 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Verification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 02. December 2014 19:02 UTC
  kernel-stable-Regression-testing-end:Thursday, 04. December 2014 10:02 UTC
  kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:03 UTC

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

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

[Kernel-packages] [Bug 1396112] Re: linux: 3.13.0-41.70 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.13.0-41.70 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 12:01 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 22:56 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 22:56 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 22:56 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 16:56 
UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 26. November 2014 16:55 UTC
  kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 16:56 
UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 16:01 UTC
+ kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:02 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/1396112

Title:
  linux: 3.13.0-41.70 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 12:01 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 22:56 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 22:56 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 22:56 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 16:56 
UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 26. November 2014 16:55 UTC
  kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 16:56 UTC
  kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 16:56 
UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 16:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:02 UTC

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

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

[Kernel-packages] [Bug 899463] Re: CVE-2011-1162

[John Johansen]

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

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Low

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

Title:
  CVE-2011-1162

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:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
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-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Fix Released
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:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric 

[Kernel-packages] [Bug 1396072] Re: linux: 3.2.0-73.108 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.2.0-73.108 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 10:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 15:10 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 15:10 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 15:10 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 25. November 2014 19:55 UTC
  kernel-stable-Verification-testing-start:Tuesday, 25. November 2014 21:01 UTC
  kernel-stable-Certification-testing-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Monday, 01. December 2014 16:01 UTC
  kernel-stable-Verification-testing-end:Monday, 01. December 2014 16:01 UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 11:01 UTC
+ kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:02 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/1396072

Title:
  linux: 3.2.0-73.108 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 10:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 15:10 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 15:10 UTC
  ppa-package-testing-start:Tuesday, 25. November 2014 15:10 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 25. November 2014 19:55 UTC
  kernel-stable-Verification-testing-start:Tuesday, 25. November 2014 21:01 UTC
  kernel-stable-Certification-testing-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-Security-signoff-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-Regression-testing-start:Tuesday, 25. November 2014 21:02 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Monday, 01. December 2014 16:01 UTC
  kernel-stable-Verification-testing-end:Monday, 01. December 2014 16:01 UTC
  kernel-stable-Regression-testing-end:Wednesday, 03. December 2014 11:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:02 UTC

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

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

[Kernel-packages] [Bug 1396188] Re: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the version to be filled upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 15:03 UTC
  kernel-stable-master-bug:1396072
  kernel-stable-Certification-testing-end:Wednesday, 26. November 2014 21:02 UTC
  kernel-stable-Prepare-package-end:Thursday, 27. November 2014 14:02 UTC
  kernel-stable-Promote-to-proposed-start:Thursday, 27. November 2014 14:02 UTC
  ppa-package-testing-start:Thursday, 27. November 2014 14:02 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 27. November 2014 21:17 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Security-signoff-start:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Verification-testing-start:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Regression-testing-start:Thursday, 27. November 2014 23:02 UTC
+ kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:03 UTC

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow package-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 15:03 UTC
  kernel-stable-master-bug:1396072
  kernel-stable-Certification-testing-end:Wednesday, 26. November 2014 21:02 UTC
  kernel-stable-Prepare-package-end:Thursday, 27. November 2014 14:02 UTC
  kernel-stable-Promote-to-proposed-start:Thursday, 27. November 2014 14:02 UTC
  ppa-package-testing-start:Thursday, 27. November 2014 14:02 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 27. November 2014 21:17 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Security-signoff-start:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Verification-testing-start:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Regression-testing-start:Thursday, 27. November 2014 23:02 UTC
  kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:03 UTC

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

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

[Zemistr]

Same here :/
New Acer Aspire V17 Nitro Black Edition with Ubuntu 14.10 and no wifi. But, 
bluetooth is OK.

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 899466] Re: CVE-2011-2203

[John Johansen]

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Medium

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

Title:
  CVE-2011-2203

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
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-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Fix Committed
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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  

[Kernel-packages] [Bug 869237] Re: CVE-2011-2491

[John Johansen]

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Medium

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

Title:
  CVE-2011-2491

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:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Invalid
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-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Fix Committed
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:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in 

[Kernel-packages] [Bug 1206880] Re: Mouse clicks not detected in JAVA after touching eGalax touchscreen

[Christopher M. Penalver]

Nyyr, in order to find the tags area, as per 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206880/comments/19 :
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 a worst case Ctrl+F - bug description or Ctrl+F - tags

Despite this, when booting into the 3.18-rc7 kernel a few times, do you
consistently have to restart Xorg to get it to work, or was that a
fluke?

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

Title:
  Mouse clicks not detected in JAVA after touching eGalax touchscreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have all-in-one PC terminal with touchscreen with Ubuntu 10.10 and
  JAVA application on Oracle JAVA JRE with some buttons. Working fine.

  After I did a minimal clean install from Ubuntu Server 12.04 CD (just with 
fluxbox WM) and Oracle JAVA JRE I run the JAVA application via javaws. I can 
click the buttons in the JAVA application using mouse, but when I try the same 
with touchscreen, the mouse pointer moves to the place I touched but the button 
is not pressed. After that when trying to use the mouse again even the mouse 
clicks are not detected !!!
  At first I thought it is the application problem but the same applies to the 
javaws laucher windows as well.

  Configuration of X11 in both versions of Ubuntu seems to be the same
  (no xorg.conf, just calibration.conf), no other adjustments.

  Touchscreen in Fluxbox is working fine in both versions. Since the
  JAVA version is the same in both versions of Ubuntu it cannot be
  problem of JAVA.

  To me it seems that in Ubuntu 12.04 the touchscreen/mouse events are passed 
to the JAVA VM differently than in Ubuntu 10.10.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-40-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', 
'/dev/snd/pcmC0D4p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [  630.974265] perf samples too long (5026  5000), lowering 
kernel.perf_event_max_sample_rate to 25000
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=6d3a7fc5-93df-46a4-9dd2-4aa18bb16551
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
i386 (20140204)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: PhoenixAward 945GSE
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.13.0-40-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/01/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GSE
  dmi.board.vendor: PhoenixAward
  dmi.board.version: 6.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/01/2009:svnPhoenixAward:pn945GSE:pvr6.0:rvnPhoenixAward:rn945GSE:rvr6.0:cvn:ct3:cvr:
  dmi.product.name: 945GSE
  dmi.product.version: 6.0
  dmi.sys.vendor: PhoenixAward

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

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

[Kernel-packages] [Bug 1395269] Re: [e1000e] ethtool -t eth0 offline loses routing table

[Peter Cordes]

Found a time when I didn't mind rebooting, and tested tested
linux-image-3.18.0-031800rc7-generic version 3.18.0-031800rc7.201411302035

peter@tesla:~$ uname -a
Linux tesla 3.18.0-031800rc7-generic #201411302035 SMP Mon Dec 1 01:36:38 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

peter@tesla:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.0.0.10.0.0.0 UG0  00 eth0
10.0.0.00.0.0.0 255.0.0.0   U 0  00 eth0

peter@tesla:~$ sudo ethtool -t eth0 offline
The test result is FAIL
The test extra info:
Register test  (offline) 0
Eeprom test(offline) 0
Interrupt test (offline) 0
Loopback test  (offline) 0
Link test   (on/offline) 1

peter@tesla:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
10.0.0.00.0.0.0 255.0.0.0   U 0  00 eth0

peter@tesla:~$ sudo route add default gw 10.0.0.1
peter@tesla:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.0.0.10.0.0.0 UG0  00 eth0
10.0.0.00.0.0.0 255.0.0.0   U 0  00 eth0


dmesg (relevant section):

[ 2039.585309] e1000e :00:19.0 eth0: offline testing starting
[ 2039.805954] e1000e: eth0 NIC Link is Down
[ 2040.225964] e1000e :00:19.0 eth0: testing unshared interrupt
[ 2053.684783] e1000e :00:19.0: irq 29 for MSI/MSI-X
[ 2053.788074] e1000e :00:19.0: irq 29 for MSI/MSI-X
[ 2068.760891] e1000e: eth0 NIC Link is Up 10 Mbps Full Duplex, Flow Control: 
Rx/Tx
[ 2068.761001] e1000e :00:19.0 eth0: Link Speed was downgraded by SmartSpeed
[ 2068.761004] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO

So it takes about 18 seconds for my NIC to fall back to a 10baseT link
to my gigabit switch.  I think my switch may be dying, I've seen some
issues on other machines, too.

 If anyone's interested in working on fixing this, you could simulate
this by unplugging the ethernet cable as you press return on ethtool,
and wait 10 secs to plug it back in.  Or just ethtool -t offline with
your cable unplugged, I guess.


** Tags added: e1000e kernel-bug-exists-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/1395269

Title:
  [e1000e] ethtool -t eth0 offline loses routing table

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ethtool -t eth0 offline does the tests, but leaves the routing table
  with only the entry for the local network.  I had to sudo route add
  default gw 10.0.0.1, in my case.  The online test didn't do this.

  Ubuntu 14.04, ethtool 1:3.13-1

  Linux tesla 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC
  2014 x86_64 x86_64 x86_64 GNU/Linux

  ethtool -i eth0: 
  driver: e1000e
  version: 2.3.2-k
  firmware-version: 1.1-0
  bus-info: :00:19.0

  relevant kernel log:
  [637008.472410] e1000e :00:19.0 eth0: offline testing starting
  [637009.077985] e1000e :00:19.0 eth0: testing unshared interrupt
  [637022.468941] e1000e :00:19.0: irq 45 for MSI/MSI-X
  [637022.572094] e1000e :00:19.0: irq 45 for MSI/MSI-X
  [637022.572257] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [637037.432893] e1000e: eth0 NIC Link is Up 10 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [637037.433003] e1000e :00:19.0 eth0: Link Speed was downgraded by 
SmartSpeed
  [637037.433005] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO
  [637037.433035] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [637037.982611] net_ratelimit: 3 callbacks suppressed
  [637037.982623] IPv4: martian source 10.0.0.17 from 80.73.161.44, on dev eth0
  [637037.982628] ll header: : 00 19 d1 11 b4 9b 00 03 6d 11 34 1b 08 
00m.4...

  (the martian packets are from TCP connections that my router is still
  NATing to this machine, even though without its routing table, it's
  not happy to see them.)

   And yes, my e1000e is autonegotiating to 10baseT/Full on the same
  cables and switch that still works at 1000baseT with another machine,
  hence running self-tests...  I thought this machine used to run at
  1000baseT, weird if I went 5 years without noticing my desktop being
  slow.  Not what this bug report is about, though.

   The e1000e hardware is on a DG965WH Intel mobo (ICH8 / g965 graphics, 
first-gen core2)
  00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network 
Connection (rev 02)
  Subsystem: Intel Corporation Device 0001
  Flags: bus master, fast devsel, latency 0, IRQ 45
  Memory at e030 (32-bit, non-prefetchable) [size=128K]
  Memory at e0324000 (32-bit, non-prefetchable) [size=4K]
  I/O 

[Kernel-packages] [Bug 1383921] Re: kipmi0 process hangs with ipmitool

[Chris J Arges]

@matt-jarvis
Thanks for verifying this!

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

Title:
  kipmi0 process hangs with ipmitool

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  In Progress
Status in linux source package in Vivid:
  In Progress

Bug description:
  we're in the process of migrating from 12.04 to 14.04 and are noticing
  a problem apparently related to the kernel and ipmi.  after an
  indeterminate period of regular ipmi queries (e.g., nagios checks
  using ipmitool) the kipmi0 process pegs a cpu to ~100% usage and
  further ipmitool commands hang.  the former is not a huge problem as
  the process is niced and its cpu usage can be limited using the
  /sys/module/ipmi_si/parameters/kipmid_max_busy_us interface.  however,
  ipmitool's hanging severely degrades hardware monitoring.

  this problem initially reared its head in our enviroment on a handful
  of 12.04 hosts on which hwe kernels were installed.  of the dozen
  deployed 14.04 hosts, four have started displaying these symptoms in
  the past week.  all of the 12.04+hwe hosts were eventually affected; i
  believe that given enough time all of the 14.04 hosts would be, as
  well.  a reboot clears it up until its recurrence.

  red hat has a bug logged that appears to match this:
  https://bugzilla.redhat.com/show_bug.cgi?id=1090619  unfortunately the
  work-around and proposed fix (from a duplicate bug) are currently non-
  public.  it does look like they were able to identify the ipmi:
  simplify locking patch from commit id
  f60adf42ad55405d1b17e9e5c33fdb63f1eb8861 as the culprit. i have just
  finished building a kernel from linux-source-3.13.0=3.13.0-37.64
  w/this patch reversed and will deploy it to see if the problem is
  alleviated.

  thank you for your time and effort.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 18 13:11 seq
   crw-rw 1 root audio 116, 33 Oct 18 13:11 timer
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Oct 21 12:55:43 2014
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Supermicro X8DT6
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=/dev/md0 
ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw 
bootdegraded=true
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0c
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT6
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0c:bd05/15/2012:svnSupermicro:pnX8DT6:pvr1234567890:rvnSupermicro:rnX8DT6:rvr1234567890:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.name: X8DT6
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

[Dimitris Matanis]

Hmmm how can your bluetooth be OK, Zemistr? Are you sure you have the
same card? Have you manually installed some bluetooth driver?

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 869243] Re: CVE-2011-2496

[John Johansen]

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Medium

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

Title:
  CVE-2011-2496

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:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Invalid
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-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Fix Committed
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:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in 

[Kernel-packages] [Bug 869245] Re: CVE-2011-2517

[John Johansen]

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Medium

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

Title:
  CVE-2011-2517

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:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Invalid
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-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Fix Committed
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:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in 

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

[Zemistr]

Correction...

Bluetooth pretend like it is OK, but nothing found.
Even my phone does not find my notebook.
I have a new clean install of Ubuntu 14.10.

'lspci' say:

07:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)

In windows I install this:
Killer Wireless-AC 1525 Bluetooth – Windows 8.1 (Version 3.0.0.400)

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

[Zemistr]

How do I know if I have the same hardware?

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Seth Forshee]

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

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

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

[Kernel-packages] [Bug 1395343] Re: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop

[prost]

Hi,

   I have the same issue here. My laptop (Dell Latitude E6400) fails to resume 
from suspend in 14.10. The console has information about one of the CPUs 
locking up - I can't see any further information as 
I can't scroll any further.

I also have Ubuntu 14.04 installed side by side on this laptop and that
resumes without any problems.

I have no such problems with resume on another laptop (Dell latitude
E6520) with Ubuntu 14.10.

Let me know if it is ok to use apport-collect to send my data.


Thanks, 
 Prost.

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

Title:
  Ubuntu 14.10 Utopic suspend/resume not working for my Laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I
  first tried with the Live CD, on failing that, and thinking that
  suspend might need some disk to write to for the suspend info, I did a
  HD installation. But still, suspend/resume is still not working.

  On second attempt (after HD installation), I switched to console and
  close my Laptop lid. It suspended well, as it has always been. On
  resume, I see the repeating errors of `sda1` soft reset failure (or
  something like that). Minutes later, I start to see all kinds of disk
  related errors, disk sector writing error, ext4 journal error, etc.

  I thus think the reason of `resume` not working is that the HD is not
  waken up.

  This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic.

  Any more info that I can provide?

  Thanks

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

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

[Kernel-packages] [Bug 1395343] Re: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop

[Christopher M. Penalver]

prost, thank you for your comment. Unfortunately, this bug report is not scoped 
to you, your hardware, or your problem. However, so your hardware and problem 
may be tracked, please file a new report with Ubuntu by executing the following 
in a terminal while booted into the default Ubuntu 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
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
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.

As well, please do not announce in this report you created a new bug
report.

Thank you for your understanding.

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

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

Title:
  Ubuntu 14.10 Utopic suspend/resume not working for my Laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I
  first tried with the Live CD, on failing that, and thinking that
  suspend might need some disk to write to for the suspend info, I did a
  HD installation. But still, suspend/resume is still not working.

  On second attempt (after HD installation), I switched to console and
  close my Laptop lid. It suspended well, as it has always been. On
  resume, I see the repeating errors of `sda1` soft reset failure (or
  something like that). Minutes later, I start to see all kinds of disk
  related errors, disk sector writing error, ext4 journal error, etc.

  I thus think the reason of `resume` not working is that the HD is not
  waken up.

  This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic.

  Any more info that I can provide?

  Thanks

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

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

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: Under certain workloads a BUG in the xen-netfront driver is
+ getting triggered.
+ 
+ Fix: Remove the offending BUG, and a related BUG which would have also
+ been triggered by the same conditions.
+ 
+ Test Case: This bug has only been seen under certain workloads involving
+ haproxy and has proved challenging to reproduce. The fix has been
+ verified by an affected user, with the BUG replaced by a WARN to ensure
+ that the conditions which would have triggered the bug were actually
+ encountered.
+ 
+ Regression Potential: The fix has been verified and acked upstream.
+ Removing the BUGs will not affect cases which were not crashing
+ previously, and cases which were crashing can't really be made much
+ worse.
+ 
+ ---
+ 
  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud. Whenever
  I install haproxy and nginx on the same server, after hitting it for a
  while, a kernel panic is caused. However, the kernel panic does not show
  up in ubuntu 12.04.  The kernel panic is pasted at the end of the
  attachment.

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

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

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

[Dimitris Matanis]

You can look at the manufacturer's specs for an exact model of the wifi
card. If that's the driver you installed for windows then maybe you DO
have the same one, or at least a really similar variant!

For me the bluetooth icon in ubuntu (tray) does not even show up.

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)

[Felix Moreno]

Hi, i respect the work of the open source community, and they take
decissions because of they create the code and they will have to take
care of it, but 

Reduce the number of chars of the filename, just because the directory
is crypted is not at all a good decision.

Is like not use doors in a car because of is more safe to have only one
door at the top of the car, or becasue of the designer of the car
decided to put the door in the top

Is very conmon to use the number of chars ext4 (for example) offers, and
if you crypt a ext4 directory you should respect the max file chars of
ext4... if not, just create your own crypted file system with your own
limits.

Is a step in the wrong direction reduce the possibilites of a file
system just because of is crypt.

Bests.

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

Title:
  file name too long when creating new file (ecryptfs_lookup:
  lookup_one_len() returned [-36] on lower_dentry)

Status in eCryptfs:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Natty:
  Won't Fix
Status in linux source package in Natty:
  Won't Fix
Status in ecryptfs-utils source package in Oneiric:
  Won't Fix
Status in linux source package in Oneiric:
  Won't Fix
Status in ecryptfs-utils source package in Precise:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  ===
  IMPORTANT: eCryptfs can only store filenames of up to 143 characters when 
filename encryption is enabled. The remaining 112 characters are used for 
storing metadata such as the encrypted filename prefix, the signature of the 
filename encryption key, and an identifier for the cipher used, as well as 
random bytes to make /foo/file and /bar/file encrypt to different ciphertext 
and padding bytes to achieve proper cipher block size alignment.

  This bug is considered 'fixed' by the upstream maintainers. The
  eCryptfs kernel error message has been reduced to a debug level log
  message and eCryptfs now correctly reports its maximum supported
  filename length through the statfs() syscall. This is all that can be
  done without implementing a completely new encrypted filename design.
  A design that allows 255 character filenames without introducing other
  design limitations has not been identified and no one is currently
  working to come up with such a design.

  Please do not add comments or create new bugs saying that mv reports
  'File name too long' or that you can't create a long filename in your
  eCryptfs mounts. It is an unfortunate design limitation that cannot be
  avoided at this time.

  Please do create new bugs when an application generates filenames that are 
too long to be stored in an eCryptfs mount. The application may be able to use 
the statfs() syscall to check the filename length limits of eCryptfs. Note that 
this does not include something like a torrent or ftp client trying to download 
a file with a long filename. The application is not generating the filename in 
those cases, it is just downloading the file that the user told it to download.
  ===

  When trying to create a new file with a relatively long filename (f. ex. 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt)
  I get an error: file name to long, when in fact the file name is not to long, 
but the encrypted name created for this file is to long, so, the file was not 
created.

  this is no problem when I try to create a file, but when I'm copying a
  lot of files to my home folder I get some: filename to long error's
  and it's hard to fix (first locate the file, create shorter name, move
  again)

  so, maybe you could create a check for to long filenames?

  I'm using ext4 here...

  mv 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt
 /home/jens/
  mv: cannot stat 
`/home/jens/dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt':
 File name too long

  libecryptfs0:
    Installed: 71-0ubuntu2
    Candidate: 71-0ubuntu2
    Version table:
   *** 71-0ubuntu2 0
  500 http://be.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup

[Péter Prőhle]

The kernel 3.13.11-03131106-generic_3.13.11-03131106.201412021942_amd64
you were kind to build extra for me DOES WORK.

During the installation there was a message: Running depmod.
depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor 
information. Ignoring.

To be sure, I checked again, that the kernel 3.13.11-03131107-generic
from ppa does not work.

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

Title:
  kernel dependent deterministic view crash on X startup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36

  The phenomenon: just when the user interface starts at the end of the
  Ununtu startup, the screen reamins in one solid color (very light
  grey, this is the everage of my colors), except for the topmost 3-4
  scan lines, where one can see some sort of vibrating content.
  Sometimes there is a 1-3 seconds of normal operation just at the
  start, when Ctrl-Alt-F2 works, and swithing there one can work in the
  character terminal forever.  But as soon as the disorder in the X view
  appears, even the Ctrl-Alt-F2 console change does not work visually,
  however a blindly stroken Ctr-Alt-Del is correctly executed.

  What I know: (1) on the core i3 based laptop there is no trace of this
  kind of view crash, while in case of the Phenom x6 1100t and Radeon HD
  6570 based desktop machine the problem is fully deterministic.  (2)
  the problem is distro independet, i.e.:  I have it with Ubuntu 14.04 +
  kernel 3.13.0-37-generic, and also with Ubuntu 14.10 +
  3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel
  3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic.
  (3) In case of Ubuntu 14.04 in average every second or third boot gave
  a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2,
  while in case of Ubuntu 14.10 there is no such a short time slot when
  I could escape.  (4) my configuration is set to fall into my only user
  account directly, I will do experiments, whether the problem is there,
  if the startup is without falling into an account.

  If I can, I will apport log files with produced with the
  3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic.

  I try to send the remaining information after my work day, now I have to 
leave, sorry.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg:
   [   11.299825] init: plymouth-upstart-bridge main process ended, respawning
   [   11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
   [   11.329706] systemd-logind[1615]: Failed to start user service: Unknown 
unit: user@1000.service
   [   11.332093] systemd-logind[1615]: New session c1 of user prohlep.
   [   11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] 
[1002:6759] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:3195]
  InstallationDate: Installed on 2014-06-26 (124 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: System manufacturer System Product Name
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Tags:  utopic ubuntu compiz-0.9
  Uname: Linux 3.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: 

[Kernel-packages] [Bug 1348277] Re: module compile error for aarch64

[Joseph Salisbury]

** Tags added: kernel-da-key

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

Title:
  module compile error for aarch64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When compiling an external module for aarch64 on Ubuntu 14.04, the
  compiler generates the following error:

  In file included from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/netlink.h:6:0,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/uapi/scsi/scsi_netlink.h:25,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/scsi/scsi_transport_fc.h:32,
  edited
  /home/ctuffli/dev/ubuntu-trusty/include/linux/skbuff.h: In function 
‘skb_can_coalesce’:
  /home/ctuffli/dev/ubuntu-trusty/include/linux/skbuff.h:2255:14: error: 
comparison between signed and unsigned integer expressions 
[-Werror=sign-compare]
off == frag-page_offset + skb_frag_size(frag);
^
  cc1: all warnings being treated as errors
  cc1: all warnings being treated as errors

  Although something like the below quiets the warning, it isn't clear
  to me this is the correct change

  diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
  index e9b1a3c..e3623cc 100644
  --- a/include/linux/skbuff.h
  +++ b/include/linux/skbuff.h
  @@ -2252,7 +2252,7 @@ static inline bool skb_can_coalesce(struct sk_buff 
*skb, int i,
const struct skb_frag_struct *frag = skb_shinfo(skb)-frags[i 
- 1];
   
return page == skb_frag_page(frag) 
  -off == frag-page_offset + skb_frag_size(frag);
  +off == (int)(frag-page_offset + skb_frag_size(frag));
}
return false;
   }
  --- 
  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
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   17.335985] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  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
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   17.335985] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1385846] Re: NFS shares in FSTAB no longer mount at boot

[Forage]

@guillaume: my apologies for the confusion. The correct version should be 
nfs-common 1:1.2.8-9ubuntu1.1 (and linux 3.16.0-25.33 for that matter).
Make sure you enabled the Recommended updates (utopic-updates) repository in 
Software  Updates on the Updates tab if you did not get this update.

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Since moving to Ubuntu 14.10 my network shares in FSTAB no longer
  mount at startup.

  Once the machine has booted the following command mount -a fixes the
  issue and all mounts become available.

  This issue was not present in 14.04 and there are a number of people
  reporting issues in the forums:

  http://ubuntuforums.org/showthread.php?t=2249713
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  toxicshadow   2543 F pulseaudio
   /dev/snd/controlC0:  toxicshadow   2543 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=0b094f80-5aff-43e5-a66c-100a4274a339
  InstallationDate: Installed on 2014-04-18 (190 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=UUID=73d2e3f6-f93f-4bd2-9f69-be107307daef ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill:
   
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Rampage II Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd09/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIExtreme:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1398597] Re: ideapad yoga needs psmouse reload

[Joseph Salisbury]

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


v3.16-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/

If v3.16-rc4 does not exhibit the bug then test v3.16-rc6:
v3.16-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc6-utopic/

If v3.16-rc4 does exhibit the bug then test v3.16-rc2:
v3.16-rc2:  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc2-utopic/

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

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

Title:
  ideapad yoga needs psmouse reload

Status in linux package in Ubuntu:
  Triaged

Bug description:
  So, my often made fun of, lenovo ideapad yoga, since sometime in the
  14.10 development cycle needs an extra help to get the trackpad
  working.

  On boot the mouse pointer is not visible.

  If I open terminal and do rmmod psmouse; modprobe psmouse the
  pointer magically appears on first touch.

  Please help me as to how I can bisect / track down what the issue here
  is. Sometime in the past it was working reliably.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xnox   3161 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  2 22:49:55 2014
  HibernationDevice: RESUME=UUID=eee95b80-dde2-400c-bb49-e5f515c9242a
  InstallationDate: Installed on 2013-08-29 (460 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829)
  MachineType: LENOVO 2191
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=5c176060-d588-4044-87b6-50b785b931b1 ro quiet splash nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2014-11-16 (15 days ago)
  dmi.bios.date: 01/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN54WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

[Zemistr]

On wifi module is written QCA6174-5

https://wikidevi.com/wiki/Qualcomm_Atheros_Killer_Wireless-AC_1525

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1322068] Re: Turn on bluetooth with Fn+F12 not working

[Antoine Sibold]

As the two kernel versions are located in two different local repositories 
(raring and quantal), how can i merge the two trees?
Does i need to do this?

In the Maverick example the good and the bad kernel versions are located
in the same local repository (tree).

Thanks for answering

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

Title:
  Turn on bluetooth with Fn+F12 not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On clevo W253EU laptop :

  After installing Ubuntu 14.04 LTS, i cannot turn on Bluetooth with Fn+F12 as 
usual.
  I have tested other versions of Ubuntu the results are:

  Ubuntu 12.04.LTS it works
  Ubuntu 12.04.1 LTS it works
  Ubuntu 12.04.2 LTS it works
  Ubuntu 12.04.3 LTS it does not working
  Ubuntu 12.04.4 LTS it does not working

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sibold 1910 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 22 09:31:55 2014
  HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab
  InstallationDate: Installed on 2014-05-17 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

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

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

[Kernel-packages] [Bug 1394032] Re: Trusty isci module doesn't handle timeouts properly

[Jason Harley]

I've installed 3.13.0-41.70 on four machines for testing.  Will report
back shortly.

# dpkg -l | grep 3.13.0-41
ii  linux-headers-3.13.0-413.13.0-41.70 
 all  Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-41-generic3.13.0-41.70 
 amd64Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-41-generic  3.13.0-41.70 
 amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-41-generic3.13.0-41.70 
 amd64Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP

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

Title:
  Trusty isci module doesn't handle timeouts properly

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

Bug description:
  I'm currently running linux 3.13.0-39 on trusty with a disks plugged
  into an Intel C602 SATA/SAS controller.  Occasionally, a timeout
  and/or SAS event (I'm not 100% sure which..) isn't handled properly
  ('Unhandled error code') and  the kernel gets a bit upset.

  I have 12 different hosts with this controller and disk combination
  and all display the same behaviour (dmesg output):

  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 8808434fa600 timed 
out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 880843673d00 timed 
out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 88105081bc00 timed 
out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 88084378e100 timed 
out
  [Tue Nov 18 16:56:10 2014] sas: Enter sas_scsi_recover_host busy: 4 failed: 4
  [Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: cmd error handler
  [Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: dev error handler
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 9e 77 60 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 77494112
  [Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: 
I/O error -5 writing to inode 261733 (offset 0 size 0 starting block 5061868)
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
5061868
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 0f d0 e0 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 68145376
  [Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: 
I/O error -5 writing to inode 261710 (offset 0 size 0 starting block 3893276)
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
3893276
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 f8 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654520
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
1081919
  [Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 58 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654360
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
1081899
  [Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
  [Tue Nov 18 16:56:10 2014] sas: --- Exit sas_scsi_recover_host: busy: 0 
failed: 0 tries: 1
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 17 19:42 seq
   crw-rw 1 root audio 116, 33 Nov 17 19:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.5
  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 14.04
  

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Seth Forshee]

** Patch added: 
0001-xen-netfront-Remove-BUGs-on-paged-skb-data-which-cro.patch
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+attachment/4274127/+files/0001-xen-netfront-Remove-BUGs-on-paged-skb-data-which-cro.patch

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

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

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

[Kernel-packages] [Bug 1398497] Re: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault

[Rafael David Tinoco]

Just got confirmation from HP regarding X2APIC and PROLIANT SERVERS
using Ubuntu Linux:

Before GEN8.. all Proliant Servers did NOT support X2APIC. They had
firmware saying OS to NOT use X2APIC (and OS started supporting this by
commit: 41750d3, already included in kernel 3.2). The thing is.. for
these servers, opting out from X2APIC made them to use XAPIC IRQ
remapping (not supported).

-

So, for Proliant Servers BEFORE GEN8 the recommended cmdline is this:

nox2apic intermap=off

Obs: nox2apic might not be needed since firmware is saying for Linux to
optout from using x2apic. Anyway I prefer to recommend this flag to make
sure kernels before 3.2 still work (not the case here).

-

AFTER GEN8 (inclusive), the firmware STILL says that X2APIC must not be
used, but they ARE indeed supported by GEN8 (DL360, DL380). So proper
cmdlines are:

intremap=no_x2apic_optout # let X2APIC enabled with IRQ remapping

OR

nox2apic intermap=off # disable X2APIC AND IRQ remapping

X2APIC for these machines ONLY differs from XAPIC in question of IRQ
remapping (easier to implement). The other difference, where x2apic is
capable of addressing more CPUs, is not needed cause # of CPUs is low
enough.

This points out to my last finding, regarding:

*** cdcd629869fabcd38ebd24a03b0a05ec1cbcafb0 x86: Fix and improve 
cmpxchg_double{,_local}()
|__  fix several problems related to cmpxchg and 64bits 
!!!

cmpxchg is where instruction pointer is at (looks like) on the analyzed
dump.

Problem here is that kernel version from the core was erased from
ddebs.ubuntu and I'm using the next ddeb version. So I'm saying this
is the most likely to be happening since I can't objdump binary used
by analyzed system.

Things to be done:

1) Provide hotfix with this fix: cdcd629869f
2) Wait for intel_idle problem observation 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318551)
3) Recommend users either:

intremap=no_x2apic_optout OR nox2apic intermap=off

TOGETHER with intel_idle.max_cstate=0

until we fix intel_idle.

Thank you

Rafael Tinoco

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

Title:
  HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic -
  General Protection Fault

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress

Bug description:
  It was brought to my attention the following situation:

  
  We massively upgraded our Ubuntu 12.04 servers (most of them are HP
  DL360p Gen8 or DL380 Gen8) to 3.2.0-67 kernel And in the last 2-3
  days we already had to reboot 5 of them because they completely hang

  Some of them had the following messages under syslog :
  kernel: [384707.675479] general protection fault:  [#5666] SMP

  others had :
  kernel: [950725.612724] BUG: unable to handle kernel paging request

  All of them have this also :
  your BIOS is broken and requested that x2apic be disabled
  

  Comments bellow

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

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

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Brad Figg]

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

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

** Also affects: linux (Ubuntu Vivid)
   Importance: High
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

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

** Changed in: linux (Ubuntu Trusty)
   Status: New = 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/1275879

Title:
  Kernel panic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  In Progress

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

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

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

[Kernel-packages] [Bug 1398597] Re: ideapad yoga needs psmouse reload

[Dimitri John Ledkov]

@ jsalisbury

I thought I've narrowed it down already:

3.15 final is good
3.16 rc 1   is bad

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

Title:
  ideapad yoga needs psmouse reload

Status in linux package in Ubuntu:
  Triaged

Bug description:
  So, my often made fun of, lenovo ideapad yoga, since sometime in the
  14.10 development cycle needs an extra help to get the trackpad
  working.

  On boot the mouse pointer is not visible.

  If I open terminal and do rmmod psmouse; modprobe psmouse the
  pointer magically appears on first touch.

  Please help me as to how I can bisect / track down what the issue here
  is. Sometime in the past it was working reliably.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xnox   3161 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  2 22:49:55 2014
  HibernationDevice: RESUME=UUID=eee95b80-dde2-400c-bb49-e5f515c9242a
  InstallationDate: Installed on 2013-08-29 (460 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829)
  MachineType: LENOVO 2191
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=5c176060-d588-4044-87b6-50b785b931b1 ro quiet splash nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2014-11-16 (15 days ago)
  dmi.bios.date: 01/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN54WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1358373] Re: sed: -e expression #1, char 6: unknown command: `m'

[Brian Murray]

Hello Nicholas, or anyone else affected,

Accepted dkms into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.10 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

** Changed in: dkms (Ubuntu Trusty)
   Status: In Progress = Fix Committed

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

Title:
  sed: -e expression #1, char 6: unknown command: `m'

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Utopic:
  Fix Committed
Status in dkms package in Debian:
  Fix Released

Bug description:
  Initial dkms setup triggers a sed error, sed: -e expression #1, char
  6: unknown command: `m'. This error does not appear to affect the
  setup and it completes. See the log below:

  --

  sudo apt-get install virtualbox-dkms
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
virtualbox-dkms
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/556 kB of archives.
  After this operation, 4,494 kB of additional disk space will be used.
  Selecting previously unselected package virtualbox-dkms.
  (Reading database ... 321942 files and directories currently installed.)
  Preparing to unpack .../virtualbox-dkms_4.3.14-dfsg-1_all.deb ...
  Unpacking virtualbox-dkms (4.3.14-dfsg-1) ...
  Setting up virtualbox-dkms (4.3.14-dfsg-1) ...
  Loading new virtualbox-4.3.14 DKMS files...
  First Installation: checking all kernels...
  Building for 3.16.0-7-generic and 3.16.0-9-generic
  Building initial module for 3.16.0-7-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
  Building initial module for 3.16.0-9-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
   * Stopping VirtualBox kernel modules 
 [ OK ] 
   * Starting VirtualBox kernel modules 
 [ OK ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: virtualbox-dkms 4.3.14-dfsg-1
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1358373] Please test proposed package

[Brian Murray]

Hello Nicholas, or anyone else affected,

Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04 in a
few hours, and then in the -proposed repository.

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

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

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

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

Title:
  sed: -e expression #1, char 6: unknown command: `m'

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Utopic:
  Fix Committed
Status in dkms package in Debian:
  Fix Released

Bug description:
  Initial dkms setup triggers a sed error, sed: -e expression #1, char
  6: unknown command: `m'. This error does not appear to affect the
  setup and it completes. See the log below:

  --

  sudo apt-get install virtualbox-dkms
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
virtualbox-dkms
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/556 kB of archives.
  After this operation, 4,494 kB of additional disk space will be used.
  Selecting previously unselected package virtualbox-dkms.
  (Reading database ... 321942 files and directories currently installed.)
  Preparing to unpack .../virtualbox-dkms_4.3.14-dfsg-1_all.deb ...
  Unpacking virtualbox-dkms (4.3.14-dfsg-1) ...
  Setting up virtualbox-dkms (4.3.14-dfsg-1) ...
  Loading new virtualbox-4.3.14 DKMS files...
  First Installation: checking all kernels...
  Building for 3.16.0-7-generic and 3.16.0-9-generic
  Building initial module for 3.16.0-7-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
  Building initial module for 3.16.0-9-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
   * Stopping VirtualBox kernel modules 
 [ OK ] 
   * Starting VirtualBox kernel modules 
 [ OK ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: virtualbox-dkms 4.3.14-dfsg-1
  ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
  Uname: Linux 3.16.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 11:51:26 2014
 

[Kernel-packages] [Bug 1398597] Re: ideapad yoga needs psmouse reload

[Joseph Salisbury]

Sorry, missed that in comment #8.  I'll start a bisect between 3.15
final and 3.16-rc1 and post a test kernel shortly.

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

Title:
  ideapad yoga needs psmouse reload

Status in linux package in Ubuntu:
  Triaged

Bug description:
  So, my often made fun of, lenovo ideapad yoga, since sometime in the
  14.10 development cycle needs an extra help to get the trackpad
  working.

  On boot the mouse pointer is not visible.

  If I open terminal and do rmmod psmouse; modprobe psmouse the
  pointer magically appears on first touch.

  Please help me as to how I can bisect / track down what the issue here
  is. Sometime in the past it was working reliably.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xnox   3161 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  2 22:49:55 2014
  HibernationDevice: RESUME=UUID=eee95b80-dde2-400c-bb49-e5f515c9242a
  InstallationDate: Installed on 2013-08-29 (460 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829)
  MachineType: LENOVO 2191
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=5c176060-d588-4044-87b6-50b785b931b1 ro quiet splash nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2014-11-16 (15 days ago)
  dmi.bios.date: 01/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN54WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup

[Joseph Salisbury]

I built a test kernel up to the following commit: aed6386

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

Can you test this kernel and see 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/1386534

Title:
  kernel dependent deterministic view crash on X startup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36

  The phenomenon: just when the user interface starts at the end of the
  Ununtu startup, the screen reamins in one solid color (very light
  grey, this is the everage of my colors), except for the topmost 3-4
  scan lines, where one can see some sort of vibrating content.
  Sometimes there is a 1-3 seconds of normal operation just at the
  start, when Ctrl-Alt-F2 works, and swithing there one can work in the
  character terminal forever.  But as soon as the disorder in the X view
  appears, even the Ctrl-Alt-F2 console change does not work visually,
  however a blindly stroken Ctr-Alt-Del is correctly executed.

  What I know: (1) on the core i3 based laptop there is no trace of this
  kind of view crash, while in case of the Phenom x6 1100t and Radeon HD
  6570 based desktop machine the problem is fully deterministic.  (2)
  the problem is distro independet, i.e.:  I have it with Ubuntu 14.04 +
  kernel 3.13.0-37-generic, and also with Ubuntu 14.10 +
  3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel
  3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic.
  (3) In case of Ubuntu 14.04 in average every second or third boot gave
  a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2,
  while in case of Ubuntu 14.10 there is no such a short time slot when
  I could escape.  (4) my configuration is set to fall into my only user
  account directly, I will do experiments, whether the problem is there,
  if the startup is without falling into an account.

  If I can, I will apport log files with produced with the
  3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic.

  I try to send the remaining information after my work day, now I have to 
leave, sorry.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg:
   [   11.299825] init: plymouth-upstart-bridge main process ended, respawning
   [   11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
   [   11.329706] systemd-logind[1615]: Failed to start user service: Unknown 
unit: user@1000.service
   [   11.332093] systemd-logind[1615]: New session c1 of user prohlep.
   [   11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] 
[1002:6759] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:3195]
  InstallationDate: Installed on 2014-06-26 (124 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: System manufacturer System Product Name
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Tags:  utopic ubuntu compiz-0.9
  Uname: Linux 3.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu 1500 by themselves

[Joseph Salisbury]

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.18 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.18-rc7-vivid/

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

** Tags added: kernel-da-key

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

Title:
  bridges cannot have a mtu  1500 by themselves

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses
  to use a larger one. This is problematic when using bridges enslaving
  only virtual NICs (vnetX) like it's common with KVM guests.

  Steps to reproduce the problem

  1) sudo ip link add br-test0 type bridge # create an empty bridge
  2) sudo ip link add br-test0 mtu 9000# attempt to set MTU  1500
  3) ip link show dev br-test0# confirm MTU

  Here, 2) returns RTNETLINK answers: Invalid argument. One
  (cumbersome) way around this is:

  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0

  Then the bridge's MTU can be changed from anywhere to 9000.

  This bug is especially annoying for the virtualization case because
  the KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on
  the guest VMs.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
Installed: 3.13.0-41.70
Candidate: 3.13.0-41.70
Version table:
   *** 3.13.0-41.70 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  iproute2:
Installed: 3.12.0-2
Candidate: 3.12.0-2
Version table:
   *** 3.12.0-2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-41-generic N/A
   linux-backports-modules-3.13.0-41-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399064/+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 1358373] Re: sed: -e expression #1, char 6: unknown command: `m'

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/dkms

** Branch linked: lp:ubuntu/utopic-proposed/dkms

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

Title:
  sed: -e expression #1, char 6: unknown command: `m'

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Utopic:
  Fix Committed
Status in dkms package in Debian:
  Fix Released

Bug description:
  Initial dkms setup triggers a sed error, sed: -e expression #1, char
  6: unknown command: `m'. This error does not appear to affect the
  setup and it completes. See the log below:

  --

  sudo apt-get install virtualbox-dkms
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
virtualbox-dkms
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/556 kB of archives.
  After this operation, 4,494 kB of additional disk space will be used.
  Selecting previously unselected package virtualbox-dkms.
  (Reading database ... 321942 files and directories currently installed.)
  Preparing to unpack .../virtualbox-dkms_4.3.14-dfsg-1_all.deb ...
  Unpacking virtualbox-dkms (4.3.14-dfsg-1) ...
  Setting up virtualbox-dkms (4.3.14-dfsg-1) ...
  Loading new virtualbox-4.3.14 DKMS files...
  First Installation: checking all kernels...
  Building for 3.16.0-7-generic and 3.16.0-9-generic
  Building initial module for 3.16.0-7-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
  Building initial module for 3.16.0-9-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
   * Stopping VirtualBox kernel modules 
 [ OK ] 
   * Starting VirtualBox kernel modules 
 [ OK ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: virtualbox-dkms 4.3.14-dfsg-1
  ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
  Uname: Linux 3.16.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 11:51:26 2014
  InstallationDate: Installed on 2013-12-19 (241 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218)
  PackageArchitecture: all
  SourcePackage: virtualbox
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (100 days ago)

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

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

[Kernel-packages] [Bug 1206880] Re: Mouse clicks not detected in JAVA after touching eGalax touchscreen

[Nyyr]

Yes, whenever I boot into X, mouse works, touchscreen works in fluxbox,
but when I try to use touchscreen to click buttons in JAVA app, after
that I cannot click JAVA buttons even with mouse until X restart. In
fluxbox touchscreen works even after click on button in JAVA app (I
closed that JAVA app using touchscreen by clicking on the top-right X
control button of the window).

When I install manufacturer's driver (eGalax) for the touchscreen, all
works fine. It is strange that only JAVA handles these events
differently

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

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

Title:
  Mouse clicks not detected in JAVA after touching eGalax touchscreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have all-in-one PC terminal with touchscreen with Ubuntu 10.10 and
  JAVA application on Oracle JAVA JRE with some buttons. Working fine.

  After I did a minimal clean install from Ubuntu Server 12.04 CD (just with 
fluxbox WM) and Oracle JAVA JRE I run the JAVA application via javaws. I can 
click the buttons in the JAVA application using mouse, but when I try the same 
with touchscreen, the mouse pointer moves to the place I touched but the button 
is not pressed. After that when trying to use the mouse again even the mouse 
clicks are not detected !!!
  At first I thought it is the application problem but the same applies to the 
javaws laucher windows as well.

  Configuration of X11 in both versions of Ubuntu seems to be the same
  (no xorg.conf, just calibration.conf), no other adjustments.

  Touchscreen in Fluxbox is working fine in both versions. Since the
  JAVA version is the same in both versions of Ubuntu it cannot be
  problem of JAVA.

  To me it seems that in Ubuntu 12.04 the touchscreen/mouse events are passed 
to the JAVA VM differently than in Ubuntu 10.10.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-40-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', 
'/dev/snd/pcmC0D4p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [  630.974265] perf samples too long (5026  5000), lowering 
kernel.perf_event_max_sample_rate to 25000
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=6d3a7fc5-93df-46a4-9dd2-4aa18bb16551
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
i386 (20140204)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: PhoenixAward 945GSE
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.13.0-40-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/01/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GSE
  dmi.board.vendor: PhoenixAward
  dmi.board.version: 6.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/01/2009:svnPhoenixAward:pn945GSE:pvr6.0:rvnPhoenixAward:rn945GSE:rvr6.0:cvn:ct3:cvr:
  dmi.product.name: 945GSE
  dmi.product.version: 6.0
  dmi.sys.vendor: PhoenixAward

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

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

[Kernel-packages] [Bug 1399010] Re: Random freeze of UI and input for ~30s

[Joseph Salisbury]

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


** Tags added: kernel-da-key

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

Title:
  Random freeze of UI and input for ~30s

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 14.10
  Release:  14.10
  Linux andy-Pangolin-Performance 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 
12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  This has happened a few times, the UI freezes and no input works for
  ~30s and then something resets/releases, all the inputs are then run
  and everything appears to be normal again.

  Note I did have Firefox nightly and icedtea-7-plugin installed (not
  sure if related to the freezes but these are the only things I have
  installed recently since the freezes have been occurring)

  The output of dmesg [0] also suggests a similar/or the same issue as
  [1]

  0 - http://pastebin.ubuntu.com/9358472/
  1 - https://bugzilla.kernel.org/show_bug.cgi?id=64431

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andy   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  3 22:53:31 2014
  HibernationDevice: RESUME=UUID=c5bf783f-d936-4a4c-9469-9c4a9685ca92
  InstallationDate: Installed on 2014-11-03 (30 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: System76, Inc. Pangolin Performance
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=589d892c-e903-4e66-8aa4-a457b38cc391 ro acpi_os_name=Linux acpi_osi= 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Pangolin Performance
  dmi.board.vendor: System76, Inc.
  dmi.board.version: panp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/25/2012:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp9:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp9:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: Pangolin Performance
  dmi.product.version: panp9
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1385846] Re: NFS shares in FSTAB no longer mount at boot

[guillaume ramelet]

@forage : thanx, fixed with nfs-common 1:1.2.8-9ubuntu1.1

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Since moving to Ubuntu 14.10 my network shares in FSTAB no longer
  mount at startup.

  Once the machine has booted the following command mount -a fixes the
  issue and all mounts become available.

  This issue was not present in 14.04 and there are a number of people
  reporting issues in the forums:

  http://ubuntuforums.org/showthread.php?t=2249713
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  toxicshadow   2543 F pulseaudio
   /dev/snd/controlC0:  toxicshadow   2543 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=0b094f80-5aff-43e5-a66c-100a4274a339
  InstallationDate: Installed on 2014-04-18 (190 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=UUID=73d2e3f6-f93f-4bd2-9f69-be107307daef ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill:
   
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Rampage II Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd09/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIExtreme:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1399200] Re: Qualcomm Atheros AR9485 (Asus R512C) - disabled in hardware at login

[Joseph Salisbury]

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.18 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.18-rc7-vivid/

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

Title:
  Qualcomm Atheros AR9485 (Asus R512C) - disabled in hardware at login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  To enable Qualcomm Atheros AR9485 Wireless Network Adapter I need to
  put the computer in sleep mode, then wake it up. Voila! The wifi
  adapter is activated.

  This is a Asus R512C laptop. The function key for enabling/disabling
  Wifi is not working, but I noticed waking up from sleep would
  automatically activate the Wifi device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-40-generic 3.13.0-40.69
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  infoglob   1609 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec  4 14:50:50 2014
  HibernationDevice: RESUME=UUID=e0b9cb80-a840-4679-be18-b5b6fc3098ce
  InstallationDate: Installed on 2014-12-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. X551CAP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4bddae4-299f-4ecc-8f46-918a55db2024 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551CAP.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551CAP
  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.:bvrX551CAP.201:bd07/15/2013:svnASUSTeKCOMPUTERINC.:pnX551CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551CAP
  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/1399200/+subscriptions

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

[Kernel-packages] [Bug 1348277] Re: module compile error for aarch64

[Joseph Salisbury]

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  module compile error for aarch64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When compiling an external module for aarch64 on Ubuntu 14.04, the
  compiler generates the following error:

  In file included from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/netlink.h:6:0,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/uapi/scsi/scsi_netlink.h:25,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/scsi/scsi_transport_fc.h:32,
  edited
  /home/ctuffli/dev/ubuntu-trusty/include/linux/skbuff.h: In function 
‘skb_can_coalesce’:
  /home/ctuffli/dev/ubuntu-trusty/include/linux/skbuff.h:2255:14: error: 
comparison between signed and unsigned integer expressions 
[-Werror=sign-compare]
off == frag-page_offset + skb_frag_size(frag);
^
  cc1: all warnings being treated as errors
  cc1: all warnings being treated as errors

  Although something like the below quiets the warning, it isn't clear
  to me this is the correct change

  diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
  index e9b1a3c..e3623cc 100644
  --- a/include/linux/skbuff.h
  +++ b/include/linux/skbuff.h
  @@ -2252,7 +2252,7 @@ static inline bool skb_can_coalesce(struct sk_buff 
*skb, int i,
const struct skb_frag_struct *frag = skb_shinfo(skb)-frags[i 
- 1];
   
return page == skb_frag_page(frag) 
  -off == frag-page_offset + skb_frag_size(frag);
  +off == (int)(frag-page_offset + skb_frag_size(frag));
}
return false;
   }
  --- 
  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
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   17.335985] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  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
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   17.335985] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1348442] Re: Unable to compile proprietary kernel driver under ARM64 Ubuntu 14.04

[Joseph Salisbury]

** Tags added: kernel-key

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

Title:
  Unable to compile proprietary kernel driver under ARM64 Ubuntu 14.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Compiling a kernel driver with a proprietary license (i.e.
  MODULE_LICENSE(Proprietary)) for ARM64 under Ubuntu 14.04 results in
  the following link error:

  # make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 -C 
/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic/ M=`pwd` modules
  make: Entering directory 
`/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic'
CC [M]  /home/ctuffli/dev/ocs/test/test.o
  In file included from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/printk.h:5:0,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/kernel.h:13,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/sched.h:15,
   from 
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/compat.h:25,
   from 
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/stat.h:23,
   from /home/ctuffli/dev/ubuntu-trusty/include/linux/stat.h:5,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/module.h:10,
   from /home/ctuffli/dev/ocs/test/test.c:1:
  /home/ctuffli/dev/ocs/test/test.c: In function ‘__inittest’:
  /home/ctuffli/dev/ubuntu-trusty/include/linux/init.h:297:4: warning: return 
from incompatible pointer type [enabled by default]
{ return initfn; } \
  ^
  /home/ctuffli/dev/ocs/test/test.c:34:1: note: in expansion of macro 
‘module_init’
   module_init(test_init);
   ^
Building modules, stage 2.
MODPOST 1 modules
  FATAL: modpost: GPL-incompatible module test.ko uses GPL-only symbol 
'xen_dma_ops'
  make[3]: *** [__modpost] Error 1
  make[2]: *** [modules] Error 2
  make[1]: *** [sub-make] Error 2
  make: *** [all] Error 2
  make: Leaving directory 
`/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic'

  It appears that including linux/dma-mapping.h is enough to trigger this 
problem
  # nm -gl test.o | grep xen_start_info
   U xen_start_info   
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/dma-mapping.h:42

  Test case attached
  --- 
  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
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   15.365073] xgene-enet 1702.ethernet eth0: eth0: link up 
1000 Mbps
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Donald Stufft]

I've tested the fix that Seth has and it resolved our issue completely.
The first time that 14.04 had been stable on our HAProxy load balancer
boxes.

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  In Progress

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

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

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

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu 1500 by themselves

[Simon Déziel]

On 12/04/2014 01:44 PM, Joseph Salisbury wrote:
 Did this issue occur in a previous version of Ubuntu, or is this a new
 issue?

This is reproducible on 12.04 too.

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

Also reproducible with:

$ uname -a
Linux xeon 3.18.0-031800rc7-generic #201411302035 SMP Mon Dec 1 01:36:38
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux


Thanks


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

** Description changed:

  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses to
  use a larger one. This is problematic when using bridges enslaving only
  virtual NICs (vnetX) like it's common with KVM guests.
  
  Steps to reproduce the problem
  
  1) sudo ip link add br-test0 type bridge # create an empty bridge
- 2) sudo ip link add br-test0 mtu 9000# attempt to set MTU  1500
- 3) ip link show dev br-test0# confirm MTU
+ 2) sudo ip link set br-test0 mtu 9000# attempt to set MTU  1500
+ 3) ip link show dev br-test0 # confirm MTU
  
  Here, 2) returns RTNETLINK answers: Invalid argument. One (cumbersome)
  way around this is:
  
  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0
  
  Then the bridge's MTU can be changed from anywhere to 9000.
  
  This bug is especially annoying for the virtualization case because the
  KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on the
  guest VMs.
  
  Additional information:
  
  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
-   Installed: 3.13.0-41.70
-   Candidate: 3.13.0-41.70
-   Version table:
-  *** 3.13.0-41.70 0
- 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.13.0-41.70
+   Candidate: 3.13.0-41.70
+   Version table:
+  *** 3.13.0-41.70 0
+ 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  iproute2:
-   Installed: 3.12.0-2
-   Candidate: 3.12.0-2
-   Version table:
-  *** 3.12.0-2 0
- 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.12.0-2
+   Candidate: 3.12.0-2
+   Version table:
+  *** 3.12.0-2 0
+ 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  simon  4594 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-41-generic N/A
-  linux-backports-modules-3.13.0-41-generic  N/A
-  linux-firmware 1.127.10
+  linux-restricted-modules-3.13.0-41-generic N/A
+  linux-backports-modules-3.13.0-41-generic  N/A
+  linux-firmware 1.127.10
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

-- 
You 

[Kernel-packages] [Bug 1398596] Re: [Revert] arm64: optimized copy_to_user and copy_from_user assembly code

[Andrew Cloke]

** Tags added: hs-arm64

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

Title:
  [Revert] arm64: optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  [Impact]
  Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.

  http://www.spinics.net/lists/arm-kernel/msg381811.html

  [Test Case]
  Put the system under memory pressure.

  [Regression Potential]
  It will cause a performance regression on certain workloads on arm64 systems.

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

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

[Kernel-packages] [Bug 1348442] Re: Unable to compile proprietary kernel driver under ARM64 Ubuntu 14.04

[Andy Whitcroft]

You are not permitted to link to GPL only symbols if your module is not
GPL, the error there is telling you you are trying to do exactly that:

FATAL: modpost: GPL-incompatible module test.ko uses GPL-only symbol
'xen_dma_ops'

Either one has to work with the upstream contributor to relax that
symbol to EXPORT_SYMBOL, or you need to find an alternative.

If you do not expect your device to encounter systems running on XEN you
could likely short circut this by defining xen_dma_ops as NULL. before
you include that header:

#define xen_dma_ops NULL

Though if you do that you should also check for xen_initial_domain() in
your init (if you can call that) and abort if true.

That said, it seems rather unfortuanate that those ops being _GPL
renders he whole DMA infratructure useless.  It is worth approaching
whoever committed that and asking for that symbol to be relaxed.

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

Title:
  Unable to compile proprietary kernel driver under ARM64 Ubuntu 14.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Compiling a kernel driver with a proprietary license (i.e.
  MODULE_LICENSE(Proprietary)) for ARM64 under Ubuntu 14.04 results in
  the following link error:

  # make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 -C 
/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic/ M=`pwd` modules
  make: Entering directory 
`/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic'
CC [M]  /home/ctuffli/dev/ocs/test/test.o
  In file included from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/printk.h:5:0,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/kernel.h:13,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/sched.h:15,
   from 
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/compat.h:25,
   from 
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/stat.h:23,
   from /home/ctuffli/dev/ubuntu-trusty/include/linux/stat.h:5,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/module.h:10,
   from /home/ctuffli/dev/ocs/test/test.c:1:
  /home/ctuffli/dev/ocs/test/test.c: In function ‘__inittest’:
  /home/ctuffli/dev/ubuntu-trusty/include/linux/init.h:297:4: warning: return 
from incompatible pointer type [enabled by default]
{ return initfn; } \
  ^
  /home/ctuffli/dev/ocs/test/test.c:34:1: note: in expansion of macro 
‘module_init’
   module_init(test_init);
   ^
Building modules, stage 2.
MODPOST 1 modules
  FATAL: modpost: GPL-incompatible module test.ko uses GPL-only symbol 
'xen_dma_ops'
  make[3]: *** [__modpost] Error 1
  make[2]: *** [modules] Error 2
  make[1]: *** [sub-make] Error 2
  make: *** [all] Error 2
  make: Leaving directory 
`/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic'

  It appears that including linux/dma-mapping.h is enough to trigger this 
problem
  # nm -gl test.o | grep xen_start_info
   U xen_start_info   
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/dma-mapping.h:42

  Test case attached
  --- 
  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
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   15.365073] xgene-enet 1702.ethernet eth0: eth0: link up 
1000 Mbps
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1397028] Re: Add support for the backported lts-utopic stack

[Brian Murray]

Hello Alberto, or anyone else affected,

Accepted bcmwl into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.248
+bdcom-0ubuntu0.1 in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: bcmwl (Ubuntu Trusty)
   Status: In Progress = Fix Committed

** Tags added: verification-needed

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

Title:
  Add support for the backported lts-utopic stack

Status in bcmwl package in Ubuntu:
  Invalid
Status in bcmwl source package in Precise:
  In Progress
Status in bcmwl source package in Trusty:
  Fix Committed

Bug description:
  SRU request:

  [Impact]

   * As a result of this bug, bcmwl-kernel-source will fail to build the
  module against linux-generic-lts-utopic in Ubuntu 14.04.2.

  [Test Case]

   * Enable the trusty-proposed repository and install bcmwl-kernel-
  source (6.30.223.248+bdcom-0ubuntu0.1).

   * Install linux-generic-lts-utopic

   * If the package installs without errors from DKMS with both the
  linux-generic and linux-generic-lts-utopic kernels, then the patches
  work correctly.

  [Regression Potential]

   * The patches that I backported from 15.04 will preserve the current
  driver behaviour on linux-generic (3.13) and linux-generic-lts-utopic
  (3.16), thanks to the use of specific macros in the code which check
  the kernel version. As a result, no regressions of any kind can be
  expected on these kernels. As a plus, support for kernels up to 3.18
  is also included.

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

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

[Kernel-packages] [Bug 1348442] Re: Unable to compile proprietary kernel driver under ARM64 Ubuntu 14.04

[Andy Whitcroft]

The dependencies on xen_dma_ops were introduced in the commit below:

  commit c7e9bc548325f19635e7ac7cd5f3ec587228952e
  Author: Stefano Stabellini stefano.stabell...@eu.citrix.com
  Date:   Fri Oct 18 16:01:26 2013 +

arm/xen: get_dma_ops: return xen_dma_ops if we are running as
xen_initial_domain

and the ops themselves in:

  commit 83862ccfc0a03212fde43b4ac29c28381828768b
  Author: Stefano Stabellini stefano.stabell...@eu.citrix.com
  Date:   Thu Oct 10 13:40:44 2013 +

xen/arm,arm64: enable SWIOTLB_XEN

So at least it seems to be the same person here.

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

Title:
  Unable to compile proprietary kernel driver under ARM64 Ubuntu 14.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Compiling a kernel driver with a proprietary license (i.e.
  MODULE_LICENSE(Proprietary)) for ARM64 under Ubuntu 14.04 results in
  the following link error:

  # make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 -C 
/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic/ M=`pwd` modules
  make: Entering directory 
`/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic'
CC [M]  /home/ctuffli/dev/ocs/test/test.o
  In file included from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/printk.h:5:0,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/kernel.h:13,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/sched.h:15,
   from 
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/compat.h:25,
   from 
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/stat.h:23,
   from /home/ctuffli/dev/ubuntu-trusty/include/linux/stat.h:5,
   from 
/home/ctuffli/dev/ubuntu-trusty/include/linux/module.h:10,
   from /home/ctuffli/dev/ocs/test/test.c:1:
  /home/ctuffli/dev/ocs/test/test.c: In function ‘__inittest’:
  /home/ctuffli/dev/ubuntu-trusty/include/linux/init.h:297:4: warning: return 
from incompatible pointer type [enabled by default]
{ return initfn; } \
  ^
  /home/ctuffli/dev/ocs/test/test.c:34:1: note: in expansion of macro 
‘module_init’
   module_init(test_init);
   ^
Building modules, stage 2.
MODPOST 1 modules
  FATAL: modpost: GPL-incompatible module test.ko uses GPL-only symbol 
'xen_dma_ops'
  make[3]: *** [__modpost] Error 1
  make[2]: *** [modules] Error 2
  make[1]: *** [sub-make] Error 2
  make: *** [all] Error 2
  make: Leaving directory 
`/home/ctuffli/dev/ubuntu-trusty/debian/build/build-generic'

  It appears that including linux/dma-mapping.h is enough to trigger this 
problem
  # nm -gl test.o | grep xen_start_info
   U xen_start_info   
/home/ctuffli/dev/ubuntu-trusty/arch/arm64/include/asm/dma-mapping.h:42

  Test case attached
  --- 
  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
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   15.365073] xgene-enet 1702.ethernet eth0: eth0: link up 
1000 Mbps
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1397028] Re: Add support for the backported lts-utopic stack

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/bcmwl

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

Title:
  Add support for the backported lts-utopic stack

Status in bcmwl package in Ubuntu:
  Invalid
Status in bcmwl source package in Precise:
  In Progress
Status in bcmwl source package in Trusty:
  Fix Committed

Bug description:
  SRU request:

  [Impact]

   * As a result of this bug, bcmwl-kernel-source will fail to build the
  module against linux-generic-lts-utopic in Ubuntu 14.04.2.

  [Test Case]

   * Enable the trusty-proposed repository and install bcmwl-kernel-
  source (6.30.223.248+bdcom-0ubuntu0.1).

   * Install linux-generic-lts-utopic

   * If the package installs without errors from DKMS with both the
  linux-generic and linux-generic-lts-utopic kernels, then the patches
  work correctly.

  [Regression Potential]

   * The patches that I backported from 15.04 will preserve the current
  driver behaviour on linux-generic (3.13) and linux-generic-lts-utopic
  (3.16), thanks to the use of specific macros in the code which check
  the kernel version. As a result, no regressions of any kind can be
  expected on these kernels. As a plus, support for kernels up to 3.18
  is also included.

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

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

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu 1500 by themselves

[Joseph Salisbury]

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

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

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

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

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

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

Title:
  bridges cannot have a mtu  1500 by themselves

Status in linux package in Ubuntu:
  Triaged

Bug description:
  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses
  to use a larger one. This is problematic when using bridges enslaving
  only virtual NICs (vnetX) like it's common with KVM guests.

  Steps to reproduce the problem

  1) sudo ip link add br-test0 type bridge # create an empty bridge
  2) sudo ip link set br-test0 mtu 9000# attempt to set MTU  1500
  3) ip link show dev br-test0 # confirm MTU

  Here, 2) returns RTNETLINK answers: Invalid argument. One
  (cumbersome) way around this is:

  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0

  Then the bridge's MTU can be changed from anywhere to 9000.

  This bug is especially annoying for the virtualization case because
  the KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on
  the guest VMs.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
    Installed: 3.13.0-41.70
    Candidate: 3.13.0-41.70
    Version table:
   *** 3.13.0-41.70 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  iproute2:
    Installed: 3.12.0-2
    Candidate: 3.12.0-2
    Version table:
   *** 3.12.0-2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-41-generic N/A
   linux-backports-modules-3.13.0-41-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1366538] Re: Synchronisation/close /dev/sdX: i/o error on target host

[Joseph Salisbury]

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

Title:
  Synchronisation/close /dev/sdX: i/o error on target host

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 14.04.1 x86-64
  wanting to unmout a pata drive (usb attached), I get this (title) Warning 
from libparted when gparted launches.
  Same issue with another pc x86-64
  Errors retries then ignore, shred /dev/sdi fails:

  shred: /dev/sdi : pass 1/2 (random)…
  shred: /dev/sdi : pass 1/2 (random)…231MiB/94GiB 0 %
  shred: /dev/sdi : failure of fdatasync: i/o error on target host

  I reached to shred the drive from a 12.04.4 i386 pc with no error.

  Sep  7 15:07:08 nux kernel: [261448.072475] usb 5-1: new high-speed USB 
device number 10 using xhci_hcd
  Sep  7 15:07:09 nux kernel: [261448.202999] usb 5-1: New USB device found, 
idVendor=04cf, idProduct=8818
  Sep  7 15:07:09 nux kernel: [261448.203008] usb 5-1: New USB device strings: 
Mfr=1, Product=2, SerialNumber=0
  Sep  7 15:07:09 nux kernel: [261448.203013] usb 5-1: Product: USB Mass 
Storage Device
  Sep  7 15:07:09 nux kernel: [261448.203018] usb 5-1: Manufacturer: Myson 
Century, Inc.
  Sep  7 15:07:09 nux kernel: [261448.205463] usb-storage 5-1:1.0: USB Mass 
Storage device detected
  Sep  7 15:07:09 nux kernel: [261448.205673] scsi20 : usb-storage 5-1:1.0
  Sep  7 15:07:10 nux kernel: [261449.206849] scsi 20:0:0:0: Direct-Access 
HTS72101 0G9AT00  MCZO PQ: 0 ANSI: 0 CCS
  Sep  7 15:07:10 nux kernel: [261449.207763] sd 20:0:0:0: Attached scsi 
generic sg7 type 0
  Sep  7 15:07:10 nux kernel: [261449.207901] sd 20:0:0:0: [sdi] 195371568 
512-byte logical blocks: (100 GB/93.1 GiB)
  Sep  7 15:07:10 nux kernel: [261449.208068] sd 20:0:0:0: [sdi] Write Protect 
is off
  Sep  7 15:07:10 nux kernel: [261449.208074] sd 20:0:0:0: [sdi] Mode Sense: 00 
14 00 00
  Sep  7 15:07:10 nux kernel: [261449.208280] sd 20:0:0:0: [sdi] Write cache: 
enabled, read cache: enabled, doesn't support DPO or FUA
  Sep  7 15:07:10 nux kernel: [261449.555232]  sdi: unknown partition table
  Sep  7 15:07:10 nux kernel: [261449.555926] sd 20:0:0:0: [sdi] Attached SCSI 
disk
  Sep  7 15:07:43 nux kernel: [261482.219026] end_request: critical target 
error, dev sdi, sector 0
  Sep  7 15:07:52 nux kernel: [261492.015180] end_request: critical target 
error, dev sdi, sector 0
  Sep  7 15:07:55 nux kernel: [261494.261159] end_request: critical target 
error, dev sdi, sector 0
  Sep  7 15:16:23 nux kernel: [262003.027005] end_request: critical target 
error, dev sdi, sector 0
  Sep  7 15:16:35 nux kernel: [262014.215352] end_request: critical target 
error, dev sdi, sector 0
  Sep  7 15:16:35 nux kernel: [262014.859651] end_request: critical target 
error, dev sdi, sector 0

  [EDIT:
  Once shreded, no error on the i386, but still same error on the 2 x86-64]

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

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

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  In Progress

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

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

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

[Kernel-packages] [Bug 1398597] Re: ideapad yoga needs psmouse reload

[Joseph Salisbury]

I started a kernel bisect between v3.15 final and v3.16-rc1. The kernel
bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
aaeb2554337217dfa4eac2fcc90da7be540b9a73

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

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

Title:
  ideapad yoga needs psmouse reload

Status in linux package in Ubuntu:
  Triaged

Bug description:
  So, my often made fun of, lenovo ideapad yoga, since sometime in the
  14.10 development cycle needs an extra help to get the trackpad
  working.

  On boot the mouse pointer is not visible.

  If I open terminal and do rmmod psmouse; modprobe psmouse the
  pointer magically appears on first touch.

  Please help me as to how I can bisect / track down what the issue here
  is. Sometime in the past it was working reliably.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xnox   3161 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  2 22:49:55 2014
  HibernationDevice: RESUME=UUID=eee95b80-dde2-400c-bb49-e5f515c9242a
  InstallationDate: Installed on 2013-08-29 (460 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829)
  MachineType: LENOVO 2191
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=5c176060-d588-4044-87b6-50b785b931b1 ro quiet splash nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2014-11-16 (15 days ago)
  dmi.bios.date: 01/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN54WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1358373] Re: sed: -e expression #1, char 6: unknown command: `m'

[Chris Kankiewicz]

Installed dkms 2.2.0.3-1.1ubuntu5.14.10 from utopic-proposed, ran 'sudo
service vboxdrv setup' successfully.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  sed: -e expression #1, char 6: unknown command: `m'

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Utopic:
  Fix Committed
Status in dkms package in Debian:
  Fix Released

Bug description:
  Initial dkms setup triggers a sed error, sed: -e expression #1, char
  6: unknown command: `m'. This error does not appear to affect the
  setup and it completes. See the log below:

  --

  sudo apt-get install virtualbox-dkms
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
virtualbox-dkms
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/556 kB of archives.
  After this operation, 4,494 kB of additional disk space will be used.
  Selecting previously unselected package virtualbox-dkms.
  (Reading database ... 321942 files and directories currently installed.)
  Preparing to unpack .../virtualbox-dkms_4.3.14-dfsg-1_all.deb ...
  Unpacking virtualbox-dkms (4.3.14-dfsg-1) ...
  Setting up virtualbox-dkms (4.3.14-dfsg-1) ...
  Loading new virtualbox-4.3.14 DKMS files...
  First Installation: checking all kernels...
  Building for 3.16.0-7-generic and 3.16.0-9-generic
  Building initial module for 3.16.0-7-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
  Building initial module for 3.16.0-9-generic
  Done.

  vboxdrv:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  vboxpci.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/

  sed: -e expression #1, char 6: unknown command: `m'
  depmod

  DKMS: install completed.
   * Stopping VirtualBox kernel modules 
 [ OK ] 
   * Starting VirtualBox kernel modules 
 [ OK ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: virtualbox-dkms 4.3.14-dfsg-1
  ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
  Uname: Linux 3.16.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 11:51:26 2014
  InstallationDate: Installed on 2013-12-19 (241 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218)
  PackageArchitecture: all
  SourcePackage: virtualbox
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (100 days ago)

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

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

[Kernel-packages] [Bug 1322068] Re: Turn on bluetooth with Fn+F12 not working

[Christopher M. Penalver]

Antoine Sibold, you would want to switch to bisecting the mainline
kernel as outlined in the article.

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

Title:
  Turn on bluetooth with Fn+F12 not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On clevo W253EU laptop :

  After installing Ubuntu 14.04 LTS, i cannot turn on Bluetooth with Fn+F12 as 
usual.
  I have tested other versions of Ubuntu the results are:

  Ubuntu 12.04.LTS it works
  Ubuntu 12.04.1 LTS it works
  Ubuntu 12.04.2 LTS it works
  Ubuntu 12.04.3 LTS it does not working
  Ubuntu 12.04.4 LTS it does not working

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sibold 1910 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 22 09:31:55 2014
  HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab
  InstallationDate: Installed on 2014-05-17 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

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

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

[Kernel-packages] [Bug 1206880] Re: Mouse clicks not detected in JAVA after touching eGalax touchscreen

[Christopher M. Penalver]

Nyyr, for dependency testing, would you be able to test this using a
different desktop environment or would the application have to be
significantly re-written?

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

Title:
  Mouse clicks not detected in JAVA after touching eGalax touchscreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have all-in-one PC terminal with touchscreen with Ubuntu 10.10 and
  JAVA application on Oracle JAVA JRE with some buttons. Working fine.

  After I did a minimal clean install from Ubuntu Server 12.04 CD (just with 
fluxbox WM) and Oracle JAVA JRE I run the JAVA application via javaws. I can 
click the buttons in the JAVA application using mouse, but when I try the same 
with touchscreen, the mouse pointer moves to the place I touched but the button 
is not pressed. After that when trying to use the mouse again even the mouse 
clicks are not detected !!!
  At first I thought it is the application problem but the same applies to the 
javaws laucher windows as well.

  Configuration of X11 in both versions of Ubuntu seems to be the same
  (no xorg.conf, just calibration.conf), no other adjustments.

  Touchscreen in Fluxbox is working fine in both versions. Since the
  JAVA version is the same in both versions of Ubuntu it cannot be
  problem of JAVA.

  To me it seems that in Ubuntu 12.04 the touchscreen/mouse events are passed 
to the JAVA VM differently than in Ubuntu 10.10.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-40-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', 
'/dev/snd/pcmC0D4p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [  630.974265] perf samples too long (5026  5000), lowering 
kernel.perf_event_max_sample_rate to 25000
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=6d3a7fc5-93df-46a4-9dd2-4aa18bb16551
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
i386 (20140204)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: PhoenixAward 945GSE
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.13.0-40-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/01/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GSE
  dmi.board.vendor: PhoenixAward
  dmi.board.version: 6.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/01/2009:svnPhoenixAward:pn945GSE:pvr6.0:rvnPhoenixAward:rn945GSE:rvr6.0:cvn:ct3:cvr:
  dmi.product.name: 945GSE
  dmi.product.version: 6.0
  dmi.sys.vendor: PhoenixAward

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

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

[Kernel-packages] [Bug 1399440] [NEW] Add iwlwifi firmware monitor support in utopic

[Seth Forshee]

Public bug reported:

SRU Justification:

Impact: These patches do not fix a bug. Instead, they help Intel collect
data from devices which are experiencing errors due to bugs in the
firmware which will help them fix these bugs.

Test Case: I have tested these patches to verify that I did not observe
any regressions with the affected hardware and to verify the
functionality of the firmware monitor support.

Regression Potential: The firmware monitor support defaults to being
disabled and is only enabled when the fw_monitor=1 option is passed to
iwlwifi, which helps to limit the possibility of regressions under
normal use. I have also reviewed and tested the patches without finding
any regressions.

---

These were introduced in 3.17 and then backported to 3.16 by Intel [1].
They aren't upstream stable material, but since Intel wireless is
probably the most widely used wireless hardware among Ubuntu users it
makes sense for us to take the patches if they will help Intel fix bugs
in their firmware.

[1]
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/129744

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: Seth Forshee (sforshee)
 Status: 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/1399440

Title:
  Add iwlwifi firmware monitor support in utopic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:

  Impact: These patches do not fix a bug. Instead, they help Intel
  collect data from devices which are experiencing errors due to bugs in
  the firmware which will help them fix these bugs.

  Test Case: I have tested these patches to verify that I did not
  observe any regressions with the affected hardware and to verify the
  functionality of the firmware monitor support.

  Regression Potential: The firmware monitor support defaults to being
  disabled and is only enabled when the fw_monitor=1 option is passed to
  iwlwifi, which helps to limit the possibility of regressions under
  normal use. I have also reviewed and tested the patches without
  finding any regressions.

  ---

  These were introduced in 3.17 and then backported to 3.16 by Intel
  [1]. They aren't upstream stable material, but since Intel wireless is
  probably the most widely used wireless hardware among Ubuntu users it
  makes sense for us to take the patches if they will help Intel fix
  bugs in their firmware.

  [1]
  http://permalink.gmane.org/gmane.linux.kernel.wireless.general/129744

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

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

[Kernel-packages] [Bug 1399010] Re: Random freeze of UI and input for ~30s

[Andrew Hayzen]

Thanks for the instructions, I have managed to install the later kernel
version and will report back if I have any freezes on this as well.

Linux andy-Pangolin-Performance 3.18.0-031800rc7-generic #201411302035
SMP Mon Dec 1 01:36:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Random freeze of UI and input for ~30s

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 14.10
  Release:  14.10
  Linux andy-Pangolin-Performance 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 
12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  This has happened a few times, the UI freezes and no input works for
  ~30s and then something resets/releases, all the inputs are then run
  and everything appears to be normal again.

  Note I did have Firefox nightly and icedtea-7-plugin installed (not
  sure if related to the freezes but these are the only things I have
  installed recently since the freezes have been occurring)

  The output of dmesg [0] also suggests a similar/or the same issue as
  [1]

  0 - http://pastebin.ubuntu.com/9358472/
  1 - https://bugzilla.kernel.org/show_bug.cgi?id=64431

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andy   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  3 22:53:31 2014
  HibernationDevice: RESUME=UUID=c5bf783f-d936-4a4c-9469-9c4a9685ca92
  InstallationDate: Installed on 2014-11-03 (30 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: System76, Inc. Pangolin Performance
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=589d892c-e903-4e66-8aa4-a457b38cc391 ro acpi_os_name=Linux acpi_osi= 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Pangolin Performance
  dmi.board.vendor: System76, Inc.
  dmi.board.version: panp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/25/2012:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp9:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp9:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: Pangolin Performance
  dmi.product.version: panp9
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 869250] Re: CVE-2011-2525

[John Johansen]

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Medium

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Medium

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

Title:
  CVE-2011-2525

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:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Invalid
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-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Fix Committed
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:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in 

[Kernel-packages] [Bug 1394368] Re: Bluetooth with AR9462 doesn't work (New ID /Firmware)

[Luis Alvarado]

In my case, with the Asus Z87-Pro motherboard (With the latest firmware)
I am having similar problems like Wallcom mentioned. The wireless (For
G, N or AC) works randomly. Reboot and it works. Reboot and it does not.

The problem gets worse if I activate the Bluetooth where it creates a
kind of weird issue with Network Manager where I can't connect to any
wifi AP.

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

Title:
  Bluetooth with AR9462 doesn't work (New ID /Firmware)

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This is (kind of) a duplicate of:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884
  (please read)

  I can't use Bluetooth with my AR9462 WLAN/BT-Combo.
  In the link above, it has been fixed, but not for my Adapter ID/Firmware:

  System:
  Ubuntu 14.10 utopic 64bit - 3.16.0-24-generic x86_64

  lspci -nnk
  02:00.0 Network controller [0280]: Qualcomm Atheros AR9462
  Wireless Network Adapter [168c:0034] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0802]
   Kernel driver in use: ath9k

  lsusb (identified Bluetooth Device)
  Bus 002 Device 003: ID 04ca:300d Lite-On Technology Corp.

  ath9k.conf
  options ath9k btcoex_enable=1

  The 04ca:300d ID is not in the Kernel, so i added it via dkms.

  I took ath3k.c and btusb.c out of the 3.16.0-24-generic source files
  and changed them:

  diff -urN ./linux-3.16.0/drivers/bluetooth/ath3k.c 
/usr/src/ar9462-1.5.1/ath3k.c
  --- ./linux-3.16.0/drivers/bluetooth/ath3k.c  2014-08-04 00:25:02.0 
+0200
  +++ /usr/src/ar9462-1.5.1/ath3k.c 2014-11-19 21:12:46.646265890 +0100
  @@ -85,6 +85,7 @@
    { USB_DEVICE(0x04CA, 0x3007) },
    { USB_DEVICE(0x04CA, 0x3008) },
    { USB_DEVICE(0x04CA, 0x300b) },
  + { USB_DEVICE(0x04CA, 0x300d) },
    { USB_DEVICE(0x0930, 0x0219) },
    { USB_DEVICE(0x0930, 0x0220) },
    { USB_DEVICE(0x0b05, 0x17d0) },
  @@ -134,6 +135,7 @@
    { USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
  + { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },

  diff -urN ./linux-3.16.0/drivers/bluetooth/btusb.c 
/usr/src/ar9462-1.5.1/btusb.c
  --- ./linux-3.16.0/drivers/bluetooth/btusb.c  2014-08-04 00:25:02.0 
+0200
  +++ /usr/src/ar9462-1.5.1/btusb.c 2014-11-19 21:12:46.646265890 +0100
  @@ -157,6 +157,7 @@
    { USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
  + { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },

  sudo dkms add -m ar9462 -v 1.5.1
  sudo dkms build -m ar9462 -v 1.5.1
  sudo dkms install -m ar9462 -v 1.5.1

  (DKMS package in the same style/versioning as in the bug report above)

  dkms status
  ar9462, 1.5.1, 3.16.0-24-generic, x86_64: installed

  Now the new output:

  dmesg | egrep 'ath3|ar3|Bluet'
  [2.787819] Bluetooth: Core ver 2.19
  [2.787833] Bluetooth: HCI device and connection manager initialized
  [2.787839] Bluetooth: HCI socket layer initialized
  [2.787842] Bluetooth: L2CAP socket layer initialized
  [2.787848] Bluetooth: SCO socket layer initialized
  [2.793551] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [2.793554] Bluetooth: BNEP filters: protocol multicast
  [2.793561] Bluetooth: BNEP socket layer initialized
  [3.130779] Bluetooth: Patch file not found ar3k/AthrBT_0x11020100.dfu
  [3.130783] Bluetooth: Loading patch file failed
  [3.130788] ath3k: probe of 2-5:1.0 failed with error -12
  [3.130823] usbcore: registered new interface driver ath3k
  [9.776503] Bluetooth: RFCOMM TTY layer initialized
  [9.776512] Bluetooth: RFCOMM socket layer initialized
  [9.776517] Bluetooth: RFCOMM ver 1.11

  My patch works, but just like in the bug report above, a Firmware file is 
missing:
  AthrBT_0x11020100.dfu

  I found it neither in linux-firmware 
(http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ar3k)
  nor elsewhere.

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

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

[Kernel-packages] [Bug 1394032] Re: Trusty isci module doesn't handle timeouts properly

[Jason Harley]

I've confirmed that 3.13.0-41.70 isn't affected by bug #1346917 (KVM
NUMA stability), so this is an improvement over 3.13.11.11.

I will continue to test 3.13.0-41.70 for isci stability.

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

Title:
  Trusty isci module doesn't handle timeouts properly

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

Bug description:
  I'm currently running linux 3.13.0-39 on trusty with a disks plugged
  into an Intel C602 SATA/SAS controller.  Occasionally, a timeout
  and/or SAS event (I'm not 100% sure which..) isn't handled properly
  ('Unhandled error code') and  the kernel gets a bit upset.

  I have 12 different hosts with this controller and disk combination
  and all display the same behaviour (dmesg output):

  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 8808434fa600 timed 
out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 880843673d00 timed 
out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 88105081bc00 timed 
out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command 88084378e100 timed 
out
  [Tue Nov 18 16:56:10 2014] sas: Enter sas_scsi_recover_host busy: 4 failed: 4
  [Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: cmd error handler
  [Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: dev error handler
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 9e 77 60 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 77494112
  [Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: 
I/O error -5 writing to inode 261733 (offset 0 size 0 starting block 5061868)
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
5061868
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 0f d0 e0 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 68145376
  [Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: 
I/O error -5 writing to inode 261710 (offset 0 size 0 starting block 3893276)
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
3893276
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 f8 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654520
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
1081919
  [Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 58 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654360
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 
1081899
  [Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
  [Tue Nov 18 16:56:10 2014] sas: --- Exit sas_scsi_recover_host: busy: 0 
failed: 0 tries: 1
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 17 19:42 seq
   crw-rw 1 root audio 116, 33 Nov 17 19:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.5
  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 14.04
  HibernationDevice: RESUME=/dev/mapper/root-swap
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT-PT
  Package: linux (not 

[Kernel-packages] [Bug 880890] Re: CVE-2011-3209

[John Johansen]

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

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Low

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

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Low

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

Title:
  CVE-2011-3209

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:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
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-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Fix Released
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:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric