[Kernel-packages] [Bug 1694225] ProcInterrupts.txt

[Rashi]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019127/+files/ProcInterrupts.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin 

[Kernel-packages] [Bug 1694225] UdevDb.txt

[Rashi]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1694225/+attachment/5019131/+files/UdevDb.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  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 

[Kernel-packages] [Bug 1694225] PulseList.txt

[Rashi]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019129/+files/PulseList.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1694225] RfKill.txt

[Rashi]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1694225/+attachment/5019130/+files/RfKill.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  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 

[Kernel-packages] [Bug 1694225] Lspci.txt

[Rashi]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1694225/+attachment/5019123/+files/Lspci.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  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
 

[Kernel-packages] [Bug 1694225] ProcModules.txt

[Rashi]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019128/+files/ProcModules.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

[Fred Kimmy]

Starting Hostname Service...

Ubuntu 17.10 ubuntu ttyAMA0

[   68.535458] Internal error: Attempting to execute userspace memory: 8604 
[#1] SMP
[   68.543288] Modules linked in: nls_iso8859_1 joydev input_leds shpchp 
ipmi_ssif ipmi_si ipmi_devintf ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ppdev lp parport 
ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
ses enclosure hid_generic usbhid hid marvell hibmc_drm ttm aes_ce_blk 
drm_kms_helper aes_ce_cipher crc32_ce syscopyarea crct10dif_ce sysfillrect 
sysimgblt ghash_ce fb_sys_fops sha2_ce sha1_ce drm hisi_sas_v2_hw hisi_sas_main 
megaraid_sas libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv 
hns_mdio hnae aes_neon_bs aes_neon_blk crypto_simd cryptd
[   68.607986] CPU: 39 PID: 2746 Comm: llvmpipe-1 Not tainted 4.13.0-16-generic 
#19-Ubuntu
[   68.615975] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.29 07/17/2017
[   68.622576] task: 8013b88ecb00 task.stack: 8013b8dc4000
[   68.628485] PC is at 0x0
[   68.631026] LR is at ttm_bo_vm_fault+0x218/0x520 [ttm]
[   68.636151] pc : [<>] lr : [] pstate: 
00400145
[   68.643533] sp : 8013b8dc7ac0
[   68.646834] x29: 8013b8dc7ac0 x28:  
[   68.652134] x27: 0cb63000 x26:  
[   68.657434] x25: 0208 x24:  
[   68.662734] x23: 8013dd0e5240 x22: 8013dd0e50b0 
[   68.668034] x21: 0cb53000 x20: 8013b324d518 
[   68.67] x19: 093b8c08 x18:  
[   68.678633] x17:  x16:  
[   68.683933] x15:  x14:  
[   68.689232] x13:  x12: 8013ddcadc00 
[   68.694531] x11:  x10: 8013e5f62900 
[   68.699831] x9 : 001000eb x8 : 01dd85b8 
[   68.705130] x7 :  x6 : 8013b8dc7bf8 
[   68.710430] x5 :  x4 : 0008 
[   68.715730] x3 : 0cb53000 x2 :  
[   68.721029] x1 :  x0 : 8013ddcadc00 
[   68.726329] Process llvmpipe-1 (pid: 2746, stack limit = 0x8013b8dc4000)
[   68.733364] Stack: (0x8013b8dc7ac0 to 0x8013b8dc8000)
[   68.739098] 7ac0: 8013b8dc7c00 082585a4 8013b8dc7cc0 
0d73
[   68.746914] 7ae0: 8013b324d518 08e2 8013b958bfe0 
8013b888a580
[   68.754731] 7b00: 8013b324d518  8013b888a5e8 
0003
[   68.762547] 7b20: 8013ddcadc00 8013ddcadc00 0cb53000 
0cd5b000
[   68.770363] 7b40: 8013b35824b0 8013b3582ed8 8013b35824d0 

[   68.778180] 7b60:  00b53000 8013b888a580 
00680f4f
[   68.785996] 7b80: 140440fb 8013bd2908f0  

[   68.793813] 7ba0: 001002f2 8013b324d590 8013b324d590 

[   68.801629] 7bc0: 01dd85b8 001000eb 8013e5f62900 

[   68.809445] 7be0: 8013ddcadc00   
00040d00
[   68.817262] 7c00: 8013b8dc7c30 0825ca7c 8013b8dc7cc0 
0d73
[   68.825078] 7c20:   8013b8dc7c70 
0825e628
[   68.832894] 7c40: 0065 093b8000 8013b324d518 
0825e52c
[   68.840710] 7c60: 0065 08165b38 8013b8dc7d30 
0825eaac
[   68.848527] 7c80: 0054 8013b324d518 0cb53000 
0040
[   68.856343] 7ca0: 8013b888a580 0054  

[   68.864160] 7cc0: 8013b324d518 014200ca0054 001000eb 
0cb53000
[   68.871976] 7ce0: 8013b8625328 8013b958bfe0  

[   68.879792] 7d00:    

[   68.887609] 7d20:  00040d00 8013b8dc7d60 
08a80e10
[   68.895425] 7d40: 8013b8dc7ec0 8013b88ecb00 0cb53000 
9206
[   68.903241] 7d60: 8013b8dc7dc0 08a81054 0cb53000 
9206
[   68.911058] 7d80: 8013b8dc7ec0 8013b8dc7ec0 08a97238 
0024
[   68.918874] 7da0: 9206 0cb53000  
8013b88ecb00
[   68.926690] 7dc0: 8013b8dc7df0 08081244 093b8000 
9206
[   68.934507] 7de0: 0cb53000 00040d00  
08083508
[   68.942323] 7e00:  8017f2d1b000  
0d939338
[   68.950139] 7e20: 2000 0200 8017fbce8090 
fbcec080
[   68.957955] 7e40:  08083930  
8017f2d1b000
[   68.965771] 

[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

[Fred Kimmy]

I use this following 17.10 ISO to test this xwindow for D05 board.

http://cdimage.ubuntu.com/releases/17.10/release/ubuntu-17.10-server-
arm64.iso

Then set this next step:
 sudo apt install ubuntu-desktop
 sudo reboot.

this desktop will crash.

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

Title:
  hibmc driver does not include "pci:" prefix in bus ID

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Incomplete

Bug description:
  SRU Justification

  [Impact]
  On the HiSilicon D05 (arm64) board, X crashes when started. [0]

  [Fix]
  The crash is attributable to the bus ID that the hibmc driver reports for the 
hibmc graphics card on the board. In particular, the bus id is missing the 
"pci:" prefix that most other cards provide: [1]
  - The busid reported on the arm64 system is "0007:a1:00.0"
  - The busid reported on a amd64 system is "pci::00:02.0"

  X tests for this prefix. A missing prefix for PCI cards leads to an
  Xorg crash.

  Fix this by using the set_pci_busid function from the DRM core.

  [Testcase]
  Successfully tested on a D05 board. [2]

  [Regression Potential]
  Changes are limited to the hibmc driver, so any regression should also be 
limited to that driver.

  [Notes]
  I submitted the patch upstream. However, upstream is refactoring the drm 
core, and set_busid is going away. That does fix this issue but the regression 
potential of the refactor is enormous, so this seems like the wiser approach. 
[3]

  [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991
  [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16
  [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29
  [3]: https://www.spinics.net/lists/dri-devel/msg143831.html

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

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

[Kernel-packages] [Bug 1694225] Lsusb.txt

[Rashi]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1694225/+attachment/5019124/+files/Lsusb.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  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
 

[Kernel-packages] [Bug 1694225] ProcCpuinfoMinimal.txt

[Rashi]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019126/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip 

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

[Simon Oberhammer]

i have the same issue. 4.13.0-17 always this oops on boot. i had
4.10.0-32 still on disk and this is what i'm using for now.

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1694225] WifiSyslog.txt

[Rashi]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019132/+files/WifiSyslog.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB

[Po-Hsu Lin]

Hello Bastian,
how do you install the -proposed kernel from Xenial/Artful?
Can you paste the kernel version here as well?

Thanks

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

Title:
  Touchpad not detected - Lenovo ideapad 320-15IKB

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Description:  Ubuntu 17.04
  Release:  17.04

  Basically the same bug as described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852

  I'm using a Lenovo ideapad 320-15IKB, though.

  I also tried the latest mainline kernel (4.13.7) which didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradanis   1747 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct 15 14:23:54 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d
  InstallationDate: Installed on 2017-10-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 81BG
  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=/vmlinuz-4.10.0-19-generic 
root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JCN14WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 81BG
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1694225] JournalErrors.txt

[Rashi]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019122/+files/JournalErrors.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1694225] ProcCpuinfo.txt

[Rashi]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019125/+files/ProcCpuinfo.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1694225] CRDA.txt

[Rashi]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1694225/+attachment/5019119/+files/CRDA.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  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
  

[Kernel-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

[Rashi]

apport information

** Tags added: apport-collected artful

** Description changed:

  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".
  
  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint (red
  pointing stick)'s left button.
  
  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.
  
  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.
  
  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use your
  left hand's index and middle finger for this.
  
  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it) on
  the desktop area, then immediately move the cursor with the pointing
  stick.
  
  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.
  
  
  The evtest log on the trackpoint:
  
  $evtest /dev/input/event15
  
  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 
  
  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:
  
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  
  But if the click lock is triggered, you would only see value 1:
  
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1
  
  I am guessing "value 0" means release the button. So when click lock is
  happening, the button left is not released at all, thus it's producing
  "hold the button" effect.
  
  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)
  
- Also, the issue doesn't occur on older thinkpad models which doesn't use
- same clickpad type touchpad, e.g. T430 or X230. For newer thinkpad
- models (e.g. T460, X260, etc) which uses same clickpad design, same
- issue might exists too (need confirmation though).
+ Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
+  /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
+ CasperVersion: 1.387
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 17.10
+ LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
+ MachineType: LENOVO 20BX001LUS
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
+ 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:  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: 03/16/2017
+ dmi.bios.vendor: LENOVO
+ 

[Kernel-packages] [Bug 1694225] CurrentDmesg.txt

[Rashi]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019120/+files/CurrentDmesg.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1694225] IwConfig.txt

[Rashi]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1694225/+attachment/5019121/+files/IwConfig.txt

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't use same 
clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. 
T460, X260, etc) which uses same clickpad design, same issue might exists too 
(need confirmation though).
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  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:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1736670] [NEW] Dependency conflicts with proposed 4.13.0.19 UEFI-aware kernel

[Pierre Etienne SCHNEIDER]

Public bug reported:

The new version 4.13.0.19 of Linux-signed-image and linux-image-generic
seem to have a sependency conflict/version mismatch on UEFI systems,
which causes linux-signed-image to try to self-uninstall.

Seems unsafe, because this would take away the Ubuntu UEFI signing
certificate from the boot sector, potentially rendering the system
unbootable, popping error messages or creating a security breach.

Upon updating, the new kernel version should update / replace the UEFI
keys in place, and no stuff should be deleted unless explicitly asked
for.


**technical data*

Ubuntu 17.10 with proposed updates enabled, current 05/12/17.


linux-signed-generic:
  Installé : 4.13.0.18.19
  Candidat : 4.13.0.19.20
 Table de version :
 4.13.0.19.20 500
500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages
 *** 4.13.0.18.19 100
100 /var/lib/dpkg/status
 4.13.0.17.18 500
500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful-security/main amd64 Packages
 4.13.0.16.17 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

Have locked the version of kernel to 4.13.0.18 in Synaptic for now to
prevent any auto-upgrading from breaking stuff.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-signed-generic 4.13.0.18.19
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pierre 1185 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Dec  6 08:42:19 2017
InstallationDate: Installed on 2017-11-29 (6 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 13d3:3408 IMC Networks 
 Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X200MA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic.efi.signed 
root=UUID=72987c52-a0fd-4447-a0ab-2ce45a285177 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-18-generic N/A
 linux-backports-modules-4.13.0-18-generic  N/A
 linux-firmware 1.169.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.506
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
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.:bvrX200MA.506:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X200MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug artful

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

Title:
  Dependency conflicts with proposed 4.13.0.19 UEFI-aware kernel

Status in linux package in Ubuntu:
  New

Bug description:
  The new version 4.13.0.19 of Linux-signed-image and linux-image-
  generic seem to have a sependency conflict/version mismatch on UEFI
  systems, which causes linux-signed-image to try to self-uninstall.

  Seems unsafe, because this would take away the Ubuntu UEFI signing
  certificate from the boot sector, potentially rendering the system
  unbootable, popping error messages or creating a security breach.

  Upon updating, the new kernel version should update / replace the UEFI
  keys in place, and no stuff should be deleted unless explicitly asked
  for.

  
  **technical data*

  Ubuntu 17.10 with proposed updates enabled, current 05/12/17.

  
  linux-signed-generic:
Installé : 4.13.0.18.19
Candidat : 4.13.0.19.20
   Table de version :
   4.13.0.19.20 500
  500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
Packages
   *** 4.13.0.18.19 100
  100 /var/lib/dpkg/status
   4.13.0.17.18 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Have locked the version of kernel to 4.13.0.18 in Synaptic for now to
  prevent any auto-upgrading 

[Kernel-packages] [Bug 1553264] Re: [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6

[P]

I was using 4.13 and now installed 4.14.0 (I guess that includes the
code from 4.12-rc2). The problem persists:

[0.00] Linux version 4.14.0-041400-generic (kernel@kathleen) (gcc 
version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #201711122031 SMP Sun Nov 12 20:32:29 
UTC 2017
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-041400-generic 
root=UUID=c07aafe2-3841-467a-becb-e8173c55fac4 ro quiet splash vt.handoff=7
...
[  276.637070] psmouse serio1: elantech: PS/2 packet [44 80 80 36 00 00]
[  277.184911] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.193353] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.201636] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.210288] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.218474] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.218476] psmouse serio1: issuing reconnect request
[  277.628452] psmouse serio1: Failed to enable mouse on isa0060/serio1

It can be triggered reproducibly by operating the trackpoint or mouse
buttons while moving a finger on the touchpad.

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

Title:
  [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at
  isa0060/serio1/input0 lost sync at byte 6

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a lenovo 260 yoga my dmesg gets flooded with these messages and the system 
finally becomes unresponsive.
  Also tried with the current upstream kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-9-generic 4.4.0-9.24 [modified: 
boot/vmlinuz-4.4.0-9-generic]
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dougie 1564 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar  5 01:31:41 2016
  HibernationDevice: RESUME=UUID=cd3e1470-ad53-49aa-b78e-654c1e7b3969
  InstallationDate: Installed on 2016-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 20FDCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic.efi.signed 
root=UUID=9e9aeb12-fc63-4e7d-af3c-a9bbf6614a4e ro quiet splash 
intel_pstate=no_hwp i915.preliminary_hw_support=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9-generic N/A
   linux-backports-modules-4.4.0-9-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET55W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FDCTO1WW
  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:bvrN1GET55W(1.34):bd02/04/2016:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FDCTO1WW
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1736666] [NEW] package linux-firmware 1.169.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück

[Andreas Cichy]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-firmware 1.169.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
AptOrdering:
 linux-firmware:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Dec  6 06:05:14 2017
Dependencies:
 
Df:
 
Dmesg:
 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
InstallationDate: Installed on 2017-04-09 (240 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: linux-firmware
Title: package linux-firmware 1.169.1 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 2 zurück
UpgradeStatus: Upgraded to artful on 2017-10-23 (43 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package linux-firmware 1.169.1 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 2 zurück

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  AptOrdering:
   linux-firmware:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Dec  6 06:05:14 2017
  Dependencies:
   
  Df:
   
  Dmesg:
   
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
  InstallationDate: Installed on 2017-04-09 (240 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.169.1 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 2 zurück
  UpgradeStatus: Upgraded to artful on 2017-10-23 (43 days ago)

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

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

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[AndrewJessop]

I have the same problem.

XUbuntu 17.04 with kernel 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6
10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Dec  6 18:06:47 HOSTNAME kernel: [205433.429560]
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C FIFO
underrun

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

[Zakatell Kanda]

Hello,

This bug has been fix mainline,
- https://bugzilla.kernel.org/show_bug.cgi?id=197147
- https://bugzilla.kernel.org/show_bug.cgi?id=197807

We just need the Ubuntu team to upgrade to the latest linux-firmware.

Cheers!


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

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

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

[dino99]

That issue was a transitional problem; it is gone now on my system since
a while.

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

Title:
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic:
  No such file or directory

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please affect that report to the real package; i've chosen apt by
  default as i've no idea about the faulty one.

  Doing some daily upgrades as usual, and have seen that curious error
  while setting 'initramfs':

  Setting up linux-firmware (1.164) ...
  update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
  update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
  WARNING: missing /lib/modules/4.8.0-25-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
  WARNING: missing /lib/modules/4.8.0-0-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

  That ZZ installation indeed only has 4.10 kernels installed, and is
  often checked for cleaning (autoremove/bleachbit). Packages are always
  purged when removed.

  So i wonder why and which process/script has left a crappy /boot/ list
  of initrd.img-4.8* to produce the errors above.

  oem@u64:~$ ls -la /boot/
  total 142448
  drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
  drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
  -rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
  -rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
  -rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
  -rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
  drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
  drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
  -rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
  -rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
  -rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
  -rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
  -rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
  -rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
  -rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
  -rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
  -rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
  -rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
  -rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 21 06:28:04 2017
  Dependencies:

  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320

[Anthony Wong]

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

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

Title:
  Touchpad stops working after a few seconds in Lenovo ideapad 320

Status in linux package in Ubuntu:
  Triaged

Bug description:
  === SRU Justifications ===

  [Impact]
  Touchpad freezes after a brief usage.

  [Fix]
  Quote from the commit log:
  "The stale cached value written at the final stage undoes the masking.
  Fix this by re-reading the register before clearing the interrupt.

  I also spotted that the interrupt-clearing code can race against
  amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there.
  Presumably this race was leading to the loss of interrupts."

  [Test Case]
  Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and
  a new Dell Inspiron.

  [Regression Potential]
  Low. It limits to AMD laptops

  === Original Bug Report ===

  I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad
  stops working a few seconds after I log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  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-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rebeca 1440 F pulseaudio
   /dev/snd/controlC0:  rebeca 1440 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 20:03:41 2017
  InstallationDate: Installed on 2017-09-22 (53 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  MachineType: LENOVO 80XS
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f 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 bionic on 2017-11-14 (0 days ago)
  dmi.bios.date: 05/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.version: Lenovo ideapad 320-15ABR
  dmi.sys.vendor: LENOVO

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

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

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

[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/1736651

Title:
  Radeon error, kernel says No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A day ago i have edited ~/.config/pulse/client.conf with the following
  change:

  ; autospawn = yes

  to

  autospawn = no

  Today i face Xorg error with the following message:
  [drm] VGACON disable radeon kernel modesetting.
  [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

  If this change caused this error, please advise a better way to solve
  another bug "pulseaudio : Daemon already running" if the
  ~/.config/pulse/client.conf should remain as "; autospawn = yes".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Dec  6 12:40:24 2017
  HibernationDevice: RESUME=UUID=c99260e9-9788-4bdd-89b4-89ed5f922889
  InstallationDate: Installed on 2017-02-12 (296 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2768CJ6
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=a2edc425-72a2-40f7-be42-d78deda20ba5 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 2768CJ6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2768CJ6:pvrThinkPadT400:rvnLENOVO:rn2768CJ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2768CJ6
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

[Serhiy Zahoriya]

In my case it's also old files in /var/lib/initramfs-tools and that
looks like another manifestation of #1713004

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

Title:
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic:
  No such file or directory

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please affect that report to the real package; i've chosen apt by
  default as i've no idea about the faulty one.

  Doing some daily upgrades as usual, and have seen that curious error
  while setting 'initramfs':

  Setting up linux-firmware (1.164) ...
  update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
  update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
  WARNING: missing /lib/modules/4.8.0-25-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
  WARNING: missing /lib/modules/4.8.0-0-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

  That ZZ installation indeed only has 4.10 kernels installed, and is
  often checked for cleaning (autoremove/bleachbit). Packages are always
  purged when removed.

  So i wonder why and which process/script has left a crappy /boot/ list
  of initrd.img-4.8* to produce the errors above.

  oem@u64:~$ ls -la /boot/
  total 142448
  drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
  drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
  -rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
  -rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
  -rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
  -rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
  drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
  drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
  -rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
  -rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
  -rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
  -rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
  -rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
  -rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
  -rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
  -rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
  -rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
  -rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
  -rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 21 06:28:04 2017
  Dependencies:

  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1736651] [NEW] Radeon error, kernel says No UMS support in radeon module

[Yovan Zhuo Jiawan]

Public bug reported:

A day ago i have edited ~/.config/pulse/client.conf with the following
change:

; autospawn = yes

to

autospawn = no

Today i face Xorg error with the following message:
[drm] VGACON disable radeon kernel modesetting.
[drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

If this change caused this error, please advise a better way to solve
another bug "pulseaudio : Daemon already running" if the
~/.config/pulse/client.conf should remain as "; autospawn = yes".

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-101-generic 4.4.0-101.124
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: Unity
Date: Wed Dec  6 12:40:24 2017
HibernationDevice: RESUME=UUID=c99260e9-9788-4bdd-89b4-89ed5f922889
InstallationDate: Installed on 2017-02-12 (296 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 2768CJ6
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=a2edc425-72a2-40f7-be42-d78deda20ba5 ro recovery nomodeset
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-101-generic N/A
 linux-backports-modules-4.4.0-101-generic  N/A
 linux-firmware 1.157.14
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET94WW (3.24 )
dmi.board.name: 2768CJ6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2768CJ6:pvrThinkPadT400:rvnLENOVO:rn2768CJ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2768CJ6
dmi.product.version: ThinkPad T400
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Radeon error, kernel says No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A day ago i have edited ~/.config/pulse/client.conf with the following
  change:

  ; autospawn = yes

  to

  autospawn = no

  Today i face Xorg error with the following message:
  [drm] VGACON disable radeon kernel modesetting.
  [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

  If this change caused this error, please advise a better way to solve
  another bug "pulseaudio : Daemon already running" if the
  ~/.config/pulse/client.conf should remain as "; autospawn = yes".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Dec  6 12:40:24 2017
  HibernationDevice: RESUME=UUID=c99260e9-9788-4bdd-89b4-89ed5f922889
  InstallationDate: Installed on 2017-02-12 (296 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2768CJ6
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=a2edc425-72a2-40f7-be42-d78deda20ba5 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 2768CJ6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  

[Kernel-packages] [Bug 1736195] Re: linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1736194
  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/1736195/+subscriptions

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

[Kernel-packages] [Bug 1736194] Re: linux: 3.13.0-137.186 -proposed tracker

[Po-Hsu Lin]

All bugs tagged with verification-needed were marked as verification
done.

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 3.13.0-137.186 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: 1736195
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Monday, 04. December 2017 19:30 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Mike R]

Well I've hit 48 hours uptime since booting to my custom build kernel
(Linux ganymede 4.13.0-17-generic #20+ryzen SMP Sun Dec 3 20:18:51 MST
2017 x86_64 x86_64 x86_64 GNU/Linux) with rcu_nocbs=0-15 in my boot
command and disabled ASLR.  That's about double my previous uptime
record, I'll report back again if I hit 1 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/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu 

[Kernel-packages] [Bug 1730762] Re: 17.10 - suspend/resume failure

[Kai-Heng Feng]

Yes,

Please follow instructions in [1], ask see if all pm_test work.
[1] 
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

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

Title:
  17.10 - suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a failure in the resume process after the suspend.
  When I try to resume the system start, but the screen stay black while
  the disk seem be really busy.

  The only way to exit from this status is unplug the system before
  restart it.

  Let me know how to collect additional info (if necessary).

  Alessandro-

  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/controlC1:  alessandro   1948 F pulseaudio
   /dev/snd/controlC0:  alessandro   1948 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 22:59:45 2017
  HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
  InstallationDate: Installed on 2016-07-09 (486 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s5no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell NEC IMEDIA 5204
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Kernel-packages] [Bug 1736639] Re: Intel 9260/9462/9560 can't connect to 5GHz AP

[AceLan Kao]

The 2 patches can be found here, they have CC'ed stable, so they will be
in artful kernel someday.

git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git

Author: Sara Sharon 
Date:   Mon Feb 8 23:30:47 2016 +0200

iwlwifi: mvm: mark MIC stripped MPDUs

When RADA is active, the hardware decrypts the packets and strips off
the MIC as it is useless after decryption. Indicate that to mac80211.

Cc: sta...@vger.kernel.org # 4.13+
[this is needed for the 9000-series HW to work properly]
Signed-off-by: Sara Sharon 
Signed-off-by: Luca Coelho 

commit 9d0fc5a50a0548f8e5d61243e5e5f26d5c405aef
Author: David Spinadel 
Date:   Mon Nov 21 17:01:25 2016 +0200

iwlwifi: mvm: enable RX offloading with TKIP and WEP

Set the flag that indicates that ICV was stripped on if
this option was enabled in the HW.

Cc: sta...@vger.kernel.org # 4.13+
[this is needed for the 9000-series HW to work properly]
Signed-off-by: David Spinadel 
Signed-off-by: Luca Coelho 

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

Title:
  Intel 9260/9462/9560 can't connect to 5GHz AP

Status in linux package in Ubuntu:
  In Progress

Bug description:
  With 1009 oem(v4.13) kernel and latest linux-firmware[1], it connect to 
2.4GHz APs without any issues.
  But it fails to connect 5GHz APs.

  It stucks when I select a 5GHz network AP, and after timeout it
  connects to another configured 2.4GHz AP.
  [ 512.404139] wlp0s20f3: authenticate with 2c:36:f8:fa:ec:00
  [ 512.410781] wlp0s20f3: send auth to 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.449561] wlp0s20f3: authenticated
  [ 512.450625] wlp0s20f3: associate with 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.452010] wlp0s20f3: RX AssocResp from 2c:36:f8:fa:ec:00
  (capab=0x111 status=0 aid=8)
  [ 512.454501] wlp0s20f3: associated
  [ 512.542439] wlp0s20f3: Limiting TX power to 27 (30 - 3) dBm as
  advertised by 2c:36:f8:fa:ec:00
  [ 557.685247] wlp0s20f3: deauthenticating from 2c:36:f8:fa:ec:00 by
  local choice (Reason: 3=DEAUTH_LEAVING)
  [ 557.695875] wlp0s20f3: failed to remove key (1, ff:ff:ff:ff:ff:ff)
  from hardware (-22)

  1. c4276b6 (tag: refs/tags/iwlwifi-fw-2017-11-03) iwlwifi: add
  firmware version 33 for new 9000 series

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

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

[Kernel-packages] [Bug 1638788] Re: [MacBookAir5, 2] Resumes immediately after suspend

[Kai-Heng Feng]

Sergio,

Do you also use MBA5,2?
If not, please file another bug.

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

Title:
  [MacBookAir5,2] Resumes immediately after suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  with default settings the laptop will immediately resume after sending
  to sleep (regardless of by closing the LID or though the menu option
  "suspend")

  the workaround is disabling the LID ACPI action by running:

  echo LID0 >/proc/acpi/wakeup

  this will fix the problem. obviously however just simply opening the
  lid won't wake the laptop anymore. so one has to manually press the
  power button.

  (I used ubuntu-bug linux, so hopefully all info should be attached)
  I'm running out of the box, up2date yakkety. without any external
  repos or custom compiled applications

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-26-generic 4.8.0-26.28
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toby   2327 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 21:49:50 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ba2577eb-f563-46c3-adb9-47967c8c5851
  InstallationDate: Installed on 2016-10-17 (16 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. MacBookAir5,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=add8c949-ae19-4310-aede-4a9007ea7514 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B04.1509111654
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B04.1509111654:bd09/11/2015:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.name: MacBookAir5,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1736639] [NEW] Intel 9260/9462/9560 can't connect to 5GHz AP

[AceLan Kao]

Public bug reported:

With 1009 oem(v4.13) kernel and latest linux-firmware[1], it connect to 2.4GHz 
APs without any issues.
But it fails to connect 5GHz APs.

It stucks when I select a 5GHz network AP, and after timeout it
connects to another configured 2.4GHz AP.
[ 512.404139] wlp0s20f3: authenticate with 2c:36:f8:fa:ec:00
[ 512.410781] wlp0s20f3: send auth to 2c:36:f8:fa:ec:00 (try 1/3)
[ 512.449561] wlp0s20f3: authenticated
[ 512.450625] wlp0s20f3: associate with 2c:36:f8:fa:ec:00 (try 1/3)
[ 512.452010] wlp0s20f3: RX AssocResp from 2c:36:f8:fa:ec:00
(capab=0x111 status=0 aid=8)
[ 512.454501] wlp0s20f3: associated
[ 512.542439] wlp0s20f3: Limiting TX power to 27 (30 - 3) dBm as
advertised by 2c:36:f8:fa:ec:00
[ 557.685247] wlp0s20f3: deauthenticating from 2c:36:f8:fa:ec:00 by
local choice (Reason: 3=DEAUTH_LEAVING)
[ 557.695875] wlp0s20f3: failed to remove key (1, ff:ff:ff:ff:ff:ff)
from hardware (-22)

1. c4276b6 (tag: refs/tags/iwlwifi-fw-2017-11-03) iwlwifi: add firmware
version 33 for new 9000 series

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

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

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

Title:
  Intel 9260/9462/9560 can't connect to 5GHz AP

Status in linux package in Ubuntu:
  In Progress

Bug description:
  With 1009 oem(v4.13) kernel and latest linux-firmware[1], it connect to 
2.4GHz APs without any issues.
  But it fails to connect 5GHz APs.

  It stucks when I select a 5GHz network AP, and after timeout it
  connects to another configured 2.4GHz AP.
  [ 512.404139] wlp0s20f3: authenticate with 2c:36:f8:fa:ec:00
  [ 512.410781] wlp0s20f3: send auth to 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.449561] wlp0s20f3: authenticated
  [ 512.450625] wlp0s20f3: associate with 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.452010] wlp0s20f3: RX AssocResp from 2c:36:f8:fa:ec:00
  (capab=0x111 status=0 aid=8)
  [ 512.454501] wlp0s20f3: associated
  [ 512.542439] wlp0s20f3: Limiting TX power to 27 (30 - 3) dBm as
  advertised by 2c:36:f8:fa:ec:00
  [ 557.685247] wlp0s20f3: deauthenticating from 2c:36:f8:fa:ec:00 by
  local choice (Reason: 3=DEAUTH_LEAVING)
  [ 557.695875] wlp0s20f3: failed to remove key (1, ff:ff:ff:ff:ff:ff)
  from hardware (-22)

  1. c4276b6 (tag: refs/tags/iwlwifi-fw-2017-11-03) iwlwifi: add
  firmware version 33 for new 9000 series

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

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

[Kernel-packages] [Bug 1736639] Re: Intel 9260/9462/9560 can't connect to 5GHz AP

[AceLan Kao]

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

>From developer, the below 2 patches fix the 5GHz network issue.
https://patchwork.kernel.org/patch/10088929/
https://patchwork.kernel.org/patch/10088939/

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

Title:
  Intel 9260/9462/9560 can't connect to 5GHz AP

Status in linux package in Ubuntu:
  In Progress

Bug description:
  With 1009 oem(v4.13) kernel and latest linux-firmware[1], it connect to 
2.4GHz APs without any issues.
  But it fails to connect 5GHz APs.

  It stucks when I select a 5GHz network AP, and after timeout it
  connects to another configured 2.4GHz AP.
  [ 512.404139] wlp0s20f3: authenticate with 2c:36:f8:fa:ec:00
  [ 512.410781] wlp0s20f3: send auth to 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.449561] wlp0s20f3: authenticated
  [ 512.450625] wlp0s20f3: associate with 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.452010] wlp0s20f3: RX AssocResp from 2c:36:f8:fa:ec:00
  (capab=0x111 status=0 aid=8)
  [ 512.454501] wlp0s20f3: associated
  [ 512.542439] wlp0s20f3: Limiting TX power to 27 (30 - 3) dBm as
  advertised by 2c:36:f8:fa:ec:00
  [ 557.685247] wlp0s20f3: deauthenticating from 2c:36:f8:fa:ec:00 by
  local choice (Reason: 3=DEAUTH_LEAVING)
  [ 557.695875] wlp0s20f3: failed to remove key (1, ff:ff:ff:ff:ff:ff)
  from hardware (-22)

  1. c4276b6 (tag: refs/tags/iwlwifi-fw-2017-11-03) iwlwifi: add
  firmware version 33 for new 9000 series

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

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

[Kernel-packages] [Bug 405525] ❤yahoo this is so lovely

[heinrich]

Hi friend!

There is  something really lovely and I thought you may enjoy it too,
take a look
http://www.epoolstroi.ru/atqgx.php?UE80MDU1MjVAYnVncy5sYXVuY2hwYWQubmV0

Best Wishes, Heinrich

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

Title:
  [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume
  failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  Under 8.10 suspend worked pretty much flawlessly. Installed Karmic as
  9.04 my sound card would not work for some reason. may end up going
  back to 8.10 as My vid card is not supported anymore by ATI after that
  version. but that is not here nor there. tried to wake up my laptop
  like normal. system stayed at black screen. backlight sis not come on.
  I know this is alpha and I am not mad but I am reporting this so the
  developers know it. I have no idea what caused the problem but
  hopefully the bug catcher included stuff to help trace it. If not
  please delete this bug as I have no other Idea what could have caused
  it.

  Thanks for making a great product. I have used Ubuntu since 6.06 and
  have watched it get better and better every release (with exception to
  9.04) ;)

  thanks again guys.

  ProblemType: KernelOops
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  Architecture: i386
  Date: Mon Jul 27 17:10:03 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=3a408910-86e2-46ec-a784-90545d8f3f2c
  InterpreterPath: /usr/bin/python2.6
  MachineType: Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)
  Package: linux-image-2.6.31-4-generic 2.6.31-4.22
  ProcCmdLine: root=UUID=fe6d390e-5c59-40db-98f8-09dbdbd0b864 ro vga=792
  ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
  ProcEnviron: PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
  RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A
  SourcePackage: linux
  Tags: resume suspend
  Title: [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume 
failure
  Uname: Linux 2.6.31-4-generic i686
  UserGroups:
   
  dmi.bios.date: 02/24/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.24
  dmi.board.name: 3096
  dmi.board.vendor: Quanta
  dmi.board.version: 47.0E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.24:bd02/24/2006:svnHewlett-Packard:pnHPPavilionze2000(EC205UA#ABA):pvrRev1:rvnQuanta:rn3096:rvr47.0E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion ze2000 (EC205UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1732894] Re: CPU call trace on AMD Raven Ridge after S3

[Zhang Junwei]

Hi all,

Verified with hwe-edge-4.13.0-18 and hwe-edge-4.13.0-19.
Both of them fix the CPU(mce) calltrace during S3.

Jerry

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

Title:
  CPU call trace on AMD Raven Ridge after S3

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Dmesg shows a call trace after S3 cycle.

  This has been fixed in v4.14-rc1 with

  commit 9662d43f523dfc0dc242ec29c2921c43898d6ae5
  Author: Yazen Ghannam 
  Date:   Mon Jul 24 12:12:28 2017 +0200

  x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  Current SMCA implementations have the same banks on each CPU with the
  non-core banks only visible to a "master thread" on each die. Practically,
  this means the smca_banks array, which describes the banks, only needs to
  be populated once by a single master thread.
  
  CPU 0 seemed like a good candidate to do the populating. However, it's
  possible that CPU 0 is not enabled in which case the smca_banks array 
won't
  be populated.
  
  Rather than try to figure out another master thread to do the populating,
  we should just allow any CPU to populate the array.
  
  Drop the CPU 0 check and return early if the bank was already initialized.
  Also, drop the WARNing about an already initialized bank, since this will
  be a common, expected occurrence.
  
  The smca_banks array is only populated at boot time and CPUs are brought
  online sequentially. So there's no need for locking around the array.
  
  If the first CPU up is a master thread, then it will populate the array
  with all banks, core and non-core. Every CPU afterwards will return
  early. If the first CPU up is not a master thread, then it will populate
  the array with all core banks. The first CPU afterwards that is a master
  thread will skip populating the core banks and continue populating the
  non-core banks.
  
  Signed-off-by: Yazen Ghannam 
  Signed-off-by: Borislav Petkov 
  Acked-by: Jack Miller 
  Cc: Linus Torvalds 
  Cc: Peter Zijlstra 
  Cc: Thomas Gleixner 
  Cc: Tony Luck 
  Cc: linux-edac 
  Link: http://lkml.kernel.org/r/20170724101228.17326-4...@alien8.de
  Signed-off-by: Ingo Molnar 

  [Test case]

  Suspend/resume Raven Ridge, see that it doesn't show the call trace
  any more.

  [Regression potential]

  4.14 released with it, and it fixes code which "for now" checked only
  CPU 0, so regressions potential is slim to none.

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

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

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

[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/1736629

Title:
  package linux-headers-4.13.0-19 (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation not
  permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  update failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-19 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  doc2667 F pulseaudio
   /dev/snd/controlC1:  doc2667 F pulseaudio
  Date: Tue Dec  5 20:01:23 2017
  DuplicateSignature:
   package:linux-headers-4.13.0-19:(not installed)
   Unpacking linux-headers-4.13.0-19 (4.13.0-19.22) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-eOV9kG/04-linux-headers-4.13.0-19_4.13.0-19.22_all.deb 
(--unpack):
unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
  InstallationDate: Installed on 2016-01-18 (687 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: EVGA 122-CK-NF68
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.13.0-19 (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 122-CK-NF68
  dmi.board.vendor: EVGA
  dmi.board.version: 2
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA
  dmi.chassis.version: 122-CK-NF68
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68:
  dmi.product.name: 122-CK-NF68
  dmi.product.version: 2
  dmi.sys.vendor: EVGA

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

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

[Kernel-packages] [Bug 1736629] Re: package linux-headers-4.13.0-19 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Oper

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-4.13.0-19 (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation not
  permitted

Status in linux package in Ubuntu:
  New

Bug description:
  update failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-19 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  doc2667 F pulseaudio
   /dev/snd/controlC1:  doc2667 F pulseaudio
  Date: Tue Dec  5 20:01:23 2017
  DuplicateSignature:
   package:linux-headers-4.13.0-19:(not installed)
   Unpacking linux-headers-4.13.0-19 (4.13.0-19.22) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-eOV9kG/04-linux-headers-4.13.0-19_4.13.0-19.22_all.deb 
(--unpack):
unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
  InstallationDate: Installed on 2016-01-18 (687 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: EVGA 122-CK-NF68
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.13.0-19 (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 122-CK-NF68
  dmi.board.vendor: EVGA
  dmi.board.version: 2
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA
  dmi.chassis.version: 122-CK-NF68
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68:
  dmi.product.name: 122-CK-NF68
  dmi.product.version: 2
  dmi.sys.vendor: EVGA

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

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

[Kernel-packages] [Bug 1736629] [NEW] package linux-headers-4.13.0-19 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Op

[Dr Bruce Seplowitz]

Public bug reported:

update failed

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-headers-4.13.0-19 (not installed)
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  doc2667 F pulseaudio
 /dev/snd/controlC1:  doc2667 F pulseaudio
Date: Tue Dec  5 20:01:23 2017
DuplicateSignature:
 package:linux-headers-4.13.0-19:(not installed)
 Unpacking linux-headers-4.13.0-19 (4.13.0-19.22) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-eOV9kG/04-linux-headers-4.13.0-19_4.13.0-19.22_all.deb 
(--unpack):
  unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
ErrorMessage: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
InstallationDate: Installed on 2016-01-18 (687 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: EVGA 122-CK-NF68
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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.
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
RfKill:
 
SourcePackage: linux
Title: package linux-headers-4.13.0-19 (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 122-CK-NF68
dmi.board.vendor: EVGA
dmi.board.version: 2
dmi.chassis.type: 3
dmi.chassis.vendor: EVGA
dmi.chassis.version: 122-CK-NF68
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68:
dmi.product.name: 122-CK-NF68
dmi.product.version: 2
dmi.sys.vendor: EVGA

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


** Tags: amd64 apport-package artful

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

Title:
  package linux-headers-4.13.0-19 (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation not
  permitted

Status in linux package in Ubuntu:
  New

Bug description:
  update failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-19 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  doc2667 F pulseaudio
   /dev/snd/controlC1:  doc2667 F pulseaudio
  Date: Tue Dec  5 20:01:23 2017
  DuplicateSignature:
   package:linux-headers-4.13.0-19:(not installed)
   Unpacking linux-headers-4.13.0-19 (4.13.0-19.22) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-eOV9kG/04-linux-headers-4.13.0-19_4.13.0-19.22_all.deb 
(--unpack):
unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
  InstallationDate: Installed on 2016-01-18 (687 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: EVGA 122-CK-NF68
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.13.0-19 (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  UpgradeStatus: No 

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

[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/1736625

Title:
  Repeatly ran into the same error while trying to upgdate to 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Greetings!
  Whenever I try to download "Artful Aardvark," I get the following error:
  Error during update:
  W.http:us.archive.ubuntu.com/ububtu/dists/artful/inrelease: The keys in the 
keyring 
  /etc/apt/trusted.gpg.d/jocket-drivers.gpg are ignored as the file is not 
readable by user '_apt' executing ...

  I suspect there are two "W"'s missing before the http.
  Thanks for listening, W. Carl Mayer

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-40-generic 4.10.0-40.44
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic i686
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   1512 F pulseaudio
   /dev/snd/controlC1:  carl   1512 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Dec  5 19:18:52 2017
  HibernationDevice: RESUME=UUID=13972a8b-4986-41b4-832c-91e952997e21
  InstallationDate: Installed on 2014-05-20 (1295 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Computer Corporation Dimension 8300
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=709e3868-3958-4f4f-9b32-f60053aa5371 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-12-06 (0 days ago)
  dmi.bios.date: 07/21/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A02
  dmi.board.name: 0M2035
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA02:bd07/21/2003:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0M2035:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 8300
  dmi.sys.vendor: Dell Computer Corporation

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

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

Thanks for doing the cleanup;  Patch looks good and I approve.

Signed-off-by: Ryan Harper 

On Tue, Dec 5, 2017 at 4:59 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> In the final patch we submit for SRU, it will also include your Signed-
> off-by, I just forgot to add it in the attached one.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  

[Kernel-packages] [Bug 1736625] [NEW] Repeatly ran into the same error while trying to upgdate to 17.10

[W. Carl Mayer]

Public bug reported:

Greetings!
Whenever I try to download "Artful Aardvark," I get the following error:
Error during update:
W.http:us.archive.ubuntu.com/ububtu/dists/artful/inrelease: The keys in the 
keyring 
/etc/apt/trusted.gpg.d/jocket-drivers.gpg are ignored as the file is not 
readable by user '_apt' executing ...

I suspect there are two "W"'s missing before the http.
Thanks for listening, W. Carl Mayer

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-40-generic 4.10.0-40.44
ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
Uname: Linux 4.10.0-40-generic i686
ApportVersion: 2.20.4-0ubuntu4.8
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  carl   1512 F pulseaudio
 /dev/snd/controlC1:  carl   1512 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Tue Dec  5 19:18:52 2017
HibernationDevice: RESUME=UUID=13972a8b-4986-41b4-832c-91e952997e21
InstallationDate: Installed on 2014-05-20 (1295 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: Dell Computer Corporation Dimension 8300
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=709e3868-3958-4f4f-9b32-f60053aa5371 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-40-generic N/A
 linux-backports-modules-4.10.0-40-generic  N/A
 linux-firmware 1.164.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-12-06 (0 days ago)
dmi.bios.date: 07/21/2003
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A02
dmi.board.name: 0M2035
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA02:bd07/21/2003:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0M2035:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: Dimension 8300
dmi.sys.vendor: Dell Computer Corporation

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


** Tags: apport-bug i386 zesty

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

Title:
  Repeatly ran into the same error while trying to upgdate to 17.10

Status in linux package in Ubuntu:
  New

Bug description:
  Greetings!
  Whenever I try to download "Artful Aardvark," I get the following error:
  Error during update:
  W.http:us.archive.ubuntu.com/ububtu/dists/artful/inrelease: The keys in the 
keyring 
  /etc/apt/trusted.gpg.d/jocket-drivers.gpg are ignored as the file is not 
readable by user '_apt' executing ...

  I suspect there are two "W"'s missing before the http.
  Thanks for listening, W. Carl Mayer

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-40-generic 4.10.0-40.44
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic i686
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   1512 F pulseaudio
   /dev/snd/controlC1:  carl   1512 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Dec  5 19:18:52 2017
  HibernationDevice: RESUME=UUID=13972a8b-4986-41b4-832c-91e952997e21
  InstallationDate: Installed on 2014-05-20 (1295 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Computer Corporation Dimension 8300
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=709e3868-3958-4f4f-9b32-f60053aa5371 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-12-06 (0 days ago)
  dmi.bios.date: 07/21/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A02
  dmi.board.name: 0M2035
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA02:bd07/21/2003:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0M2035:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 8300
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

[Steve Langasek]

04941829b0049d2446c7042ab9686dd057d809a6 is good.

7581d5ca2bb269cfc2ce2d0cb489aac513167f6b is the first bad commit

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  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
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1638788] Re: [MacBookAir5, 2] Resumes immediately after suspend

[Sergio Arboleda]

Ubuntu 16.04. I'm having this issue too... "echo XHC1 >
/proc/acpi/wakeup"  fixed but I don't know how to make it permanent.
thanks

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

Title:
  [MacBookAir5,2] Resumes immediately after suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  with default settings the laptop will immediately resume after sending
  to sleep (regardless of by closing the LID or though the menu option
  "suspend")

  the workaround is disabling the LID ACPI action by running:

  echo LID0 >/proc/acpi/wakeup

  this will fix the problem. obviously however just simply opening the
  lid won't wake the laptop anymore. so one has to manually press the
  power button.

  (I used ubuntu-bug linux, so hopefully all info should be attached)
  I'm running out of the box, up2date yakkety. without any external
  repos or custom compiled applications

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-26-generic 4.8.0-26.28
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toby   2327 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 21:49:50 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ba2577eb-f563-46c3-adb9-47967c8c5851
  InstallationDate: Installed on 2016-10-17 (16 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. MacBookAir5,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=add8c949-ae19-4310-aede-4a9007ea7514 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B04.1509111654
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B04.1509111654:bd09/11/2015:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.name: MacBookAir5,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

[Ujwal Setlur]

The last time something like this was fixed was
https://bugs.launchpad.net/bugs/1329434. The fix was to disable APIC
virtualization in nested guests. Did it suddenly get turned on again?
Any patches we could test? Thanks.

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

Title:
  nested KVM fails  - KVM: entry failed, hardware error 0x0

Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  We just noticed that systemd's autopkgtests have started failing often
  on amd64 for all releases, when run in Canonical's scalingstack cloud.

  This is nested KVM I think.

  TEST RUN: Basic systemd setup
  + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel 
/boot/vmlinuz-4.10.0-19-generic -drive 
format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd 
/boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host 
-append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd 
ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no  '
  KVM: entry failed, hardware error 0x0
  EAX= EBX= ECX= EDX=000206a1
  ESI= EDI= EBP= ESP=
  EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000   9b00
  SS =   9300
  DS =   9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90  5b e0 
00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  I have observed a failure on the compute node (region lgw01)

Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6
  18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  and a pass of the exact same package on the compute node (region
  lcy01)

Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  Here's an example log-

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz

  I found bug #1329434 which looks more or less identical and was fixed
  for 3.13. Perhaps it regressed in 4.4?

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

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

[Kernel-packages] [Bug 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  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: 1736181
  phase: Uploaded
+ kernel-stable-phase-changed:Tuesday, 05. December 2017 23:06 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  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: 1736181
- phase: Uploaded
- kernel-stable-phase-changed:Tuesday, 05. December 2017 23:06 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1736181
  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/1736187/+subscriptions

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

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Joseph Salisbury]

In the final patch we submit for SRU, it will also include your Signed-
off-by, I just forgot to add it in the attached one.

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Joseph Salisbury]

I attached an update to your patch, Ryan.

I added a subject, commit log and couple of missing semi colons /
parenthesis.

Can you look it over and see if you approve of the log and subject?
I'll see if it applies to the other Ubuntu releases and builds on them
as well.

** Patch added: "0001-bcache-decouple-emitting-a-cached_dev-CHANGE-uevent.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5018981/+files/0001-bcache-decouple-emitting-a-cached_dev-CHANGE-uevent.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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: 

[Kernel-packages] [Bug 1736617] [NEW] Port nvidia-settings to gtk3

[Jeremy Bicha]

Public bug reported:

gtk3 was declared stable in September 2016 with the gtk 3.22 release.
nvidia-settings should switch to gtk3.

nvidia-settings is one of the last dozen packages to keep gtk2 in main.

https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gtk2-demotion

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic gtk2-demotion

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

Title:
  Port nvidia-settings to gtk3

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  gtk3 was declared stable in September 2016 with the gtk 3.22 release.
  nvidia-settings should switch to gtk3.

  nvidia-settings is one of the last dozen packages to keep gtk2 in
  main.

  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gtk2-demotion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1736617/+subscriptions

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

[Kernel-packages] [Bug 1736593] Re: ThunderX: IPv6 TX failure unless checksum offload disabled

[dann frazier]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  ThunderX: IPv6 TX failure unless checksum offload disabled

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

Bug description:
  [Impact]
  Most attempts to use IPv6 on the ThunderX NIC will fail.

  [Test Case]
  Attempt an IPv6 TCP connection:

  $ wget -6 'http://www.kernel.org/'

  The connection will time out.

  [Regression Risk]
  The fix is upstream, and is limited to the ThunderX nicvf driver.

  [Workaround]
  Disable TX checksum offload:

  $ ethtool -K eth0 tx off

  [More Details]
  The issue first appears in Linux 4.12.  A fix from Cavium has been merged 
upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379

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

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

Woot!

I think that did the trick.

ubuntu@ubuntu:~$ cat /etc/cloud/build.info
build_name: server
serial: 20171122
ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
ubuntu@ubuntu:~$ set -o vi
ubuntu@ubuntu:~$ dpkg --list | grep linux-image
ii  linux-image-4.13.0-17-generic  4.13.0-17.20~lp1739145
 amd64Linux kernel image for version 4.13.0 on 64
bit x86 SMP
ii  linux-image-virtual4.13.0.17.18
 amd64Virtual Linux kernel image
ubuntu@ubuntu:~$ dpkg --list | grep bcache-tools
ii  bcache-tools   1.0.8-2build1
amd64bcache userspace tools

ubuntu@ubuntu:~$ sudo tree /dev/bcache
/dev/bcache
├── by-label
│   ├── backing0 -> ../../bcache1
│   └── backing1 -> ../../bcache0
└── by-uuid
├── 1375d23f-4780-46d7-9fca-c397f8333685 -> ../../bcache2
├── 57e009b1-6bf4-42ea-abe0-334b10941a0b -> ../../bcache0
├── 7ce7dc32-7da9-42a8-899a-5d21ed7ea714 -> ../../bcache3
└── 92d882d8-38cd-4537-847b-6f9c40ba67b4 -> ../../bcache1

2 directories, 6 files


On Tue, Dec 5, 2017 at 4:00 PM, Ryan Harper 
wrote:

> Thanks!  I'll give it a try today.
>
> On Tue, Dec 5, 2017 at 3:43 PM, Joseph Salisbury <
> joseph.salisb...@canonical.com> wrote:
>
>> I built an Artful test kernel with the path provided by Ryan.  The test
>> kernel can be downloaded from:
>>
>> http://kernel.ubuntu.com/~jsalisbury/lp1729145/
>>
>> Can those that can reproduce this bug give this test kernel a try?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1729145
>>
>> Title:
>>   /dev/bcache/by-uuid links not created after reboot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145
>> /+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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 

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

[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 1736593

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

Title:
  ThunderX: IPv6 TX failure unless checksum offload disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Most attempts to use IPv6 on the ThunderX NIC will fail.

  [Test Case]
  Attempt an IPv6 TCP connection:

  $ wget -6 'http://www.kernel.org/'

  The connection will time out.

  [Regression Risk]
  The fix is upstream, and is limited to the ThunderX nicvf driver.

  [Workaround]
  Disable TX checksum offload:

  $ ethtool -K eth0 tx off

  [More Details]
  The issue first appears in Linux 4.12.  A fix from Cavium has been merged 
upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379

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

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

Thanks!  I'll give it a try today.

On Tue, Dec 5, 2017 at 3:43 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> I built an Artful test kernel with the path provided by Ryan.  The test
> kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1729145/
>
> Can those that can reproduce this bug give this test kernel a try?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 

[Kernel-packages] [Bug 1730762] Re: 17.10 - suspend/resume failure

[venturia]

Hello, there is still someone looking for this issue?
Thanks, Alessandro-

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

Title:
  17.10 - suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a failure in the resume process after the suspend.
  When I try to resume the system start, but the screen stay black while
  the disk seem be really busy.

  The only way to exit from this status is unplug the system before
  restart it.

  Let me know how to collect additional info (if necessary).

  Alessandro-

  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/controlC1:  alessandro   1948 F pulseaudio
   /dev/snd/controlC0:  alessandro   1948 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 22:59:45 2017
  HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
  InstallationDate: Installed on 2016-07-09 (486 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s5no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell NEC IMEDIA 5204
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system

[Joseph Salisbury]

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

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

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Kernel panic on a nfsroot system

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

Bug description:
  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.

  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw

  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64

  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash

  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; 

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Joseph Salisbury]

I built an Artful test kernel with the path provided by Ryan.  The test
kernel can be downloaded from:

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

Can those that can reproduce this bug give this test kernel a try?

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:

[Kernel-packages] [Bug 1736593] [NEW] ThunderX: IPv6 TX failure unless checksum offload disabled

[Scott Burns]

Public bug reported:

[Impact]
Most attempts to use IPv6 on the ThunderX NIC will fail.

[Test Case]
Attempt an IPv6 TCP connection:

$ wget -6 'http://www.kernel.org/'

The connection will time out.

[Regression Risk]
The fix is upstream, and is limited to the ThunderX nicvf driver.

[Workaround]
Disable TX checksum offload:

$ ethtool -K eth0 tx off

[More Details]
The issue first appears in Linux 4.12.  A fix from Cavium has been merged 
upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379

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

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

Title:
  ThunderX: IPv6 TX failure unless checksum offload disabled

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Most attempts to use IPv6 on the ThunderX NIC will fail.

  [Test Case]
  Attempt an IPv6 TCP connection:

  $ wget -6 'http://www.kernel.org/'

  The connection will time out.

  [Regression Risk]
  The fix is upstream, and is limited to the ThunderX nicvf driver.

  [Workaround]
  Disable TX checksum offload:

  $ ethtool -K eth0 tx off

  [More Details]
  The issue first appears in Linux 4.12.  A fix from Cavium has been merged 
upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379

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

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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

[Joseph Salisbury]

** Tags removed: kernel-da-key

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

Title:
  nested KVM fails  - KVM: entry failed, hardware error 0x0

Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  We just noticed that systemd's autopkgtests have started failing often
  on amd64 for all releases, when run in Canonical's scalingstack cloud.

  This is nested KVM I think.

  TEST RUN: Basic systemd setup
  + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel 
/boot/vmlinuz-4.10.0-19-generic -drive 
format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd 
/boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host 
-append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd 
ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no  '
  KVM: entry failed, hardware error 0x0
  EAX= EBX= ECX= EDX=000206a1
  ESI= EDI= EBP= ESP=
  EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000   9b00
  SS =   9300
  DS =   9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90  5b e0 
00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  I have observed a failure on the compute node (region lgw01)

Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6
  18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  and a pass of the exact same package on the compute node (region
  lcy01)

Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  Here's an example log-

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz

  I found bug #1329434 which looks more or less identical and was fixed
  for 3.13. Perhaps it regressed in 4.4?

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

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

[Kernel-packages] [Bug 1735977] Re: Using asymmetric key for IMA appraisal crashes the system in Ubuntu 16.04

[Joseph Salisbury]

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

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

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

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

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

Title:
  Using asymmetric key for IMA appraisal crashes the system in Ubuntu
  16.04

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

Bug description:
  I'm trying to enable IMA appraisal with signatures for executable files on 
xenial with Linux 4.4. I took the following steps:
  * Downloaded ubuntu-xenial kernel sources
  * Run fakeroot debian/rules editconfigs to set CONFIG_SYSTEM_TRUSTED_KEYS to 
my key
  * Run fakeroot debian/rules binary-headers binary-generic binary-perarch to 
build the kernel deb packaes
  * Installed the kernel
  * Signed the filesystem with my key using 'evmctl sing'
  * Enabled IMA policy so that it will include the following line
appraise fowner=0 appraise_type=imasig
  * From this point invocation of a signed binary cases a kernel BUG():

  [ 1395.036910] kernel BUG at 
/home/rapoport/git/ubuntu-xenial/crypto/asymmetric_keys/public_key.c:80!
  [ 1395.038963] invalid opcode:  [#1] SMP 
  [ 1395.039973] Modules linked in: isofs ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper psmouse cryptd floppy
  [ 1395.050761] CPU: 6 PID: 31586 Comm: bash Not tainted 4.4.0-101-generic #124
  [ 1395.051909] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [ 1395.053510] task: 8800bae9c600 ti: 88042c52c000 task.ti: 
88042c52c000
  [ 1395.054763] RIP: 0010:[]  [] 
public_key_verify_signature+0x46/0x50
  [ 1395.056406] RSP: 0018:88042c52fa98  EFLAGS: 00010246
  [ 1395.057307] RAX: 813bdb80 RBX: fff4 RCX: 
0001
  [ 1395.058518] RDX: 81ea73c0 RSI: 88042c52fac8 RDI: 
88042a107c10
  [ 1395.059709] RBP: 88042c52faa0 R08: 88042a849100 R09: 
0007
  [ 1395.061109] R10: 88042a0f9d00 R11: 88042c52fb07 R12: 
0080
  [ 1395.062289] R13: 88042abd9a80 R14: 0014 R15: 
88042a849ac4
  [ 1395.063404] FS:  7f5e21958700() GS:88043fd8() 
knlGS:
  [ 1395.064771] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1395.065809] CR2: 7f5e20f5c3cc CR3: 00042cabc000 CR4: 
000406e0
  [ 1395.067058] Stack:
  [ 1395.067540]  813bdb95 88042c52fab0 813bdaec 
88042c52fb38
  [ 1395.068964]  813a759e 88042c52fac8  

  [ 1395.070417]  88042a849ac4 02000114 88042a849100 

  [ 1395.071973] Call Trace:
  [ 1395.072510]  [] ? public_key_verify_signature_2+0x15/0x20
  [ 1395.073605]  [] verify_signature+0x3c/0x50
  [ 1395.074526]  [] asymmetric_verify+0x17e/0x2a0
  [ 1395.075475]  [] integrity_digsig_verify+0x70/0x110
  [ 1395.076481]  [] ima_appraise_measurement+0x244/0x420
  [ 1395.077518]  [] process_measurement+0x3fa/0x480
  [ 1395.078479]  [] ima_file_check+0x18/0x20
  [ 1395.079381]  [] path_openat+0x1f3/0x1330
  [ 1395.080274]  [] ? __slab_free+0xcb/0x2c0
  [ 1395.081165]  [] do_filp_open+0x91/0x100
  [ 1395.082050]  [] ? apparmor_cred_prepare+0x2f/0x50
  [ 1395.083046]  [] ? security_prepare_creds+0x43/0x60
  [ 1395.084056]  [] do_open_execat+0x78/0x1d0
  [ 1395.084952]  [] do_execveat_common.isra.33+0x240/0x760
  [ 1395.086016]  [] SyS_execve+0x3a/0x50
  [ 1395.086877]  [] stub_execve+0x5/0x5
  [ 1395.087711]  [] ? entry_SYSCALL_64_fastpath+0x16/0x71
  [ 1395.088746] Code: 2a 0f b6 57 0c b8 bf ff ff ff 80 fa 01 77 14 48 8b 14 d5 
b0 05 a5 81 48 85 d2 74 07 55 48 89 e5 ff d2 5d f3 c3 0f 0b 0f 0b 0f 0b <0f> 0b 
0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 8b bf a0 00 
  [ 1395.093215] RIP  [] public_key_verify_signature+0x46/0x50
  [ 1395.094322]  RSP 
  [ 1395.095364] ---[ end trace 7ee330317745ad36 ]---

  I did some checks and it appears that upstream commit db6c43bd2132 ("crypto: 
KEYS: convert public key and digsig asym to the akcipher api") has changed 
public keys APIs, but the IMA usage of that API was fixed only by commit 
eb5798f2e28f ("integrity: convert digsig to akcipher api")
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec  

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Joseph Salisbury]

** Tags removed: kernel-da-key

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

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

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using an IBM thinkpad R50

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newton  901 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 27
 Simple ctrls  : 18
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
1RHT71WW-3.04'
 Mixer name : 'ThinkPad EC 1RHT71WW-3.04'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 8 [57%] [on]
  Date: Mon Dec  4 21:58:51 2017
  DuplicateSignature:
   package:linux-image-4.13.0-17-generic:(not installed)
   Preparing to unpack 
.../12-linux-image-4.13.0-17-generic_4.13.0-17.20_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-hnysPd/12-linux-image-4.13.0-17-generic_4.13.0-17.20_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=5c65b509-112c-4f21-a68b-76ba7fb8ba32
  InstallationDate: Installed on 2017-11-21 (14 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: IBM 0123456
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=034bd9a6-74ee-45c6-bbb3-f3a5ebd3f36b 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-17-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2006
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDPWW (3.21 )
  dmi.board.name: 0123456
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDPWW(3.21):bd06/02/2006:svnIBM:pn0123456:pvrThinkPadR50:rvnIBM:rn0123456:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 0123456
  dmi.product.version: ThinkPad R50
  dmi.sys.vendor: IBM

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

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

[Joseph Salisbury]

Is this issue new in bionic?  Do you you happen to know of a prior
kernel version that does not exhibit the bug?

Also, could you see if this bug happens with the latest mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Confirmed

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

** Tags added: kernel-key

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

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

Title:
  openvswitch: kernel opps destroying interfaces on i386

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

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 1729573] Re: netplan breaks Xen VIF driver

[Dan Streetman]

xenial:

ubuntu@ip-172-31-52-172:~$ lsb_release -r
Release:16.04
ubuntu@ip-172-31-52-172:~$ dpkg -l|grep nplan
ii  nplan0.23~16.04.1   
amd64YAML network configuration abstraction for various backends
ubuntu@ip-172-31-52-172:~$ ip l show eth1
3: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-31-52-172:~$ sudo netplan --debug apply
** (generate:3891): DEBUG: Processing input file 
//etc/netplan/10-ifupdown.yaml..
** (generate:3891): DEBUG: starting new processing pass
** (generate:3891): DEBUG: eth0: setting default backend to 1
** (generate:3891): DEBUG: Generating output files..
** (generate:3891): DEBUG: NetworkManager: definition eth0 is not for us 
(backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:device eth0 operstate is up, not replugging
DEBUG:netplan triggering .link rules for eth0
DEBUG:replug eth1: unbinding vif-1 from /sys/bus/xen/drivers/vif
DEBUG:replug eth1: rebinding vif-1 to /sys/bus/xen/drivers/vif
ubuntu@ip-172-31-52-172:~$ ip l show eth1
4: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff


ubuntu@ip-172-31-52-172:~$ lsb_release -r
Release:16.04
ubuntu@ip-172-31-52-172:~$ dpkg -l|grep nplan
ii  nplan0.32~16.04.3   
amd64YAML network configuration abstraction for various backends
ubuntu@ip-172-31-52-172:~$ ip l show eth1
3: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-31-52-172:~$ sudo netplan --debug apply
sudo: unable to resolve host ip-172-31-52-172
** (generate:1317): DEBUG: Processing input file 
//etc/netplan/10-ifupdown.yaml..
** (generate:1317): DEBUG: starting new processing pass
** (generate:1317): DEBUG: eth0: setting default backend to 1
** (generate:1317): DEBUG: Generating output files..
** (generate:1317): DEBUG: NetworkManager: definition eth0 is not for us 
(backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:device eth0 operstate is up, not replugging
DEBUG:netplan triggering .link rules for eth0
DEBUG:replug eth1: xen:vif fails on rebinding, ignoring
DEBUG:netplan triggering .link rules for eth1
ubuntu@ip-172-31-52-172:~$ ip l show eth1
3: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff


** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to 

[Kernel-packages] [Bug 1729573] Re: netplan breaks Xen VIF driver

[Dan Streetman]

artful:

ubuntu@ip-172-31-58-142:~$ lsb_release -r
Release:17.10
ubuntu@ip-172-31-58-142:~$ dpkg -l|grep nplan
ii  nplan  0.30 
amd64YAML network configuration abstraction for various 
backends
ubuntu@ip-172-31-58-142:~$ ip l show eth1
3: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-31-58-142:~$ sudo netplan --debug apply
** (generate:7935): DEBUG: Processing input file 
//etc/netplan/10-ifupdown.yaml..
** (generate:7935): DEBUG: starting new processing pass
** (generate:7935): DEBUG: eth0: setting default backend to 1
** (generate:7935): DEBUG: Generating output files..
** (generate:7935): DEBUG: NetworkManager: definition eth0 is not for us 
(backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:replug eth1: unbinding vif-1 from /sys/bus/xen/drivers/vif
DEBUG:replug eth1: rebinding vif-1 to /sys/bus/xen/drivers/vif
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:device eth0 operstate is up, not replugging
DEBUG:netplan triggering .link rules for eth0
ubuntu@ip-172-31-58-142:~$ ip l show eth1
4: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff


ubuntu@ip-172-31-58-142:~$ lsb_release -r
Release:17.10
ubuntu@ip-172-31-58-142:~$ dpkg -l|grep nplan
ii  nplan  0.32~17.10.1 
amd64YAML network configuration abstraction for various 
backends
ubuntu@ip-172-31-58-142:~$ ip l show eth1
4: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-31-58-142:~$ sudo netplan --debug apply
** (generate:1267): DEBUG: Processing input file 
//etc/netplan/10-ifupdown.yaml..
** (generate:1267): DEBUG: starting new processing pass
** (generate:1267): DEBUG: eth0: setting default backend to 1
** (generate:1267): DEBUG: Generating output files..
** (generate:1267): DEBUG: NetworkManager: definition eth0 is not for us 
(backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:device eth0 operstate is up, not replugging
DEBUG:netplan triggering .link rules for eth0
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:replug eth1: xen:vif fails on rebinding, ignoring
DEBUG:netplan triggering .link rules for eth1
ubuntu@ip-172-31-58-142:~$ ip l show eth1
4: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff


** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never 

[Kernel-packages] [Bug 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1736181
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1735024] Re: Cannot boot without acpi=off

[Armands Skolmeisters]

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

Title:
  Cannot boot without acpi=off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bought a new laptop but after reinstalling cannot boot without
  acpi=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseniuss954 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 29 02:25:57 2017
  InstallationDate: Installed on 2017-11-26 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-51
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=7105a1eb-3d1e-4b00-9668-da7cce948f4e ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnNitroAN515-51:pvrV1.05:rvnKBL:rnFreed_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-51
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1736195] Re: linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  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: 1736194
  phase: Uploaded
+ kernel-stable-phase-changed:Tuesday, 05. December 2017 20:03 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  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: 1736194
- phase: Uploaded
- kernel-stable-phase-changed:Tuesday, 05. December 2017 20:03 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1736194
  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/1736195/+subscriptions

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

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Tom Reynolds]

The workaround discussed at http://blog.programster.org/ubuntu-16-04
-compile-custom-kernel-for-ryzen fixes the recurring (roughly once or
twice in 6 hours of operation, during low or idle CPU load periods)
system freezes for this Ryzen 7 1800X (early weeks), AMD microcode
0x8001129, ASRock X370 Taichi (Firmware P3.20, BIOS 5.12, Release Date:
09/08/2017) system running XUbuntu 16.04 LTS (with latest updates)

All the mainline kernels up to linux-image-4.13.10-041310-generic, and
official Ubuntu kernels (default 16.04 kernel, hwe) all kept freezing -
although I had only tested them without "rcu_nocbs=0-15". I did test
hwe-edge (4.10.0.20.13), both with and without "rcu_nocbs=0-15". Both
variants gave me freezes.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  

[Kernel-packages] [Bug 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  In Progress
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1736181
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1736168] Re: linux: 4.14.0-11.13 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

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

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Fix Committed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug is for tracking the 4.14.0-11.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-phase-changed:Monday, 04. December 2017 15:32 UTC
- kernel-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase:Uploaded
+ kernel-phase-changed:Tuesday, 05. December 2017 19:31 UTC

** Description changed:

  This bug is for tracking the 4.14.0-11.13 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 --
- phase: Packaging
- kernel-phase:Uploaded
- kernel-phase-changed:Tuesday, 05. December 2017 19:31 UTC
+ phase: Uploaded

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

Title:
  linux: 4.14.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-11.13 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 --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1736549] Re: Poor kernel builtin r8169 driver performance, r8168-dkms driver not compatible with kernels > 4.7

[dino99]

** Description changed:

  From the Bionic archive (universe) the r8168-dkms driver is supposed to
  get better performance compared to the kernel builin r8169 one, which
  has degraded speed mainly due to MTU 576 and only using 100 Mbits/s.
  
  Installing that driver onto a 4.13.13 based kernel goes as expected, but
  after rebooting there is no network at all, ping fails. Blacklisting
  r8169 or not makes no difference.
  
  An issue is opened on https://github.com/mtorromeo/r8168/issues/9
  
  So that driver is not usable actually with the proposed kernels from the
  recent ubuntu releases; maybe the driver description could point that
  limitation, if a bypass is not found.
+ 
+ Will get a chance to the proposition found on:
+ https://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers/en
  
  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.
  
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:
  
  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

** Description changed:

  From the Bionic archive (universe) the r8168-dkms driver is supposed to
  get better performance compared to the kernel builin r8169 one, which
  has degraded speed mainly due to MTU 576 and only using 100 Mbits/s.
  
  Installing that driver onto a 4.13.13 based kernel goes as expected, but
  after rebooting there is no network at all, ping fails. Blacklisting
  r8169 or not makes no difference.
  
  An issue is opened on https://github.com/mtorromeo/r8168/issues/9
  
  So that driver is not usable actually with the proposed kernels from the
  recent ubuntu releases; maybe the driver description could point that
  limitation, if a bypass is not found.
  
- Will get a chance to the proposition found on:
+ Will get a chance to the propositions found on:
  https://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers/en
  
  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.
  
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: 

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

[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/1736549

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] ProcInterrupts.txt

[dino99]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018862/+files/ProcInterrupts.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] PulseList.txt

[dino99]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018864/+files/PulseList.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] Lspci.txt

[dino99]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1736549/+attachment/5018860/+files/Lspci.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] ProcModules.txt

[dino99]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018863/+files/ProcModules.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] UdevDb.txt

[dino99]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1736549/+attachment/5018865/+files/UdevDb.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] AlsaInfo.txt

[dino99]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018855/+files/AlsaInfo.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] WifiSyslog.txt

[dino99]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018866/+files/WifiSyslog.txt

** Description changed:

  From the Bionic archive (universe) the r8168-dkms driver is supposed to
- get better performance compared to the kernel builin r8169 one, with has
- degraded speed mainly due to MTU 576 and only using 100 Mbits/s.
+ get better performance compared to the kernel builin r8169 one, which
+ has degraded speed mainly due to MTU 576 and only using 100 Mbits/s.
  
  Installing that driver onto a 4.13.13 based kernel goes as expected, but
  after rebooting there is no network at all, ping fails. Blacklisting
  r8169 or not makes no difference.
  
  An issue is opened on https://github.com/mtorromeo/r8168/issues/9
  
  So that driver is not usable actually with the proposed kernels from the
  recent ubuntu releases; maybe the driver description could point that
  limitation, if a bypass is not found.
  
  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
- --- 
+ ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  oem1288 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
-  enp2s0no wireless extensions.
-  
-  lono wireless extensions.
+  enp2s0no wireless extensions.
+ 
+  lono wireless extensions.
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
+  linux-restricted-modules-4.13.0-17-generic N/A
+  linux-backports-modules-4.13.0-17-generic  N/A
+  linux-firmware 1.170
  RfKill:
-  
+ 
  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  

[Kernel-packages] [Bug 1736549] CRDA.txt

[dino99]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1736549/+attachment/5018856/+files/CRDA.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] CurrentDmesg.txt

[dino99]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018857/+files/CurrentDmesg.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] ProcCpuinfoMinimal.txt

[dino99]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018861/+files/ProcCpuinfoMinimal.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] JournalErrors.txt

[dino99]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018859/+files/JournalErrors.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] Dependencies.txt

[dino99]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1736549/+attachment/5018858/+files/Dependencies.txt

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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

[Kernel-packages] [Bug 1736549] Re: Poor kernel builtin r8169 driver performance, r8168-dkms driver not compatible with kernels > 4.7

[dino99]

oem@ubuntu:~$ sudo lshw -class network
[sudo] password for oem: 
  *-network 
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: enp2s0
   version: 06
   serial: 70:85:c2:23:9b:4c
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 
ip=192.168.1.3 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
   resources: irq:127 ioport:d000(size=256) memory:df00-df000fff 
memory:d000-d0003fff


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

** Tags added: apport-collected bionic

** Description changed:

  From the Bionic archive (universe) the r8168-dkms driver is supposed to
  get better performance compared to the kernel builin r8169 one, with has
  degraded speed mainly due to MTU 576 and only using 100 Mbits/s.
  
  Installing that driver onto a 4.13.13 based kernel goes as expected, but
  after rebooting there is no network at all, ping fails. Blacklisting
  r8169 or not makes no difference.
  
  An issue is opened on https://github.com/mtorromeo/r8168/issues/9
  
  So that driver is not usable actually with the proposed kernels from the
  recent ubuntu releases; maybe the driver description could point that
  limitation, if a bypass is not found.
  
- About the kernel itself, maybe the builtin r8169 driver could deliver
- better performance , for example setting MTU to >=1492 at least.
+ About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
+ --- 
+ ApportVersion: 2.20.8-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  oem1288 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 18.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
+ IwConfig:
+  enp2s0no wireless extensions.
+  
+  lono wireless extensions.
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: r8168-dkms 8.045.08-1
+ PackageArchitecture: all
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
+ ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
+ 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
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 4.13.0-17-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/07/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P7.00
+ dmi.board.name: B150M-HDV
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.
+ modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
+ mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Confirmed
Status in r8168-dkms package in Ubuntu:
  New

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel 

[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system

[Sergey Kozlov]

4.13.0-13-generic #14~lp1734327Commit1c8d41925cf is not affected.

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

Title:
  Kernel panic on a nfsroot system

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

Bug description:
  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.

  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw

  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64

  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash

  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/0xe0
  

[Kernel-packages] [Bug 1736195] Re: linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1736194
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1736194] Re: linux: 3.13.0-137.186 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 3.13.0-137.186 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: 1736195
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Monday, 04. December 2017 19:30 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.4.0-103.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Monday, 04. December 2017 16:33 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 315762] ☑hey! Re: interesting

[ixzel]

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

Hello friend,

I simply read articles that you may be thinking about, please read it
here http://www.autoservis-
sao.ru/amsgx.php?UE8zMTU3NjJAYnVncy5sYXVuY2hwYWQubmV0

See you around, Suzanne Randolph


From: Bug 315762 [mailto:315...@bugs.launchpad.net]
Sent: Tuesday, December 05, 2017 11:16 AM
To: oscurosp...@yahoo.com
Subject: or a big penis

No, but I vaguely remember, perhaps from Sid Meier's "Pirates" that
there is a Long Island somewhere in the Caribbean.

The reason I specified though, is that I wasn't  sure if people would
know where LI is in the world. I  suppose I could have just said we
were in the states, but I  like  some  specificity in any  story.


Sent from Mail for Windows 10

** Attachment added: "E4F78157FCB6E309.jpg"
   
https://bugs.launchpad.net/bugs/315762/+attachment/5018844/+files/E4F78157FCB6E309.jpg

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

Title:
  when finishing the instalation of updated data, instalation halts and
  the windows message appears with following "Failed: E:
  /var/cache/apt/archives/linux-
  image-2.6.27-7-generic_2.6.27-7.16_i386.deb: impossível criar ligação
  de backup de './boot/vmlinuz-2.6.27-7-generic' antes de instalar nova
  versão".

Status in linux package in Ubuntu:
  New

Bug description:
  E: /var/cache/apt/archives/linux-
  image-2.6.27-7-generic_2.6.27-7.16_i386.deb: impossível criar ligação
  de backup de './boot/vmlinuz-2.6.27-7-generic' antes de instalar nova
  versão

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  LsUsb:
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 1307:0163 Transcend Information, Inc. 512MB USB Flash 
Drive
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.27-9-generic 2.6.27-9.19
  ProcCmdLine: root=UUID=3836-A19B loop=/hostname/disks/root.disk ro 
ROOTFLAGS=sync quiet splash
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.27-9.19-generic
  SourcePackage: linux

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

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

[Kernel-packages] [Bug 1736152] Re: linux: 4.10.0-42.46 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.10.0-42.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1736153,1736154
  derivatives: 1736155
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Monday, 04. December 2017 15:00 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system

[Joseph Salisbury]

I started a kernel bisect between 4.13.0-12 and 4.13.0-14. The kernel
bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
1c8d41925cff57972056048511a451040fa3b790

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

Can you test that kernel and report back if it has the bug or not?  I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Kernel panic on a nfsroot system

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

Bug description:
  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.

  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw

  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64

  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash

  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; 

[Kernel-packages] [Bug 1736118] Re: linux: 4.13.0-19.22 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.13.0-19.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Monday, 04. December 2017 12:32 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[m.fazil]

Can confirm for Z50-70. The "bug" occurs just after Ubuntu 17.10
installation and makes UEFI useless except for booting Ubuntu itself.
What is interesting for me is that, my prior linux installations did not
create a new label in the boot menu. After any os installation I would
get a boot entry which is basically referred as my harddrive name. But
for the last problematic Ubuntu 17.10 installation, there do exist an
entry just called as "ubuntu". Nothing more nothing less, no disk name
either. It just boots properly but the "bug" is still there. It might
not be directly related to the bug, but is is somewhat interesting to
collide with the problematic kernel or sth and how it handles boot
entries.

-- 
You 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 package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Hi all,

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

   UPDATE (01/12/2017) 

  LENOVO machines affected so far:

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

[James Page]

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

Title:
  openvswitch: kernel opps destroying interfaces on i386

Status in linux package in Ubuntu:
  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 1724635] Re: linux-azure-edge: 4.13.0-1002.2 -proposed tracker

[Stefan Bader]

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

** This bug is no longer a duplicate of bug 1733533
   linux-azure-edge: 4.13.0-1004.4 -proposed tracker
** This bug has been marked a duplicate of bug 1736120
   linux-azure-edge: 4.13.0-1005.5 -proposed tracker

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

Title:
  linux-azure-edge: 4.13.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.13.0-1002.2 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
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1730449] Re: linux-azure-edge: 4.13.0-1003.3 -proposed tracker

[Stefan Bader]

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

** This bug is no longer a duplicate of bug 1733533
   linux-azure-edge: 4.13.0-1004.4 -proposed tracker
** This bug has been marked a duplicate of bug 1736120
   linux-azure-edge: 4.13.0-1005.5 -proposed tracker

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

Title:
  linux-azure-edge: 4.13.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.13.0-1003.3 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
  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/1730449/+subscriptions

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