date:20191112

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ XPS 13 9350/9360 has unbearlbe headphone noise after recent kernel
+ updates.
+ 
+ [Fix]
+ Lock Headphone Mic Boost level to 1 as an workaround to solve the issue.
+ 
+ [Test]
+ Plug a headphone to audio jack, the noise is really bad.
+ After applying the patch the noise is gone.
+ 
+ [Regression Potenial]
+ Low. This change only targets to 2 systems, so it has limited impact.
+ 
+ === Original Bug Report ===
  Pertaining to 16.04 on a dell XPS 13 9360
  
  ii  alsa-base 1.0.25+dfsg-0ubuntu5
  
  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.
  
- 
- When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 
+ When headphones are plugged in, there is a clearly audible hiss (white
+ noise). This is present as soon as the headphones are plugged in,
+ whether 'headphones' or 'headset' are selected from the pop-up box.
  
  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:
  
- 10.00, 10.00 (one notch up) the hiss disappears. 
- 20.00, 20.00 cause a louder hiss and 
- 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 
+ 10.00, 10.00 (one notch up) the hiss disappears.
+ 20.00, 20.00 cause a louder hiss and
+ 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts.
  
  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.
  
  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

** Changed in: linux (Ubuntu)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in linux package in Ubuntu:
  In Progress

Bug description:
  === SRU Justification ===
  [Impact]
  XPS 13 9350/9360 has unbearlbe headphone noise after recent kernel
  updates.

  [Fix]
  Lock Headphone Mic Boost level to 1 as an workaround to solve the issue.

  [Test]
  Plug a headphone to audio jack, the noise is really bad.
  After applying the patch the noise is gone.

  [Regression Potenial]
  Low. This change only targets to 2 systems, so it has limited impact.

  === Original Bug Report ===
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  When headphones are plugged in, there is a clearly audible hiss (white
  noise). This is present as soon as the headphones are plugged in,
  whether 'headphones' or 'headset' are selected from the pop-up box.

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears.
  20.00, 20.00 cause a louder hiss and
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts.

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

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

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

[Kernel-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

** No longer affects: pulseaudio (Ubuntu)

** No longer affects: alsa-driver (Ubuntu)

** No longer affects: dell-sputnik

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

Title:
Dell XPS 13 9350/9360 headphone audio hiss

Status in linux package in Ubuntu:
In Progress

Bug description:
=== SRU Justification ===
[Impact]
XPS 13 9350/9360 has unbearlbe headphone noise after recent kernel
updates.

[Fix]
Lock Headphone Mic Boost level to 1 as an workaround to solve the issue.

[Test]
Plug a headphone to audio jack, the noise is really bad.
After applying the patch the noise is gone.

[Regression Potenial]
Low. This change only targets to 2 systems, so it has limited impact.

=== Original Bug Report ===
Pertaining to 16.04 on a dell XPS 13 9360

ii alsa-base 1.0.25+dfsg-0ubuntu5

Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

When headphones are plugged in, there is a clearly audible hiss (white
noise). This is present as soon as the headphones are plugged in,
whether 'headphones' or 'headset' are selected from the pop-up box.

Using alsamixer to debug the issue reveals that it is related to
"Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
this is changed to:

10.00, 10.00 (one notch up) the hiss disappears.
20.00, 20.00 cause a louder hiss and
30.00, 30.00 causes an even louder hiss with high frequency audio artifacts.

When the headphones are removed and plugged back in the Headphone Mic
Boost setting returns to dB gain 0 and the problem also returns.

This (problem and workaround) has been reported in the wild:
https://news.ycombinator.com/item?id=13050843 and

https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
for example

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

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

[Kernel-packages] [Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu

** Description changed:

- Similar to bug
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC
- address pass through does not work with a Lenovo Thunderbolt 3
- Workstation Dock.
+ === SRU Justification ===
+ [Impact]
+ Lenovo dock doesn't support MAC passthrough.
+ 
+ [Fix]
+ Add support to Lenovo Dock MAC passthrough.
+ 
+ [Test]
+ MAC passthrough works once the patch is applied.
+ 
+ [Regression Potential]
+ Low. Apart from adding support to Lenovo Dock, this patch only did minor
+ refactoring to existing behavior, no functional change to current code.
+ 
+ === Original Bug Report ===
+ Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 
the MAC address pass through does not work with a Lenovo Thunderbolt 3 
Workstation Dock.
  
  The dock's network port is recognized and working but it has its own MAC
  address even though MAC Address pass through is enabled in the BIOS.
  
  This is the dock in question:
  
  https://www.lenovo.com/us/en/accessories-and-monitors/top-tech
  /Thunderbolt-WS-230W-dock-US/p/40AN0230US
  
  and the laptop is a Lenovo P1. Debug files attached.
- 
  
  Please let me know if further info is required.
  
  Thanks!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  rauer  2107 F pulseaudio
-  /dev/snd/controlC1:  rauer  2107 F pulseaudio
-  /dev/snd/controlC0:  rauer  2107 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  rauer  2107 F pulseaudio
+  /dev/snd/controlC1:  rauer  2107 F pulseaudio
+  /dev/snd/controlC0:  rauer  2107 F pulseaudio
  CurrentDesktop: i3
  Date: Mon May  6 19:34:26 2019
  InstallationDate: Installed on 2019-04-09 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20MES1WH00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-13-generic N/A
-  linux-backports-modules-5.0.0-13-generic  N/A
-  linux-firmware1.178
+  linux-restricted-modules-5.0.0-13-generic N/A
+  linux-backports-modules-5.0.0-13-generic  N/A
+  linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET39W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES1WH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES1WH00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

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

Title:
  Lenovo dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Lenovo dock doesn't support MAC passthrough.

  [Fix]
  Add support to Lenovo Dock MAC passthrough.

  [Test]
  MAC passthrough works once the patch is applied.

  [Regression Potential]
  Low. Apart from adding support to Lenovo Dock, this patch only did minor
  refactoring to existing behavior, no functional change to current code.

  === Original Bug Report ===
  Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 
the MAC address pass through does not work with a Lenovo Thunderbolt 3 
Workstation Dock.

  The dock's network port is recognized and working but it has its own
  MAC address even though MAC Address pass through is enabled in the
  BIOS.

  This is the dock in question:

  https://www.lenovo.com/us/en/accessories-and-monitors/top-tech
  /Thunderbolt-WS-230W-dock-US/p/40AN0230US

  and the laptop is a Lenovo P1. Debug files attached.

  Please let me know if further info is required.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND

[Kernel-packages] [Bug 620074]

https://adbirt.com/
https://healthwises.com/category/home-remedies/

https://healthwises.com/category/mens-solution/

https://healthwises.com/forum-2/

https://healthwises.com/about-us/

https://healthwises.com/category/vitamins/

https://healthwises.com/category/anti-aging/

https://healthwises.com/category/weight-management/

https://healthwises.com/back-or-venus-dimples-amazing-facts/

https://healthwises.com/long-paragraphs-for-him-which-you-can-copy-and-
paste/

https://healthbodywise.com/health-benefits-of-aloe-vera-juice/

https://healthwises.com/how-to-increase-size-of-pennis-using-hand
https://www.pinterest.com/pin/732397958136002128/

https://medium.com/@neolifeupdate/health-wises-a37a23ba1723

https://www.pinterest.com/pin/732397958136014610/

https://healthwises.com/how-to-get-firm-breast-in-2-weeks/

https://www.bloglovin.com/blogs/health-wises-19894373

https://www.pinterest.com/pin/732397958136045364/

https://www.pinterest.com/pin/732397958136047412/

https://www.pinterest.com/pin/732397958136047515/

https://medium.com/@blueskyluv11

https://healthbodywise.com/diets-that-pregnant-women-should-avoid/

https://www.pinterest.com/pin/732397958135182632/
http://adbirt.com/blog

https://healthwises.com/how-to-get-bigger-thighs

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

Title:
  Thrashing turns system unusable

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Thrashing on Ubuntu seems to make it almost impossible to interact
  with the system. It can be minutes before any interaction has an
  effect, including remote connections. This means that if a program
  either misbehaves or simply needs more memory than available RAM, it
  might be hard or impossible to stop it, either locally or remotely.
  This can be both an annoyance and a security threat (since a process
  without elevated privileges can effectively hang the system).

  It is not hard to make a system go into thrashing, especially if it is
  low on memory (that's probably true in general, not only of Ubuntu).
  On my ASUS netbook running Ubuntu 10.04, with only 1GB RAM, thrashing
  can occur as easily as running both Chromium (which is a bit of a
  memory hog) and the Resynthesizer plugin in the GIMP at the same time.
  Running these programs plus another memory-intensive program like
  Mathematica can generate thrashing even when 2GB or 4GB of physical
  memory are available.

  I am including a short C++ program that allocates and accesses a large
  amount of memory, guaranteeing thrashing will occur on any system.
  Using this or any other memory-intensive program, the steps required
  to reproduce the condition I described are

  1. Start one or more memory-intensive programs.
  2. As RAM is filled, paging will start, and if the programs try to access the 
memory that has been swapped out, thrashing occurs.

  What happens?

  - Interactivity with the system drops to almost zero. Mouse barely
  moves, keyboard interaction has huge delays (tens of seconds),
  starting a terminal or switching to one if one is already open can
  take minutes, as is the case with remote (e.g. SSH) connections.

  What I would expect/want to happen?

  - The system should keep interactivity levels high at all times. While
  I'm not at all an expert on this, I would think this could be achieved
  by either not allowing paging out of essential user-interface
  elements, or more generally by giving processes that generate a lot of
  page faults comparatively lower priority than other processes,
  especially processes that are just starting, or are part of the user
  interface.

  
  To use the included program, compile with

  g++ -o bug bug.cc

  and run with

  ./bug 

  where  is the amount of memory in MB to be
  allocated. One can run several instances of the program at the same
  time, to compete for memory. One can use top, free or the System
  Monitor to check when RAM is completely filled, and thrashing starts.

  PS: This seems to be a long-standing issue with Linux, it's not
  limited to the current version of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-24-generic 2.6.32-24.39
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tibi   1596 F pulseaudio
   /dev/snd/pcmC0D0p:   tibi   1596 F...m pulseaudio
   /dev/snd/controlC1:  tibi   1596 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21'
 Mixer name : 'Nvidia MCP78 HDMI'

[Kernel-packages] [Bug 988799]

https://adbirt.com/
https://healthwises.com/category/home-remedies/

https://healthwises.com/category/mens-solution/

https://healthwises.com/forum-2/

https://healthwises.com/about-us/

https://healthwises.com/category/vitamins/

https://healthwises.com/category/anti-aging/

https://healthwises.com/category/weight-management/

https://healthwises.com/back-or-venus-dimples-amazing-facts/

https://healthwises.com/long-paragraphs-for-him-which-you-can-copy-and-
paste/

https://healthbodywise.com/health-benefits-of-aloe-vera-juice/

https://healthwises.com/how-to-increase-size-of-pennis-using-hand
https://www.pinterest.com/pin/732397958136002128/

https://medium.com/@neolifeupdate/health-wises-a37a23ba1723

https://www.pinterest.com/pin/732397958136014610/

https://healthwises.com/how-to-get-firm-breast-in-2-weeks/

https://www.bloglovin.com/blogs/health-wises-19894373

https://www.pinterest.com/pin/732397958136045364/

https://www.pinterest.com/pin/732397958136047412/

https://www.pinterest.com/pin/732397958136047515/

https://medium.com/@blueskyluv11

https://healthbodywise.com/diets-that-pregnant-women-should-avoid/

https://www.pinterest.com/pin/732397958135182632/
http://adbirt.com/blog

https://healthwises.com/how-to-get-bigger-thighs

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

Title:
  Precise freezes under heavy i/o

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Whilst creating a VM with 20 GB persistent HD and my system froze
  until the disk was created.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-23-generic 3.2.0-23.36
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gema   2526 F pulseaudio
   /dev/snd/controlC0:  gema   2526 F pulseaudio
   /dev/snd/controlC1:  gema   2526 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,104383c4,0010'
 Controls  : 45
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:081d'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 16
 Mono: Capture 12 [75%] [24.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Thu Apr 26 11:59:11 2012
  HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   lono wireless extensions.
   
   virbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago)
  dmi.bios.date: 03/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  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: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

[Kernel-packages] [Bug 988799]

https://healthbodywise.com/living-with-a-disability-how-to-build-better-relationships-with-people/

https://anyservice.ng/

http://adbirt.com/blog

https://nslite.com/

https://praise.ng/download-free-mp3/david-g-songs-download-new/

https://praise.ng/https://praise.ng/download-free-mp3/onos-ariyo-song-
download/

https://praise.ng/download-free-mp3/david-g-songs-download-new/

https://adbirt.com/

https://www.mp3downloadhits.com/

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

Title:
  Precise freezes under heavy i/o

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Whilst creating a VM with 20 GB persistent HD and my system froze
  until the disk was created.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-23-generic 3.2.0-23.36
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gema   2526 F pulseaudio
   /dev/snd/controlC0:  gema   2526 F pulseaudio
   /dev/snd/controlC1:  gema   2526 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,104383c4,0010'
 Controls  : 45
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:081d'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 16
 Mono: Capture 12 [75%] [24.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Thu Apr 26 11:59:11 2012
  HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   lono wireless extensions.
   
   virbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago)
  dmi.bios.date: 03/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  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: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 620074]

https://healthbodywise.com/living-with-a-disability-how-to-build-better-relationships-with-people/

https://anyservice.ng/

http://adbirt.com/blog

https://nslite.com/

https://praise.ng/download-free-mp3/david-g-songs-download-new/

https://praise.ng/https://praise.ng/download-free-mp3/onos-ariyo-song-
download/

https://praise.ng/download-free-mp3/david-g-songs-download-new/

https://adbirt.com/

https://www.mp3downloadhits.com/

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

Title:
Thrashing turns system unusable

Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete

Bug description:
Thrashing on Ubuntu seems to make it almost impossible to interact
with the system. It can be minutes before any interaction has an
effect, including remote connections. This means that if a program
either misbehaves or simply needs more memory than available RAM, it
might be hard or impossible to stop it, either locally or remotely.
This can be both an annoyance and a security threat (since a process
without elevated privileges can effectively hang the system).

It is not hard to make a system go into thrashing, especially if it is
low on memory (that's probably true in general, not only of Ubuntu).
On my ASUS netbook running Ubuntu 10.04, with only 1GB RAM, thrashing
can occur as easily as running both Chromium (which is a bit of a
memory hog) and the Resynthesizer plugin in the GIMP at the same time.
Running these programs plus another memory-intensive program like
Mathematica can generate thrashing even when 2GB or 4GB of physical
memory are available.

I am including a short C++ program that allocates and accesses a large
amount of memory, guaranteeing thrashing will occur on any system.
Using this or any other memory-intensive program, the steps required
to reproduce the condition I described are

1. Start one or more memory-intensive programs.
2. As RAM is filled, paging will start, and if the programs try to access the
memory that has been swapped out, thrashing occurs.

What happens?

- Interactivity with the system drops to almost zero. Mouse barely
moves, keyboard interaction has huge delays (tens of seconds),
starting a terminal or switching to one if one is already open can
take minutes, as is the case with remote (e.g. SSH) connections.

What I would expect/want to happen?

- The system should keep interactivity levels high at all times. While
I'm not at all an expert on this, I would think this could be achieved
by either not allowing paging out of essential user-interface
elements, or more generally by giving processes that generate a lot of
page faults comparatively lower priority than other processes,
especially processes that are just starting, or are part of the user
interface.

To use the included program, compile with

g++ -o bug bug.cc

and run with

./bug

where is the amount of memory in MB to be
allocated. One can run several instances of the program at the same
time, to compete for memory. One can use top, free or the System
Monitor to check when RAM is completely filled, and thrashing starts.

PS: This seems to be a long-standing issue with Linux, it's not
limited to the current version of Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.39
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tibi 1596 F pulseaudio
/dev/snd/pcmC0D0p: tibi 1596 F...m pulseaudio
/dev/snd/controlC1: tibi 1596 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21'
Mixer name : 'Nvidia MCP78 HDMI'
Components : 'HDA:10ec0888,10250153,00100202
HDA:10de0002,10de0101,0010'
Controls : 37
Simple ctrls : 20
Card1.Amixer.info:
Card hw:1 'U0x46d0x8da'/'USB Device 0x46d:0x8da at usb-:00:04.0-2, full
speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:08da'
Controls : 3
Simple ctrls : 2
Date: Wed Aug 18 13:01:30 2010
HibernationDevice: RESUME=UUID=9464cfb9-e39a-46ab-bf3a-01a7f2194ab1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IwConfig:
lono wireless extensions.

eth0 no wireless extensions.
MachineType: eMachines EL1210-09
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic
root=UUID=93f3d657-74ac-4853-acab-704f74ab4cd0 ro quiet splash
ProcEnviron:
PATH=(custom, user)

[Kernel-packages] [Bug 1848555] Re: Add Intel Comet Lake ethernet support

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => Fix Committed

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

Title:
  Add Intel Comet Lake ethernet support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  e1000e.ko doesn't load for Intel CML ethernet.

  [Fix]
  Add missing ID for the device.

  [Test]
  The driver loads and works once the ID is added.

  [Regression Potential]
  Minimal. Only adds some IDs, no functional change at all.

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

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

[Kernel-packages] [Bug 1849848] Re: autofs module missing from linux-modules in 5+ kernels

** Changed in: linux-gcp (Ubuntu Disco)
   Status: Confirmed => Fix Committed

** Changed in: linux-gcp (Ubuntu Eoan)
   Status: Confirmed => Fix Committed

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

Title:
  autofs module missing from linux-modules in 5+ kernels

Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Disco:
  Fix Committed
Status in linux-gcp source package in Eoan:
  Fix Committed
Status in linux-gcp source package in Focal:
  Confirmed

Bug description:
  Commit a2225d931f75ddd3c39f4d0d195fad99dfd68671 removes fs/autofs4 path
  and replaces it with fs/autofs. This results in the autfs module ending
  up in linux-modules-extra package. Update the gcp.inclusion-list with
  the correct path.
  
  This issue has been addressed for the generic kernels (see lp 1824333). 
  This fixes it for the gcp kernels.

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

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

[Kernel-packages] [Bug 1850950] Re: autofs module missing from linux-modules in 5+ kernels

** Changed in: linux-aws (Ubuntu Disco)
   Status: Confirmed => Fix Committed

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

Title:
  autofs module missing from linux-modules in 5+ kernels

Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Disco:
  Fix Committed
Status in linux-aws source package in Eoan:
  Fix Committed
Status in linux-aws source package in Focal:
  Confirmed

Bug description:
  Commit a2225d931f75ddd3c39f4d0d195fad99dfd68671 removes fs/autofs4 path
  and replaces it with fs/autofs. This results in the autfs module ending
  up in linux-modules-extra package. Update the aws.inclusion-list with
  the correct path.

  This issue has been addressed for the generic kernels (see lp 1824333).
  This fixes it for the aws kernels.

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

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

[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

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

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

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

[Kernel-packages] [Bug 1851506] Re: Add GeminiLake support on Intel int340x thermal device

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

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

Title:
  Add GeminiLake support on Intel int340x thermal device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Intel GLK systems may overheat and trigger a shutdown when doing CPU stress 
test. It's because the CPU thermal zone is missing.

  [Fix]
  Add missing ID to let int340x device work.

  [Test]
  With the patch, the thermal zone "TCPU" is corretly created. In conjunction 
with latest thermald, the system doesn't get shutdown by overheating anymore.

  [Regression Potenial]
  Minimal. This patch only adds a missing ID, no functional change.

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

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

[Kernel-packages] [Bug 1812352] Re: Handle the skip return code in kernel_selftests on Bionic

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

Title:
  Handle the skip return code in kernel_selftests on Bionic

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Justification ==
  In the ubuntu_kernel_selftests, the skipped test will uses return code 4
  (KSFT_SKIP).

  However the code to handle this non-zero return code was not implemented
  in the kselftest framework. And this will generate some false-positive
  results as those skipped tests were treated as a failure.

  For example the raw_skew test in timers on 4.15:
  1..0 # Skipped: The clock was adjusted externally. Shutdown NTPd or other 
time sync daemons
  not ok 1..7 selftests: raw_skew [FAIL]

  And the test_user_copy.sh test in user (failure could be found in KVM 
kernels):
  user: module test_user_copy is not found [SKIP]
  not ok 1..1 selftests: test_user_copy.sh [FAIL]

  Xenial is affected by this issue as well. Considering the fact that
  this issue in Bionic affects more tests / kernel variants, and it's
  way easier to fix this in Bionic, I decided to go for Bionic first.

  == Fix ==
  771cbc3b (selftests: lib.mk set KSFT_TAP_LEVEL to prevent nested TAP headers)
  a3355440 (selftests: Fix lib.mk run_tests target shell script)
  42b44c34 (selftests: lib.mk: cleanup RUN_TESTS define and make it readable)
  3f4435b5 (selftests: lib.mk: add SKIP handling to RUN_TESTS define)

  All these can be cherry-picked into Bionic.

  The crucial patch is commit 3f4435b5, the other three patches are just
  some minor fixes that pave the road for it to be cherry-picked.

  == Test ==
  Tested on a Bionic amd64 node, the result shows positive.

  A test summary before the patch:
  END GOOD ubuntu_kernel_selftests.setup
  END GOOD ubuntu_kernel_selftests.breakpoints
  END GOOD ubuntu_kernel_selftests.cpu-hotplug
  END GOOD ubuntu_kernel_selftests.efivarfs
  END GOOD ubuntu_kernel_selftests.memfd
  END GOOD ubuntu_kernel_selftests.memory-hotplug
  END GOOD ubuntu_kernel_selftests.mount
  END GOOD ubuntu_kernel_selftests.net
  END GOOD ubuntu_kernel_selftests.ptrace
  END GOOD ubuntu_kernel_selftests.seccomp
  END ERROR ubuntu_kernel_selftests.timers
  END GOOD ubuntu_kernel_selftests.powerpc
  END GOOD ubuntu_kernel_selftests.user
  END GOOD ubuntu_kernel_selftests.ftrace

  A test summary after the patch:
  END GOOD ubuntu_kernel_selftests.setup
  END GOOD ubuntu_kernel_selftests.breakpoints
  END GOOD ubuntu_kernel_selftests.cpu-hotplug
  END GOOD ubuntu_kernel_selftests.efivarfs
  END GOOD ubuntu_kernel_selftests.memfd
  END GOOD ubuntu_kernel_selftests.memory-hotplug
  END GOOD ubuntu_kernel_selftests.mount
  END GOOD ubuntu_kernel_selftests.net
  END GOOD ubuntu_kernel_selftests.ptrace
  END GOOD ubuntu_kernel_selftests.seccomp
  END GOOD ubuntu_kernel_selftests.timers
  END GOOD ubuntu_kernel_selftests.powerpc
  END GOOD ubuntu_kernel_selftests.user
  END GOOD ubuntu_kernel_selftests.ftrac

  No tests were skipped unintentionally. And the raw_skew test in timers
  is now marked as [SKIPPED] and no longer causing failure.

  A complete test report could be found in the bug report attachment.

  == Regression Potential ==
  Low, this patch set just added support to handle the skip return code
  and changes are limited to the kselftest framework itself, no actual
  impact to normal users.

  
  == Original bug report ==
  In the selftests tool, we are using a KSFT_SKIP=4 return code for those 
skipped tests in the latest upstream kernel tree.

  But the corresponding code to take care of this return value does not
  exist in Bionic and Xenial kernel, this will cause the test still
  being marked as failed:

  selftests: test_user_copy.sh
  
  user: module test_user_copy is not found [SKIP]
  not ok 1..1 selftests:  test_user_copy.sh [FAIL]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812352/+subscriptions

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

[Kernel-packages] [Bug 1851469] Re: Incorrect raspi2 snapcraft.yaml file

** Changed in: linux-raspi2 (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  Incorrect raspi2 snapcraft.yaml file

Status in linux-raspi2 package in Ubuntu:
  In Progress
Status in linux-raspi2 source package in Disco:
  Fix Committed
Status in linux-raspi2 source package in Eoan:
  Fix Committed
Status in linux-raspi2 source package in Focal:
  In Progress

Bug description:
  [Impact]

  The current snapcraft.yaml file on the raspi2 branch is the one from
  the main/master kernel and not the raspi2 version.

  [Test Case]

  Compare snapcraft.yaml from the affected series with the version from
  bionic:linux-raspi2.

  Try to snap the kernel:
  $ snapcraft --target-arch=armhf

  [Fix]

  Update snapcraft.yaml.

  [Regression Potential]

  Low, since it's currently completely broken.

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

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

[Kernel-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

2019-11-12 Thread James

I observe this on my XPS 13 9360.  
As mentioned by others, the headphone hissing goes away when I mute the system 
or when I run "amixer -c0 sset 'Headphone Mic Boost' 10dB".  I created an even 
in /etc/acpi/events to call run this whenever headphones are inserted so that 
it persists after reboot.

Has anyone had luck advising Dell of the suspected hardware issue?

James

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

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

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

[Kernel-packages] [Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu

** Changed in: linux (Ubuntu)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  Lenovo dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Similar to bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC
  address pass through does not work with a Lenovo Thunderbolt 3
  Workstation Dock.

  The dock's network port is recognized and working but it has its own
  MAC address even though MAC Address pass through is enabled in the
  BIOS.

  This is the dock in question:

  https://www.lenovo.com/us/en/accessories-and-monitors/top-tech
  /Thunderbolt-WS-230W-dock-US/p/40AN0230US

  and the laptop is a Lenovo P1. Debug files attached.

  
  Please let me know if further info is required.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rauer  2107 F pulseaudio
   /dev/snd/controlC1:  rauer  2107 F pulseaudio
   /dev/snd/controlC0:  rauer  2107 F pulseaudio
  CurrentDesktop: i3
  Date: Mon May  6 19:34:26 2019
  InstallationDate: Installed on 2019-04-09 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20MES1WH00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET39W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES1WH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES1WH00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1852077] Re: Backport: bonding: fix state transition issue in link monitoring

2019-11-12 Thread Po-Hsu Lin

Awesome,
thanks for testing these, I will SRU them.

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

Title:
  Backport: bonding: fix state transition issue in link monitoring

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  There's an issue with bonding driver in the current ubuntu kernels.
  Sometimes one link stuck in a weird state.
  It was fixed with patch https://www.spinics.net/lists/netdev/msg609506.html 
in upstream.
  Commit 1899bb325149e481de31a4f32b59ea6f24e176ea.

  We see this bug with linux 4.15 (ubuntu xenial, hwe kernel), but it
  should be reproducible with other current kernel versions.

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

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

[Kernel-packages] [Bug 1841410] Re: Module extra package is not available for Trusty AWS

2019-11-12 Thread Po-Hsu Lin

I will revert this status as commit
a54839d364ff085a28e4826a669ed840234dff4b was reverted

These ubuntu_quota_smoke_test and ubuntu_zram_smoke_test tests are not working 
on T-AWS, but it can still be tested on other flavour / kernels on Trusty.
Blacklisting them will drop regression coverage on these features.

A better solution is to build a linux-modules-extra-aws package or at
least just blacklist them on T-AWS.

** Changed in: ubuntu-kernel-tests
   Status: Fix Released => Confirmed

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

** Changed in: linux-aws (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: linux-aws (Ubuntu Trusty)
   Status: Fix Released => Triaged

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

Title:
  Module extra package is not available for Trusty AWS

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  Triaged
Status in linux-aws source package in Trusty:
  Triaged

Bug description:
  After bug 1836706, we start shipping the modules-extra for AWS.

  However this was not applied to Trusty AWS. (As it's ESM now)

  We will need to turn off the following tests specifically for T-AWS:
  * quota related test in ubuntu_ltp_syscalls
  * ubuntu_quota_smoke_test
  * ubuntu_zram_smoke_test

  If we're gonna to add this package for it in the future, we can add
  these tests back.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1841410/+subscriptions

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

[Kernel-packages] [Bug 1852364] [NEW] iwlwifi: Microcode SW error detected

2019-11-12 Thread Mathieu Tarral

Public bug reported:

Hi,

I just had an unresponsive Wifi connexion, and checking the dmesg logs
gave me this:

[53468.634940] iwlwifi :00:14.3: Queue 11 is active on fifo 1 and stuck for 
1 ms. SW [0, 15] HW [0, 15] FH TRB=0x0c010b000
[53468.635087] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[53468.635466] iwlwifi :00:14.3: Start IWL Error Log Dump:
[53468.635471] iwlwifi :00:14.3: Status: 0x0080, count: 6
[53468.635475] iwlwifi :00:14.3: Loaded firmware version: 46.6bf1df06.0
[53468.635480] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN   
[53468.635484] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0
[53468.635488] iwlwifi :00:14.3: 0x | trm_hw_status1
[53468.635491] iwlwifi :00:14.3: 0x004882DA | branchlink2
[53468.635495] iwlwifi :00:14.3: 0x0047932A | interruptlink1
[53468.635498] iwlwifi :00:14.3: 0x0047932A | interruptlink2



It looks like a iwlwifi firmware crash.

See the dmesg log attached.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-firmware 1.183.1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 13 02:54:38 2019
Dependencies:
 
InstallationDate: Installed on 2019-09-26 (47 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "dmesg log"
   
https://bugs.launchpad.net/bugs/1852364/+attachment/5304906/+files/bug_iwl.txt

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

Title:
  iwlwifi: Microcode SW error detected

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi,

  I just had an unresponsive Wifi connexion, and checking the dmesg logs
  gave me this:

  [53468.634940] iwlwifi :00:14.3: Queue 11 is active on fifo 1 and stuck 
for 1 ms. SW [0, 15] HW [0, 15] FH TRB=0x0c010b000
  [53468.635087] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [53468.635466] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [53468.635471] iwlwifi :00:14.3: Status: 0x0080, count: 6
  [53468.635475] iwlwifi :00:14.3: Loaded firmware version: 46.6bf1df06.0
  [53468.635480] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN   
  [53468.635484] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0
  [53468.635488] iwlwifi :00:14.3: 0x | trm_hw_status1
  [53468.635491] iwlwifi :00:14.3: 0x004882DA | branchlink2
  [53468.635495] iwlwifi :00:14.3: 0x0047932A | interruptlink1
  [53468.635498] iwlwifi :00:14.3: 0x0047932A | interruptlink2

  

  It looks like a iwlwifi firmware crash.

  See the dmesg log attached.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.183.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 02:54:38 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-09-26 (47 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1847892] Re: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

2019-11-12 Thread arQon

Thanks Kai.

Yes, I really want to use Ubuntu kernel to bisect: or at least, I need
the option to be able to - because if the problem is coming from the
Ubuntu patchset, I could spend weeks bisecting mainline and never find
it, whereas if I bisect the Ubuntu tree I'm guaranteed to find it and
that one can be mapped back to mainline if needed, whereas we can't go
the other way around.

The other critical aspect to having the Ubuntu tree available is that it
gives me the Ubuntu 5.0.0-23 build as a sanity check, it case the
problem is being caused elsewhere. Remember, this is *wifi* we're
talking about: any number of pieces could be to blame, from a power
outage resetting something in the router (20/40 coexistence, for
example) to physical antennas in multiple devices, and so on. I need a
way to validate beyond question that it IS the kernel that's at fault
before I go any further with this to avoid risking wasting everybody's
time, including yours.  :)

Anyway, now that I have that info I'll free up a Passport and get things
underway. Thanks again.

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

Title:
  large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Probably relevant:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116

  Card is an RTL8723BE.

  On 16.04 with the HWE stack, after 1795116 was fixed performance was a
  stable 75-80Mb/s.

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Fri 26-Jul-19 12:28
  sent 459,277,171 bytes  received 35 bytes  9,278,327.39 bytes/sec

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Sat 27-Jul-19 01:23
  sent 459,277,171 bytes  received 35 bytes  10,320,836.09 bytes/sec

  On 18.04, performance was still a stable 75-80Mb/s.

  After updating to 19.10, performance is typically ~50Mb/s, or about a
  37% regression.

  $ iwconfig wlan0
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=59/70  Signal level=-51 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  $ ./wifibench.sh 
  Linux 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
  Sat 12-Oct-19 20:30
  sent 459,277,171 bytes  received 35 bytes  5,566,996.44 bytes/sec

  $ iwconfig wlan0 
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=68/70  Signal level=-42 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  So no corrupted packets or etc during that transfer.

  $ ifconfig wlan0
  wlan0: flags=4163  mtu 1500
  inet 192.168.1.33  netmask 255.255.255.0  broadcast 192.168.1.255
  ether dc:85:de:e4:17:a3  txqueuelen 1000  (Ethernet)
  RX packets 56608204  bytes 79066485957 (79.0 GB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 21634510  bytes 8726094217 (8.7 GB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  No issues of any kind in the week that it's been up. Just terrible
  performance.

  I'm painfully aware of all the module's parameters etc, and have tried
  them all, with no change in the results outside of typical wifi
  variance.

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

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

[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

2019-11-12 Thread Morten Kjeldgaard

@kaihengfegn I guess I need this one:

  linux-image-
unsigned-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb

as well as the corresponding headers and modules.

but what does "unsigned" mean?

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: 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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no

[Kernel-packages] [Bug 1778705] Re: skey in ubuntu-kvm-unit-test failed on X/C zVM

We are still affected by this: http://10.246.72.4/test-
results/4.4.0-167.196-generic/s2lp6g001__4.4.0-167.196__2019-10-23_08-15-00/ubuntu_kvm_unit_tests/results/ubuntu_kvm_unit_tests.skey/debug/ubuntu_kvm_unit_tests.skey.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

Title:
  skey in ubuntu-kvm-unit-test failed on X/C zVM

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
  FAIL skey (2 tests)

  This is the only failure in this test suite on Xenial zVM, need to run
  it manually to see what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 3288.479241] audit_printk_skb: 153 callbacks suppressed
   [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser"
   [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 
comm="apparmor_parser"
  Date: Tue Jun 26 07:05:34 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1778705/+subscriptions

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

[Kernel-packages] [Bug 1778705] Re: skey in ubuntu-kvm-unit-test failed on X/C zVM

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  skey in ubuntu-kvm-unit-test failed on X/C zVM

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
  FAIL skey (2 tests)

  This is the only failure in this test suite on Xenial zVM, need to run
  it manually to see what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 3288.479241] audit_printk_skb: 153 callbacks suppressed
   [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser"
   [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 
comm="apparmor_parser"
  Date: Tue Jun 26 07:05:34 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1778705/+subscriptions

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

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-11-12 Thread Russell Neches

On my X1 Carbon 4th gen, kernel 5.3.0-22-generic seems to have
completely fixed the issue. Yay!

$ uname -a
Linux evenedric 5.3.0-22-generic #24-Ubuntu SMP Sat Nov 9 17:34:30 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13

[Kernel-packages] [Bug 1747847] Re: Tests in ubuntu_qrt_kernel_security (021, 022) complains about ASLR not functional on Trusty ARM64

This is still an issue: http://10.246.72.4/test-
results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_08-59-00/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security
.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-
security.py.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

Title:
  Tests in ubuntu_qrt_kernel_security (021, 022) complains about ASLR
  not functional on Trusty ARM64

Status in QA Regression Testing:
  Confirmed
Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported in bug 163
  I think it's better it tear it down into pieces.

   FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 1832, in test_021_aslr_dapper_libs
   self._test_aslr('libs', expected)
 File "./test-kernel-security.py", line 1795, in _test_aslr
   self._test_aslr_all(area, expected, "unlimited stack %s" % area)
 File "./test-kernel-security.py", line 1772, in _test_aslr_all
   self._test_aslr_exec(area, expected, target, name)
 File "./test-kernel-security.py", line 1765, in _test_aslr_exec
   self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: unlimited stack libs native:
   Got exit code 1, expected 0
   Command: './aslr', 'libs', '--verbose'
   Output:
   Checking ASLR of libs:
0x22f130
0x22f130
0x22f130
   FAIL: ASLR not functional (libs always at 0x22f130)
   
   
   ==
   FAIL: test_021_aslr_dapper_mmap (__main__.KernelSecurityTest)
   ASLR of mmap
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 1817, in test_021_aslr_dapper_mmap
   self._test_aslr('mmap', expected)
 File "./test-kernel-security.py", line 1795, in _test_aslr
   self._test_aslr_all(area, expected, "unlimited stack %s" % area)
 File "./test-kernel-security.py", line 1772, in _test_aslr_all
   self._test_aslr_exec(area, expected, target, name)
 File "./test-kernel-security.py", line 1765, in _test_aslr_exec
   self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: unlimited stack mmap native:
   Got exit code 1, expected 0
   Command: './aslr', 'mmap', '--verbose'
   Output:
   Checking ASLR of mmap:
0x200018e010
0x200018e010
0x200018e010
   FAIL: ASLR not functional (mmap always at 0x200018e010)
   
   
   ==
   FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
   ASLR of vdso
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso
   self._test_aslr('vdso', expected)
 File "./test-kernel-security.py", line 1795, in _test_aslr
   self._test_aslr_all(area, expected, "unlimited stack %s" % area)
 File "./test-kernel-security.py", line 1772, in _test_aslr_all
   self._test_aslr_exec(area, expected, target, name)
 File "./test-kernel-security.py", line 1765, in _test_aslr_exec
   self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: unlimited stack vdso native:
   Got exit code 1, expected 0
   Command: './aslr', 'vdso', '--verbose'
   Output:
   Checking ASLR of vdso:
0x21c000
0x21c000
0x21c000
   FAIL: ASLR not functional (vdso always at 0x21c000)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: User Name

[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]

2019-11-12 Thread Akshay

I am having the same problem, wifi adapter not detected Ubuntu 19.10 / Intel 
9260. 
[4.778071] Loading modules backported from iwlwifi
[4.778073] iwlwifi-stack-public:master:8042:654c426c
[4.931110] iwlwifi :73:00.0: enabling device ( -> 0002)
[5.297929] iwlwifi: probe of :73:00.0 failed with error -110

How can I use the dkms backport (commands)?

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

Title:
  iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem
  [8086:0010]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10
  Kernel 5.3.0-18-generic
  Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card.

  Expected: Wifi connects, uploads/downloads as normal

  Symptom: Wifi connects, as soon as an upload/download (any heavy
  traffic) start, the system comes to a crawl, becomes barely usable,
  and I end up opening a prompt to reboot.

  The system is unusable. This happens even with the Live USB version.

  The only solution I found was to download a different (newer) firmware.
  Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi

  This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz

  I then manually copy the contained firmware to /lib/firmware, remove
  all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode
  that the kernel expects to load.

  This completely resolves the issue.

  This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh 
installs):
  
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending 
SCAN_CFG_CMD: time out after 2000ms.
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue 
read_ptr 64 write_ptr 65
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting 
before reading
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, 
count: 609870115
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 
46.6bf1df06.0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | 
ADVANCED_SYSASSERT  
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | 
trm_hw_status0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | 
trm_hw_status1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | 
interruptlink1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | 
interruptlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode 
revision type
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode 
version major
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode 
version minor
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board 
version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | 
l2p_addr_match
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler
  Oct 20 01:51:16 weywot kernel: iwlwifi

[Kernel-packages] [Bug 1747823] Re: noresv-preserve-resv-page test in libhugetlbfs failed on Trusty arm64

This is still an issue: http://10.246.72.4/test-
results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_10-32-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

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

Title:
  noresv-preserve-resv-page test in libhugetlbfs failed on Trusty arm64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Steps:
  1. Deploy an ARM64 system with Trusty
  2. Install necessary packages
  3. git clone --depth=1 -b next 
https://github.com/libhugetlbfs/libhugetlbfs.git
  4. make BUILDTYPE=NATIVEONLY
  5. execute the run_test.py in tests directory

  Result:
  * The noresv-preserve-resv-page test case will fail

  Output with sudo ./run_test.py -v:
  noresv-preserve-resv-page (2M: 64):   Starting testcase 
"noresv-preserve-resv-page", pid 16071
  Reserve all hugepages 31935
  Write  to 0x2f97e0 to steal reserved page
  FAIL  Steal reserved page

  Output with sudo ./run_test.py -V
  noresv-preserve-resv-page (2M: 64): libhugetlbfs 
[ms10-34-mcdivittB0-kernel:19589]: INFO: Found pagesize 2048 kB
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Parsed kernel version: 
[3] . [13] . [0] 
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Feature 
private_reservations is present in this kernel
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Feature noreserve_safe 
is present in this kernel
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Feature map_hugetlb is 
present in this kernel
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Kernel has MAP_PRIVATE 
reservations.  Disabling heap prefaulting.
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Kernel supports 
MAP_HUGETLB
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: HUGETLB_SHARE=0, 
sharing disabled
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: HUGETLB_NO_RESERVE=no, 
reservations enabled
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: No segments were 
appropriate for remapping
  FAILSteal reserved page


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic aarch64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Wed Feb  7 03:11:38 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-141-generic N/A
   linux-backports-modules-3.13.0-141-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1747823/+subscriptions

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

[Kernel-packages] [Bug 1747828] Re: chunk-overcommit test in libhugetlbfs test suite will fail on Trusty ARM64

This is still an issue: http://10.246.72.4/test-
results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_10-32-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

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

Title:
  chunk-overcommit test in libhugetlbfs test suite will fail on Trusty
  ARM64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Steps:
  1. Deploy an ARM64 system with Trusty
  2. Install necessary packages
  3. git clone --depth=1 -b next 
https://github.com/libhugetlbfs/libhugetlbfs.git
  4. make BUILDTYPE=NATIVEONLY
  5. execute the run_test.py in tests directory

  Result:
  * The chunk-overcommit test case will fail

  chunk-overcommit (2M: 64):Starting testcase "chunk-overcommit", pid 17370
  overcommit: 31935 hugepages available: chunk1=15968 chunk2=15968
  Looks like we've overcommitted, testing...
  FAIL  Killed by signal "Bus error" due to overcommit

  Error message could be found in syslog:
  AutotestCrashHandler: Application chunk-overcommi, PID 2269 crashed
  AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.chunk-overcommi.2269']
  AutotestCrashHandler: Could not determine from which application core file 
/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.chunk-overcommi.2269/core
 is from

  Please find the attachement for the core file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic aarch64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Wed Feb  7 04:14:16 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-141-generic N/A
   linux-backports-modules-3.13.0-141-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1747828/+subscriptions

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

[Kernel-packages] [Bug 1747630] Re: Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

Precise ESM reached end of life in April 2019.

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

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Invalid

** Changed in: qa-regression-testing
   Status: New => 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/1747630

Title:
  Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This issue can be reproduced in 3.2.0-133 in proposed and 3.2.0-131.
  So it should not be considered as a regression.

  We didn't spot this issue before, until I'm testing 3.2 kernel on one
  of the laptop (CID 201307-13930) in Cert lab instead of using our
  regular regression-testing test pool from kernel team this cycle.

    ==
    FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
    ASLR of vdso
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso
    self._test_aslr('vdso', expected)
  File "./test-kernel-security.py", line 1795, in _test_aslr
    self._test_aslr_all(area, expected, "unlimited stack %s" % area)
  File "./test-kernel-security.py", line 1772, in _test_aslr_all
    self._test_aslr_exec(area, expected, target, name)
  File "./test-kernel-security.py", line 1765, in _test_aslr_exec
    self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
    self.assertEqual(expected, rc, msg + result + report)
    AssertionError: unlimited stack vdso native:
    Got exit code 1, expected 0
    Command: './aslr', 'vdso', '--verbose'
    Output:
    Checking ASLR of vdso:
     0x40022000
     0x40022000
     0x40022000
    FAIL: ASLR not functional (vdso always at 0x40022000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1747630/+subscriptions

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

[Kernel-packages] [Bug 1842023] Re: run_netsocktests from net in ubuntu_kernel_selftests failed with X-4.15

verified fix for SRU-2019.10.21

** Changed in: ubuntu-kernel-tests
   Status: New => Triaged

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Sean Feole (sfeole)

** Changed in: ubuntu-kernel-tests
   Status: Triaged => Fix Released

** Changed in: linux-hwe (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  run_netsocktests from net in ubuntu_kernel_selftests failed with
  X-4.15

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Invalid

Bug description:
  Just like bug 1830016
  This test failed with the same error on X-4.15:

  selftests: run_netsocktests
  
  
  running socket test
  
  socket(41, 0, 0) expected err (Address family not supported by protocol) got 
(Socket type not supported)
  [FAIL]
  not ok 1..6 selftests:  run_netsocktests [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67~16.04.1
  ProcVersionSignature: User Name 4.15.0-60.67~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Fri Aug 30 06:49:48 2019
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1842023/+subscriptions

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

[Kernel-packages] [Bug 1684789] Re: trunc-file.sh.btrfs from ubuntu_ecryptfs test-suite failed on T-LTS

I just tried this on an s390x box running Xenial. This is still an
issue, but I don't think constrained to T-LTS like mentioned earlier.

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

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

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

Title:
  trunc-file.sh.btrfs from ubuntu_ecryptfs test-suite failed on T-LTS

Status in eCryptfs:
  New
Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Triaged

Bug description:
  This test has failed on both amd64, i386 and arm64 T-LTS kernel
  For this test, it complains about the: size should be > 0

  04/15 05:13:22 DEBUG| utils:0116| Running 'apt-get install --yes --force-yes 
build-essential libglib2.0-dev intltool keyutils libkeyutils-dev libpam0g-dev 
libnss3-dev libtool acl xfsprogs btrfs-tools libattr1-dev gcc-multilib'
  04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading package lists...
  04/15 05:13:22 DEBUG| utils:0153| [stdout] Building dependency tree...
  04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading state information...
  04/15 05:13:22 DEBUG| utils:0153| [stdout] acl is already the newest version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] build-essential is already the 
newest version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] gcc-multilib is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] intltool is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] keyutils is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] libattr1-dev is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] libkeyutils-dev is already the 
newest version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] libtool is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] xfsprogs is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] btrfs-tools is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] libglib2.0-dev is already the 
newest version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] libnss3-dev is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] libpam0g-dev is already the newest 
version.
  04/15 05:13:22 DEBUG| utils:0153| [stdout] 0 upgraded, 0 newly installed, 0 
to remove and 0 not upgraded.
  04/15 05:13:22 DEBUG| utils:0116| Running 'which gcc'
  04/15 05:13:22 DEBUG| utils:0153| [stdout] /usr/bin/gcc
  04/15 05:13:22 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t 
trunc-file.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs'
  04/15 05:13:34 ERROR| utils:0153| [stderr] size should be > 0
  04/15 05:13:35 DEBUG| utils:0153| [stdout] trunc-file FAIL
  04/15 05:13:35 DEBUG| utils:0153| [stdout]
  04/15 05:13:35 DEBUG| utils:0153| [stdout] Test Summary:
  04/15 05:13:35 DEBUG| utils:0153| [stdout] 0 passed
  04/15 05:13:35 DEBUG| utils:0153| [stdout] 1 failed
  04/15 05:13:35 ERROR| test:0414| Exception escaping from test:
  Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
  File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", 
line 45, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command failed, rc=1, Command returned non-zero exit status
  * Command:
  tests/run_one.sh -K -t trunc-file.sh -b 100 -D /mnt/image -l
  /mnt/lower -u /mnt/upper -f btrfs
  Exit status: 1
  Duration: 12.9071211815
  stdout:
  trunc-file FAIL
  Test Summary:
  0 passed
  1 failed
  stderr:
  size should be > 0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-74-generic 4.4.0-74.95~14.04.1
  ProcVersionSignature: User Name 4.4.0-74.95~14.04.1-generic 4.4.59
  Uname: Linux 4.4.0-74-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Thu Apr 20 13:58:58 2017
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in linux-aws source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in linux-aws source package in Eoan:
  New

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "crypto_user02 crypto_user02" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions

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

[Kernel-packages] [Bug 1717856] Re: Kernel security test test_021_aslr_dapper_libs failed on 3.2 Precise i386

ESM for Precise ended in April 2019.

** Changed in: linux (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Invalid

** Changed in: qa-regression-testing
   Status: New => 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/1717856

Title:
  Kernel security test test_021_aslr_dapper_libs failed on 3.2 Precise
  i386

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Won't Fix

Bug description:
  Kernel: 3.2.0-131 Precise (i386)

  This is not a regression, as this issue can be reproduced on older kernel.
  AMD64 system does not have this issue. 

  FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
  ASLR of libs
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1827, in test_021_aslr_dapper_libs
  self._test_aslr('libs', expected)
  File "./test-kernel-security.py", line 1790, in _test_aslr
  self._test_aslr_all(area, expected, "unlimited stack %s" % area)
  File "./test-kernel-security.py", line 1767, in _test_aslr_all
  self._test_aslr_exec(area, expected, target, name)
  File "./test-kernel-security.py", line 1760, in _test_aslr_exec
  self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
  self.assertEqual(expected, rc, msg + result + report)
  AssertionError: unlimited stack libs native:
  Got exit code 1, expected 0
  Command: './aslr', 'libs', '--verbose'
  Output:
  Checking ASLR of libs:
  0x4002bd80
  0x4002bd80
  0x4002bd80
  FAIL: ASLR not functional (libs always at 0x4002bd80)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1717856/+subscriptions

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

[Kernel-packages] [Bug 1841410] Re: Module extra package is not available for Trusty AWS

Sam updated the quota rules in autotest-client-tests on Aug 26th in
commit 29ab00ab179418fce9310632a4a58edc5cf5a259   which addressed the
issue with ubuntu_ltp_syscalls

I pushed commit a54839d364ff085a28e4826a669ed840234dff4b to ensure the
correct rules are in place for ubuntu_quota_smoke_test and
ubuntu_zram_smoke_test

Any Yes Fan notify was fixed in bug 775165 , so essentially 3 fixes at
once here.

Marking Fix-Released

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

** Changed in: linux-aws (Ubuntu)
   Status: New => Fix Released

** Changed in: linux-aws (Ubuntu Trusty)
   Status: New => Fix Released

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

Title:
  Module extra package is not available for Trusty AWS

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Trusty:
  Fix Released

Bug description:
  After bug 1836706, we start shipping the modules-extra for AWS.

  However this was not applied to Trusty AWS. (As it's ESM now)

  We will need to turn off the following tests specifically for T-AWS:
  * quota related test in ubuntu_ltp_syscalls
  * ubuntu_quota_smoke_test
  * ubuntu_zram_smoke_test

  If we're gonna to add this package for it in the future, we can add
  these tests back.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1841410/+subscriptions

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

[Kernel-packages] [Bug 1803179]

2019-11-12 Thread mfulz

More infos:

powertop shows this when using intel gpu only (my workarounds from post
https://bugzilla.kernel.org/show_bug.cgi?id=156341#c139)

  0.0%PCI Device: Intel Corporation Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor PCIe Controller (x16)
  0.0%PCI Device: Intel Corporation Cannon Lake PCH HECI 
Controller
  0.0%PCI Device: NVIDIA Corporation GP107M [GeForce GTX 
1050 Mobile]
  0.0%PCI Device: Intel Corporation Cannon Lake PCH SPI 
Controller
  0.0%PCI Device: Intel Corporation Cannon Lake PCH cAVS
  0.0%PCI Device: NVIDIA Corporation GP107GL High 
Definition Audio Controller
  0.0%PCI Device: Intel Corporation Cannon Lake PCH Shared 
SRAM
  0.0%PCI Device: Intel Corporation Cannon Lake PCH SMBus 
Controller
  0.0%PCI Device: Intel Corporation Cannon Lake PCH PCI 
Express Root Port #14
 
when using the patches with nvidia modules unloaded and power set to auto its 
still saying 100%

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 (9750); it might eventually manage to suspend when the lid
  is closed, but more often than not will not wake up again when the lid
  is opened. Waking up using the power button often results in a system
  that is apparently frozen (graphics displayed are the last on screen
  before suspend, clock seconds do not change)

  System is unresponsive to the keyboard at that time (can't switch to a
  VT or otherwise interact with the system other than holding the power
  button for a few seconds to shut it down).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mtrudel2516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 10:42:08 2018
  InstallationDate: Installed on 2018-11-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1803179]

2019-11-12 Thread mfulz

Of course I've set the power to auto for everything

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 (9750); it might eventually manage to suspend when the lid
  is closed, but more often than not will not wake up again when the lid
  is opened. Waking up using the power button often results in a system
  that is apparently frozen (graphics displayed are the last on screen
  before suspend, clock seconds do not change)

  System is unresponsive to the keyboard at that time (can't switch to a
  VT or otherwise interact with the system other than holding the power
  button for a few seconds to shut it down).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mtrudel2516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 10:42:08 2018
  InstallationDate: Installed on 2018-11-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1803179]

2019-11-12 Thread mfulz

I've tryed the patches and can confirm that the issues with lockups are
gone with just using bumblebee (unloading nvidia module).

But still the problems are the same:
1.) Just unloading the nvidia modules keeps the power consumption up to 13/14W 
which is 5-6W more (almoest double) in compare to intel only ~8W

2.) Using acpi call to poweroff the nvidia card completely which drops
the power consumption to 8W the lockups are back.

So for me the patches are not working :(

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 (9750); it might eventually manage to suspend when the lid
  is closed, but more often than not will not wake up again when the lid
  is opened. Waking up using the power button often results in a system
  that is apparently frozen (graphics displayed are the last on screen
  before suspend, clock seconds do not change)

  System is unresponsive to the keyboard at that time (can't switch to a
  VT or otherwise interact with the system other than holding the power
  button for a few seconds to shut it down).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mtrudel2516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 10:42:08 2018
  InstallationDate: Installed on 2018-11-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1653597] Re: libhugetlbfs test suite failed with brk_near_huge test

I just looked at the test results for this test suite across some GCP
cloud instances and it looks like it's failing across the 4.15 kernels.

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

Title:
  libhugetlbfs test suite failed with brk_near_huge test

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Kernel: 4.8.0-34.36

  The libhugetlbfs failed with the brk_near_huge test on x86_64(gce)

  12/24 04:59:42 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS
  12/24 04:59:42 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2403: 
sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || 
((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned 
long) old_end & (pagesize - 1)) == 0)' failed.
  12/24 04:59:42 DEBUG| utils:0153| [stdout] brk_near_huge (2M: 64):
  12/24 04:59:42 DEBUG| utils:0153| [stdout] task-size-overrun (2M: 64): PASS

  Full log: http://pastebin.ubuntu.com/23732201/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1653597/+subscriptions

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

[Kernel-packages] [Bug 1850135] Re: mlx5: Tail padding HW Checksum crash in ubuntu 18.04

2019-11-12 Thread Matthew Ruffell

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

Hello,

I believe this bug is a duplicate of Bug 1840854, and the fix should be
released in 4.15.0-59. Can you please review Bug 1840854 and try
installing a newer kernel, say 4.15.0-69, and let me know if it fixes
the problem?

Thanks,
Matthew

** This bug has been marked a duplicate of bug 1840854
   mlx5_core reports hardware checksum error for padded packets on Mellanox NICs

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

Title:
  mlx5: Tail padding HW Checksum crash in ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  we have the following issue which affects a lot of our customers this issue 
fixes upstream and need to add the fixes to ubuntu 18.04.

  Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel
  4.15.0-58-generic.

  Crach log:

  [Fri Aug 30 07:15:23 2019] enp59s0f0.101: hw csum failure
  [Fri Aug 30 07:15:23 2019] CPU: 40 PID: 0 Comm: swapper/40 Not tainted 
4.15.0-58-generic #64-Ubuntu
  [Fri Aug 30 07:15:23 2019] Hardware name: Supermicro 
SYS-2029BT-A2-ADBE-FS011/X11DPT-B, BIOS 3.1 04/30/2019
  [Fri Aug 30 07:15:23 2019] Call Trace:
  [Fri Aug 30 07:15:23 2019] 
  [Fri Aug 30 07:15:23 2019] dump_stack+0x63/0x8b
  [Fri Aug 30 07:15:23 2019] netdev_rx_csum_fault+0x38/0x40
  [Fri Aug 30 07:15:23 2019] __skb_checksum_complete+0xbc/0xd0
  [Fri Aug 30 07:15:23 2019] nf_ip_checksum+0xc3/0xf0
  [Fri Aug 30 07:15:23 2019] tcp_error+0x162/0x1c0 [nf_conntrack]
  [Fri Aug 30 07:15:23 2019] ? update_load_avg+0x57f/0x6e0
  [Fri Aug 30 07:15:23 2019] ? __update_load_avg_se.isra.38+0x1c0/0x1d0
  [Fri Aug 30 07:15:23 2019] nf_conntrack_in+0x14f/0x500 [nf_conntrack]
  [Fri Aug 30 07:15:23 2019] ? csum_partial_ext+0x9/0x10
  [Fri Aug 30 07:15:23 2019] ? __skb_checksum+0x6b/0x300
  [Fri Aug 30 07:15:23 2019] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
  [Fri Aug 30 07:15:23 2019] nf_hook_slow+0x48/0xc0
  [Fri Aug 30 07:15:23 2019] ? skb_send_sock+0x50/0x50
  [Fri Aug 30 07:15:23 2019] ip_rcv+0x2fa/0x360
  [Fri Aug 30 07:15:23 2019] ? inet_del_offload+0x40/0x40
  [Fri Aug 30 07:15:23 2019] __netif_receive_skb_core+0x432/0xb40
  [Fri Aug 30 07:15:23 2019] ? tcp4_gro_receive+0x137/0x1a0
  [Fri Aug 30 07:15:23 2019] __netif_receive_skb+0x18/0x60
  [Fri Aug 30 07:15:23 2019] ? __netif_receive_skb+0x18/0x60
  [Fri Aug 30 07:15:23 2019] netif_receive_skb_internal+0x45/0xe0
  [Fri Aug 30 07:15:23 2019] napi_gro_receive+0xc5/0xf0
  [Fri Aug 30 07:15:23 2019] mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] net_rx_action+0x140/0x3a0
  [Fri Aug 30 07:15:23 2019] __do_softirq+0xe4/0x2d4
  [Fri Aug 30 07:15:23 2019] irq_exit+0xc5/0xd0
  [Fri Aug 30 07:15:23 2019] do_IRQ+0x8a/0xe0
  [Fri Aug 30 07:15:23 2019] common_interrupt+0x8c/0x8c
  [Fri Aug 30 07:15:23 2019] 
  [Fri Aug 30 07:15:23 2019] RIP: 0010:cpu_idle_poll+0x3b/0x14


  
  additional info:
  this issue fixed upstream by the following patches list:
net/mlx5e: Rx, Fix checksum calculation for new hardware -->  
db849faa9bef993a1379dc510623f750a72fa7ce
net/mlx5e: Rx, Check ip headers sanity - > 
0318a7b7fcad9765931146efa7ca3a034194737c
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding -->  
0aa1d18615c163f92935b806dcaff9157645233a
net/mlx5e: XDP, Avoid checksum complete when XDP prog is loaded --> 
5d0bb3bac4b9f6c22280b04545626fdfd99edc6b
mlx5: fix get_ip_proto() --> ef6fcd455278c2be3032a346cc66d9dd9866b787
net/mlx5e: Allow reporting of checksum unnecessary -->   
b856df28f9230a47669efbdd57896084caadb2b3
net/mlx5e: don't set CHECKSUM_COMPLETE on SCTP packets --> 
fe1dc069990c1f290ef6b99adb46332c03258f38
net/mlx5e: Set ECN for received packets using CQE indication --> 
f007c13d4ad62f494c83897eda96437005df4a91
net/mlx5e: Add likely to the common RX checksum flow --> 
63a612f984a1fae040ab6f1c6a0f1fdcdf1954b8  --> taking
net/mlx5e: CHECKSUM_COMPLETE offload for VLAN/QinQ packets -->  
f938daeee95eb36ef6b431bf054a5cc6cdada112 --> in ubuntu 

  we trying to backport those patches list to bionic kernel master
  branch, will add the adjusted patches once the backporting is done.

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

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

[Kernel-packages] [Bug 1848173] Re: Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not established by zcrypt device driver

2019-11-12 Thread Andrew Cloke

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not
  established by zcrypt device driver

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Ubuntu 16.04.6 systems on z15 with crypto CEX7C adapters under z/VM
  cannot see and make use of their hw crypto resources.

  * The patch/backport adds CEX7 toleration support (by mapping it to
  CEX5) to kernel 4.4.

  [Fix]

  * Backport:
  
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848173/+attachment/5297314/+files/s390
  -zcrypt-CEX7-toleration-support.patch

  [Test Case]

  * Define a z/VM guest with 'apvirt' (hardware crypto adapter
  virtualization) having CryptoExpress 7S adapters attached to z/VM
  LPAR.

  * Use lszcrypt command (ideally lszcrypt -VVV) from the s390-tools
  package to list the detected and available hardware crypto resources.

  * Canonical can only do a toleration test: IBM needs to do the
  functional test (due to hardware availability).

  [Regression Potential]

  * The regression potential can be considered as moderate since this is
  purely s390x specific

  * and limited to CryptoExpress 7S (CEX7) adapter cards

  * and again if they running under z/VM (on z15) with 'apvirt'
  configured for the guest.

  * and again only with 16.04.6's kernel 4.4.

  [Other Info]

  * The patch was already applied, kernel compiled and things tested on
  z15 und z/VM.

  __

  System: IBM Z15 z/VM with shared CEX7C adapters
  OS:  Ubuntu 16.04.6 LTS ( 4.4.0-165-generic kernel ) with latest updates
  Shared CEX7C adapters are not displayed on Ubuntu even though APAR 66266 had 
been installed onto the unterlying z/VM system.

  Details
  ===
  Defined shared CEX7C CCA adapters to provide cryptographic accelerators based 
on CCA cards to a z/VM guest system running Ubuntu 16.04.6 LTS.

  The adapters display all right under vm or when running vmcp commands
  under Linux.

  lszcrypt -VVV does not display any adapter.

  We observed that zcrypt_cex4 was not automatically loaded via
  dependency by modprobe ap. Explicitly loading by modprobe zcrypt_cex4
  did not change card availability.

  Please investigate.

  Thanks.

  Terminal output
  ==
  root@system:/sys/bus/ap/devices/card01# ls -l
  total 0
  -r--r--r-- 1 root root 4096 Oct  8 17:51 ap_functions
  -r--r--r-- 1 root root 4096 Oct  8 17:51 depth
  -r--r--r-- 1 root root 4096 Oct  8 17:51 hwtype
  -r--r--r-- 1 root root 4096 Oct  8 17:51 interrupt
  -r--r--r-- 1 root root 4096 Oct  8 17:51 modalias
  -r--r--r-- 1 root root 4096 Oct  8 17:51 pendingq_count
  drwxr-xr-x 2 root root0 Oct  8 17:51 power
  -r--r--r-- 1 root root 4096 Oct  8 17:51 raw_hwtype
  -r--r--r-- 1 root root 4096 Oct  8 17:51 request_count
  -r--r--r-- 1 root root 4096 Oct  8 17:51 requestq_count
  -r--r--r-- 1 root root 4096 Oct  8 17:51 reset
  lrwxrwxrwx 1 root root0 Oct  8 17:51 subsystem -> ../../../bus/ap
  -rw-r--r-- 1 root root 4096 Oct  8 17:50 uevent

  # lszcrypt -V// < No output displayed >
  # vmcp q v crypto
  AP 001 CEX7C Domain 001 shared online

  root@system:/sys/bus/ap/devices/card01# cat hwtype
  13
  root@system:/sys/bus/ap/devices/card01# cat raw_hwtype
  13

  # lsmod
  Module  Size  Used by
  ap 36864  0
  ghash_s390 16384  0
  prng   16384  0
  aes_s390   20480  0
  des_s390   16384  0
  des_generic28672  1 des_s390
  sha512_s39016384  0
  qeth_l253248  1
  sha256_s39016384  0
  sha1_s390  16384  0
  sha_common 16384  3 sha256_s390,sha1_s390,sha512_s390
  qeth  151552  1 qeth_l2
  vmur   20480  0
  ccwgroup   20480  1 qeth
  dm_multipath   36864  0
  zfcp  143360  0
  dasd_eckd_mod 118784  8
  qdio   73728  3 qeth,zfcp,qeth_l2
  scsi_transport_fc  86016  1 zfcp
  dasd_mod  135168  5 dasd_eckd_mod

  # modprobe zcrypt_cex4
  ...
  zcrypt_cex416384  0
  zcrypt_api 36864  1 zcrypt_cex4
  ap 36864  2 zcrypt_cex4,zcrypt_api
  ...

  Contact Information = christian.r...@de.ibm.com

  ---uname output---
  Linux system 4.4.0-164-generic #192-Ubuntu SMP Fri Sep 13 12:01:28 UTC 2019 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Type: 8561 Model:
  403  T01

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1.) Define shared CEX7 CCA cards to z/VM

[Kernel-packages] [Bug 1840935] Re: [Regression] net test from ubuntu_kernel_selftests failed due to bpf test compilation issue

Verified Fix Released, updating bug

** Changed in: ubuntu-kernel-tests
   Status: New => Triaged

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Sean Feole (sfeole)

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

** Changed in: ubuntu-kernel-tests
   Status: Triaged => Fix Released

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

Title:
  [Regression] net test from ubuntu_kernel_selftests failed due to bpf
  test compilation issue

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Commit a25d38b54163 (bpf: relax verifier restriction on BPF_MOV | BPF_ALU) in 
Bionic tree

  Is causing bpf test compilation failure:
  $ sudo make -C tools/testing/selftests TARGETS=bpf run_tests
  make: Entering directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests'
  make[1]: Entering directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf'
  make -C ../../../lib/bpf 
OUTPUT=/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/
  make[2]: Entering directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from 
latest version at 'include/uapi/linux/bpf.h'
  make[2]: Leaving directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf'
  make -C ../../../lib/bpf 
OUTPUT=/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/
  make[2]: Entering directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from 
latest version at 'include/uapi/linux/bpf.h'
  make[2]: Leaving directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf'
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/libbpf.a 
/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/cgroup_helpers.c
 -lcap -lelf -lrt -o 
/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/test_verifier
  test_verifier.c:2173:4: error: ‘struct bpf_test’ has no member named ‘retval’
     .retval = 0,
  ^~
  ../lib.mk:121: recipe for target 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/test_verifier'
 failed
  make[1]: *** 
[/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/test_verifier]
 Error 1
  make[1]: Leaving directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf'
  Makefile:73: recipe for target 'all' failed
  make: *** [all] Error 2
  make: Leaving directory 
'/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests'

  [Fix]
  Bionic misses 111e6b45315c (selftests/bpf: make test_verifier run most 
programs), which adds the 'retval' member to struct bpf_test. The fix is a 
SAUCE patch to remove setting '.retval = 0'.

  [Test Case]
  Run bpf kernel selftests.

  [Regression Potential]
  Low. There's a chance that not backporting 111e6b45315c (selftests/bpf: make 
test_verifier run most programs) will cause possible bugs on the changes added 
by a25d38b54163 (bpf: relax verifier restriction on BPF_MOV | BPF_ALU) to 
remain uncaught.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1040-gke 4.15.0-1040.42
  ProcVersionSignature: Ubuntu 4.15.0-1040.42-gke 4.15.18
  Uname: Linux 4.15.0-1040-gke x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Aug 21 15:09:32 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-gke-4.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840935/+subscriptions

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

[Kernel-packages] [Bug 1847109] Re: Ubuntu 18.04 - wrong cpu-mf counter number

2019-11-12 Thread Andrew Cloke

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 18.04  - wrong cpu-mf counter number

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * wrong cpu-mf counter number of LAST_HOST_TRANSLATIONS

  [Fix]

  * 81507f38d427ebed3291a3c153a798937c998140 81507f38 "s390/cpum_cf:
  correct counter number of LAST_HOST_TRANSLATIONS"

  [Test Case]

  * inspect the counter number of the LAST_HOST_TRANSLATIONS (virtual)
  file

  * cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS

  * returns 'event=0x00e9', but should be 'event=0x00e8'

  * event is only available on z14 and higher, hence Canonical can only
  do regression testing - IBM the functional verification

  [Regression Potential]

  * very minimal, patch just changes one hex number in one code line

  * change is limited to z14 (and higher) hardware counters only

  [Other Info]

  * fix/patch got upstream accepted with 4.16

  * hence it's already in (cosmic and) disco and eoan and only need to be 
applied to bionic 4.15
  __

  Kernel:
  Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 
s390x s390x s390x GNU/Linux

  Description/Reproduction:
  The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number.

  # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS
  event=0x00e9

  should be event=0x00e8

  Fix already available:
  commit 81507f38d427ebed3291a3c153a798937c998140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847109/+subscriptions

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

[Kernel-packages] [Bug 1840932] Re: [Regression] failed to compile seccomp test from ubuntu_kernel_selftests