[Kernel-packages] [Bug 1704433] Re: [Feature] Crystal Ridge - Use FS DAX radix tree as a cache to service page faults

2019-08-27 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Feature] Crystal Ridge - Use FS DAX radix tree as a cache to service
  page faults

Status in intel:
  Invalid
Status in linux package in Ubuntu:
  Expired

Bug description:
  Description

  We already keep the sector in the radix tree as part of the
  exceptional entry. For page faults where we already have an
  exceptional entry, use this information directly from the radix tree
  instead of calling into the filesystem to get a block mapping. This
  should show a measurable performance improvement, which should be
  reported as motivation for the patches.

  Target Kernel:TBD
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1704433/+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 1833474] Re: Radom & frequent total crashes since upgrade to 19.04

2019-08-27 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Radom & frequent total crashes since upgrade to 19.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,

  I'm using an ASUS X751L laptop for several years with no (=a few
  manageable) problem(s).

  Two weeks ago, I switched to Xunbuntu 19.04, by:
  - changing the lines in the /etc/sources.list
  - running apt-get dist-upgrade

  Since then, the computer randomly totally freezes ~twice a day. Even
  after another dist-upgrade this morning...

  
  When I say "totally freezes", I mean:
  - Mouse is froozen, if there was sound playing (be it movie or music, played 
either with mplayer or vlc), then the last 1/2 second loops indefinitely
  - CTRL-ALT-Fn do not work
  - There's nothing in the logs: kern.log, syslog, dmesg... appart some garbage 
chars (like ^@^@^@...) that sometimes gets appended in syslog at crash time.
  - Even when activated Magic SysReq (ALT-SysReq-RSEIUB) do not work
  - Alt-SysReq 1 + Alt-SysReq t do not create anything in /var/crash (there are 
some files for qemu & xfce4-panel, that I already reported)
  - Following https://wiki.ubuntu.com/Kernel/CrashdumpRecipe , I installed 
linux-crashdump, and verified it correctly sets the boot line option, but 
nothing gets created in /var/crash when computer crashes (apart a kexec_cmd 
file that simply lists the boot line args).
  - Quick (2/3 sec) press on the power button does nothing
  - Long (10 sec) press on the power button is the only way to regain control...
  - I've tried to run Memtest86+ (even if I'm sure RAM is not the problem as it 
started occurring only after dist-upgrade to 19.04), but the system is UEFI, so 
option is not in the grub menu. I'll try to make a USB stick to test the RAM

  FYI, the internal wifi card (rtl8723) has always caused troubles: HD
  write slowdowns, audio device locks, etc (from what I guess, it
  overfills some internal bus...). So I deactivate it at boot by
  removing the module, and I use another external Wifi dongle
  (rt2800usb)

  $ uname -a
  Linux gmuller-X751LAB 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  # Note: crashes occurred also with 5.0.0-15

  Does anyone has any hints/tips on how I could get more info & target
  where the problem comes from? because as-is the computer is just
  unusable...

  In the attached log files, the crash occurred right before my manual
  reboot at 15:17:24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833474/+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 1834559] Re: Touchpad stopped working after minor update

2019-08-27 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Touchpad stopped working after minor update

Status in linux package in Ubuntu:
  Expired

Bug description:
  Touchpad stopped working after a minor OS update. I was unable to move
  the cursor even before rebooting the machine. The output of
  /proc/bus/input/devices is attached and, as you can see, does not
  contain my Synaptics touchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834559/+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 1841704] Missing required logs.

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

apport-collect 1841704

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

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

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

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

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

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

Title:
  Test 391/u and 391/p from ubuntu_bpf failed on B

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

Bug description:
  #391/u bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x0
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    R1 has unknown scalar with mixed signed bounds, pointer arithmetic with it 
prohibited for !root

  
    #391/p bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x9391367ba400
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    math between map_value pointer and register with unbounded min value is not 
allowed

  Test result with older kernel:
    #391/u bounds checks mixing signed and unsigned, variant 15 OK
    #391/p bounds checks mixing signed and unsigned, variant 15 OK

  The test has passed but the variant number is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
   crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No 

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

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

apport-collect 1841707

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

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

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

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

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

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

Title:
  Test 491/u and 491/p from ubuntu_bpf failed on B

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

Bug description:
#491/u check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 = 0
1: (75) if r0 s>= 0x0 goto pc+1
3: (95) exit
processed 3 insns, stack depth 0

#491/p check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 = 0
1: (75) if r0 s>= 0x0 goto pc+1
3: (95) exit
processed 3 insns, stack depth 0

  Test result from 4.15.0-58:
#491/u check deducing bounds from const, 6 OK
#491/p check deducing bounds from const, 6 OK

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
   crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  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:
  CurrentDmesg:
   [  540.701915] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [  540.708360] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Aug 28 03:14:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-60-generic N/A
   linux-backports-modules-4.15.0-60-generic  N/A
   linux-firmware 1.173.10
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1841707/+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 1841704] Re: Test 391/u and 391/p from ubuntu_bpf failed on B

2019-08-27 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  Test 391/u and 391/p from ubuntu_bpf failed on B

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

Bug description:
  #391/u bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x0
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    R1 has unknown scalar with mixed signed bounds, pointer arithmetic with it 
prohibited for !root

  
    #391/p bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x9391367ba400
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    math between map_value pointer and register with unbounded min value is not 
allowed

  Test result with older kernel:
    #391/u bounds checks mixing signed and unsigned, variant 15 OK
    #391/p bounds checks mixing signed and unsigned, variant 15 OK

  The test has passed but the variant number is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
   crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  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:
  CurrentDmesg:

  Date: Wed Aug 28 02:58:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1841707] [NEW] Test 491/u and 491/p from ubuntu_bpf failed on B

2019-08-27 Thread Po-Hsu Lin
Public bug reported:

  #491/u check deducing bounds from const, 5 FAIL
  Unexpected success to load!
  0: (b7) r0 = 0
  1: (75) if r0 s>= 0x0 goto pc+1
  3: (95) exit
  processed 3 insns, stack depth 0

  #491/p check deducing bounds from const, 5 FAIL
  Unexpected success to load!
  0: (b7) r0 = 0
  1: (75) if r0 s>= 0x0 goto pc+1
  3: (95) exit
  processed 3 insns, stack depth 0

Test result from 4.15.0-58:
  #491/u check deducing bounds from const, 6 OK
  #491/p check deducing bounds from const, 6 OK

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-60-generic 4.15.0-60.67
ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
Uname: Linux 4.15.0-60-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
 crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.7
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:
CurrentDmesg:
 [  540.701915] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
 [  540.708360] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Date: Wed Aug 28 03:14:59 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-60-generic N/A
 linux-backports-modules-4.15.0-60-generic  N/A
 linux-firmware 1.173.10
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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


** Tags: amd64 apport-bug bionic package-from-proposed uec-images

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  Test 491/u and 491/p from ubuntu_bpf failed on B

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

Bug description:
#491/u check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 = 0
1: (75) if r0 s>= 0x0 goto pc+1
3: (95) exit
processed 3 insns, stack depth 0

#491/p check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 = 0
1: (75) if r0 s>= 0x0 goto pc+1
3: (95) exit
processed 3 insns, stack depth 0

  Test result from 4.15.0-58:
#491/u check deducing bounds from const, 6 OK
#491/p check deducing bounds from const, 6 OK

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
   crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  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:
  CurrentDmesg:
   [  540.701915] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [  540.708360] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Aug 28 03:14:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  

[Kernel-packages] [Bug 1841704] [NEW] Test 391/u and 391/p from ubuntu_bpf failed on B

2019-08-27 Thread Po-Hsu Lin
Public bug reported:

#391/u bounds checks mixing signed and unsigned, variant 14 FAIL
  Unexpected error message!
  0: (61) r9 = *(u32 *)(r1 +8)
  1: (7a) *(u64 *)(r10 -8) = 0
  2: (bf) r2 = r10
  3: (07) r2 += -8
  4: (18) r1 = 0x0
  6: (85) call bpf_map_lookup_elem#1
  7: (15) if r0 == 0x0 goto pc+8
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
  8: (7a) *(u64 *)(r10 -16) = -8
  9: (79) r1 = *(u64 *)(r10 -16)
  10: (b7) r2 = -1
  11: (b7) r8 = 2
  12: (15) if r9 == 0x2a goto pc+6
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
  13: (6d) if r8 s> r1 goto pc+3
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
  14: (65) if r1 s> 0x1 goto pc+2
  17: (b7) r0 = 0
  18: (95) exit

  from 13 to 17: safe

  from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 
R8=inv2 R9=inv42 R10=fp0
  19: (2d) if r1 > r2 goto pc-3
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
  20: (05) goto pc-7
  14: (65) if r1 s> 0x1 goto pc+2
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) R2=inv-1 
R8=inv2 R9=inv42 R10=fp0
  15: (0f) r0 += r1
  R1 has unknown scalar with mixed signed bounds, pointer arithmetic with it 
prohibited for !root


  #391/p bounds checks mixing signed and unsigned, variant 14 FAIL
  Unexpected error message!
  0: (61) r9 = *(u32 *)(r1 +8)
  1: (7a) *(u64 *)(r10 -8) = 0
  2: (bf) r2 = r10
  3: (07) r2 += -8
  4: (18) r1 = 0x9391367ba400
  6: (85) call bpf_map_lookup_elem#1
  7: (15) if r0 == 0x0 goto pc+8
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
  8: (7a) *(u64 *)(r10 -16) = -8
  9: (79) r1 = *(u64 *)(r10 -16)
  10: (b7) r2 = -1
  11: (b7) r8 = 2
  12: (15) if r9 == 0x2a goto pc+6
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
  13: (6d) if r8 s> r1 goto pc+3
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
  14: (65) if r1 s> 0x1 goto pc+2
  17: (b7) r0 = 0
  18: (95) exit

  from 13 to 17: safe

  from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 
R8=inv2 R9=inv42 R10=fp0
  19: (2d) if r1 > r2 goto pc-3
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
  20: (05) goto pc-7
  14: (65) if r1 s> 0x1 goto pc+2
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) R2=inv-1 
R8=inv2 R9=inv42 R10=fp0
  15: (0f) r0 += r1
  math between map_value pointer and register with unbounded min value is not 
allowed

Test result with older kernel:
  #391/u bounds checks mixing signed and unsigned, variant 15 OK
  #391/p bounds checks mixing signed and unsigned, variant 15 OK

The test has passed but the variant number is different.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-60-generic 4.15.0-60.67
ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
Uname: Linux 4.15.0-60-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
 crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.7
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:
CurrentDmesg:

Date: Wed Aug 28 02:58:14 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:

ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-60-generic N/A
 linux-backports-modules-4.15.0-60-generic  N/A
 linux-firmware 1.173.10
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: 

[Kernel-packages] [Bug 1767654] Re: [Intel Braswell/Apollo Lake] Cursor gets stuck on left side of the screen

2019-08-27 Thread Daniel van Vugt
** Summary changed:

- [Intel Braswell] Cursor gets stuck on left side of the screen
+ [Intel Braswell/Apollo Lake] Cursor gets stuck on left side of the screen

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

Title:
  [Intel Braswell/Apollo Lake] Cursor gets stuck on left side of the
  screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1841661] Re: The cursor disappears, when I use GNOME on Wayland

2019-08-27 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1767654 ***
https://bugs.launchpad.net/bugs/1767654

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1767654, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1767654
   [Intel Braswell/Apollo Lake] Cursor gets stuck on left side of the screen

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

Title:
  The cursor disappears, when I use GNOME on Wayland

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
  P.S. Any screen recorders don't work on Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 22:36:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-25 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841661/+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 1730331] Re: ath10k_pci: firmware crashed!

2019-08-27 Thread Shahar Or
@mangoo-wpkg, that seems like valuable information upstream. Does anyone
know the procedure to get it upstream, please?

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

Title:
  ath10k_pci: firmware crashed!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware package in Fedora:
  Unknown

Bug description:
  ...
  Nov  4 18:35:50 akane kernel: [   10.216896] ath10k_pci :04:00.0: qca988x 
hw2.0 target 0x4100016c chip_id 0x043222ff sub :
  Nov  4 18:35:50 akane kernel: [   10.216908] ath10k_pci :04:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
  Nov  4 18:35:50 akane kernel: [   10.217641] ath10k_pci :04:00.0: 
firmware ver 10.2.4.70.63-2 api 5 features 
no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
  Nov  4 18:35:50 akane kernel: [   10.228600] kvm: Nested Virtualization 
enabled
  Nov  4 18:35:50 akane kernel: [   10.228611] kvm: Nested Paging enabled
  Nov  4 18:35:50 akane kernel: [   10.258913] ath10k_pci :04:00.0: 
board_file api 1 bmi_id N/A crc32 bebc7c08
  Nov  4 18:35:50 akane kernel: [   10.263535] MCE: In-kernel MCE decoding 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271401] EDAC amd64: Node 0: DRAM ECC 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271416] EDAC amd64: F16h_M30h detected 
(node 0).
  Nov  4 18:35:50 akane kernel: [   10.271491] EDAC MC: DCT0 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271494] EDAC amd64: MC: 0:  4096MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271523] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271526] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271528] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271530] EDAC MC: DCT1 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271532] EDAC amd64: MC: 0: 0MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271534] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271537] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271539] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271541] EDAC amd64: using x4 syndromes.
  Nov  4 18:35:50 akane kernel: [   10.271542] EDAC amd64: MCT channel count: 1
  Nov  4 18:35:50 akane kernel: [   10.271829] EDAC MC0: Giving out device to 
module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT)
  Nov  4 18:35:50 akane kernel: [   10.271892] EDAC PCI0: Giving out device to 
module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED)
  Nov  4 18:35:50 akane kernel: [   10.271894] AMD64 EDAC driver v3.5.0
  Nov  4 18:35:50 akane kernel: [   10.532131] EXT4-fs (sdc1): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
  Nov  4 18:35:50 akane kernel: [   10.575859] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
  Nov  4 18:35:50 akane kernel: [   11.397803] ath10k_pci :04:00.0: 
firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa)
  Nov  4 18:35:50 akane kernel: [   11.407389] ath10k_pci :04:00.0: qca988x 
hw2.0 target 0x4100016c chip_id 0x043222ff sub :
  Nov  4 18:35:50 akane kernel: [   11.407395] ath10k_pci :04:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
  Nov  4 18:35:50 akane kernel: [   11.408085] ath10k_pci :04:00.0: 
firmware ver 10.2.4.70.63-2 api 5 features 
no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
  Nov  4 18:35:50 akane kernel: [   11.408148] ath10k_pci :04:00.0: 
board_file api 1 bmi_id N/A crc32 bebc7c08
  Nov  4 18:35:50 akane kernel: [   11.408156] ath10k_pci :04:00.0: htt-ver 
0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
  Nov  4 18:35:50 akane kernel: [   11.410197] ath10k_pci :04:00.0: 
firmware register dump:
  Nov  4 18:35:50 akane kernel: [   11.416213] ath10k_pci :04:00.0: [00]: 
0x4100016C 0x15B3 0x009BFF84 0x00955B31
  Nov  4 18:35:50 akane kernel: [   11.424559] ath10k_pci :04:00.0: [04]: 
0x009BFF84 0x00060130 0x0013 0x
  Nov  4 18:35:50 akane kernel: [   11.432767] ath10k_pci :04:00.0: [08]: 
0x009C8EA4 0x7170 0x0001 0x00435300
  Nov  4 18:35:50 akane kernel: [   11.441059] ath10k_pci :04:00.0: [12]: 
0x0009 0x 0x00958360 0x0095836B
  Nov  4 18:35:50 akane kernel: [   11.449397] ath10k_pci :04:00.0: [16]: 
0x00958080 0x0094078E 0x 0x
  Nov  4 18:35:50 akane kernel: [   11.457686] ath10k_pci :04:00.0: [20]: 
0x409BFF84 0x0040AB44 0x004101E0 0x000C
  Nov  4 18:35:50 akane kernel: [   11.466132] ath10k_pci :04:00.0: [24]: 
0x809BFE1C 0x0040ABA4 0x0006 0xC09BFF84
  Nov  4 18:35:50 akane kernel: [   11.474583] ath10k_pci :04:00.0: [28]: 
0x8098E907 

[Kernel-packages] [Bug 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04

2019-08-27 Thread Daniel van Vugt
Pander, please open a new bug by running:

  ubuntu-bug linux

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796573/+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 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04

2019-08-27 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

---

Pander, please open a new bug by running:

  ubuntu-bug linux.

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796573/+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 1841614] Re: Doesn't start

2019-08-27 Thread Alex Murray
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Doesn't start

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello everybody.

  I have an old 32 bit acer 1672 wlmi laptop and I have installed on it
  linux mint xfde 19.2 Tina with the  latest kernel. I have installed
  some previous kernels also to avoid make format again and again. The
  latest kernel doesn't work propeprly as times as install it on.  have
  erased a lot of times to make the perfect installation. Sometimes pc
  doesn't start at all, sometimes needs to enter the pass more than two
  times and sometimes doesn't shut down.

  I am waiting for your instructions.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841614/+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 1841614]

2019-08-27 Thread Alex Murray
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!

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

Title:
  Doesn't start

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello everybody.

  I have an old 32 bit acer 1672 wlmi laptop and I have installed on it
  linux mint xfde 19.2 Tina with the  latest kernel. I have installed
  some previous kernels also to avoid make format again and again. The
  latest kernel doesn't work propeprly as times as install it on.  have
  erased a lot of times to make the perfect installation. Sometimes pc
  doesn't start at all, sometimes needs to enter the pass more than two
  times and sometimes doesn't shut down.

  I am waiting for your instructions.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841614/+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 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances

2019-08-27 Thread Tiago Pasqualini da Silva
Fix up for review: https://review.opendev.org/#/c/678956/

** Changed in: charm-neutron-openvswitch
 Assignee: (unassigned) => Tiago Pasqualini da Silva (tiago.pasqualini)

** Changed in: charm-neutron-openvswitch
   Status: Confirmed => In Progress

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

Title:
  After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic
  to instances

Status in OpenStack neutron-openvswitch charm:
  In Progress
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With an environment running Xenial-Queens, and having just upgraded
  the linux-image-generic kernel for MDS patching, a few of our
  hypervisor hosts that were rebooted (3 out of 100) ended up dropping
  IP (tcp/udp) ingress traffic.

  It turns out that nf_conntrack module was loaded, but
  nf_conntrack_ipv4 was not loading, and the traffic was being dropped
  by this rule:

   table=72, n_packets=214989, priority=50,ct_state=+inv+trk
  actions=resubmit(,93)

  The ct_state "inv" means invalid conntrack state, which the manpage
  describes as:

   The state is invalid, meaning that the connection tracker
   couldn’t identify the connection. This flag is a catch-
   all for problems in the connection or the connection
   tracker, such as:

   • L3/L4 protocol handler is not loaded/unavailable.
  With the Linux kernel datapath, this may mean that
  the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules
  are not loaded.

   • L3/L4 protocol handler determines that the packet
  is malformed.

   • Packets are unexpected length for protocol.

  It appears that there may be an issue when patching the OS of a
  hypervisor not running instances may fail to update initrd to load
  nf_conntrack_ipv4 (and/or _ipv6).

  I couldn't find anywhere in the charm code that this would be loaded
  unless the charm's "harden" option is used on nova-compute charm (see
  charmhelpers contrib/host templates).  It is unset in our environment,
  so we are not using any special module probing.

  Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel
  upgrades or is it possible that the charm should define a modprobe
  file if we have the OVS firewall driver configured?

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+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 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu

2019-08-27 Thread Gustavo Romero
Sorry, agent looks missing on proposed for Xenial. Canonical, could you
please check it?

There is no libperf-jvmti.so afaics.

I'm marking it as 'verification-failed-xenial'.

gromero@gromero16:/tmp$ dpkg -L linux-tools-4.4.0-160 
/.
/usr
/usr/lib
/usr/lib/linux-tools-4.4.0-160
/usr/lib/linux-tools-4.4.0-160/perf
/usr/lib/linux-tools-4.4.0-160/usbip
/usr/lib/linux-tools-4.4.0-160/cpupower
/usr/lib/linux-tools-4.4.0-160/usbipd
/usr/lib/libcpupower.so.4.4.0-160
/usr/share
/usr/share/doc
/usr/share/doc/linux-tools-4.4.0-160
/usr/share/doc/linux-tools-4.4.0-160/changelog.Debian.gz
/usr/share/doc/linux-tools-4.4.0-160/copyright
gromero@gromero16:/tmp$ dpkg -L linux-tools-4.4.0-160-generic
/.
/usr
/usr/lib
/usr/lib/linux-tools
/usr/lib/linux-tools/4.4.0-160-generic
/usr/share
/usr/share/doc
/usr/share/doc/linux-tools-4.4.0-160-generic
/usr/share/doc/linux-tools-4.4.0-160-generic/copyright
/usr/lib/linux-tools/4.4.0-160-generic/perf
/usr/lib/linux-tools/4.4.0-160-generic/usbip
/usr/lib/linux-tools/4.4.0-160-generic/cpupower
/usr/lib/linux-tools/4.4.0-160-generic/usbipd
/usr/share/doc/linux-tools-4.4.0-160-generic/changelog.Debian.gz
gromero@gromero16:/tmp$ uname -a
Linux gromero16 4.4.0-160-generic #188-Ubuntu SMP Wed Aug 14 04:17:46 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux
gromero@gromero16:/tmp$ ls -l /usr/lib/linux-tools-4.4.0-160
total 10776
-rwxr-xr-x 1 root root   230096 Aug 14 00:53 cpupower
-rwxr-xr-x 1 root root 10314320 Aug 14 00:53 perf
-rwxr-xr-x 1 root root   260112 Aug 14 00:53 usbip
-rwxr-xr-x 1 root root   218056 Aug 14 00:53 usbipd
gromero@gromero16:/tmp$ 


** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws-edge package in Ubuntu:
  Fix Committed
Status in linux-aws-hwe package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-aws-edge source package in Xenial:
  Invalid
Status in linux-aws-hwe source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in linux-aws source package in Artful:
  Invalid
Status in linux-aws-edge source package in Artful:
  Invalid
Status in linux-aws-hwe source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws-edge source package in Bionic:
  Fix Committed
Status in linux-aws-hwe source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in linux-aws source package in Cosmic:
  Invalid
Status in linux-aws-edge source package in Cosmic:
  Invalid
Status in linux-aws-hwe source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-aws source package in Disco:
  Fix Committed
Status in linux-aws-edge source package in Disco:
  Invalid
Status in linux-aws-hwe source package in Disco:
  Invalid

Bug description:
  [Impact]
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods.

  [Test case]
  $ sudo perf record -k 1 -e instructions:u ./java 
-agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32
  $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted
  $ sudo perf report -f -i ./perf.data.jitted

  [Fix]
  Include java build dependencies and install the library into linux-tools 
package.

  [Regression potential]
  Small regression potential, an extra file is distributed and is not 
automatically linked to anything. It could impact the build, which was tested.

  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods

  ---uname output---
  linux-image-4.13.0-36-generic

  Machine Type = not relevant

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

  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being 

[Kernel-packages] [Bug 1841681] [NEW] Disco update: upstream stable patchset 2019-08-27

2019-08-27 Thread Kamal Mostafa
Public bug reported:

SRU Justification

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

   upstream stable patchset 2019-08-27

Ported from the following upstream stable releases:
v4.19.64, v5.2.6,
v4.19.65, v5.2.7

   from git://git.kernel.org/

hv_sock: Add support for delayed close
vsock: correct removal of socket from the list
ISDN: hfcsusb: checking idx of ep configuration
media: au0828: fix null dereference in error path
ath10k: Change the warning message string
media: cpia2_usb: first wake up, then free in disconnect
media: pvrusb2: use a different format for warnings
NFS: Cleanup if nfs_match_client is interrupted
media: radio-raremono: change devm_k*alloc to k*alloc
Bluetooth: hci_uart: check for missing tty operations
sched/fair: Don't free p->numa_faults with concurrent readers
sched/fair: Use RCU accessors consistently for ->numa_group
/proc//cmdline: remove all the special cases
/proc//cmdline: add back the setproctitle() special case
drivers/pps/pps.c: clear offset flags in PPS_SETPARAMS ioctl
Fix allyesconfig output.
ceph: hold i_ceph_lock when removing caps for freeing inode
ip_tunnel: allow not to count pkts on tstats by setting skb's dev to NULL
xfrm: policy: fix bydst hlist corruption on hash rebuild
nvme: fix multipath crash when ANA is deactivated
UBUNTU: upstream stable to v4.19.64, v5.2.6
ARM: riscpc: fix DMA
ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
ftrace: Enable trampoline when rec count returns back to one
dmaengine: tegra-apb: Error out if DMA_PREP_INTERRUPT flag is unset
arm64: dts: rockchip: fix isp iommu clocks and power domain
kernel/module.c: Only return -EEXIST for modules that have finished loading
firmware/psci: psci_checker: Park kthreads before stopping them
MIPS: lantiq: Fix bitfield masking
dmaengine: rcar-dmac: Reject zero-length slave DMA requests
clk: tegra210: fix PLLU and PLLU_OUT1
fs/adfs: super: fix use-after-free bug
clk: sprd: Add check for return value of sprd_clk_regmap_init()
btrfs: fix minimum number of chunk errors for DUP
btrfs: qgroup: Don't hold qgroup_ioctl_lock in btrfs_qgroup_inherit()
cifs: Fix a race condition with cifs_echo_request
ceph: fix improper use of smp_mb__before_atomic()
ceph: return -ERANGE if virtual xattr value didn't fit in buffer
ACPI: blacklist: fix clang warning for unused DMI table
scsi: zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized
perf version: Fix segfault due to missing OPT_END()
x86: kvm: avoid constant-conversion warning
ACPI: fix false-positive -Wuninitialized warning
be2net: Signal that the device cannot transmit during reconfiguration
x86/apic: Silence -Wtype-limits compiler warnings
x86: math-emu: Hide clang warnings for 16-bit overflow
mm/cma.c: fail if fixed declaration can't be honored
lib/test_overflow.c: avoid tainting the kernel and fix wrap size
lib/test_string.c: avoid masking memset16/32/64 failures
coda: add error handling for fget
coda: fix build using bare-metal toolchain
uapi linux/coda_psdev.h: move upc_req definition from uapi to kernel side 
headers
drivers/rapidio/devices/rio_mport_cdev.c: NUL terminate some strings
ipc/mqueue.c: only perform resource calculation if user valid
xen/pv: Fix a boot up hang revealed by int3 self test
x86/kvm: Don't call kvm_spurious_fault() from .fixup
x86/paravirt: Fix callee-saved function ELF sizes
x86, boot: Remove multiple copy of static function sanitize_boot_params()
drm/nouveau: fix memory leak in nouveau_conn_reset()
kconfig: Clear "written" flag to avoid data loss
kbuild: initialize CLANG_FLAGS correctly in the top Makefile
Btrfs: fix incremental send failure after deduplication
Btrfs: fix race leading to fs corruption after transaction abort
mmc: dw_mmc: Fix occasional hang after tuning on eMMC
mmc: meson-mx-sdio: Fix misuse of GENMASK macro
gpiolib: fix incorrect IRQ requesting of an active-low lineevent
IB/hfi1: Fix Spectre v1 vulnerability
mtd: rawnand: micron: handle on-die "ECC-off" devices correctly
selinux: fix memory leak in policydb_init()
ALSA: hda: Fix 1-minute detection delay when i915 module is not available
mm: vmscan: check if mem cgroup is disabled or not before calling memcg slab 
shrinker
s390/dasd: fix endless loop after read unit address configuration
cgroup: kselftest: relax fs_spec checks
parisc: Fix build of compressed kernel even with debug enabled
drivers/perf: arm_pmu: Fix failure path in PM notifier
arm64: compat: Allow 

Re: [Kernel-packages] [Bug 1841661] Re: The cursor disappears, when I use GNOME on Wayland

2019-08-27 Thread Artyom Pozharov
Oh thank you, sir!

ср, 28 авг. 2019 г., 0:01 Iain Lane :

> On Tue, Aug 27, 2019 at 07:47:53PM -, Artyom Pozharov wrote:
> > Public bug reported:
> >
> > Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
>
> Yes, thanks for filing. I showed this to the upstream guys and they knew
> about it. It's apparently a kernel problem as if you revert to kernel
> 5.0 it goes away. So I'll reassign this bug to linux - maybe we can find
> out when it was introduced if the kernel team can help us to bisect.
>
> Cheers,
>
> --
> Iain Lane  [ i...@orangesquash.org.uk ]
> Debian Developer   [ la...@debian.org ]
> Ubuntu Developer   [ la...@ubuntu.com ]
>
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Confirmed
>
> ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1841661
>
> Title:
>   The cursor disappears, when I use GNOME on Wayland
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
>   P.S. Any screen recorders don't work on Wayland.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell 3.33.91-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
>   Uname: Linux 5.2.0-13-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Aug 27 22:36:59 2019
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2019-08-25 (2 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
>   ProcEnviron:
>LANGUAGE=ru_UA:ru
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_UA.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841661/+subscriptions
>

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

Title:
  The cursor disappears, when I use GNOME on Wayland

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
  P.S. Any screen recorders don't work on Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 22:36:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-25 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841661/+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 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04

2019-08-27 Thread Pander
I have tried that on 19.04 with kernel 5.0.0-25-generic but it did not
work. What are ways to debug this?

/sys/class/leds/asus::kbd_backlight/brightness exists and can hold a
value of 0, 1, 2 or 3. Lower than 0 results in

bash: echo: write error: Invalid argument

Values over 3 result in 3.

Tree is

# ls -ltra /sys/class/leds/asus::kbd_backlight/
total 0
-rw-r--r-- 1 root root 4096 Aug 27 22:45 uevent
drwxr-xr-x 4 root root0 Aug 27 22:45 ..
lrwxrwxrwx 1 root root0 Aug 27 22:45 subsystem -> ../../../../../class/leds
-r--r--r-- 1 root root 4096 Aug 27 22:45 max_brightness
-r--r--r-- 1 root root 4096 Aug 27 22:45 brightness_hw_changed
-rw-r--r-- 1 root root 4096 Aug 27 22:46 trigger
drwxr-xr-x 2 root root0 Aug 27 22:46 power
lrwxrwxrwx 1 root root0 Aug 27 22:46 device -> ../../../asus-nb-wmi
-rw-r--r-- 1 root root 4096 Aug 27 22:51 brightness
drwxr-xr-x 3 root root0 Aug 27 22:53 .

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

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

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796573/+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 1841661] Re: The cursor disappears, when I use GNOME on Wayland

2019-08-27 Thread Iain Lane
On Tue, Aug 27, 2019 at 07:47:53PM -, Artyom Pozharov wrote:
> Public bug reported:
> 
> Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8

Yes, thanks for filing. I showed this to the upstream guys and they knew
about it. It's apparently a kernel problem as if you revert to kernel
5.0 it goes away. So I'll reassign this bug to linux - maybe we can find
out when it was introduced if the kernel team can help us to bisect.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

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

Title:
  The cursor disappears, when I use GNOME on Wayland

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
  P.S. Any screen recorders don't work on Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 22:36:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-25 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841661/+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 1841661] [NEW] The cursor disappears, when I use GNOME on Wayland

2019-08-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
P.S. Any screen recorders don't work on Wayland.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.33.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
Uname: Linux 5.2.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 27 22:36:59 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-25 (2 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan wayland-session
-- 
The cursor disappears, when I use GNOME on Wayland 
https://bugs.launchpad.net/bugs/1841661
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1791143] Re: Suggestion to make zfsutils-linux a snap

2019-08-27 Thread Sam Van den Eynde
As kernels 5.2.0-x will bring zfs 0.8.x to Bionic LTS, I'd like to draw
some attention to this request. People will get the 0.8.x zfs module via
HWE but won't be able to do much with the major new features without the
userland tools.

I tried to install the debs from Eoan, but they require a higher libc
version which complicates that route a lot.

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

Title:
  Suggestion to make zfsutils-linux a snap

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  This circumvents the need to keep it on the same major version
  throughout the LTS cycle. LXD is doing snaps, perhaps for zfs this is
  the best approach as well.

  Xenial still has zfsutils on generation 0.6, with the module on 0.7.
  Even when patches are applied as needed that approach has its
  limitations. E.g. the Bionic cycle might possibly see 2 major zfs
  releases, who'll say.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1791143/+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 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841544/+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 787210] Re: ath9k drivers freeze the system when changing state

2019-08-27 Thread Sam Van den Eynde
** Changed in: linux (Ubuntu)
   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/787210

Title:
  ath9k drivers freeze the system when changing state

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: linux-image-generic

  The ath9k driver freezes the laptop when the adapter changes state.
  Reproduceable by enabling/disabling wireless adapter using the network
  manager applet, or by suspending the system. The issue exists at least
  in 10.10 as well, but never had issues running 10.04. Since applicable
  in several kernel versions, reported this against linux-image-generic.
  It's 32 bit stock kernel, latest updates, Natty 11.04 i386.

  On 10.10 the system got freezes randomly just while browsing, which
  was even worse. Used compat-wireless which made it much better but not
  perfect (only freezes on state changes as mentioned above).

  I am 100% sure it is triggered by the wireless driver: issuing "rmmod
  ath9k ath9k_common ath9k_hw ath" prior to suspending the laptop,
  followed by "modprobe ath9k" after resume, makes the freeze disappear.
  I actually added a script in /etc/pm.d/sleep.d issuing these commands
  and now laptop works normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-generic 2.6.38.8.22
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam1773 F xfce4-volumed
sam1794 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0x9310 irq 23'
 Mixer name : 'Nvidia MCP79/7A HDMI'
 Components : 'HDA:111d7605,103c3651,00100402 
HDA:10de0007,10de0101,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Mon May 23 22:55:40 2011
  InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release i386 (20110426.1)
  MachineType: Hewlett-Packard Compaq Mini 311-1100
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=76ad9066-c058-4318-95ea-d214f8737341 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.52
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3651
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 49.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.12:bd11/07/2009:svnHewlett-Packard:pnCompaqMini311-1100:pvr048F11201C032:rvnHewlett-Packard:rn3651:rvr49.18:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Compaq Mini 311-1100
  dmi.product.version: 048F11201C032
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/787210/+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 1840571] Re: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+

2019-08-27 Thread Seiichi Nakashima
I update kernel 5.3-rc6 at this mail client environment.
kernel 5.3-rc6 may work fine at BIOS only PC.
I remained to use other PC, that are BIOS only, UEFI only.
step by step, I wish to test.

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

Title:
  ubuntu 18.04.3 startup purple screen blink and could not start with
  kernel 5.0.0+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I update ubuntu by software-updater.
  I update kernel 5.0.0-25, and reboot ubuntu system,
  but startup purple screen blink for ever,and could not login.
  I reboot kernel 5.0.0-23(before kernel), and login.

  as kernel 5.0.0-23, sometime same event occured,
  but I reset PC, next time restart normaly.

  I upload syslog file.

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-05-31 (83 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Tags: bionic third-party-packages
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (86 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840571/+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 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
- phase: Ready for Packaging
- phase-changed: Tuesday, 27. August 2019 19:31 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 27. August 2019 19:35 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Packaging
  phase-changed: Tuesday, 27. August 2019 19:35 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841658/+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 1839995] Re: bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

2019-08-27 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658

** This bug is no longer a duplicate of bug 1840974
   bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker
** This bug has been marked a duplicate of bug 1841658
   linux-ibm-gt:  -proposed tracker

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Testing
  phase-changed: Monday, 19. August 2019 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839995/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

2019-08-27 Thread Khaled El Mously
** Summary changed:

- disco/linux-oracle: 5.0.0-1001.1 -proposed tracker
+ disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
promote-to-proposed: Stalled -- packages no longer available
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1839277] Re: bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker

2019-08-27 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658

** This bug is no longer a duplicate of bug 1840974
   bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker
** This bug has been marked a duplicate of bug 1841658
   linux-ibm-gt:  -proposed tracker

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Complete
  phase-changed: Tuesday, 13. August 2019 11:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839277/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840826 (bionic/linux-oracle-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Stalled -- packages no longer available
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
promote-to-proposed: Stalled -- packages no longer available
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1841658] Re: bionic/linux-ibm-gt: -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Summary changed:

- linux-ibm-gt:  -proposed tracker
+ bionic/linux-ibm-gt:  -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841086
+ packages:
+   main: linux-ibm-gt
+   meta: linux-meta-ibm-gt
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 27. August 2019 19:31 UTC
+ reason:
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Packaging
  phase-changed: Tuesday, 27. August 2019 19:35 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841658/+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 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

2019-08-27 Thread Marcelo Cerri
** Summary changed:

- bionic/linux-ibm-gt:  -proposed tracker
+ bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

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

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

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

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

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Packaging
  phase-changed: Tuesday, 27. August 2019 19:35 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841658/+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 1839108] Re: bionic/linux-ibm-gt: 4.15.0-1030.32 -proposed tracker

2019-08-27 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658

** This bug is no longer a duplicate of bug 1840974
   bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker
** This bug has been marked a duplicate of bug 1841658
   linux-ibm-gt:  -proposed tracker

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1030.32 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Testing
  phase-changed: Wednesday, 07. August 2019 07:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839108/+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 1840974] Re: bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker

2019-08-27 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658

** Tags removed: kernel-sru-derivative-of-1841086

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Testing
  phase-changed: Thursday, 22. August 2019 14:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

** This bug has been marked a duplicate of bug 1841658
   linux-ibm-gt:  -proposed tracker

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Testing
  phase-changed: Thursday, 22. August 2019 14:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840974/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Signoff
  phase-changed: Monday, 26. August 2019 14:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1841084
bionic/linux-fips: bug 1839998
bionic/linux-gke-4.15: bug 1839992
-   bionic/linux-ibm-gt: bug 1840974
+   bionic/linux-ibm-gt: bug 1841658
bionic/linux-kvm: bug 1839993
bionic/linux-oem: bug 1839980
bionic/linux-oracle: bug 1839997
bionic/linux-raspi2: bug 1839977
bionic/linux-snapdragon: bug 1839979
bionic/linux/pc-kernel: bug 1841078
bionic/linux/pc-lowlatency-kernel: bug 1841080
xenial/linux-azure: bug 1840002
xenial/linux-gcp: bug 1840674
xenial/linux-hwe: bug 1841085
  variant: debs

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

Title:
  bionic/linux: 4.15.0-60.67 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Signoff
  phase-changed: Monday, 26. August 2019 14:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1841084
bionic/linux-fips: bug 1839998
bionic/linux-gke-4.15: bug 1839992
bionic/linux-ibm-gt: bug 1841658
bionic/linux-kvm: bug 1839993
bionic/linux-oem: bug 1839980
bionic/linux-oracle: bug 1839997
bionic/linux-raspi2: bug 1839977
bionic/linux-snapdragon: bug 1839979
bionic/linux/pc-kernel: bug 1841078
bionic/linux/pc-lowlatency-kernel: bug 1841080
xenial/linux-azure: bug 1840002
xenial/linux-gcp: bug 1840674
xenial/linux-hwe: bug 1841085
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1841658] [NEW] bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

2019-08-27 Thread Marcelo Cerri
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

-- swm properties --
kernel-stable-master-bug: 1841086
packages:
  main: linux-ibm-gt
  meta: linux-meta-ibm-gt
phase: Packaging
phase-changed: Tuesday, 27. August 2019 19:35 UTC
reason:
  prepare-package: Pending -- package not yet uploaded
  prepare-package-meta: Pending -- package not yet uploaded
variant: debs

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

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

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

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

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: Invalid

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

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Invalid


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.08.12-8 kernel-sru-derivative-of-1841086

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: 

[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu28

---
zfs-linux (0.6.5.6-0ubuntu28) xenial; urgency=medium

  * Fix ZFS shrinker deadlock with xattrs (LP: #1839521)
- Upstream ZFS fix 31b6111fd92a ("Kill zp->z_xattr_parent to prevent 
pinning")
  and ddae16a9cf0b ("xattr dir doesn't get purged during iput") fix a 
deadlock
  in shrinker path when a xattr directory inode and its xattr inode are in 
the
  same disposal list and the xattr dir inode is evicted before the xattr 
inode.

 -- Mauricio Faria de Oliveira   Wed, 07 Aug 2019
11:01:11 -0300

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Xenial: ZFS deadlock in shrinker path with xattrs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Xenial's ZFS can deadlock in the memory shrinker path
     after removing files with extended attributes (xattr).

   * Extended attributes are enabled by default, but are
     _not_ used by default, which reduces the likelyhood.

   * It's very difficult/rare to reproduce this problem,
     due to file/xattr/remove/shrinker/lru order/timing
     circumstances required. (weeks for a reporter user)
     but a synthetic test-case has been found for tests.

  [Test Case]

   * A synthetic reproducer is available for this LP,
     with a few steps to touch/setfattr/rm/drop_caches
     plus a kernel module to massage the disposal list.
 (comment #8)

   * In the original ZFS module:
     the xattr dir inode is not purged immediately on
     file removal, but possibly purged _two_ shrinker
     invocations later.  This allows for other thread
     started before file remove to call zfs_zget() on
     the xattr child inode and iput() it, so it makes
     to the same disposal list as the xattr dir inode.
 (comment #3)

   * In the modified ZFS module:
     the xattr dir inode is purged immediately on file
     removal not possibly later on shrinker invocation,
     so the problem window above doesn't exist anymore.
 (comment #12)

  [Regression Potential]

   * Low. The patches are confined to extended attributes
     in ZFS, specifically node removal/purge, and another
     change how an xattr child inode tracks its xattr dir
     (parent) inode, so that it can be purged immediately
     on removal.

   * The ZFS test-suite has been run on original/modified
     zfs-dkms package/kernel modules, with no regressions.
 (comment #11)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+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 1839521] Update Released

2019-08-27 Thread Brian Murray
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Xenial: ZFS deadlock in shrinker path with xattrs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Xenial's ZFS can deadlock in the memory shrinker path
     after removing files with extended attributes (xattr).

   * Extended attributes are enabled by default, but are
     _not_ used by default, which reduces the likelyhood.

   * It's very difficult/rare to reproduce this problem,
     due to file/xattr/remove/shrinker/lru order/timing
     circumstances required. (weeks for a reporter user)
     but a synthetic test-case has been found for tests.

  [Test Case]

   * A synthetic reproducer is available for this LP,
     with a few steps to touch/setfattr/rm/drop_caches
     plus a kernel module to massage the disposal list.
 (comment #8)

   * In the original ZFS module:
     the xattr dir inode is not purged immediately on
     file removal, but possibly purged _two_ shrinker
     invocations later.  This allows for other thread
     started before file remove to call zfs_zget() on
     the xattr child inode and iput() it, so it makes
     to the same disposal list as the xattr dir inode.
 (comment #3)

   * In the modified ZFS module:
     the xattr dir inode is purged immediately on file
     removal not possibly later on shrinker invocation,
     so the problem window above doesn't exist anymore.
 (comment #12)

  [Regression Potential]

   * Low. The patches are confined to extended attributes
     in ZFS, specifically node removal/purge, and another
     change how an xattr child inode tracks its xattr dir
     (parent) inode, so that it can be purged immediately
     on removal.

   * The ZFS test-suite has been run on original/modified
     zfs-dkms package/kernel modules, with no regressions.
 (comment #11)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+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 1840835] Re: High power consumption using 5.0.0-25-generic

2019-08-27 Thread George Kapetanos
** Attachment added: "dmesg50028nvidia"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+attachment/5285033/+files/dmesg50028nvidia

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

Title:
  High power consumption using 5.0.0-25-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to 5.0.0-25-generic kernel, battery life is
  considerably less and power consumption is about 10 watts more idle,
  using integrated graphics. This is a hybrid GPU laptop Intel HD
  630/GP107M, and a possible cause is not powering off the dedicated GPU
  completely while using the integrated.

  nvidia-driver-430
  GP107M [GeForce GTX 1050 Mobile]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1840835] Re: High power consumption using 5.0.0-25-generic

2019-08-27 Thread George Kapetanos
I installed the test kernel:
linux-headers-5.0.0-28_5.0.0-28.29~lp1840835_all.deb
linux-headers-5.0.0-28-generic_5.0.0-28.29~lp1840835_amd64.deb
linux-image-unsigned-5.0.0-28-generic_5.0.0-28.29~lp1840835_amd64.deb
linux-modules-5.0.0-28-generic_5.0.0-28.29~lp1840835_amd64.deb
linux-modules-extra-5.0.0-28-generic_5.0.0-28.29~lp1840835_amd64.deb

uname -r: 5.0.0-28-generic

Power consumption was completely normal, idling at less than 4 watts as 
expected. While using iGPU, I noticed that each time I run lspci, it lags for 
less than a second and the following messages appear on dmesg:
[7.587195] snd_hda_codec_hdmi hdaudioC1D0: Unable to sync register 
0x7f0800. -5
[7.587200] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1

On file dmesg50028 I provide the dmesg output.

I switch to nvidia gpu for test purposes. Everything is normal, and
those messages only appear at gpu initialization, and lspci didnt lag at
all. On file dmesg50028nvidia I provide the dmesg output after switching
to nvidia gpu.

Excluding those messages, I conclude that it fixes the power consumption
problem.

** Attachment added: "dmesg50028"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+attachment/5285032/+files/dmesg50028

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

Title:
  High power consumption using 5.0.0-25-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to 5.0.0-25-generic kernel, battery life is
  considerably less and power consumption is about 10 watts more idle,
  using integrated graphics. This is a hybrid GPU laptop Intel HD
  630/GP107M, and a possible cause is not powering off the dedicated GPU
  completely while using the integrated.

  nvidia-driver-430
  GP107M [GeForce GTX 1050 Mobile]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1832144] Re: Ubuntu 19.04 suspend freeze on Dell inspiron 7373

2019-08-27 Thread Sean Yang
It broke again today :( Maybe the the solution earlier didn't work

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

Title:
  Ubuntu 19.04 suspend freeze on Dell inspiron 7373

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 19.04 in my Dell Inspiron 7373 and I am
  getting issues with suspend. When I lock the case or write the
  "systemctl suspend" command, the screen turn off, the system freeze
  and the laptop keeps turned on. I need to force the laptop turn off
  and on again. There are some cases when it suspends without issues,
  but most of the time it freezes.

  There are some workarounds for issues like this one but they are
  mostly for laptops using nvidia graphics.

  I am not sure how to provide debug information about this issue, but I
  can give it if someone tells me how to do it.

  "lsb_release -rd" output:
  Description:Ubuntu 19.04
  Release:19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144/+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 1841652] [NEW] Bionic update: upstream stable patchset 2019-08-27

2019-08-27 Thread Kamal Mostafa
Public bug reported:

SRU Justification

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

   upstream stable patchset 2019-08-27

Ported from the following upstream stable releases:
v4.14.140, v4.19.68

   from git://git.kernel.org/

sh: kernel: hw_breakpoint: Fix missing break in switch statement
mm/usercopy: use memory range to be accessed for wraparound check
mm/memcontrol.c: fix use after free in mem_cgroup_iter()
bpf: get rid of pure_initcall dependency to enable jits
bpf: restrict access to core bpf sysctls
bpf: add bpf_jit_limit knob to restrict unpriv allocations
xtensa: add missing isync to the cpu_reset TLB code
ALSA: hda - Apply workaround for another AMD chip 1022:1487
ALSA: hda - Fix a memory leak bug
ALSA: hda - Add a generic reboot_notify
ALSA: hda - Let all conexant codec enter D3 when rebooting
HID: holtek: test for sanity of intfdata
HID: hiddev: avoid opening a disconnected device
HID: hiddev: do cleanup in failure of opening a device
Input: kbtab - sanity check for endpoint type
Input: iforce - add sanity checks
net: usb: pegasus: fix improper read if get_registers() fail
netfilter: ebtables: also count base chain policies
clk: at91: generated: Truncate divisor to GENERATED_MAX_DIV + 1
clk: renesas: cpg-mssr: Fix reset control race condition
xen/pciback: remove set but not used variable 'old_state'
irqchip/gic-v3-its: Free unused vpt_page when alloc vpe table fail
irqchip/irq-imx-gpcv2: Forward irq type to parent
perf header: Fix divide by zero error if f_header.attr_size==0
perf header: Fix use of unitialized value warning
libata: zpodd: Fix small read overflow in zpodd_get_mech_type()
drm/bridge: lvds-encoder: Fix build error while CONFIG_DRM_KMS_HELPER=m
scsi: hpsa: correct scsi command status issue after reset
scsi: qla2xxx: Fix possible fcport null-pointer dereferences
ata: libahci: do not complain in case of deferred probe
kbuild: modpost: handle KBUILD_EXTRA_SYMBOLS only for external modules
arm64/efi: fix variable 'si' set but not used
arm64: unwind: Prohibit probing on return_address()
arm64/mm: fix variable 'pud' set but not used
IB/core: Add mitigation for Spectre V1
IB/mad: Fix use-after-free in ib mad completion handling
drm: msm: Fix add_gpu_components
ocfs2: remove set but not used variable 'last_hash'
asm-generic: fix -Wtype-limits compiler warnings
UBUNTU: [Packaging] update retpoline for get_order rework
KVM: arm/arm64: Sync ICH_VMCR_EL2 back when about to block
staging: comedi: dt3000: Fix signed integer overflow 'divider * base'
staging: comedi: dt3000: Fix rounding up of timer divisor
iio: adc: max9611: Fix temperature reading in probe
USB: core: Fix races in character device registration and deregistraion
usb: gadget: udc: renesas_usb3: Fix sysfs interface of "role"
usb: cdc-acm: make sure a refcount is taken early enough
USB: CDC: fix sanity checks in CDC union parser
USB: serial: option: add D-Link DWM-222 device ID
USB: serial: option: Add support for ZTE MF871A
USB: serial: option: add the BroadMobi BM818 card
USB: serial: option: Add Motorola modem UARTs
bpf: fix bpf_jit_limit knob for PAGE_SIZE >= 64K
arm64: ftrace: Ensure module ftrace trampoline is coherent with I-side
netfilter: conntrack: Use consistent ct id hash calculation
Input: psmouse - fix build error of multiple definition
iommu/amd: Move iommu_init_pci() to .init section
bnx2x: Fix VF's VLAN reconfiguration in reload.
net/mlx4_en: fix a memory leak bug
net/packet: fix race in tpacket_snd()
sctp: fix the transport error_count check
xen/netback: Reset nr_frags before freeing skb
net/mlx5e: Only support tx/rx pause setting for port owner
net/mlx5e: Use flow keys dissector to parse packets for ARFS
team: Add vlan tx offload to hw_enc_features
bonding: Add vlan tx offload to hw_enc_features
mmc: sdhci-of-arasan: Do now show error message in case of deffered probe
xfrm: policy: remove pcpu policy cache
mm/hmm: fix bad subpage pointer in try_to_unmap_one
mm: mempolicy: make the behavior consistent when MPOL_MF_MOVE* and 
MPOL_MF_STRICT were specified
mm: mempolicy: handle vma with unmovable pages mapped correctly in mbind
riscv: Make __fstate_clean() work correctly.
Revert "kmemleak: allow to coexist with fault injection"
sctp: fix memleak in sctp_send_reset_streams
UBUNTU: upstream stable to v4.14.140, v4.19.68

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux 

[Kernel-packages] [Bug 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1841158 (bionic/linux-hwe-edge)
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 13:36 UTC
+ phase: Testing
+ phase-changed: Tuesday, 27. August 2019 18:16 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

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

Title:
  eoan/linux: 5.2.0-15.16 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1841158 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 27. August 2019 18:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot

2019-08-27 Thread Alistair Buxton
Seems like you may be right. I could not reproduce it with
1bcf165ac6556d after about 10 attempts. This isn't conclusive
unfortunately. I will continue with a regular bisect.

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

Title:
  r8169 ethernet sometimes doesn't work after cold boot/boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever the computer is rebooted there is a roughly 50% chance that
  the r8169 ethernet cannot negotiate a link. There is no relevant
  information in dmesg except for the "link down" message. The work
  around is to just keep rebooting the computer until it eventually
  works; sometimes this may take up to 7 reboots.

  The first set of attached log files were generated while the ethernet
  was working.

  The second set are generated on the 5.0 HWE kernel when the ethernet
  was NOT working.

  Note that this is a regression. Ubuntu 16.04 ran on this computer for
  three years without the ethernet doing this even once.

  Unloading and loading the r8169 module will eventually make it work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-58-generic 4.15.0-58.64
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Thu Aug 22 10:05:17 2019
  HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
  InstallationDate: Installed on 2013-12-22 (2068 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-58-generic N/A
   linux-backports-modules-4.15.0-58-generic  N/A
   linux-firmware 1.173.9
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago)
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  al14985 F pulseaudio
   /dev/snd/controlC0:  al14985 F pulseaudio
   /dev/snd/controlC1:  al14985 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
  InstallationDate: Installed on 2013-12-22 (2068 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.173.9
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  bionic
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago)
  UserGroups: adm lpadmin sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 

[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0.0 kernel

2019-08-27 Thread Connor Kuehl
I can't reproduce this in a local VM on the disco/master-next branch
(tip of my branch is currently at: ebf9271500ba "UBUNTU: upstream stable
to v4.19.55, v5.1.14")

Here's what I'm doing:

sudo make -C tools/testing/selftests TARGETS=net run_tests

Here's the relevant test:

selftests: net: ip_defrag.sh

ipv4 defrag
PASS
seed = 1566927625
ipv4 defrag with overlaps
PASS
seed = 1566927626
ipv6 defrag
PASS
seed = 1566927656
ipv6 defrag with overlaps
PASS
seed = 1566927656
all tests done
ok 1..17 selftests: net: ip_defrag.sh [PASS]

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

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0.0
  kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  In Progress

Bug description:
  Test failed becuase:
 ./ip_defrag: sendto overlap: 1400: Operation not permitted

  
   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+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 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle

2019-08-27 Thread Bryan Quigley
My reproducer for Disco+ is a different bug.  I get input/output errors
very quickly once specifying nfs vers=4.0.  If you don't specify it, it
works fine.

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

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

Title:
  NFS v4.0: Stale data after file is renamed while another process has
  an open file handle

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Xenial:
  Confirmed
Status in linux-hwe source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-hwe source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Won't Fix

Bug description:
  NOTE: This bug has been fixed in the upstream mainline kernel via
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
  and merged in the latest NFS client patches in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

  The full patchset is here: https://marc.info/?l=linux-
  nfs=153816500525563=2

  I'm repeating the report I sent to the NFS maintainers on the mailing
  list:

  On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
  stale data is shown if a file remains open on one machine, and the
  file is overwritten via a rename() on another. Here's my test:

  1. On node A, create two different files on a shared NFS mount:
  "test1.txt" and "test2.txt".
  2. On node B, continuously show the contents of the first file: "while
  true; do cat test1.txt; done"
  3. On node B, run a process that keeps "test1.txt" open. For example,
  with Python, run:
   f = open('/nfs-mount/test1.txt', 'r')
  4. Rename test2.txt via "mv -f test2.txt test1.txt"

  On node B, I see the contents of the original test1.txt indefinitely,
  even after I disabled attribute caching and the lookup cache. I can
  make the while loop in step 2 show the new content if I perform one of
  these actions:

  1. Run "ls /nfs-mount"
  2. Close the open file in step 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+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 1687130] Re: NFS client input/output-error on kernel >=4.9

2019-08-27 Thread Bryan Quigley
Thanks for reporting this bug and helping to make Ubuntu better.

Was an upstream bug ever filed?  Was a clear reproducer ever identified?

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

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

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

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

Title:
  NFS client input/output-error on kernel >=4.9

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Incomplete

Bug description:
  I'm experiencing input/output errors on mounting NFS-shares, starting
  from kernel 4.9 and above.

  No errors logged to syslog, but the system reports IO-errors when
  reading from the mount after only a few seconds. Doesn't matter which
  program that are accessing the disk.

  My problems started after upgrading to ubuntu 17.04, but I have
  narrowed it down to being present from ubuntu kernel 4.9 and above by
  installing kernels from the ubuntu kernel ppa - i.e. when downgrading
  to latest 4.8-kernel from the PPA, NFS starts working as expected even
  on ubuntu 17.04. So it's definetely kernel related.

  Probably not a hardware error either as the bug is present when NFS is
  mounted over both eth0 and wlan0.

  Only special thing in my setup is that NFS is mounted over an ssh-
  tunnel.

  The NFS server runs an completely up to date ubuntu 16.04 LTS install.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-11 (991 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687130/+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 1730331] Re: ath10k_pci: firmware crashed!

2019-08-27 Thread TomaszChmielewski
This problem happens for me, with newest firmware, newest kernel, as of
today - but turns out only in the following situation:

- wireless router supports both 2.4 and 5 GHz
- same SSID name is used for both ranges


I.e. after disabling 5 GHz support on the router, the wifi card no longer 
crashes. Hope it helps anyone who wants a stable connection.

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

Title:
  ath10k_pci: firmware crashed!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware package in Fedora:
  Unknown

Bug description:
  ...
  Nov  4 18:35:50 akane kernel: [   10.216896] ath10k_pci :04:00.0: qca988x 
hw2.0 target 0x4100016c chip_id 0x043222ff sub :
  Nov  4 18:35:50 akane kernel: [   10.216908] ath10k_pci :04:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
  Nov  4 18:35:50 akane kernel: [   10.217641] ath10k_pci :04:00.0: 
firmware ver 10.2.4.70.63-2 api 5 features 
no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
  Nov  4 18:35:50 akane kernel: [   10.228600] kvm: Nested Virtualization 
enabled
  Nov  4 18:35:50 akane kernel: [   10.228611] kvm: Nested Paging enabled
  Nov  4 18:35:50 akane kernel: [   10.258913] ath10k_pci :04:00.0: 
board_file api 1 bmi_id N/A crc32 bebc7c08
  Nov  4 18:35:50 akane kernel: [   10.263535] MCE: In-kernel MCE decoding 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271401] EDAC amd64: Node 0: DRAM ECC 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271416] EDAC amd64: F16h_M30h detected 
(node 0).
  Nov  4 18:35:50 akane kernel: [   10.271491] EDAC MC: DCT0 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271494] EDAC amd64: MC: 0:  4096MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271523] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271526] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271528] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271530] EDAC MC: DCT1 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271532] EDAC amd64: MC: 0: 0MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271534] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271537] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271539] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271541] EDAC amd64: using x4 syndromes.
  Nov  4 18:35:50 akane kernel: [   10.271542] EDAC amd64: MCT channel count: 1
  Nov  4 18:35:50 akane kernel: [   10.271829] EDAC MC0: Giving out device to 
module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT)
  Nov  4 18:35:50 akane kernel: [   10.271892] EDAC PCI0: Giving out device to 
module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED)
  Nov  4 18:35:50 akane kernel: [   10.271894] AMD64 EDAC driver v3.5.0
  Nov  4 18:35:50 akane kernel: [   10.532131] EXT4-fs (sdc1): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
  Nov  4 18:35:50 akane kernel: [   10.575859] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
  Nov  4 18:35:50 akane kernel: [   11.397803] ath10k_pci :04:00.0: 
firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa)
  Nov  4 18:35:50 akane kernel: [   11.407389] ath10k_pci :04:00.0: qca988x 
hw2.0 target 0x4100016c chip_id 0x043222ff sub :
  Nov  4 18:35:50 akane kernel: [   11.407395] ath10k_pci :04:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
  Nov  4 18:35:50 akane kernel: [   11.408085] ath10k_pci :04:00.0: 
firmware ver 10.2.4.70.63-2 api 5 features 
no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
  Nov  4 18:35:50 akane kernel: [   11.408148] ath10k_pci :04:00.0: 
board_file api 1 bmi_id N/A crc32 bebc7c08
  Nov  4 18:35:50 akane kernel: [   11.408156] ath10k_pci :04:00.0: htt-ver 
0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
  Nov  4 18:35:50 akane kernel: [   11.410197] ath10k_pci :04:00.0: 
firmware register dump:
  Nov  4 18:35:50 akane kernel: [   11.416213] ath10k_pci :04:00.0: [00]: 
0x4100016C 0x15B3 0x009BFF84 0x00955B31
  Nov  4 18:35:50 akane kernel: [   11.424559] ath10k_pci :04:00.0: [04]: 
0x009BFF84 0x00060130 0x0013 0x
  Nov  4 18:35:50 akane kernel: [   11.432767] ath10k_pci :04:00.0: [08]: 
0x009C8EA4 0x7170 0x0001 0x00435300
  Nov  4 18:35:50 akane kernel: [   11.441059] ath10k_pci :04:00.0: [12]: 
0x0009 0x 0x00958360 0x0095836B
  Nov  4 18:35:50 akane kernel: [   11.449397] ath10k_pci :04:00.0: [16]: 
0x00958080 0x0094078E 0x 0x
  Nov  4 18:35:50 akane kernel: [   11.457686] ath10k_pci :04:00.0: [20]: 
0x409BFF84 0x0040AB44 

[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle

2019-08-27 Thread Bryan Quigley
** Also affects: linux-hwe (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: linux-hwe (Ubuntu Disco)
   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/1802585

Title:
  NFS v4.0: Stale data after file is renamed while another process has
  an open file handle

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Xenial:
  Confirmed
Status in linux-hwe source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-hwe source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in linux-hwe source package in Disco:
  Won't Fix

Bug description:
  NOTE: This bug has been fixed in the upstream mainline kernel via
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
  and merged in the latest NFS client patches in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

  The full patchset is here: https://marc.info/?l=linux-
  nfs=153816500525563=2

  I'm repeating the report I sent to the NFS maintainers on the mailing
  list:

  On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
  stale data is shown if a file remains open on one machine, and the
  file is overwritten via a rename() on another. Here's my test:

  1. On node A, create two different files on a shared NFS mount:
  "test1.txt" and "test2.txt".
  2. On node B, continuously show the contents of the first file: "while
  true; do cat test1.txt; done"
  3. On node B, run a process that keeps "test1.txt" open. For example,
  with Python, run:
   f = open('/nfs-mount/test1.txt', 'r')
  4. Rename test2.txt via "mv -f test2.txt test1.txt"

  On node B, I see the contents of the original test1.txt indefinitely,
  even after I disabled attribute caching and the lookup cache. I can
  make the while loop in step 2 show the new content if I perform one of
  these actions:

  1. Run "ls /nfs-mount"
  2. Close the open file in step 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+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 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle

2019-08-27 Thread Bryan Quigley
I was also able to reproduce this on Eoan by specifying vers=4.0 - where
I thought it should be fixed.

I was able to confirm that the -proposed 4.15 kernel (I tested xenial
HWE version) does have the fix and it
works:https://lists.ubuntu.com/archives/xenial-
changes/2019-August/025318.html

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

Title:
  NFS v4.0: Stale data after file is renamed while another process has
  an open file handle

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Confirmed

Bug description:
  NOTE: This bug has been fixed in the upstream mainline kernel via
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
  and merged in the latest NFS client patches in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

  The full patchset is here: https://marc.info/?l=linux-
  nfs=153816500525563=2

  I'm repeating the report I sent to the NFS maintainers on the mailing
  list:

  On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
  stale data is shown if a file remains open on one machine, and the
  file is overwritten via a rename() on another. Here's my test:

  1. On node A, create two different files on a shared NFS mount:
  "test1.txt" and "test2.txt".
  2. On node B, continuously show the contents of the first file: "while
  true; do cat test1.txt; done"
  3. On node B, run a process that keeps "test1.txt" open. For example,
  with Python, run:
   f = open('/nfs-mount/test1.txt', 'r')
  4. Rename test2.txt via "mv -f test2.txt test1.txt"

  On node B, I see the contents of the original test1.txt indefinitely,
  even after I disabled attribute caching and the lookup cache. I can
  make the while loop in step 2 show the new content if I perform one of
  these actions:

  1. Run "ls /nfs-mount"
  2. Close the open file in step 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+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 1752772] Re: r8169 ethernet card don't work after returning from suspension

2019-08-27 Thread John Holcomb
Same here with kernel 5.0.0-25-generic, however the script from post
#120 seems to work around this.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/120

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-kernel-headers package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  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: 

[Kernel-packages] [Bug 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1841158 (bionic/linux-hwe-edge)
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:36 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

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

Title:
  eoan/linux: 5.2.0-15.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1841158 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:36 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1838477] Re: [regression] r8169 network device unable to detect link on x86 arch

2019-08-27 Thread Kai-Heng Feng
** Description changed:

+ === SRU Justification ===
+ [Impact]
+ r8169 network device unable to detect link after boot.
+ 
+ [Fix]
+ Don't use MSI for older r8169 chips.
+ 
+ [Test]
+ User confirmed the issue is fixed with the patch applied.
+ 
+ [Regression Potential]
+ Low. This reverts affected r8169 device to use INTx, which is more
+ reliable on older hardware.
+ 
+ === Original Bug Report ===
  Since changes were introduced with 4.15.0-24 (LP #1752772), the r8169 driver 
became unusable on x86 machines (16.04 and 18.04 distributions). The device is 
always in link down state.
- --- 
+ ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-23-generic N/A
-  linux-backports-modules-4.15.0-23-generic  N/A
-  linux-firmware 1.173.9
+  linux-restricted-modules-4.15.0-23-generic N/A
+  linux-backports-modules-4.15.0-23-generic  N/A
+  linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic i686
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
- --- 
+ ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-23-generic N/A
-  linux-backports-modules-4.15.0-23-generic  N/A
-  linux-firmware 1.173.9
+  linux-restricted-modules-4.15.0-23-generic N/A
+  linux-backports-modules-4.15.0-23-generic  N/A
+  linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841540/+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 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot

2019-08-27 Thread Kai-Heng Feng
I think it's unlikely that these two caused the regression.

Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Network

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

Title:
  r8169 ethernet sometimes doesn't work after cold boot/boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever the computer is rebooted there is a roughly 50% chance that
  the r8169 ethernet cannot negotiate a link. There is no relevant
  information in dmesg except for the "link down" message. The work
  around is to just keep rebooting the computer until it eventually
  works; sometimes this may take up to 7 reboots.

  The first set of attached log files were generated while the ethernet
  was working.

  The second set are generated on the 5.0 HWE kernel when the ethernet
  was NOT working.

  Note that this is a regression. Ubuntu 16.04 ran on this computer for
  three years without the ethernet doing this even once.

  Unloading and loading the r8169 module will eventually make it work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-58-generic 4.15.0-58.64
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Thu Aug 22 10:05:17 2019
  HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
  InstallationDate: Installed on 2013-12-22 (2068 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-58-generic N/A
   linux-backports-modules-4.15.0-58-generic  N/A
   linux-firmware 1.173.9
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago)
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  al14985 F pulseaudio
   /dev/snd/controlC0:  al14985 F pulseaudio
   /dev/snd/controlC1:  al14985 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
  InstallationDate: Installed on 2013-12-22 (2068 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.173.9
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  bionic
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago)
  UserGroups: adm lpadmin sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  

[Kernel-packages] [Bug 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1841158 (bionic/linux-hwe-edge)
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:36 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

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

Title:
  eoan/linux: 5.2.0-15.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1841158 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:36 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait,signed:depwait
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait,signed:depwait
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841540/+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 1841132] Re: mpt3sas - storage controller resets under heavy disk io

2019-08-27 Thread Mauricio Faria de Oliveira
Hi Drew,

That's very good news!  So it looks like that patch resolves the
problem.

Could you please test the kernel in bionic-proposed [1] (4.15.0-60-generic)
which has that patch to confirm it's also working correctly?

Thanks!
Mauricio

[1] https://wiki.ubuntu.com/Testing/EnableProposed

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

Title:
  mpt3sas - storage controller resets under heavy disk io

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [summary]
  when a server running ubuntu 18.04 with an lsi sas controller experiences 
high disk io there is a chance the storage controller will reset
  this can take weeks or months, but once the controller resets it will keep 
resetting every few seconds or few minutes, dramatically degrading disk io
  the server must be rebooted to restore the controller to a normal state

  [hardware configuration]
  server: dell poweredge r7415, purchased 2019-02
  cpu/chipset: amd epyc naples
  storage controller: "dell hba330 mini" with chipset "lsi sas3008"
  drives: 4x samsung 860 pro 2TB ssd

  [software configuration]
  ubuntu 18.04 server
  mdadm raid6
  all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q)

  [what happened]
  server was operating as a vm host for months without issue
  one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag 
reset !!" and "Power-on or device reset occurred", along with unusably-slow 
disk io
  the server was removed from production and I looked for a way to reproduce 
the issue

  [how to reproduce the issue]
  there are probably many ways to product this issue, the hackish way I found 
to reliably reproduce it was:
  have the four ssds in a mdadm raid6 with ext4 filesystem
  create three 500GB files containing random data
  open three terminals. one calculates md5sum of file1 in a loop, another does 
the same for file2, the third does a copy of file3 to file3-temp in a loop
  the number of files is arbitrary, the goal is just to generate a lot of disk 
io on files too large to be cached in memory
  then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause 
even more drive thrashing
  within 1-15min the controller will enter the broken state. the longest I ever 
saw it take was 30min. I reproduced this several times
  rebooting the server restores the controller to a normal state
  if the server is not rebooted and the controller is left in this broken state 
eventually drives will fall out of the array, and sometimes array/filesystem 
corruption will occur

  [why this is being reported here]
  It's unlikely I am exceeding limits of the hardware since this server chassis 
can hold 24 drives and I am only using 4. The controller specs indicate I 
should not hit pcie bandwidth limits until at least 16 drives.
  My first thought was that the lsi controller firmware was at fault since they 
have been historically buggy, however I reproduced this with the newest 
firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be 
dell-specific).
  I then tried the most recent motherboard bios "1.9.3", and downgraded to 
"1.9.2", no change.
  I then wanted to eliminate the possibility of a bad drive. swapped out all 4 
drives with different ones of the same model, no change.
  I then upgraded from the standard 18.04 kernel to the newer backported hwe 
kernel, which also came with a newer mpt3sas driver, no change.
  I then ran the same test on the same array but with rhel 8, to my surprise I 
could no longer reproduce the issue.
  -
  tl;dr version:
  ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller 
breaks in 1-10min
  ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage 
controller breaks in 1-15min, max 30min
  rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same 
array for 19h, no errors

  [caveats]
  Server os misconfiguration is possible, however this is a rather basic vm 
host running kvm and no 3rd-party packages.
  I can't conclusively prove this isn't a hardware fault since I don't have a 
second unused identical server to test on right now, however the fact that the 
problem can be easily reproduced under ubuntu but not under rhel seems 
noteworthy.
  There is another bug (LP: #1810781) similar to this, I didn't post there 
because it's already marked as fixed.
  There is also a debian bug (Debian #926202) that encountered this on kernel 
4.19.0, but I'm unable to tell if it's the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841132/+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 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841544/+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 1841288] Re: does not create compressed dump on 5.0 or later kernels

2019-08-27 Thread Thadeu Lima de Souza Cascardo
Some details about those debdiffs: they were prepared on top of a
version done by Connor Kuehl that could have landed in -proposed between
my uploading of the diff and the package upload/sponsorship.

That explains the extra changelog stanza and the versioning. It also
explains the change in the original patches: I didn't revert the changes
back, they were on Connor's version. I plan on keeping those as part of
a workflow that allows multiple people to work on the package, as that
seems to be happening more often these days, even though it hasn't
landed in -proposed. They are all nitpicks and have no impact on users.

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

Title:
  does not create compressed dump on 5.0 or later kernels

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Disco:
  In Progress

Bug description:
  [Impact]
  On ppc64el, makedumpfile won't create compressed dumps, causing them to be 
very large. This affects any kernel later than 4.19 actually.

  [Test case]
  Crash a system with kdump-tools installed and enabled, by using the following 
sequence. Verify the created dumps are compressed by using file. This is the 
same test as the autopkgtest for makedumpfile.

  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  [Regression potential]
  This is a small fix and should only impact ppc64el. Older kernels should 
still work, and should be tested.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+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 1841539] Re: xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:05 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Holding -- master bug not ready for proposed
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:05 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841539/+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 1841541] Re: trusty/linux-aws: 4.4.0-1052.56 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 12:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

Title:
  trusty/linux-aws: 4.4.0-1052.56 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 12:31 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841541/+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 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841544/+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 1830756] Re: tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

2019-08-27 Thread Stefan Bader
** Description changed:

+ [SRU Justification]
+ 
+ == Impact ==
+ 
+ 1bd4978a88ac2 ("tun: honor IFF_UP in tun_get_user()") which is part of
+ kernel v4.5 introduced an issue where userspace processes might not get
+ notified if a link comes up after initially being down. This was fixed
+ in the requested backport (from 4.17).
+ 
+ == Fix ==
+ 
+ Backport the requested patch to Bionic (4.15). Xenial (4.4) is not
+ affected and Disco and later already contain that fix.
+ 
+ == Risk of Regregression ==
+ 
+ The change only slightly modifies a very specific protocol function.
+ Risk should be low and limited to tuntap.
+ 
+ ---
+ 
  The upstream commit 2f3ab6221e4c ("tuntap: correctly set 
SOCKWQ_ASYNC_NOSPACE") is missing.
  Without this patch, userspace apps that use tuntap may be blocked.
  
- 
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c

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

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

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

Title:
  tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

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

Bug description:
  [SRU Justification]

  == Impact ==

  1bd4978a88ac2 ("tun: honor IFF_UP in tun_get_user()") which is part of
  kernel v4.5 introduced an issue where userspace processes might not
  get notified if a link comes up after initially being down. This was
  fixed in the requested backport (from 4.17).

  == Fix ==

  Backport the requested patch to Bionic (4.15). Xenial (4.4) is not
  affected and Disco and later already contain that fix.

  == Risk of Regregression ==

  The change only slightly modifies a very specific protocol function.
  Risk should be low and limited to tuntap.

  ---

  The upstream commit 2f3ab6221e4c ("tuntap: correctly set 
SOCKWQ_ASYNC_NOSPACE") is missing.
  Without this patch, userspace apps that use tuntap may be blocked.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830756/+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 1838477] Re: [regression] r8169 network device unable to detect link on x86 arch

2019-08-27 Thread Roman Valov
Works well!

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

Title:
  [regression] r8169 network device unable to detect link on x86 arch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since changes were introduced with 4.15.0-24 (LP #1752772), the r8169 driver 
became unusable on x86 machines (16.04 and 18.04 distributions). The device is 
always in link down state.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic i686
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 

[Kernel-packages] [Bug 1840835] Re: High power consumption using 5.0.0-25-generic

2019-08-27 Thread Kai-Heng Feng
A test kernel can be found here:
https://people.canonical.com/~khfeng/lp1840835/

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

Title:
  High power consumption using 5.0.0-25-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to 5.0.0-25-generic kernel, battery life is
  considerably less and power consumption is about 10 watts more idle,
  using integrated graphics. This is a hybrid GPU laptop Intel HD
  630/GP107M, and a possible cause is not powering off the dedicated GPU
  completely while using the integrated.

  nvidia-driver-430
  GP107M [GeForce GTX 1050 Mobile]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1838575] Re: passthrough devices cause >17min boot delay

2019-08-27 Thread Christian Ehrhardt 
I could next build a test kernel with some debug around the vfio iommu dma map 
to check how time below that call is spent.
I'm sure that data already is hidden in some of my trace data, but to 
eventually change/experiment I need to build one anyway.

I expect anyway to summarize and go into a discussion at some point, as
even if one would split the map calls iommus are full of quirks and
constraints that might bit us later.

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

Title:
  passthrough devices cause >17min boot delay

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Adding passthrough devices to a guest introduces a boot delay of > 17
  minutes. During this time libvirt reports the guest to be "paused".
  The delay does not seem to scale with the # of hostdevs - that is, 1
  hostdev causes about a 17min delay, while 16 only bumps that up to
  ~18min. Removing all hostdevs avoids the delay.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838575/+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 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

2019-08-27 Thread Andrew Cloke
Excellent news! Thanks Eric :-)

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+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 1840800] Re: disco/linux-aws: 5.0.0-1014.16 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840820 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Testing
- phase-changed: Monday, 26. August 2019 20:07 UTC
+ phase: Signoff
+ phase-changed: Tuesday, 27. August 2019 14:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-edge: bug 1840820
  variant: debs

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

Title:
  disco/linux-aws: 5.0.0-1014.16 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840820 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Signoff
  phase-changed: Tuesday, 27. August 2019 14:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-edge: bug 1840820
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840800/+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 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

2019-08-27 Thread Eric Desrochers
Hi Andrew Cloke,

Yes, I'm currently sponsoring D/B for cascardo/gpicolli.

Disco is already uploaded waiting for SRU team approval:
https://launchpad.net/ubuntu/disco/+queue?queue_state=1_text=makedumpfile

Bionic debdiff needs some rework before I do the final upload.

- Eric

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+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 1840261] Re: eoan/linux: 5.2.0-13.14 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  eoan/linux: 5.2.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840259 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 27. August 2019 13:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-hwe-edge: bug 1840259
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840261/+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 1840800] Re: disco/linux-aws: 5.0.0-1014.16 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840820 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Monday, 26. August 2019 20:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-edge: bug 1840820
  variant: debs

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

Title:
  disco/linux-aws: 5.0.0-1014.16 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840820 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Monday, 26. August 2019 20:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-edge: bug 1840820
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840800/+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 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840803
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Friday, 23. August 2019 18:31 UTC
+ phase: Signoff
+ phase-changed: Tuesday, 27. August 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1840821
bionic/linux-azure/azure-kernel: bug 1840801
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-
  edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840803
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Signoff
  phase-changed: Tuesday, 27. August 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1840821
bionic/linux-azure/azure-kernel: bug 1840801
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1841084] Re: bionic/linux-aws: 4.15.0-1047.49 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1841086
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Testing
- phase-changed: Friday, 23. August 2019 23:25 UTC
+ phase: Signoff
+ phase-changed: Tuesday, 27. August 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws/aws-kernel: bug 1841081
xenial/linux-aws-hwe: bug 1841083
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1047.49 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1841086
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Signoff
  phase-changed: Tuesday, 27. August 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws/aws-kernel: bug 1841081
xenial/linux-aws-hwe: bug 1841083
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1838575] Re: passthrough devices cause >17min boot delay

2019-08-27 Thread Christian Ehrhardt 
Reference:
this is the call from qemu that I think we see above (on x86) is at [1].
If this time the assumption is correct the kernel place would be at 
vfio_iommu_type1_ioctl.

For debugging:
$ gdb qemu/x86_64-softmmu/qemu-system-x86_64
(gdb) catch syscall 16
(gdb) run -m 131072 -smp 1 -no-user-config -device 
vfio-pci,host=21:00.1,id=hostdev0,bus=pci.0,addr=0x7
(gdb) continue 22
# Now we are "in front" of the bad call.

https://git.qemu.org/?p=qemu.git;a=blob;f=hw/vfio/common.c;h=3e03c495d868f154b26a33c0c2d870273a0b4198;hb=HEAD#l480

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

Title:
  passthrough devices cause >17min boot delay

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Adding passthrough devices to a guest introduces a boot delay of > 17
  minutes. During this time libvirt reports the guest to be "paused".
  The delay does not seem to scale with the # of hostdevs - that is, 1
  hostdev causes about a 17min delay, while 16 only bumps that up to
  ~18min. Removing all hostdevs avoids the delay.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838575/+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 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

2019-08-27 Thread Andrew Cloke
Next step is to consider backport feasibility for disco and bionic.

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+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 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)

2019-08-27 Thread Andrew Cloke
Awaiting confirmation from IBM (Anju), as per Michael's last comment.

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

Title:
  [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is
  seen while running perf fuzzer (perf:)

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-02-02 
01:21:36 ==
  Problem Description :
  =

  Warn on message is seen while running perf fuzzer tests.

  Machine details :
  ==
  Hardware : Witherspoon (wsp12) + DD2.1
  OS : Ubuntu 1804
  uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 )

  
  Steps to reproduce :
  
  Build Kernel :
  
  To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in 
the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

  
  Call trace :
  ===
  [  329.228031] [ cut here ]
  [  329.228039] WARNING: CPU: 43 PID: 9088 at 
/home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 
perf_pmu_sched_task+0x170/0x180
  [  329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart 
powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler 
ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 
crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci 
nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc
  [  329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 
4.13.0-32-generic #35~lp1746225
  [  329.228070] task: c03f776ac900 task.stack: c03f77728000
  [  329.228071] NIP: c0299b70 LR: c02a4534 CTR: 
c029bb80
  [  329.228073] REGS: c03f7772b760 TRAP: 0700   Not tainted  
(4.13.0-32-generic)
  [  329.228073] MSR: 9282b033 
  [  329.228079]   CR: 24008822  XER: 
  [  329.228080] CFAR: c0299a70 SOFTE: 0 
 GPR00: c02a4534 c03f7772b9e0 c1606200 
c03fef858908 
 GPR04: c03f776ac900 0001  
003fee73 
 GPR08:   c11220d8 
0002 
 GPR12: c029bb80 c7a3d900  
 
 GPR16:    
 
 GPR20:   c03f776ad090 
c0c71354 
 GPR24: c03fef716780 003fee73 c03fe69d4200 
c03f776ad330 
 GPR28: c11220d8 0001 c14c6108 
c03fef858900 
  [  329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180
  [  329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230
  [  329.228101] Call Trace:
  [  329.228102] [c03f7772b9e0] [c02a0678] 
perf_iterate_sb+0x158/0x2a0 (unreliable)
  [  329.228105] [c03f7772ba30] [c02a4534] 
__perf_event_task_sched_in+0xc4/0x230
  [  329.228107] [c03f7772bab0] [c01396dc] 
finish_task_switch+0x21c/0x310
  [  329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80
  [  329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0
  [  329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0
  [  329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0
  [  329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0
  [  329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c
  [  329.228121] Instruction dump:
  [  329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 
38210050 
  [  329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 
6000 6042 
  [  329.228131] ---[ end trace 8c46856d314c1811 ]---
  [  375.755943] hrtimer: interrupt took 31601 ns

  == Comment: #4 - SEETEENA THOUFEEK  - 2018-02-05
  06:34:09 ==

  
  == Comment: #5 - SEETEENA THOUFEEK  - 2018-02-05 
06:36:12 ==
  We have similar issue reported on different distro where Anju Provided the 
patch. Patch attached above. 
  . 
  Will check with her if 

[Kernel-packages] [Bug 1840811] Re: disco/linux-oracle: 5.0.0-1001.1 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840826 (bionic/linux-oracle-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1001.1 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840835] Re: High power consumption using 5.0.0-25-generic

2019-08-27 Thread Kai-Heng Feng
My proposed patch to fix the issue:
https://lkml.org/lkml/2019/8/27/956

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

Title:
  High power consumption using 5.0.0-25-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to 5.0.0-25-generic kernel, battery life is
  considerably less and power consumption is about 10 watts more idle,
  using integrated graphics. This is a hybrid GPU laptop Intel HD
  630/GP107M, and a possible cause is not powering off the dedicated GPU
  completely while using the integrated.

  nvidia-driver-430
  GP107M [GeForce GTX 1050 Mobile]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1841158 (bionic/linux-hwe-edge)
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 13:29 UTC
+ phase: Promote to Proposed
+ phase-changed: Tuesday, 27. August 2019 13:36 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

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

Title:
  eoan/linux: 5.2.0-15.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1841158 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:36 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 08:36 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841544/+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 1840261] Re: eoan/linux: 5.2.0-13.14 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-release
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840259 (bionic/linux-hwe-edge)
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Promote to Release
- phase-changed: Thursday, 22. August 2019 22:34 UTC
+ phase: Complete
+ phase-changed: Tuesday, 27. August 2019 13:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-release: Pending -- ready to copy
  trackers:
bionic/linux-hwe-edge: bug 1840259
  variant: debs

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

Title:
  eoan/linux: 5.2.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840259 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 27. August 2019 13:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-hwe-edge: bug 1840259
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840261/+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 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-eoan

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1841158 (bionic/linux-hwe-edge)
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Holding before Promote to Proposed
- phase-changed: Friday, 23. August 2019 15:43 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 27. August 2019 13:29 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

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

Title:
  eoan/linux: 5.2.0-15.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1841158 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:36 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1658219] Re: flock not mediated by 'k'

2019-08-27 Thread Tyler Hicks
@mvo I don't understand why we'd add the "assumes" to the kernel's
snapcraft.yaml now since we're reverting the problematic AppArmor
commit. A kernel with the AppArmor commit will never be released to
stable (or -updates/-security) so I don't think that the "assumes"
workaround is needed any longer.

We decided to revert the commit rather than go down the "assumes" route
because the breakage would affect more than just snap confinement. It
also affects non-snap processes that are confined by AppArmor.

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+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 1841534] Re: xenial/linux-kvm: 4.4.0-1056.63 -proposed tracker

2019-08-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Packaging
- phase-changed: Tuesday, 27. August 2019 12:15 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 27. August 2019 13:15 UTC
  reason:
-   prepare-package: Stalled -- package tag not yet published
-   promote-to-proposed: Pending -- builds not complete in ppa main:queued
+   promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

Title:
  xenial/linux-kvm: 4.4.0-1056.63 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:15 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841534/+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 1784665] Re: bcache: bch_allocator_thread(): hung task timeout

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1838539] Re: Eoan update: v5.2.5 upstream stable release

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures

2019-08-27 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1784665 ***
https://bugs.launchpad.net/bugs/1784665

This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: 

[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1839154] Re: please backport upstream patch to kernel 5.2

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1838575] Re: passthrough devices cause >17min boot delay

2019-08-27 Thread Christian Ehrhardt 
Many ioctls (as expected) but they are all fast and match what we knew from 
strace.
Thread 1 "qemu-system-x86" hit Catchpoint 1 (call to syscall ioctl), 
0x772fae0b in ioctl () at ../sysdeps/unix/syscall-template.S:78
78  in ../sysdeps/unix/syscall-template.S
(gdb) bt
#0  0x772fae0b in ioctl () at ../sysdeps/unix/syscall-template.S:78
#1  0x55914217 in vfio_init_container (container=0x57608430, 
group_fd=11, errp=0x7fffdda8) at /home/ubuntu/qemu/hw/vfio/common.c:1172
#2  0x5591445e in vfio_connect_container (group=0x576083b0, 
as=0x565ca5a0 , errp=0x7fffdda8) at 
/home/ubuntu/qemu/hw/vfio/common.c:1257
#3  0x55914f35 in vfio_get_group (groupid=45, as=0x565ca5a0 
, errp=0x7fffdda8) at 
/home/ubuntu/qemu/hw/vfio/common.c:1482
#4  0x55920575 in vfio_realize (pdev=0x57600570, 
errp=0x7fffdda8) at /home/ubuntu/qemu/hw/vfio/pci.c:2759
#5  0x55b853d7 in pci_qdev_realize (qdev=0x57600570, 
errp=0x7fffde20) at hw/pci/pci.c:2096
#6  0x55aac178 in device_set_realized (obj=0x57600570, value=true, 
errp=0x7fffdff0) at hw/core/qdev.c:835
#7  0x55cb857a in property_set_bool (obj=0x57600570, 
v=0x57602f00, name=0x55f3b5d2 "realized", opaque=0x574e79e0, 
errp=0x7fffdff0) at qom/object.c:2080
#8  0x55cb6731 in object_property_set (obj=0x57600570, 
v=0x57602f00, name=0x55f3b5d2 "realized", errp=0x7fffdff0) at 
qom/object.c:1272
#9  0x55cb9965 in object_property_set_qobject (obj=0x57600570, 
value=0x57602dc0, name=0x55f3b5d2 "realized", errp=0x7fffdff0) at 
qom/qom-qobject.c:26
#10 0x55cb6a2a in object_property_set_bool (obj=0x57600570, 
value=true, name=0x55f3b5d2 "realized", errp=0x7fffdff0) at 
qom/object.c:1338
#11 0x55a12cb1 in qdev_device_add (opts=0x566a0770, 
errp=0x5661e790 ) at qdev-monitor.c:635
#12 0x55a1b11f in device_init_func (opaque=0x0, opts=0x566a0770, 
errp=0x5661e790 ) at vl.c:2206
#13 0x55e1c7fd in qemu_opts_foreach (list=0x56468ee0 
, func=0x55a1b0f4 , opaque=0x0, 
errp=0x5661e790 )
at util/qemu-option.c:1170
#14 0x55a2009d in main (argc=14, argv=0x7fffe3d8, 
envp=0x7fffe450) at vl.c:4387


The slow one is again the full iommu mapping of the guest memory:
(gdb) bt
#0  0x772fae0b in ioctl () at ../sysdeps/unix/syscall-template.S:78
#1  0x55911a9e in vfio_dma_map (container=0x57608430, 
iova=4294967296, size=134217728000, vaddr=0x7fe01fe0, readonly=false) at 
/home/ubuntu/qemu/hw/vfio/common.c:349
#2  0x5591299b in vfio_listener_region_add (listener=0x57608440, 
section=0x7fffcad0) at /home/ubuntu/qemu/hw/vfio/common.c:664
#3  0x5587dfb0 in listener_add_address_space (listener=0x57608440, 
as=0x565ca5a0 ) at /home/ubuntu/qemu/memory.c:2714
#4  0x5587e3dd in memory_listener_register (listener=0x57608440, 
as=0x565ca5a0 ) at /home/ubuntu/qemu/memory.c:2781
#5  0x5591499b in vfio_connect_container (group=0x576083b0, 
as=0x565ca5a0 , errp=0x7fffdda8) at 
/home/ubuntu/qemu/hw/vfio/common.c:1365
#6  0x55914f35 in vfio_get_group (groupid=45, as=0x565ca5a0 
, errp=0x7fffdda8) at 
/home/ubuntu/qemu/hw/vfio/common.c:1482
#7  0x55920575 in vfio_realize (pdev=0x57600570, 
errp=0x7fffdda8) at /home/ubuntu/qemu/hw/vfio/pci.c:2759
#8  0x55b853d7 in pci_qdev_realize (qdev=0x57600570, 
errp=0x7fffde20) at hw/pci/pci.c:2096
#9  0x55aac178 in device_set_realized (obj=0x57600570, value=true, 
errp=0x7fffdff0) at hw/core/qdev.c:835
#10 0x55cb857a in property_set_bool (obj=0x57600570, 
v=0x57602f00, name=0x55f3b5d2 "realized", opaque=0x574e79e0, 
errp=0x7fffdff0) at qom/object.c:2080
#11 0x55cb6731 in object_property_set (obj=0x57600570, 
v=0x57602f00, name=0x55f3b5d2 "realized", errp=0x7fffdff0) at 
qom/object.c:1272
#12 0x55cb9965 in object_property_set_qobject (obj=0x57600570, 
value=0x57602dc0, name=0x55f3b5d2 "realized", errp=0x7fffdff0) at 
qom/qom-qobject.c:26
#13 0x55cb6a2a in object_property_set_bool (obj=0x57600570, 
value=true, name=0x55f3b5d2 "realized", errp=0x7fffdff0) at 
qom/object.c:1338
#14 0x55a12cb1 in qdev_device_add (opts=0x566a0770, 
errp=0x5661e790 ) at qdev-monitor.c:635
#15 0x55a1b11f in device_init_func (opaque=0x0, opts=0x566a0770, 
errp=0x5661e790 ) at vl.c:2206
#16 0x55e1c7fd in qemu_opts_foreach (list=0x56468ee0 
, func=0x55a1b0f4 , opaque=0x0, 
errp=0x5661e790 )
at util/qemu-option.c:1170
#17 0x55a2009d in main (argc=14, argv=0x7fffe3d8, 
envp=0x7fffe450) at vl.c:4387
(gdb) c
Continuing.


In particular:
vfio_dma_map (container=0x57608430, iova=4294967296, size=134217728000, 

[Kernel-packages] [Bug 1838677] Re: shiftfs: allow overlayfs

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1839588] Re: Eoan update: v5.2.7 upstream stable release

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1839395] Re: Regressions in CMA allocation rework

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1839587] Re: Eoan update: v5.2.6 upstream stable release

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1840178] Re: Eoan update: v5.2.8 upstream stable release

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1840028] Re: NULL pointer dereference when Inserting the VIMC module

2019-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: imx: soc-imx8: Correct return value of error handle
- dmaengine: tegra-apb: Error out if 

[Kernel-packages] [Bug 1840184] Re: eoan/linux: 5.2.0-12.13 -proposed tracker

2019-08-27 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1840261 ***
https://bugs.launchpad.net/bugs/1840261

This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: 

[Kernel-packages] [Bug 1839646] Re: eoan/linux: 5.2.0-11.12 -proposed tracker

2019-08-27 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1840261 ***
https://bugs.launchpad.net/bugs/1840261

This bug was fixed in the package linux - 5.2.0-13.14

---
linux (5.2.0-13.14) eoan; urgency=medium

  * eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)

  * NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare

  * Miscellaneous upstream changes
- selftests/bpf: remove bpf_util.h from BPF C progs

linux (5.2.0-12.13) eoan; urgency=medium

  * eoan/linux: 5.2.0-12.13 -proposed tracker (LP: #1840184)

  * Eoan update: v5.2.8 upstream stable release (LP: #1840178)
- scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
- libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
- libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
- ALSA: usb-audio: Sanity checks for each pipe and EP types
- ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
- HID: wacom: fix bit shift for Cintiq Companion 2
- HID: Add quirk for HP X1200 PIXART OEM mouse
- atm: iphase: Fix Spectre v1 vulnerability
- bnx2x: Disable multi-cos feature.
- drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
- ife: error out when nla attributes are empty
- ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
- ip6_tunnel: fix possible use-after-free on xmit
- ipip: validate header length in ipip_tunnel_xmit
- mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
- mvpp2: fix panic on module removal
- mvpp2: refactor MTU change code
- net: bridge: delete local fdb on device init failure
- net: bridge: mcast: don't delete permanent entries when fast leave is
  enabled
- net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
- net: fix ifindex collision during namespace removal
- net/mlx5e: always initialize frag->last_in_page
- net/mlx5: Use reversed order when unregister devices
- net: phy: fixed_phy: print gpio error only if gpio node is present
- net: phylink: don't start and stop SGMII PHYs in SFP modules twice
- net: phylink: Fix flow control for fixed-link
- net: phy: mscc: initialize stats array
- net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
- net: sched: Fix a possible null-pointer dereference in dequeue_func()
- net sched: update vlan action for batched events operations
- net: sched: use temporary variable for actions indexes
- net/smc: do not schedule tx_work in SMC_CLOSED state
- net: stmmac: Use netif_tx_napi_add() for TX polling function
- NFC: nfcmrvl: fix gpio-handling regression
- ocelot: Cancel delayed work before wq destruction
- tipc: compat: allow tipc commands without arguments
- tipc: fix unitilized skb list crash
- tun: mark small packets as owned by the tap sock
- net/mlx5: Fix modify_cq_in alignment
- net/mlx5e: Prevent encap flow counter update async to user query
- r8169: don't use MSI before RTL8168d
- bpf: fix XDP vlan selftests test_xdp_vlan.sh
- selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- selftests/bpf: reduce time to execute test_xdp_vlan.sh
- net: fix bpf_xdp_adjust_head regression for generic-XDP
- hv_sock: Fix hang when a connection is closed
- net: phy: fix race in genphy_update_link
- net/smc: avoid fallback in case of non-blocking connect
- rocker: fix memory leaks of fib_work on two error return paths
- mlxsw: spectrum_buffers: Further reduce pool size on Spectrum-2
- net/mlx5: Add missing RDMA_RX capabilities
- net/mlx5e: Fix matching of speed to PRM link modes
- compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
- drm/i915/vbt: Fix VBT parsing for the PSR section
- Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
- spi: bcm2835: Fix 3-wire mode if DMA is enabled
- Linux 5.2.8

  * Miscellaneous Ubuntu changes
- SAUCE: selftests/bpf: do not include Kbuild.include in makefile
- update dkms package versions

linux (5.2.0-11.12) eoan; urgency=medium

  * eoan/linux: 5.2.0-11.12 -proposed tracker (LP: #1839646)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Eoan update: v5.2.7 upstream stable release (LP: #1839588)
- Revert "UBUNTU: SAUCE: Revert "loop: Don't change loop device under
  exclusive opener""
- ARM: riscpc: fix DMA
- ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
- ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
- clk: meson: mpll: properly handle spread spectrum
- ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
- ftrace: Enable trampoline when rec count returns back to one
- arm64: dts: qcom: qcs404-evb: fix l3 min voltage
- soc: qcom: rpmpd: fixup rpmpd set performance state
- arm64: dts: marvell: mcbin: enlarge PCI memory window
- soc: 

  1   2   3   >