[Kernel-packages] [Bug 887793] Re: [HP 6710b] Kworker constantly taking about 100% CPU

2020-07-28 Thread Colin Law
For anyone finding this the problem has re-appeared with Ubuntu 20.04 on a 
Fujitsu Lifebook A544 after upgrading to BIOS version 1.24 (or 1.25).  It shows 
itself as workers kacpid and acpid_notify hogging most of a core. the fix (or 
workaround?) is to run
sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13'
which works until a reboot, or to make it persistent add to the root crontab 
(using sudo crontab -e)
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13

Whether this has any side effects I don't know.

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

Title:
  [HP 6710b] Kworker constantly taking about 100% CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've this issue since the latest Ubuntu 11.10 version, all updates
  applied till today, and it's still there. Ubuntu 11.04 did not have
  this issue.

  If I run top there is a Kworker constantly taking much CPU, I don't
  know how to research where this comes from.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kp 1473 F pulseaudio
  CRDA: Error: [Errno 2] Bestand of map bestaat niet
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xe4404000 irq 46'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,103c30c0,00100200 
HDA:11c11040,103c1378,00100200'
 Controls  : 11
 Simple ctrls  : 9
  Date: Tue Nov  8 22:29:10 2011
  HibernationDevice: RESUME=UUID=ad8d4a18-9fe4-4246-ba44-85cf6b4dace5
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: Hewlett-Packard HP Compaq 6710b (GB891ET#ABH)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=686d2155-83a9-4743-a2a4-8e9570ee3da6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.15
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: CNU72913PH
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.15:bd01/15/2009:svnHewlett-Packard:pnHPCompaq6710b(GB891ET#ABH):pvrF.15:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6710b (GB891ET#ABH)
  dmi.product.version: F.15
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-09 Thread Colin Law
@yonsy your problem is not caused by this bug, which completely prevents
booting.

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


[Kernel-packages] [Bug 887793] Re: [HP 6710b] Kworker constantly taking about 100% CPU

2018-10-14 Thread Colin Law
It is not still open, it is marked as invalid.

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

Title:
  [HP 6710b] Kworker constantly taking about 100% CPU

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I've this issue since the latest Ubuntu 11.10 version, all updates
  applied till today, and it's still there. Ubuntu 11.04 did not have
  this issue.

  If I run top there is a Kworker constantly taking much CPU, I don't
  know how to research where this comes from.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kp 1473 F pulseaudio
  CRDA: Error: [Errno 2] Bestand of map bestaat niet
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xe4404000 irq 46'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,103c30c0,00100200 
HDA:11c11040,103c1378,00100200'
 Controls  : 11
 Simple ctrls  : 9
  Date: Tue Nov  8 22:29:10 2011
  HibernationDevice: RESUME=UUID=ad8d4a18-9fe4-4246-ba44-85cf6b4dace5
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: Hewlett-Packard HP Compaq 6710b (GB891ET#ABH)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=686d2155-83a9-4743-a2a4-8e9570ee3da6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.15
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: CNU72913PH
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.15:bd01/15/2009:svnHewlett-Packard:pnHPCompaq6710b(GB891ET#ABH):pvrF.15:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6710b (GB891ET#ABH)
  dmi.product.version: F.15
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-07-04 Thread Colin Law
I believe the bug should not be affecting more people as it is not
present in current kernels.  Also 17.10 goes end of life in a few weeks.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-06-23 Thread Colin Law
@Danny Vilca the repair method described in the bug description should
fix it. If not then ask for help on the Ubuntu Users mailing list.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-03-02 Thread Colin Law
The release notes for the 17.10 installer [1] linked to from the Desktop
download page [2] still have this issue in the Known Issues section at
the bottom.  Possibly the release notes need to be updated accordingly

[1]
https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes?_ga=2.209410322.1075533256.1519927551-135491812.1519054530

[2] https://www.ubuntu.com/download/desktop

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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

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

2016-01-16 Thread Colin Law
I can confirm that updating to BIOS 1.20 also fixes it for me (with SSD
drive).  Strange that the problem only exhibited itself with certain
kernel versions.  So it seems Joseph and myself have wasted our time
bisecting the kernel.  Sorry Joseph.  I learnt a lot in the process
however.  I will close the bug, I presume that correct status is '
invalid'.

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

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

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

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

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Invalid

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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-11-25 Thread Colin Law
Is anything happening on this?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1504420] Re: [FUJITSU LIFEBOOK A544] suspend/resume failure

2015-11-25 Thread Colin Law
** Attachment added: "dmesg on re-boot after failure with current kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504420/+attachment/4525280/+files/dmesg.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/1504420

Title:
  [FUJITSU LIFEBOOK A544] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On resume the screens (laptop + external)  showed windows as before
  suspend but the machine was completely unresponsive.

  This happens around 1 in 10 times I suspend.  I am suspending using
  pm-suspend or via the cog > Suspend.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1670 F pulseaudio
   /dev/snd/controlC1:  colinl 1670 F pulseaudio
  Date: Thu Oct  8 19:33:00 2015
  DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-10-21 (352 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK A544
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
  UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
  UserGroups:

  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/ubuntu/+source/linux/+bug/1504420/+subscriptions

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


[Kernel-packages] [Bug 1504420] Re: [FUJITSU LIFEBOOK A544] suspend/resume failure

2015-11-25 Thread Colin Law
** Attachment added: "/proc/acpi/wakeup from current kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504420/+attachment/4525281/+files/wakeup.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/1504420

Title:
  [FUJITSU LIFEBOOK A544] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On resume the screens (laptop + external)  showed windows as before
  suspend but the machine was completely unresponsive.

  This happens around 1 in 10 times I suspend.  I am suspending using
  pm-suspend or via the cog > Suspend.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1670 F pulseaudio
   /dev/snd/controlC1:  colinl 1670 F pulseaudio
  Date: Thu Oct  8 19:33:00 2015
  DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-10-21 (352 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK A544
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
  UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
  UserGroups:

  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/ubuntu/+source/linux/+bug/1504420/+subscriptions

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


[Kernel-packages] [Bug 1504420] Re: [FUJITSU LIFEBOOK A544] suspend/resume failure

2015-11-25 Thread Colin Law
After several weeks running with the suspend command
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
with both the latest mainline kernel I was unable to make it fail.  I reverted 
to the current kernel and it still refused to fail.  I then resorted to just 
using pm_suspend (with current kernel) and it did fail.  I don't know whether 
it is necessary to have 
echo 1 > /sys/power/pm_trace
on every suspend but from dmesg > dmesg.txt I see
$ grep -i "hash matches" dmesg.txt 
[2.322145] bdi 1:12: hash matches
[2.322151] tty ttyS14: hash matches

Suggestions on what I should do next please?

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

Title:
  [FUJITSU LIFEBOOK A544] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On resume the screens (laptop + external)  showed windows as before
  suspend but the machine was completely unresponsive.

  This happens around 1 in 10 times I suspend.  I am suspending using
  pm-suspend or via the cog > Suspend.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1670 F pulseaudio
   /dev/snd/controlC1:  colinl 1670 F pulseaudio
  Date: Thu Oct  8 19:33:00 2015
  DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-10-21 (352 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK A544
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
  UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
  UserGroups:

  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/ubuntu/+source/linux/+bug/1504420/+subscriptions

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


[Kernel-packages] [Bug 1504420] Re: [FUJITSU LIFEBOOK A544] suspend/resume failure

2015-10-15 Thread Colin Law
Tested with mainline kernel 4.3.0 rc5 and got the same failure, though
it seemed to take longer before it failed.  Likely just the statistics
working themselves out though.

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

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

Title:
  [FUJITSU LIFEBOOK A544] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On resume the screens (laptop + external)  showed windows as before
  suspend but the machine was completely unresponsive.

  This happens around 1 in 10 times I suspend.  I am suspending using
  pm-suspend or via the cog > Suspend.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1670 F pulseaudio
   /dev/snd/controlC1:  colinl 1670 F pulseaudio
  Date: Thu Oct  8 19:33:00 2015
  DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-10-21 (352 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK A544
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
  UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
  UserGroups:

  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/ubuntu/+source/linux/+bug/1504420/+subscriptions

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


[Kernel-packages] [Bug 1504420] [NEW] [FUJITSU LIFEBOOK A544] suspend/resume failure

2015-10-09 Thread Colin Law
Public bug reported:

On resume the screens (laptop + external)  showed windows as before
suspend but the machine was completely unresponsive.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-14-generic 4.2.0-14.16
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  colinl 1670 F pulseaudio
 /dev/snd/controlC1:  colinl 1670 F pulseaudio
Date: Thu Oct  8 19:33:00 2015
DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2014-10-21 (352 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
InterpreterPath: /usr/bin/python3.4
MachineType: FUJITSU LIFEBOOK A544
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-14-generic N/A
 linux-backports-modules-4.2.0-14-generic  N/A
 linux-firmware1.149
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
UserGroups:
 
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

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


** Tags: amd64 apport-kerneloops resume suspend wily

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

Title:
  [FUJITSU LIFEBOOK A544] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On resume the screens (laptop + external)  showed windows as before
  suspend but the machine was completely unresponsive.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1670 F pulseaudio
   /dev/snd/controlC1:  colinl 1670 F pulseaudio
  Date: Thu Oct  8 19:33:00 2015
  DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-10-21 (352 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK A544
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
  UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
  UserGroups:
   
  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

[Kernel-packages] [Bug 1504420] Re: [FUJITSU LIFEBOOK A544] suspend/resume failure

2015-10-09 Thread Colin Law
** Description changed:

  On resume the screens (laptop + external)  showed windows as before
  suspend but the machine was completely unresponsive.
+ 
+ This happens around 1 in 10 times I suspend.  I am suspending using pm-
+ suspend or via the cog > Suspend.
  
  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  colinl 1670 F pulseaudio
-  /dev/snd/controlC1:  colinl 1670 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  colinl 1670 F pulseaudio
+  /dev/snd/controlC1:  colinl 1670 F pulseaudio
  Date: Thu Oct  8 19:33:00 2015
  DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-10-21 (352 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK A544
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-4.2.0-14-generic N/A
-  linux-backports-modules-4.2.0-14-generic  N/A
-  linux-firmware1.149
+  linux-restricted-modules-4.2.0-14-generic N/A
+  linux-backports-modules-4.2.0-14-generic  N/A
+  linux-firmware1.149
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: yes
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: yes
+   Hard blocked: no
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
  UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
  UserGroups:
-  
+ 
  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

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

Title:
  [FUJITSU LIFEBOOK A544] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On resume the screens (laptop + external)  showed windows as before
  suspend but the machine was completely unresponsive.

  This happens around 1 in 10 times I suspend.  I am suspending using
  pm-suspend or via the cog > Suspend.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1670 F pulseaudio
   /dev/snd/controlC1:  colinl 1670 F pulseaudio
  Date: Thu Oct  8 19:33:00 2015
  DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-10-21 (352 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK A544
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
 

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

2015-10-07 Thread Colin Law
** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491467/+attachment/4486870/+files/acpidump.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/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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-16 Thread Colin Law
4.3-rc1 kernel (linux-
image-4.3.0-040300rc1-generic_4.3.0-040300rc1.201509160642_amd64.deb)
also exhibits the problem.

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-14 Thread Colin Law
OK.  In case it is of interest I have determined that the problem was
originally fixed between mainline kernels 3.13.11.11-trusty and
3.14-rc1-trusty, before being reintroduced in 4.0.

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-14 Thread Colin Law
I think 4.3-rc1 kernel build has failed, at least there are no images
there.  I will test it when they appear.

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-13 Thread Colin Law
Have I missed something or has it not arrived yet?

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

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

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

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

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

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

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

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

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

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

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


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

2015-09-10 Thread Colin Law
0dc553652102c55a43eb1ab52e2049e478469f53
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509092055_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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-09 Thread Colin Law
30fc8d138e9123f374a3c3867e7c7c5cd4004941
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081948_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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-09 Thread Colin Law
I don't think you have actually, there's nowt there :)

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-09 Thread Colin Law
71ed848fd791bc0b53a1b7a04f29eb9e994c7cbb
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509091541_amd64.deb 

is BAD

Only one, or two, to go :)

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-09 Thread Colin Law
It may be of interest that another A544 running kernel 3.13 exhibits the
problem.  It went away some time between then and 3.19 and came back in
4.0.  The other machine does not have an SSD so that may not be a
factor, though comments in the upstream bug suggested that it was a
factor.  Of course there may be multiple causes for apparently similar
symptoms.

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-08 Thread Colin Law
afb5abc262e962089ef2d7c2bbf71bb6f53a2a78
/home/colinl/Downloads/linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-08 Thread Colin Law
875edad528cf29b382e82837e652e997aec16c49
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-08 Thread Colin Law
Can you confirm the repo please, I get
$ git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/
Cloning into 'linux'...
fatal: remote error: Repository '~ubuntu-kernel/ubuntu/+source/linux' not found.

Alternatively is it fundamentally the same (as far as this exercise is 
concerned) as 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-06 Thread Colin Law
As a matter of interest, which repository have you cloned from?

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-06 Thread Colin Law
7b1ee96f074cc931a2c226b33607fe7a74d5cba3
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509050242_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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-04 Thread Colin Law
ba4877b9ca51f80b5d30f304a46762f0509e1635
linux-image-3.19.0-031900-generic_3.19.0-031900.201509041408_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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-04 Thread Colin Law
d3f180ea1a44aecba1b0dab2a253428e77f906bf
linux-image-3.19.0-031900-generic_3.19.0-031900.201509032049_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 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 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 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-03 Thread Colin Law
c5ce28df0e7c01a1de23c36ebdefcd803f2b6cbb
linux-image-3.19.0-031900-generic_3.19.0-031900.201509022146_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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-02 Thread Colin Law
02f1f2170d2831b3233e91091c60a66622f29e82
http://kernel.ubuntu.com/~jsalisbury/lp1491467
linux-image-3.19.0-031900-generic_3.19.0-031900.201509021605_amd64.deb

is BAD
that is it shows the bug.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1491467] [NEW] kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-02 Thread Colin Law
Public bug reported:

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

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


** Tags: amd64 apport-bug wily

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

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

Status in linux package in Ubuntu:
  New

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/ubuntu/+source/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   : 

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

2015-09-02 Thread Colin Law
I can confirm that 
v3.19 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ does 
not show the problem

4.0-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/
and
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/
both do show the problem

-- 
You 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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

2015-09-02 Thread Colin Law
By bisecting the kernel I have determined that the problem is not seen
on the last Ubuntu 3.19 kernel  3.19.8-vivid but is seen on the first
4.0 kernel that will build using fakeroot debian/rules binary-headers
binary-generic, which is

commit 636cdd7b2930ca2cdaf90eedd04fdb9fc7a8d5ec
Author: Stefan Bader 
Date:   Thu Feb 14 09:55:49 2008 -0500

UBUNTU: SAUCE: (no-up) ubuntu: dm-raid45

from  https://code.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/wily

It also exists on the latest mainline kernel 4.2.0

-- 
You 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 package in Ubuntu:
  New

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/ubuntu/+source/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 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working

2015-08-02 Thread Colin Law
*** This bug is a duplicate of bug 1459571 ***
https://bugs.launchpad.net/bugs/1459571

** This bug has been marked a duplicate of bug 1459571
   Keyboard shortcuts stop working

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

Title:
  [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have
  stopped working

Status in linux package in Ubuntu:
  Expired

Bug description:
  All of a sudden, the volume keys from the keyboard have stopped
  working.

  The volume control on the top right corner of the screen does work if
  used with the mouse.

  I have both an external usb keyboard with dedicated volume + and -
  keys, and the builtin laptop keyboard where the volume +/-keys are the
  combination of the Fn key plus the up/down arrows.

  All these used to work up to a few minutes ago. Now none of them works.
  I think they stopped working with the last reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo2303 F pulseaudio
   /dev/snd/pcmC0D0p:   teo2303 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:13:35 2014
  HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
  InstallationDate: Installed on 2013-10-11 (298 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1429143] [NEW] Slow shutdown after booting with systemd

2015-03-06 Thread Colin Law
Public bug reported:

When running vivid booted with systemd kernel, shutdown consistently
takes around 90 seconds.  With the normal kernel it is about 15 seconds.

In the log, shutdown started (from the cog) at 13:50:20, Mar 6th.  The
purple Ubuntu screen with dots appears after a few seconds and then sits
there.  It actually powered off at 13:51:55.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  colinl 1948 F pulseaudio
 /dev/snd/controlC1:  colinl 1948 F pulseaudio
CurrentDesktop: Unity
Date: Fri Mar  6 13:54:29 2015
InstallationDate: Installed on 2014-10-21 (135 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
MachineType: FUJITSU LIFEBOOK A544
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-bug vivid

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

Title:
  Slow shutdown after booting with systemd

Status in linux package in Ubuntu:
  New

Bug description:
  When running vivid booted with systemd kernel, shutdown consistently
  takes around 90 seconds.  With the normal kernel it is about 15
  seconds.

  In the log, shutdown started (from the cog) at 13:50:20, Mar 6th.  The
  purple Ubuntu screen with dots appears after a few seconds and then
  sits there.  It actually powered off at 13:51:55.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1948 F pulseaudio
   /dev/snd/controlC1:  colinl 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  6 13:54:29 2015
  InstallationDate: Installed on 2014-10-21 (135 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014: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/ubuntu/+source/linux/+bug/1429143/+subscriptions

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


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

2015-03-02 Thread Colin Law
@Sander under what circumstances are you seeing that?  I see a similar
message running stock Vivid on Fujitsu A544, but only if I close the lid
(for suspend) immediately after booting.  It does not suspend
immediately, but if lid is left down it does suspend a couple of minutes
later and the page_flip message is in syslog.

I don't see it if I wait a few minutes after booting and then close the
lid.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

  [ 2243.391146] Call Trace:
  [ 2243.391149]  IRQ  [817c4c00] dump_stack+0x45/0x57
  [ 2243.391162]  [81076e87] warn_slowpath_common+0x97/0xe0
  [ 2243.391166]  [81076f86] warn_slowpath_fmt+0x46/0x50
  [ 2243.391192]  [c04408a6] intel_check_page_flip+0xe6/0xf0 [i915]
  [ 2243.391214]  [c0405628] 
valleyview_pipestat_irq_handler+0x188/0x220 [i915]
  [ 2243.391236]  [c040bd2f] valleyview_irq_handler+0xaf/0x180 [i915]
  [ 2243.391242]  [8175d745] ? ip6_finish_output+0x95/0xd0
  [ 2243.391247]  [810ce4cd] handle_irq_event_percpu+0x5d/0x1e0
  [ 2243.391251]  [8175b18a] ? ip6_xmit+0x22a/0x490
  [ 2243.391255]  [810ce698] handle_irq_event+0x48/0x70
  [ 2243.391258]  [810d171f] handle_edge_irq+0x7f/0x120
  [ 2243.391263]  [810178a2] handle_irq+0x22/0x40
  [ 2243.391267]  [817d4e4c] do_IRQ+0x5c/0x110
  [ 2243.391271]  [817d2cad] common_interrupt+0x6d/0x6d
  [ 2243.391276]  [81703921] ? tcp_queue_rcv+0x21/0x130
  [ 2243.391280]  [816a7ac2] ? __skb_checksum_complete+0x22/0xd0
  [ 2243.391284]  [81708b54] tcp_rcv_established+0x194/0x740
  [ 2243.391289]  

[Kernel-packages] [Bug 1426123] Re: Laptop does not suspend on lid close when external monitor connected

2015-03-01 Thread Colin Law
Bug still present in kernel 4.0-rc1-vivid

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

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

Title:
  Laptop does not suspend on lid close when external monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected.  The external monitor blanks briefly and then resumes.
  It suspends ok using the menu and does suspend on lid close if the external 
monitor is not connected.
  On Utopic it suspended ok with external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-13-generic 3.18.0-13.14
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 2141 F pulseaudio
   /dev/snd/controlC1:  colinl 2141 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 26 20:50:04 2015
  InstallationDate: Installed on 2014-10-21 (128 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-13-generic N/A
   linux-backports-modules-3.18.0-13-generic  N/A
   linux-firmware 1.141
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (0 days ago)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014: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/ubuntu/+source/linux/+bug/1426123/+subscriptions

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


[Kernel-packages] [Bug 1426123] Re: Laptop does not suspend on lid close when external monitor connected

2015-03-01 Thread Colin Law
Is this definitely a kernel problem?  The same thing happened a few
Ubuntu versions ago and then I thought it was due to a decision in
upstream gnome somewhere that a laptop with external monitor should not
suspend when lid is closed, but that eventually got reverted, either
upstream or in Ubuntu, not sure which.

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

Title:
  Laptop does not suspend on lid close when external monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected.  The external monitor blanks briefly and then resumes.
  It suspends ok using the menu and does suspend on lid close if the external 
monitor is not connected.
  On Utopic it suspended ok with external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-13-generic 3.18.0-13.14
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 2141 F pulseaudio
   /dev/snd/controlC1:  colinl 2141 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 26 20:50:04 2015
  InstallationDate: Installed on 2014-10-21 (128 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-13-generic N/A
   linux-backports-modules-3.18.0-13-generic  N/A
   linux-firmware 1.141
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (0 days ago)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014: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/ubuntu/+source/linux/+bug/1426123/+subscriptions

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


[Kernel-packages] [Bug 1426123] [NEW] Laptop does not suspend on lid close when external monitor connected

2015-02-26 Thread Colin Law
Public bug reported:

Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected.  The external monitor blanks briefly and then resumes.
It suspends ok using the menu and does suspend on lid close if the external 
monitor is not connected.
On Utopic it suspended ok with external monitor.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.18.0-13-generic 3.18.0-13.14
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  colinl 2141 F pulseaudio
 /dev/snd/controlC1:  colinl 2141 F pulseaudio
CurrentDesktop: Unity
Date: Thu Feb 26 20:50:04 2015
InstallationDate: Installed on 2014-10-21 (128 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
MachineType: FUJITSU LIFEBOOK A544
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.18.0-13-generic N/A
 linux-backports-modules-3.18.0-13-generic  N/A
 linux-firmware 1.141
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-02-25 (0 days ago)
dmi.bios.date: 05/09/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.17
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-bug vivid

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

Title:
  Laptop does not suspend on lid close when external monitor connected

Status in linux package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected.  The external monitor blanks briefly and then resumes.
  It suspends ok using the menu and does suspend on lid close if the external 
monitor is not connected.
  On Utopic it suspended ok with external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-13-generic 3.18.0-13.14
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 2141 F pulseaudio
   /dev/snd/controlC1:  colinl 2141 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 26 20:50:04 2015
  InstallationDate: Installed on 2014-10-21 (128 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-13-generic N/A
   linux-backports-modules-3.18.0-13-generic  N/A
   linux-firmware 1.141
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (0 days ago)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014: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/ubuntu/+source/linux/+bug/1426123/+subscriptions

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


[Kernel-packages] [Bug 940350] Re: After suspend / resume only one monitor of dual head usable

2014-12-05 Thread Colin Law
@Christopher, no I can't I am afraid.  The machine is now running 14.04 and the 
problem is no longer seen.  Even if I could, is work still being done to fix 
non-critical Unity 2d bugs?
Possibly it is still affecting one of the other affected users.

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

Title:
  After suspend / resume only one monitor of dual head usable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using unity-2d on Precise, with dual head system, after suspend/resume
  I find about 50% of the time that only the external monitor is
  enabled.  The mouse will only move on that display and the launcher is
  shown on that display when before suspend it was on the laptop
  display.  Furthermore I cannot re-enable the laptop display using
  System Settings  Displays (the laptop shows as Off, and if I enable
  it it shows On but does not in fact come on).  I have to reboot in
  order to re-activate it.

  Further analysis added 20 Mar 12 as described in comment #7
  In System Settings  Power I have Do Nothing as the action on lid close (as 
there is a problem with this Toshiba Satellite laptop if the lid is used to 
suspend). I am suspending using the top panel menu action.
  If I close the lid then I find that it turns off the laptop display and the 
PC switches to single monitor mode on the external monitor, which is ok. On 
opening the lid it reverts to dual monitor mode.
  The bug described here is triggered if I initiate the suspend but then close 
the lid before the suspend is complete. On re-opening the lid the PC resumes 
but the laptop display does not switch back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pm-utils 1.4.1-9
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  Date: Fri Feb 24 14:28:04 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 
(2029.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1372967] Re: Touchpad not working and not recognized

2014-10-22 Thread Colin Law
@Davide for the future click on the yellow pen marker by Tags at the
bottom of the description.  I have added the tag.

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

Title:
  Touchpad not working and not recognized

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Even during installation the touchpad did not work, after installing
  ubuntu 14.04 i tried to use xinput list but this is the result:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02E3 id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02B1 id=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ FJ Camera   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)

  
  The SynPS/2 Synaptics TouchPad is not present anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dquaglio   1524 F pulseaudio
   /dev/snd/controlC0:  dquaglio   1524 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 23 16:19:31 2014
  HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831
  InstallationDate: Installed on 2014-09-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=04575c6d-aff9-4da6-8b8b-f7cdfdb0a5a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.6
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.13
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd11/18/2013: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/ubuntu/+source/linux/+bug/1372967/+subscriptions

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


[Kernel-packages] [Bug 1372967] Re: Touchpad not working and not recognized

2014-10-22 Thread Colin Law
Present on Utopic release candidate.  Kernel 3.16.0-23 64 bit.

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

Title:
  Touchpad not working and not recognized

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Even during installation the touchpad did not work, after installing
  ubuntu 14.04 i tried to use xinput list but this is the result:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02E3 id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02B1 id=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ FJ Camera   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)

  
  The SynPS/2 Synaptics TouchPad is not present anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dquaglio   1524 F pulseaudio
   /dev/snd/controlC0:  dquaglio   1524 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 23 16:19:31 2014
  HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831
  InstallationDate: Installed on 2014-09-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=04575c6d-aff9-4da6-8b8b-f7cdfdb0a5a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.6
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.13
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd11/18/2013: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/ubuntu/+source/linux/+bug/1372967/+subscriptions

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


[Kernel-packages] [Bug 1372967] Re: Touchpad not working and not recognized

2014-10-22 Thread Colin Law
As noted in duplicate bug #1372967 a workaround appears to be to add boot 
options
i8042.notimeout i8042.nomux
According to that report, however, this is only temporary, though it is working 
ok fo me so far.

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

Title:
  Touchpad not working and not recognized

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Even during installation the touchpad did not work, after installing
  ubuntu 14.04 i tried to use xinput list but this is the result:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02E3 id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02B1 id=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ FJ Camera   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)

  
  The SynPS/2 Synaptics TouchPad is not present anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dquaglio   1524 F pulseaudio
   /dev/snd/controlC0:  dquaglio   1524 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 23 16:19:31 2014
  HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831
  InstallationDate: Installed on 2014-09-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=04575c6d-aff9-4da6-8b8b-f7cdfdb0a5a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.6
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.13
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd11/18/2013: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/ubuntu/+source/linux/+bug/1372967/+subscriptions

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


[Kernel-packages] [Bug 1037094] Re: writing `/dev/mem': Bad address Error writing to ACPI area with 32 bit kernel

2014-01-01 Thread Colin Law
Christopher, this is no longer giving me a problem as bug 806032 has
been fixed.  However I have checked with Trusty (kernel 3.12.0-7 32 bit)
and the problem described here does still exist.  The bug is therefore
not invalid, but from my point of view it does not need fixing.  I don't
know what the convention is in such cases.  Won't Fix might be more
appropriate but it will not let me set it to that.

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

Title:
  writing `/dev/mem': Bad address Error writing to ACPI area with 32
  bit kernel

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using the 32 bit kernel I am unable to write to the ACPI memory area
  using the command

  sudo dd if=value_file of=/dev/mem bs=1 seek=3660685688 count=4
  This gives the error
  dd: writing `/dev/mem': Bad address

  3660685688 is 0xDA31A178 and sudo cat /proc/iomem shows
  ...
  da216000-da32bfff : ACPI Non-volatile Storage
  ...

  This works ok with the 64 bit kernel.
  I have also tested it with the Oneiric kernel 3.0.0-12 and again the 64 bit 
kernel is ok but the 32 bit gives the error.

  In case it is relevant the context is that I am trying to apply the 
workaround for bug #806032 (
  Fn + F[89] does not work for controlling brightness on Clevo laptops) 
described in comment #7, which works perfectly on the 64 bit kernel but gives 
Bad Address error on 32 bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-10-generic 3.5.0-10.10
  ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
  Uname: Linux 3.5.0-10-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 2142 F pulseaudio
  Date: Wed Aug 15 13:42:37 2012
  HibernationDevice: RESUME=UUID=386e4578-bf9d-4970-a10f-b0b513b32771
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1)
  MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-10-generic 
root=UUID=c5043680-f556-4f19-9e32-c6fdb4c05f9e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-10-generic N/A
   linux-backports-modules-3.5.0-10-generic  N/A
   linux-firmware1.88
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/24/2012:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

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

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


[Kernel-packages] [Bug 971876] Re: Realtek Card Reader RTL8411 Device 5289 (PCI 03:00.0) Driver and udisks Rule

2013-11-12 Thread Colin Law
This bug has been fixed, the 13.10 kernel should support this device
without a workaround.  Anyone still seeing a problem should report a new
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/971876

Title:
  Realtek Card Reader RTL8411 Device 5289 (PCI 03:00.0) Driver and
  udisks Rule

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Fix Released
Status in “udisks” package in Ubuntu:
  Fix Released

Bug description:
  We have been provided with a new Realtek Card Reader driver for this
  device. The code is GPL licensed but we don't see it publicly
  available yet. This is a new driver module with the name rts_bpp. As
  such a new udisks rule is necessary for automounting.

  New driver is attached rts_bpp.tar.bz2.

  For automount, the following line needs to be added to
  '/lib/udev/rules.d/80-udisks.rules'

  DRIVERS==rts_bpp, ENV{ID_DRIVE_FLASH_SD}=1

  #

  We created a DKMS module .deb to make install easier until the driver
  can be included in Ubuntu. Commands:

  wget http://planet76.com/drivers/realtek/rts-bpp-dkms_1.1_all.deb
  sudo apt-get install dkms
  sudo dpkg -i rts-bpp-dkms_1.1_all.deb
  echo 'DRIVERS==rts_bpp, ENV{ID_DRIVE_FLASH_SD}=1' | sudo tee -a 
/lib/udev/rules.d/81-udisks-realtek.rules

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: udisks 1.0.4-5ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Mon Apr  2 14:16:29 2012
  HotplugNewDevices: /dev/sdb1
  HotplugNewMounts: /dev/sdb1 /media/6331-6363 vfat 
rw,nosuid,nodev,relatime,uid=2,gid=2,fmask=0022,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro
 0 0
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic 
root=UUID=596df159-fc9a-41b4-8528-5dca5215dbd5 ro quiet splash vt.handoff=7
  SourcePackage: udisks
  Symptom: storage
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/24/2012:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

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

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