[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Gabriele Ara
Will do, 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/1818802

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1832369] Re: [Thomson THN14B] Internal speaker does not work

2019-06-11 Thread Hui Wang
It is an i2s codec on your machine, needs ucm to make it work from
pulseaudio or gnome layer.

please refer to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301, it is the
same issue as yours.

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

Title:
  [Thomson THN14B] Internal speaker does not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HI,

  I have a thomson THN14B with audio card rt5651 and bluetooth

  If i list a aplay -l to list all my sound card i get :

   Liste des Périphériques Matériels PLAYBACK 
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  
  I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

  Have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sandra 1154 F pulseaudio
   /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
   /dev/snd/controlC0:  sandra 1154 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 11 17:21:59 2019
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago)
  dmi.bios.date: 01/02/2018
  dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: THN14B
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Thomson
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034

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

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


[Kernel-packages] [Bug 1809704] Re: efivarfs test in ubuntu_kernel_selftest failed on the second run

2019-06-11 Thread Po-Hsu Lin
C/D:
  * dff6d2ae56d0056261e2f7b19c4b96b86b893cd8
X/B:
  * 1f0ea95853bd55a1812f2903b2f776853069f21f
  * dff6d2ae56d0056261e2f7b19c4b96b86b893cd8

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

Title:
  efivarfs test in ubuntu_kernel_selftest failed on the second run

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  New

Bug description:
  This seems to be an issue to the test case, if you run the test suite
  twice, it will fail on the second run.

  The first run will create the test file:
  $ ll 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27
  -rw--- 1 root root 0 Dec 24 07:16 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27

  This is cause the open(O_WRONLY) test in test_create_read failed with 
premission denied on the second run.
  This issue can be reproduced with upstream kernel tree on Xenial as well.

  $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  for TARGET in efivarfs; do \
   make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  for TARGET in efivarfs; do \
   make -C $TARGET run_tests; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  
  running test_create
  
  ./efivarfs.sh: line 48: 
/sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: 
Permission denied
    [PASS]
  
  running test_create_empty
  
  ./efivarfs.sh: line 65: 
/sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27:
 Permission denied
    [PASS]
  
  running test_create_read
  
  open(O_WRONLY): Permission denied
    [FAIL]
  
  running test_delete
  
    [PASS]
  
  running test_zero_size_delete
  
    [PASS]
  
  running test_open_unlink
  
    [PASS]
  
  running test_valid_filenames
  
    [PASS]
  
  running test_invalid_filenames
  
    [PASS]
  selftests: efivarfs.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 24 05:10 seq
   crw-rw 1 root audio 116, 33 Dec 24 05:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [92859.670497] smpboot: CPU 111 is now offline
   [92859.723040] kvm: disabled by bios
   [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d
   [92859.821706] kvm: disabled by bios
  Date: Tue Dec 25 06:30:01 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp.
   Bus 001 Device 002: ID :0001
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFT
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed 
root=UUID=e93f24ed-4e90-4ccb-ba6d-f3b97fe0436f ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-141-generic N/A
   linux-backports-modules-4.4.0-141-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1832290] Re: Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle

2019-06-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  $ uptime
   12:40:44 up 1 day, 10:56,  1 user,  load average: 4.00, 4.02, 4.00

  The load is always reported as higher than 4 even on an idle system.

  Seems to be this upstream:
  https://github.com/raspberrypi/linux/issues/2881

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9
  ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8
  Uname: Linux 5.0.0-1009-raspi2 aarch64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: arm64
  Date: Tue Jun 11 12:33:57 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-raspi2
  UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago)

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

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


[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak

2019-06-11 Thread Daniel van Vugt
** Tags added: bionic

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

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

Title:
  rtlwifi: aggresive memory leak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI) 
the memory usage grows slowly to take all the available RAM when i let the 
computer running over the night (with just top and irssi), and i have to reboot 
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i 
was still flooded with message about pci aer taking lots of disk space in the 
logs, but pci=noaer fixed this problem and i had no memory leak.
  The computer is a common laptop: HP Pavilion.

  ---
  Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly 
disabled to capture the AERs.

  Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
  overnight booted just to console (systemd.unit=multi-user.target).

  The memory leak doesn't affect Windows but owner is going to check
  Windows Event Log for signs of AERs being logged.

  ---

  Original suspect of AER is not guilty.

  This turns out to be a bug in the rtlwifi driver where in some rare
  circumstances it fails to free an sk_buf.

  Reporter has been testing a DKMS build of rtlwfi with the fix applied
  and confirms it solves the issue.

  Upstream has the commit. Can we get this cherry-picked into all
  releases?

  commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
  Author: Larry Finger 
  Date:   Sat Nov 17 20:55:03 2018 -0600

  rtlwifi: Fix leak of skb when processing C2H_BT_INFO
  
  With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
  C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
  the routine returns without freeing that skb, thereby leaking it.
  
  This issue has been discussed at 
https://github.com/lwfinger/rtlwifi_new/issues/401
  and the fix tested there.
  
  Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing 
C2H_BT_INFO")
  Reported-and-tested-by: Francisco Machado Magalhães Neto 

  Cc: Francisco Machado Magalhães Neto 
  Cc: Ping-Ke Shih 
  Cc: Stable  # 4.18+
  Signed-off-by: Larry Finger 
  Signed-off-by: Kalle Valo 

  diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c 
b/drivers/net/wireless/realtek/rtlwifi/base.c
  index f4122c8fdd97..ef9b502ce576 100644
  --- a/drivers/net/wireless/realtek/rtlwifi/base.c
  +++ b/drivers/net/wireless/realtek/rtlwifi/base.c
  @@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct 
sk_buff *skb)
   
  if (rtl_c2h_fast_cmd(hw, skb)) {
  rtl_c2h_content_parsing(hw, skb);
  +   kfree_skb(skb);
  return;
  }

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

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


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

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

apport-collect 1832369

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

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

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

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

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

Title:
  [Thomson THN14B] Internal speaker does not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HI,

  I have a thomson THN14B with audio card rt5651 and bluetooth

  If i list a aplay -l to list all my sound card i get :

   Liste des Périphériques Matériels PLAYBACK 
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  
  I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

  Have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sandra 1154 F pulseaudio
   /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
   /dev/snd/controlC0:  sandra 1154 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 11 17:21:59 2019
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago)
  dmi.bios.date: 01/02/2018
  dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: THN14B
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Thomson
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034

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

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


[Kernel-packages] [Bug 1832419] Re: Xorg freeze

2019-06-11 Thread Daniel van Vugt
Does the freeze only happen when connected to wifi?

I can see a couple of errors from the kernel graphics driver suggesting
the display might freeze:

[  598.213901] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure 
on pipe A ...
[ 3696.507718] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure 
on pipe A ...

Please try logging into "Ubuntu on Wayland" and tell us if that helps.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

** Summary changed:

- Xorg freeze
+ Display freezes

** Summary changed:

- Display freezes
+ Acer Chromebook [banon] display freezes

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

Title:
  Acer Chromebook [banon] display freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Freezes  when connected to wifi.  Running lsof -i and closing some of
  the processes results in black display, need to restart computer.  i
  can use the computer for very short periods when connected to the
  internet, frequently the display freezes requiring restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 11 18:39:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: GOOGLE Banon
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.9
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1832419] Re: Acer Chromebook [banon] display freezes

2019-06-11 Thread Daniel van Vugt
Also, it looks like you have some custom firmware installed:

  dmi.bios.version: MrChromebox-4.9

I wonder if the problem occured before installing that.

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

Title:
  Acer Chromebook [banon] display freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Freezes  when connected to wifi.  Running lsof -i and closing some of
  the processes results in black display, need to restart computer.  i
  can use the computer for very short periods when connected to the
  internet, frequently the display freezes requiring restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 11 18:39:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: GOOGLE Banon
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.9
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1832369] Re: [Thomson THN14B] Internal speaker does not work

2019-06-11 Thread Daniel van Vugt
Can you please try booting Ubuntu 19.04 from USB and tell us if that
fixes the problem?

  http://releases.ubuntu.com/19.04/

Please also note that Ubuntu 18.10 will reach end-of-life next month
(https://wiki.ubuntu.com/Releases).

** Summary changed:

- AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER
+ [Thomson THN14B] Internal speaker does not work

** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)

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

Title:
  [Thomson THN14B] Internal speaker does not work

Status in linux package in Ubuntu:
  New

Bug description:
  HI,

  I have a thomson THN14B with audio card rt5651 and bluetooth

  If i list a aplay -l to list all my sound card i get :

   Liste des Périphériques Matériels PLAYBACK 
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  
  I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

  Have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sandra 1154 F pulseaudio
   /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
   /dev/snd/controlC0:  sandra 1154 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 11 17:21:59 2019
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago)
  dmi.bios.date: 01/02/2018
  dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: THN14B
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Thomson
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034

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

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


[Kernel-packages] [Bug 1832419] [NEW] Xorg freeze

2019-06-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Freezes  when connected to wifi.  Running lsof -i and closing some of
the processes results in black display, need to restart computer.  i can
use the computer for very short periods when connected to the internet,
frequently the display freezes requiring restart.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Tue Jun 11 18:39:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
InstallationDate: Installed on 2019-06-11 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: GOOGLE Banon
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2019
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.9
dmi.board.name: Banon
dmi.board.vendor: GOOGLE
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:
dmi.product.family: Intel_Strago
dmi.product.name: Banon
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1832419
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1832369] [NEW] [Thomson THN14B] Internal speaker does not work

2019-06-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

HI,

I have a thomson THN14B with audio card rt5651 and bluetooth

If i list a aplay -l to list all my sound card i get :

 Liste des Périphériques Matériels PLAYBACK 
carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
  Sous-périphériques: 0/1
  Sous-périphérique #0: subdevice #0
carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0


I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

Have a nice day

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:12.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  sandra 1154 F pulseaudio
 /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
 /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
 /dev/snd/controlC0:  sandra 1154 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jun 11 17:21:59 2019
InstallationDate: Installed on 2019-06-11 (0 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago)
dmi.bios.date: 01/02/2018
dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Cherry Trail CR
dmi.board.vendor: AMI Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: THN14B
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Thomson
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034

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


** Tags: amd64 apport-bug cosmic third-party-packages
-- 
[Thomson THN14B] Internal speaker does not work
https://bugs.launchpad.net/bugs/1832369
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Daniel van Vugt
Filip,

Since you are the original reporter and no longer experience a problem
then I would prefer to keep this bug closed.

---

Gabriele,

If you are experiencing audio problems then please open a new bug by
running:

  ubuntu-bug pulseaudio

so that we can review the details of your affected machine.

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

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

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

2019-06-11 Thread Eric Chai
Hello,
I have the same issue on VirtualBox with MacBook Pro as host. After the recent 
update, the boot stops on all purple screen. However SSH login still works.

The WORKAROUND 1 % 2 don't work. Any more Workarounds?

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

Title:
  intel-microcode on ASUS makes kernel stuck during loading initramfs on
  bionic-updates, bionic-security

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymouth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  - reinstall cryptsetup & update-grub (as suggested in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 )

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

  EDIT:

  Hypothesis:
  Only affects ASUS with i7-8565U Whiskey Lake Intel CPU

  Upstream Bug Report:
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

  WORKAROUND 1: disable intel microcode updates during boot
  From this bug: 
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
  1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
  2/ update-grub

  WORKAROUND 2: downgrade (and hold) intel-microcode to older version from 
bionic/main
  apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2339 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Tags: third-party-packages bionic wayland-session
  Uname: Linux 5.0.0-15-generic x86_64
  UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny 
balíky třetích stran a zkuste to znovu.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions

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


[Kernel-packages] [Bug 1572132] Re: SMBv2+ does not show all files when mounting a windows share

2019-06-11 Thread Felipe Aranda
This issue is gone to me after I updated the kernel to v4.19. I tried
v5.1.9 first, but my WiFi stopped working, so I rolled back a bit. I'm
running Linux Mint 19 that was on kernel 4.15.

A couple of folders were missing on a particular samba share mounted via
fstab. I was able to access them by manually entering their paths.

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

Title:
  SMBv2+ does not show all files when mounting a windows share

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

Bug description:
  When using the SMBv2 Protocol to mount a top level windows share (such
  as C:\) not all files (or directories) are shown that exist  on the
  server side. Exactly 2 files are always missing...

  Steps to reproduce:
  On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top 
level share - a subfolder like C:\data\ seems to work)

  sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
  domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0

  As a result always 2 Files (or directories) are missing in the mounted
  directory of the ubuntu installation.

  Seems to be a kernel bug (source tree: linux/fs/cifs).

  The ubuntu versions I have checked:
  Ubuntu 14.04LTS amd64
  Ubuntu 15.10 amd64
  Ubuntu 16.04 amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.12
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Apr 19 14:50:02 2016
  InstallationDate: Installed on 2016-04-19 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

2019-06-11 Thread Christopher M. Penalver
Johannes, thank you for reporting this and helping make Ubuntu better.
Please answer all of the following:

1) Which firmware file did downloaded precisely? There are a lot of
2.3.X. files listed on the site.

2) When you boot into the BIOS does it state which version of the
Marvell BIOS and firmware is presently installed?

3) To confirm, does using the following kernel boot parameter provide a 
WORKAROUND:
amd_iommu=off

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

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

** Summary changed:

- failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller
+ failed command: WRITE FPDMA QUEUED on ata6 port of Marvell 88EE9230 controller

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

Title:
  failed command: WRITE FPDMA QUEUED on ata6 port of Marvell 88EE9230
  controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating the Marvell 88EE9230 SATA controller firmware to 2.3.xxx from:
  
https://www.station-drivers.com/index.php?option=com_remository=352=select=347=en

  approximately every 2-3 weeks the ata6 port populated with a SAMSUNG MZ7TN512 
throws errors:
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  The other ports don't throw errors.

  However, when the Marvell controller was initially using firmware 1.x.xxx, 
the siutation was even worse. Frequently, links were rested, raid corruption 
happened, and kernel panics occurred. Example from May/2018 (hostname changed, 
same machine):
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
   crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
  InstallationDate: Installed on 2018-03-29 (438 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp3s0 no wireless extensions.

   lo no 

[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

2019-06-11 Thread Christopher M. Penalver
** Tags added: latest-bios-p1.50

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

Title:
  failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata
  controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the Marvell 88EE9230 SATA controller firmware to 2.3.xxx from:
  
https://www.station-drivers.com/index.php?option=com_remository=352=select=347=en

  approximately every 2-3 weeks the ata6 port populated with a SAMSUNG MZ7TN512 
throws errors:
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  The other ports don't throw errors.

  However, when the Marvell controller was initially using firmware 1.x.xxx, 
the siutation was even worse. Frequently, links were rested, raid corruption 
happened, and kernel panics occurred. Example from May/2018 (hostname changed, 
same machine):
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
   crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
  InstallationDate: Installed on 2018-03-29 (438 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp3s0 no wireless extensions.

   lo no wireless extensions.

   enp5s0 no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  PciMultimedia:

  ProcFB:
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  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.18.0-21-generic N/A
   linux-backports-modules-4.18.0-21-generic N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 

[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

2019-06-11 Thread Christopher M. Penalver
** Description changed:

- This is connected to:
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
+ After updating the Marvell 88EE9230 SATA controller firmware to 2.3.xxx from:
+ 
https://www.station-drivers.com/index.php?option=com_remository=352=select=347=en
  
- CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
- 
- My machines throws errors on ata6.00 like these:
- 
+ approximately every 2-3 weeks the ata6 port populated with a SAMSUNG MZ7TN512 
throws errors:
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
  
- ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
- The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.
+ The other ports don't throw errors.
  
- ##
- 
- The Marvell controller itself initially was used with firmware  1.x.xxx
- which caused massive problems with all connected drives. It was common,
- that the kernel rested links, which caused raid corruption, kernel
- panics. Example from May/2018 (hostname changed, same machine)
- 
+ However, when the Marvell controller was initially using firmware 1.x.xxx, 
the siutation was even worse. Frequently, links were rested, raid corruption 
happened, and kernel panics occurred. Example from May/2018 (hostname changed, 
same machine):
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
  
  Which also caused errors within the drives (smartctl -a /dev/sdd):
- 
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.
  
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231
  
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT
+ 
+ ---
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
+  crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
+ InstallationDate: Installed on 2018-03-29 (438 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ IwConfig:
+  enp3s0 no wireless extensions.
+ 
+  lo no wireless extensions.
+ 
+  enp5s0 no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ PciMultimedia:
+ 
+ ProcFB:

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

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

apport-collect 1832388

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

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

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

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

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

** Tags added: 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/1832388

Title:
  [power9] [Cosmic] kernel panic while testing kdump

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  I installed cosmic on power9 (boston) a non-nvme system, installed
  initramfs-tools from -proposed and install kdump-tools. Triggered a
  dump, but I got a kernel panic. This might be a kernel bug/regression.

  ubuntu@tiselius:~$ uname -a 
  Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux
  ubuntu@tiselius:~$ 

  ubuntu@tiselius:~$ apt policy initramfs-tools
  initramfs-tools:
Installed: 0.131ubuntu15.2
Candidate: 0.131ubuntu15.2
Version table:
   *** 0.131ubuntu15.2 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el 
Packages
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ apt policy kdump-tools 
  kdump-tools:
Installed: 1:1.6.5-1ubuntu1~18.10.1
Candidate: 1:1.6.5-1ubuntu1~18.10.1
Version table:
   *** 1:1.6.5-1ubuntu1~18.10.1 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el 
Packages
  100 /var/lib/dpkg/status
   1:1.6.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages
  ubuntu@tiselius:~$ 

  ubuntu@tiselius:~$ sudo kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.18.0-21-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ cat /proc/cmdline 
  root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ dmesg | grep Reser
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] cma: Reserved 6560 MiB at 0x200e6200
  ubuntu@tiselius:~$

  root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq
  root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger

  tiselius login: [  150.167288] cloud-init[4529]: Cloud-init v. 
19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 
19:53:40 +. Up 149.80 seconds.
  [  150.167687] cloud-init[4529]: Cloud-init v. 
19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. 
Datasource DataSourceMAAS 
[http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/].  Up 150.11 seconds
  [  360.313029] kdump-tools[4915]: Stopping kdump-tools:  * unloaded kdump 
kernel
  [  376.552452] kdump-tools[10449]: Starting kdump-tools:  * Creating symlink 
/var/lib/kdump/vmlinuz
  [  376.553743] kdump-tools[10449]:  * Creating symlink 
/var/lib/kdump/initrd.img
  [  376.585085] kdump-tools[10449]: Modified 
cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb 
elfcorehdr=158784K
  [  376.953223] kdump-tools[10449]:  * loaded kdump kernel
  [  398.517900] sysrq: SysRq : Trigger a crash
  [  398.517952] Unable to handle kernel paging request for data at address 
0x
  [  398.518000] Faulting instruction address: 0xc082a3a8
  [  398.518071] Oops: Kernel access of bad area, sig: 11 [#1]
  [  398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV
  [  398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart 
crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler 
uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser 
rdma_cm iw_cm ib_cm ib_core 

[Kernel-packages] [Bug 1832087] Re: Bluetooth not work on INTEL WIRELESS-AC 9260

2019-06-11 Thread Philippe
Yes the problem is present on kernel 5.0.0-15 => bluetooth does not
work, wifi is ok.

kernel 5.0.0-16 => bluetooth works by intermitance, wifi is ok.

kernel 5.2 => nothing works

I dont now is my problem of temperature is in relation with powertop
software (by Intel, to get low cpu temperature and low fan ventilation)
in version 2.9 ?? I start automatically this software on my laptop at
system boot by cron.d fonction.

The last version of powertop is 2.10 but is it not disponible on the
software repertory. If you add powertop v.2.10, I'm ok to test it with
kernels 5.0.0-15 & 5.0-16 and to try to resolve the problem of
overheating.

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

Title:
  Bluetooth not work on INTEL WIRELESS-AC 9260

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump

2019-06-11 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   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/1832388

Title:
  [power9] [Cosmic] kernel panic while testing kdump

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  I installed cosmic on power9 (boston) a non-nvme system, installed
  initramfs-tools from -proposed and install kdump-tools. Triggered a
  dump, but I got a kernel panic. This might be a kernel bug/regression.

  ubuntu@tiselius:~$ uname -a 
  Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux
  ubuntu@tiselius:~$ 

  ubuntu@tiselius:~$ apt policy initramfs-tools
  initramfs-tools:
Installed: 0.131ubuntu15.2
Candidate: 0.131ubuntu15.2
Version table:
   *** 0.131ubuntu15.2 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el 
Packages
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ apt policy kdump-tools 
  kdump-tools:
Installed: 1:1.6.5-1ubuntu1~18.10.1
Candidate: 1:1.6.5-1ubuntu1~18.10.1
Version table:
   *** 1:1.6.5-1ubuntu1~18.10.1 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el 
Packages
  100 /var/lib/dpkg/status
   1:1.6.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages
  ubuntu@tiselius:~$ 

  ubuntu@tiselius:~$ sudo kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.18.0-21-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ cat /proc/cmdline 
  root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ dmesg | grep Reser
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] cma: Reserved 6560 MiB at 0x200e6200
  ubuntu@tiselius:~$

  root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq
  root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger

  tiselius login: [  150.167288] cloud-init[4529]: Cloud-init v. 
19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 
19:53:40 +. Up 149.80 seconds.
  [  150.167687] cloud-init[4529]: Cloud-init v. 
19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. 
Datasource DataSourceMAAS 
[http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/].  Up 150.11 seconds
  [  360.313029] kdump-tools[4915]: Stopping kdump-tools:  * unloaded kdump 
kernel
  [  376.552452] kdump-tools[10449]: Starting kdump-tools:  * Creating symlink 
/var/lib/kdump/vmlinuz
  [  376.553743] kdump-tools[10449]:  * Creating symlink 
/var/lib/kdump/initrd.img
  [  376.585085] kdump-tools[10449]: Modified 
cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb 
elfcorehdr=158784K
  [  376.953223] kdump-tools[10449]:  * loaded kdump kernel
  [  398.517900] sysrq: SysRq : Trigger a crash
  [  398.517952] Unable to handle kernel paging request for data at address 
0x
  [  398.518000] Faulting instruction address: 0xc082a3a8
  [  398.518071] Oops: Kernel access of bad area, sig: 11 [#1]
  [  398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV
  [  398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart 
crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler 
uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser 
rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas 
hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm crc32c_vpmsum i40e aacraid 
drm_panel_orientation_quirks
  [  398.518769] CPU: 0 PID: 10529 Comm: bash Kdump: loaded Not tainted 
4.18.0-21-generic #22-Ubuntu
  [  398.518881] NIP:  

[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Filip Golab
Hey, Im not quite sure how I can reopen it, if you could tell me I would
do it for you. For me this issue had fixed randomly before I upgraded to
19.04 and was not pressent since then.

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

2019-06-11 Thread Steven Tang
Hi Kai-Heng,
  Indeed, it should be <=1, btw, do you want me to follow the kernel dev 
process to send the patch to upstream maintainer, or do you want a patch 
uploaded here?
  I'm unfamiliar with the process, but I think I can find out if there isn't 
any guidelines.

Thanks,

Steven

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

Title:
  kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 
1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can 
no longer boot with the 4.15.0-50 kernel installed with 1804.
  We tried various kernel flags without luck, and installed latest 4.18.0-20 
from HWE and got the same result.
  Unfortunately, no logs are created in /var/logs when the issue happens, and 
we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to 
get a backtrace in a photo.
  The issue happens consistently, i.e. the backtrace looks always the same just 
happens on different cores.
  Attached the boot-info output and the picture taken at the end of the kernel 
loading.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  steventang   2047 F pulseaudio
   /dev/snd/controlC0:  steventang   2047 F pulseaudio
   /dev/snd/controlC1:  steventang   2047 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870
  InstallationDate: Installed on 2019-05-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacPro5,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic 
root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-148-generic N/A
   linux-backports-modules-4.4.0-148-generic  N/A
   linux-firmware 1.173.6
  Tags:  bionic
  Uname: Linux 4.4.0-148-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MP51.88Z.0084.B00.1708080528
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.name: MacPro5,1
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-06-11 Thread Steve Langasek
Other commenters, please confirm what kernel version you are seeing this
behavior with.  If this is not reproducible with either the linux-
generic 3.13 kernel or the linux-lts-xenial 4.4 kernel, then it is not
going to be fixed.

Note also that Ubuntu 14.04 has reached the end of standard support, so
in addition to the other *-lts-* kernels being out of security support
for a long time already, the rest of your system is also out of security
support unless you have ESM enabled.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell 88SE9230 SATA Controller

2019-06-11 Thread Johannes
Christoper, I filed the bug. Anyway I made a mistake. I took the output from 
lshw where scsi@6 was not populated and I took for granted, that ata6 equals 
scsi@6 which isn't the case. Therefore I get the mentioned errors on my boot 
drive. 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383

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

Title:
  amd_iommu conflict with  Marvell 88SE9230 SATA Controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/153

  WORKAROUND: Use kernel boot parameter:
  amd_iommu=off

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.

   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:

  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-06-11 Thread Steve Langasek
@vandebo, your apport information shows the following:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-77-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27

That appears to be the last released version of the linux-lts-utopic
kernel.  That kernel is out of security support and has not been updated
since 2016.  You should upgrade to linux-lts-xenial immediately by
installing the linux-signed-generic-lts-xenial package.

@Lurchman, your comment also shows that you are running
3.19.0-82-generic, which is the last released version of the linux-
lts-*vivid* kernel, which is also out of security support and has not
been updated since February 2017.  You should also install linux-signed-
generic-lts-xenial immediately.

Please report if you are still experiencing issues once you have a
currently-supported version of the kernel on 14.04.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

2019-06-11 Thread Johannes
** Summary changed:

- failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 
88EE9230 sata controller
+ failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

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

Title:
  failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata
  controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-06-11 Thread Eric Desrochers
Sponsored for Cosmic 'd-i'.

The version used "4.18.0-20" is available in cosmic-updates.

rmadison:
 linux-image-4.18.0-20-generic | 4.18.0-20.21 | cosmic-security | 
amd64, arm64, armhf, i386, ppc64el, s390x
 linux-image-4.18.0-20-generic | 4.18.0-20.21 | cosmic-updates  | 
amd64, arm64, armhf, i386, ppc64el, s390x

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Fix Committed
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Fix Committed
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Fix Committed
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
  been tested in detail, and falls back to
  previous behavior if it fails.
  see comment 13.

  [Other Info]

   * This has been verified both by the developer with a simple iSCSI
     iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
     and by an user with system/firmware that supports iBFT for iSCSI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions

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


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

2019-06-11 Thread Johannes
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1832383/+attachment/5270202/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

2019-06-11 Thread Johannes
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1832383/+attachment/5270197/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

2019-06-11 Thread Johannes
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1832383/+attachment/5270201/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller

2019-06-11 Thread Johannes
I made a mistake!
ata6 is populated with an drive. It is an SAMSUNG MZ7TN512 which lshw locates 
at scsi@5:0.0.0 which is ata6

Typical off by one on layer 8 :/

** Attachment added: "tree /sys/bus/scsi/drivers/sd/"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+attachment/5270205/+files/scisi_drives.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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

2019-06-11 Thread Johannes
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1832383/+attachment/5270203/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

2019-06-11 Thread Johannes
apport information

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

** Description changed:

  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
+ 
+ CORRECTION: ata6 is populated! I made a mistake!
  
  My machines throws errors on ata6.00 like these:
  
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
  
  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.
  
  ##
  
  The Marvell controller itself initially was used with firmware  1.x.xxx
  which caused massive problems with all connected drives. It was common,
  that the kernel rested links, which caused raid corruption, kernel
  panics. Example from May/2018 (hostname changed, same machine)
  
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
  
  Which also caused errors within the drives (smartctl -a /dev/sdd):
  
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
-   When the command that caused the error occurred, the device was active or 
idle.
-   
-   After command completion occurred, registers were:
-   ER ST SC SN CL CH DH  
-   -- -- -- -- -- -- --  
-   84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231
- 
-   Commands leading to the command that caused the error were:
-   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-   -- -- -- -- -- -- -- --       
-   25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT  
-   25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
-   25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
-   25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
-   25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT
- --- 
- ProblemType: Bug
- AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jun 11 01:17 seq
-  crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
- AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
- ApportVersion: 2.20.9-0ubuntu7.6
- Architecture: amd64
- ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
- AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
- DistroRelease: Ubuntu 18.04
- EcryptfsInUse: Yes
- HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
- InstallationDate: Installed on 2018-03-29 (438 days ago)
- InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
- IwConfig:
-  enp3s0no wireless extensions.
-  
-  lono wireless extensions.
-  
-  enp5s0no wireless extensions.
- MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
- Package: linux (not installed)
- PciMultimedia:
-  
- ProcFB:
-  
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro
- ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

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

2019-06-11 Thread Johannes
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1832383/+attachment/5270200/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

2019-06-11 Thread Johannes
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1832383/+attachment/5270199/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

2019-06-11 Thread Johannes
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1832383/+attachment/5270196/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

2019-06-11 Thread Johannes
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1832383/+attachment/5270198/+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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  CORRECTION: ata6 is populated! I made a mistake! Please see Post #14

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller

2019-06-11 Thread Johannes
apport information

** Tags added: apport-collected bionic

** Description changed:

  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
  
  My machines throws errors on ata6.00 like these:
  
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
  
  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.
  
  ##
  
  The Marvell controller itself initially was used with firmware  1.x.xxx
  which caused massive problems with all connected drives. It was common,
  that the kernel rested links, which caused raid corruption, kernel
  panics. Example from May/2018 (hostname changed, same machine)
  
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
  
  Which also caused errors within the drives (smartctl -a /dev/sdd):
  
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or 
idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH  
-- -- -- -- -- -- --  
84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231
  
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-- -- -- -- -- -- -- --       
25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT  
25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jun 11 01:17 seq
+  crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
+ InstallationDate: Installed on 2018-03-29 (438 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ IwConfig:
+  enp3s0no wireless extensions.
+  
+  lono wireless extensions.
+  
+  enp5s0no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro
+ ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
+ 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.18.0-21-generic N/A
+  

[Kernel-packages] [Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-06-11 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Title:
  Unable to unmount apparently unused filesystem

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We periodically see an issue where unmounting a ZFS filesystem fails
  with EBUSY, even though there appears to be no one using it.

  # cat /proc/self/mounts | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive zfs 
rw,nosuid,nodev,noexec,relatime,xattr,noacl 0 0

  'lsof' and 'fuser' show no processes using any of the files in the
  problematic filesystem:

  # ls -l 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
  total 221
  -rw-r- 1 500 500  52736 May 22 11:01 1_19_1008904362.dbf
  -rw-r- 1 500 500 541696 May 22 11:03 1_20_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_20_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_19_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
  # lsof | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  #

  The filesystem was shared over NFS, but has since been unshared:

  # showmount -e | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  #

  Since no one appears to be using the filesystem, our expectation is
  that it should be possible to unmount the filesystem. However,
  attempts to unmount the filesystem fail with EBUSY:

  # zfs destroy 
domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.
  cannot unmount 
'/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive': 
umount failed
  # umount 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.

  
  Using bpftrace, we can see that the unmount is failing in 
'propagate_mount_busy()' in the kernel. Using a live kernel debugger, we can 
look at the 'mount' struct for this particular mount and see that the 
'mnt_count' refcount summed across all CPUs is 2. For filesystems that are 
eligible for unmounting, the refcount is 1.

  The only way to work around this issue that we have found is to
  reboot, at which point the filesystem can be unmounted and destroyed.

  
  So far, we have only been able to reproduce this using a workload driven by 
our application. The application mananges ZFS filesystems in groups, and the 
lifecycle of each group looks something like

  - Create and mount a group of filesystems, 1 parent and 4 children:
  /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/datafile
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/external
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/temp
  - Share all 5 filesystems over NFS
  - A client mounts all 5 shares using NFSv3
  - For a few hours, the client does NFS operations on the filesystems and 
the server occasionally takes ZFS snapshots of them
  - Unshare filesystems
  - Unmount filesystems
  - Delete filesystems

  These groups of filesystems are constantly being created and
  destroyed. At any given time, we have ~30k filesystems on the system,
  about 5k of which are shared. On average, one out of ~200-300k
  unmounts fails with this EBUSY error. To create and destroy this many
  filesystems takes us about a week or so.

  Note that we are using ZFS built from https://github.com/delphix/zfs,
  which is essentially master ZFS on Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 20 19:10 seq
   crw-rw 1 root audio 116, 33 May 20 19:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: 

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

2019-06-11 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Unable to unmount apparently unused filesystem

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We periodically see an issue where unmounting a ZFS filesystem fails
  with EBUSY, even though there appears to be no one using it.

  # cat /proc/self/mounts | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive zfs 
rw,nosuid,nodev,noexec,relatime,xattr,noacl 0 0

  'lsof' and 'fuser' show no processes using any of the files in the
  problematic filesystem:

  # ls -l 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
  total 221
  -rw-r- 1 500 500  52736 May 22 11:01 1_19_1008904362.dbf
  -rw-r- 1 500 500 541696 May 22 11:03 1_20_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_20_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_19_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
  # lsof | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  #

  The filesystem was shared over NFS, but has since been unshared:

  # showmount -e | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  #

  Since no one appears to be using the filesystem, our expectation is
  that it should be possible to unmount the filesystem. However,
  attempts to unmount the filesystem fail with EBUSY:

  # zfs destroy 
domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.
  cannot unmount 
'/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive': 
umount failed
  # umount 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.

  
  Using bpftrace, we can see that the unmount is failing in 
'propagate_mount_busy()' in the kernel. Using a live kernel debugger, we can 
look at the 'mount' struct for this particular mount and see that the 
'mnt_count' refcount summed across all CPUs is 2. For filesystems that are 
eligible for unmounting, the refcount is 1.

  The only way to work around this issue that we have found is to
  reboot, at which point the filesystem can be unmounted and destroyed.

  
  So far, we have only been able to reproduce this using a workload driven by 
our application. The application mananges ZFS filesystems in groups, and the 
lifecycle of each group looks something like

  - Create and mount a group of filesystems, 1 parent and 4 children:
  /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/datafile
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/external
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/temp
  - Share all 5 filesystems over NFS
  - A client mounts all 5 shares using NFSv3
  - For a few hours, the client does NFS operations on the filesystems and 
the server occasionally takes ZFS snapshots of them
  - Unshare filesystems
  - Unmount filesystems
  - Delete filesystems

  These groups of filesystems are constantly being created and
  destroyed. At any given time, we have ~30k filesystems on the system,
  about 5k of which are shared. On average, one out of ~200-300k
  unmounts fails with this EBUSY error. To create and destroy this many
  filesystems takes us about a week or so.

  Note that we are using ZFS built from https://github.com/delphix/zfs,
  which is essentially master ZFS on Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 20 19:10 seq
   crw-rw 1 root audio 116, 33 May 20 19:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', 

[Kernel-packages] [Bug 1832384] [NEW] Unable to unmount apparently unused filesystem

2019-06-11 Thread John Gallagher
Public bug reported:

We periodically see an issue where unmounting a ZFS filesystem fails
with EBUSY, even though there appears to be no one using it.

# cat /proc/self/mounts | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive zfs 
rw,nosuid,nodev,noexec,relatime,xattr,noacl 0 0

'lsof' and 'fuser' show no processes using any of the files in the
problematic filesystem:

# ls -l 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
total 221
-rw-r- 1 500 500  52736 May 22 11:01 1_19_1008904362.dbf
-rw-r- 1 500 500 541696 May 22 11:03 1_20_1008904362.dbf
# fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_20_1008904362.dbf
# fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_19_1008904362.dbf
# fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
# lsof | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
#

The filesystem was shared over NFS, but has since been unshared:

# showmount -e | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
#

Since no one appears to be using the filesystem, our expectation is that
it should be possible to unmount the filesystem. However, attempts to
unmount the filesystem fail with EBUSY:

# zfs destroy 
domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.
cannot unmount 
'/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive': 
umount failed
# umount 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.


Using bpftrace, we can see that the unmount is failing in 
'propagate_mount_busy()' in the kernel. Using a live kernel debugger, we can 
look at the 'mount' struct for this particular mount and see that the 
'mnt_count' refcount summed across all CPUs is 2. For filesystems that are 
eligible for unmounting, the refcount is 1.

The only way to work around this issue that we have found is to reboot,
at which point the filesystem can be unmounted and destroyed.


So far, we have only been able to reproduce this using a workload driven by our 
application. The application mananges ZFS filesystems in groups, and the 
lifecycle of each group looks something like

- Create and mount a group of filesystems, 1 parent and 4 children:
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/datafile
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/external
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/temp
- Share all 5 filesystems over NFS
- A client mounts all 5 shares using NFSv3
- For a few hours, the client does NFS operations on the filesystems and 
the server occasionally takes ZFS snapshots of them
- Unshare filesystems
- Unmount filesystems
- Delete filesystems

These groups of filesystems are constantly being created and destroyed.
At any given time, we have ~30k filesystems on the system, about 5k of
which are shared. On average, one out of ~200-300k unmounts fails with
this EBUSY error. To create and destroy this many filesystems takes us
about a week or so.

Note that we are using ZFS built from https://github.com/delphix/zfs,
which is essentially master ZFS on Linux.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May 20 19:10 seq
 crw-rw 1 root audio 116, 33 May 20 19:10 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Jun 11 05:28:21 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb'
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: 

[Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

2019-06-11 Thread Jeremy
Proceed

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

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad has not been used since the purchase of the product.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  5 13:41:22 2019
  InstallationDate: Installed on 2019-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  athena 1232 F pulseaudio
   /dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
   /dev/snd/controlC0:  athena 1232 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 81D2
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-21-generic N/A
   linux-backports-modules-4.18.0-21-generic  N/A
   linux-firmware 1.173.6
  Tags:  bionic
  Uname: Linux 4.18.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/10/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VCN46WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
  dmi.product.family: ideapad 330-15ARR
  dmi.product.name: 81D2
  dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
  dmi.product.version: Lenovo ideapad 330-15ARR
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-06-11 Thread vandebo
I encountered this issue with the nvidia_384 modules.

modprobe: ERROR: could not insert 'nvidia_384': Package not installed

To resolve I did:
apt-get remove --purge shim-signed
apt-get install --reinstall nvidia_384

After those two commands, modprobe succeeded.  I ran the apport command.

** Changed in: shim-signed (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller

2019-06-11 Thread Johannes
Output of lshw -C storage -C disk

Note: There is no drive attached to scsi@6.0.0.0

** Attachment added: "lshw -C storage -C disk"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+attachment/5270183/+files/lshw_storage_disk.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/1832383

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or 
idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH  
-- -- -- -- -- -- --  
84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231
  
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-- -- -- -- -- -- -- --       
25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT  
25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


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

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

apport-collect 1832383

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

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

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

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

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

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example from May/2018 (hostname changed,
  same machine)

  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):

  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or 
idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH  
-- -- -- -- -- -- --  
84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231
  
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-- -- -- -- -- -- -- --       
25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT  
25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

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


[Kernel-packages] [Bug 1832383] [NEW] failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller

2019-06-11 Thread Johannes
Public bug reported:

This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

My machines throws errors on ata6.00 like these:

Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate the 
behaviour. Anyhow, the system is stable.

##

The Marvell controller itself initially was used with firmware  1.x.xxx
which caused massive problems with all connected drives. It was common,
that the kernel rested links, which caused raid corruption, kernel
panics. Example from May/2018 (hostname changed, same machine)

May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

Which also caused errors within the drives (smartctl -a /dev/sdd):

Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
  When the command that caused the error occurred, the device was active or 
idle.
  
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH  
  -- -- -- -- -- -- --  
  84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --       
  25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT  
  25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
  25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
  25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
  25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

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

** Attachment added: "ubuntu-bug linux"
   
https://bugs.launchpad.net/bugs/1832383/+attachment/5270182/+files/apport.linux-image-4.18.0-21-generic.4fpndma9.apport

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

Title:
  failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
  88EE9230 sata controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is connected to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158

  My machines throws errors on ata6.00 like these:

  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
  The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.

  ##

  The Marvell controller itself initially was used with firmware
  1.x.xxx which caused massive problems with all connected drives. It
  was common, that the kernel rested links, which caused raid
  corruption, kernel panics. Example 

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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] UdevLog.txt

2019-06-11 Thread vandebo
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1818134/+attachment/5270179/+files/UdevLog.txt

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] EFITables.txt

2019-06-11 Thread vandebo
apport information

** Attachment added: "EFITables.txt"
   
https://bugs.launchpad.net/bugs/1818134/+attachment/5270171/+files/EFITables.txt

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] Dependencies.txt

2019-06-11 Thread vandebo
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1818134/+attachment/5270170/+files/Dependencies.txt

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


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

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] AudioDevicesInUse.txt

2019-06-11 Thread vandebo
apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1818134/+attachment/5270166/+files/AudioDevicesInUse.txt

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] BootDmesg.txt

2019-06-11 Thread vandebo
apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1818134/+attachment/5270167/+files/BootDmesg.txt

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] AlsaInfo.txt

2019-06-11 Thread vandebo
apport information

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-06-11 Thread vandebo
.proc.sys.kernel.moksbstate.disabled: 0
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
DistroRelease: Ubuntu 14.04
EFIBootMgr:
 
HibernationDevice: RESUME=UUID=07ff7c9f-3b95-46e0-84ee-17a77e7d60e2
InstallationDate: Installed on 2015-10-02 (1347 days ago)
InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150219.1)
IwConfig:
 eth0  no wireless extensions.
 
 docker0   no wireless extensions.
 
 lono wireless extensions.
MachineType: Hewlett-Packard HP Z440 Workstation
Package: shim-signed 1.33.1~14.04.5+13-0ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-77-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-77-generic N/A
 linux-backports-modules-3.16.0-77-generic  N/A
 linux-firmware 1.127.24
RfKill:
 
Tags:  trusty trusty
Uname: Linux 3.16.0-77-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/09/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M60 v01.58
dmi.board.asset.tag: 990496
dmi.board.name: 212B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: unknown
dmi.chassis.asset.tag: 990496
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM60v01.58:bd06/09/2015:svnHewlett-Packard:pnHPZ440Workstation:pvr:rvnHewlett-Packard:rn212B:rvrunknown:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z440 Workstation
dmi.sys.vendor: Hewlett-Packard


** Tags added: apport-collected trusty

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-06-11 Thread Eric Desrochers
** Tags removed: sts-sponsor sts-sponsor-slashd
** Tags added: sts

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Fix Committed
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Fix Committed
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Fix Committed
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
  been tested in detail, and falls back to
  previous behavior if it fails.
  see comment 13.

  [Other Info]

   * This has been verified both by the developer with a simple iSCSI
     iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
     and by an user with system/firmware that supports iBFT for iSCSI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions

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


[Kernel-packages] [Bug 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker

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


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: In Progress => Fix Released

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1830941
- phase: Ready for Release
- phase-changed: Tuesday, 04. June 2019 12:42 UTC
+ phase: Release
+ phase-changed: Tuesday, 11. June 2019 16:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-updates: Pending -- ready to copy

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

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

Title:
  linux-fips: 4.4.0-1011.14 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1830941
  phase: Release
  phase-changed: Tuesday, 11. June 2019 16:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

2019-06-11 Thread Kai-Heng Feng
Write "options ath9k btcoex_enable=1" to some config file under
"/etc/modprobe.conf.d/".

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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


[Kernel-packages] [Bug 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker

2019-06-11 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => In Progress

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

Title:
  linux-fips: 4.4.0-1011.14 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1830941
  phase: Ready for Release
  phase-changed: Tuesday, 04. June 2019 12:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy

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

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


[Kernel-packages] [Bug 1832087] Re: Bluetooth not work on INTEL WIRELESS-AC 9260

2019-06-11 Thread Kai-Heng Feng
iwlwifi crashed.
So does the issue happen on 5.0.0-15?

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

Title:
  Bluetooth not work on INTEL WIRELESS-AC 9260

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-06-11 Thread Eric Desrochers
Sponsored for Bionic 'd-i'.

The new kernel version used "4.18.0-20" (aka HWE) and "4.15.0-50" are
both available in the archive for Bionic in -updates.

$ rmadison linux-image-4.18.0-20-generic
 linux-image-4.18.0-20-generic | 4.18.0-20.21~18.04.1 | bionic-security | 
amd64, arm64, armhf, i386, ppc64el, s390x
 linux-image-4.18.0-20-generic | 4.18.0-20.21~18.04.1 | bionic-updates  | 
amd64, arm64, armhf, i386, ppc64el, s390x

$ rmadison linux-image-4.15.0-50-generic
 linux-image-4.15.0-50-generic | 4.15.0-50.54 | bionic-security | 
amd64, arm64, armhf, i386, ppc64el, s390x
 linux-image-4.15.0-50-generic | 4.15.0-50.54 | bionic-updates  | 
amd64, arm64, armhf, i386, ppc64el, s390x

- Eric

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Fix Committed
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Fix Committed
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Fix Committed
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
  been tested in detail, and falls back to
  previous behavior if it fails.
  see comment 13.

  [Other Info]

   * This has been verified both by the developer with a simple iSCSI
     iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
     and by an user with system/firmware that supports iBFT for iSCSI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions

-- 

[Kernel-packages] [Bug 1832087] Re: Bluetooth not work on INTEL WIRELESS-AC 9260

2019-06-11 Thread Philippe
Sorry for my bad English ... I speak google translate

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

Title:
  Bluetooth not work on INTEL WIRELESS-AC 9260

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1832087] Re: Bluetooth not work on INTEL WIRELESS-AC 9260

2019-06-11 Thread Philippe
The problem persists with the v5.2-rc4 kernel. The bluetooth does not
work and I could not activate the wifi either, it's even worse... It is
even more serious than with the kernel 5.0.0-16 with which bluetooth
works from time to time, but not often. Wifi is all ready ok on kernel
5.0.0-16.

With 5.2-rc4 kernel the apparent management of the CPU temperature is
catastrophic, my software indicated 98 ° C and the fans did not turn on
;(

Unless it's a bug with incorrect temperature display, kernel 5.2 RC4 is
dangerous for my laptop...

Please in the future do not ask me to test a kernel that seems to
potentially damage my laptop.

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

Title:
  Bluetooth not work on INTEL WIRELESS-AC 9260

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-06-11 Thread Dan Streetman
** Tags removed: sts-sponsor-ddstreet
** Tags added: sts-sponsor-slashd

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Fix Committed
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Fix Committed
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Fix Committed
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
  been tested in detail, and falls back to
  previous behavior if it fails.
  see comment 13.

  [Other Info]

   * This has been verified both by the developer with a simple iSCSI
     iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
     and by an user with system/firmware that supports iBFT for iSCSI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions

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


[Kernel-packages] [Bug 1832238] Re: ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-utils dependencies

2019-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-fan - 0.12.13

---
ubuntu-fan (0.12.13) eoan; urgency=medium

  * d/t/control: Fix missing dependencies for autopkgtests (LP:
#1832238)

 -- Rafael David Tinoco   Mon, 10 Jun 2019
15:41:11 +

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-
  utils dependencies

Status in ubuntu-fan package in Ubuntu:
  Fix Released

Bug description:
  
  Whenever running autopkgtests in ubuntu-fan you might hit issues on missing 
dependencies:

  

  Starting fanatic-test
  Remapping container filesystem
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  slave: detected primary route through eth0
  slave: DNS: systemd(250.0.1.1)
  test master: ping test (250.0.1.179) ...
  test slave: ping test (250.0.1.1) ...
  test master: ping test ... PASS
  test master: short data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: ping test ... PASS
  test slave: short data test (250.0.1.179 -> 250.0.1.1) ...
  test master: short data ... PASS
  test master: long data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: short data ... PASS
  test slave: long data test (250.0.1.179 -> 250.0.1.1) ...
  test slave: long data ... PASS
  test master: long data ... PASS
  local lxd test: destroying test container ...
  local lxd test: test complete PASS (master=0 slave=0)
  II: Undefining LXD profile for Fan Bridge...
  de-configuring LXD underlay:127.0.0.0/16 overlay:250.0.0.0/8
  Profile fan-250 deleted
  /tmp/autopkgtest.WLlVT9/build.Imn/src/debian/tests/lxd: line 57: ifconfig: 
command not found
  FAIL: No fan-250 left after disable-lxd
  autopkgtest [14:33:37]: test lxd: ---]
  autopkgtest [14:33:37]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd  FAIL non-zero exit status 1
  autopkgtest [14:33:37]:  summary
  docker   FAIL non-zero exit status 1
  lxd  FAIL non-zero exit status 1
  Exit request sent.

  

  autopkgtest [15:24:09]: test lxd: [---
  /tmp/autopkgtest.7u3mm8/build.s4D/src/debian/tests/lxd: line 3: route: 
command not found
  II: Test LXD...
  master: detected primary route through bridge0
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: systemd-resolve failure!
  local lxd test: prepare master failed!
  FAIL: Error on LXD test
  autopkgtest [15:24:40]: test lxd: ---]
  autopkgtest [15:24:40]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd  FAIL non-zero exit status 1

  

  That happens because tests don't explicitly declare bridge-utils and
  net-tools as its dependency and the building/autopkgtest environment
  might not have them installed by default.

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

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-06-11 Thread Eric Desrochers
Sponsored for Disco 'd-i'. - No-Change rebuild
Will review C/B  'd-i' soon (which involve master kernel change)

- Eric

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Fix Committed
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Fix Committed
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Fix Committed
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
  been tested in detail, and falls back to
  previous behavior if it fails.
  see comment 13.

  [Other Info]

   * This has been verified both by the developer with a simple iSCSI
     iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
     and by an user with system/firmware that supports iBFT for iSCSI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions

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


[Kernel-packages] [Bug 1827162] Re: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

2019-06-11 Thread Manoj Iyer
Based on our analysis and comments from IBM confirming that this is an
expected behavior, I am marking this as wont fix.

** Changed in: ubuntu-power-systems
   Status: Incomplete => Won't Fix

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

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

Title:
  "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

Status in The Ubuntu-power-systems project:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  This bug is created from bug LP #1766201 which reported multiple
  errors in the kernel log on ppc64el. This bug is for tracking the
  issue of the error message "vio vio: uevent: failed to send synthetic
  uevent" (see the original bug, and
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12
  for more info)

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

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


[Kernel-packages] [Bug 1774711] Re: excessive seccomp audit logs

2019-06-11 Thread A. Denton
For the record:

My/our signature line is:
Ubuntu 4.15.0-50.54-generic 4.15.18

Messages look like this:
Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295
uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse"
exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e
syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5

Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295
uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse"
exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e
syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5

Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295
uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse"
exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e
syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5

Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295
uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse"
exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e
syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5

Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295
uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse"
exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e
syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5

...

Precondition is that auditd.service is started.

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

Title:
  excessive seccomp audit logs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello, my audit logs are currently filled with messages from Firefox's
  seccomp filters which looks like this:

  type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3

  $ aa-decode 57656220436F6E74656E74
  Decoded: Web Content
  $ aa-decode 
2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429
  Decoded: /usr/lib/firefox/firefox (deleted)

  Over a recent 48 hour stretch it averaged out to nearly one message
  per second.

  My current audit rules are:
  ## This file is automatically generated from /etc/audit/rules.d
  -D
  -b 8192

  --loginuid-immutable
  -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change
  -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change
  -a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change
  -a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change
  -w /etc/localtime -p wa -k time-change
 

[Kernel-packages] [Bug 1832131] Re: Linux on Raspberry Pi kernels have KVM disabled

2019-06-11 Thread justmaybe
*** This bug is a duplicate of bug 1783961 ***
https://bugs.launchpad.net/bugs/1783961

** This bug has been marked a duplicate of bug 1783961
   CONFIG_KVM is disabled for linux-raspi2 (aarch64)

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

Title:
  Linux on Raspberry Pi kernels have KVM disabled

Status in linux-meta-raspi2 package in Ubuntu:
  New

Bug description:
  Hi,

  Despite the Raspberry Pi hardware being able of using KVM
  virtualization, CONFIG_KVM is disabled on the downstream Ubuntu
  kernels, making the feature not usable.

  (and the generic kernels do not have the DTBs for the 3B+ too, so no
  workaround there)

  The feature is expected to be enabled, and works on some other
  distributions even.

  This was tested on a Raspberry Pi 3 Model B+, on arm64 Ubuntu 18.04.

  Thanks,

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

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


[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
- phase: Testing
- phase-changed: Tuesday, 11. June 2019 10:31 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 11. June 2019 12:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

Title:
  linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Ready for Testing
  phase-changed: Tuesday, 11. June 2019 12:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

2019-06-11 Thread Vikrant Kumar
Any update how to solve this problem

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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


[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Testing
  phase-changed: Tuesday, 11. June 2019 10:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

Title:
  linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Testing
  phase-changed: Tuesday, 11. June 2019 10:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

2019-06-11 Thread Rafael David Tinoco
I just realized that from my previous comment I said:

(2)

There is *no current request* to allow following features to be
reported by EAX_7H_ECX_0_EDX QEMU/KVM right now:

* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
* CPUID.(EAX=7H,ECX=0):EDX[31] SSBD support flag.

But the other bug:

https://bugs.launchpad.net/intel/+bug/1830821

Is about enabling SSBD support:

CPUID.(EAX=7H,ECX=0):EDX[29] (IA32_ARCH_CAPABILITIES feature flag)
...
- (bit 4) SSB_NO: processor not susceptible to spec store bypass

and to enable guest to opt out from SSB (speculative store bypass)


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

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

** Changed in: qemu (Ubuntu)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  This is a bug.

  Test Environment:

  Repro Steps:

  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  :CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

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

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


[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Gabriele Ara
I can confirm that the same problem affects 19.04 too.

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Gabriele Ara
Hey there, same problem here, audio has strange glitches, maybe we could
reopen this issue? Both a collegue and I bought this same laptop and we
are both affected by this issue, even on recent kernel builds.

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


Re: [Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

2019-06-11 Thread Sumneet Kaur Bamrah
Hey Jeremy,
I tried disabling the secure boot.
"EFI variables are not supported on this system"
Is it an error/cause of concern, do I proceed?

On Tue, Jun 11, 2019 at 2:30 AM Jeremy <1831...@bugs.launchpad.net>
wrote:

> Boot into Ubuntu 18.04, in terminal check>  mokutil --sb-state
> as Secure Boot will need to be disabled
> Then do in terminal
> sudo apt install git build-essential dkms
> git clone https://github.com/jeremyb31/mouse-4.18.git
> sudo dkms add ./mouse-4.18
> sudo dkms install mouse/1.0
>
> Reboot
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1831710
>
> Title:
>   Touchpad not working (Lenevo Ideapad 330 series)
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The touch pad has not been used since the purchase of the product.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>   Uname: Linux 4.18.0-21-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Jun  5 13:41:22 2019
>   InstallationDate: Installed on 2019-06-05 (0 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   SourcePackage: linux-signed-hwe
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  athena 1232 F pulseaudio
>/dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
>/dev/snd/controlC0:  athena 1232 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.04
>   InstallationDate: Installed on 2019-06-05 (1 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   MachineType: LENOVO 81D2
>   Package: linux (not installed)
>   ProcFB: 0 amdgpudrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic
> root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>   RelatedPackageVersions:
>linux-restricted-modules-4.18.0-21-generic N/A
>linux-backports-modules-4.18.0-21-generic  N/A
>linux-firmware 1.173.6
>   Tags:  bionic
>   Uname: Linux 4.18.0-21-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 12/10/2018
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 7VCN46WW
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: LNVNB161216
>   dmi.board.vendor: LENOVO
>   dmi.board.version: NO DPK
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Lenovo ideapad 330-15ARR
>   dmi.modalias:
> dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
>   dmi.product.family: ideapad 330-15ARR
>   dmi.product.name: 81D2
>   dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
>   dmi.product.version: Lenovo ideapad 330-15ARR
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+subscriptions
>


-- 
Thanks and Regards,
Sumneet Kaur Bamrah

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

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad has not been used since the purchase of the product.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  5 13:41:22 2019
  InstallationDate: Installed on 2019-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  athena 1232 F pulseaudio
   /dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
   /dev/snd/controlC0:  athena 1232 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-05 (1 

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

2019-06-11 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Testing
  phase-changed: Tuesday, 11. June 2019 10:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   verification-testing: Pending -- Ready

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

Title:
  linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Testing
  phase-changed: Tuesday, 11. June 2019 10:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1828394] Comment bridged from LTC Bugzilla

2019-06-11 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-06-11 06:37 EDT---
IBM Bugzilla status -> closed, Fix Released for requested distro

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

Title:
  [UBUNTU] qdio: clear intparm during shutdown

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

Bug description:
  SRU Justification:

  [Impact]

  * Crash in qeth_irq() with "Unable to handle kernel pointer
  dereference in virtual kernel address space"

  [Fix]

  * 89286320a236d245834075fa13adb0bdd827ecaa 8928632 "s390/qdio: clear
  intparm during shutdown"

  [Test Case]

  * Offline an OSA CHPID with multiple active qeth interfaces.

  [Regression Potential]

  * The regression potential can be considered as very low since it only
  affects the s390x platform

  * and there it only affects the (ccW) qeth (OSA) network devices

  * and again this happens if the CHPID is offlined, which usually
  doesn't happen during regular operation.

  [Other Info]

  * The patch was upstream accepted with kernel 4.17, hence it's already
  part of cosmic, disco and eoan and proven there to work.

  * It needs to be applied to kernel 4.15 to land in 18.04 GA and 16.04.5 HWE.
  _

  Description:   qdio: clear intparm during shutdown
  Symptom:   Crash in qeth_irq() with "Unable to handle kernel pointer
     dereference in virtual kernel address space".
  Problem:   During shutdown, qdio returns its ccw device back to control
     by qeth - but doesn't reset the interrupt parameter on the
     device. If qdio_shutdown() failed to terminate its
     long-running IO on the ccw_device, qeth will subsequently
     do so. In this case the IRQ for the IO completion is
     presented to qeth_irq() with the _old_ interrupt parameter,
     which gets mis-interpreted as a valid qeth_cmd_buffer
     pointer. Dereferencing this bogus pointer in
     qeth_release_buffer() triggers the crash.
  Solution:  When returning the ccw device in qdio_shutdown(), also reset
     its interrupt parameter.
  Reproduction:  Offline an OSA CHPID with multiple active qeth interfaces.

  Component: Kernel
  Upstream-ID:   89286320a236d245834075fa13adb0bdd827ecaa

  Reported:  Ubuntu 18.04

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

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


[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
- phase: Promote to Proposed
- phase-changed: Monday, 10. June 2019 14:08 UTC
+ phase: Testing
+ phase-changed: Tuesday, 11. June 2019 10:31 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Pending -- Ready

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

Title:
  linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Testing
  phase-changed: Tuesday, 11. June 2019 10:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Pending -- Ready

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

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


[Kernel-packages] [Bug 1831371] Re: Touchpad stops working for a period of time

2019-06-11 Thread Rob Aldridge
Hi Kai-Heng,

I tried the new kernel, touchpad still not working.

dmesg attached.

Cheers,
Rob

** Attachment added: "dmesg2_1831371.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831371/+attachment/5270127/+files/dmesg2_1831371.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/1831371

Title:
  Touchpad stops working for a period of time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occasionally the touchpad will stop working for a period of time, the
  mouse cursor disappears but the touchpad buttons still work. The
  keyboard and touchscreen still work normally.

  Eventually after a few minutes the touchpad starts working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob   13195 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  2 22:09:46 2019
  InstallationDate: Installed on 2019-04-24 (38 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Stream x360 Convertible 11-ag1XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8501
  dmi.board.vendor: HP
  dmi.board.version: 05.21
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Stream x360 Convertible 11-ag1XX
  dmi.product.sku: 4RV86PA#ABG
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1832316] Re: shiftfs: allow changing ro/rw for subvolumes

2019-06-11 Thread Christian Brauner
Sent patch:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101305.html

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

Title:
  shiftfs: allow changing ro/rw for subvolumes

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: Stéphane reported regression for btrfs workloads employing shiftfs.
  Unprivileged users can already toggle whether a subvolume will be ro or
  rw. This is broken on current shiftfs as we haven't whitelisted these
  ioctls().

  Fix: To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO,
  BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. All of them should
  be safe for unprivileged users.

  Regression Potential: Limited to shiftfs.

  Test Case: Tested with LXD running shiftfs on top of btrfs and verified
  btrfs subvolumes can be made ro or rw.

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

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


[Kernel-packages] [Bug 1832091] Re: Kernel 5.0.0-16 keyboard malfunction

2019-06-11 Thread Mike Rans
I've set to confirmed as per the Ubuntu Kernel Bot's advice. Let me know
if I need to provide anything else.

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

** Summary changed:

- Kernel 5.0.0-16 keyboard malfunction
+ Kernel 5.0.0-16 USB-2 keyboard on USB-C dock malfunction

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

Title:
  Kernel 5.0.0-16 USB-2 keyboard on USB-C dock malfunction

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading to kernel package linux-image-5.0.0-16-generic causes the
  keyboard which is a USB 2 device connected to a USB C hub on my Dell
  XPS 13 to behave erratically. The previous kernel (linux-
  image-5.0.0-15-generic) doesn't have this problem. (The keyboard is
  fine when plugged directly into the laptop's USB rather than into the
  USB C hub on 5.0.0-16, so it seems to be a USB C problem in 5.0.0-16).

  Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mcarans3298 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=7c0ba900-f99e-46fe-9dd8-7ff287d1c43f
  InstallationDate: Installed on 2017-12-08 (547 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=b6c8e517-c0ed-4ec5-a257-85c0cac387b4 ro deadline quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 0TPN17
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0TPN17:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 082A
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1832316] Re: shiftfs: allow changing ro/rw for subvolumes

2019-06-11 Thread Christian Brauner
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Christian Brauner (cbrauner)

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

Title:
  shiftfs: allow changing ro/rw for subvolumes

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: Stéphane reported regression for btrfs workloads employing shiftfs.
  Unprivileged users can already toggle whether a subvolume will be ro or
  rw. This is broken on current shiftfs as we haven't whitelisted these
  ioctls().

  Fix: To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO,
  BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. All of them should
  be safe for unprivileged users.

  Regression Potential: Limited to shiftfs.

  Test Case: Tested with LXD running shiftfs on top of btrfs and verified
  btrfs subvolumes can be made ro or rw.

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

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


[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

2019-06-11 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1829219
- boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
-   promote-to-proposed: Pending -- packages copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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


[Kernel-packages] [Bug 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

2019-06-11 Thread Dan Streetman
** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => Won't Fix

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

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

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix

Bug description:
  The kernel triggers a BUG when it finds it is in move_freepages() but
  the start and end pfns for the move are in different zones.

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

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


[Kernel-packages] [Bug 1829219] Re: linux: 4.15.0-51.55 -proposed tracker

2019-06-11 Thread Stefan Bader
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
-   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
- derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829194 (linux-aws), bug 1829200 (linux-gcp), bug 1829202 (linux-gke-4.15), bug 
1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), bug 1829210 (linux-oracle), 
bug 1829211 (linux-fips), bug 1829846 (linux)
+ derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829194 (linux-aws), bug 1829200 (linux-gcp), bug 1829202 (linux-gke-4.15), bug 
1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), bug 1829210 (linux-oracle), 
bug 1829211 (linux-fips), bug 1829846 (linux), bug 1832206 (linux-oem)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Security
  phase-changed: Wednesday, 05. June 2019 13:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

Title:
  linux: 4.15.0-51.55 -proposed tracker

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

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

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

  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829194 (linux-aws), bug 1829200 (linux-gcp), bug 1829202 (linux-gke-4.15), bug 
1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), bug 1829210 (linux-oracle), 
bug 1829211 (linux-fips), bug 1829846 (linux), bug 1832206 (linux-oem)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Security
  phase-changed: Wednesday, 05. June 2019 13:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

2019-06-11 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
-   promote-to-proposed: Pending -- packages copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1829219
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
    promote-to-proposed: Pending -- packages copied to Proposed signed:queued

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

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


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

2019-06-11 Thread Stefan Bader
** Tags removed: kernel-release-tracking-bug-live

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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

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

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

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


[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

2019-06-11 Thread Stefan Bader
** Tags added: kernel-sru-derivative-of-1829219

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
-   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ kernel-stable-master-bug: 1829219
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   promote-to-proposed: Pending -- packages copied to Proposed signed:queued

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

Title:
  linux-oem: 4.15.0-1041.46 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1829219
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
    promote-to-proposed: Pending -- packages copied to Proposed signed:queued

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

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


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

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

apport-collect 1832316

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

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

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

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

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

Title:
  shiftfs: allow changing ro/rw for subvolumes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification

  Impact: Stéphane reported regression for btrfs workloads employing shiftfs.
  Unprivileged users can already toggle whether a subvolume will be ro or
  rw. This is broken on current shiftfs as we haven't whitelisted these
  ioctls().

  Fix: To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO,
  BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. All of them should
  be safe for unprivileged users.

  Regression Potential: Limited to shiftfs.

  Test Case: Tested with LXD running shiftfs on top of btrfs and verified
  btrfs subvolumes can be made ro or rw.

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

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


[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

2019-06-11 Thread Christian Ehrhardt 
FYI things resurfaced with monitors of higher resolution.
But it was so bad that I sent them back, so no testbed available atm.

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

Title:
  4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

Status in linux package in Ubuntu:
  Expired
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Expired
Status in linux-hwe source package in Cosmic:
  Invalid

Bug description:
  On 2019-04-03 I updated to the latest linux-image-generic-
  hwe-18.04:amd64 and then I got on a trip where things worked fine at
  first. Back home I realized that the new version 4.18.0-17-generic has
  issues initializing gnome with multiple monitors.

  Steps to reproduce:
  - boot into 4.18.0-17-generic (to be specific Ubuntu 
4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log)
  - start Ubuntu Desktop (gdm works fine at first)
  - Log in

  I have found that this only triggers:
  - with multiple monitors attached ( I have laptop fullHD + 2* external 
fullHD; with just the laptop screen it works)
  - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine 
(=>upgrade-regression?)

  On init of the gnome shell the system crashes with:
  kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A 
FIFO underrun
  [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, 
found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 
d293602a, found 7548bc60)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 
(expected 0x0003, found 0x0001)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in 
base.adjusted_mode.crtc_clock (expected 148500, found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, 
found 54)

  Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to
  consoles anymore. I can only hard reset via 5sec power button.

  I'll attach a full journal of the system and run an apport run on it.
  Let me know if I can help any further.

  So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16
  right away.

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

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


[Kernel-packages] [Bug 1798400]

2019-06-11 Thread Qa-admin-q
[Automated Action] NeedInfo-To-Unconfirmed

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions

-- 
Mailing list: https://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   >