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

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

apport-collect 1796445

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

** Tags added: bionic

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

Title:
  Ubuntu 18.04 no wifi even after installing Realtek wifi drivers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using HP laptop which is currently using Realtek wifi drivers. I have 
followed steps to install it.
  It installs successfully but I do not get proper wifi connectivity on Ubuntu 
18.04.
  Following same steps and installting wifi drivers on ubuntu 16.04 works 
flawlessly.

  This is a serious issue which stops me using ubuntu 18.04.
  It would be great if Ubuntu in it future releases fix these problems.

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

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


[Kernel-packages] [Bug 1796445] Re: Ubuntu 18.04 no wifi even after installing Realtek wifi drivers

2018-10-05 Thread William Grant
** Project changed: launchpad => linux (Ubuntu)

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

Title:
  Ubuntu 18.04 no wifi even after installing Realtek wifi drivers

Status in linux package in Ubuntu:
  New

Bug description:
  Using HP laptop which is currently using Realtek wifi drivers. I have 
followed steps to install it.
  It installs successfully but I do not get proper wifi connectivity on Ubuntu 
18.04.
  Following same steps and installting wifi drivers on ubuntu 16.04 works 
flawlessly.

  This is a serious issue which stops me using ubuntu 18.04.
  It would be great if Ubuntu in it future releases fix these problems.

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

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


[Kernel-packages] [Bug 1796445] [NEW] Ubuntu 18.04 no wifi even after installing Realtek wifi drivers

2018-10-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Using HP laptop which is currently using Realtek wifi drivers. I have followed 
steps to install it.
It installs successfully but I do not get proper wifi connectivity on Ubuntu 
18.04.
Following same steps and installting wifi drivers on ubuntu 16.04 works 
flawlessly.

This is a serious issue which stops me using ubuntu 18.04.
It would be great if Ubuntu in it future releases fix these problems.

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

-- 
Ubuntu 18.04 no wifi even after installing Realtek wifi drivers
https://bugs.launchpad.net/bugs/1796445
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1

2018-10-05 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Audio streaming over bluetooth to Bose QC35 is highly unreliable on a
  MacBookPro12,1

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Streaming of audio files over bluetooth is not possible in Ubuntu
  17.10.

  Connecting a headphone requires several attempts.
  Then the sound settings have to be selected manually
  Even then, the sound offered is mono
  I tested with a Bose QC35.
  There is a sound profile that requires manual selection and offers stereo 
speakers.
  However, while testing left speaker gives reasonable results, testing the 
right speaker only produces cracking noise.
  Playback of music is virtually impossible (the stream is repeatedly 
interupted by voice anouncements of incoming calls ??? and reconnection attemts)

  To eliminate hardware issues I tested under macOS and the sound quality is 
excellent (even during working in a spread sheet and a word processor in 
parallel).
  => issues caused by the software stack

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 15:12:02 2017
  InstallationDate: Installed on 2017-09-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:32:75:9F:91:1E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0
TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0

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

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


[Kernel-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

2018-10-05 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Periodic glitch in sound with Firewire and snd-dice

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  Not sure if this information can be added afterwards: but I installed
  the  3.19.8 low latency kernel, and the problem disappeared. On 17.1 I
  can't use the current low latency kernel because the system becomes
  very unresponsive to the point of being hard to even log in. So I'm
  not sure if this is just a matter of difference between the low
  latency and regular kernels.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx: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.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', 
'/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', 
'/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  

[Kernel-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

2018-10-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Periodic glitch in sound with Firewire and snd-dice

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  Not sure if this information can be added afterwards: but I installed
  the  3.19.8 low latency kernel, and the problem disappeared. On 17.1 I
  can't use the current low latency kernel because the system becomes
  very unresponsive to the point of being hard to even log in. So I'm
  not sure if this is just a matter of difference between the low
  latency and regular kernels.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx: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.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', 
'/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', 
'/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: 

[Kernel-packages] [Bug 1728385] Re: Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill (0x12)"

2018-10-05 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Reduce/hide excessive logging when Bluetooth is intentionally
  disabled: "Failed to set mode: Blocked through rfkill (0x12)"

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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


[Kernel-packages] [Bug 1733667] Re: Bluetooth doesn't (usually) work on booting [MacBookPro12, 1]

2018-10-05 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth doesn't (usually) work on booting [MacBookPro12,1]

Status in bluez package in Ubuntu:
  Expired

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  Just updated to latest repo kernel.

  After reboot, the bluetoothd gets started but not activated.

  Restarting does not work (error msg in bluetooth panel: adapter not
  found - it was there before the reboot).

  Required several reboots to fix the issue (i.e. after a reboot I have
  to reboot several times, click the mouse frantically during boot to
  get it recognized somewhere during the bootup).

  I remember this to have happened two kernels before so I think it is a
  regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 18:58:04 2017
  InstallationDate: Installed on 2017-10-20 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:32:75:9F:91:1E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:28328 acl:854 sco:0 events:231 errors:0
TX bytes:6881 acl:65 sco:0 commands:121 errors:0

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

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


[Kernel-packages] [Bug 1708774] Re: bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type() from _dbus_message_has_type_interface_member() from browse_request_complete() from device_svc_res

2018-10-05 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type()
  from _dbus_message_has_type_interface_member() from
  browse_request_complete() from device_svc_resolved()

Status in bluez package in Ubuntu:
  Expired

Bug description:
  This is happening over and over while running behind the scenes.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.45-0ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Jul 31 22:44:35 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-07-29 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: initrd=\ubuntu\initrd.img-generic 
root=/dev/mapper/volgrp-root rw
  SegvAnalysis:
   Segfault happened at: 0x7f2b54231cf0:mov(%rdi),%rax
   PC (0x7f2b54231cf0) ok
   source "(%rdi)" (0x3130383130303038) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
   ?? ()
   ?? ()
  Title: bluetoothd crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F4:5C:89:C2:92:3C  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING 
RX bytes:1054 acl:0 sco:0 events:59 errors:0
TX bytes:2965 acl:0 sco:0 commands:59 errors:0

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

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


[Kernel-packages] [Bug 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1

2018-10-05 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Audio streaming over bluetooth to Bose QC35 is highly unreliable on a
  MacBookPro12,1

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Streaming of audio files over bluetooth is not possible in Ubuntu
  17.10.

  Connecting a headphone requires several attempts.
  Then the sound settings have to be selected manually
  Even then, the sound offered is mono
  I tested with a Bose QC35.
  There is a sound profile that requires manual selection and offers stereo 
speakers.
  However, while testing left speaker gives reasonable results, testing the 
right speaker only produces cracking noise.
  Playback of music is virtually impossible (the stream is repeatedly 
interupted by voice anouncements of incoming calls ??? and reconnection attemts)

  To eliminate hardware issues I tested under macOS and the sound quality is 
excellent (even during working in a spread sheet and a word processor in 
parallel).
  => issues caused by the software stack

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 15:12:02 2017
  InstallationDate: Installed on 2017-09-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:32:75:9F:91:1E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0
TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0

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

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


[Kernel-packages] [Bug 1785020] Re: fsync is slow on later kernels with ext4 filesystms

2018-10-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  fsync is slow on later kernels with ext4 filesystms

Status in linux package in Ubuntu:
  Expired

Bug description:
  
  So this is a simple one, if I run the following code (see below) on Ubuntu 
18.04 (4.15.0-29-generic ) and against Ubuntu 16.04 ( 4.4.0-87-generic) I get 
two different results ; The question is why? It seems that fsync may be broken 
in the latest kernel and may well be broken as early as 4.10 ? This has huge 
implications around performance sensitive applications like mysql. 

  It also so worth noting that I'm running this against an ext4 filesystem with 
the following mount options
  rw,noatime,nodiratime,nobarrier,data=journal 

  
  4.4.0-87-generic - # time ./fsync 
  real 0m7.537s <-
  user 0m0.000s
  sys 0m1.060s <-

  
  4.15.0-29-generic - # time ./fsync
  real 1m38.299s <-
  user 0m0.013s
  sys 0m0.893s <-

  
  Linux buntu-1804 4.15.0-29-generic

  no sync() seconds:0.024438   writes per second:0.00
 sync() seconds:1.705764   writes per second:0.00

  real3m6.475s
  user0m0.006s
  sys 0m1.725s

  
  Linux ubuntu 4.4.0-87-generic

  no sync() seconds:0.012887   writes per second:0.01
 sync() seconds:0.736563   writes per second:0.00

  real0m8.945s
  user0m0.016s
  sys 0m0.732s



  
  #!/usr/bin/python
  import os, sys, mmap
  # Open a file
  fd = os.open( "/a/testfile", os.O_RDWR|os.O_CREAT|os.O_DIRECT )
  m = mmap.mmap(-1, 512)
  for i in range (1,1):
 os.lseek(fd,os.SEEK_SET,0)
 m[1] = "1"
 os.write(fd, m)
 os.fsync(fd)
  # Close opened file
  os.close( fd )

  
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  void withSync() {
  int f = open( "/a/t8" , O_RDWR | O_CREAT |O_DIRECT );
  lseek (f, 0, SEEK_SET );
  int records = 10*1000;
  clock_t ustart = clock();
  for(int i = 0; i < records; i++) {
  write(f, "012345678901234567890123456789" , 30);
  fsync(f);
  }
  clock_t uend = clock();
  close (f);
  printf("   sync() seconds:%lf   writes per second:%lf\n", 
((double)(uend-ustart))/(CLOCKS_PER_SEC), 
((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC));
  }

  void withoutSync() {
  int f = open( "/a/t10" , O_RDWR | O_CREAT | O_DIRECT );
  lseek (f, 0, SEEK_SET );
  int records = 10*1000;
  clock_t ustart = clock();
  for(int i = 0; i < records; i++) {
  write(f, "012345678901234567890123456789" , 30 );
  }
  clock_t uend = clock();
  close (f);
  printf("no sync() seconds:%lf   writes per second:%lf \n", 
((double)(uend-ustart))/(CLOCKS_PER_SEC), 
((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC));
  }

  int main(int argc, const char * argv[])
  {
  withoutSync();
  withSync();
  return 0;
  }

  
  Linux buntu-1804 4.15.0-29-generic

  no sync() seconds:0.024438   writes per second:0.00
 sync() seconds:1.705764   writes per second:0.00

  real3m6.475s
  user0m0.006s
  sys 0m1.725s

  
  Linux ubuntu 4.4.0-87-generic

  no sync() seconds:0.012887   writes per second:0.01
 sync() seconds:0.736563   writes per second:0.00

  real 0m8.945s
  user0m0.016s
  sys  0m0.732s

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

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


[Kernel-packages] [Bug 1785428] Re: wi-fi adapter not work Atheros Communications, Inc, I'm using ubuntu 18.04

2018-10-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  wi-fi adapter not work Atheros Communications, Inc, I'm using ubuntu
  18.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  Bus 001 Device 006: ID 0cf3:e300 Atheros Communications, Inc.

  ricardo@ricardolinux:~$ ifconfig 
  enp3s0: flags=4163  mtu 1500
  inet 192.168.0.11  netmask 255.255.255.0  broadcast 192.168.0.255
  inet6 fe80::8600:6ced:f190:1c4f  prefixlen 64  scopeid 0x20
  inet6 2804:14c:123:828a:b1af:bb38:98fa:66b6  prefixlen 64  scopeid 
0x0
  ether 54:e1:ad:72:10:0c  txqueuelen 1000  (Ethernet)
  RX packets 17245  bytes 14615254 (14.6 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 9810  bytes 1414975 (1.4 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 1395  bytes 114707 (114.7 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 1395  bytes 114707 (114.7 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ricardo1374 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-05 (1 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: LENOVO 81CQ
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=70240dc8-8f79-417d-845a-96f8312fab00 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4GCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4GCN31WW:bd09/27/2017:svnLENOVO:pn81CQ:pvrLenovoY720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoY720-15IKB:
  dmi.product.family: Y720-15IKB
  dmi.product.name: 81CQ
  dmi.product.version: Lenovo Y720-15IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ricardo1374 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-05 (1 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: LENOVO 81CQ
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=70240dc8-8f79-417d-845a-96f8312fab00 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4GCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4GCN31WW:bd09/27/2017:svnLENOVO:pn81CQ:pvrLenovoY720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoY720-15IKB:
  dmi.product.family: Y720-15IKB
  dmi.product.name: 81CQ
  dmi.product.version: Lenovo Y720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications 

[Kernel-packages] [Bug 1785554] Re: BUG: scheduling while atomic: Xorg/865/0x00000100

2018-10-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  BUG: scheduling while atomic: Xorg/865/0x0100

Status in linux package in Ubuntu:
  Expired

Bug description:
  unexpected error

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-6-generic 4.17.0-6.7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.17.0-6-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1896 F pulseaudio
   /dev/snd/controlC1:  ian1896 F pulseaudio
  Date: Mon Aug  6 18:02:20 2018
  Failure: oops
  InstallationDate: Installed on 2018-08-06 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=94d4a0a4-084d-4cfe-95ed-d689b51c557a ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8188eu
  Title: BUG: scheduling while atomic: Xorg/865/0x0100
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 144A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 65.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr059B11243010010020100:rvnHewlett-Packard:rn144A:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 059B11243010010020100
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1785472] Re: Kernel Bug

2018-10-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Kernel Bug

Status in linux package in Ubuntu:
  Expired

Bug description:
  System intermittently crashed / freezes with below logs.

  Version Signature : Ubuntu 4.15.0-29.31-generic 4.15.18 
  Description:Ubuntu 18.04.1 LTS and Ubuntu 17.10
  Release:18.04
  Platform : VMWare
  Error Occured when using vmxnet3 adapter, changed to E1000 adapter in midst 
of monitoring.

  Logs :

  Aug  5 19:48:32 10920.494211] kernel BUG at 
/build/linux-60XibS/linux-4.15.0/drivers/net/vmxnet3/vmxnet3_drv.c:1425!
  Aug  5 19:48:32 10920.496542] invalid opcode:  [#1] SMP PTI
  Aug  5 19:48:32 10920.497745] Modules linked in: iptable_filter isofs sb_edac 
coretemp intel_rapl_perf joydev input_leds serio_raw vmw_balloon shpchp mac_hid 
vmw_vsock_vmci_transport vsock vmw_vmci sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress 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 pcbc 
aesni_intel aes_x86_64 vmwgfx crypto_simd glue_helper cryptd ttm drm_kms_helper 
syscopyarea sysfillrect mptspi psmouse sysimgblt mptscsih fb_sys_fops pata_acpi 
mptbase ahci vmxnet3 drm libahci scsi_transport_spi i2c_piix4
  Aug  5 19:48:32 10920.507716] CPU: 7 PID: 52 Comm: ksoftirqd/7 Not tainted 
4.15.0-29-generic #31-Ubuntu
  Aug  5 19:48:32 10920.508680] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS 6.00 04/05/2016
  Aug  5 19:48:32 10920.509903] RIP: 0010:vmxnet3_rq_rx_complete+0x865/0xeb0 
[vmxnet3]
  Aug  5 19:48:32 10920.510521] RSP: 0018:b81ac1213d40 EFLAGS: 00010297
  Aug  5 19:48:32 10920.511077] RAX: 0001 RBX: 9b3baf0ecb90 
RCX: 9b3baddccf00
  Aug  5 19:48:32 10920.511631] RDX: 0012 RSI: 0040 
RDI: 0002
  Aug  5 19:48:32 10920.512184] RBP: b81ac1213da8 R08: 0028 
R09: 

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

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


[Kernel-packages] [Bug 1785620] Re: YouTube and other HTML5 videos lag and are choppy

2018-10-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  YouTube and other HTML5 videos lag and are choppy

Status in linux package in Ubuntu:
  Expired

Bug description:
  Title says it all. .23 doesn't do this, so it's definetly a kernel
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sam1617 F pulseaudio
   /dev/snd/controlC0:  sam1617 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  6 15:30:14 2018
  InstallationDate: Installed on 2018-05-04 (93 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude E5420
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=ad0c13a7-8e94-45ef-9a93-27865baa2140 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0H5TG2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd07/10/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-10-05 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is
  set on command line

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My new Elitebook, with the latest bios 1.03.01, refuses to boot any
  kernel later than 4.10 unless mce=off is appended to the kernel
  command line.  As in, there are no kernel messages at all after grub
  (yes, quiet and splash were removed from the command line).  Perhaps
  it crashes before the efifb kicks in?

  System operates fine if mce=off is added to the kernel command line
  (and iommu=soft, but that's a separate issue, and fails with kernel
  output in that case).

  I opened upstream bug here :
  https://bugzilla.kernel.org/show_bug.cgi?id=201291

  I bisected the problem down to this commit (and the few before it,
  which also added extra MCE output, but didn't actually crash):

  18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit
  commit 18807ddb7f88d4ac3797302bafb18143d573e66f
  Author: Yazen Ghannam 
  Date:   Tue Nov 15 15:13:53 2016 -0600

  x86/mce/AMD: Reset Threshold Limit after logging error

  The error count field in MCA_MISC does not get reset by hardware when the
  threshold has been reached. Software is expected to reset it. Currently,
  the threshold limit only gets reset during init or when a user writes to
  sysfs.

  If the user is not monitoring threshold interrupts and resetting
  the limit then the user will only see 1 interrupt when the limit is first
  hit. So if, for example, the limit is set to 10 then only 1 interrupt will
  be recorded after 10 errors even if 100 errors have occurred. The user may
  then assume that only 10 errors have occurred.

  There are threads online about this being related to the latest bios.
  The upstream bug has acpidump attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   2015 F pulseaudio
   /dev/snd/pcmC1D0p:   john   2015 F...m pulseaudio
   /dev/snd/controlC0:  john   2015 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 23:24:45 2018
  InstallationDate: Installed on 2018-09-30 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 745 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft 
mce=off
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  RfKill:
   1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q81 Ver. 01.03.01
  dmi.board.name: 83D5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 08.47.00
  dmi.chassis.asset.tag: 5CG838305Y
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 745 G5
  dmi.product.sku: 2MG23AV
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line

2018-10-05 Thread John Clemens
Note: bug also effect 18.04. Debian stable works, as it's based on 4.9.

** Description changed:

  My new Elitebook, with the latest bios 1.03.01, refuses to boot any
  kernel later than 4.10 unless mce=off is appended to the kernel command
  line.  As in, there are no kernel messages at all after grub (yes, quiet
  and splash were removed from the command line).  Perhaps it crashes
  before the efifb kicks in?
  
  System operates fine if mce=off is added to the kernel command line (and
  iommu=soft, but that's a separate issue, and fails with kernel output in
  that case).
  
  I opened upstream bug here :
  https://bugzilla.kernel.org/show_bug.cgi?id=201291
  
  I bisected the problem down to this commit (and the few before it, which
- also added extra MCE output, but didn't actually crash.
+ also added extra MCE output, but didn't actually crash):
  
- 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit
- commit 18807ddb7f88d4ac3797302bafb18143d573e66f
- Author: Yazen Ghannam 
- Date:   Tue Nov 15 15:13:53 2016 -0600
+ 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit
+ commit 18807ddb7f88d4ac3797302bafb18143d573e66f
+ Author: Yazen Ghannam 
+ Date:   Tue Nov 15 15:13:53 2016 -0600
  
- x86/mce/AMD: Reset Threshold Limit after logging error
- 
- The error count field in MCA_MISC does not get reset by hardware when the
- threshold has been reached. Software is expected to reset it. Currently,
- the threshold limit only gets reset during init or when a user writes to
- sysfs.
- 
- If the user is not monitoring threshold interrupts and resetting
- the limit then the user will only see 1 interrupt when the limit is first
- hit. So if, for example, the limit is set to 10 then only 1 interrupt will
- be recorded after 10 errors even if 100 errors have occurred. The user may
- then assume that only 10 errors have occurred.
+ x86/mce/AMD: Reset Threshold Limit after logging error
+ 
+ The error count field in MCA_MISC does not get reset by hardware when the
+ threshold has been reached. Software is expected to reset it. Currently,
+ the threshold limit only gets reset during init or when a user writes to
+ sysfs.
+ 
+ If the user is not monitoring threshold interrupts and resetting
+ the limit then the user will only see 1 interrupt when the limit is first
+ hit. So if, for example, the limit is set to 10 then only 1 interrupt will
+ be recorded after 10 errors even if 100 errors have occurred. The user may
+ then assume that only 10 errors have occurred.
  
  There are threads online about this being related to the latest bios.
  The upstream bug has acpidump attached.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  john   2015 F pulseaudio
-  /dev/snd/pcmC1D0p:   john   2015 F...m pulseaudio
-  /dev/snd/controlC0:  john   2015 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  john   2015 F pulseaudio
+  /dev/snd/pcmC1D0p:   john   2015 F...m pulseaudio
+  /dev/snd/controlC0:  john   2015 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 23:24:45 2018
  InstallationDate: Installed on 2018-09-30 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
-  Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 745 G5
  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 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft 
mce=off
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-8-generic N/A
-  linux-backports-modules-4.18.0-8-generic  N/A
-  linux-firmware1.175
+  linux-restricted-modules-4.18.0-8-generic N/A
+  

[Kernel-packages] [Bug 1796443] [NEW] HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line

2018-10-05 Thread John Clemens
Public bug reported:

My new Elitebook, with the latest bios 1.03.01, refuses to boot any
kernel later than 4.10 unless mce=off is appended to the kernel command
line.  As in, there are no kernel messages at all after grub (yes, quiet
and splash were removed from the command line).  Perhaps it crashes
before the efifb kicks in?

System operates fine if mce=off is added to the kernel command line (and
iommu=soft, but that's a separate issue, and fails with kernel output in
that case).

I opened upstream bug here :
https://bugzilla.kernel.org/show_bug.cgi?id=201291

I bisected the problem down to this commit (and the few before it, which
also added extra MCE output, but didn't actually crash.

18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit
commit 18807ddb7f88d4ac3797302bafb18143d573e66f
Author: Yazen Ghannam 
Date:   Tue Nov 15 15:13:53 2016 -0600

x86/mce/AMD: Reset Threshold Limit after logging error

The error count field in MCA_MISC does not get reset by hardware when the
threshold has been reached. Software is expected to reset it. Currently,
the threshold limit only gets reset during init or when a user writes to
sysfs.

If the user is not monitoring threshold interrupts and resetting
the limit then the user will only see 1 interrupt when the limit is first
hit. So if, for example, the limit is set to 10 then only 1 interrupt will
be recorded after 10 errors even if 100 errors have occurred. The user may
then assume that only 10 errors have occurred.

There are threads online about this being related to the latest bios.
The upstream bug has acpidump attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  john   2015 F pulseaudio
 /dev/snd/pcmC1D0p:   john   2015 F...m pulseaudio
 /dev/snd/controlC0:  john   2015 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  5 23:24:45 2018
InstallationDate: Installed on 2018-09-30 (5 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP EliteBook 745 G5
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft 
mce=off
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-8-generic N/A
 linux-backports-modules-4.18.0-8-generic  N/A
 linux-firmware1.175
RfKill:
 1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: r8822be
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2018
dmi.bios.vendor: HP
dmi.bios.version: Q81 Ver. 01.03.01
dmi.board.name: 83D5
dmi.board.vendor: HP
dmi.board.version: KBC Version 08.47.00
dmi.chassis.asset.tag: 5CG838305Y
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 745 G5
dmi.product.sku: 2MG23AV
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug cosmic staging

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

Title:
  HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is
  set on command line

Status in linux package in Ubuntu:
  New

Bug description:
  My new Elitebook, with the latest bios 1.03.01, refuses to boot any
  kernel later than 4.10 unless mce=off is appended to the kernel
  command line.  As in, there are no kernel messages at all after grub
  (yes, quiet and splash were removed from the command line).  Perhaps
  it crashes before the efifb kicks in?

  System operates fine if mce=off is added to the kernel command line
  (and iommu=soft, but that's a separate issue, and fails with kernel
  output in that case).

  I opened upstream bug here :
  https://bugzilla.kernel.org/show_bug.cgi?id=201291

  I bisected the problem down to this commit (and the few before it,
  which also added extra MCE output, but didn't actually crash.

  

[Kernel-packages] [Bug 1795256] Re: frequent crash of Ubuntu 18.04 with purple dotted screen or black screen error death

2018-10-05 Thread Aravind R
Mr. Joseph Salisbury,

I am trying v4.19-rc6

The first problem with this built is that virtual box not working.

Sender : systemd

Failed to start LSB: VirtualBox Linux kernel module.

Priority: 3

I will confirm you tomorrow. And sorry for the delay.

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

Title:
  frequent crash of Ubuntu 18.04 with purple dotted screen or black
  screen error death

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I had same problem in Ubuntu 16.04.3. But not frequent. It was
  happening when I play HD video. But now after installing Ubuntu 18.04
  the same problem even when browsing. Its too frequent.

  I have tried to reinstall Intel-microcode, bumblebee, xorg video
  drivers. No improvement.

  The system don't crash even show error message in dmesg and
  journalctl.

  aravind@comp:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1)
  00:1d.3 PCI bridge: Intel Corporation Device 9d1b (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation Device 179c (rev ff)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

  
  aravind@comp:~$ sudo lshw
  [sudo] password for aravind: 
  comp
  description: Notebook
  product: Aspire E5-575G (Aspire E5-575G_115F_1.25)
  vendor: Acer
  version: V1.25
  serial: NXGDWSI034717145457600
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: chassis=notebook family=KBL sku=Aspire E5-575G_115F_1.25 
uuid=BB9943DA-A143-49C0-8D00-A81E84883CFD
*-core
 description: Motherboard
 product: Ironman_SK
 vendor: Acer
 physical id: 0
 version: V1.25
 serial: NBGD411006717145457600
 slot: Type2 - Board Chassis Location
   *-firmware
description: BIOS
vendor: Insyde Corp.
physical id: 0
version: V1.25
date: 03/03/2017
size: 128KiB
capacity: 4544KiB
capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
   *-cpu
description: CPU
product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify 

[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick

2018-10-05 Thread Newell Jensen
** Merge proposal unlinked:
   https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053

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

Title:
  Sharkoon Fireglider mouse is wrongly detected as a joystick

Status in udev:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-input-evdev

  I've been programming a game in SDL and I was surprised that SDL was
  reporting that 1 joystick was connected when there were none. SDL
  provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows
  one joystick connected:

  by-idevent0  event2  event4  event6  event8  micemouse1
  by-path  event1  event3  event5  event7  js0 mouse0

  lsusb shows my mouse as:

  Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd

  Unplugging the mouse makes /dev/input/js0 disappear.
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 10.10
  InstallationMedia: elementary 0.2 Jupiter - Release i386
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Tags: maverick
  Uname: Linux 2.6.37-02063706-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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


[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)

2018-10-05 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc6

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

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

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

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

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

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

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

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

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

Title:
  Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
  18.04)

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

Bug description:
  Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel
  4.13 to the Kernel 4.15.0-24-generic.

  On a "Dell PowerEdge R330" server with a network adapter "Intel
  Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network
  card no longer works and permanently displays these three lines :

  
  [   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, 
NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
  [   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
  [   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

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

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


[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick

2018-10-05 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053

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

Title:
  Sharkoon Fireglider mouse is wrongly detected as a joystick

Status in udev:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-input-evdev

  I've been programming a game in SDL and I was surprised that SDL was
  reporting that 1 joystick was connected when there were none. SDL
  provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows
  one joystick connected:

  by-idevent0  event2  event4  event6  event8  micemouse1
  by-path  event1  event3  event5  event7  js0 mouse0

  lsusb shows my mouse as:

  Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd

  Unplugging the mouse makes /dev/input/js0 disappear.
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 10.10
  InstallationMedia: elementary 0.2 Jupiter - Release i386
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Tags: maverick
  Uname: Linux 2.6.37-02063706-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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


[Kernel-packages] [Bug 1796433] Re: Ubuntu 18.10 regression: nvidia driver does not work

2018-10-05 Thread Cristian Aravena Romero
Hello,

I'm confirming this report for dmesg

Best regards,
--
Cristian Aravena Romero (caravena)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu 18.10 regression: nvidia driver does not work

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Problems started after upgrade to 18.10 and first reboot.
  Symptoms:
  * Login screen appears
  * After providing credentials desktop does not start

  Part of dmesg:
  -
  ...
  [   10.482929] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more than PCI Bus :00 [mem 0x000c-0x000d window]
  [   10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping 
multiple BARs
  [   10.801510] [ cut here ]
  [   10.801512] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
  [   10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc 
nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) 
aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi 
intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath 
snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf 
ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me 
sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi 
sch_fq_codel
  [   10.801559]  nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport 
ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic 
usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii
  [   10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P   OE 
4.18.0-8-generic #9-Ubuntu
  ...
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  6 02:03:52 2018
  InstallationDate: Installed on 2016-01-06 (1003 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+subscriptions

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


[Kernel-packages] [Bug 1796433] [NEW] Ubuntu 18.10 regression: nvidia driver does not work

2018-10-05 Thread Alexey Balmashnov
Public bug reported:

Problems started after upgrade to 18.10 and first reboot.
Symptoms:
* Login screen appears
* After providing credentials desktop does not start

Part of dmesg:
-
...
[   10.482929] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more than PCI Bus :00 [mem 0x000c-0x000d window]
[   10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping 
multiple BARs
[   10.801510] [ cut here ]
[   10.801512] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
[   10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
[   10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc 
nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) 
aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi 
intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath 
snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf 
ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me 
sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi 
sch_fq_codel
[   10.801559]  nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport 
ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic 
usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii
[   10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P   OE 
4.18.0-8-generic #9-Ubuntu
...
-

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nvidia-driver-390 (not installed)
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  6 02:03:52 2018
InstallationDate: Installed on 2016-01-06 (1003 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: nvidia-graphics-drivers-390
UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic

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

Title:
  Ubuntu 18.10 regression: nvidia driver does not work

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Problems started after upgrade to 18.10 and first reboot.
  Symptoms:
  * Login screen appears
  * After providing credentials desktop does not start

  Part of dmesg:
  -
  ...
  [   10.482929] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more than PCI Bus :00 [mem 0x000c-0x000d window]
  [   10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping 
multiple BARs
  [   10.801510] [ cut here ]
  [   10.801512] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
  [   10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc 
nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) 
aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi 
intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath 
snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf 
ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me 
sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi 
sch_fq_codel
  [   10.801559]  nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport 
ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic 
usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii
  [   10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P   OE 
4.18.0-8-generic #9-Ubuntu
  ...
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: 

[Kernel-packages] [Bug 1796433] Re: Ubuntu 18.10 regression: nvidia driver does not work

2018-10-05 Thread Alexey Balmashnov
** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+attachment/5197786/+files/dmesg.log

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

Title:
  Ubuntu 18.10 regression: nvidia driver does not work

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Problems started after upgrade to 18.10 and first reboot.
  Symptoms:
  * Login screen appears
  * After providing credentials desktop does not start

  Part of dmesg:
  -
  ...
  [   10.482929] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more than PCI Bus :00 [mem 0x000c-0x000d window]
  [   10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping 
multiple BARs
  [   10.801510] [ cut here ]
  [   10.801512] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
  [   10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc 
nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) 
aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi 
intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath 
snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf 
ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me 
sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi 
sch_fq_codel
  [   10.801559]  nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport 
ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic 
usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii
  [   10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P   OE 
4.18.0-8-generic #9-Ubuntu
  ...
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  6 02:03:52 2018
  InstallationDate: Installed on 2016-01-06 (1003 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+subscriptions

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


[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

2018-10-05 Thread Andy Smith
Successful boot with kernel from bionic-proposed.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

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

Bug description:
  == SRU Justification ==
  After an upgrade to Bionic, the bug reporter states the 32-bit kernel
  does not boot under Xen PV mode.  This bug does not affect 64-bit
  kernels and if fixed by mainline commit 6a92b11169a6.

  == Fix ==
  6a92b11169a6 ("x86/EISA: Don't probe EISA bus for Xen PV guests")

  == Regression Potential ==
  Low.  This commit only affects x86 kernels.  This commit has also been cc'd 
to upstream stable, so it has had
  additional upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it now 
refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 

  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

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


[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

2018-10-05 Thread Andy Smith
Successful boot with kernel from bionic-proposed.

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

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

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

Bug description:
  == SRU Justification ==
  After an upgrade to Bionic, the bug reporter states the 32-bit kernel
  does not boot under Xen PV mode.  This bug does not affect 64-bit
  kernels and if fixed by mainline commit 6a92b11169a6.

  == Fix ==
  6a92b11169a6 ("x86/EISA: Don't probe EISA bus for Xen PV guests")

  == Regression Potential ==
  Low.  This commit only affects x86 kernels.  This commit has also been cc'd 
to upstream stable, so it has had
  additional upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it now 
refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 

  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

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


[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2018-10-05 Thread Guilherme G. Piccoli
Hi Roy, thanks for your quick response. First thing, I'd like to ask you
to attach the output of "lspci -vvv" and "dmidecode" in this LP so we
can validate the adapters and be sure they are exactly the same, and
also the motherboard type. Run both commands as root user.

After that, i'll ask you to reproduce the issue and attach the output of
"dmesg" command right after reproduction. If you can also elaborate more
about the test you're running, I'd really be glad.

I'll then provide you custom commands to use the kernel trace system to infer 
more about the issue. One final thing: are you willing to test with mainline 
kernel in order to check if there's some upstream fix for your instance of the 
issue?
If so, you can get it here: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
This PPA provides a build from kernel 4.18.

Thanks in advance,


Guilherme

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

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

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

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

** Summary changed:

- timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency
+ sysfs test ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

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

Title:
  sysfs test ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  

[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded

2018-10-05 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Medium => High

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

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

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

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

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  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 

[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded

2018-10-05 Thread Joseph Salisbury
@Ridsai,

Are you still see this bug with the latest updates applied?

** Tags added: kernel-key

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

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

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

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

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

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 

[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

2018-10-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
  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/1795583/+subscriptions

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


[Kernel-packages] [Bug 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker

2018-10-05 Thread Seth Forshee
** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.18.0-1003.3 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

Title:
  linux-kvm: 4.18.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  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 --
  kernel-master-bug: 1796346

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

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


[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

2018-10-05 Thread Guillaume Penin
Sorry, i'm not able to run apport through our enterprise Network.

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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


[Kernel-packages] [Bug 1795568] Re: linux-azure: 4.15.0-1026.27 -proposed tracker

2018-10-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** 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 --
  kernel-stable-master-bug: 1795564
  phase: Packaging
+ kernel-stable-phase-changed:Friday, 05. October 2018 19:33 UTC
+ kernel-stable-phase:Uploaded

** 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 --
  kernel-stable-master-bug: 1795564
- phase: Packaging
- kernel-stable-phase-changed:Friday, 05. October 2018 19:33 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-azure: 4.15.0-1026.27 -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:
  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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  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 --
  kernel-stable-master-bug: 1795564
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)

2018-10-05 Thread Vivien GUEANT
** Summary changed:

- i40e driver does not work with kernel 4.15
+ Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)

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

Title:
  Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
  18.04)

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel
  4.13 to the Kernel 4.15.0-24-generic.

  On a "Dell PowerEdge R330" server with a network adapter "Intel
  Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network
  card no longer works and permanently displays these three lines :

  
  [   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, 
NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
  [   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
  [   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

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

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


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

2018-10-05 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can use the system for a while, then at random, the screen blinks and 
freezes. Must reboot.
  Seems to happen both with Wayland and Xorg.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   2039 F pulseaudio
   /dev/snd/controlC1:  greg   2039 F pulseaudio
  Date: Tue Oct  2 15:56:23 2018
  Failure: oops
  InstallationDate: Installed on 2018-09-28 (7 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-UD4-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1779756] Re: i40e driver does not work with kernel 4.15

2018-10-05 Thread Vivien GUEANT
Cf bug https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1795587

Intel released the 6.01 Firmware for the Intel XL710 network cards. As
stated in the feature support matrix [1] in the table 9 on page 18, the
minimum kernel driver version for the 6.01 Firmware i40e must be 2.1.26,
the recent driver version is 2.4.10 [2]

The i40 driver version included in the 4.15.0-36 (Bionic, LTS) is
2.1.14-k.

$ uname -a
Linux ubuntu-bionic 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

$ modinfo i40e
filename: 
/lib/modules/4.15.0-36-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko
version: 2.1.14-k
license: GPL
description: Intel(R) Ethernet Connection XL710 Network Driver

Release notes: [3] [4] [5] [6] [7]

The firmware 6.01 introduce better performance for DPDK and SR-IOV
applications for those cards, and NFV application workloads would
perform better.

[1] Intel® Ethernet Controller X710/ XXV710/XL710 Feature Support Matrix
https://www.intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-matrix.pdf

[2] Intel® Network Adapter Driver for PCIe* 40 Gigabit Ethernet Network 
Connections Under Linux*
https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=75021

[3] Intel(R) Network Connections Software Version 23.2 Release Notes
https://downloadmirror.intel.com/24411/eng/readme.txt

[4] Intel(R) Network Connections Software Version 23.1 Release Notes
https://downloadmirror.intel.com/27869/eng/readme.txt

[5] Intel(R) Network Connections Software Version 22.10 Release Notes
https://downloadmirror.intel.com/27547/eng/readme.txt

[6] Intel(R) Network Connections Software Version 22.9 Release Notes
https://downloadmirror.intel.com/27547/eng/readme.txt

[7] Intel(R) Network Connections Software Version 22.6 Release Notes
https://downloadmirror.intel.com/27189/eng/readme.txt

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

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

Title:
  i40e driver does not work with kernel 4.15

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel
  4.13 to the Kernel 4.15.0-24-generic.

  On a "Dell PowerEdge R330" server with a network adapter "Intel
  Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network
  card no longer works and permanently displays these three lines :

  
  [   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, 
NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
  [   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
  [   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

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

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


[Kernel-packages] [Bug 1796385] [NEW] watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]

2018-10-05 Thread Bounty
Public bug reported:

I can use the system for a while, then at random, the screen blinks and 
freezes. Must reboot.
Seems to happen both with Wayland and Xorg.

ProblemType: KernelOops
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  greg   2039 F pulseaudio
 /dev/snd/controlC1:  greg   2039 F pulseaudio
Date: Tue Oct  2 15:56:23 2018
Failure: oops
InstallationDate: Installed on 2018-09-28 (7 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23
dmi.board.asset.tag: Default string
dmi.board.name: X99-UD4-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-kerneloops cosmic kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]

Status in linux package in Ubuntu:
  New

Bug description:
  I can use the system for a while, then at random, the screen blinks and 
freezes. Must reboot.
  Seems to happen both with Wayland and Xorg.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   2039 F pulseaudio
   /dev/snd/controlC1:  greg   2039 F pulseaudio
  Date: Tue Oct  2 15:56:23 2018
  Failure: oops
  InstallationDate: Installed on 2018-09-28 (7 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-UD4-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications 

[Kernel-packages] [Bug 1779756] [NEW] i40e driver does not work with kernel 4.15

2018-10-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13
to the Kernel 4.15.0-24-generic.

On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet
Converged Network Adapter X710-DA2" (driver i40e) the network card no
longer works and permanently displays these three lines :


[   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 
0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
[   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
[   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

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


** Tags: 4.15.0-24-generic kernel
-- 
i40e driver does not work with kernel 4.15
https://bugs.launchpad.net/bugs/1779756
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-firmware in Ubuntu.

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


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

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

apport-collect 1796376

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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


[Kernel-packages] [Bug 1796376] [NEW] Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

2018-10-05 Thread Guillaume Penin
Public bug reported:

Since the following linux-cloud-tools-common package versions :

Xenial : 4.4.0-135.161
Bionic : 4.15.0-34.37

the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

- Package state after reboot :

iFR linux-cloud-tools-common  4.15.0-34.37
all  Linux kernel version specific cloud tools for version
4.15.0

- Unattended-upgrades dpkg logs :

Log started: 2018-10-05  17:59:04
(Reading database ... 52043 files and directories currently installed.)
Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
Log ended: 2018-10-05  18:00:54

- Impact :

The current impact is very important as all security updates are blocked
until you manually fix each server with :

dpkg --configure -a
apt install --only-upgrade linux-cloud-tools-common

- Workaround/Fix :

As a simple straightforward fix, replacing :

Before=shutdown.target cloud-init-local.service walinuxagent.service

with :

Before=shutdown.target walinuxagent.service

makes the package upgradable during shutdown.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1796376

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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


[Kernel-packages] [Bug 1795568] Re: linux-azure: 4.15.0-1026.27 -proposed tracker

2018-10-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

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

Title:
  linux-azure: 4.15.0-1026.27 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  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 --
  kernel-stable-master-bug: 1795564
  phase: Packaging

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

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


[Kernel-packages] [Bug 1389077] Re: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU

2018-10-05 Thread Jerry Zhao
happened to my asus n56 laptop 16.04 4.4.0-134-generic today.

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

Title:
  [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from KUbuntu 14.04 to 14.10. Immediately, while playing
  minecraft with my daughter, I noticed the game was running very
  slowly. Even after closing the game, my web browsing slowed to a
  crawl.

  Looking at the processes in top, I noticed there were 4 tasks called
  kidle_inject running at 50% CPU each. After spending a long time
  figuring out what caused this, I found out this is caused by the Intel
  Powerclamp driver. I never did anything to enable this, and haven't
  observed this slowdown before the upgrade.

  I found the powerclamp driver in the
  /sys/class/thermal/cooling_device5 directory:

  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat type 
  intel_powerclamp
  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat cur_state 
  -1
  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat max_state 
  50

  I tried to echo 0 to cur_state, but it still reported -1 when I catted
  the value.

  There seems to be no obvious way to disable this, and this should not
  have been enabled in the first place.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bkat   2780 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Nov  3 23:16:04 2014
  HibernationDevice: RESUME=UUID=35e1d874-a3bd-4227-acab-16f3e929d993
  InstallationDate: Installed on 2012-04-22 (925 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=743f1686-bfe7-4e32-911d-5371633ccec8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-11-03 (0 days ago)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.09
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.1A
  dmi.chassis.asset.tag: CNU1284V1X
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4530s
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1793430] Re: Page leaking in cachefiles_read_backing_file while vmscan is active

2018-10-05 Thread Kiran Kumar Modukuri
we are trying to get hardware resource to test this before 10/9. will
keep you posted.

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

Title:
  Page leaking in cachefiles_read_backing_file while vmscan is active

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification
  -

  [Description]
  In a heavily loaded system where the system pagecache is nearing memory 
limits and fscache is enabled, pages can be leaked by fscache while trying read 
pages from cachefiles backend. This can happen because two applications can be 
reading same page from a single mount, two threads can be trying to read the 
backing page at same time. This results in one of the thread finding that a 
page for the backing file or netfs file is already in the radix tree. During 
the error handling cachefiles does not cleanup the reference on backing page, 
leading to page leak.
  
  [Fix]
  The fix is straightforward, to decrement the reference when error is 
encounterd.
  
  [Testing]
  A user has tested the fix using following method for 12+ hrs.
  
  1) mkdir -p /mnt/nfs ; mount -o vers=3,fsc :/export /mnt/nfs
  2) create 1 files of 2.8MB in a NFS mount.
  3) start a thread to simulate heavy VM presssure
 (while true ; do echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done)&
  4) start multiple parallel reader for data set at same time
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 ..
 ..
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
  5) finally check using cat /proc/fs/fscache/stats | grep -i pages ;
 free -h , cat /proc/meminfo and page-types -r -b lru
 to ensure all pages are freed.

  [Regression Potential]
  Limited to cachefiles.

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

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


[Kernel-packages] [Bug 1795568] Re: linux-azure: 4.15.0-1026.27 -proposed tracker

2018-10-05 Thread Marcelo Cerri
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.15.0-1026.27 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux-azure: 4.15.0-1026.27 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  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 --
  kernel-stable-master-bug: 1795564
  phase: Packaging

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Colin Ian King
And reproducible way back to 4.4.0-21-lowlatency too

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| [stdout] [ 1422.281009]  [] ? 
find_vma+0x68/0x70
  16:50:05 DEBUG| 

[Kernel-packages] [Bug 1789518] Re: automounting MTP or USB storage devices no longer works.

2018-10-05 Thread b
Tried again today and MTP automounts fine. No idea what was wrong
before.

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

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

Title:
  automounting MTP or USB storage devices no longer works.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrading from xenial to bionic, USB (both MTP and mass storage)
  devices will not automount.

  syslog shows the usb device is found and recognized as a storage
  device:

  Aug 28 16:49:18 insitu kernel: [ 4412.072025] usb 1-8: new high-speed USB 
device number 18 using ehci-pci
  Aug 28 16:49:19 insitu kernel: [ 4412.229198] usb 1-8: New USB device found, 
idVendor=0421, idProduct=01c7
  Aug 28 16:49:19 insitu kernel: [ 4412.229202] usb 1-8: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Aug 28 16:49:19 insitu kernel: [ 4412.229204] usb 1-8: Product: N900 (Storage 
Mode)
  Aug 28 16:49:19 insitu kernel: [ 4412.229206] usb 1-8: Manufacturer: Nokia
  Aug 28 16:49:19 insitu kernel: [ 4412.229211] usb 1-8: SerialNumber: 
372041756775
  Aug 28 16:49:19 insitu kernel: [ 4412.231642] usb-storage 1-8:1.0: USB Mass 
Storage device detected
  Aug 28 16:49:19 insitu kernel: [ 4412.233887] scsi host7: usb-storage 1-8:1.0
  Aug 28 16:49:19 insitu mtp-probe: checking bus 1, device 18: 
"/sys/devices/pci:00/:00:10.4/usb1/1-8"
  Aug 28 16:49:19 insitu mtp-probe: bus: 1, device: 18 was not an MTP device
  Aug 28 16:49:19 insitu upowerd[1485]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:10.4/usb1/1-8/1-8:1.0
  Aug 28 16:49:19 insitu upowerd[1485]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:10.4/usb1/1-8
  Aug 28 16:49:20 insitu kernel: [ 4413.251860] scsi 7:0:0:0: Direct-Access 
NokiaN900  031 PQ: 0 ANSI: 2
  Aug 28 16:49:20 insitu kernel: [ 4413.252743] scsi 7:0:0:1: Direct-Access 
NokiaN900  031 PQ: 0 ANSI: 2
  Aug 28 16:49:20 insitu kernel: [ 4413.254638] sd 7:0:0:0: Attached scsi 
generic sg3 type 0
  Aug 28 16:49:20 insitu kernel: [ 4413.254946] sd 7:0:0:1: Attached scsi 
generic sg4 type 0
  Aug 28 16:49:20 insitu kernel: [ 4413.255201] sd 7:0:0:0: Power-on or device 
reset occurred
  Aug 28 16:49:20 insitu kernel: [ 4413.255822] sd 7:0:0:1: Power-on or device 
reset occurred
  Aug 28 16:49:20 insitu kernel: [ 4413.260481] sd 7:0:0:1: [sdd] Attached SCSI 
removable disk
  Aug 28 16:49:20 insitu kernel: [ 4413.261109] sd 7:0:0:0: [sdc] Attached SCSI 
removable disk
  Aug 28 16:49:26 insitu kernel: [ 4419.523221] sd 7:0:0:0: [sdc] 56631296 
512-byte logical blocks: (29.0 GB/27.0 GiB)
  Aug 28 16:49:26 insitu kernel: [ 4419.523952] sd 7:0:0:0: [sdc] Write cache: 
enabled, read cache: enabled, doesn't support DPO or FUA
  Aug 28 16:49:26 insitu kernel: [ 4419.719652]  sdc:

  sdc is never mounted; I can mount it manually with:

  sudo mount /dev/sdc /mnt/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1490 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Aug 28 16:45:48 2018
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=13df1544-3ecd-4a0b-bea6-347f3f27871d
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2010-11-05 (2853 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=0ab4bde0-8376-4cbe-9bc0-af6c3a7936bd ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  Symptom: storage
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (12 days ago)
  dmi.bios.date: 10/06/2005
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1015.002
  dmi.board.name: A8V Deluxe
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1795486] Re: Cosmic update to 4.18.11 stable release

2018-10-05 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Cosmic update to 4.18.11 stable release

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.18.11 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.18.11 stable release shall be
  applied:

  
  Linux 4.18.11
  spi: Fix double IDR allocation with DT aliases
  iw_cxgb4: only allow 1 flush on user qps
  vmw_balloon: include asm/io.h
  sched/fair: Fix vruntime_normalized() for remote non-migration wakeup
  ext4, dax: set ext4_dax_aops for dax files
  ext4, dax: add ext4_bmap to ext4_dax_aops
  ext4: show test_dummy_encryption mount option in /proc/mounts
  ext4: don't mark mmp buffer head dirty
  ext4: fix online resizing for bigalloc file systems with a 1k block size
  ext4: fix online resize's handling of a too-small final block group
  ext4: recalucate superblock checksum after updating free blocks/inodes
  ext4: avoid arithemetic overflow that can trigger a BUG
  ext4: avoid divide by zero fault when deleting corrupted inline directories
  ext4: check to make sure the rename(2)'s destination is not freed
  tty: vt_ioctl: fix potential Spectre v1
  drm/amdgpu: add new polaris pci id
  drm: udl: Destroy framebuffer only if it was initialized
  drm/vc4: Fix the "no scaling" case on multi-planar YUV formats
  drm/nouveau/drm/nouveau: Prevent handling ACPI HPD events too early
  drm/nouveau/drm/nouveau: Use pm_runtime_get_noresume() in connector_detect()
  drm/nouveau/drm/nouveau: Fix deadlock with fb_helper with async RPM requests
  drm/nouveau/drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement
  drm/nouveau/drm/nouveau: Don't forget to cancel hpd_work on suspend/unload
  drm/nouveau: Fix deadlocks in nouveau_connector_detect()
  drm/nouveau: Remove duplicate poll_enable() in pmops_runtime_suspend()
  drm/nouveau: Only write DP_MSTM_CTRL when needed
  drm/nouveau: Reset MST branching unit before enabling
  drm/i915/bdw: Increase IPS disable timeout to 100ms
  ocfs2: fix ocfs2 read block panic
  libata: mask swap internal and hardware tag
  Revert "ubifs: xattr: Don't operate on deleted inodes"
  scsi: target: iscsi: Use bin2hex instead of a re-implementation
  scsi: target: iscsi: Use hex2bin instead of a re-implementation
  Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct 
member name"
  bpf/verifier: disallow pointer subtraction
  Revert "rpmsg: core: add support to power domains for devices"
  mm: shmem.c: Correctly annotate new inodes for lockdep
  mm: disable deferred struct page for 32-bit arches
  fork: report pid exhaustion correctly
  crypto: x86/aegis,morus - Do not require OSXSAVE for SSE2
  ring-buffer: Allow for rescheduling when removing pages
  Revert "PCI: Add ACS quirk for Intel 300 series"
  spi: fix IDR collision on systems with both fixed and dynamic SPI bus numbers
  xen/x86/vpmu: Zero struct pt_regs before calling into sample handling code
  xen/netfront: don't bug in case of too many frags
  platform/x86: alienware-wmi: Correct a memory leak
  platform/x86: dell-smbios-wmi: Correct a memory leak
  mtd: rawnand: denali: fix a race condition when DMA is kicked
  mtd: devices: m25p80: Make sure the buffer passed in op is DMA-able
  ALSA: oxfw: fix memory leak of private data
  ALSA: oxfw: fix memory leak of discovered stream formats at error path
  ALSA: oxfw: fix memory leak for model-dependent data at error path
  ALSA: fireworks: fix memory leak of response buffer at error path
  ALSA: firewire-tascam: fix memory leak of private data
  ALSA: firewire-digi00x: fix memory leak of private data
  ALSA: fireface: fix memory leak in ff400_switch_fetching_mode()
  ALSA: emu10k1: fix possible info leak to userspace on SNDRV_EMU10K1_IOCTL_INFO
  ALSA: bebob: use address returned by kmalloc() instead of kernel stack for 
streaming DMA mapping
  ALSA: bebob: fix memory leak for M-Audio FW1814 and ProjectMix I/O at error 
path
  ASoC: uapi: fix sound/skl-tplg-interface.h userspace compilation errors
  ASoC: rsnd: fixup not to call clk_get/set under non-atomic
  ASoC: tas6424: Save last fault register even when clear
  ASoC: cs4265: fix MMTLR Data switch control
  ASoC: wm9712: fix replace codec to component
  NFC: Fix the number of pipes
  NFC: Fix possible 

[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

2018-10-05 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled on this 6bpp display. This issue was not present on
  non-HWE Ubuntu 16.04, and it showed up after I upgraded to Ubuntu
  18.04. There was already a very similar bug #1749420 that had a fix
  released, however, because the make and model of an LCD screen in that
  case was different, the quirk added to the kernel did not address the
  problem that affects my machine. The cause of this issue is probably
  the same, since I have checked that pre-4.8.0-rc2 kernels handled
  dithering correctly, and 4.8.0-rc2 and later kernels already had the
  bug described. I believe that adding quirk for an another type of
  display may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Colin Ian King
And is reproduced in previous kernel 4.4.0-137-lowlatency too, so not a
regression on -138

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| [stdout] [ 1422.281009]  [] ? 

[Kernel-packages] [Bug 1796346] Re: linux: 4.18.0-9.10 -proposed tracker

2018-10-05 Thread Seth Forshee
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.18.0-9.10 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

Title:
  linux: 4.18.0-9.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  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: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge)
  derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 
1796351 (linux-gcp), bug 1796353 (linux-kvm)

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Colin Ian King
..after this hangs, I see:

[  261.473664] Oops:  [#1] PREEMPT SMP 
[  261.520488] Modules linked in: ipmi_ssif ipmi_devintf kvm_amd kvm dcdbas 
irqbypass input_leds serio_raw joydev amd64_edac_mod edac_mce_amd fam15h_power 
edac_core k10temp ipmi_si shpchp i2c_piix4 ipmi_msghandler 8250_fintek mac_hid 
acpi_power_meter 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 
hid_generic ghash_clmulni_intel aesni_intel mptsas aes_x86_64 pata_acpi lrw 
mptscsih gf128mul usbhid ahci glue_helper ablk_helper hid cryptd psmouse 
pata_atiixp mptbase libahci bnx2 scsi_transport_sas
[  262.283269] CPU: 3 PID: 1846 Comm: stress-ng Not tainted 
4.4.0-138-lowlatency #164-Ubuntu
[  262.381038] Hardware name: Dell Inc. PowerEdge R415/08WNM9, BIOS 1.9.3 
04/26/2012
[  262.470483] task: 8800d8323900 ti: 8800ded34000 task.ti: 
8800ded34000
[  262.559926] RIP: 0010:[]  [] 
kmem_cache_alloc+0x72/0x200
[  262.660817] RSP: 0018:8800ded37d18  EFLAGS: 00010206
[  262.724260] RAX:  RBX: 88020f630e10 RCX: 22a95403
[  262.809545] RDX: 22a95203 RSI: 22a95203 RDI: 0001a740
[  262.894829] RBP: 8800ded37d48 R08: 811d8ebc R09: 0001
[  262.980114] R10: 88021eff9000 R11:  R12: 02000200
[  263.065397] R13: 7ffcfd834000 R14: 880215003b00 R15: 880215003b00
[  263.150683] FS:  7f0599fc9700() GS:8802156c() 
knlGS:
[  263.247404] CS:  0010 DS:  ES:  CR0: 80050033
[  263.316050] CR2: 7ffcfd834000 CR3: d83a6000 CR4: 000406f0
[  263.401334] Stack:
[  263.425258]  7f059881dfff 88020f630e10  
8800d3d84f40
[  263.513690]  0001 8800dae95a40 8800ded37da0 
811d8ebc
[  263.602120]   88020ef23518 88020f630e88 
88020ef23590
[  263.690550] Call Trace:
[  263.719678]  [] anon_vma_clone+0x6c/0x200
[  263.786248]  [] anon_vma_fork+0x32/0x140
[  263.851779]  [] copy_process+0x1474/0x1c70
[  263.919385]  [] _do_fork+0x80/0x390
[  263.979714]  [] SyS_clone+0x19/0x20
[  264.040041]  [] entry_SYSCALL_64_fastpath+0x22/0xc1
[  264.117009] Code: 08 48 39 f2 75 e7 48 83 78 10 00 4c 8b 28 0f 84 40 01 00 
00 4d 85 ed 0f 84 37 01 00 00 49 63 46 20 49 8b 3e 48 8d 8a 00 02 00 00 <49> 8b 
5c 05 00 4c 89 e8 65 48 0f c7 0f 0f 94 c0 84 c0 74 ab 49 
[  264.343111] RIP  [] kmem_cache_alloc+0x72/0x200
[  264.415924]  RSP 
[  264.457529] CR2: 7ffcfd834000
[  264.497083] ---[ end trace 9af64fddce7496da ]---

and further opens seem to hang up.

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp 

[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Colin Ian King
It appears to hang when more than one thread is concurrently opening
/sys/kernel/security/tpm0/ascii_bios_measurements

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| 

[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Colin Ian King
..and after that last oops we get:

ubuntu@gonzo:~$ dmesg
Killed
ubuntu@gonzo:~$ top
Killed
ubuntu@gonzo:~$ ps
Killed

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| 

[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

2018-10-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-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/security-signoff
   Status: New => In Progress

** 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: 1795582
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 05. October 2018 15:32 UTC

** 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: 1795582
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 05. October 2018 15:32 UTC
+ 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/1795583

Title:
  linux-aws: 4.4.0-1032.35 -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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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 Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
  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/1795583/+subscriptions

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


[Kernel-packages] [Bug 1796346] Re: linux: -proposed tracker

2018-10-05 Thread Seth Forshee
** 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
+ 
+ backports: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge)
+ derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 
1796351 (linux-gcp), bug 1796353 (linux-kvm)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  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: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge)
  derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 
1796351 (linux-gcp), bug 1796353 (linux-kvm)

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

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


[Kernel-packages] [Bug 1796353] [NEW] linux-kvm: -proposed tracker

2018-10-05 Thread Seth Forshee
Public bug reported:

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 --
kernel-master-bug: 1796346

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-kvm (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.10.05 kernel-sru-derivative-of-1796346

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-kvm (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Tags added: kernel-sru-cycle-d2018.10.05

** Tags added: kernel-sru-derivative-of-1796346

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.

[Kernel-packages] [Bug 1796323] Re: linux-azure: -proposed tracker

2018-10-05 Thread Seth Forshee
** Changed in: kernel-sru-workflow
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Invalid

** Changed in: linux-azure (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Invalid

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 --
  kernel-master-bug: 1796319

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

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


[Kernel-packages] [Bug 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)

2018-10-05 Thread Dan Streetman
as I can't reproduce this, and I have heard no more reports of it, i'm
marking this as incomplete.  If anyone does actually still see this
problem with the latest (x/b/c) kernel, please add a comment to this
bug.

** Changed in: linux (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

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

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => 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/1772675

Title:
  Intel i40e PF reset due to incorrect MDD detection
  (continues...again...)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  [impact]

  The i40e driver sometimes causes a "malicious device" event that the
  firmware detects, which causes the firmware to reset the nic, causing
  an interruption in the network connection - which can cause further
  problems, e.g. if the interface is in a bond; the reset will at least
  cause a temporary interruption in network traffic.

  [fix]

  The fix for this is currently unknown.  As the "MDD event" is
  generated by the i40e firmware, and is completely undocumented, there
  is no way to tell what the i40e driver did to cause the MDD event.

  [test case]

  the bug is unfortunately very difficult to reproduce, but as shown in
  this (and previous) bug comments, some users of the i40e have traffic
  that can consistently reproduce the problem (although usually on the
  order of days, or longer, to reproduce). Reproducing is easily
  detected, as the nw traffic will be interrupted and the system logs
  will contain a message like:

  i40e :02:00.1: TX driver issue detected, PF reset issued

  [regression potential]

  unknown since the specific fix is unknown.

  [original description]

  This is a continuation from bug 1713553 and then bug 1723127; a patch
  was added in the first bug and then the second bug, to attempt to fix
  this, and it may have helped reduce the issue but appears not to have
  fixed it, based on more reports.

  See bug 1713553 and bug 1723127 for more details.

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

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


[Kernel-packages] [Bug 1796350] [NEW] linux-azure: -proposed tracker

2018-10-05 Thread Seth Forshee
Public bug reported:

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 --
kernel-master-bug: 1796346

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: Joshua R. Poulson (jrp)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-azure (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.10.05 kernel-sru-derivative-of-1796346

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-azure (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/stakeholder-signoff
 Assignee: (unassigned) => Joshua R. Poulson (jrp)

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: 

[Kernel-packages] [Bug 1796346] [NEW] linux: -proposed tracker

2018-10-05 Thread Seth Forshee
Public bug reported:

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: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge)
derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 1796351 
(linux-gcp), bug 1796353 (linux-kvm)

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.10.05 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Tags added: kernel-sru-cycle-d2018.10.05

** Tags added: kernel-sru-master-kernel

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 

[Kernel-packages] [Bug 1796351] [NEW] linux-gcp: -proposed tracker

2018-10-05 Thread Seth Forshee
Public bug reported:

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 --
kernel-master-bug: 1796346

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-gcp (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-gcp (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.10.05 kernel-sru-derivative-of-1796346

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-gcp (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Tags added: kernel-sru-cycle-d2018.10.05

** Tags added: kernel-sru-derivative-of-1796346

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing 

[Kernel-packages] [Bug 1796319] Re: linux: -proposed tracker

2018-10-05 Thread Seth Forshee
** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

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

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Invalid

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Invalid

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

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

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


[Kernel-packages] [Bug 1796319] [NEW] linux: -proposed tracker

2018-10-05 Thread Seth Forshee
Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.10.05 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Tags added: kernel-sru-cycle-d2018.10.05

** Tags added: kernel-sru-master-kernel

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  

[Kernel-packages] [Bug 1796323] [NEW] linux-azure: -proposed tracker

2018-10-05 Thread Seth Forshee
Public bug reported:

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 --
kernel-master-bug: 1796319

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Undecided
 Status: New

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

** Affects: linux-azure (Ubuntu Cosmic)
 Importance: Undecided
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-azure (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  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 --
  kernel-master-bug: 1796319

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

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


[Kernel-packages] [Bug 1795675] Re: kernel BUG at /build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!

2018-10-05 Thread Juerg Haefliger
Turns out that it is the cpu hotplug kernel selftest that crashes the kernel. 
Simply run:
$ bash tools/testing/selftests/cpu-hotplug/on-off-test.sh
from the Trusty 3.13 tree and the machine will fall over a couple of minutes 
later.

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

Title:
  kernel BUG at /build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!

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

Bug description:
  Running a set of autotests on Trusty with kernel 3.13.0-160-generic
  results in the following reproducible crash:

  [10870.247844] kernel BUG at 
/build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!
  [10870.255080] invalid opcode:  [#1] SMP 
  [10870.259339] Modules linked in: squashfs aufs quota_v2 quota_tree 
ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp 
bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat 
ebtables x_tables dm_crypt snd_hda_codec_realtek x86_pkg_temp_thermal coretemp 
kvm_intel kvm dell_wmi sparse_keymap snd_hda_intel crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_hda_codec aesni_intel dcdbas snd_hwdep 
aes_x86_64 snd_pcm snd_page_alloc lrw snd_timer gf128mul glue_helper 
dm_multipath e1000e(OX) snd ablk_helper cryptd scsi_dh ptp serio_raw pps_core 
joydev shpchp soundcore acpi_pad mac_hid lp parport zfs(POX) zunicode(POX) 
zcommon(POX) znvpair(POX) spl(OX) zavl(POX) nbd hid_generic usbhid hid ahci 
psmouse libahci wmi video [last unloaded: notifier_error_inject]
  [10870.341666] CPU: 3 PID: 0 Comm: swapper/3 Tainted: PW  OX 
3.13.0-160-generic #210-Ubuntu
  [10870.350483] Hardware name: Dell Inc. PowerEdge T30/07T4MC, BIOS 1.0.10 
09/28/2017
  [10870.358004] task: 880261d38000 ti: 880261d2e000 task.ti: 
880261d2e000
  [10870.365527] RIP: 0010:[]  [] 
add_timer_on+0x100/0x110
  [10870.373808] RSP: 0018:88026dd83e20  EFLAGS: 00010286
  [10870.379157] RAX:  RBX: 88026dd8f5e0 RCX: 
000100297ce1
  [10870.386321] RDX: 88026dd8 RSI: 0003 RDI: 
88026dd8f5e0
  [10870.393483] RBP: 88026dd83e50 R08: 0001002857e9 R09: 
88026dd83da0
  [10870.400648] R10: 88026dd83da4 R11: 88026dd83b2e R12: 
880261e04000
  [10870.407813] R13: 0100 R14: 0003 R15: 
88026dd8f5e0
  [10870.414977] FS:  () GS:88026dd8() 
knlGS:
  [10870.423103] CS:  0010 DS:  ES:  CR0: 80050033
  [10870.428886] CR2: 7ffef89bc3c8 CR3: 01c0e000 CR4: 
00360770
  [10870.437837] DR0:  DR1:  DR2: 

  [10870.445000] DR3:  DR6: fffe0ff0 DR7: 
0400
  [10870.452164] Stack:
  [10870.454229]  0c0a 88026dd8f5e0 000249f0 
0100
  [10870.461928]  8103ac10 0001 88026dd83e70 
8103aca4
  [10870.469630]  880261e04000 88026dc8f5e0 88026dd83ea8 
8107aab8
  [10870.477330] Call Trace:
  [10870.479828]   
  [10870.481796]  [] ? mce_cpu_restart+0x40/0x40
  [10870.487899]  [] mce_timer_fn+0x94/0x130
  [10870.493335]  [] call_timer_fn+0x38/0x150
  [10870.498856]  [] ? mce_cpu_restart+0x40/0x40
  [10870.504640]  [] run_timer_softirq+0x21f/0x310
  [10870.510602]  [] __do_softirq+0x101/0x310
  [10870.516130]  [] irq_exit+0x105/0x110
  [10870.521315]  [] smp_apic_timer_interrupt+0x53/0x70
  [10870.527709]  [] apic_timer_interrupt+0x191/0x1a0
  [10870.533927]   
  [10870.535894]  [] ? sched_clock_cpu+0xb5/0x100
  [10870.542083]  [] ? cpuidle_enter_state+0x57/0xd0
  [10870.548213]  [] ? cpuidle_enter_state+0x4d/0xd0
  [10870.554343]  [] cpuidle_idle_call+0xe4/0x240
  [10870.560212]  [] arch_cpu_idle+0xe/0x40
  [10870.565563]  [] cpu_startup_entry+0xc1/0x2c0
  [10870.571433]  [] start_secondary+0x24e/0x300
  [10870.577215] Code: 74 24 48 8b 03 66 0f 1f 44 00 00 48 8b 7b 08 48 83 c3 10 
4c 89 ea 4c 89 fe e8 2d 6f 6d 00 48 8b 03 48 85 c0 75 e5 e9 78 ff ff ff <0f> 0b 
48 8b 75 08 e8 05 fe ff ff e9 30 ff ff ff 0f 1f 44 00 00 
  [10870.600416] RIP  [] add_timer_on+0x100/0x110
  [10870.606350]  RSP 
  [10870.609887] ---[ end trace 4a4c8eb5651e9968 ]---
  [10870.619578] Kernel panic - not syncing: Fatal exception in interrupt
  [10870.626062] Kernel Offset: 0x0 from 0x8100 (relocation range: 
0x8000-0x9fff)

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

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


[Kernel-packages] [Bug 1795675] Re: kernel BUG at /build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!

2018-10-05 Thread Juerg Haefliger
Works fine in a VM.

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

Title:
  kernel BUG at /build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!

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

Bug description:
  Running a set of autotests on Trusty with kernel 3.13.0-160-generic
  results in the following reproducible crash:

  [10870.247844] kernel BUG at 
/build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!
  [10870.255080] invalid opcode:  [#1] SMP 
  [10870.259339] Modules linked in: squashfs aufs quota_v2 quota_tree 
ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp 
bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat 
ebtables x_tables dm_crypt snd_hda_codec_realtek x86_pkg_temp_thermal coretemp 
kvm_intel kvm dell_wmi sparse_keymap snd_hda_intel crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_hda_codec aesni_intel dcdbas snd_hwdep 
aes_x86_64 snd_pcm snd_page_alloc lrw snd_timer gf128mul glue_helper 
dm_multipath e1000e(OX) snd ablk_helper cryptd scsi_dh ptp serio_raw pps_core 
joydev shpchp soundcore acpi_pad mac_hid lp parport zfs(POX) zunicode(POX) 
zcommon(POX) znvpair(POX) spl(OX) zavl(POX) nbd hid_generic usbhid hid ahci 
psmouse libahci wmi video [last unloaded: notifier_error_inject]
  [10870.341666] CPU: 3 PID: 0 Comm: swapper/3 Tainted: PW  OX 
3.13.0-160-generic #210-Ubuntu
  [10870.350483] Hardware name: Dell Inc. PowerEdge T30/07T4MC, BIOS 1.0.10 
09/28/2017
  [10870.358004] task: 880261d38000 ti: 880261d2e000 task.ti: 
880261d2e000
  [10870.365527] RIP: 0010:[]  [] 
add_timer_on+0x100/0x110
  [10870.373808] RSP: 0018:88026dd83e20  EFLAGS: 00010286
  [10870.379157] RAX:  RBX: 88026dd8f5e0 RCX: 
000100297ce1
  [10870.386321] RDX: 88026dd8 RSI: 0003 RDI: 
88026dd8f5e0
  [10870.393483] RBP: 88026dd83e50 R08: 0001002857e9 R09: 
88026dd83da0
  [10870.400648] R10: 88026dd83da4 R11: 88026dd83b2e R12: 
880261e04000
  [10870.407813] R13: 0100 R14: 0003 R15: 
88026dd8f5e0
  [10870.414977] FS:  () GS:88026dd8() 
knlGS:
  [10870.423103] CS:  0010 DS:  ES:  CR0: 80050033
  [10870.428886] CR2: 7ffef89bc3c8 CR3: 01c0e000 CR4: 
00360770
  [10870.437837] DR0:  DR1:  DR2: 

  [10870.445000] DR3:  DR6: fffe0ff0 DR7: 
0400
  [10870.452164] Stack:
  [10870.454229]  0c0a 88026dd8f5e0 000249f0 
0100
  [10870.461928]  8103ac10 0001 88026dd83e70 
8103aca4
  [10870.469630]  880261e04000 88026dc8f5e0 88026dd83ea8 
8107aab8
  [10870.477330] Call Trace:
  [10870.479828]   
  [10870.481796]  [] ? mce_cpu_restart+0x40/0x40
  [10870.487899]  [] mce_timer_fn+0x94/0x130
  [10870.493335]  [] call_timer_fn+0x38/0x150
  [10870.498856]  [] ? mce_cpu_restart+0x40/0x40
  [10870.504640]  [] run_timer_softirq+0x21f/0x310
  [10870.510602]  [] __do_softirq+0x101/0x310
  [10870.516130]  [] irq_exit+0x105/0x110
  [10870.521315]  [] smp_apic_timer_interrupt+0x53/0x70
  [10870.527709]  [] apic_timer_interrupt+0x191/0x1a0
  [10870.533927]   
  [10870.535894]  [] ? sched_clock_cpu+0xb5/0x100
  [10870.542083]  [] ? cpuidle_enter_state+0x57/0xd0
  [10870.548213]  [] ? cpuidle_enter_state+0x4d/0xd0
  [10870.554343]  [] cpuidle_idle_call+0xe4/0x240
  [10870.560212]  [] arch_cpu_idle+0xe/0x40
  [10870.565563]  [] cpu_startup_entry+0xc1/0x2c0
  [10870.571433]  [] start_secondary+0x24e/0x300
  [10870.577215] Code: 74 24 48 8b 03 66 0f 1f 44 00 00 48 8b 7b 08 48 83 c3 10 
4c 89 ea 4c 89 fe e8 2d 6f 6d 00 48 8b 03 48 85 c0 75 e5 e9 78 ff ff ff <0f> 0b 
48 8b 75 08 e8 05 fe ff ff e9 30 ff ff ff 0f 1f 44 00 00 
  [10870.600416] RIP  [] add_timer_on+0x100/0x110
  [10870.606350]  RSP 
  [10870.609887] ---[ end trace 4a4c8eb5651e9968 ]---
  [10870.619578] Kernel panic - not syncing: Fatal exception in interrupt
  [10870.626062] Kernel Offset: 0x0 from 0x8100 (relocation range: 
0x8000-0x9fff)

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

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


[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2018-10-05 Thread Roy Thompson
Hi Guilherme,

Thanks for the response. I have several (3) quad port ASMedia 2142
PCIe/USB 3.1 cards installed in a Dell R740 rack server.  I am using the
standard Ubuntu 18.04 kernel (Linux dell-PowerEdge-R740
4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux).

For one of my applications, it runs a loop that opens and closes a high
speed connection to a USB device connected through the ASMedia board.
After this goes on for several minutes without any issues, I see this in
dmesg:

[Oct 5 10:12] xhci_hcd :be:00.0: WARN Set TR Deq Ptr cmd failed due to 
incorrect slot or ep state.
[  +3.418076] xhci_hcd :be:00.0: WARN Successful completion on short TX
[  +0.35] xhci_hcd :be:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 12 comp_code 1
[  +0.03] xhci_hcd :be:00.0: Looking for event-dma 001fe9759610 
trb-start 001fe9759620 trb-end 001fe9759620 seg-start 001fe9759000 
seg-end 001fe9759ff0

This is then followed shortly after by several kernel dump messages, and
then the whole system starts behaving erratically, requiring a hard
reboot to recover.

The condition is easy for me to reproduce and I will happily provide any
logs that may be of use to help debug this.  Please just let me know
what you would like and how to get them (as I am not a kernel expert).

Thanks,
Roy

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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


[Kernel-packages] [Bug 1796130] Re: Patches for Additional NVME Support

2018-10-05 Thread Brad Figg
** Changed in: linux (Ubuntu Cosmic)
   Status: Incomplete => Triaged

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

Title:
  Patches for  Additional NVME Support

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Dell is requesting these patches for inclusion into 18.04.2 for
  additional NVME support

  PCI: Check for PCIe Link downtraining
  
https://github.com/torvalds/linux/commit/2d1ce5ec2117d16047334a1aa4b62e0cfb5a0605

  
  PCI/AER: Add sysfs attributes to provide AER stats and breakdown
  https://github.com/torvalds/linux/commit/81aa5206f9a7

  
  PCI/AER: Honor "pcie_ports=native" even if HEST sets FIRMWARE_FIRST
  https://github.com/torvalds/linux/commit/7af02fcd84c1

  
  PCI/AER: Don't clear AER bits if error handling is Firmware-First
  https://github.com/torvalds/linux/commit/45687f96c112

  
  PCI: pciehp: Differentiate between surprise and safe removal
  
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/hotplug=e76ac5875f5d5848558edc79a0869bf20765fec3

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

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


[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

2018-10-05 Thread Ł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/1795583

Title:
  linux-aws: 4.4.0-1032.35 -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:
  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 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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

2018-10-05 Thread Pablo Abrudsky
I just updated my system (sudo apt dist-upgrade), and still having the issue, 
latest kernel didn't fix it for me.
I am attaching the ``udevadm info -e`` for Dell Inspiron 15 5577, without any 
boot kernel params set.


** Attachment added: "``udevadm info -e`` for Dell Inspiron 15 5577"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+attachment/5197555/+files/dell-inspiron-15-5577-udevadm.info

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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


[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

2018-10-05 Thread Ł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/1795583

Title:
  linux-aws: 4.4.0-1032.35 -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:
  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:
  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 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 Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Colin Ian King
Exercising /sys/kernel/security/tpm0/ascii_bios_measurements causes:

[  381.545913] iounmap: bad address c9000e62
[  381.602107] CPU: 2 PID: 1833 Comm: stress-ng-sysfs Not tainted 
4.4.0-138-lowlatency #164-Ubuntu
[  381.602109] Hardware name: Dell Inc. PowerEdge R415/08WNM9, BIOS 1.9.3 
04/26/2012
[  381.602111]  0286 fc02aae09141f60c 8800daa03bc0 
8140dc61
[  381.602117]  88021145cbc0 c9000e62 8800daa03be0 
8106ec1f
[  381.602124]  88021145cbc0 c9000e62 8800daa03bf0 
8106ec5c
[  381.602127] Call Trace:
[  381.602134]  [] dump_stack+0x63/0x82
[  381.602138]  [] iounmap.part.1+0x7f/0x90
[  381.602140]  [] iounmap+0x2c/0x30
[  381.602144]  [] acpi_os_map_cleanup.part.9+0x31/0x40
[  381.602147]  [] acpi_os_unmap_iomem+0xbe/0xf0
[  381.602151]  [] read_log+0xad/0x170
[  381.602153]  [] tpm_ascii_bios_measurements_open+0x37/0x90
[  381.602158]  [] do_dentry_open+0x202/0x310
[  381.602160]  [] ? 
tpm_binary_bios_measurements_open+0x90/0x90
[  381.602164]  [] vfs_open+0x54/0x80
[  381.602166]  [] ? may_open+0x5b/0xf0
[  381.602169]  [] path_openat+0x1b6/0x13a0
[  381.602172]  [] ? free_one_page+0x191/0x340
[  381.602175]  [] do_filp_open+0x91/0x100
[  381.602179]  [] ? common_file_perm+0x70/0x1b0
[  381.602181]  [] ? __alloc_fd+0xc7/0x190
[  381.602185]  [] do_sys_open+0x138/0x2b0
[  381.602187]  [] SyS_open+0x1e/0x20
[  381.602191]  [] entry_SYSCALL_64_fastpath+0x22/0xc1

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 

[Kernel-packages] [Bug 1780628] Re: linux-4.15.0-23-generic RAID 5 kernel BUG

2018-10-05 Thread Steve Kowalik
And v4.19-rc6:

[ 3635.247863] [ cut here ]
[ 3635.247865] kernel BUG at drivers/md/raid5.c:1760!
[ 3635.247872] invalid opcode:  [#1] SMP PTI
[ 3635.247875] CPU: 2 PID: 279 Comm: md0_raid5 Not tainted 
4.19.0-041900rc6-generic #201809301631
[ 3635.247877] Hardware name: Gigabyte Technology Co., Ltd. H370M-D3H/H370M 
D3H-CF, BIOS F3 03/01/2018
[ 3635.247883] RIP: 0010:raid_run_ops+0xbda/0x15d0 [raid456]
[ 3635.247886] Code: 48 8d 04 d0 48 89 45 c8 83 f9 01 0f 85 f8 f5 ff ff 49 8b 
75 00 31 c9 31 d2 4c 89 e7 e8 3f a0 d4 ff 48 89 45 98 e9 f0 f5 ff ff <0f> 0b 0f 
0b e9 52 f9 ff ff 4c 8b 75 80 83 85 4c ff ff ff 01 e9 18
[ 3635.247888] RSP: 0018:a0154122fb48 EFLAGS: 00010002
[ 3635.247891] RAX: 0198 RBX: 88dad8917800 RCX: 
[ 3635.247893] RDX: 88dad8917598 RSI: 88da08ead120 RDI: 88dad8917468
[ 3635.247895] RBP: a0154122fc08 R08: 1000 R09: a0154122fad8
[ 3635.247896] R10: 88dad8917488 R11:  R12: 88db5a759898
[ 3635.247898] R13: 88dad8917468 R14: 88dad8917400 R15: 88db586c
[ 3635.247900] FS:  () GS:88db6628() 
knlGS:
[ 3635.247902] CS:  0010 DS:  ES:  CR0: 80050033
[ 3635.247904] CR2: 7ff2fe7f8ff8 CR3: 2220a005 CR4: 003606e0
[ 3635.247906] Call Trace:
[ 3635.247911]  ? handle_stripe_dirtying+0x706/0x800 [raid456]
[ 3635.247915]  handle_stripe+0xb9b/0x1f90 [raid456]
[ 3635.247919]  ? __wake_up_common_lock+0x8e/0xc0
[ 3635.247923]  handle_active_stripes.isra.74+0x3e6/0x5d0 [raid456]
[ 3635.247927]  raid5d+0x359/0x550 [raid456]
[ 3635.247931]  md_thread+0x98/0x160
[ 3635.247934]  ? wait_woken+0x80/0x80
[ 3635.247937]  kthread+0x120/0x140
[ 3635.247939]  ? md_rdev_init+0xb0/0xb0
[ 3635.247942]  ? kthread_bind+0x40/0x40
[ 3635.247945]  ret_from_fork+0x35/0x40
[ 3635.247947] Modules linked in: xfs nls_iso8859_1 snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal 
intel_powerclamp snd_hda_intel coretemp ppdev kvm_intel snd_hda_codec 
snd_hda_core snd_hwdep intel_cstate snd_pcm snd_timer sch_fq_codel snd wmi_bmof 
acpi_pad intel_rapl_perf soundcore parport_pc mac_hid intel_pch_thermal mei_me 
mei parport ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp libiscsi_tcp 
libiscsi auth_rpcgss scsi_transport_iscsi nfs_acl lockd grace sunrpc ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid1 raid0 multipath linear 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c i915 crct10dif_pclmul kvmgt crc32_pclmul vfio_mdev 
ghash_clmulni_intel mdev pcbc vfio_iommu_type1 vfio aesni_intel kvm
[ 3635.247984]  irqbypass aes_x86_64 i2c_algo_bit crypto_simd drm_kms_helper 
cryptd glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm e1000e 
ahci libahci wmi video pinctrl_cannonlake pinctrl_intel
[ 3635.247996] ---[ end trace 70e03761eb30ac04 ]---
[ 3635.248000] RIP: 0010:raid_run_ops+0xbda/0x15d0 [raid456]
[ 3635.248002] Code: 48 8d 04 d0 48 89 45 c8 83 f9 01 0f 85 f8 f5 ff ff 49 8b 
75 00 31 c9 31 d2 4c 89 e7 e8 3f a0 d4 ff 48 89 45 98 e9 f0 f5 ff ff <0f> 0b 0f 
0b e9 52 f9 ff ff 4c 8b 75 80 83 85 4c ff ff ff 01 e9 18
[ 3635.248005] RSP: 0018:a0154122fb48 EFLAGS: 00010002
[ 3635.248007] RAX: 0198 RBX: 88dad8917800 RCX: 
[ 3635.248009] RDX: 88dad8917598 RSI: 88da08ead120 RDI: 88dad8917468
[ 3635.248011] RBP: a0154122fc08 R08: 1000 R09: a0154122fad8
[ 3635.248012] R10: 88dad8917488 R11:  R12: 88db5a759898
[ 3635.248014] R13: 88dad8917468 R14: 88dad8917400 R15: 88db586c
[ 3635.248016] FS:  () GS:88db6628() 
knlGS:
[ 3635.248019] CS:  0010 DS:  ES:  CR0: 80050033
[ 3635.248020] CR2: 7ff2fe7f8ff8 CR3: 2220a005 CR4: 003606e0

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

Title:
  linux-4.15.0-23-generic RAID 5 kernel BUG

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

Bug description:
  I have a machine running linux-4.15.0-23-generic, and I can reliably
  trigger a kernel BUG under heavy write I/O using RAID 5.

  $ cat /proc/mdstat 
  Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] 
[raid10] 
  md0 : active raid5 sdd2[1] sda2[0] sdb2[2] sdc2[3]
23440220160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] 
[]
bitmap: 0/59 pages [0KB], 65536KB chunk

  unused devices: 

  [35679.932015] [ cut here ]
  [35679.932017] kernel BUG at 
/build/linux-uT8zSN/linux-4.15.0/drivers/md/raid5.c:1757!
  [35679.932044] invalid opcode:  [#1] SMP PTI
  [35679.932054] Modules linked in: xfs nls_iso8859_1 

[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

2018-10-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-trusty

** Tags added: block-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: 1795582
  phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1032.35 -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:
  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:
  Confirmed
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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1796094] Re: Livepatch failed

2018-10-05 Thread Joseph Salisbury
Can you provide some additional information about what happened?  Did
you see a specific error message?  Are you able to reproduce the bug?

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

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

** Tags added: kernel-da-key

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

Title:
  Livepatch failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  apply-failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_33_36_generic_44
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 wrz  5 12:10 seq
   crw-rw+ 1 root audio 116, 33 wrz  5 12:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  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:
  Date: Thu Oct  4 15:37:06 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=95e22705-c020-4957-b87d-c3d208a53f15
  InstallationDate: Installed on 2018-09-05 (29 days ago)
  InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd 
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro Super Server
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=9f187778-61da-48dc-bece-1d20b3d8f11c ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-05 (29 days ago)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SSL-F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSL-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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


[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2018-10-05 Thread Guilherme G. Piccoli
Hi Roy, thanks for the report. What is your motherboard? What kernel are you 
running? And what tests are triggering this issue for you?
If you have logs, it'll be pretty useful.

Maybe it's a similar but different case..or the logs may help to confirm
it's exact the same issue.

ASMedia seems to have a FW fix but that depends on your motherboard
vendor to provide it. They don't provide the fix themselves...it needs
some cooking from the vendor, to match subsystem IDs and whatnot.

Cheers,


Guilherme

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

** Changed in: linux (Debian)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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


[Kernel-packages] [Bug 1787191] Re: Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter state X

2018-10-05 Thread smzhou
*** This bug is a duplicate of bug 1787127 ***
https://bugs.launchpad.net/bugs/1787127

I build custom kernel from  ubuntu kernel source 3.13.0-158 with  bfq patch 
,bug still happen .The error message is : 
[35952.358708] BUG: Bad page map in process java  pte:01e67320 pmd:16efdd067

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

Title:
  Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter
  state X

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

Bug description:
  Multiple SuperMicro based servers running 14.04 are experiencing
  continual kernel errors since upgrading to 3.13.0-155 which quickly
  leads to the system becoming unresponsive. The errors start
  immediately after boot.

  Small excerpt from the attached kern.log:

  Aug 15 09:54:15 server kernel: [0.00] CPU0 microcode updated early to 
revision 0x713, date = 2018-01-26
  ...
  Aug 15 09:54:17 server kernel: [   14.381553] ipmi device interface
  Aug 15 09:54:17 server kernel: [   14.610493] NFS: Registering the 
id_resolver key type
  Aug 15 09:54:17 server kernel: [   14.610504] Key type id_resolver registered
  Aug 15 09:54:17 server kernel: [   14.610505] Key type id_legacy registered
  Aug 15 09:54:26 server kernel: [   23.412042] BUG: Bad page map in process 
plymouthd  pte:800860a3d966 pmd:465c17067
  Aug 15 09:54:26 server kernel: [   23.442867] addr:7fb8cc137000 
vm_flags:08100073 anon_vma:880866695ab0 mapping:88086543a870 index:7
  Aug 15 09:54:26 server kernel: [   23.472375] vma->vm_ops->fault: 
filemap_fault+0x0/0x400
  Aug 15 09:54:26 server kernel: [   23.484454] vma->vm_file->f_op->mmap: 
ext4_file_mmap+0x0/0x60
  Aug 15 09:54:26 server kernel: [   23.496669] CPU: 4 PID: 523 Comm: plymouthd 
Tainted: GB 3.13.0-155-generic #205-Ubuntu
  Aug 15 09:54:26 server kernel: [   23.496670] Hardware name: Supermicro 
X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013
  Aug 15 09:54:26 server kernel: [   23.496671]   
880465f37d00 8173983f 7fb8cc137000
  Aug 15 09:54:26 server kernel: [   23.496675]  8808652c63c0 
880465f37d50 8117e374 800860a3d966
  Aug 15 09:54:26 server kernel: [   23.496678]  000465c17067 
0007 880465c179b8 800860a3d966
  Aug 15 09:54:26 server kernel: [   23.496681] Call Trace:
  Aug 15 09:54:26 server kernel: [   23.496684]  [] 
dump_stack+0x64/0x80
  Aug 15 09:54:26 server kernel: [   23.496687]  [] 
print_bad_pte+0x1a4/0x250
  Aug 15 09:54:26 server kernel: [   23.496690]  [] 
vm_normal_page+0x6e/0x80
  Aug 15 09:54:26 server kernel: [   23.496701]  [] 
change_protection_range+0x55f/0x720
  Aug 15 09:54:26 server kernel: [   23.496706]  [] 
change_protection+0x65/0xb0
  Aug 15 09:54:26 server kernel: [   23.496709]  [] 
change_prot_numa+0x1b/0x40
  Aug 15 09:54:26 server kernel: [   23.496712]  [] 
task_numa_work+0x1d2/0x300
  Aug 15 09:54:26 server kernel: [   23.496714]  [] 
task_work_run+0xaf/0xd0
  Aug 15 09:54:26 server kernel: [   23.496717]  [] 
do_notify_resume+0x97/0xb0
  Aug 15 09:54:26 server kernel: [   23.496720]  [] 
int_signal+0x12/0x17
  ...
  Aug 15 09:54:54 server kernel: [   50.902769] BUG: Bad rss-counter state 
mm:880466869880 idx:1 val:338
  Aug 15 09:55:25 server kernel: [   82.513872] BUG: Bad rss-counter state 
mm:880866d6b800 idx:1 val:249
  ...
  Aug 15 09:56:30 server kernel: [  144.954186] CPU: 18 PID: 4139 Comm: php-cgi 
Tainted: GB 3.13.0-155-generic #205-Ubuntu
  Aug 15 09:56:30 server kernel: [  144.954189]   
880467cefd00 8173983f 02d2e000
  Aug 15 09:56:30 server kernel: [  144.954193]  000468950067 
2d2e 880468950970 80042a764966
  Aug 15 09:56:30 server kernel: [  144.954195]  [] 
dump_stack+0x64/0x80
  Aug 15 09:56:30 server kernel: [  144.954199]  [] 
vm_normal_page+0x6e/0x80
  Aug 15 09:56:30 server kernel: [  144.954203]  [] 
change_protection+0x65/0xb0
  Aug 15 09:56:30 server kernel: [  144.954207]  [] 
change_prot_numa+0x1b/0x40
  Aug 15 09:56:30 server kernel: [  144.954211]  [] 
task_work_run+0xaf/0xd0
  Aug 15 09:56:30 server kernel: [  144.954214]  [] 
retint_signal+0x48/0x86
  Aug 15 09:56:30 server kernel: [  144.954216] addr:02d2f000 
vm_flags:08100073 anon_vma:880467651c18 mapping:  (null) index:2d2f
  Aug 15 09:56:30 server kernel: [  144.954218] CPU: 18 PID: 4139 Comm: php-cgi 
Tainted: GB 3.13.0-155-generic #205-Ubuntu
  Aug 15 09:56:30 server kernel: [  144.954218] Hardware name: Supermicro 
X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013
  Aug 15 09:56:30 server kernel: [  144.954221]   
880467cefd00 8173983f 02d2f000
  Aug 15 09:56:30 server kernel: [  144.954223]  880868111800 
880467cefd50 8117e374 

[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Colin Ian King
So I believe this is the sysfs test that causes the issues, the
subsequent tee timer stressors just appear to be broken because the
sysfs stressor got the kernel into a mangled broken state.

I was able to run the tee and timer stressors on a cleanly booted
4.4.0-137-lowlatency kernel without any issues.  Running the sysfs
stressor caused a load of oopses as follows:

  740.873265] iounmap: bad address c90004da
[  740.929503] CPU: 4 PID: 1788 Comm: stress-ng-sysfs Not tainted 
4.4.0-138-lowlatency #164-Ubuntu
[  740.929509] Hardware name: Dell Inc. PowerEdge R415/08WNM9, BIOS 1.9.3 
04/26/2012
[  740.929512]  0286 5dc48b8f33ce7222 8800da813bc0 
8140dc61
[  740.929536]  8800df1f9d80 c90004da 8800da813be0 
8106ec1f
[  740.929541]  8800df1f9d80 c90004da 8800da813bf0 
8106ec5c
[  740.929544] Call Trace:
[  740.929553]  [] dump_stack+0x63/0x82
[  740.929558]  [] iounmap.part.1+0x7f/0x90
[  740.929563]  [] iounmap+0x2c/0x30
[  740.929572]  [] acpi_os_map_cleanup.part.9+0x31/0x40
[  740.929587]  [] acpi_os_unmap_iomem+0xbe/0xf0
[  740.929607]  [] read_log+0xad/0x170
[  740.929619]  [] tpm_binary_bios_measurements_open+0x37/0x90
[  740.929626]  [] do_dentry_open+0x202/0x310
[  740.929632]  [] ? 
tpm_ascii_bios_measurements_show+0x260/0x260
[  740.929645]  [] vfs_open+0x54/0x80
[  740.929656]  [] ? may_open+0x5b/0xf0
[  740.929662]  [] path_openat+0x1b6/0x13a0
[  740.929670]  [] ? __do_page_fault+0x23a/0x440
[  740.929678]  [] ? free_one_page+0x191/0x340
[  740.929686]  [] do_filp_open+0x91/0x100
[  740.929695]  [] ? mntput_no_expire+0x2e/0x1b0
[  740.929702]  [] ? __alloc_fd+0xc7/0x190
[  740.929720]  [] do_sys_open+0x138/0x2b0
[  740.929735]  [] SyS_open+0x1e/0x20
[  740.929747]  [] entry_SYSCALL_64_fastpath+0x22/0xc1
[  749.735460] BUG: unable to handle kernel paging request at 00010001
[  749.818685] IP: [] kmem_cache_alloc_trace+0x76/0x210
[  749.896706] PGD d3e68067 PUD 0 
[  749.934172] Oops:  [#1] PREEMPT SMP 
[  749.981003] Modules linked in: kvm_amd kvm irqbypass ipmi_devintf ipmi_ssif 
dcdbas input_leds joydev amd64_edac_mod 8250_fintek k10temp fam15h_power 
serio_raw edac_mce_amd ipmi_si i2c_piix4 acpi_power_meter edac_core 
ipmi_msghandler shpchp mac_hid 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 hid_generic aes_x86_64 mptsas lrw mptscsih 
gf128mul usbhid glue_helper ablk_helper pata_acpi hid cryptd psmouse 
pata_atiixp mptbase ahci bnx2 libahci scsi_transport_sas
[  750.743813] CPU: 4 PID: 1791 Comm: stress-ng-sysfs Not tainted 
4.4.0-138-lowlatency #164-Ubuntu
[  750.847825] Hardware name: Dell Inc. PowerEdge R415/08WNM9, BIOS 1.9.3 
04/26/2012
[  750.937282] task: 8800d3e45580 ti: 8800da824000 task.ti: 
8800da824000
[  751.026734] RIP: 0010:[]  [] 
kmem_cache_alloc_trace+0x76/0x210
[  751.133881] RSP: 0018:8800da827c18  EFLAGS: 00010202
[  751.197334] RAX:  RBX:  RCX: 0b1af204
[  751.282627] RDX: 0b1af004 RSI: 0b1af004 RDI: 0001a740
[  751.367921] RBP: 8800da827c58 R08: 880215003b00 R09: 8129e635
[  751.453209] R10: 0637760b R11:  R12: 024000c0
[  751.538502] R13: 00010001 R14: 88020fc24900 R15: 880215003b00
[  751.623798] FS:  7f8e5a1f4700() GS:88021570() 
knlGS:
[  751.720535] CS:  0010 DS:  ES:  CR0: 80050033
[  751.789183] CR2: 00010001 CR3: db29e000 CR4: 000406f0
[  751.874477] Stack:
[  751.898415]   88020fc24900 0030 

[  751.986848]  88020f67cf00 8800d94cf980 88020fc24900 
8802124386a8
[  752.075289]  8800da827c98 8129e635  
88020fc24900
[  752.163722] Call Trace:
[  752.192853]  [] kernfs_fop_open+0x275/0x370
[  752.261505]  [] do_dentry_open+0x202/0x310
[  752.329117]  [] ? kernfs_fop_release+0x60/0x60
[  752.400893]  [] vfs_open+0x54/0x80
[  752.460186]  [] ? may_open+0x5b/0xf0
[  752.521559]  [] path_openat+0x1b6/0x13a0
[  752.587093]  [] ? bad_area_access_error+0x43/0x50
[  752.661986]  [] do_filp_open+0x91/0x100
[  752.726486]  [] ? __alloc_fd+0xc7/0x190
[  752.790980]  [] do_sys_open+0x138/0x2b0
[  752.855479]  [] SyS_open+0x1e/0x20
[  752.914775]  [] entry_SYSCALL_64_fastpath+0x22/0xc1
[  752.991744] Code: 08 48 39 f2 75 e7 48 83 78 10 00 4c 8b 28 0f 84 48 01 00 
00 4d 85 ed 0f 84 3f 01 00 00 49 63 47 20 49 8b 3f 48 8d 8a 00 02 00 00 <49> 8b 
5c 05 00 4c 89 e8 65 48 0f c7 0f 0f 94 c0 84 c0 74 ab 49 
[  753.217863] RIP  [] kmem_cache_alloc_trace+0x76/0x210
[  753.296928]  RSP 
[  753.338534] CR2: 00010001
[  

[Kernel-packages] [Bug 1795566] Re: linux-oem: 4.15.0-1022.25 -proposed tracker

2018-10-05 Thread 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/security-signoff
   Status: New => In Progress

** 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: 1795564
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 05. October 2018 11:32 UTC

** 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: 1795564
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 05. October 2018 11:32 UTC
+ 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1795566

Title:
  linux-oem: 4.15.0-1022.25 -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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  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: 1795564
  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/1795566/+subscriptions

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


[Kernel-packages] [Bug 1795092] Re: xubuntu 18.10 daily image (x86) fails to boot - initramfs

2018-10-05 Thread Chris Guiver
found my xubuntu 18.10 daily image iso (updated this morning 2018-10-04 is date 
found in zsync)
xubuntu plymouth screen, ctrl-alt-f2 & scrolling

[ 99.99]  ehci-pci :00:1a.7:dma_direct_map_sg: overflow
0x00016cbe6+2048 of device mask 

and eventually

---
[  9.570802] sd 8:0:0:0: [sdb] No Caching mode page found
[  9.570846] sd 8:0:0:0: [sdb] Assuming drive cache: write through

"BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands

(initramfs) Unable to find a medium containing a live file system
[  234.592022]  usb 4-1:device descriptor read/64, error -110
[  240.353082]  usb 4-1:device descriptor read/8m error -110
// three more usb 4-1 messages
... usb  usb4-port1: unable to enumerate USB device

// the usb messages I ignore; they appeared when I started using a cheap powered
// hub which is always connected ; occurred on fedora (now gone) & opensuse
// on ctrl-alt-f2 or text screen there were more usb messages I ignore
// also note I'm keying this text in on nearby desktop; typos may exist.

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

Title:
  xubuntu 18.10 daily image (x86) fails to boot - initramfs

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

Bug description:
  x86 daily image (32bit) XUBUNTU 18.10

  - booted & ran fine on dell latitude d610
  - booted & ran fine on ibm thinkpad t43

  fails on

  - hp dc7700 small form factor desktop
  - dell 755 desktop
  - lenovo thinkpad x201

  I don't get the "try xubuntu / install xubuntu" screen, instead it
  eventually drops to

  
  "BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands

  (initramfs) Unable to find a medium containing a live file system
  

  Note: I typed the messages in so typos may exist

  I suspect it's the same issue as
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922

  where Walter (wxl) gave a possible link to

  http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-
  on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html

  I've been testing xubuntu 18.10 daily images for awhile (but not
  logging on qa-tracker - my bad, sorry!!!) without issue on t43 & d610,
  and only rarely booting on other boxes (like 755/dc7700/..)

  It may have been ~15-20 days since last tested on dell 755; but it
  worked fine back then (& prior) but due to my QA-tracking omission, we
  can't be exact - sorry again!

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

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


[Kernel-packages] [Bug 1795092] Re: xubuntu 18.10 daily image (x86) fails to boot - initramfs

2018-10-05 Thread Chris Guiver
installed lubuntu 18.04.1 on dell 755 without updates, format of /, but
used my old /home (from fedora). rebooted post install, pointed sources
to my ISP's ubuntu mirror (bandwidth free updates) & dist-upgrade. I
added xubuntu-desktop & some of the apps missing from my modified xfce
desktop.

added canonical kernel ppa; changed [ppa] source to point to cosmic;
update & install kernel. reboot & login (normally!)

guiverc@755-lubu:~$ screenfetch -n
 guiverc@755-lubu
 OS: Ubuntu 18.04 bionic
 Kernel: x86_64 Linux 4.18.0-8-generic
 Uptime: 10m
 Packages: 1678
 Shell: bash 4.4.19
 Resolution: 1680x1050
 DE: XFCE
 WM: Xfwm4
 WM Theme: Agualemon
 GTK Theme: Mist [GTK2]
 Icon Theme: gnome
 Font: Sans 10
 CPU: Intel Core2 Duo E6850 @ 2x 2.71GHz
 GPU: ATI RV515
 RAM: 477MiB / 4824MiB

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

Title:
  xubuntu 18.10 daily image (x86) fails to boot - initramfs

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

Bug description:
  x86 daily image (32bit) XUBUNTU 18.10

  - booted & ran fine on dell latitude d610
  - booted & ran fine on ibm thinkpad t43

  fails on

  - hp dc7700 small form factor desktop
  - dell 755 desktop
  - lenovo thinkpad x201

  I don't get the "try xubuntu / install xubuntu" screen, instead it
  eventually drops to

  
  "BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands

  (initramfs) Unable to find a medium containing a live file system
  

  Note: I typed the messages in so typos may exist

  I suspect it's the same issue as
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922

  where Walter (wxl) gave a possible link to

  http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-
  on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html

  I've been testing xubuntu 18.10 daily images for awhile (but not
  logging on qa-tracker - my bad, sorry!!!) without issue on t43 & d610,
  and only rarely booting on other boxes (like 755/dc7700/..)

  It may have been ~15-20 days since last tested on dell 755; but it
  worked fine back then (& prior) but due to my QA-tracking omission, we
  can't be exact - sorry again!

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   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/1796250

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| [stdout] [ 1422.281009]  [] ? 

[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

2018-10-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** 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 --
  kernel-stable-master-bug: 1795582
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 05. October 2018 10:31 UTC

** 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 --
  kernel-stable-master-bug: 1795582
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 05. October 2018 10:31 UTC
+ phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1032.35 -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:
  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:
  New
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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1795582
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1575437] Re: Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

2018-10-05 Thread baximus
the bug reproduced on ubuntu 18.04

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

Title:
  Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  A fresh install of Ubuntu Gnome 16.04 on an Asus ZenBook UX501VW hangs
  during boot, approximately 80% to 90% of the time... occasionally it
  manages to complete the startup for no discernible reason, at which
  point the fan will run at full speed nonstop (very loud) until the
  machine is powered down. Due to the information from
  , I installed the wily 4.3.5 kernel (replacing 4.4.0)
  from ,
  which appears to work perfectly... no bootup hangs or odd fan
  behavior.

  The hang occurs shortly after providing the disk decryption key (I
  opted for full-disk encryption during installation). The issue occurs
  frequently when booting Ubuntu Gnome from a flash drive using "try
  before installation" mode, however, so I'm confident that it's not
  actually encryption related.

  I am *not* using any proprietary drivers (no nvidia, etc.).

  WORKAROUND: Use kernel parameter:
  nouveau.modeset=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adric  1574 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:19:26 2016
  HibernationDevice: RESUME=UUID=74c52e77-74c8-49d1-843b-23584516bd07
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  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=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Po-Hsu Lin
It looks like this issue is a bit random, with 4.4.0-137-lowlatency
amd64 kernel on gonzo, the kernel oops happened with sysfs and tee test.

** Description changed:

- This is a POTENTIAL REGRESSION found on a SRU testing node "gonzo", with
- 4.4 amd64 lowlatency kernel.
+ This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
+ kernel.
  
  This issue cannot be reproduced with the kernel in -updates (4.4.0-137)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well
- 
  
  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
- 16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0 
- 16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP 
+ 16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
+ 16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| [stdout] [ 1422.281009]  [] ? 
find_vma+0x68/0x70
  16:50:05 DEBUG| [stdout] [ 1422.342374]  [] ? 

[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

2018-10-05 Thread Kleber Sacilotto de Souza
** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1032.35 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux-aws: 4.4.0-1032.35 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1795582
  phase: Packaging

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

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


[Kernel-packages] [Bug 1796250] Re: timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Po-Hsu Lin
Tested on a KVM with 4.4.0-138 amd64 lowlatency kernel, didn't spot this
issue.

Need to test on "gonzo"

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a POTENTIAL REGRESSION found on a SRU testing node "gonzo",
  with 4.4 amd64 lowlatency kernel.

  This issue cannot be reproduced with the kernel in -updates (4.4.0-137)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  
  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0 
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP 
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| [stdout] [ 1422.281009]  [] ? 
find_vma+0x68/0x70
  

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

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

apport-collect 1796250

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

Title:
  timer test in ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a POTENTIAL REGRESSION found on a SRU testing node "gonzo",
  with 4.4 amd64 lowlatency kernel.

  This issue cannot be reproduced with the kernel in -updates (4.4.0-137)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  
  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0 
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP 
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 

[Kernel-packages] [Bug 1796250] [NEW] timer test in ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-05 Thread Po-Hsu Lin
Public bug reported:

This is a POTENTIAL REGRESSION found on a SRU testing node "gonzo", with
4.4 amd64 lowlatency kernel.

This issue cannot be reproduced with the kernel in -updates (4.4.0-137)
And cannot be reproduced with the AMD64 generic kernel in -proposed (4.4.0-138) 
as well


16:50:01 DEBUG| [stdout] timer STARTING
16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
16:50:05 DEBUG| [stdout] timer RETURNED 137
16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0 
16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP 
16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
16:50:05 DEBUG| [stdout] [ 1420.062172]  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 mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: ubuntu_stress_s 
Tainted: G  D 4.4.0-138-generic #164-Ubuntu
16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
16:50:05 DEBUG| [stdout] [ 1422.281009]  [] ? 
find_vma+0x68/0x70
16:50:05 DEBUG| [stdout] [ 1422.342374]  [] ? 
follow_page_mask+0x36/0x3a0
16:50:05 DEBUG| [stdout] [ 1422.413100]  [] 
__get_user_pages+0x11e/0x600
16:50:05 DEBUG| [stdout] [ 1422.482788]  [] 
get_user_pages+0x52/0x60
16:50:05 DEBUG| [stdout] [ 1422.548314]  [] 
copy_strings.isra.20+0x173/0x350
16:50:05 DEBUG| [stdout] [ 1422.622161]  [] 
copy_strings_kernel+0x34/0x40
16:50:05 DEBUG| [stdout] [ 1422.692898]  [] 
do_execveat_common.isra.31+0x4cc/0x770
16:50:05 DEBUG| [stdout] [ 

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

2018-10-05 Thread bugproxy
--- Comment From xxd...@de.ibm.com 2018-10-05 03:46 EDT---
Hello Robie,

Because I migrated both my KVM hypervisors to 18.04, I cannot test it anymore.
But Christian Ehrhardt could reproduce the problem. Hopefully he has still the 
appropriate test envirnoment.

Regards, Andreas (bugproxy)

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial

   * Newer guests might use virtio attributes that are clobbered on 
 migration with the old qemu code.

  [Test Case]

   * Setup two Xenial hosts on ppc64el

   * Create a guest that has a rather new kernel (>=4.14) I'd recommend 
 Bionic

   * Migrate that guest from Host1 to Host2

  [Regression Potential]

   * The modification could affect virtio handling in other cases in a non 
 expected way, but mostly related to migrations. So the expected 
 regression would be issues to migrate properly.
 I verified plenty of migrations in regression testing and we had
 this very code in the Yakkety release as we picked 2.6.1 stable release 
 back then. Due to that it is actually pretty well tested and should not 
 really regress anything out in the wild.

  [Other Info]
   
   * So far this only triggers on the confused endian marshalling on 
 ppc64el, but in theory a different case could trigger it on x86 just as 
 much.

  ---

  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+subscriptions

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


[Kernel-packages] [Bug 1794151] Re: hisi_sas: Add SATA FIX check for v3 hw

2018-10-05 Thread Ike Panhc
Regression test with bionic-proposed passed.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  hisi_sas: Add SATA FIX check for v3 hw

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  If something goes wrong during phy initialization, the device may fail to 
come up.

  [Test Case]
  I don't have a way to inject a FIS error, so this will be smoke tested for 
regressions only.
  Needs to be tested on both D05 and D06 systems, since it touches code on both 
v2 and v3 hw.

  [Fix]
  commit f4e34f2a5dd9c0db19baad3f015c3abd5f2e0343
  Author: Xiang Chen 
  Date:   Wed Jul 18 22:14:33 2018 +0800

  scsi: hisi_sas: Add SATA FIS check for v3 hw

  [Regression Risk]
  Changes to a single driver which will be regression tested across the 2 
platforms that use it.
  Since I can't inject such an error, the error handling code will go untested. 
But, if we enter the error handling code at all, the driver presumably was 
going to fail anyway.

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

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


[Kernel-packages] [Bug 1794156] Re: Fix potential corruption using SAS controller on HiSilicon arm64 boards

2018-10-05 Thread Ike Panhc
Regression test with bionic-proposed passed.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Fix potential corruption using SAS controller on HiSilicon arm64
  boards

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On HiSilicon ARM server systems, there is a potential for corruption when 
multiple CPUs are accessing the same controller.

  [Test Case]
  I don't have a reproducer for the failure, so will be regression tested only 
on D05 and D06 platforms.

  [Fix]
  commit 1c09b663168bb5fd8562234976b76115f2aebe91
  Author: Xiaofei Tan 
  Date:   Wed Jul 18 22:14:32 2018 +0800

  scsi: hisi_sas: add memory barrier in task delivery function

  [Regression Risk]
  The biggest regression risk I see would be a performance impact. But correct 
data is better than fast data :)

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

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


[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

2018-10-05 Thread Niel
I think an update fixed this for me, the log flooding have not happened now for 
24 hours. Can anyone else confirm this.
Ubuntu 18.04 fully updated - No steps was taken to fix this from my side.

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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


[Kernel-packages] [Bug 1794172] Re: HiSilicon SAS controller doesn't recover from PHY STP link timeout

2018-10-05 Thread Ike Panhc
Regression test with bionic-proposed passed.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  HiSilicon SAS controller doesn't recover from PHY STP link timeout

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Under certain conditions, the SAS controller may not recover from an STP link 
timeout, which can make disks behind the controller inaccessible.

  [Test Case]
  I don't have a way of injecting this error, so regression tested only.

  [Fix]
  commit 25908cac84b2ea18d4609fc237d6135d0037041d
  Author: Xiaofei Tan 
  Date:   Wed Jul 18 22:14:27 2018 +0800

  scsi: hisi_sas: Fix the failure of recovering PHY from STP link
  timeout

  [Regression Risk]
  This driver in Ubuntu is only used by the SoC in the D06 board, which will be 
directly regression tested.

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

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


[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2018-10-05 Thread Caramba
The possible source of the problem and the solution:
https://discourse.ubuntu.com/t/call-for-testing-nvidia-prime-in-
ubuntu-18-04-and-18-10/8207

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

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

2018-10-05 Thread bugproxy
--- Comment From indira.pr...@in.ibm.com 2018-10-05 02:20 EDT---
As per comment#16, this issue is fixed & tested in the bionic kernel.
root@boslcp3:~# uname -r
4.13.0-32-generic

Regards,
Indira

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

Title:
  [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start
  the guest with more than 1 thread on ubuntu1804 KVM host machine.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2018-01-07 
13:18:32 ==
  Problem Description:
  ===
  Not able to start the ubutnu1804 guest with more than 1 thread on ubuntu1804 
KVM host machine

  Steps to re-create:
  ==
  > Installed Ubuntu1804 on boslcp3 host.

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.13.0-17-generic

  > Installed qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
  packages

  root@boslcp3:/home# virsh version
  Compiled against library: libvirt 3.6.0
  Using library: libvirt 3.6.0
  Using API: QEMU 3.6.0
  Running hypervisor: QEMU 2.10.1

  > root@boslcp3:~# ppc64_cpu --smt
  SMT is off

  > Defined the guest boslcp3g1 from host machine

  root@boslcp3:/home# virsh list --all
   IdName   State
  
   - boslcp3g1  shut off

  Please cherry pick

  commit 45c940ba490df28cb87b993981a5f63df6bbb8db
  Author: Paul Mackerras 
  Date:   Fri Nov 18 17:43:30 2016 +1100

  KVM: PPC: Book3S HV: Treat POWER9 CPU threads as independent subcores


  > Started the guest and it fails with the error

  root@boslcp3:~# virsh start --console boslcp3g1
  error: Failed to start domain boslcp3g1
  error: internal error: process exited while connecting to monitor: 
2018-01-05T02:54:37.762120Z qemu-system-ppc64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/3 (label charserial0)
  2018-01-05T02:54:37.829236Z qemu-system-ppc64: Cannot support more than 1 
threads on PPC with KVM

  > Unable to start the guest with more than 1 Thread from Ubuntu1804
  KVM host machine.

  XML:
  
  root@boslcp3:/home# virsh dumpxml boslcp3g1
  
boslcp3g1
95374879-0ed3-4562-a00f-e47d9aaf285c
10485760
6291456
6291456

  

  

32

  /machine


  hvm
  
  
  


  
  


  power9
  
  


  


destroy
restart
coredump-restart

  /usr/bin/qemu-system-ppc64 
  




  
  




  
  




  
  

  
  

  
  


  
  


  
  




  
  


  
  


  
  

  
  

  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742892/+subscriptions

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


[Kernel-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2018-10-05 Thread Daniel van Vugt
Confirmed by duplicate bug 1768967.

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => Confirmed

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

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

** Tags added: bionic

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+subscriptions

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


[Kernel-packages] [Bug 1768967] Re: Screen randomly flips 180 degrees

2018-10-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1726160 ***
https://bugs.launchpad.net/bugs/1726160

Sounds like it might be a continuation of bug bug 1726160.

** This bug has been marked a duplicate of bug 1726160
   On login, display rotates to wrong orientation [HP Pavilion]

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

Title:
  Screen randomly flips 180 degrees

Status in iio-sensor-proxy package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 on an HP 350 G1 laptop. According to jstest-
  gtk, the laptop has a ST LIS3LV02DL Accelerometer with three axes.
  Axes 0 and 2 remain at 0 (center) no matter what I do. Axis 1 on the
  other hand senses how much the base of the laptop (the lower half of
  the clam shell, the part with the keyboard), is tilted. When the
  laptop is level, the Axis's value should be 0, but it can be anywhere
  from -20 to 20 while the laptop is being typed on. When its reading is
  above 0, the screen flips. These two facts cause the screen to flip
  seemingly randomly while it's being used.

  Workarround: Lock the screen orientation in GNOME.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 15:53:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:21b7]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1a8b0eca-695f-444c-9cb1-558fe4916595 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: Classis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd10/17/2014:svnHewlett-Packard:pnHPPavilion350G1NotebookPC:pvr05A620300:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242
  dmi.product.name: HP Pavilion 350 G1 Notebook PC
  dmi.product.version: 05A620300
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1768967/+subscriptions

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


  1   2   >