date:20150903

** Description changed:

- Error: 
+ Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down
  
  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).
  
  Attempted repair, failed:
- Laptop has sleeping ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.
+ Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.
  
  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
- 3. Put the computer to sleep when it's too hot.
+ 3. Put the computer to suspend when it's too hot.
  
  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  user   2171 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
-  Socket 0:
-no product info available
+  Socket 0:
+    no product info available
  PccardctlStatus:
-  Socket 0:
-no card
+  Socket 0:
+    no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-62-generic N/A
-  linux-backports-modules-3.13.0-62-generic  N/A
-  linux-firmware 1.127.15
+  linux-restricted-modules-3.13.0-62-generic N/A
+  linux-backports-modules-3.13.0-62-generic  N/A
+  linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio

[Kernel-packages] [Bug 1484980] Re: AVRCP support for Ubuntu Phone

2015-09-03 Thread Simon Fels

>From what jhodap told me the sound indicator might be the one
responsible for this.

** Also affects: indicator-sound (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: indicator-sound
   Importance: Undecided
   Status: New

** No longer affects: indicator-sound

** Package changed: bluez (Ubuntu) => canonical-devices-system-image

** Changed in: canonical-devices-system-image
   Status: Invalid => Confirmed

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

Title:
  AVRCP support for Ubuntu Phone

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  Hey!

  I bought a bluetooth headphone, but the volume, next and previous
  track buttons don't work with my Ubuntu Phone, because it doesn't
  support AVRCP. So please implement this feature. :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1484980/+subscriptions

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

2015-09-03 Thread Simon Fels

@JoiHap: Can you test this again with the latest rc-proposed image?

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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

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

2015-09-03 Thread Colin Law

718749d56214aa97015fe01b76b6d6dd0c171796
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031253_amd64.deb

is GOOD

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1446786] Re: Wrong read balance when a drive is write-mostly

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

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

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

Title:
  Wrong read balance when a drive is write-mostly

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

Bug description:
  This bug related to `mdadm` `--write-mostly` option. When we create
  SSD for read operation, but want to use HDD to mirror SSD content we
  can create RAID-1 with SSD and 'write-mostly' HDD disk.

  In Ubuntu kernel there is a bug, which lead to havy read from both SSD
  and HDD drives. More over if we add HDD as regular disk and SSD as a
  'write-mostly' replica most read operations will go to SSD drive
  (which is clear from sources and we have prove it in our setup).

  In upstream kernel sources this was already fixed:

  
https://github.com/torvalds/linux/commit/63a7d0a9160421a23baac407847e484e8488d12a

  Could you backport this functionality? - This patch looks safe to
  apply as is.

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

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

[Kernel-packages] [Bug 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

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

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

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

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

** Changed in: linux (Ubuntu Precise)
   Status: Triaged => 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/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

Have you tried cleaning the fans and vents to ensure they are free of
dust?

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

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1491656] Re: ACPI: Enabled 4 GPEs in block 00 to 3F

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

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

Title:
  ACPI: Enabled 4 GPEs in block 00 to 3F

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [0.161885] ACPI: Enabled 4 GPEs in block 00 to 3F

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:30:23 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491655] Re: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150619/hwxface-580)

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

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

Title:
  ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_]
  (20150619/hwxface-580)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [0.131913] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State 
[\_S2_] (20150619/hwxface-580)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:28:18 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491652] Re: ACPI: Executed 1 blocks of module-level executable AML code

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

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

Title:
  ACPI: Executed 1 blocks of module-level executable AML code

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [0.123773] ACPI: Executed 1 blocks of module-level executable AML code

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:24:19 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1491658] Re: systemd[1]: Failed to insert module 'kdbus': Function not implemented

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

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

Title:
  systemd[1]: Failed to insert module 'kdbus': Function not implemented

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [3.770177] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:35:22 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491648] Re: ACPI: All ACPI Tables successfully acquired

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

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

Title:
  ACPI: All ACPI Tables successfully acquired

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [0.010758] ACPI: All ACPI Tables successfully acquired

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:17:47 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491657] Re: usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes

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

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

Title:
  usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep desc says
  80 microframes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [1.468281] usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep 
desc says 80 microframes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:33:18 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

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

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/v4.2-unstable/


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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1491510] Re: Touchpad not working

Does the touchpad start working if you boot the prior kernel version?

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

** Tags added: needs-bisect

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  touchpad not working after installing upgrade from 12.04 to 14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dilesh 2401 F pulseaudio
   /dev/snd/controlC0:  dilesh 2401 F pulseaudio
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-yuanli-precise-amd64-20140320-1
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=22f8102e-a1a5-44c6-a067-1ef05dd6a664
  InstallationDate: Installed on 2014-10-23 (314 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20140320-07:21
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=f9c316c9-331e-4cc7-aac8-3f73e8f90f97 ro i915.modeset=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  Tags:  trusty
  Uname: Linux 3.13.0-62-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-09-01 (0 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1491653] Re: ACPI: Dynamic OEM Table Load:

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

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

Title:
  ACPI: Dynamic OEM Table Load:

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  0.128167] ACPI: Dynamic OEM Table Load:
  [0.128181] ACPI: SSDT 0x880119CA5000 000784 (v01 PmRef  Cpu0Cst  
3001 INTL 20061109)
  [0.128951] ACPI: Dynamic OEM Table Load:
  [0.128961] ACPI: SSDT 0x880119F3D000 000303 (v01 PmRef  ApIst
3000 INTL 20061109)
  [0.129627] ACPI: Dynamic OEM Table Load:
  [0.129635] ACPI: SSDT 0x880119F65C00 000119 (v01 PmRef  ApCst
3000 INTL 20061109)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:26:47 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491761] Re: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and 15.04

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

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/v4.2-unstable/

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

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

Title:
  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E
  PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and
  15.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
   (eth0): carrier is OFF
  Sep  2 20:00:32 cq71 NetworkManager[579]:  (eth0): new Ethernet device 
(driver: 'r8169' ifindex: 2)
  Sep  2 20:00:32 cq71 NetworkManager[579]:  (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/1
  Sep  2 20:00:32 cq71 NetworkManager[579]:  (eth0): device state change: 
unmanaged -> unavailable (reason 'managed') [10 20 2]
  Sep  2 20:00:32 cq71 NetworkManager[579]:  [1441216832.927980] 
[platform/nm-linux-platform.c:2250] link_change(): Netlink error changing link 
2:   mtu 0 (1) driver 'r8169' udi 
'/sys/devices/pci:00/:00:1c.1/:03:00.0/net/eth0': Invalid address 
for specified address family
  Sep  2 20:00:32 cq71 NetworkManager[579]:  (eth0): preparing device

  r8169 :03:00.0 eth0: RTL8102e at 0xc90004778000,
  00:00:00:00:00:00, XID 04c0 IRQ 27

  03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Subsystem: Hewlett-Packard Company Device 306c
Kernel driver in use: r8169

*-network DISABLED
 description: Ethernet interface
 product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: eth0
 version: 02
 size: 100Mbit/s
 capacity: 100Mbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list rom 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full latency=0 link=no multicast=yes port=MII 
speed=100Mbit/s
 resources: irq:27 ioport:2000(size=256) memory:d401-d4010fff 
memory:d400-d400 memory:d500-d500

  i compiled the r8101 module from here:
  
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  after i put in a "cloned mac adress" the card is functional.
  there is also an old bug report of this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/256331

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

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

[Kernel-packages] [Bug 1491647] Re: ACPI: RSDP 0x00000000000F0120 000024 (v02 SECCSD)

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

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

Title:
  ACPI: RSDP 0x000F0120 24 (v02 SECCSD)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [0.00] ACPI: RSDP 0x000F0120 24 (v02 SECCSD)
  [0.00] ACPI: XSDT 0xDAFFE170 94 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: FACP 0xDAFEE000 00010C (v05 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: DSDT 0xDAFF1000 0092DA (v02 SECCSD IVB-CPT  
 INTL 20061109)
  [0.00] ACPI: FACS 0xDAF7B000 40
  [0.00] ACPI: SLIC 0xDAFFD000 000176 (v01 SECCSD LH43STAR 
0002 PTL  0001)
  [0.00] ACPI: SSDT 0xDAFFB000 001068 (v01 SECCSD PtidDevc 
1000 INTL 20061109)
  [0.00] ACPI: ASF! 0xDAFF A5 (v32 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: HPET 0xDAFED000 38 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: APIC 0xDAFEC000 98 (v03 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: MCFG 0xDAFEB000 3C (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: FPDT 0xDAFEA000 54 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: SSDT 0xDAFE9000 0007D7 (v01 PmRef  Cpu0Ist  
3000 INTL 20061109)
  [0.00] ACPI: SSDT 0xDAFE8000 000AD0 (v01 PmRef  CpuPm
3000 INTL 20061109)
  [0.00] ACPI: UEFI 0xDAFE7000 3E (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: UEFI 0xDAFE6000 42 (v01 PTLCOMBUF   
0001 PTL  0001)
  [0.00] ACPI: POAT 0xDAF78000 55 (v03 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: UEFI 0xDAFE5000 00022E (v01 SECCSD LH43STAR 
0002 PTL  0002)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:14:54 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491649] Re: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

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

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

Title:
  ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [0.013502] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
  [0.013504] ENERGY_PERF_BIAS: View and update with 
x86_energy_perf_policy(8)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:20:52 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491651] Re: mtrr: your CPUs had inconsistent variable MTRR settings

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

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

Title:
  mtrr: your CPUs had inconsistent variable MTRR settings

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [0.116009] mtrr: your CPUs had inconsistent variable MTRR settings

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1187 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1187 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep  2 20:22:45 2015
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

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

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

Title:
  Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04
  installation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Current Behavior
  ==
  1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

  Reference Verification
  ==
  1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
  2. Which similar project/product passed/failed? NA

  Steps to reproduce the problem
  ==
  1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
  2. Power on system and install Ubuntu 14.04.
  3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

  Expected Behavior
  ==
  1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 
install.

  Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

  
  Copied from private bug 1454945.

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

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

[Kernel-packages] [Bug 1400319] Re: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10 and 15.04

Hi Chris,

Do you have a list of the patches you mention in comment #27?  I'd like
to check the status upstream.

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

Title:
  [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10 and 15.04

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Utopic:
  Confirmed
Status in linux source package in Utopic:
  Confirmed
Status in kexec-tools source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  While testing the final build of 14.10 32bit we found that kernel
  panic cannot be activated for an installation on a Hyper-V VM.

  Repro rate: 100%
  Repro details:
  Hyper-V: Server 2012 R2
  VM: Ubuntu 14.10 32bit

  Kdump is enabled in the config file at /etc/default/kdump-tools

  Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m
  | 384M-:256M

  VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this
  in combination with the values for crashkernel.

  Trying to start the kdump service:
  root@ubuntu1410i386:~# /etc/init.d/kdump-tools start
  Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes...
  locate_hole failed
  * failed to load kdump kernel
  ---

  root@ubuntu1410i386:~# cat /sys/kernel/kexec_crash_loaded
  0

  
  If the conversion from hex to dec is right, the mentioned memory mapping of 
0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then 
related to the RAM allocation nor the crashkernel value used.
  --- 
  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.7-0ubuntu8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=5a5d0aa4-b8ee-4bf7-b1b9-761b7d1550b6
  InstallationDate: Installed on 2014-10-31 (37 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release i386 
(20141022.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=83fb481a-8898-4adc-bf31-4e160f5f0ce8 ro crashkernel=128M-:64M
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  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
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPREQUEST of 10.226.59.102 on 
eth0 to 10.184.232.100 port 67 (xid=0x4b67ffa3)
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPACK of 10.226.59.102 from 
10.184.232.100
   Dec  8 08:16:47 ubuntu1410i386 dhclient: bound to 10.226.59.102 -- renewal 
in 13914 seconds.
   Dec  8 10:10:47 ubuntu1410i386 kernel: [1840786.031060] init: tty1 main 
process ended, respawning
  _MarkForUpload: True
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7176-0455-3377-8479-3268-6677-66
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work

I just wanted to check what patches we think are needed to resolve this
bug?  I build a test kernel with a cherry pick of only commit 4e4bd36f.
However, it looks like there may be a total of three patches required:

commit 4e4bd36f
commit 7ace9917
commit e298ff75

Joshua or nmeier can you confirm this?  If so, I'll build test kernels
with all three of these commits for all Ubuntu releases.

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

Title:
  Memory balloning in Hyper-V generation 2 does not work

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

Bug description:
  The generation 2 VM has been assinged a memory range of 512 MiB-
  4096MiB with a starting memory of 512 MiB. It should get additional
  memory when needed, but the total available memory in the VM stays at
  the intial 512 MiB and the kernel starts swapping instead of
  allocating more memory from the host.

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

[Kernel-packages] [Bug 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

According to the mailing list:

* We've got positive testing results from Jerry Kao (tested HSW and BDW)
   and myself [David Henningsson] (tested SKL)

* Upstream, Takashi Iwai has now merged the corresponding patch set into
   his for-next tree and it's been scheduled to reach 4.3-rc1.

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

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

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

[Kernel-packages] [Bug 1490606] tarf (amd64) - tests ran: 197, failed: 13

tests ran: 197, failed: 13;
  
http://kernel.ubuntu.com/testing/tarf__3.19.0-28.30__2015-09-03_08-57-00/results-index.html

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

Title:
  linux: 3.19.0-28.30 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC

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

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

[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-09-03 Thread Alexandre Magno

@corradoventu, I ask if you followed my comment #155.

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

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

2015-09-03 Thread Elias Aarnio

I also get "Device does not have any RAPL domains, cannot power measure
power usage."

Thinkpad X201, Ubuntu 14.04 LTS.

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Does this issue go away if you boot back into the prior kernel?

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

** Tags added: kernel-da-key kernel-hyper-v

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

Title:
  3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt
  upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I
  have network connection problems, and have a lot of error message on
  screen like the above ones.

  Sep  3 18:48:07 RailGun kernel: [   71.437967] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.438276] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.438596] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.439016] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.439434] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.439847] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.440155] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.465593] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.466165] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.466827] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.467508] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.468056] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.474507] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.474998] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.475419] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.475833] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.476145] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.483356] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.483823] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.484266] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.484683] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.484993] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.491738] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.492223] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.492645] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.493060] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.493369] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.493689] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.494109] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.494527] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.494941] hv_netvsc vmbus_0_16 eth0: 
unable

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2015-09-03 Thread ubuntu

Bug is still present in Vivid 3.19.0-26-generic.

Is there a workaround that avoids this problem?  There's considerable
pressure to move off of Hyper-V and I'd rather not do it.

[57055.788468] sd 0:0:0:0: [storvsc] Sense Key : Unit Attention [current]
[57055.788561] sd 0:0:0:0: [storvsc] Add. Sense: Changed operating definition
[57055.788704] sd 0:0:0:0: Warning! Received an indication that the operating 
parameters on this target have changed. The Linux SCSI layer does not 
automatically adjust these parameters.
[57055.788719] blk_update_request: I/O error, dev sda, sector 207053224
[57055.788924] Aborting journal on device sda2-8.
[57055.880744] EXT4-fs error (device sda2): ext4_journal_check_start:56: 
Detected aborted journal
[57055.880833] EXT4-fs (sda2): Remounting filesystem read-only
[57055.885165] sd 0:0:0:1: [storvsc] Sense Key : Unit Attention [current]
[57055.885269] sd 0:0:0:1: [storvsc] Add. Sense: Changed operating definition
[57055.885342] sd 0:0:0:1: Warning! Received an indication that the operating 
parameters on this target have changed. The Linux SCSI layer does not 
automatically adjust these parameters.
[57315.373166] sd 0:0:0:2: [storvsc] Sense Key : Unit Attention [current]
[57315.373230] sd 0:0:0:2: [storvsc] Add. Sense: Changed operating definition
[57315.373379] sd 0:0:0:2: Warning! Received an indication that the operating 
parameters on this target have changed. The Linux SCSI layer does not 
automatically adjust these parameters.

Linux db003 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC
2015 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/1470250

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

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

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1471096] Re: CVE-2015-3212

** Description changed:

- [SCTP race condition allows list corruption and panic from userlevel]
+ Race condition in net/sctp/socket.c in the Linux kernel before 4.1.2
+ allows local users to cause a denial of service (list corruption and
+ panic) via a rapid series of system calls related to sockets, as
+ demonstrated by setsockopt calls.
  
  Break-Fix: 9f7d653b67aed2d92540fbb0a8adaf32fcf352ae
  2d45a02d0166caf2627fe91897c6ffc3b19514c4

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

Title:
  CVE-2015-3212

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

[Kernel-packages] [Bug 1477026] Re: CVE-2015-3290

** Description changed:

- High impact NMI bug on x86_64
+ arch/x86/entry/entry_64.S in the Linux kernel before 4.1.6 on the x86_64
+ platform improperly relies on espfix64 during nested NMI processing,
+ which allows local users to gain privileges by triggering an NMI within
+ a certain instruction window.
  
  Break-Fix: - 9b6e6a8334d56354853f9c255d1395c2ba570e0a

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

Title:
  CVE-2015-3290

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source 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-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:

[Kernel-packages] [Bug 1490606] onza (amd64) - tests ran: 197, failed: 1

tests ran: 197, failed: 1;
  
http://kernel.ubuntu.com/testing/onza__3.19.0-28.30__2015-09-03_10-56-00/results-index.html

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

Title:
  linux: 3.19.0-28.30 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC

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

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

[Kernel-packages] [Bug 1492007] Re: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration canno

2015-09-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to
  install/upgrade: package linux-image-extra-3.13.0-46-generic is not
  ready for configuration  cannot configure (current status `half-
  installed')

Status in linux package in Ubuntu:
  New

Bug description:
  The system came apart after I used BleachBit (root) and opted to clean
  the system.

  I had no desktop (xfce4) but managed to get it back ok.

  Tried using Computer Janitor to remove old packages to make room on
  /boot for upgrades.

  Now system is (may be) down on next re-boot.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic i686
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2076 F pulseaudio
  Date: Thu Sep  3 20:24:34 2015
  DuplicateSignature: 
package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package 
linux-image-extra-3.13.0-46-generic is not ready for configuration  cannot 
configure (current status `half-installed')
  ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9
  InstallationDate: Installed on 2015-02-25 (189 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to 
install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2003
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-6738
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr:
  dmi.product.name: KM266-8235
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 1491988] [NEW] 15.10: Multiple Bluetooth controllers not found

2015-09-03 Thread TJ

Public bug reported:

$ hcitool dev
Devices:
hci100:10:7A:4D:15:33
hci000:1F:3A:E0:0A:AF

$ hcitool -i hci1 scan
Scanning ...
00:0A:95:4B:BD:C2   Apple Wireless Keyboard

$ sudo systemctl restart bluetooth

$ journalctl -u bluetooth | grep adapter_service_add 
Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
[bluetooth]# list
Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

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

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

Title:
  15.10: Multiple Bluetooth controllers not found

Status in bluez package in Ubuntu:
  New

Bug description:
  $ hcitool dev
  Devices:
hci100:10:7A:4D:15:33
hci000:1F:3A:E0:0A:AF

  $ hcitool -i hci1 scan
  Scanning ...
00:0A:95:4B:BD:C2   Apple Wireless Keyboard

  $ sudo systemctl restart bluetooth

  $ journalctl -u bluetooth | grep adapter_service_add 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

Attached is a spreadsheet with the above data and some graphs.

The first graph compares normalized data from the ACPI thermal zones
(acpiz), CPU freq and CPU utilization. This shows a good correlation
on CPU utilization and temperature (as we would expect). CPU frequencies
are scaling according to the load and looks OK to me.

The second graph is a comparison of ACPI thermal zones and CPU
utilization in absolute terms (e.g. degrees C and CPU %). Note that
the CPU is loaded never less than 20% and that at this level the
temperature seems to be levelling out to around 70 degrees C which seems
rather high. The CPU is bouncing around 800Mhz - 1.8GHz at that point,
which I guess is to be expected if one has so many context switches and
IRQs occurring.

So. Some interesting data:

1. The IRQ rate does seem high.
2. The Context switch rate seems high too.
3. The machine is not that idle.
4. Even at a low-ish load, the system is rather hot. (This makes me wonder if
there is something physically wrong between the CPU and the heatpipe/fan unit.)
5. Dropping from fully loaded to partially loaded we see heat being dissipated
but not that well, e.g. it drops from nearly 100 C down to 70-65 C, which is
surprising and I expected this to go lower.

Hence I think it may be a physical hardware issue with the cooling.

** Attachment added: "LibreOffice spreadsheet"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+attachment/4456965/+files/powerstat-lenovo-W500-2015.09.03.ods

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

Title:
Shuts down when supposed to suspend as a reaction to self-caused
overheat, session lost

Status in linux package in Ubuntu:
In Progress

Bug description:
Error:
Kernel foolishly shuts down the computer when it overheats.
/var/log/kern.log
W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature
reached (100 C), shutting down

Consequence:
Shutting down destroys session in Ubuntu, Gnome, and all applications that
can't remember their latest conscious state (most applications).

Attempted repair, failed:
Laptop has suspending ability, but I can't find the setting for the kernel to
make the computer suspend instead of shutting down.

Repair suggestions:
1. Persistence of session, so that everything would reappear after the
restart. (this would also make updating less disruptive)
2. Do not heat the machine like crazy; speed up fans or slow down processes.
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
3. Put the computer to suspend when it's too hot.

(The problem has remained the same from at least Ubuntu 11.10 through
14.04)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-62-generic 3.13.0-62.102
ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 2171 F pulseaudio
CurrentDesktop: Unity
Date: Thu Sep 3 13:42:28 2015
HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
InstallationDate: Installed on 2013-12-29 (612 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MachineType: LENOVO 4063B22
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-62-generic N/A
linux-backports-modules-3.13.0-62-generic N/A
linux-firmware 1.127.15
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
dmi.bios.date: 12/14/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET92WW (3.22 )
dmi.board.name: 4063B22
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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4063B22
dmi.product.version: ThinkPad W500
dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1490606] Re: linux: 3.19.0-28.30 -proposed tracker

2015-09-03 Thread Steve Beattie

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: John Johansen (jjohansen) => Steve Beattie (sbeattie)

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

Title:
  linux: 3.19.0-28.30 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2015-09-03 Thread ubuntu

To add to comment #30 I posted, the read-only bug continues to occur on
both Generation 1 and Generation 2 VMs.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

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

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1478819] Re: CVE-2015-3291

** Description changed:

- Malicious user code can cause some fraction of NMIs to be ignored.
+ arch/x86/entry/entry_64.S in the Linux kernel before 4.1.6 on the x86_64
+ platform does not properly determine when nested NMI processing is
+ occurring, which allows local users to cause a denial of service
+ (skipped NMI) by modifying the rsp register, issuing a syscall
+ instruction, and triggering an NMI.
  
  Break-Fix: 3f3c8b8c4b2a34776c3470142a7c8baafcda6eb0
  810bc075f78ff2c221536eb3008eac6a492dba2d

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

Title:
  CVE-2015-3291

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source 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-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in

[Kernel-packages] [Bug 1469488] Re: Suspend crashes ubuntu every now and then

2015-09-03 Thread eezacque

The problem persists...

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

Title:
  Suspend crashes ubuntu every now and then

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Once every 5 or so suspends,  ubuntu crashes immediately: power leds
  are still indicating the hardware is running, monitor falls asleep as
  on successful suspend, cannot ctr-alt-f into terminal, cannot ssh
  into ubuntu, logs show no errors...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-21-generic 3.19.0-21.21
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   izak   1957 F...m pulseaudio
   /dev/snd/pcmC1D0p:   izak   1957 F...m pulseaudio
   /dev/snd/controlC0:  izak   1957 F pulseaudio
   /dev/snd/controlC1:  izak   1957 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jun 28 11:28:11 2015
  HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763
  InstallationDate: Installed on 2014-10-24 (246 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-21-generic N/A
   linux-backports-modules-3.19.0-21-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-04 (54 days ago)
  dmi.bios.date: 09/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2012
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1492007] [NEW] package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration can

2015-09-03 Thread Robert Friendship

Public bug reported:

The system came apart after I used BleachBit (root) and opted to clean
the system.

I had no desktop (xfce4) but managed to get it back ok.

Tried using Computer Janitor to remove old packages to make room on
/boot for upgrades.

Now system is (may be) down on next re-boot.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic i686
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  robert 2076 F pulseaudio
Date: Thu Sep  3 20:24:34 2015
DuplicateSignature: 
package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package 
linux-image-extra-3.13.0-46-generic is not ready for configuration  cannot 
configure (current status `half-installed')
ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9
InstallationDate: Installed on 2015-02-25 (189 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to 
install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2003
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-6738
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr:
dmi.product.name: KM266-8235
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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


** Tags: apport-package dist-upgrade i386 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/1492007

Title:
  package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to
  install/upgrade: package linux-image-extra-3.13.0-46-generic is not
  ready for configuration  cannot configure (current status `half-
  installed')

Status in linux package in Ubuntu:
  New

Bug description:
  The system came apart after I used BleachBit (root) and opted to clean
  the system.

  I had no desktop (xfce4) but managed to get it back ok.

  Tried using Computer Janitor to remove old packages to make room on
  /boot for upgrades.

  Now system is (may be) down on next re-boot.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic i686
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2076 F pulseaudio
  Date: Thu Sep  3 20:24:34 2015
  DuplicateSignature: 
package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package 
linux-image-extra-3.13.0-46-generic is not ready for configuration  cannot 
configure (current status `half-installed')
  ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9
  InstallationDate: Installed on 2015-02-25 (189 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to 
install/upgrade: package linux-image-extra-3.13.0-46-generic is not

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

2015-09-03 Thread Colin Law

b3d6524ff7956c5a898d51a18eaecb62a60a2b84
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031452_amd64.deb

is GOOD

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

Martin,

I'm not wireless expert but, after reading a bit and analysing your
syslog output:


Aug 20 12:57:16 martin04 kernel: [ 9464.423445] Call Trace:
Aug 20 12:57:16 martin04 kernel: [ 9464.423451]  [] 
dump_stack+0x45/0x57
Aug 20 12:57:16 martin04 kernel: [ 9464.423453]  [] 
warn_slowpath_common+0x8a/0xc0
Aug 20 12:57:16 martin04 kernel: [ 9464.423455]  [] 
warn_slowpath_null+0x1a/0x20
Aug 20 12:57:16 martin04 kernel: [ 9464.423462]  [] 
cfg80211_roamed+0x89/0x90 [cfg80211]
Aug 20 12:57:16 martin04 kernel: [ 9464.423489]  [] 
wl_notify_roaming_status+0xcb/0x150 [wl]
Aug 20 12:57:16 martin04 kernel: [ 9464.423508]  [] 
wl_event_handler+0x6a/0x230 [wl]
Aug 20 12:57:16 martin04 kernel: [ 9464.423526]  [] ? 
wl_free_wdev.isra.23+0x80/0x80 [wl]
Aug 20 12:57:16 martin04 kernel: [ 9464.423529]  [] 
kthread+0xd2/0xf0
Aug 20 12:57:16 martin04 kernel: [ 9464.423531]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
Aug 20 12:57:16 martin04 kernel: [ 9464.423533]  [] 
ret_from_fork+0x58/0x90
Aug 20 12:57:16 martin04 kernel: [ 9464.423535]  [] ? 
kthread_create_on_node+0x1c0/0x1c0


This only means that broadcom WL driver tried to warn kernel that it
roamed from one AP to another and new BSS could not be found (meaning
that the card could not get all its new BSS - peers, APs, etc).

*** Try configuring the wireless adapter to use a SPECIFIC AP *** and
check your wifi env for interferences that might be stepping into
broadcom's driver decisions on whether to roam or not -> This does not
mean a fix for WL is not needed, it only means we would have to wait for
Broadcom to come up with a new driver.

Based on good feedback from Igor I'll suggest fixes for all Ubuntu
versions. Even if upstream BW driver still faces problems with adapters,
we still have to fix this bug's original problem.

I'll attach debdiffs for this bug soon.

Alberto,

I saw you pushed precise into latest version (right now in -proposed),
I'll check if it also needs the fix and provide debdiff. Let me know if
you have any other comments since you've been handling all bcmwl work
and you are more into it than I am.

Thank you

Rafael

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

I might renew the cooler paste some day.

Why isn't the fan being run in disengaged mode at 5100 RPM by the kernel
in a thermal emergency? Surely that would be easier to do than to have
every Lenovo W500's cooler pastes renewed?

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1491850] Re: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

2015-09-03 Thread Brian Murray

** Package changed: ubuntu => linux-meta (Ubuntu)

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

Title:
  ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

Status in linux-meta package in Ubuntu:
  New

Bug description:
  == Comment: #0 - YUECHANG E. MEI  - 2015-09-02 12:57:52 ==
  ---Problem Description---
  We tried to install linux-crashdump package (using "apt-get install 
linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we 
have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the 
work around in bug 122925 and the linux-crashdump get install successfully.

  Error we see when we install linux-crashdump:

  root@conelp2:~# apt-get install linux-crashdump
  
  
  Unpacking linux-crashdump (4.1.0.3.3) ...
  Selecting previously unselected package policykit-1.
  Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ...
  Unpacking policykit-1 (0.105-11) ...
  Processing triggers for man-db (2.7.2-1) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (224-2ubuntu2) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20)
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for dbus (1.9.20-1ubuntu2) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  root@conelp2:~# dpkg -l | grep linux-crashdump
  iU  linux-crashdump   4.1.0.3.3   ppc64el 
 Linux kernel crashdump setup for the latest generic kernel

   
  ---uname output---
  Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = n/a 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install Ubuntu 15.10 in a lpar
  2. Login as root, and run "apt-get update".
  3. Install linux-crashdump packages, run "apt-get install linux-crashdump", 
then you will see the error
   

  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com,  Raja  
Sunkari /rajas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem

And because I moved back to previous kernel, I cannot create more logs.
But is you really need the "apport-collect 1491957" then maybe I can
upgrade again to the new kernel, but after I removed it, now I cannot
see it if I try apt upgrade, so in this case please tell me how I can
re-update the kernel after I removed it.

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

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

Title:
  3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt
  upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I
  have network connection problems, and have a lot of error message on
  screen like the above ones.

  Sep  3 18:48:07 RailGun kernel: [   71.437967] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.438276] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.438596] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.439016] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.439434] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.439847] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.440155] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.465593] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.466165] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.466827] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.467508] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.468056] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.474507] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.474998] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.475419] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.475833] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.476145] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.483356] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.483823] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.484266] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.484683] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.484993] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.491738] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.492223] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.492645] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.493060] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.493369] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.493689] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.494109] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 2
  Sep

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

The hardware was disassembled and everything was fine. Fan kept speed well 
after blowing into it.
I drilled extra holes to the case bottom to aid air flow.

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

Installed kernel Linux 4.2.0-040200-generic . 
Ensured it was running.
Problem remains the same: overheating with fan speed staying low (up to 3600 
out of 5000rpm) after several minutes at 90-96C.


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

** Tags added: 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/1491797

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1490606] Re: linux: 3.19.0-28.30 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => John Johansen 
(jjohansen)

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

Title:
  linux: 3.19.0-28.30 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC

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

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

[Kernel-packages] [Bug 1462761] Re: [MacBook8, 1] TouchPad doesn't work

2015-09-03 Thread Oliver Arnold

Hi Guys.

This is quite a serious bug. I have installed 15.10Beta1 and still no
keyboard no mouse ... basically completely useless :( I updated to
kernel 4.2 from the ubuntu kernel team. same behavior.

I saw comments, that is because of USB-c ?

How can I help to debug this? You guys need new logfiles?

Tanks derarnold

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

Title:
  [MacBook8,1] TouchPad doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad doesn't work.

  ---
  ApportVersion: 2.17.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1889 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1889 F pulseaudio
  CasperVersion: 1.360
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150603)
  MachineType: Apple Inc. MacBook8,1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-20-generic N/A
   linux-backports-modules-3.19.0-20-generic  N/A
   linux-firmware 1.144
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB81.88Z.0164.B02.1503241252
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-BE0E8AC46FE800CC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBook8,1
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-BE0E8AC46FE800CC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB81.88Z.0164.B02.1503241252:bd03/24/2015:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-BE0E8AC46FE800CC:
  dmi.product.name: MacBook8,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/1462761/+subscriptions

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

[Kernel-packages] [Bug 1490785] Re: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => John Johansen 
(jjohansen)

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

Title:
  linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 01. September 2015 01:02 UTC
  kernel-stable-master-bug:1490606
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

running
"powerstat -Da 1 60"
returns
"Device does not have any RAPL domains, cannot power measure power usage."

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running

This bug was fixed in the package linux-mako - 3.4.0-6.37~15.04.1

---
linux-mako (3.4.0-6.37~15.04.1) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584

 -- Tim Gardner   Mon, 13 Jul 2015 14:53:48
-0700

** Changed in: linux-goldfish (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  AUDIT_USER_AVC messages are not printk'ed when auditd is not running

Status in linux-flo package in Ubuntu:
  Fix Released
Status in linux-goldfish package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Fix Released
Status in linux-manta package in Ubuntu:
  Fix Released
Status in linux-flo source package in Vivid:
  Fix Released
Status in linux-goldfish source package in Vivid:
  Fix Released
Status in linux-mako source package in Vivid:
  Fix Released
Status in linux-manta source package in Vivid:
  Fix Released

Bug description:
  The auditd daemon is not part of the default phone images. At the
  kernel level, the audit_enabled variable remains 0 until an auditd
  daemon registers itself. There is a bug in old kernels that causes
  AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
  the bug several years ago and marked the patch for the stable tree but
  the phone kernels (mako, at least) did not pull in the patch. The
  upstream commit id is:

    0868a5e150bc4c47e7a003367cd755811eb41e0b

  What this means for our phone images is that any denial messages from
  the system D-Bus daemon are dropped instead of being properly routed
  to the syslog. This results in headaches for debugging app confinement
  denials.

  == Verification Steps ==

  # Load an AppArmor profile for testing
  $ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq

  # Verify that we can talk to the system bus
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
  method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
     array [
    string "org.freedesktop.DBus"
     ...

  # Clear the dmesg buffer
  $ sudo dmesg -C

  # Attempt to talk to the system bus under confinement
  $ aa-exec -p test -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" 
member="Hello" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.DBus" (bus)

  # We should now see an AppArmor denial in the dmesg output.
  # Successful fix verification *must* show the denial from the D-Bus daemon.
  $ sudo dmesg | grep DENIED
  [  187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="Hello" mask="send" 
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"

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

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

[Kernel-packages] [Bug 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running

This bug was fixed in the package linux-goldfish - 3.4.0-4.24~15.04.1

---
linux-goldfish (3.4.0-4.24~15.04.1) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584

 -- Tim Gardner   Mon, 13 Jul 2015 14:57:44
-0700

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

Title:
  AUDIT_USER_AVC messages are not printk'ed when auditd is not running

Status in linux-flo package in Ubuntu:
  Fix Released
Status in linux-goldfish package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Fix Released
Status in linux-manta package in Ubuntu:
  Fix Released
Status in linux-flo source package in Vivid:
  Fix Released
Status in linux-goldfish source package in Vivid:
  Fix Released
Status in linux-mako source package in Vivid:
  Fix Released
Status in linux-manta source package in Vivid:
  Fix Released

Bug description:
  The auditd daemon is not part of the default phone images. At the
  kernel level, the audit_enabled variable remains 0 until an auditd
  daemon registers itself. There is a bug in old kernels that causes
  AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
  the bug several years ago and marked the patch for the stable tree but
  the phone kernels (mako, at least) did not pull in the patch. The
  upstream commit id is:

    0868a5e150bc4c47e7a003367cd755811eb41e0b

  What this means for our phone images is that any denial messages from
  the system D-Bus daemon are dropped instead of being properly routed
  to the syslog. This results in headaches for debugging app confinement
  denials.

  == Verification Steps ==

  # Load an AppArmor profile for testing
  $ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq

  # Verify that we can talk to the system bus
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
  method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
     array [
    string "org.freedesktop.DBus"
     ...

  # Clear the dmesg buffer
  $ sudo dmesg -C

  # Attempt to talk to the system bus under confinement
  $ aa-exec -p test -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" 
member="Hello" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.DBus" (bus)

  # We should now see an AppArmor denial in the dmesg output.
  # Successful fix verification *must* show the denial from the D-Bus daemon.
  $ sudo dmesg | grep DENIED
  [  187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="Hello" mask="send" 
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

If thermald is supposed to throttle CPU according to temperature, it
doesn't work.

Whatever is throttling the CPU seems to be unaware of temperature,
because the more I load the machine, the more reliably "cpufreq-info -w"
returns "2801000" while temperature is at 90-95 C.

Only when there is less load, does the CPU run at lower frequencies.

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1491850] [NEW] ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

You have been subscribed to a public bug:

== Comment: #0 - YUECHANG E. MEI  - 2015-09-02 12:57:52 ==
---Problem Description---
We tried to install linux-crashdump package (using "apt-get install 
linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we 
have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the 
work around in bug 122925 and the linux-crashdump get install successfully.

Error we see when we install linux-crashdump:

root@conelp2:~# apt-get install linux-crashdump


Unpacking linux-crashdump (4.1.0.3.3) ...
Selecting previously unselected package policykit-1.
Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ...
Unpacking policykit-1 (0.105-11) ...
Processing triggers for man-db (2.7.2-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (224-2ubuntu2) ...
Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20)
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for dbus (1.9.20-1ubuntu2) ...
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@conelp2:~# dpkg -l | grep linux-crashdump
iU  linux-crashdump   4.1.0.3.3   ppc64el   
   Linux kernel crashdump setup for the latest generic kernel

 
---uname output---
Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = n/a 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. Install Ubuntu 15.10 in a lpar
2. Login as root, and run "apt-get update".
3. Install linux-crashdump packages, run "apt-get install linux-crashdump", 
then you will see the error
 

Stack trace output:
 no
 
Oops output:
 no
 
System Dump Info:
  The system is not configured to capture a system dump.
 
*Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com,  Raja  
Sunkari /rajas...@in.ibm.com: 
-Attach sysctl -a output output to the bug.

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


** Tags: architecture-ppc64le bot-comment bugnameltc-129812 severity-high 
targetmilestone-inin---
-- 
ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages
https://bugs.launchpad.net/bugs/1491850
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-meta in Ubuntu.

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

[Kernel-packages] [Bug 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running

This bug was fixed in the package linux-flo - 3.4.0-4.18~15.04.1

---
linux-flo (3.4.0-4.18~15.04.1) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584

 -- Tim Gardner   Mon, 13 Jul 2015 14:39:54
-0700

** Changed in: linux-flo (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: linux-manta (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  AUDIT_USER_AVC messages are not printk'ed when auditd is not running

Status in linux-flo package in Ubuntu:
  Fix Released
Status in linux-goldfish package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Fix Released
Status in linux-manta package in Ubuntu:
  Fix Released
Status in linux-flo source package in Vivid:
  Fix Released
Status in linux-goldfish source package in Vivid:
  Fix Released
Status in linux-mako source package in Vivid:
  Fix Released
Status in linux-manta source package in Vivid:
  Fix Released

Bug description:
  The auditd daemon is not part of the default phone images. At the
  kernel level, the audit_enabled variable remains 0 until an auditd
  daemon registers itself. There is a bug in old kernels that causes
  AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
  the bug several years ago and marked the patch for the stable tree but
  the phone kernels (mako, at least) did not pull in the patch. The
  upstream commit id is:

    0868a5e150bc4c47e7a003367cd755811eb41e0b

  What this means for our phone images is that any denial messages from
  the system D-Bus daemon are dropped instead of being properly routed
  to the syslog. This results in headaches for debugging app confinement
  denials.

  == Verification Steps ==

  # Load an AppArmor profile for testing
  $ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq

  # Verify that we can talk to the system bus
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
  method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
     array [
    string "org.freedesktop.DBus"
     ...

  # Clear the dmesg buffer
  $ sudo dmesg -C

  # Attempt to talk to the system bus under confinement
  $ aa-exec -p test -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" 
member="Hello" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.DBus" (bus)

  # We should now see an AppArmor denial in the dmesg output.
  # Successful fix verification *must* show the denial from the D-Bus daemon.
  $ sudo dmesg | grep DENIED
  [  187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="Hello" mask="send" 
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"

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

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

[Kernel-packages] [Bug 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running

This bug was fixed in the package linux-manta - 3.4.0-7.32~15.04.1

---
linux-manta (3.4.0-7.32~15.04.1) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584

 -- Tim Gardner   Mon, 13 Jul 2015 14:49:51
-0700

** Changed in: linux-mako (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  AUDIT_USER_AVC messages are not printk'ed when auditd is not running

Status in linux-flo package in Ubuntu:
  Fix Released
Status in linux-goldfish package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Fix Released
Status in linux-manta package in Ubuntu:
  Fix Released
Status in linux-flo source package in Vivid:
  Fix Released
Status in linux-goldfish source package in Vivid:
  Fix Released
Status in linux-mako source package in Vivid:
  Fix Released
Status in linux-manta source package in Vivid:
  Fix Released

Bug description:
  The auditd daemon is not part of the default phone images. At the
  kernel level, the audit_enabled variable remains 0 until an auditd
  daemon registers itself. There is a bug in old kernels that causes
  AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
  the bug several years ago and marked the patch for the stable tree but
  the phone kernels (mako, at least) did not pull in the patch. The
  upstream commit id is:

    0868a5e150bc4c47e7a003367cd755811eb41e0b

  What this means for our phone images is that any denial messages from
  the system D-Bus daemon are dropped instead of being properly routed
  to the syslog. This results in headaches for debugging app confinement
  denials.

  == Verification Steps ==

  # Load an AppArmor profile for testing
  $ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq

  # Verify that we can talk to the system bus
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
  method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
     array [
    string "org.freedesktop.DBus"
     ...

  # Clear the dmesg buffer
  $ sudo dmesg -C

  # Attempt to talk to the system bus under confinement
  $ aa-exec -p test -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" 
member="Hello" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.DBus" (bus)

  # We should now see an AppArmor denial in the dmesg output.
  # Successful fix verification *must* show the denial from the D-Bus daemon.
  $ sudo dmesg | grep DENIED
  [  187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="Hello" mask="send" 
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

Attachment from "powerstat -za 1 480".

** Attachment added: "Intermittent full load over 30% base load"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+attachment/4456951/+files/powerstat-lenovo-W500-2015.09.03.txt

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Due to the nature of the issue I am unable to run "apport-collect
1491957", because I changed back the kernel to the previos one.

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

Title:
  3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt
  upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I
  have network connection problems, and have a lot of error message on
  screen like the above ones.

  Sep  3 18:48:07 RailGun kernel: [   71.437967] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.438276] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.438596] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.439016] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.439434] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.439847] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.440155] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.465593] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.466165] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.466827] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.467508] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.468056] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.474507] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.474998] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.475419] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.475833] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.476145] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.483356] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.483823] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.484266] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.484683] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.484993] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.491738] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.492223] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.492645] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.493060] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.493369] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.493689] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.494109] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.494527] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.494941] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid

[Kernel-packages] [Bug 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Joseph, yes, I moved back to the prior kernel.
And now it works again.

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

Title:
  3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt
  upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I
  have network connection problems, and have a lot of error message on
  screen like the above ones.

  Sep  3 18:48:07 RailGun kernel: [   71.437967] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.438276] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.438596] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.439016] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.439434] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.439847] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.440155] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.465593] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.466165] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.466827] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.467508] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.468056] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.474507] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.474998] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.475419] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.475833] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.476145] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.483356] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.483823] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.484266] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.484683] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.484993] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.491738] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.492223] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.492645] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.493060] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.493369] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.493689] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.494109] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.494527] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.494941] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.495249]

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

I'd like to get a profile of your machine's CPU clock speed, CPU
utilization and thermal zone temperatures.  Can you install the  latest
powerstat and run a profile for me.  To do so, use:

sudo add-apt-repository ppa:colin-king/white
sudo apt-get update
sudo apt-get install powerstat

then run:

powerstat -Da 1 60

and attach the output to the bug report. Thanks!

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

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

2015-09-03 Thread bugproxy

--- Comment From cha...@us.ibm.com 2015-09-03 16:44 EDT---
*** Bug 129843 has been marked as a duplicate of this bug. ***

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

Title:
  Ubuntu 14.04.3 LTS Crash in notifier_call_chain after boot

Status in linux package in Ubuntu:
  New
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Users of 3.19 kernel with power8 machines get a kernel crash on boot.

  [Test Case]
  Boot system.

  [Fix]
  commit 792f96e9a769b799a2944e9369e4ea1e467135b2 needed to be backported in 
addition to d7cf83fcaf1b1668201eae4cdd6e6fe7a2448654. Our 3.19 kernel had a 
partial backport of the first patch.

  --

  
  ---Problem Description---
  Installed Ubuntu 14.04.3 LTS on Palmetto and its crashing after booting to 
login.
  This happens every time I boot Ubuntu 14.04.3 LTS.  I've reinstalled Ubuntu 
and replaced the hard disk as well and re-installed.  Still crashing.

  ---uname output---
  Linux paul40 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:10:52 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Palmetto

  ---System Hang---
   Ubuntu OS crashes and cannot access host. Must reboot system

  ---Steps to Reproduce---
   Boot system

  Oops output:
   [   33.132376] Unable to handle kernel paging request for data at address 
0x200
  [   33.132565] Faulting instruction address: 0xc00dbc60
  [   33.133422] Oops: Kernel access of bad area, sig: 11 [#1]
  [   33.134410] SMP NR_CPUS=2048 NUMA PowerNV
  [   33.134478] Modules linked in: ast ttm drm_kms_helper joydev mac_hid 
drm hid_generic usbhid hid syscopyarea sysfillrect sysimgblt i2c_algo_bit 
ofpart cmdlinepart at24 uio_pdrv_genirq powernv_flash mtd ipmi_powernv 
powernv_rng opal_prd ipmi_msghandler uio uas usb_storage ahci libahci
  [   33.139112] CPU: 24 PID: 0 Comm: swapper/24 Not tainted 
3.19.0-26-generic #28~14.04.1-Ubuntu
  [   33.139943] task: c13cccb0 ti: c00fff70 task.ti: 
c1448000
  [   33.141642] NIP: c00dbc60 LR: c00dbd94 CTR: 

  [   33.142605] REGS: c00fff703980 TRAP: 0300   Not tainted  
(3.19.0-26-generic)
  [   33.143417] MSR: 90009033   CR: 
28002888  XER: 
  [   33.144244] CFAR: c0008468 DAR: 0200 DSISR: 
4000 SOFTE: 0
  GPR00: c00dbd94 c00fff703c00 c144cc00 c15f03c0
  GPR04: 0007 c15f03b8  
  GPR08:  0200 c006c394 90001003
  GPR12: 2200 cfb8d800 0058 
  GPR16: c1448000 c1448000 c1448080 c0e9a880
  GPR20: c1448080 0001 0002 0012
  GPR24: c00f1e432200   c15f03b8
  GPR28: 0007  c15f03c0 
  [   33.157013] NIP [c00dbc60] notifier_call_chain+0x70/0x100
  [   33.157818] LR [c00dbd94] atomic_notifier_call_chain+0x44/0x60
  [   33.162090] Call Trace:
  [   33.162845] [c00fff703c00] [0008] 0x8 (unreliable)
  [   33.163644] [c00fff703c50] [c00dbd94] 
atomic_notifier_call_chain+0x44/0x60
  [   33.164647] [c00fff703c90] [c006f2a8] 
opal_message_notify+0xa8/0x100
  [   33.165476] [c00fff703d00] [c00dbc88] 
notifier_call_chain+0x98/0x100
  [   33.167007] [c00fff703d50] [c00dbd94] 
atomic_notifier_call_chain+0x44/0x60
  [   33.167816] [c00fff703d90] [c006f654] 
opal_do_notifier.part.5+0x74/0xa0
  [   33.172166] [c00fff703dd0] [c006f6d8] 
opal_interrupt+0x58/0x70
  [   33.172997] [c00fff703e10] [c01273d0] 
handle_irq_event_percpu+0x90/0x2b0
  [   33.174507] [c00fff703ed0] [c0127658] 
handle_irq_event+0x68/0xd0
  [   33.175312] [c00fff703f00] [c012baf4] 
handle_fasteoi_irq+0xe4/0x240
  [   33.176124] [c00fff703f30] [c01265c8] 
generic_handle_irq+0x58/0x90
  [   33.176936] [c00fff703f60] [c0010f10] __do_irq+0x80/0x190
  [   33.182406] [c00fff703f90] [c002476c] call_do_irq+0x14/0x24
  [   33.183258] [c144ba30] [c00110c0] do_IRQ+0xa0/0x120
  [   33.184072] [c144ba90] [c00025d8] 
hardware_interrupt_common+0x158/0x180
  [   33.184907] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [   33.184907] LR = arch_local_irq_restore+0x40/0x90
  [   33.186473] [c144bd80] [c00f2ae19808] 0xc00f2ae19808 
(unreliable)
  [   33.188024] [c144bda0] [c085d5d8]

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

2015-09-03 Thread Roland Weber

** Attachment added: "last good kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456919/+files/dmesg.good.full.txt

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  reproducible: always

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

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

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

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

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

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

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

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

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

2015-09-03 Thread Roland Weber

Valentine, your problem is almost certainly not related to the one I reported
here.
You should seek advice in forums or on mailing lists for your computer and/or
distribution.

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

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

Status in linux package in Ubuntu:
Triaged

Bug description:
reproducible: always

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1491957] [NEW] 3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Public bug reported:

I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt
upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have
network connection problems, and have a lot of error message on screen
like the above ones.

Sep  3 18:48:07 RailGun kernel: [   71.437967] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...retrying 4
Sep  3 18:48:07 RailGun kernel: [   71.438276] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...give up retrying
Sep  3 18:48:07 RailGun kernel: [   71.438596] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 1
Sep  3 18:48:07 RailGun kernel: [   71.439016] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 2
Sep  3 18:48:07 RailGun kernel: [   71.439434] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 3
Sep  3 18:48:07 RailGun kernel: [   71.439847] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 4
Sep  3 18:48:07 RailGun kernel: [   71.440155] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...give up retrying
Sep  3 18:48:07 RailGun kernel: [   71.465593] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 1
Sep  3 18:48:07 RailGun kernel: [   71.466165] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 2
Sep  3 18:48:07 RailGun kernel: [   71.466827] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 3
Sep  3 18:48:07 RailGun kernel: [   71.467508] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 4
Sep  3 18:48:07 RailGun kernel: [   71.468056] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...give up retrying
Sep  3 18:48:07 RailGun kernel: [   71.474507] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 1
Sep  3 18:48:07 RailGun kernel: [   71.474998] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 2
Sep  3 18:48:07 RailGun kernel: [   71.475419] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 3
Sep  3 18:48:07 RailGun kernel: [   71.475833] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 4
Sep  3 18:48:07 RailGun kernel: [   71.476145] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...give up retrying
Sep  3 18:48:07 RailGun kernel: [   71.483356] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 1
Sep  3 18:48:07 RailGun kernel: [   71.483823] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 2
Sep  3 18:48:07 RailGun kernel: [   71.484266] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 3
Sep  3 18:48:07 RailGun kernel: [   71.484683] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 4
Sep  3 18:48:07 RailGun kernel: [   71.484993] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...give up retrying
Sep  3 18:48:07 RailGun kernel: [   71.491738] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 1
Sep  3 18:48:07 RailGun kernel: [   71.492223] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 2
Sep  3 18:48:07 RailGun kernel: [   71.492645] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 3
Sep  3 18:48:07 RailGun kernel: [   71.493060] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 4
Sep  3 18:48:07 RailGun kernel: [   71.493369] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...give up retrying
Sep  3 18:48:07 RailGun kernel: [   71.493689] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 1
Sep  3 18:48:07 RailGun kernel: [   71.494109] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 2
Sep  3 18:48:07 RailGun kernel: [   71.494527] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 3
Sep  3 18:48:07 RailGun kernel: [   71.494941] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 4
Sep  3 18:48:07 RailGun kernel: [   71.495249] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...give up retrying
Sep  3 18:48:07 RailGun kernel: [   71.509010] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206f)...retrying 1
Sep  3 18:48:07 RailGun kernel: [   71.509467] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206f)...retrying 2
Sep  3 18:48:07 RailGun kernel: [

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

We can examine the thermald issues later, lets get some idea of what
powerstat says and then I can ponder on the next best step to make.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 874694] Re: [i845] Resolution cannot be set higher than 640x480 and doesn't fit screen

2015-09-03 Thread BJB

I have update the Amilo config to 15.04. The bug is still there.

Settting i915.modeset=0 does not bring improvement anymore : instead of
640x480 max resolution stuck at top left of the screen you now get the
640x480 max reslution in the middle of the screen.

Any fix on this is highly welcomed to be able to run Ubuntu on those
machine.

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

Title:
  [i845] Resolution cannot be set higher than 640x480 and doesn't fit
  screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Lubuntu 11.10 I cannot set the resolution higher than 640x480.  The
  screen clearly doesn't like this and doesn't fit the desktop.  See
  attached photo
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/874694/+attachment/2545700/+files/2011-10-15%2000.59.24.jpg
  .

  WORKAROUND: Use kernel parameter:
  i915.modeset=0

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Sat Oct 15 00:43:38 2011
  InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

apport-collect 1491957

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

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

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

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

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

Title:
  3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt
  upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I
  have network connection problems, and have a lot of error message on
  screen like the above ones.

  Sep  3 18:48:07 RailGun kernel: [   71.437967] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.438276] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.438596] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.439016] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.439434] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.439847] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.440155] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.465593] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.466165] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.466827] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.467508] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.468056] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.474507] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.474998] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.475419] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.475833] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.476145] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.483356] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.483823] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.484266] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.484683] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.484993] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.491738] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.492223] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.492645] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.493060] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.493369] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.493689] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206e)...retrying 1
  Sep  3 18:48:07

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1491850] Re: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - YUECHANG E. MEI  - 2015-09-02 12:57:52 ==
  ---Problem Description---
  We tried to install linux-crashdump package (using "apt-get install 
linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we 
have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the 
work around in bug 122925 and the linux-crashdump get install successfully.

  Error we see when we install linux-crashdump:

  root@conelp2:~# apt-get install linux-crashdump
  
  
  Unpacking linux-crashdump (4.1.0.3.3) ...
  Selecting previously unselected package policykit-1.
  Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ...
  Unpacking policykit-1 (0.105-11) ...
  Processing triggers for man-db (2.7.2-1) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (224-2ubuntu2) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20)
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for dbus (1.9.20-1ubuntu2) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  root@conelp2:~# dpkg -l | grep linux-crashdump
  iU  linux-crashdump   4.1.0.3.3   ppc64el 
 Linux kernel crashdump setup for the latest generic kernel

   
  ---uname output---
  Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = n/a 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install Ubuntu 15.10 in a lpar
  2. Login as root, and run "apt-get update".
  3. Install linux-crashdump packages, run "apt-get install linux-crashdump", 
then you will see the error
   

  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com,  Raja  
Sunkari /rajas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1491850] Re: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

2015-09-03 Thread bugproxy

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1510

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

Title:
  ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - YUECHANG E. MEI  - 2015-09-02 12:57:52 ==
  ---Problem Description---
  We tried to install linux-crashdump package (using "apt-get install 
linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we 
have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the 
work around in bug 122925 and the linux-crashdump get install successfully.

  Error we see when we install linux-crashdump:

  root@conelp2:~# apt-get install linux-crashdump
  
  
  Unpacking linux-crashdump (4.1.0.3.3) ...
  Selecting previously unselected package policykit-1.
  Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ...
  Unpacking policykit-1 (0.105-11) ...
  Processing triggers for man-db (2.7.2-1) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (224-2ubuntu2) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20)
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for dbus (1.9.20-1ubuntu2) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  root@conelp2:~# dpkg -l | grep linux-crashdump
  iU  linux-crashdump   4.1.0.3.3   ppc64el 
 Linux kernel crashdump setup for the latest generic kernel

   
  ---uname output---
  Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = n/a 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install Ubuntu 15.10 in a lpar
  2. Login as root, and run "apt-get update".
  3. Install linux-crashdump packages, run "apt-get install linux-crashdump", 
then you will see the error
   

  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com,  Raja  
Sunkari /rajas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

This model of thinkpad has 8 levels of fan control: 
  0=off, 
  1-2 = 1900 RPM
  3-5 = ~3000 RPM, 
  6-7 = ~3500 RPM
and a disengaged mode works at ~5100 RPM

The 6-7 level @ 3500 RPM should be enough to dissipate heat generated by
a loaded CPU.  The fact that your fan is running at 3500 RPM is
indicating that the fan control is correctly enabling the highest fan
control level (6-7) and even that is not enough to dump all the heat out
of the laptop.  Also,  thermald should be actively throttling back the
CPU as a passive mode control, so this should also help reduce the
overheating.   The fact that this seems to be occurring across a wide
range of kernel versions suggests to me that that perhaps this is
hardware related, for example, is the thermal paste between the CPU and
the thermal pipe/fan unit working correctly?

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1394368] Re: Bluetooth with AR9462 doesn't work (New ID /Firmware)

2015-09-03 Thread Jukka Niiranen

I've been following this bug as I'm also affected. I've AR9462 in Acer
Aspire V3-371-79RJ and Ubuntu 15.04 (3.19.0-26-generic).

I made a clean install about a month ago and have now all updates
installed. Still dmesg says: "Bluetooth: Patch file not found
ar3k/AthrBT_0x11020100.dfu" and bluetooth is not working.

Could someone please recap the above discussion and point out what steps
a general user needs to take to make Bluetooth work?

Thanks for fixing this for us!

-- 
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 package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Fix Released
Status in linux-firmware source package in Vivid:
  Confirmed

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

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

2015-09-03 Thread Roland Weber

As suggested on the linux.usb mailing list, I've added some additional debug 
print statements to the first bad kernel. They are not triggered by "lsusb -v" 
though. I'm attaching kernel debug output from the boot sequence of two kernels:
- the bad one, with additional print statements
- the last good one, without additional print statements
The difference in the startup behavior is remarkable.

** Attachment added: "first bad kernel, extra output "entry" and "exit""
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456918/+files/dmesg.bad.full.txt

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  reproducible: always

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost

OK, no RAPL interface, so can you run "powerstat -za 1 480" instead.

The default mode for the fan is to be controlled by the firmware and not
the kernel, so the kernel has no direct control by default.   The
alternative mechanism is to enable the thinkpad_acpi fan control and
twiddle the settings either manually or by software control.   By
default though, one would expect the firmware do be able to control the
fan correctly since that what the system designers intended to be the
default fan control mode.

If you do intend to try twiddling the fan controls manually, I believe
the following instructions may work (but I've not tried these myself, so
I can't vouch that they are correct):

as root, create a new file /etc/modprobe.d/thinkpad_acpi.conf and add
the following line to it:

options thinkpad_acpi fan_control=1

..and reboot.

as root try the following to set the fan to the highest "engaged" fan
speed:

echo level 7 > /proc/acpi/ibm/fan

..hopefully that will crank the fan up to ~5100 RPM in engaged mode.

you can enabled disengaged mode using:

echo level disengaged > /proc/acpi/ibm/fan

Essentially, "engaged" mode is where the fan speed is locked to a
defined fan speed.  "disengaged" mode can be used to drive the fan
faster (I believe there is no feedback loop between the speed and a
firmware control that sets the speed in disengaged mode).   For more
details, see http://www.thinkwiki.org/wiki/How_to_control_fan_speed

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

Title:
  Shuts down when supposed to suspend as a reaction to self-caused
  overheat, session lost

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error:
  Kernel foolishly shuts down the computer when it overheats.
  /var/log/kern.log
  W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature 
reached (100 C), shutting down

  Consequence:
  Shutting down destroys session in Ubuntu, Gnome, and all applications that 
can't remember their latest conscious state (most applications).

  Attempted repair, failed:
  Laptop has suspending ability, but I can't find the setting for the kernel to 
make the computer suspend instead of shutting down.

  Repair suggestions:
  1. Persistence of session, so that everything would reappear after the 
restart. (this would also make updating less disruptive)
  2. Do not heat the machine like crazy; speed up fans or slow down processes. 
(problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end)
  3. Put the computer to suspend when it's too hot.

  (The problem has remained the same from at least Ubuntu 11.10 through
  14.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep  3 13:42:28 2015
  HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256
  InstallationDate: Installed on 2013-12-29 (612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4063B22
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 4063B22
  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:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063B22
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1454758] Re: [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed

The cherry-pick of commit dc45708c into Precise also required 8b612fa as
a prereq.  I built a test kernel with these two commits.  The test
kernel can be downloaded from:

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

Can folks affected by this bug test this kernel?  If it resolves this
bug, I will SRU these commits to Precise.

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

Title:
  [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer
  is needed

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  The following critical bugfix has been accepted into the upstream
  kernel. It is needed for 15.10, 15.02, 14.10, 14.04 and 14.04 HWE
  (and, by extension, 12.04 and 12.04 HWE). We have seen IHV drivers in
  the field throw errors and time out due to receiving SRB flags set
  when no data transfer is expected.

  storvsc: Set the SRB flags correctly when no data transfer is needed
  Set the SRB flags correctly when there is no data transfer.  Without this
  change some IHV drivers will fail valid commands such as TEST_UNIT_READY.

  Commit
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=dc45708ca9988656d706940df5fd102672c5de92

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

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

[Kernel-packages] [Bug 1457807] Re: CVE-2015-4036

** Description changed:

- [drivers/vhost/scsi.c: potential memory corruption]
+ Array index error in the tcm_vhost_make_tpg function in
+ drivers/vhost/scsi.c in the Linux kernel before 4.0 might allow guest OS
+ users to cause a denial of service (memory corruption) or possibly have
+ unspecified other impact via a crafted VHOST_SCSI_SET_ENDPOINT ioctl
+ call. NOTE: the affected function was renamed to vhost_scsi_make_tpg
+ before the vulnerability was announced.
  
  Break-Fix: 057cbf49a1f08297877e46c82f707b1bfea806a8
  59c816c1f24df0204e01851431d3bab3eb76719c

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

Title:
  CVE-2015-4036

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

[Kernel-packages] [Bug 1490785] Re: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker

2015-09-03 Thread Steve Beattie

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: John Johansen (jjohansen) => Steve Beattie (sbeattie)

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

Title:
  linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 01. September 2015 01:02 UTC
  kernel-stable-master-bug:1490606
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC

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

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

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

2015-09-03 Thread Colin Law

8cc748aa76c921d8834ef00f762f31acd2c93aa8
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031637_amd64.deb

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1469320] Re: CVE-2015-4700

** Description changed:

- Crafted BPF filters may crash kernel during JIT optimisation
+ The bpf_int_jit_compile function in arch/x86/net/bpf_jit_comp.c in the
+ Linux kernel before 4.0.6 allows local users to cause a denial of
+ service (system crash) by creating a packet filter and then loading
+ crafted BPF instructions that trigger late convergence by the JIT
+ compiler.
  
  Break-Fix: 0a14842f5a3c0e88a1e59fac5c3025db39721f74
  3f7352bf21f8fd7ba3e2fcef9488756f188e12be

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

Title:
  CVE-2015-4700

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

[Kernel-packages] [Bug 1472165] Re: CVE-2015-5366

** Description changed:

- [Linux UDP checksum DoS EGAIN part]
+ The (1) udp_recvmsg and (2) udpv6_recvmsg functions in the Linux kernel
+ before 4.0.6 provide inappropriate -EAGAIN return values, which allows
+ remote attackers to cause a denial of service (EPOLLET epoll application
+ read outage) via an incorrect checksum in a UDP packet, a different
+ vulnerability than CVE-2015-5364.
  
  Break-Fix: - beb39db59d14990e401e235faf66a6b9b31240b0

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

Title:
  CVE-2015-5366

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

[Kernel-packages] [Bug 1472160] Re: CVE-2015-5364

** Description changed:

- [Linux UDP checksum DoS]
+ The (1) udp_recvmsg and (2) udpv6_recvmsg functions in the Linux kernel
+ before 4.0.6 do not properly consider yielding a processor, which allows
+ remote attackers to cause a denial of service (system hang) via
+ incorrect checksums within a UDP packet flood.
  
  Break-Fix: - beb39db59d14990e401e235faf66a6b9b31240b0

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

Title:
  CVE-2015-5364

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

[Kernel-packages] [Bug 1484797] Re: CVE-2015-5706

** Description changed:

- [Use-after-free in path lookup]
+ Use-after-free vulnerability in the path_openat function in fs/namei.c
+ in the Linux kernel 3.x and 4.x before 4.0.4 allows local users to cause
+ a denial of service or possibly have unspecified other impact via
+ O_TMPFILE filesystem operations that leverage a duplicate cleanup
+ operation.
  
  Break-Fix: 60545d0d4610b02e55f65d141c95b18ccf855b6e
  f15133df088ecadd141ea1907f2c96df67c729f0

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

Title:
  CVE-2015-5706

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish 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-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta 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
Status in linux source package in Wily:
  Invalid
Status in

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

** Patch added: "vivid-bcmwl_6.30.223.248+bdcom-0ubuntu2.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4457001/+files/vivid-bcmwl_6.30.223.248%2Bbdcom-0ubuntu2.1.debdiff

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

** Patch added: "trusty_bcmwl_6.30.223.248+bdcom-0ubuntu0.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4457000/+files/trusty_bcmwl_6.30.223.248%2Bbdcom-0ubuntu0.2.debdiff

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

** Patch added: "precise-updates_bcmwl_6.30.223.248+bdcom-0ubuntu0.0.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4456999/+files/precise-updates_bcmwl_6.30.223.248%2Bbdcom-0ubuntu0.0.3.debdiff

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

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

This change was made by a bot.

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

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

Title:
  package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to
  install/upgrade: package linux-image-extra-3.13.0-46-generic is not
  ready for configuration  cannot configure (current status `half-
  installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system came apart after I used BleachBit (root) and opted to clean
  the system.

  I had no desktop (xfce4) but managed to get it back ok.

  Tried using Computer Janitor to remove old packages to make room on
  /boot for upgrades.

  Now system is (may be) down on next re-boot.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic i686
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2076 F pulseaudio
  Date: Thu Sep  3 20:24:34 2015
  DuplicateSignature: 
package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package 
linux-image-extra-3.13.0-46-generic is not ready for configuration  cannot 
configure (current status `half-installed')
  ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9
  InstallationDate: Installed on 2015-02-25 (189 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to 
install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2003
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-6738
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr:
  dmi.product.name: KM266-8235
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

I've subscribed Ubuntu Sponsors team seeking for sponsorship on Precise
(Updates), Trusty, Vivid and Wily fixes (attached to this case). Let me
know if I can assist with anything else.

Best Regards

Rafael Tinoco

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

** Patch added: "wily_bcmwl_6.30.223.248+bdcom-0ubuntu4.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4457002/+files/wily_bcmwl_6.30.223.248%2Bbdcom-0ubuntu4.1.debdiff

** Description changed:

+ [Impact]
+ 
+  * bcmwl does not compile on new kernels (or HWE kernels)
+  * bcmwl suffers from null reference bug 
+ 
+ [Test Case]
+ 
+  * public PPA provided to community and feedback
+  * based on patch available to other distros
+  * comment #42
+ 
+ [Regression Potential]
+ 
+  * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
+  * for the null reference change -> proved to fix problem for community based 
on feedback
+ 
+ [Other Info]
+ 
+ Original bug description:
+ 
  The bcmwl package as of now misses one patch for a bug that occurs with
  BCM43142 and possibly other broadcom chipsets that will look like random
  disconnects, poor wifi signal and kernel warnings, See also #1379524.
  
  Adding the patch is a fairly simple process:
  
  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)
  
  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was linked
  from the respective AUR package.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

[Kernel-packages] [Bug 1489318] Re: CVE-2015-6526

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

** Description changed:

- Description needed
+ The perf_callchain_user_64 function in arch/powerpc/perf/callchain.c in
+ the Linux kernel before 4.0.2 on ppc64 platforms allows local users to
+ cause a denial of service (infinite loop) via a deep 64-bit userspace
+ backtrace.
  
  Break-Fix: - 9a5cbce421a283e6aea3c4007f141735bf9da8c3

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

Title:
  CVE-2015-6526

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

[Kernel-packages] [Bug 1492007] BOT: Examined VarLogDistupgradeApttermlog.gz

done
   dpkg: error processing package linux-image-extra-3.13.0-46-generic 
(--configure):
package linux-image-extra-3.13.0-46-generic is not ready for configuration


** Tags added: varlogdistupgradeapttermlog-examined

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

Title:
  package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to
  install/upgrade: package linux-image-extra-3.13.0-46-generic is not
  ready for configuration  cannot configure (current status `half-
  installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system came apart after I used BleachBit (root) and opted to clean
  the system.

  I had no desktop (xfce4) but managed to get it back ok.

  Tried using Computer Janitor to remove old packages to make room on
  /boot for upgrades.

  Now system is (may be) down on next re-boot.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic i686
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2076 F pulseaudio
  Date: Thu Sep  3 20:24:34 2015
  DuplicateSignature: 
package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package 
linux-image-extra-3.13.0-46-generic is not ready for configuration  cannot 
configure (current status `half-installed')
  ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9
  InstallationDate: Installed on 2015-02-25 (189 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to 
install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2003
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-6738
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr:
  dmi.product.name: KM266-8235
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 1490606] Re: linux: 3.19.0-28.30 -proposed tracker

** Description changed:

  This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC
+ kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20: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/1490606

Title:
  linux: 3.19.0-28.30 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC
  kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC

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

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

[Kernel-packages] [Bug 1490785] Re: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker

** Description changed:

  This bug is for tracking the 3.19.0-28.30~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 01. September 2015 01:02 UTC
  kernel-stable-master-bug:1490606
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC
+ kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC

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

Title:
  linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 01. September 2015 01:02 UTC
  kernel-stable-master-bug:1490606
  kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC
  kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC
  kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC

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

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

[Kernel-packages] [Bug 1478826] Re: CVE-2015-5157