date:20180103

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

2018-01-03 Thread bford16

Successful fix verified on Lenovo Flex 3-1120, using step 8 from the
description.

--
You 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:
Confirmed
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'.

---

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 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
Dell Inspiron 15-3531 (not fixed by 4.14.9)
Mediacom Smartbook 14 Ultra M-SB14UC
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 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")

2018-01-03 Thread Zhanglei Mao

This patch have been accepted to be merged in in kernel V4.16. Please
refer to:  https://lkml.org/lkml/2017/12/25/24

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

Title:
  hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
  io_mem_pfn callback")

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  On Artful kernels, X fails to start and a kernel splat is printed.

  This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
  incomplete: the hisilicon hibmc driver does not contain the callback
  and so the kernel tries to execute code at NULL.

  [Fix]
  There is a discussion and potential fix at 
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The 
fix hasn't landed yet and it looks like they're going to re-engineer the entire 
section instead.

  Rather than wait for that and deal with the massive regression
  potential, the fix I have picked to submit is very very minimal and
  touches only hibmc.

  [Regression Potential]
  Minimal - fix only touches hibmc driver. Tested on D05 board.

  [Testcase]
  Install patched kernel, try to start X. If it succeeds, the fix works. If 
there's a kernel splat, the fix does not work.

  [Notes]
  HiSilicon would really like this fix in Artful in such time so that when the 
next 16.04 point release ships in February, the HWE kernel will work with Xorg.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-03 Thread uocc4me

The kernel in step 8 fixed the bios in my Acer ES1-111M-C7DE (with
Winbond 25Q64FWSIG). Now I can make changes to the settings (such as
UEFI/legacy), and they are still there after rebooting. System details
at #193.

I got the kernel from http://people.canonical.com/~ypwong/lp1734147
/linux-
image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb

Cheers!

--
You 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

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:

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'.

---

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:

---

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

[Kernel-packages] [Bug 1737005] Re: Mainline kernel 4.14 does not start apparmor

2018-01-03 Thread Klaus Bielke

Behavior was explained and confirmed by comment #2. Proposed kernel
parameter works for me. Adding logs seems not helpfull to me, confirming
anyway.

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

Title:
  Mainline kernel 4.14 does not start apparmor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
  4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
  ureadahead.service. Sometimes udisks2.service fails too.

  $ uname -a
  Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25 
UTC 2017 i686 i686 i686 GNU/Linux

  $ systemctl --failed
    UNIT   LOAD   ACTIVE SUBDESCRIPTION
  ● apparmor.service   loaded failed failed LSB: AppArmor initialization
  ● udisks2.serviceloaded failed failed Disk Manager
  ● ureadahead.service loaded failed failed Read required files in advance

  $ systemctl status apparmor.service
  ● apparmor.service - LSB: AppArmor initialization
     Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
     Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
   Docs: man:systemd-sysv-generator(8)
    Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)

  Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor 
initialization...
  Dez 07 18:04:51 lieselotte apparmor[689]:  * Starting AppArmor profiles
  Dez 07 18:04:51 lieselotte apparmor[689]:  * AppArmor not available as kernel 
LSM.
  Dez 07 18:04:51 lieselotte apparmor[689]:...fail!
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process 
exited, code=exited status=1
  Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed 
state.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 
'exit-code'.

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

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

[Kernel-packages] [Bug 1741166] [NEW] [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

2018-01-03 Thread AceLan Kao

Public bug reported:

[Impact]
QCA6174A XR can scan but can't pair with bt 4.0 device.

[Fix]
[0cf3:e010] is one of the QCA ROME family and should be listed in btusb driver.

[Test Case]
Applied the patch and can pair with bt 4.0 keyboard without any issue.

[Regression Potential]
Adding the device to the list won't have any regression potential.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Patch added: "0001-Bluetooth-btusb-Add-support-for-0cf3-e010.patch"
   
https://bugs.launchpad.net/bugs/1741166/+attachment/5030859/+files/0001-Bluetooth-btusb-Add-support-for-0cf3-e010.patch

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

Title:
  [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  QCA6174A XR can scan but can't pair with bt 4.0 device.

  [Fix]
  [0cf3:e010] is one of the QCA ROME family and should be listed in btusb 
driver.

  [Test Case]
  Applied the patch and can pair with bt 4.0 keyboard without any issue.

  [Regression Potential]
  Adding the device to the list won't have any regression potential.

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

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

[Kernel-packages] [Bug 1741167] [NEW] Mainline kernel 4.14.11 not booting on Lenovo X220

2018-01-03 Thread Klaus Bielke

Public bug reported:

With Ubuntu 16.04.3 LTS (Xenial Xerus), Ubuntu mainline kernel 4.14.10
or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. After
GRUB message 'loading initrd' screen is cleared and machine restarts
BIOS. Nothing is written to screen or system log.

Mainline kernels up to 4.14.9 for arch i386 works fine.

Booting same machine with mainline kernel 4.14.11 for arch amd64 works
fine.

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

** Attachment added: "lspci (kernel 4.14.9 running)"
   
https://bugs.launchpad.net/bugs/1741167/+attachment/5030860/+files/lspci-vnvn.log

** Description changed:

- With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
- 4.14.10 or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220.
- After GRUB message 'loading initrd' screen is cleared and machine
- restarts BIOS. Nothing is written to screen or system log.
+ With Ubuntu 16.04.3 LTS (Xenial Xerus), Ubuntu mainline kernel 4.14.10
+ or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. After
+ GRUB message 'loading initrd' screen is cleared and machine restarts
+ BIOS. Nothing is written to screen or system log.
  
  Mainline kernels up to 4.14.9 for arch i386 works fine.
  
  Booting same machine with mainline kernel 4.14.11 for arch amd64 works
  fine.

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

Title:
  Mainline kernel 4.14.11 not booting on Lenovo X220

Status in linux package in Ubuntu:
  New

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), Ubuntu mainline kernel 4.14.10
  or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. After
  GRUB message 'loading initrd' screen is cleared and machine restarts
  BIOS. Nothing is written to screen or system log.

  Mainline kernels up to 4.14.9 for arch i386 works fine.

  Booting same machine with mainline kernel 4.14.11 for arch amd64 works
  fine.

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

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

[Kernel-packages] [Bug 1738523] Re: External HDMI monitor failed to show screen on Lenovo X1 series

2018-01-03 Thread AaronMa

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  External HDMI monitor failed to show screen on Lenovo X1 series

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Thinkpad X1 yoga:
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])

  Steps:
  1, Connect an external monitor
  2, Try to switch display modes in mirrored, extended, displayed on external 
or internal.

  [Impact]
  External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon

  [Fix]
  Add a workaround to bypass this TMDS_OE writing on identified laptop models.

  [Test Case]
  Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output
  OK.

  [Regression Potential]
  Low, it limits to ThinkPad specific laptops.

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

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

[Kernel-packages] [Bug 1741168] Re: HID: Fix RayD touchscreen failure to resume from suspend

2018-01-03 Thread AaronMa

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

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

Title:
  HID: Fix RayD touchscreen failure to resume from suspend

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

Bug description:
  Link: https://patchwork.kernel.org/patch/10141099/
  Link: https://patchwork.kernel.org/patch/10141097/

  [Impact]
  Resume of S3 cause system hang on Lenovo laptops with RayD touchscreen.

  [Fix]
  RayD touchscreen issued corrupted data after it resume from suspend,
  then HID driver didn't handle the data well because of the data overflow
  and made a call trace and hang.
  Keep memset safe from corrupted data and add command to make RayD
  touchscreen back to normal.
  Then touchscreen works fine.

  [Test Case]
  Tested on ThinkPad L380, works fine with fixes.

  [Regression Potential]
  Low, keep the data in hid-core and i2c-hid more strictly.
  Add specific device quirk in i2c-hid.

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

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

[Kernel-packages] [Bug 1723986] Re: Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

2018-01-03 Thread AaronMa

** Changed in: hwe-next
 Assignee: (unassigned) => AaronMa (mapengyu)

** Changed in: hwe-next
   Importance: Undecided => Critical

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Synaptics devices on Lenovo X1C6 and X280 can not work via PS/2 mode, it show:
  [   11.366996] psmouse serio1: synaptics: Touchpad model: 1, fw: 9.16, id: 
0x1e2a1, caps: 0xf001a3/0x940300/0x12e800/0x50, board id: 3382, fw id: 
2629663
  [   11.367002] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [   11.781876] psmouse serio2: Failed to reset mouse on synaptics-pt/serio0
  [   30.390508] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [   30.862260] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  Enable SMBus mode on these devices will make them work.

  Cherrypick 3 patches from patchwork as sauce patches on Ubuntu Artful
  kernel.

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

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

[Kernel-packages] [Bug 1740438] Re: Kernel has troule recognizing Corsair Harpoon RGB mouse

2018-01-03 Thread TuxRocks

kaihengfeng, it seems to happen a little less often with the linked
kernel, but I'm still experiencing the error. I have copied my dmesg
output below.

[0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1 
with crng_init=0
[0.00] Linux version 4.13.0-22-generic (root@Precision-3520) (gcc 
version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)) #25~lp1740438 SMP Wed Jan 3 12:06:33 
CST 2018 (Ubuntu 4.13.0-22.25~lp1740438-generic 4.13.13)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic 
root=UUID=ce80946f-0157-40fa-8410-c866a1e5c481 ro quiet splash vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x86120fff] usable
[0.00] BIOS-e820: [mem 0x86121000-0x86121fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x86122000-0x86122fff] reserved
[0.00] BIOS-e820: [mem 0x86123000-0x8e6e9fff] usable
[0.00] BIOS-e820: [mem 0x8e6ea000-0x8eb71fff] reserved
[0.00] BIOS-e820: [mem 0x8eb72000-0x8ec18fff] usable
[0.00] BIOS-e820: [mem 0x8ec19000-0x8efc0fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x8efc1000-0x8fb42fff] reserved
[0.00] BIOS-e820: [mem 0x8fb43000-0x8fbfefff] type 20
[0.00] BIOS-e820: [mem 0x8fbff000-0x8fbf] usable
[0.00] BIOS-e820: [mem 0x8fc0-0x8fff] reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00046eff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.60 by American Megatrends
[0.00] efi:  ACPI 2.0=0x8ec19000  ACPI=0x8ec19000  SMBIOS=0x8fa65000  
MPS=0xfc9e0  ESRT=0x88a1ce98  MEMATTR=0x889da018 
[0.00] random: fast init done
[0.00] SMBIOS 3.0 present.
[0.00] DMI: MSI MS-7A59/Z270 SLI (MS-7A59), BIOS 1.80 11/20/2017
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x46f000 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 00C000 mask 7FC000 uncachable
[0.00]   1 base 00A000 mask 7FE000 uncachable
[0.00]   2 base 009000 mask 7FF000 uncachable
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0x8fc00 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fcc40-0x000fcc4f] mapped at 
[90ec000fcc40]
[0.00] esrt: Reserving ESRT space from 0x88a1ce98 to 
0x88a1ced0.
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [90ec00095000] 95000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x3e8b23000,

Re: [Kernel-packages] [Bug 1581799] radeon driver hangs : nothing else that static effect on display

2018-01-03 Thread Kai-Heng Feng

> On 4 Jan 2018, at 4:08 AM, magowiz <1581...@bugs.launchpad.net> wrote:
> 
> Ok, thank you for the information, do I need to report here upstream bug
> reference after I created bug report?

Yes, that would be really helpful, thanks!

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1581799
> 
> Title:
>  radeon driver hangs : nothing else that static effect on display
> 
> Status in linux package in Ubuntu:
>  Triaged
> 
> Bug description:
>  Hi,
>  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
> due to drop support of fglrx driver (that was working) and due to radeon 
> opensource driver not working with my VGA.
> 
>  Mine video card:
>  $ lspci -nn | grep VGA
>  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]
> 
>  $ lsb_release -rd
>  Description: Ubuntu 16.04 LTS
>  Release: 16.04
> 
>  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
>  --- 
>  ApportVersion: 2.20.1-0ubuntu2.1
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/pcmC0D0c:   magowiz4930 F...m pulseaudio
>   /dev/snd/pcmC0D0p:   magowiz4930 F...m pulseaudio
>   /dev/snd/controlC0:  magowiz4930 F pulseaudio
>  DistroRelease: Ubuntu 16.04
>  HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
>  InstallationDate: Installed on 2012-01-03 (1615 days ago)
>  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
>  IwConfig:
>   eth0  no wireless extensions.
> 
>   lono wireless extensions.
>  MachineType: System manufacturer System Product Name
>  Package: linux (not installed)
>  ProcFB: 0 radeondrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
> root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
>  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
>  RelatedPackageVersions:
>   linux-restricted-modules-4.4.0-22-generic N/A
>   linux-backports-modules-4.4.0-22-generic  N/A
>   linux-firmware1.157
>  RfKill:
> 
>  Tags:  xenial
>  Uname: Linux 4.4.0-22-generic x86_64
>  UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago)
>  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>  _MarkForUpload: True
>  dmi.bios.date: 12/09/2011
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: 1003
>  dmi.board.asset.tag: To be filled by O.E.M.
>  dmi.board.name: F1A55-M LE
>  dmi.board.vendor: ASUSTeK COMPUTER INC.
>  dmi.board.version: Rev X.0x
>  dmi.chassis.asset.tag: Asset-1234567890
>  dmi.chassis.type: 3
>  dmi.chassis.vendor: Chassis Manufacture
>  dmi.chassis.version: Chassis Version
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
>  dmi.product.name: System Product Name
>  dmi.product.version: System Version
>  dmi.sys.vendor: System manufacturer
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+subscriptions

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   magowiz4930 F...m pulseaudio
   /dev/snd/pcmC0D0p:   magowiz4930 F...m pulseaudio
   /dev/snd/controlC0:  magowiz4930 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
  InstallationDate: Installed on 2012-01-03 (1615 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
  ProcVersionSignature:

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

2018-01-03 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1741167

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

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

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

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

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

Title:
  Mainline kernel 4.14.11 not booting on Lenovo X220

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), Ubuntu mainline kernel 4.14.10
  or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. After
  GRUB message 'loading initrd' screen is cleared and machine restarts
  BIOS. Nothing is written to screen or system log.

  Mainline kernels up to 4.14.9 for arch i386 works fine.

  Booting same machine with mainline kernel 4.14.11 for arch amd64 works
  fine.

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

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

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

2018-01-03 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1741168

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

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

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

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

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

Title:
  HID: Fix RayD touchscreen failure to resume from suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Link: https://patchwork.kernel.org/patch/10141099/
  Link: https://patchwork.kernel.org/patch/10141097/

  [Impact]
  Resume of S3 cause system hang on Lenovo laptops with RayD touchscreen.

  [Fix]
  RayD touchscreen issued corrupted data after it resume from suspend,
  then HID driver didn't handle the data well because of the data overflow
  and made a call trace and hang.
  Keep memset safe from corrupted data and add command to make RayD
  touchscreen back to normal.
  Then touchscreen works fine.

  [Test Case]
  Tested on ThinkPad L380, works fine with fixes.

  [Regression Potential]
  Low, keep the data in hid-core and i2c-hid more strictly.
  Add specific device quirk in i2c-hid.

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

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

[Kernel-packages] [Bug 1741168] [NEW] HID: Fix RayD touchscreen failure to resume from suspend

2018-01-03 Thread AaronMa

Public bug reported:

Link: https://patchwork.kernel.org/patch/10141099/
Link: https://patchwork.kernel.org/patch/10141097/

[Impact]
Resume of S3 cause system hang on Lenovo laptops with RayD touchscreen.

[Fix]
RayD touchscreen issued corrupted data after it resume from suspend,
then HID driver didn't handle the data well because of the data overflow
and made a call trace and hang.
Keep memset safe from corrupted data and add command to make RayD
touchscreen back to normal.
Then touchscreen works fine.

[Test Case]
Tested on ThinkPad L380, works fine with fixes.

[Regression Potential]
Low, keep the data in hid-core and i2c-hid more strictly.
Add specific device quirk in i2c-hid.

** Affects: hwe-next
 Importance: Critical
 Assignee: AaronMa (mapengyu)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: AaronMa (mapengyu)
 Status: Incomplete


** Tags: originate-from-1731135 sutton

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

** Tags added: originate-from-1731135 sutton

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  HID: Fix RayD touchscreen failure to resume from suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Link: https://patchwork.kernel.org/patch/10141099/
  Link: https://patchwork.kernel.org/patch/10141097/

  [Impact]
  Resume of S3 cause system hang on Lenovo laptops with RayD touchscreen.

  [Fix]
  RayD touchscreen issued corrupted data after it resume from suspend,
  then HID driver didn't handle the data well because of the data overflow
  and made a call trace and hang.
  Keep memset safe from corrupted data and add command to make RayD
  touchscreen back to normal.
  Then touchscreen works fine.

  [Test Case]
  Tested on ThinkPad L380, works fine with fixes.

  [Regression Potential]
  Low, keep the data in hid-core and i2c-hid more strictly.
  Add specific device quirk in i2c-hid.

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

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

[Kernel-packages] [Bug 1741166] Re: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

2018-01-03 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  QCA6174A XR can scan but can't pair with bt 4.0 device.

  [Fix]
  [0cf3:e010] is one of the QCA ROME family and should be listed in btusb 
driver.

  [Test Case]
  Applied the patch and can pair with bt 4.0 keyboard without any issue.

  [Regression Potential]
  Adding the device to the list won't have any regression potential.

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

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

[Kernel-packages] [Bug 1740438] Re: Kernel has troule recognizing Corsair Harpoon RGB mouse

2018-01-03 Thread Kai-Heng Feng

Please try this kernel:
http://people.canonical.com/~khfeng/lp1740438-2/

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

Title:
  Kernel has troule recognizing Corsair Harpoon RGB mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently started using a Corsair Harpoon RGB mouse and the kernel is
  having trouble recognizing it. About half of the time when I boot, I
  see messages like this:

  [7.132078] usb 1-14: unable to read config index 0 descriptor/all
  [7.132081] usb 1-14: can't read configurations, error -110

  Occasionally they repeat after a few seconds. The mouse will not
  function until I unplug the mouse and plug it back in. So far, one
  unplug and plug has fixed it every time. I am running Xubuntu 17.10 on
  4.13.0-21.24-generic 4.13.13. I have attached the extra debug
  information that is generated by ubuntu-bug linux. I can provide
  additional information, if needed, and I am available to troubleshoot
  this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ben 937 F pulseaudio
   /dev/snd/controlC0:  ben 937 F pulseaudio
   /dev/snd/controlC1:  ben 937 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 28 14:13:19 2017
  InstallationDate: Installed on 2017-12-20 (8 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7A59
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=ce80946f-0157-40fa-8410-c866a1e5c481 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270 SLI (MS-7A59)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd11/20/2017:svnMSI:pnMS-7A59:pvr1.0:rvnMSI:rnZ270SLI(MS-7A59):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A59
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1741084] Re: rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229]

2018-01-03 Thread Launchpad Bug Tracker

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

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

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

Title:
  rtsx_pci needs to be manually loaded for Realtek Semiconductor Co.,
  Ltd. RTS5229 PCI Express Card Reader [10ec:5229]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A friend's card reader in his ThinkPad L430 [10ec:5229] was not
  automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had
  to manually load the rtsx_pci module.

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

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

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

2018-01-03 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1741084

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

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

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

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

Title:
  rtsx_pci needs to be manually loaded for Realtek Semiconductor Co.,
  Ltd. RTS5229 PCI Express Card Reader [10ec:5229]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A friend's card reader in his ThinkPad L430 [10ec:5229] was not
  automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had
  to manually load the rtsx_pci module.

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

2018-01-03 Thread Launchpad Bug Tracker

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

** Changed in: openvswitch (Ubuntu)
   Status: New => Confirmed

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

Title:
  openvswitch: kernel opps destroying interfaces on i386

Status in linux package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in openvswitch source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in openvswitch source package in Bionic:
  Confirmed

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

2018-01-03 Thread Launchpad Bug Tracker

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

** Changed in: openvswitch (Ubuntu Artful)
   Status: New => Confirmed

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

Title:
  openvswitch: kernel opps destroying interfaces on i386

Status in linux package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in openvswitch source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in openvswitch source package in Bionic:
  Confirmed

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

2018-01-03 Thread ChristianEhrhardt

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

** This bug has been marked a duplicate of bug 1736390
   openvswitch: kernel opps destroying interfaces on i386

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

Title:
  4.12.0-11-generic - crashing in infrastructure on i386 openvswitch
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Hi,
  this seems to me to be a kernel crash of some sorts.
  Somewhat in the spirit of older bugs:
  - bug 1630940
  - bug 1630578

  Xnox asked me to look into a hang on openvswitch dep8 tests.
  What I found initially was in the log just
"ERROR: Removing temporary files on testbed timed out"
  That message brought me to the two bugs above.

  But in there I read that this was the infra running dep8 crashing.
  So for a better bug report I tried to reproduce locally and that actually 
seems to work very reliable.

  To reproduce do:
  $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
  $ pull-lp-source openvswitch
  $ autopkgtest --apt-upgrade --shell --no-built-binaries 
openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu 
~/work/autopkgtest-artful-i386.img
  # This guest currently will crash after a while of testing

  
  But with that running you can attach to the console and monitor of that guest.
  For example:
  $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0

  That gave me a crash on the hang which kind of matches the older bugs, here 
the console:
  [   54.256253] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   54.257156] IP: add_grec+0x28/0x440
  [   54.257553] *pdpt = 1a869001 *pde =  
  [   54.257555] 
  [   54.258338] Oops:  [#1] SMP
  [   54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg 
i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net floppy pata_acpi
  [   54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW   
4.12.0-11-generic #12-Ubuntu
  [   54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
  [   54.263610] task: c7b622c0 task.stack: c7b5a000
  [   54.264039] EIP: add_grec+0x28/0x440
  [   54.264378] EFLAGS: 00010202 CPU: 0
  [   54.264711] EAX:  EBX: dd062540 ECX: 0006 EDX: dd062540
  [   54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0
  [   54.265793]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.266297] CR0: 80050033 CR2:  CR3: 1e930d80 CR4: 06f0
  [   54.266885] Call Trace:
  [   54.267120]  
  [   54.267349]  mld_ifc_timer_expire+0xfe/0x250
  [   54.267754]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268173]  call_timer_fn+0x30/0x120
  [   54.268524]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268942]  ? mld_dad_timer_expire+0x50/0x50
  [   54.269364]  run_timer_softirq+0x3c5/0x420
  [   54.269760]  ? __softirqentry_text_start+0x8/0x8
  [   54.270198]  __do_softirq+0xa9/0x245
  [   54.270539]  ? __softirqentry_text_start+0x8/0x8
  [   54.270976]  do_softirq_own_stack+0x24/0x30
  [   54.271373]  
  [   54.271611]  irq_exit+0xad/0xb0
  [   54.271913]  smp_apic_timer_interrupt+0x38/0x50
  [   54.272344]  apic_timer_interrupt+0x39/0x40
  [   54.272745] EIP: native_safe_halt+0x5/0x10
  [   54.273139] EFLAGS: 0246 CPU: 0
  [   54.273624] EAX:  EBX:  ECX: 0001 EDX: 
  [   54.274000] ESI:  EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10
  [   54.274361]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.274687]  default_idle+0x1c/0xf0
  [   54.274896]  arch_cpu_idle+0xe/0x10
  [   54.275286]  default_idle_call+0x1e/0x30
  [   54.275787]  do_idle+0x145/0x1c0
  [   54.276092]  cpu_startup_entry+0x65/0x70
  [   54.276441]  rest_init+0x62/0x70
  [   54.276718]  start_kernel+0x3be/0x3d7
  [   54.276974]  i386_start_kernel+0x9d/0xa1
  [   54.277260]  startup_32_smp+0x16b/0x16d
  [   54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 
89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 
c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b
  [   54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0
  [   54.279829] CR2: 
  [   54.280143] ---[ end trace 3164b1c0dd7745bc ]---
  [   54.280550] Kernel panic - not syncing: Fatal exception in interrupt
  [   54.281078] Kernel Offset: 0x600 from 0xc100 (relocation range: 
0xc000-0xdfbfdfff)
  [   54.281797] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt

  But since this is

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Per Ekelund

Possible problem with Dell XPS 13 9350.

Upgraded to 17.10 before christmas, with kernel ...19. Sudden freeze,
when doing powercycle I got a "no bootable device found". I was able to
update the BIOS but with no luck. Then I booted 17.04 from USB but Linux
was unable to find the disk. However the Samsung controller was found.

Has sent the unit in for repair.

--
You 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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Bug description:
Description: An update to linux kernel on Ubuntu 17.10 that enabled
the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
Settings being not stored, USB Boot impossible and EFI entries read-
only.

Fix: The issue was fixed in Kernel Version 4.13.0-21. 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:

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'.

---

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:

---

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

2018-01-03 Thread ChristianEhrhardt

>From the Dup - FYI
To reproduce do:
$ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
$ pull-lp-source openvswitch
$ autopkgtest --apt-upgrade --shell --no-built-binaries 
openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu 
~/work/autopkgtest-artful-i386.img
# This guest currently will crash after a while of testing

Really easy to reproduce (and close to 100% fail rate)

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

Title:
  openvswitch: kernel opps destroying interfaces on i386

Status in linux package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in openvswitch source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in openvswitch source package in Bionic:
  Confirmed

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-01-03 Thread Ryan Burke

@Brad - As much as I dislike using "old" kernels, this is definitely
worth testing. I'll try as you've suggested tonight and report back
ASAP.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1731163] Re: Trackpoint device not working by default on Thinkpad L570

2018-01-03 Thread Martin Dirichs

Someone else seems to have reported this issue on kernel.org in the
meantime:

https://bugzilla.kernel.org/show_bug.cgi?id=198223


** Bug watch added: Linux Kernel Bug Tracker #198223
   https://bugzilla.kernel.org/show_bug.cgi?id=198223

** Tags added: kernel-bug-reported-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/1731163

Title:
  Trackpoint device not working by default on Thinkpad L570

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Installing Ubuntu 17.10 on a ThinkPad L570 (L470 should be the same in
  this regard) leaves the trackpoint as well as the trackpoint buttons
  in a non-working state. Most probably, it is not correctly detected on
  startup; dmesg shows

  kernel: [ 2.997182 ] input: AlpsPS/2 ALPS GlidePoint as
  /devices/platform/i8042/serio1/input/input6

  As far as I understand it, "GlidePoint" only refers to a touch pad
  without track point. All events coming from the track point are
  consequently actively discarded, seen in dmesg as

  kernel: [ 2279.323441 ] psmouse serio1: alps: Rejected trackstick
  packet from non DualPoint device

  Searching for this problem I found this kernel developer discussion
  which seems related:

  https://patchwork.kernel.org/patch/9941661/

  As suggested by one of the kernel developers there, I added
  "psmouse.proto=imps" as a kernel boot parameter. The touch pad and
  track point now show up in the system log as

  input: PS/2 Generic Mouse as
  /devices/platform/i8042/serio1/input/input6

  And it works well now, just as it should. I also noted that the touch
  pad became a lot more usable at the same time. Previously (with the
  default installation) it was lagging and could produce pseudo clicks
  at random.

  I am submitting this report here in order to help improve the hardware
  detection in Ubuntu / linux kernel.

  Ubuntu version: 17.10
  Kernel version: 4.13.0.16.17
  Default GNOME desktop, Wayland, etc, just as it comes in the default install
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dirichs 896 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-11-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 5986:111c Acer, Inc 
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20J8CTO1WW
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=f2a92db0-5f37-4d70-b878-a4ba4c80e890 ro quiet splash 
psmouse.proto=imps vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1XET43W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J8CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1XET43W(1.21):bd07/12/2017:svnLENOVO:pn20J8CTO1WW:pvrThinkPadL570:rvnLENOVO:rn20J8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L570
  dmi.product.name: 20J8CTO1WW
  dmi.product.version: ThinkPad L570
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1741080] Re: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped

2018-01-03 Thread Cristian Aravena Romero

** Bug watch added: Linux Kernel Bug Tracker #198291
   https://bugzilla.kernel.org/show_bug.cgi?id=198291

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=198291
   Importance: Unknown
   Status: Unknown

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

Title:
  cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped

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

Bug description:
  Hello,

  dmesg:
  [  141.782347] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped
  [  142.828101] usbcore: registered new interface driver usbserial
  [  142.828159] usbcore: registered new interface driver usbserial_generic
  [  142.828207] usbserial: USB Serial support registered for generic
  [  142.840302] usbcore: registered new interface driver option
  [  142.840350] usbserial: USB Serial support registered for GSM modem (1-port)
  [  146.863549] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.14.0-13-generic 4.14.0-13.15
  ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7
  Uname: Linux 4.14.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1740 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 13:13:02 2018
  InstallationDate: Installed on 2017-10-13 (82 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-13-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.14.0-13-generic N/A
   linux-backports-modules-4.14.0-13-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1740290] Re: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped

2018-01-03 Thread Cristian Aravena Romero

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

** No longer affects: linux

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

Title:
  cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 5519.779175] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped
  [ 5519.779186] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped
  [ 5519.779193] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped
  [ 5519.785793] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped
  [ 5519.785803] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped
  [ 5519.819250] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1655 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1655 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 15:30:53 2017
  InstallationDate: Installed on 2017-10-13 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

2018-01-03 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  ubuntu 17.00 kernel freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop hangs frequently, with a high cpu comsumption, don't react to 
Ctrl-Alt-whatever, only way to restart is hardware or fn-alt-print screen-B
  any other fn-alt-print screen combination doesn't works.
  I don't know how to trace what's wrong, or what component can be responsible.
  I have tried several X-servers, I have tried to disable hardware nvidia 
acceleration, etc. with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-22-generic 4.13.0-22.25
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rogelio2095 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Jan  3 13:37:36 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (244 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-22-generic N/A
   linux-backports-modules-4.13.0-22-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1738736] Re: ACPI error message flooding syslog

2018-01-03 Thread Alex Garel

FYI, still got it with "4.13.0-21-generic".

Sorry, but I still won't be able to test on the upstream kernel this
week…

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

Title:
  ACPI error message flooding syslog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This message :

  Dec 18 09:20:13 tignasse kernel: [   85.652805] ACPI Error: Needed type 
[Reference], found [Integer] 99eae08481f8 (20170531/exresop-103)
  Dec 18 09:20:13 tignasse kernel: [   85.652831] ACPI Exception: 
AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] 
(20170531/dswexec-461)
  Dec 18 09:20:13 tignasse kernel: [   85.652847] ACPI Error: Method 
parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE 
(20170531/psparse-550)

  Is flooding my syslog at a pace of on message every 200 ms !

  This is really annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   5166 F pulseaudio
   /dev/snd/controlC1:  alex   5166 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Dec 18 09:22:16 2017
  HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583
  InstallationDate: Installed on 2015-11-10 (768 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Intel Corporation Skylake Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-23 (24 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: RVP7
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: Skylake System
  dmi.product.name: Skylake Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1739765] Re: xt_TCPMSS buffer overflow bug

2018-01-03 Thread Seth Arnold

Use CVE-2017-18017.

Thanks

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18017

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

Title:
  xt_TCPMSS buffer overflow bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug was reported in LKML here: https://lkml.org/lkml/2017/4/2/13
  In few words - corrupted packet might be used to modify memory at router who 
has xt_TCPMSS used as iptables action.
  This is really nasty bug, and can be triggered remotely by malicious person 
on anything that usually use this iptables action (PPPoE/PPTP-enabled ISP or 
VPN provider, for example).
  This bug existed for several years, i guess.
  I waited for a while since April, as it's already pushed to stable, and 
probably all distributions have it updated, so now it's time to do bugreport, 
to make sure it is really fixed everywhere.
  Maybe worth to assign CVE for it?

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

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

[Kernel-packages] [Bug 1739765] Re: xt_TCPMSS buffer overflow bug

2018-01-03 Thread Denys Fedoryshchenko

Perfect! Thanks a lot, now i have big reason to ask some sysadmins and
vendors to upgrade their kernels.

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

Title:
  xt_TCPMSS buffer overflow bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug was reported in LKML here: https://lkml.org/lkml/2017/4/2/13
  In few words - corrupted packet might be used to modify memory at router who 
has xt_TCPMSS used as iptables action.
  This is really nasty bug, and can be triggered remotely by malicious person 
on anything that usually use this iptables action (PPPoE/PPTP-enabled ISP or 
VPN provider, for example).
  This bug existed for several years, i guess.
  I waited for a while since April, as it's already pushed to stable, and 
probably all distributions have it updated, so now it's time to do bugreport, 
to make sure it is really fixed everywhere.
  Maybe worth to assign CVE for it?

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

2018-01-03 Thread Steve Langasek

** Summary changed:

- openvswitch: kernel opps destroying interfaces on i386
+ openvswitch: kernel oops destroying interfaces on i386

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

Status in linux package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in openvswitch source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in openvswitch source package in Bionic:
  Confirmed

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1581799] Re: radeon driver hangs : nothing else that static effect on display

2018-01-03 Thread magowiz

Ok, thank you for the information, do I need to report here upstream bug
reference after I created bug report?

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   magowiz4930 F...m pulseaudio
   /dev/snd/pcmC0D0p:   magowiz4930 F...m pulseaudio
   /dev/snd/controlC0:  magowiz4930 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
  InstallationDate: Installed on 2012-01-03 (1615 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A55-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Leó Kolbeinsson

Re #446

Just for the record - also solved and also running Acer Aspire E3 -111 -
P60s with InsydeH20 BIOS.

--
You 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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Fix: The issue was fixed in Kernel Version 4.13.0-21. 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:

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'.

---

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:

---

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
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:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  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 Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  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
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  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 1697450] Re: Gnome Shell hangs at startup

2018-01-03 Thread Alberto Donato

@Daniel I can't really follow those steps exactly, as the machine hangs
as soon as either GDM or gnome-shell is started

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

Title:
  Gnome Shell hangs at startup

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-30 (71 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Tags:  artful wayland-session
  Uname: Linux 4.8.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1738773] Re: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno

2018-01-03 Thread Seth Forshee

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Amitkumar Karwar (amitkarwar)

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

Title:
  Connection issue in Bluetooth SPP mode between a Dell Edge Gateway
  3000 and an HC-05 BT module attached to Arduino Uno

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Connection issue in Bluetooth SPP mode between a Dell Edge
  Gateway 3000 and an HC-05 BT module attached to Arduino Uno

  Fix: Updated firmware from Redpine containing a fix for the issue.

  Regression Potential: Below stress tests are conducted to ensure there is no 
regression with updated firmware
  BT mouse + BT keyboard
  BT mouse + BLE keyboard
  BT keyboard + BLE mouse
  BLE keyboard + BLE mouse
  BT mouse or keyboard + Wifi connected
  BT mouse + BT keyboard + WiFi connected
  BLE mouse + BLE keyboard + WiFi Connected
  BT mouse + BLE keyboard + Wifi connected
  BLE mouse + BT keyboard + Wifi connected
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + Wifi Scan
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + BT inquiry + 
BLE scan
  BT file transfer from mobile + WiFi connected

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

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

[Kernel-packages] [Bug 1741103] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]

2018-01-03 Thread piero vitareti

Public bug reported:

starting system

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1027 F pulseaudio
  piero  1387 F pulseaudio
Date: Wed Jan  3 19:19:44 2018
Failure: oops
HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a
InstallationDate: Installed on 2018-01-03 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IwConfig:
 lono wireless extensions.
 
 enp0s15   no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903
dmi.board.name: P5N-MX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  starting system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1027 F pulseaudio
piero  1387 F pulseaudio
  Date: Wed Jan  3 19:19:44 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a
  InstallationDate: Installed on 2018-01-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp0s15   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903
  dmi.board.name: P5N-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list:

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

2018-01-03 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  starting system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1027 F pulseaudio
piero  1387 F pulseaudio
  Date: Wed Jan  3 19:19:44 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a
  InstallationDate: Installed on 2018-01-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp0s15   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903
  dmi.board.name: P5N-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Francesco

The problem linked to the bios has Just solved thank to your new
instructions (Acer Aspire es1-111m). Thank you guys!

--
You 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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Fix: The issue was fixed in Kernel Version 4.13.0-21. 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:

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'.

---

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:

---

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-01-03 Thread Brad

Kernel 4.14 is LTS (Long Term Support) for SIX years!... so maybe it
gets more dev attention than 4.15? dunno.  I did read there are some
related Touchpad fixes to be rolled into 4.16 and no doubt back ported
to 4.14.X

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1730904] Re: 17.10 freezes every hour ramdomly

2018-01-03 Thread Roger Tri

the problem persist after under new kernel:
Linux rogelio-K55A 4.14.11-041411-generic #201801022143 SMP Tue Jan 2 21:44:21 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  17.10 freezes every hour ramdomly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  on 17.04 I had frequent errors reported, now hangs all the computer,
  please some workaround or way back to 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rogelio1645 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 09:07:15 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (187 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago)
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Mika Westerberg

This particular bug cannot affect Dell XPS 13 9350 as it is based on
Skylake and the intel-spi driver does not even support it.

However, in order to boot Linux I think you need at least to switch the
SATA controller to AHCI mode as described in:

https://wiki.archlinux.org/index.php/Dell_XPS_13_(9350)

--
You 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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Fix: The issue was fixed in Kernel Version 4.13.0-21. 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:

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'.

---

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:

---

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-01-03 Thread Ryan Burke

That's fair enough. I'll be sure to try 4.14.3 as well as the newer .11
variant.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1738791] Re: linux: 4.13.0-22.25 -proposed tracker

2018-01-03 Thread Steve Beattie

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

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

Title:
  linux: 4.13.0-22.25 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1738792,1738793,1738794,1738796,1738797
  derivatives: 1738798
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Paul Hawkins

The second kernel from step 8 of the new description has solved the
problem on my Lenovo S20-30 touch. Thanks for fixing.

--
You 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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Fix: The issue was fixed in Kernel Version 4.13.0-21. 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:

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'.

---

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:

---

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

[Kernel-packages] [Bug 1737918] Re: linux-aws: 4.4.0-1007.7 -proposed tracker

2018-01-03 Thread Steve Beattie

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

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

Title:
  linux-aws: 4.4.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

< 1 2

101 - 147 of 147 matches

Mail list logo