[Kernel-packages] [Bug 1831587] Re: brightness control not work with OLED panel

2019-10-08 Thread Nicolas
Same issue for me on an ThinkPad X1 extreme (gen 2),

EDID info:

# edid-decode /sys/class/drm/card0-eDP-1/edid   
 [09:29:37]
Extracted contents:
header:  00 ff ff ff ff ff ff 00
serial number:   4c 83 41 41 00 00 00 00 13 1d
version: 01 04
basic params:b5 22 13 78 02
chroma info: 94 91 ae 51 3e b7 24 0b 50 54
established: 00 00 00
standard:01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:f0 d4 00 40 f1 70 18 80 30 20 44 00 58 c2 10 00 00 1b
descriptor 2:f0 d4 00 40 f1 70 18 80 30 20 44 00 58 c2 10 00 00 1b
descriptor 3:00 00 00 0f 00 ff 09 3c ff 09 3c 2c 80 00 00 00 00 00
descriptor 4:00 00 00 fe 00 41 54 4e 41 35 36 57 52 30 38 2d 30 20
extensions:  01
checksum:15

Manufacturer: SDC Model 4141 Serial Number 0
Made week 19 of 2019
EDID version: 1.4
Digital display
10 bits per primary color channel
DisplayPort interface
Maximum image size: 34 cm x 19 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
Detailed mode: Clock 545.120 MHz, 344 mm x 194 mm
   3840 3888 3920 4160 hborder 0
   2160 2164 2168 2184 vborder 0
   +hsync -vsync 
Detailed mode: Clock 545.120 MHz, 344 mm x 194 mm
   3840 3888 3920 4160 hborder 0
   2160 2164 2168 2184 vborder 0
   +hsync -vsync 
Manufacturer-specified data, tag 15
ASCII string: ATNA56WR08-0
Has 1 extension blocks
Checksum: 0x15 (valid)

CEA extension block
Extension version: 3
11 bytes of CEA data
  Extended tag: Colorimetry data block
xvYCC601
xvYCC709
sYCC601
AdobeYCC601
AdobeRGB
BT2020cYCC
BT2020YCC
BT2020RGB
  Extended tag: HDR static metadata data block
Electro optical transfer functions:
  Traditional gamma - SDR luminance range
  Traditional gamma - HDR luminance range
  SMPTE ST2084
Supported static metadata descriptors:
  Static metadata type 1
Desired content max luminance: 115
Desired content max frame-average luminance: 109
Desired content min luminance: 7
0 native detailed modes
Checksum: 0xab (valid)

EDID block does NOT conform to EDID 1.3!
Missing name descriptor
Missing monitor ranges
Detailed block string not properly terminated

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

Title:
  brightness control not work with OLED panel

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  image: disco 19.04
  kernel: 5.0.0-15-generic
  also verified failed on linux-image-unsigned-5.2.0-050200rc2-generic

  also refer to :
   - 
https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness
   - https://bugs.freedesktop.org/show_bug.cgi?id=97883

  Linux can not control the brightness on the OLED panel in the traditional way 
[1].
  Although there's a workaround from the community [2] that to execute script 
while brightness hotkey event is triggered. But if we want to upstream it, it's 
still a problem to recognize the OLED panel so that the system knows when to go 
workaround.
   - EDID of my laptop which has OLED: https://paste.ubuntu.com/p/w7rVqJTYDy/
   - EDID of the same model without OLED: https://paste.ubuntu.com/p/P3ChhX9yBJ/

  there's a kernel patch related OLED for reference:
   - https://patchwork.kernel.org/patch/6133471/

  [1] https://wiki.ubuntu.com/Kernel/Debugging/Backlight
  [2] 
https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness

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

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


[Kernel-packages] [Bug 1971567] Re: TPM breaks resume from suspend

2022-05-28 Thread Nicolas
Have the same behaviour on my Lenovo Thinkpad T460s (20FAS0FD07) running 
5.15.0-33-generic:
1. laptop can't get out of suspend
2. boot is longer than with 21.10 due to the time out of TPM 

[0.027286] ACPI: Reserving TPM2 table memory at [mem 0xcfff8000-0xcfff8033]
[5.122778] tpm tpm0: Operation Timed out
[   11.946910] tpm tpm0: Operation Timed out
[   11.946942] tpm_crb: probe of MSFT0101:00 failed with error -62
[   12.023475] ima: No TPM chip found, activating TPM-bypass!

(^^ extract of "demsg | grep -i tpm")

Thanks,
Nicolas

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

Title:
  TPM breaks resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Lenovo Thinkpad X260 from 21.10 to 22.04, following
  error shows at boot:

  [4.830657] tpm tpm0: Operation Timed out
  [   11.654699] tpm tpm0: Operation Timed out
  [   11.654718] tpm_crb: probe of MSFT0101:00 failed with error -62

  Notable consequence is that the laptop will not resume from suspend
  any more, even with the power button pressed.

  After disabling TPM ("Security Chip" in Lenovo BIOS) completely,
  everything works normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 2147 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  4 13:15:17 2022
  InstallationDate: Installed on 2022-03-06 (59 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20F5S0V400
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (10 days ago)
  dmi.bios.date: 02/23/2022
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET76W (1.49 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F5S0V400
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET76W(1.49):bd02/23/2022:br1.49:efr1.16:svnLENOVO:pn20F5S0V400:pvrThinkPadX260:rvnLENOVO:rn20F5S0V400:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F5_BU_Think_FM_ThinkPadX260:
  dmi.product.family: ThinkPad X260
  dmi.product.name: 20F5S0V400
  dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

2020-05-06 Thread Nicolas
Same bug for me, kernel 5.3.0-51-generic, ubuntu 19.10. It only happens
when working on PyCharm (2 sec freeze, mouse moving, getting back what I
typed after the freeze)

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

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

Bug description:
  Hi,

  Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent
  (every couple of minutes) GPU hangs and reset manifesting as 2-3
  seconds freezes of the GUI (other than the mouse pointer).

  No particular triggers identified although have Chrome / Chromium
  running with Hardware Acceleration enabled does appear to increase the
  frequency.

  I have seen incidences of these hangs in jounralctl output using
  previous kernels in the 5.3.0-xx series but they were very infrequent
  (one or twice in a week of daily usage)

  System Info
  steve@steve-Inspiron-5580:~$ inxi -SCGxxxz
  System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 
compiler: gcc v: 7.5.0
     Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
Distro: Linux Mint 19.3 Tricia
     base: Ubuntu 18.04 bionic
  CPU:   Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT 
MCP arch: Kaby Lake rev: B
     L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 28800
     Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800
     8: 800
  Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:3ea0
     Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 
GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0
     direct render: Yes

  steve@steve-Inspiron-5580:~$ journalctl -b | grep i915
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
deactivate vga console
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_04.bin (v1.4)
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 
20190619 for :00:02.0 on minor 0
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary 
device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb 
frame buffer device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: 
ecode 9:0:0x, hang on rcs0
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 

[Kernel-packages] [Bug 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported

2016-05-21 Thread Nicolas
Thanks so much Brian Murray,
I had installed Ubuntu 16.04 from scratch on my Lenovo U31-70 but the wifi 
wouldn't work. Followed your instructions and now all is good :).

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

Title:
  Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041]
  is not supported

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed

Bug description:
  The firmware for this card isn't included with Ubuntu.  The firmware
  provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when
  used with this card.  This included firmware is likely for the QCA6174
  instead of this card, the QCA6164.

  Yes, you read that right: the files for the QCA6164 need to be a
  folder called QCA6174 in order for the card to work.  Running
  "modprobe ath10k_pci" shows that the ath10k_pci module looks for
  firmware in a folder called QCA6174, but not in any folder called
  QCA6164.

  It seems that before this issue can be resolved, the ath10k_pci module
  must be changed so that it recognizes firmware for both the QCA6164
  and QCA6174, in separate folders.

  ---

  HOW TO GET THIS CARD TO WORK:

  1) Use a kernel that supports this card

  According to WikiDevi, support for this card was added in kernel 4.3.
  If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip
  to the next step.  If you're running Ubuntu 15.10 or below, see
  https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
  newer kernel.  Alternatively, you can use backports.  This is a lot
  more work, but if you really need to keep using an older kernel for
  some reason, there are some guides to installing backports in the
  comments below.

  2) Get rid of the firmware folder for this card that's included with
  Ubuntu:

  sudo rm -r /lib/firmware/ath10k/QCA6174/

  3) Download the latest firmware:

  wget https://github.com/kvalo/ath10k-firmware/archive/master.zip

  4) Unzip the downloaded file.  Inside the ath10k-firmware-master
  folder is a folder named QCA6174.  Copy the QCA6174 folder to
  /lib/firmware/ath10k:

  unzip master.zip
  sudo cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/

  5) Rename two of the firmware files like so:

  cd /lib/firmware/ath10k/QCA6174/hw2.1/
  sudo mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin
  cd /lib/firmware/ath10k/QCA6174/hw3.0/
  sudo mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin

  6) Reboot your computer.  Run "lshw -C network" to see if your card is
  recognized.  You can delete the files you downloaded earlier:

  cd ~
  rm master.zip
  rm -r ath10k-firmware-master/

  Verified to work on Ubuntu 16.04 LTS (with kernel 4.4.0-21-generic)

  Last updated April 22, 2016

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

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


[Kernel-packages] [Bug 1626749] Re: autofs set $USER to "root" instead of current user

2016-11-14 Thread Nicolas
*** This bug is a duplicate of bug 1629204 ***
https://bugs.launchpad.net/bugs/1629204

Hello
4.4.0-47 solved it for me.

thks
Regards

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-09-23 Thread Nicolas
apport information

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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


[Kernel-packages] [Bug 1626749] Re: autofs set $USER to "root" instead of current user

2016-09-23 Thread Nicolas
apport information

** Tags added: apport-collected

** Description changed:

  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music
  
  When a user account try to mount the FS, automount complain :
  
   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file
  
  $USER, $UID and $GID are now sets with root variables instead of user
  account variables
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  nicolas1941 F pulseaudio
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
+ InstallationDate: Installed on 2016-02-07 (228 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ MachineType: Sony Corporation SVS1511R9ES
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=fr_FR
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-38-generic N/A
+  linux-backports-modules-4.4.0-38-generic  N/A
+  linux-firmware1.157.3
+ Tags:  xenial
+ Uname: Linux 4.4.0-38-generic x86_64
+ UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 03/30/2012
+ dmi.bios.vendor: Insyde Corp.
+ dmi.bios.version: R0140C5
+ dmi.board.asset.tag: N/A
+ dmi.board.name: VAIO
+ dmi.board.vendor: Sony Corporation
+ dmi.board.version: N/A
+ dmi.chassis.asset.tag: N/A
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Sony Corporation
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
+ dmi.product.name: SVS1511R9ES
+ dmi.product.version: C60AGQAL
+ dmi.sys.vendor: Sony Corporation

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1626749/+attachment/4747243/+files/AlsaInfo.txt

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5

[Kernel-packages] [Bug 1626749] Re: autofs set $USER to "root" instead of current user

2016-09-23 Thread Nicolas
I post the logfile generate in the syslog by automount in debug mode


Sep 23 19:43:28 nroc-linux automount[25168]: handle_packet: type = 3
Sep 23 19:43:28 nroc-linux automount[25168]: handle_packet_missing_indirect: 
token 307, name video, request pid 12909
Sep 23 19:43:28 nroc-linux automount[25168]: attempting to mount entry 
/home/nicolas/NASNRO/video
Sep 23 19:43:28 nroc-linux automount[25168]: lookup_mount: lookup(file): 
looking up video
Sep 23 19:43:28 nroc-linux automount[25168]: lookup_mount: lookup(file): video 
-> 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/video
Sep 23 19:43:28 nroc-linux automount[25168]: parse_mount: parse(sun): expanded 
entry: -fstype=cifs,credentials=/home/root/.creds-file,user=root,uid=0,gid=0 
://192.168.1.9/video
Sep 23 19:43:28 nroc-linux automount[25168]: parse_mount: parse(sun): gathered 
options: fstype=cifs,credentials=/home/root/.creds-file,user=root,uid=0,gid=0
Sep 23 19:43:28 nroc-linux automount[25168]: parse_mount: parse(sun): 
dequote("://192.168.1.9/video") -> ://192.168.1.9/video
Sep 23 19:43:28 nroc-linux automount[25168]: parse_mount: parse(sun): core of 
entry: 
options=fstype=cifs,credentials=/home/root/.creds-file,user=root,uid=0,gid=0, 
loc=://192.168.1.9/video
Sep 23 19:43:28 nroc-linux automount[25168]: sun_mount: parse(sun): mounting 
root /home/nicolas/NASNRO, mountpoint video, what //192.168.1.9/video, fstype 
cifs, options credentials=/home/root/.creds-file,user=root,uid=0,gid=0
Sep 23 19:43:28 nroc-linux automount[25168]: do_mount: //192.168.1.9/video 
/home/nicolas/NASNRO/video type cifs options 
credentials=/home/root/.creds-file,user=root,uid=0,gid=0 using module generic
Sep 23 19:43:28 nroc-linux automount[25168]: mount_mount: mount(generic): 
calling mkdir_path /home/nicolas/NASNRO/video
Sep 23 19:43:28 nroc-linux automount[25168]: mount_mount: mount(generic): 
calling mount -t cifs -o 
credentials=/home/root/.creds-file,user=root,uid=0,gid=0 //192.168.1.9/video 
/home/nicolas/NASNRO/video
Sep 23 19:43:28 nroc-linux automount[25168]: >> error 2 (No such file or 
directory) opening credential file /home/root/.creds-file
Sep 23 19:43:28 nroc-linux automount[25168]: mount(generic): failed to mount 
//192.168.1.9/video (type cifs) on /home/nicolas/NASNRO/video
Sep 23 19:43:28 nroc-linux automount[25168]: dev_ioctl_send_fail: token = 307
Sep 23 19:43:28 nroc-linux automount[25168]: failed to mount 
/home/nicolas/NASNRO/video
Sep 23 19:43:28 nroc-linux automount[25168]: handle_packet: type = 3
Sep 23 19:43:28 nroc-linux automount[25168]: handle_packet_missing_indirect: 
token 308, name video, request pid 12909
Sep 23 19:43:28 nroc-linux automount[25168]: dev_ioctl_send_fail: token = 308
Sep 23 19:43:28 nroc-linux automount[25168]: st_expire: state 1 path 
/home/nicolas/NASNRO
Sep 23 19:43:28 nroc-linux automount[25168]: expire_proc: exp_proc = 
139912387811072 path /home/nicolas/NASNRO
Sep 23 19:43:28 nroc-linux automount[25168]: expire_cleanup: got thid 
139912387811072 path /home/nicolas/NASNRO stat 0
Sep 23 19:43:28 nroc-linux automount[25168]: expire_cleanup: sigchld: exp 
139912387811072 finished, switching from 2 to 1
Sep 23 19:43:28 nroc-linux automount[25168]: st_ready: st_ready(): state = 2 
path /home/nicolas/NASNRO




The configuration files are (if needed to reproduce this testcase):

file /etc/auto.master :

/home/nicolas/NASNRO /etc/auto.nasnro --ghost,--timeout=30


file /etc/auto.nasnro :

video -fstype=cifs,credentials=/home/$USER/.creds-
file,user=$USER,uid=$UID,gid=$GID ://192.168.1.9/video


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

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnv

[Kernel-packages] [Bug 1437759] [NEW] [Lenovo Miix] Synaptic/ITE Tech touchpad (06cb:a001) cannot be configured by hid-rmi

2015-03-28 Thread Nicolas
Public bug reported:

Problem:
The touchpad in the dock of the Lenovo Miix 2 11 tablet does not work. It is 
handled by hid-rmi, which fails to configure the device:

kernel: [ 3007.388388] input: ITE Tech. Inc. ITE Device(8595) as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3.3/1-3.3:1.0/0003:06CB:A001.0008/input/input18
kernel: [ 3007.442088] hid-generic 0003:06CB:A001.0008: input,hiddev0,hidraw2: 
USB HID v1.10 Keyboard [ITE Tech. Inc. ITE Device(8595)] on 
usb-:00:14.0-3.3/input0
kernel: [ 3007.521067] hid-rmi 0003:06CB:A001.0009: failed to write hid report 
(-38)
kernel: [ 3007.521074] hid-rmi 0003:06CB:A001.0009: rmi_set_page: set page 
failed: -38.
kernel: [ 3007.521077] hid-rmi 0003:06CB:A001.0009: failed to set page select 
to 0.
kernel: [ 3007.523194] input: ITE Tech. Inc. ITE Device(8595) as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3.3/1-3.3:1.1/0003:06CB:A001.0009/input/input19
kernel: [ 3007.523546] hid-rmi 0003:06CB:A001.0009: input,hiddev0,hidraw3: USB 
HID v1.10 Pointer [ITE Tech. Inc. ITE Device(8595)] on 
usb-:00:14.0-3.3/input1
kernel: [ 3007.523552] hid-rmi 0003:06CB:A001.0009: Device failed to be 
properly configured


Ubuntu 15.04 Beta (but same problem with 14.10)
Kernel: Linux miix 3.19.0-10-generic #10-Ubuntu SMP Mon Mar 23 16:16:45 UTC 
2015 i686 i686 i686 GNU/Linux


The Keyboard (which works) and the touchpad are connected as one USB device 
with two interfaces:

Bus 001 Device 015: ID 06cb:a001 Synaptics, Inc. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x06cb Synaptics, Inc.
  idProduct  0xa001 
  bcdDevice0.03
  iManufacturer   1 ITE Tech. Inc.
  iProduct2 ITE Device(8595)
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   59
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  1 Boot Interface Subclass
  bInterfaceProtocol  1 Keyboard
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.10
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength 163
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   4
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  1 Boot Interface Subclass
  bInterfaceProtocol  2 Mouse
  iInterface  1 ITE Tech. Inc.
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.10
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength 133
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   4
Device Status: 0x
  (Bus Powered)


Workaround:
The touchpad works with hid-generic, if it is forces to handle the device. Yet, 
multitouch and dragging does not work.

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


** Tags: touch

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

Title:
  [Lenovo Miix] Synaptic/ITE Tech touchpad

[Kernel-packages] [Bug 1437759] Re: [Lenovo Miix] Synaptic/ITE Tech touchpad (06cb:a001) cannot be configured by hid-rmi

2015-03-30 Thread Nicolas
To force hid-generic, remove hid-rmi, load hid-generic and run:

echo echo 3 06cb a001 0 | sudo tee /sys/module/hid_generic/drivers/hid
\:hid-generic/new_id

By the way, the touchpad has a Synaptics S3203B chip.

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

Title:
  [Lenovo Miix] Synaptic/ITE Tech touchpad (06cb:a001) cannot be
  configured by hid-rmi

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problem:
  The touchpad in the dock of the Lenovo Miix 2 11 tablet does not work. It is 
handled by hid-rmi, which fails to configure the device:

  kernel: [ 3007.388388] input: ITE Tech. Inc. ITE Device(8595) as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3.3/1-3.3:1.0/0003:06CB:A001.0008/input/input18
  kernel: [ 3007.442088] hid-generic 0003:06CB:A001.0008: 
input,hiddev0,hidraw2: USB HID v1.10 Keyboard [ITE Tech. Inc. ITE Device(8595)] 
on usb-:00:14.0-3.3/input0
  kernel: [ 3007.521067] hid-rmi 0003:06CB:A001.0009: failed to write hid 
report (-38)
  kernel: [ 3007.521074] hid-rmi 0003:06CB:A001.0009: rmi_set_page: set page 
failed: -38.
  kernel: [ 3007.521077] hid-rmi 0003:06CB:A001.0009: failed to set page select 
to 0.
  kernel: [ 3007.523194] input: ITE Tech. Inc. ITE Device(8595) as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3.3/1-3.3:1.1/0003:06CB:A001.0009/input/input19
  kernel: [ 3007.523546] hid-rmi 0003:06CB:A001.0009: input,hiddev0,hidraw3: 
USB HID v1.10 Pointer [ITE Tech. Inc. ITE Device(8595)] on 
usb-:00:14.0-3.3/input1
  kernel: [ 3007.523552] hid-rmi 0003:06CB:A001.0009: Device failed to be 
properly configured

  
  Ubuntu 15.04 Beta (but same problem with 14.10)
  Kernel: Linux miix 3.19.0-10-generic #10-Ubuntu SMP Mon Mar 23 16:16:45 UTC 
2015 i686 i686 i686 GNU/Linux

  
  The Keyboard (which works) and the touchpad are connected as one USB device 
with two interfaces:

  Bus 001 Device 015: ID 06cb:a001 Synaptics, Inc. 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x06cb Synaptics, Inc.
idProduct  0xa001 
bcdDevice0.03
iManufacturer   1 ITE Tech. Inc.
iProduct2 ITE Device(8595)
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   59
  bNumInterfaces  2
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
  MaxPower  100mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass  1 Boot Interface Subclass
bInterfaceProtocol  1 Keyboard
iInterface  0 
  HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID   1.10
bCountryCode0 Not supported
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 163
   Report Descriptors: 
 ** UNAVAILABLE **
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   4
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber1
bAlternateSetting   0
bNumEndpoints   1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass  1 Boot Interface Subclass
bInterfaceProtocol  2 Mouse
iInterface  1 ITE Tech. Inc.
  HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID   1.10
bCountryCode0 Not supported
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 133
   Report Descriptors: 
 ** UNAVAILABLE **
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x82  EP 2 IN
  bmAt

[Kernel-packages] [Bug 1430846] [NEW] [Lenovo Thinkpad X1 Carbon, X250] Clickpad buttons not working with synaptics

2015-03-11 Thread Nicolas
Public bug reported:

On the Thinkpad X1 and X250 which have a new clickpad with hardware buttons 
(again), I cannot use the hardware buttons with the synaptics driver.
There is a patch series available fixing this problem:
https://patchwork.kernel.org/patch/5794551/
https://patchwork.kernel.org/patch/5794641/
https://patchwork.kernel.org/patch/5794561/
https://patchwork.kernel.org/patch/5794671/
https://patchwork.kernel.org/patch/5794681/
https://patchwork.kernel.org/patch/5794621/
https://patchwork.kernel.org/patch/5794601/
https://patchwork.kernel.org/patch/5820871/

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

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

Title:
  [Lenovo Thinkpad X1 Carbon, X250] Clickpad buttons not working with
  synaptics

Status in linux package in Ubuntu:
  New

Bug description:
  On the Thinkpad X1 and X250 which have a new clickpad with hardware buttons 
(again), I cannot use the hardware buttons with the synaptics driver.
  There is a patch series available fixing this problem:
  https://patchwork.kernel.org/patch/5794551/
  https://patchwork.kernel.org/patch/5794641/
  https://patchwork.kernel.org/patch/5794561/
  https://patchwork.kernel.org/patch/5794671/
  https://patchwork.kernel.org/patch/5794681/
  https://patchwork.kernel.org/patch/5794621/
  https://patchwork.kernel.org/patch/5794601/
  https://patchwork.kernel.org/patch/5820871/

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

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


[Kernel-packages] [Bug 1430846] Re: [Lenovo Thinkpad X1 Carbon, X250] Clickpad buttons not working with synaptics

2015-03-11 Thread Nicolas
Ah, thanks for the clarification about the stable update process.

I only tried the full patchset (including the 8th) and rebuilt the
kernel by myself -- which was working fine.

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

Title:
  [Lenovo Thinkpad X1 Carbon, X250] Clickpad buttons not working with
  synaptics

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Thinkpad X1 and X250 which have a new clickpad with hardware buttons 
(again), I cannot use the hardware buttons with the synaptics driver.
  There is a patch series available fixing this problem:
  https://patchwork.kernel.org/patch/5794551/
  https://patchwork.kernel.org/patch/5794641/
  https://patchwork.kernel.org/patch/5794561/
  https://patchwork.kernel.org/patch/5794671/
  https://patchwork.kernel.org/patch/5794681/
  https://patchwork.kernel.org/patch/5794621/
  https://patchwork.kernel.org/patch/5794601/
  https://patchwork.kernel.org/patch/5820871/

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

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


[Kernel-packages] [Bug 1430846] Re: [Lenovo Thinkpad X1 Carbon, X250] Clickpad buttons not working with synaptics

2015-04-11 Thread Nicolas
As  the new kernel versions of vivid contain these patches, and the
touchpad is working perfectly now, this bug can be closed.

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

Title:
  [Lenovo Thinkpad X1 Carbon, X250] Clickpad buttons not working with
  synaptics

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Thinkpad X1 and X250 which have a new clickpad with hardware buttons 
(again), I cannot use the hardware buttons with the synaptics driver.
  There is a patch series available fixing this problem:
  https://patchwork.kernel.org/patch/5794551/
  https://patchwork.kernel.org/patch/5794641/
  https://patchwork.kernel.org/patch/5794561/
  https://patchwork.kernel.org/patch/5794671/
  https://patchwork.kernel.org/patch/5794681/
  https://patchwork.kernel.org/patch/5794621/
  https://patchwork.kernel.org/patch/5794601/
  https://patchwork.kernel.org/patch/5820871/

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

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


[Kernel-packages] [Bug 1852423] [NEW] Nouveau driver fails to set up GeForce GTX 1050 Ti

2019-11-13 Thread Nicolas
Public bug reported:

The nouveau driver fails to setup the GeForce GTX 1050 Ti (not mobile)
card. As soon as it tries to set the mode (before X11 starts), the
screen becomes messed up. The screen still refreshes, but pixels look
scrambled. X11 does not start any more.

This bug appeared with a recent update.

Adding nomodeset to the command line fixes the problem. But then, dual
screen no longer works.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.15.0.69.71
ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18
Uname: Linux 4.15.0-69-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Wed Nov 13 12:27:38 2019
MachineType: HP HP Z8 G4 Workstation
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-69-generic 
root=/dev/mapper/vg-ubuntu ro intel_iommu=on iommu=pt rd.driver.pre=vfio-pci 
rd.driver.blacklist=nvidia acpi_osi=! "acpi_osi=Windows 2009" text
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-69-generic N/A
 linux-backports-modules-4.15.0-69-generic  N/A
 linux-firmware 1.173.9
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2018
dmi.bios.vendor: HP
dmi.bios.version: P60 v01.71
dmi.board.asset.tag: CZC907BCFH
dmi.board.name: 81C7
dmi.board.vendor: HP
dmi.board.version: MVB 0C
dmi.chassis.asset.tag: CZC907BCFH
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP60v01.71:bd11/05/2018:svnHP:pnHPZ8G4Workstation:pvr:rvnHP:rn81C7:rvrMVB0C:cvnHP:ct3:cvr:
dmi.product.family: 103C_53335X HP Workstation
dmi.product.name: HP Z8 G4 Workstation
dmi.sys.vendor: HP

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


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

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

Title:
  Nouveau driver fails to set up GeForce GTX 1050 Ti

Status in linux package in Ubuntu:
  New

Bug description:
  The nouveau driver fails to setup the GeForce GTX 1050 Ti (not mobile)
  card. As soon as it tries to set the mode (before X11 starts), the
  screen becomes messed up. The screen still refreshes, but pixels look
  scrambled. X11 does not start any more.

  This bug appeared with a recent update.

  Adding nomodeset to the command line fixes the problem. But then, dual
  screen no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.69.71
  ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18
  Uname: Linux 4.15.0-69-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov 13 12:27:38 2019
  MachineType: HP HP Z8 G4 Workstation
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-69-generic 
root=/dev/mapper/vg-ubuntu ro intel_iommu=on iommu=pt rd.driver.pre=vfio-pci 
rd.driver.blacklist=nvidia acpi_osi=! "acpi_osi=Windows 2009" text
  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-69-generic N/A
   linux-backports-modules-4.15.0-69-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P60 v01.71
  dmi.board.asset.tag: CZC907BCFH
  dmi.board.name: 81C7
  dmi.board.vendor: HP
  dmi.board.version: MVB 0C
  dmi.chassis.asset.tag: CZC907BCFH
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP60v01.71:bd11/05/2018:svnHP:pnHPZ8G4Workstation:pvr:rvnHP:rn81C7:rvrMVB0C:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z8 G4 Workstation
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packa

[Kernel-packages] [Bug 1806392] [NEW] tun/tap: unable to manage carrier state from userland

2018-12-03 Thread Nicolas Dichtel
Public bug reported:

This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e

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

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

Title:
  tun/tap: unable to manage carrier state from userland

Status in linux package in Ubuntu:
  New

Bug description:
  This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
  change").

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=26d31925cd5e

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

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


[Kernel-packages] [Bug 1766573] [NEW] linux < 4.11: unable to use netfilter logging from non-init namespaces

2018-04-24 Thread Nicolas Dichtel
Public bug reported:

Was disabled by the following patch (linux 3.10):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2
netfilter: xt_LOG: add net namespace support for xt_LOG

And fixed in linux 4.11:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3
netfilter: allow logging from non-init namespaces

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

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

Title:
  linux < 4.11: unable to use netfilter logging from non-init namespaces

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Was disabled by the following patch (linux 3.10):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2
  netfilter: xt_LOG: add net namespace support for xt_LOG

  And fixed in linux 4.11:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3
  netfilter: allow logging from non-init namespaces

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

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


[Kernel-packages] [Bug 1766573] Re: linux < 4.11: unable to use netfilter logging from non-init namespaces

2018-04-25 Thread Nicolas Dichtel
Test is ok on my side.
Thank you for the quick 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/1766573

Title:
  linux < 4.11: unable to use netfilter logging from non-init namespaces

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

Bug description:
  Was disabled by the following patch (linux 3.10):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2
  netfilter: xt_LOG: add net namespace support for xt_LOG

  And fixed in linux 4.11:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3
  netfilter: allow logging from non-init namespaces

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

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


[Kernel-packages] [Bug 1828351] [NEW] RAID 10 with MegaRaid controller gives poor write performance

2019-05-09 Thread Nicolas Pochet
Public bug reported:

On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
A simple test:
dd if=/dev/zero of=out bs=1M count=100
Outputs a 35MB/s speed.

The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
Strip size: 64K
Access Policy: RW
Read Policy: Normal
Write Policy: Writethrough
IO Policy: Direct
Disable BGI: No

uname -a
4.15.0-48-generic #51-Ubuntu SMP

[0]
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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


** Tags: bionic

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

Title:
  RAID 10 with MegaRaid controller gives poor write performance

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
  A simple test:
  dd if=/dev/zero of=out bs=1M count=100
  Outputs a 35MB/s speed.

  The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
  Strip size: 64K
  Access Policy: RW
  Read Policy: Normal
  Write Policy: Writethrough
  IO Policy: Direct
  Disable BGI: No

  uname -a
  4.15.0-48-generic #51-Ubuntu SMP

  [0]
  
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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

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


[Kernel-packages] [Bug 1828351] Re: RAID 10 with MegaRaid controller gives poor write performance

2019-05-09 Thread Nicolas Pochet
Subscribing field-critical as it is blocking an ongoing deployment

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

Title:
  RAID 10 with MegaRaid controller gives poor write performance

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
  A simple test:
  dd if=/dev/zero of=out bs=1M count=100
  Outputs a 35MB/s speed.

  The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
  Strip size: 64K
  Access Policy: RW
  Read Policy: Normal
  Write Policy: Writethrough
  IO Policy: Direct
  Disable BGI: No

  uname -a
  4.15.0-48-generic #51-Ubuntu SMP

  [0]
  
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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

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


[Kernel-packages] [Bug 1828351] Re: RAID 10 with MegaRaid controller gives poor write performance

2019-05-09 Thread Nicolas Pochet
Unsubscribing field-critical and marking as invalid. The main reason of
this was that bcache was not tuned automatically.

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

Title:
  RAID 10 with MegaRaid controller gives poor write performance

Status in linux package in Ubuntu:
  Invalid

Bug description:
  On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
  A simple test:
  dd if=/dev/zero of=out bs=1M count=100
  Outputs a 35MB/s speed.

  The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
  Strip size: 64K
  Access Policy: RW
  Read Policy: Normal
  Write Policy: Writethrough
  IO Policy: Direct
  Disable BGI: No

  uname -a
  4.15.0-48-generic #51-Ubuntu SMP

  [0]
  
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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

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


[Kernel-packages] [Bug 1779830] [NEW] vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

2018-07-03 Thread Nicolas Dichtel
Public bug reported:

The following upstream patch (v4.7) is missing in xenial:

450744051d20 ("vfio/pci: Hide broken INTx support from user")
http://scm/kernels/linux-upstream/commit/?id=450744051d20

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

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

Title:
  vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

Status in linux package in Ubuntu:
  New

Bug description:
  The following upstream patch (v4.7) is missing in xenial:

  450744051d20 ("vfio/pci: Hide broken INTx support from user")
  http://scm/kernels/linux-upstream/commit/?id=450744051d20

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

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


[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns

2018-07-12 Thread Nicolas Dichtel
Well, it could be a workaround but it would be great to have it in the
4.4 if it's not too complicated for you. What do you think?

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

Title:
  netns: unable to follow an interface that moves to another netns

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

Bug description:
  The following upstream patches are missing (v4.16):

  6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-04-18 Thread Nicolas Devillers
Hello,

It works fine with the proposed kernel 4.15.0-48-generic taken at:

http://ppa.launchpad.net/canonical-kernel-
team/proposed/ubuntu/pool/main/l/linux/

Please note that I updated to the latest Lenovo Provided Bios (1.23)
since then.

** Description changed:

  === SRU Justification ===
  [Impact]
- 4.15.0-46 breaks once worked external display over docking.
+ 4.15.0-46 breaks once working external display over docking.
  
  [Fix]
  Revert the commit that causes regression.
-  
+ 
  [Test]
  User confirms reverting the commit solves the regression.
  
  [Regression Potential]
  Low. Docking can works without this commit on Bionic kernel.
  
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.
  
  === Original Bug Report ===
  
  Laptop is running Ubuntu 18.04.2 LTS.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

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

Bug description:
  === SRU Justification ===
  [Impact]
  4.15.0-46 breaks once working external display over docking.

  [Fix]
  Revert the commit that causes regression.

  [Test]
  User confirms reverting the commit solves the regression.

  [Regression Potential]
  Low. Docking can works without this commit on Bionic kernel.

  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  === Original Bug Report ===

  Laptop is running Ubuntu 18.04.2 LTS.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.

[Kernel-packages] [Bug 1825490] [NEW] Bug in the update of ubuntu 18.10 to 19.04

2019-04-19 Thread Nicolas Barrat
Public bug reported:

First in the upgrade I had a notification like the install-info were not
installed correctly. After, at the end after the next part of the
installation, they say that the upgrade has not been completed and that
a restauration will be made. Then a new page was opened to say that the
upgrade was made successfully. After this, everything was closed but the
part of the cleaning and restarting was not made so I restarted my
computer and I was on ubuntu 19.04 but a new notification said me that I
had software bug so I send the report.

(It was an upgrade from the last update of Ubuntu 18.10, I made an
update before the upgrade, to the 19.04)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nicolasb   1854 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 10:50:23 2019
InstallationDate: Installed on 2019-02-27 (50 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 04ca:706d Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ProBook 450 G5
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f6f4518b-e644-4545-86f7-061cb36bda20 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware1.178
SourcePackage: linux
StagingDrivers: r8822be
UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
dmi.bios.date: 01/03/2019
dmi.bios.vendor: HP
dmi.bios.version: Q85 Ver. 01.06.00
dmi.board.name: 837D
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.32.00
dmi.chassis.asset.tag: 5CD82354RB
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.06.00:bd01/03/2019:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.32.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 450 G5
dmi.product.sku: 1LU55AV
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug disco staging

** Attachment added: "Capture d’écran de 2019-04-19 10-44-52.png"
   
https://bugs.launchpad.net/bugs/1825490/+attachment/5256942/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202019-04-19%2010-44-52.png

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

Title:
  Bug in the update of ubuntu 18.10 to 19.04

Status in linux package in Ubuntu:
  New

Bug description:
  First in the upgrade I had a notification like the install-info were
  not installed correctly. After, at the end after the next part of the
  installation, they say that the upgrade has not been completed and
  that a restauration will be made. Then a new page was opened to say
  that the upgrade was made successfully. After this, everything was
  closed but the part of the cleaning and restarting was not made so I
  restarted my computer and I was on ubuntu 19.04 but a new notification
  said me that I had software bug so I send the report.

  (It was an upgrade from the last update of Ubuntu 18.10, I made an
  update before the upgrade, to the 19.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolasb   1854 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 10:50:23 2019
  InstallationDate: Installed on 2019-02-27 (50 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04ca:706d Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f6f4518b-e644-4545-86f7-061cb36bda20 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   l

[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial

2019-04-19 Thread Nicolas Dichtel
root@ubuntu1604:~# dpkg --list | grep iproute2
ii  iproute2 4.3.0-1ubuntu3.16.04.4
amd64networking and traffic control tools
root@ubuntu1604:~# apt-get install iproute2/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '4.3.0-1ubuntu3.16.04.5' (Ubuntu:16.04/xenial-proposed 
[amd64]) for 'iproute2'
Suggested packages:
  iproute2-doc
The following packages will be upgraded:
  iproute2
1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
Need to get 523 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 iproute2 
amd64 4.3.0-1ubuntu3.16.04.5 [523 kB]
Fetched 523 kB in 0s (6,782 kB/s)
(Reading database ... 85262 files and directories currently installed.)
Preparing to unpack .../iproute2_4.3.0-1ubuntu3.16.04.5_amd64.deb ...
Unpacking iproute2 (4.3.0-1ubuntu3.16.04.5) over (4.3.0-1ubuntu3.16.04.4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up iproute2 (4.3.0-1ubuntu3.16.04.5) ...
root@ubuntu1604:~# dpkg --list | grep iproute2
ii  iproute2 4.3.0-1ubuntu3.16.04.5
amd64networking and traffic control tools
root@ubuntu1604:~# ip link add dev dummy0 type dummy
RTNETLINK answers: File exists
root@ubuntu1604:~# ip link add dev dummy1 type dummy
root@ubuntu1604:~# ip link set dev dummy0 up
root@ubuntu1604:~# ip link set dev dummy1 up
root@ubuntu1604:~# tc qdisc add dev dummy0 handle 1: root prio
root@ubuntu1604:~# tc filter add dev dummy0 parent 1: matchall skip_hw action 
mirred egress mirror dev dummy1
root@ubuntu1604:~# tc filter show dev dummy0
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1

root@ubuntu1604:~#

=> test is OK.

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

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]

  == Impact ==
  The Xenial 4.4 kernel already has a patch applied which implements the 
matchall filter. But in order to actually use it, iproute2 needs to pick up the 
user-space
  side of the implementation.

  == Fix ==
  Backported a patch from iproute2 upstream which adds the missing support. 
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).

  == Risk of Regression ==
  This adds a new filter type which has to be actively selected. This should 
not impact existing uses. So low.

  == Testcase ==
  ip link add dev dummy0 type dummy
  ip link add dev dummy1 type dummy
  ip link set dev dummy0 up
  ip link set dev dummy1 up
  tc qdisc add dev dummy0 handle 1: root prio
  tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress 
mirror dev dummy1

  at this point, "tc filter show dev dummy0" should spit out something
  like:

  filter parent 1: protocol all pref 49152 matchall 
  filter parent 1: protocol all pref 49152 matchall handle 0x1 
  action order 1: mirred (Egress Mirror to device dummy1) pipe
  index 1 ref 1 bind 1
   
  and the functionality can be tested via

  tcpdump -n -i dummy1 &
  ping -I dummy0 1.2.3.4

  ---

  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

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

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


[Kernel-packages] [Bug 1825985] [NEW] macvlan: add ndo_change_proto_down support

2019-04-23 Thread Nicolas Dichtel
Public bug reported:

The following linux upstream patches are missing to support vrrp with
frr:

- b58996795dc4 ("net: dev: add generic protodown handler")
- 2e8b4ba64676 ("macvlan: add ndo_change_proto_down support")
- 8f1af75df3a7 ("vxlan: add ndo_change_proto_down support")

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b58996795dc4
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2e8b4ba64676
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f1af75df3a7

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

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

Title:
  macvlan: add ndo_change_proto_down support

Status in linux package in Ubuntu:
  New

Bug description:
  The following linux upstream patches are missing to support vrrp with
  frr:

  - b58996795dc4 ("net: dev: add generic protodown handler")
  - 2e8b4ba64676 ("macvlan: add ndo_change_proto_down support")
  - 8f1af75df3a7 ("vxlan: add ndo_change_proto_down support")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b58996795dc4
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2e8b4ba64676
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f1af75df3a7

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

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


[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns

2018-08-13 Thread Nicolas Dichtel
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  netns: unable to follow an interface that moves to another netns

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

Bug description:

  == SRU Justification ==
  6Wind is requesting these three patches. The patches fix a bug that prevents 
a user
  from following an interface that moves to another netns.

  These commits are also needed in Xenial.  However, they will be sent in
  a separate SRU request due to additional prereq commits being needed for
  Xenial.

  == Fixes ==
  b2d3bcfa26a7 ("net: core: Expose number of link up/down transitions")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  == Regression Potential ==
  Medium due to three patches needed and the changes to core networking. 

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





  The following upstream patches are missing (v4.16):

  6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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


[Kernel-packages] [Bug 1779761] Re: Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

2018-08-24 Thread Nicolas Ramoudt
*** This bug is a duplicate of bug 1779827 ***
https://bugs.launchpad.net/bugs/1779827

I recently experience exactly the same issue on a production server
(Linode vps solution).  Reading this specific log starts to make sense
to me now.  Started already a thread on
https://www.linode.com/community/questions/17135/php72-fpmservice-
failing-after-reboot-nginx-error-502

Issue started after migrating to a new vps plan but slower server.  But
despite a slower system, the kernel here appeared automatically upgraded
to 4.17.17.  Previous kernel was < 4.14 (but didn't know the exact
number because didn't pay attention to as at that time, it worked fine
then).

Symptoms are exactly the same:
php7.2-fpm.service: Start operation timed out. Terminating.
php7.2-fpm.service: Failed with result 'timeout'.
Failed to start The PHP 7.2 FastCGI Process Manager.

ssh login manually, do a "sudo service php7.2-fpm start" and then it
works...

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:c

[Kernel-packages] [Bug 1830756] [NEW] tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

2019-05-28 Thread Nicolas Dichtel
Public bug reported:

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

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

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

Title:
  tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 1823725] Re: packet: reset network header if packet shorter than ll reserved space

2019-06-12 Thread Nicolas Dichtel
This bug is still there, valid packets may be dropped with variable
length protocols like IP tunnels for example. Any actions expected on my
side?

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

Title:
  packet: reset network header if packet shorter than ll reserved space

Status in linux package in Ubuntu:
  New

Bug description:
  After backport of linux upstream commit 9ed988cd5915 ("packet:
  validate variable length ll headers")
  (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
  missing :

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915

  9ed988cd5915 ("packet: validate variable length ll headers")

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

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


[Kernel-packages] [Bug 1812875] [NEW] ip6_gre: fix tunnel list corruption for x-netns

2019-01-22 Thread Nicolas Dichtel
Public bug reported:

The following upstream patch is missing in ubuntu-18.04: ab5098fa25b9
("ip6_gre: fix tunnel list corruption for x-netns").

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

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

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

Title:
  ip6_gre: fix tunnel list corruption for x-netns

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following upstream patch is missing in ubuntu-18.04: ab5098fa25b9
  ("ip6_gre: fix tunnel list corruption for x-netns").

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

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

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


[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2018-03-23 Thread Nicolas Krzywinski
Same problem on Gigabyte GA-T1028X
Intel® Atom™ Processor N280(1.66GHz)
Mobile Intel® GS945 Express Chipsets
Intel® GMA 950

Adding this to /etc/default/grub helped me too:
GRUB_GFXPAYLOAD_LINUX=text

Additionally adding this to the GRUB_CMDLINE_LINUX_DEFAULT line enabled the 
touchpad (which wasn't working before):
i8042.noloop=1 usbhid.quirks=0xeef:0x1:0x40

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1759314] [NEW] missing memory (32Gib instead of 64GiB)

2018-03-27 Thread Nicolas Jungers
Public bug reported:

The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
16384 MiB, but dmesg and free report 32GiB

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/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'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Date: Tue Mar 27 17:48:32 2018
HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
InstallationDate: Installed on 2018-03-27 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-13-generic N/A
 linux-backports-modules-4.15.0-13-generic  N/A
 linux-firmware 1.173
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/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: X370 Taichi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug bionic

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

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/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'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-res

[Kernel-packages] [Bug 1759314] Re: missing memory (32Gib instead of 64GiB)

2018-03-27 Thread Nicolas Jungers
dmidecode --type memory

** Attachment added: "dmidecode --type memory"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759314/+attachment/5092475/+files/dmidecode_memory.txt

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

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/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'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  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/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1759314] Re: missing memory (32Gib instead of 64GiB)

2018-03-28 Thread Nicolas Jungers
I suspect a HW bug. Kernel 4.13.0-37-generic shows 32 GiB and kernel
4.16.0-041600rc7-generic both report 32 GiB. But on another box with the
very same HW I got 64 GiB with all kernels.

You can mark this one as invalid. Sorry for the false alarm.

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

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/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'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  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/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

2018-10-03 Thread Nicolas Dichtel
It works on my side:

$ ./ip/ip r a 2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto 188 metric 20
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0  proto 188  metric 20
$ mkdir -p /etc/iproute2/rt_protos.d
$ echo "188 foo" > /etc/iproute2/rt_protos.d/bar.conf
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0  proto foo  metric 20

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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


[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial

2018-10-03 Thread Nicolas Dichtel
> Note that the iproute2 patch will be needed to use this filter:
> 
> https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=d5cbf3ff0561
> (embedded headers must be updated also).

This link is dead, here is another one:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=d5cbf3ff0561

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

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

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


[Kernel-packages] [Bug 1849085] [NEW] netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID

2019-10-21 Thread Nicolas Dichtel
Public bug reported:

The following upstream patch is missing:

- 993e4c929a07 netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07

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

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

Title:
  netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID

Status in linux package in Ubuntu:
  New

Bug description:
  The following upstream patch is missing:

  - 993e4c929a07 netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07

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

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


[Kernel-packages] [Bug 1849085] Re: netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID

2019-10-21 Thread Nicolas Dichtel
** Description changed:

- The following upstream patch is missing:
+ [SRU Justification]
  
- - 993e4c929a07 netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID
+ [Impact]
+ 
+ The netlink flag NLM_F_ECHO has no effect with the rtnetlink command
+ RTM_NEWNSID. This has been fixed in v5.4 by the upstream commit
+ 993e4c929a07 ("netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID"). The
+ bug is here since v4.0.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07
+ 
+ == Fix ==
+ 
+ Backport the requested patches to Disco (5.0), Bionic (4.15) and
+ Xenial (4.4).
+ 
+ == Risk of Regregression ==
+ 
+ This patch is quite trivial and limited to the code that manage
+ RTM_[NEW|GET]NSID commands. Risk should be low.

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

Title:
  netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  The netlink flag NLM_F_ECHO has no effect with the rtnetlink command
  RTM_NEWNSID. This has been fixed in v5.4 by the upstream commit
  993e4c929a07 ("netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID"). The
  bug is here since v4.0.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07

  == Fix ==

  Backport the requested patches to Disco (5.0), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regregression ==

  This patch is quite trivial and limited to the code that manage
  RTM_[NEW|GET]NSID commands. Risk should be low.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-13 Thread Nicolas Dichtel
** Changed in: linux (Ubuntu)
   Status: Expired => 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/1830756

Title:
  tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 1823725] Re: packet: reset network header if packet shorter than ll reserved space

2019-08-13 Thread Nicolas Dichtel
** Changed in: linux (Ubuntu)
   Status: Expired => New

** Description changed:

  After backport of linux upstream commit 9ed988cd5915 ("packet: validate
  variable length ll headers") (https://kernel.ubuntu.com/git/ubuntu
  /ubuntu-bionic.git/commit/?id=c6026847a0a1) the following upstream patch
  is missing :
  
- 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993675a3100b
  
- 9ed988cd5915 ("packet: validate variable length ll headers")
+ 993675a3100b ("packet: reset network header if packet shorter than ll
+ reserved space")

** Description changed:

- After backport of linux upstream commit 9ed988cd5915 ("packet: validate
- variable length ll headers") (https://kernel.ubuntu.com/git/ubuntu
- /ubuntu-bionic.git/commit/?id=c6026847a0a1) the following upstream patch
- is missing :
+ After backport of linux upstream commit b84bbaf7a6c8 ("packet: in
+ packet_snd start writing at link layer allocation")
+ (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
+ bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
+ missing :
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993675a3100b
  
  993675a3100b ("packet: reset network header if packet shorter than ll
  reserved space")

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

Title:
  packet: reset network header if packet shorter than ll reserved space

Status in linux package in Ubuntu:
  New

Bug description:
  After backport of linux upstream commit b84bbaf7a6c8 ("packet: in
  packet_snd start writing at link layer allocation")
  (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
  missing :

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993675a3100b

  993675a3100b ("packet: reset network header if packet shorter than ll
  reserved space")

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

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


[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket

2019-08-29 Thread Nicolas Dichtel
** Description changed:

+ [SRU Justification]
+ 
+ == Impact ==
+ 
+ IPv6 packets may be dropped during the neighbor resolution when a
+ userspace program uses IPv6 raw sockets. The commit that introduces
+ this bug has not been identified, but it's here at least from Xenial (4.4).
+ This was fixed in the requested backport (from 5.2).
+ 
+ == Fix ==
+ 
+ Backport the requested patches to Disco (5.0), Bionic (4.15) and
+ Xenial (4.4).
+ 
+ == Risk of Regregression ==
+ 
+ The change slightly modifies the target IPv6 address in neighbor
+ resolution engine. Risk should be low and limited to ipv6.
+ 
+ ---
+ 
  With an IPv6 raw socket, packets may be dropped during the neighbour
  resolution. It is fixed upstream by these patches:
  
  9b1c1ef13b35 ipv6: constify rt6_nexthop()
  2c6b55f45d53 ipv6: fix neighbour resolution with raw socket
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f
  
  The detail of the bug is explained in the second patch.

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

Title:
  ipv6: fix neighbour resolution with raw socket

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

Bug description:
  [SRU Justification]

  == Impact ==

  IPv6 packets may be dropped during the neighbor resolution when a
  userspace program uses IPv6 raw sockets. The commit that introduces
  this bug has not been identified, but it's here at least from Xenial (4.4).
  This was fixed in the requested backport (from 5.2).

  == Fix ==

  Backport the requested patches to Disco (5.0), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regregression ==

  The change slightly modifies the target IPv6 address in neighbor
  resolution engine. Risk should be low and limited to ipv6.

  ---

  With an IPv6 raw socket, packets may be dropped during the neighbour
  resolution. It is fixed upstream by these patches:

  9b1c1ef13b35 ipv6: constify rt6_nexthop()
  2c6b55f45d53 ipv6: fix neighbour resolution with raw socket

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f

  The detail of the bug is explained in the second patch.

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

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


[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket

2019-09-06 Thread Nicolas Dichtel
Tests are ok for us.

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

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

Title:
  ipv6: fix neighbour resolution with raw socket

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

Bug description:
  [SRU Justification]

  == Impact ==

  IPv6 packets may be dropped during the neighbor resolution when a
  userspace program uses IPv6 raw sockets. The commit that introduces
  this bug has not been identified, but it's here at least from Xenial (4.4).
  This was fixed in the requested backport (from 5.2).

  == Fix ==

  Backport the requested patches to Disco (5.0), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regregression ==

  The change slightly modifies the target IPv6 address in neighbor
  resolution engine. Risk should be low and limited to ipv6.

  ---

  With an IPv6 raw socket, packets may be dropped during the neighbour
  resolution. It is fixed upstream by these patches:

  9b1c1ef13b35 ipv6: constify rt6_nexthop()
  2c6b55f45d53 ipv6: fix neighbour resolution with raw socket

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f

  The detail of the bug is explained in the second patch.

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

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


[Kernel-packages] [Bug 1774815] Re: Add bpftool to linux-tools-common

2019-03-06 Thread Nicolas Dichtel
Any news on this topic?

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

Title:
  Add bpftool to linux-tools-common

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

Bug description:
  bpftool is a debugging and introspection tool actively developed by
  the BPF kernel community. It's developed as part of the kernel source
  tree under tools/:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/bpf/bpftool

  It would be really great and appreciated if Ubuntu folks could package
  this as part of linux-tools-common.

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

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


[Kernel-packages] [Bug 1819486] [NEW] Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-11 Thread Nicolas Devillers
Public bug reported:

While previously working using 4.15.0-45-generic, booting my thinkpad
T480 on a dock with additional screen connected and "kernel
4.15.0-46-generic" lead to a crash of the system.

Laptop is running Ubuntu 18.04.2 LTS.

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


** Tags: bionic

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-11 Thread Nicolas Devillers
** Attachment added: "kernelst.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+attachment/5245483/+files/kernelst.txt

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-11 Thread Nicolas Devillers
** Attachment added: "version.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+attachment/5245481/+files/version.txt

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-11 Thread Nicolas Devillers
** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+attachment/5245482/+files/lspci.txt

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-11 Thread Nicolas Devillers
apport information

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

** Tags added: apport-collected

** Description changed:

  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.
  
  Laptop is running Ubuntu 18.04.2 LTS.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
+  /dev/snd/controlC1:  user   3449 F pulseaudio
+  /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
+  /dev/snd/controlC0:  user   3449 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
+ InstallationDate: Installed on 2018-06-28 (256 days ago)
+ InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
+ MachineType: LENOVO 20L5000AFR
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
+ ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-45-generic N/A
+  linux-backports-modules-4.15.0-45-generic  N/A
+  linux-firmware 1.173.3
+ Tags:  bionic
+ Uname: Linux 4.15.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 03/14/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N24ET37W (1.12 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20L5000AFR
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad T480
+ dmi.product.name: 20L5000AFR
+ dmi.product.version: ThinkPad T480
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1819486/+attachment/5245517/+files/AlsaInfo.txt

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

To manage notificat

[Kernel-packages] [Bug 1819486] ProcEnviron.txt

2019-03-11 Thread Nicolas Devillers
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1819486/+attachment/5245525/+files/ProcEnviron.txt

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-03-11 Thread Nicolas Devillers
apport information

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

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-11 Thread Nicolas Devillers
** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+attachment/5245519/+files/CurrentDmesg.txt

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-12 Thread Nicolas Devillers
Kai, It looks like that the intel driver was not bundle in this kernel?
No kernel panic but WM runs in software mode and additional display are
not being detected.

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-12 Thread Nicolas Devillers
pff, clearly I needed one cup of coffee before answering this.. sry. I
will check again shortly..

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

2019-03-12 Thread Nicolas Devillers
Yeah, it works fine with your module. Did you just revert "drm-i915-fix-
hotplug-irq-ack-on-i965-g4x.patch" ?

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  Laptop is running Ubuntu 18.04.2 LTS.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1806392] Re: tun/tap: unable to manage carrier state from userland

2019-03-20 Thread Nicolas Dichtel
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  tun/tap: unable to manage carrier state from userland

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

Bug description:
  === SRU Justification ===
  [Impact]
  Userspace cannot change tun's carrier state.

  [Fix]
  Add .ndo_change_carrier callback for tun.

  [Test]
  User confirm the backport works.
   
  [Regression Potential]
  Low. It add a new function and a new case switch for ioctl, but the new
  code doesn't affect existing behavior.
  === Original Bug Report ===
  This upstream patch is missing: 26d31925cd5e ("tun: implement carrier 
change").

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=26d31925cd5e

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

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


[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket

2019-10-03 Thread Nicolas Dichtel
Tests are ok here.

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

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

Title:
  ipv6: fix neighbour resolution with raw socket

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

Bug description:
  [SRU Justification]

  == Impact ==

  IPv6 packets may be dropped during the neighbor resolution when a
  userspace program uses IPv6 raw sockets. The commit that introduces
  this bug has not been identified, but it's here at least from Xenial (4.4).
  This was fixed in the requested backport (from 5.2).

  == Fix ==

  Backport the requested patches to Disco (5.0), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regregression ==

  The change slightly modifies the target IPv6 address in neighbor
  resolution engine. Risk should be low and limited to ipv6.

  ---

  With an IPv6 raw socket, packets may be dropped during the neighbour
  resolution. It is fixed upstream by these patches:

  9b1c1ef13b35 ipv6: constify rt6_nexthop()
  2c6b55f45d53 ipv6: fix neighbour resolution with raw socket

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f

  The detail of the bug is explained in the second patch.

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

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


[Kernel-packages] [Bug 1836261] Re: xfrm interface: several kernel panic

2019-10-07 Thread Nicolas Dichtel
root@dut-vm:~# ip netns add foo
root@dut-vm:~# ip netns add bar
root@dut-vm:~# ip -n foo netns set bar 0
root@dut-vm:~# ip -n foo link add xfrmi0 link-netnsid 0 type xfrm dev lo if_id 
23
root@dut-vm:~# ip -n bar link ls xfrmi0
Device "xfrmi0" does not exist.
root@dut-vm:~# ip -n foo link ls xfrmi0
2: xfrmi0@if1:  mtu 1500 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
link/none 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff link-netns bar

=> interface is correctly created and there is no backtrace in dmesg, OK


root@dut-vm:~# ip netns del foo
root@dut-vm:~# ip netns del bar
root@dut-vm:~# ip link add xfrm1 type xfrm dev lo if_id 1
root@dut-vm:~# ip link add xfrm2 type xfrm dev lo if_id 2
root@dut-vm:~# ip link set xfrm1 type xfrm dev lo if_id 2
RTNETLINK answers: File exists
root@dut-vm:~# ip -d link list dev xfrm1
7: xfrm1@lo:  mtu 1500 qdisc noop state DOWN mode DEFAULT group default 
qlen 1000
link/none 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 
maxmtu 1500
xfrm if_id 0x1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 
65536 gso_max_segs 65535

=> if_id 0x1 and no backtrace in dmesg, OK


root@dut-vm:~# ip link add dummy type dummy
root@dut-vm:~# ip link add xfrm1 type xfrm dev dummy if_id 1
root@dut-vm:~# ip l d dummy
root@dut-vm:~# ip -d l ls xfrm1
10: xfrm1@if9:  mtu 1500 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
link/none 3a:90:dc:59:76:c6 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 
maxmtu 1500
xfrm if_id 0x1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 
65536 gso_max_segs 65535
root@dut-vm:~#

=> no refcnt pb, OK

Our internal tests suite is also OK.

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

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

Title:
  xfrm interface: several kernel panic

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1836261

  [Impact]

  Upstream has recently received a number of bug fixes that resolve
  kernel panics, memory leaks, and list handling for virtual xfrm
  interfaces that were debuted in 4.19.

  [Test Case]

  3 of the 5 patches have test cases in their commit message for
  reproducing the fault they address.

  Another patch prevents including a stale name in the log files.

  And the other patch that doesn't have an explicit test case improves list
  handling.

  [Regression Potential]

  This patchset contains a nontrivial amount of changes. However, the
  heavier patches contain test cases that they resolve the regressions
  they were created for. They've been upstream since July and I don't
  see any follow up Fixes commits targeting these. The blast radius is
  "only" the xfrm interface but this is smoke tested and if any
  dependents rely on it for core functionality they might exercise it
  and would possibly notice any issues by now as well.

  Original bug description follows:
  

  There was several problems reported upstream:

  1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823

  2/ xfrm interface: avoid corruption on changelink
  http://patchwork.ozlabs.org/patch/1130240/

  3/ xfrm interface: ifname may be wrong in logs
  http://patchwork.ozlabs.org/patch/1130241/

  4/ xfrm interface: fix list corruption for x-netns
  http://patchwork.ozlabs.org/patch/1130385/

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

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


[Kernel-packages] [Bug 1836261] Re: xfrm interface: several kernel panic

2019-09-16 Thread Nicolas Dichtel
Here are the official commits from Linus tree:

56c5ee1a5823 ("xfrm interface: fix memory leak on creation")
e9e7e85d75f3 ("xfrm interface: avoid corruption on changelink")
e0aaa332e6a9 ("xfrm interface: ifname may be wrong in logs")
c5d1030f2300 ("xfrm interface: fix list corruption for x-netns")
22d6552f827e ("xfrm interface: fix management of phydev")

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=56c5ee1a5823
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9e7e85d75f3
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e0aaa332e6a9
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5d1030f2300
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22d6552f827e

The bugs have been introduced in v4.19 by commit f203b76d7809 ("xfrm: Add 
virtual xfrm interfaces"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f203b76d7809

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

Title:
  xfrm interface: several kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There was several problems reported upstream:

  1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823

  2/ xfrm interface: avoid corruption on changelink
  http://patchwork.ozlabs.org/patch/1130240/

  3/ xfrm interface: ifname may be wrong in logs
  http://patchwork.ozlabs.org/patch/1130241/

  4/ xfrm interface: fix list corruption for x-netns
  http://patchwork.ozlabs.org/patch/1130385/

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

-- 
Mailing list: https://launchpad.net/~kernel-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-09-17 Thread Nicolas Dichtel
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

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 1806392] Re: tun/tap: unable to manage carrier state from userland

2019-02-13 Thread Nicolas Dichtel
Any news for this patch?

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

Title:
  tun/tap: unable to manage carrier state from userland

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
  change").

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=26d31925cd5e

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

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


[Kernel-packages] [Bug 1806392] Re: tun/tap: unable to manage carrier state from userland

2019-03-04 Thread Nicolas Dichtel
Tests are ok on my side, 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/1806392

Title:
  tun/tap: unable to manage carrier state from userland

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
  change").

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=26d31925cd5e

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

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


[Kernel-packages] [Bug 1951606] Re: bonding: arp monitoring is failing with tuntap interfaces

2022-03-21 Thread Nicolas Dichtel
The patch has been merged in ubuntu focal:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=fa748ace5184

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

Title:
  bonding: arp monitoring is failing with tuntap interfaces

Status in linux package in Ubuntu:
  Expired

Bug description:
  [Impact]

  When tuntap interfaces are slaves of a bonding interface, arp
  monitoring is unusable.

  This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
  active backup with arp monitoring"). It will be included in linux
  v5.16.

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

  [Test Case]

  Create a bonding with two tuntap interfaces and arp monitoring
  configured. Before the patch, slave interfaces are flapping
  continuously.

  Example:
  Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
  Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new 
active one
  Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
  Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely 
down, disabling slave
  Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active 
interface!
  Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
  Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new 
active one
  Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
  Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely 
down, disabling slave
  Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active 
interface!
  Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
  Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new 
active one
  Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
  Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
  Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely 
down, disabling slave
  Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new 
active one

  [Regression Potential]

  The patch is trivial, the potential regressions are low.

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


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


[Kernel-packages] [Bug 1988584] [NEW] cgroup: all controller mounted when using 'cgroup_no_v1='

2022-09-02 Thread Nicolas Dichtel
Public bug reported:

[Impact]

When mounting a cgroup hierarchy with disabled controller in cgroup v1,
all available controllers will be attached.
For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then
mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all
enabled controllers will be attached except cpu.

This exists since linux v5.1 and fixed in linux v5.11 with this commit:
61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param()

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637

[Test Case]

root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic 
--initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat 
/proc/cmdline) cgroup_no_v1=net_prio,net_cls"
root@dut-vm:~# systemctl kexec
root@dut-vm:~# mount | grep cgroup
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma)


=> All controllers are associated to /sys/fs/cgroup/net_cls,net_prio.
Note that several reboots may be needed to reproduce the problem (it fails only 
when systemd tries to mount 'net_cls,net_prio' first, but the order is random).

[Regression Potential]

The patch is located in cgroup1_parse_param(), the potential regressions
are low.

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

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

Title:
  cgroup: all controller mounted when using 'cgroup_no_v1='

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  When mounting a cgroup hierarchy with disabled controller in cgroup v1,
  all available controllers will be attached.
  For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then
  mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all
  enabled controllers will be attached except cpu.

  This exists since linux v5.1 and fixed in linux v5.11 with this commit:
  61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param()

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637

  [Test Case]

  root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic 
--initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat 
/proc/cmdline) cgroup_no_v1=net_prio,net_cls"
  root@dut-vm:~# systemctl kexec
  root@dut-vm:~# mount | grep cgroup
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma)

  
  => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio.
  Note that several reboots may be needed to reproduce the problem (it fails 
only when systemd tries to mount 'net_cls,net_prio' first, but the order is 
random).

  [Regression Potential]

  The patch is located in cgroup1_parse_param(), the potential
  regressions are low.

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


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


[Kernel-packages] [Bug 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='

2022-09-02 Thread Nicolas Dichtel
** Summary changed:

- cgroup: all controller mounted when using 'cgroup_no_v1='
+ cgroup: all controllers mounted when using 'cgroup_no_v1='

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

Title:
  cgroup: all controllers mounted when using 'cgroup_no_v1='

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  When mounting a cgroup hierarchy with disabled controller in cgroup v1,
  all available controllers will be attached.
  For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then
  mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all
  enabled controllers will be attached except cpu.

  This exists since linux v5.1 and fixed in linux v5.11 with this commit:
  61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param()

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637

  [Test Case]

  root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic 
--initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat 
/proc/cmdline) cgroup_no_v1=net_prio,net_cls"
  root@dut-vm:~# systemctl kexec
  root@dut-vm:~# mount | grep cgroup
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma)

  
  => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio.
  Note that several reboots may be needed to reproduce the problem (it fails 
only when systemd tries to mount 'net_cls,net_prio' first, but the order is 
random).

  [Regression Potential]

  The patch is located in cgroup1_parse_param(), the potential
  regressions are low.

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


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


[Kernel-packages] [Bug 1988809] [NEW] ip/nexthop: fix default address selection for connected nexthop

2022-09-06 Thread Nicolas Dichtel
Public bug reported:

[Impact]

Packets sent by userland apps are rejected/dropped if the source address
is not specified and the corresponding route is using a connected
nexthop object.

This bug exists since linux v5.3 and has been fixed in v5.19 by the following 
upstream commits:
 - 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
 - cd72e61bad14 ("selftests/net: test nexthop without gw")
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
 - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd

The last commit (v6.0) fixes a regression introduced by the first
commit.

[Test Case]

A detailed test case is explained in the first commit and a self-test is
added in the second commit.

[Regression Potential]

The patch modifies some internal routing states. It has been living in the 
upstream trees for 2 months and the reported regression about icmp redirects 
has been fixed.
The risk of regression should be contained.

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

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

Title:
  ip/nexthop: fix default address selection for connected nexthop

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  Packets sent by userland apps are rejected/dropped if the source
  address is not specified and the corresponding route is using a
  connected nexthop object.

  This bug exists since linux v5.3 and has been fixed in v5.19 by the following 
upstream commits:
   - 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
   - cd72e61bad14 ("selftests/net: test nexthop without gw")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
   - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd

  The last commit (v6.0) fixes a regression introduced by the first
  commit.

  [Test Case]

  A detailed test case is explained in the first commit and a self-test
  is added in the second commit.

  [Regression Potential]

  The patch modifies some internal routing states. It has been living in the 
upstream trees for 2 months and the reported regression about icmp redirects 
has been fixed.
  The risk of regression should be contained.

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


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


[Kernel-packages] [Bug 1967721] Re: Laptop never resuming from standby

2022-05-11 Thread Nicolas Frenay
Adding more hardware: I have the same problem with a Thinkpad T460s on 22.04.
Ubuntu 21.10 worked fine.

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

Title:
  Laptop never resuming from standby

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel,
  after suspending the laptop, it's never possible to wake it up.

  Neither keyboard nor power button work, only way is to long-press to
  force poweroff and restart.

  This did not happen with 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Apr  4 08:30:52 2022
  InstallationDate: Installed on 2022-04-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: LENOVO 20F6CTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2019
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET71W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:
  dmi.product.family: ThinkPad X260
  dmi.product.name: 20F6CTO1WW
  dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space

2021-08-23 Thread Nicolas Dichtel
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  dev_forward_skb: do not scrub skb mark within the same name space

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

Bug description:
  [Impact]

  The ebpf function 'bpf_redirect' reset the mark when used with the flag 
BPF_F_INGRESS.
  There are two main problems with that:
   - it's not consistent between legacy tunnels and ebpf;
   - it's not consistent between ingress and egress.

  In fact, the eBPF program can easily reset the mark, but it cannot
  preserve it.

  This kind of patch was already done in the past, see commit
  963a88b31ddb ("tunnels: harmonize cleanup done on skb on xmit path"),
  commit ea23192e8e57 ("tunnels: harmonize cleanup done on skb on rx
  path") and commit 213dd74aee76 ("skbuff: Do not scrub skb mark within
  the same name space").

  This is fixed upstream with commit ff70202b2d1a ("dev_forward_skb: do
  not scrub skb mark within the same name space").

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

  [Test Case]

  Mark a packet in the POSTROUTING hook, redirect it to another
  interface and display it with a netfilter log rule to check the mark.

  [Regression Potential]

  A user could expect that the mark is reset after a call to
  bpf_redirect(BPF_F_INGRESS), but he could easily reset it in the eBPF
  program himself.

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


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


[Kernel-packages] [Bug 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space

2021-08-23 Thread Nicolas Dichtel
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute

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

Title:
  dev_forward_skb: do not scrub skb mark within the same name space

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

Bug description:
  [Impact]

  The ebpf function 'bpf_redirect' reset the mark when used with the flag 
BPF_F_INGRESS.
  There are two main problems with that:
   - it's not consistent between legacy tunnels and ebpf;
   - it's not consistent between ingress and egress.

  In fact, the eBPF program can easily reset the mark, but it cannot
  preserve it.

  This kind of patch was already done in the past, see commit
  963a88b31ddb ("tunnels: harmonize cleanup done on skb on xmit path"),
  commit ea23192e8e57 ("tunnels: harmonize cleanup done on skb on rx
  path") and commit 213dd74aee76 ("skbuff: Do not scrub skb mark within
  the same name space").

  This is fixed upstream with commit ff70202b2d1a ("dev_forward_skb: do
  not scrub skb mark within the same name space").

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

  [Test Case]

  Mark a packet in the POSTROUTING hook, redirect it to another
  interface and display it with a netfilter log rule to check the mark.

  [Regression Potential]

  A user could expect that the mark is reset after a call to
  bpf_redirect(BPF_F_INGRESS), but he could easily reset it in the eBPF
  program himself.

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


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


[Kernel-packages] [Bug 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space

2021-08-23 Thread Nicolas Dichtel
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  dev_forward_skb: do not scrub skb mark within the same name space

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

Bug description:
  [Impact]

  The ebpf function 'bpf_redirect' reset the mark when used with the flag 
BPF_F_INGRESS.
  There are two main problems with that:
   - it's not consistent between legacy tunnels and ebpf;
   - it's not consistent between ingress and egress.

  In fact, the eBPF program can easily reset the mark, but it cannot
  preserve it.

  This kind of patch was already done in the past, see commit
  963a88b31ddb ("tunnels: harmonize cleanup done on skb on xmit path"),
  commit ea23192e8e57 ("tunnels: harmonize cleanup done on skb on rx
  path") and commit 213dd74aee76 ("skbuff: Do not scrub skb mark within
  the same name space").

  This is fixed upstream with commit ff70202b2d1a ("dev_forward_skb: do
  not scrub skb mark within the same name space").

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

  [Test Case]

  Mark a packet in the POSTROUTING hook, redirect it to another
  interface and display it with a netfilter log rule to check the mark.

  [Regression Potential]

  A user could expect that the mark is reset after a call to
  bpf_redirect(BPF_F_INGRESS), but he could easily reset it in the eBPF
  program himself.

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


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


[Kernel-packages] [Bug 1968591] [NEW] xfrm interface cannot be changed anymore

2022-04-11 Thread Nicolas Dichtel
Public bug reported:

[Impact]

An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In 
fact, the regression has been introduced by this backport:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135

It has been fixed upstream by this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0

[Test Case]

root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1
Error: if_id must be non zero.
root@dut-vm:~# uname -a
Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux
root@dut-vm:~#

[Regression Potential]

The patch is trivial, the potential regressions are low.

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

** Description changed:

  [Impact]
  
  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135
+ 
+ It has been fixed upstream by this commit:
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0
  
  [Test Case]
  
  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
  root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#
  
  [Regression Potential]
  
  The patch is trivial, the potential regressions are low.

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

Title:
  xfrm interface cannot be changed anymore

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135

  It has been fixed upstream by this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0

  [Test Case]

  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
  root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#

  [Regression Potential]

  The patch is trivial, the potential regressions are low.

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


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


[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore

2022-04-20 Thread Nicolas Dichtel
** Description changed:

  [Impact]
  
  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135
  
  It has been fixed upstream by this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0
  
  [Test Case]
  
  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
- root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1
+ root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#
  
  [Regression Potential]
  
  The patch is trivial, the potential regressions are low.

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

Title:
  xfrm interface cannot be changed anymore

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135

  It has been fixed upstream by this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0

  [Test Case]

  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
  root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#

  [Regression Potential]

  The patch is trivial, the potential regressions are low.

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


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


[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore

2022-04-20 Thread Nicolas Dichtel
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  xfrm interface cannot be changed anymore

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135

  It has been fixed upstream by this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0

  [Test Case]

  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
  root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#

  [Regression Potential]

  The patch is trivial, the potential regressions are low.

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


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


[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore

2022-04-20 Thread Nicolas Dichtel
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish

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

Title:
  xfrm interface cannot be changed anymore

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135

  It has been fixed upstream by this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0

  [Test Case]

  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
  root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#

  [Regression Potential]

  The patch is trivial, the potential regressions are low.

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


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


[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop

2022-09-22 Thread Nicolas Dichtel
** Tags added: verification-done-focal verification-done-jammy

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

Title:
  ip/nexthop: fix default address selection for connected nexthop

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Packets sent by userland apps are rejected/dropped if the source
  address is not specified and the corresponding route is using a
  connected nexthop object.

  This bug exists since linux v5.3 and has been fixed in v5.19 by the following 
upstream commits:
   - 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
   - cd72e61bad14 ("selftests/net: test nexthop without gw")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
   - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd

  The last commit (v6.0) fixes a regression introduced by the first
  commit.

  [Test Case]

  A detailed test case is explained in the first commit and a self-test
  is added in the second commit.

  [Regression Potential]

  The patch modifies some internal routing states. It has been living in the 
upstream trees for 2 months and the reported regression about icmp redirects 
has been fixed.
  The risk of regression should be contained.

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


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


[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop

2022-09-22 Thread Nicolas Dichtel
Before the update:
++

root@ubuntu2004:~/linux# uname -a
Linux ubuntu2004 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh
TEST: nexthop: get route with nexthop without gw[FAIL]
TEST: nexthop: ping through nexthop without gw  [FAIL]


With the new focal kernel:
++

root@ubuntu2004:~/linux# uname -a
Linux ubuntu2004 5.4.0-128-generic #144-Ubuntu SMP Tue Sep 20 11:00:04 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh
TEST: nexthop: get route with nexthop without gw[ OK ]
TEST: nexthop: ping through nexthop without gw  [ OK ]


With the new jammy kernel:
++

root@ubuntu2004:~/linux# uname -a
Linux ubuntu2004 5.15.0-50-generic #56-Ubuntu SMP Tue Sep 20 13:23:26 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh
TEST: nexthop: get route with nexthop without gw[ OK ]
TEST: nexthop: ping through nexthop without gw  [ OK ]

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

Title:
  ip/nexthop: fix default address selection for connected nexthop

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Packets sent by userland apps are rejected/dropped if the source
  address is not specified and the corresponding route is using a
  connected nexthop object.

  This bug exists since linux v5.3 and has been fixed in v5.19 by the following 
upstream commits:
   - 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
   - cd72e61bad14 ("selftests/net: test nexthop without gw")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
   - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd

  The last commit (v6.0) fixes a regression introduced by the first
  commit.

  [Test Case]

  A detailed test case is explained in the first commit and a self-test
  is added in the second commit.

  [Regression Potential]

  The patch modifies some internal routing states. It has been living in the 
upstream trees for 2 months and the reported regression about icmp redirects 
has been fixed.
  The risk of regression should be contained.

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


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


[Kernel-packages] [Bug 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='

2022-10-26 Thread Nicolas Dichtel
** Tags added: verification-done-focal

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

Title:
  cgroup: all controllers mounted when using 'cgroup_no_v1='

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  When mounting a cgroup hierarchy with disabled controller in cgroup v1,
  all available controllers will be attached.
  For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then
  mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all
  enabled controllers will be attached except cpu.

  This exists since linux v5.1 and fixed in linux v5.11 with this commit:
  61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param()

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637

  [Test Case]

  root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic 
--initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat 
/proc/cmdline) cgroup_no_v1=net_prio,net_cls"
  root@dut-vm:~# systemctl kexec
  root@dut-vm:~# mount | grep cgroup
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma)

  
  => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio.
  Note that several reboots may be needed to reproduce the problem (it fails 
only when systemd tries to mount 'net_cls,net_prio' first, but the order is 
random).

  [Regression Potential]

  The patch is located in cgroup1_parse_param(), the potential
  regressions are low.

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


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


  1   2   3   4   5   6   >