date:20180622

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  watchdog: BUG: soft lockup - CPU#7 stuck for 23s! [kworker/7:1:75]

Status in linux package in Ubuntu:
  Expired

Bug description:
  I had just done a power and BIOS reset to fix a battery problem --
  disconnected the battery and the CMOS battery, and held down buttons
  to reset the power configuration and BIOS. (Not sure I would recommend
  this, but it worked!)

  Booting back into Ubuntu, I had this problem. Things seemed normal,
  but WiFi wouldn't connect, and any interaction with the system (trying
  to change wifi networks, turn off wifi, power down, restart) just
  resulted in no response. I did a Alt-SysRq REISUB and booted back in,
  saw this error report, and here we are.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16 [modified: 
boot/vmlinuz-4.15.0-15-generic]
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1266 F pulseaudio
  Date: Sun Apr 22 14:25:35 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-21 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180420)
  MachineType: Acer Spin SP515-51GN
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=9e351fb3-4ce7-444e-bfe9-07b1c7cd1519 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#7 stuck for 23s! [kworker/7:1:75]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Buzz_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.03
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd10/26/2017:svnAcer:pnSpinSP515-51GN:pvrV1.03:rvnKBL:rnBuzz_KL:rvrV1.03:cvnAcer:ct31:cvrV1.03:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP515-51GN
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1764852] Re: Suspend Fails On Lid Closure (Powers Off)

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Suspend Fails On Lid Closure (Powers Off)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu Bionic Beaver 18.04

  Package files:
   100 /var/lib/dpkg/status
   release a=now
   500 http://ppa.launchpad.net/webupd8team/atom/ubuntu bionic/main i386 
Packages
   release v=18.04,o=LP-PPA-webupd8team-atom,a=bionic,n=bionic,l=Atom text 
editor,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/webupd8team/atom/ubuntu bionic/main amd64 
Packages
   release v=18.04,o=LP-PPA-webupd8team-atom,a=bionic,n=bionic,l=Atom text 
editor,c=main,b=amd64
   origin ppa.launchpad.net
   500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
   release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main,b=amd64
   origin dl.google.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=i386
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=amd64
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=i386
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=amd64
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/restricted i386 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=restricted,b=i386
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=restricted,b=amd64
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=main,b=i386
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=main,b=amd64
   origin us.archive.ubuntu.com

  After a recent update/upgrade the suspend feature on lid close stopped
  working, and now the system powers down.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.16
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 12:59:55 2018
  InstallationDate: Installed on 2018-02-16 (60 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-02-16 (60 days ago)

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

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

[Kernel-packages] [Bug 1765838] Re: BUG: Bad rss-counter state mm:000000002ddfedce idx:2 val:-1

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  BUG: Bad rss-counter state mm:2ddfedce idx:2 val:-1

Status in linux package in Ubuntu:
  Expired

Bug description:
  Booted. Started firefox. A couple seconds later it was back on the
  lock screen. Logged in again and it hung.

  This is a fresh "Erase disk and reinstall" of minimal from yesterdays
  bionic iso

  Ubuntu 4.15.0-15.16-generic 4.15.15

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Fri Apr 20 12:13:12 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-19 (0 days ago)
  InstallationMedia:
   
  MachineType: System manufacturer System Product Name
  OopsText:
   BUG: Bad rss-counter state mm:2ddfedce idx:2 val:-1
   TaskSchedulerFo[35882]: segfault at 5cf3c85816d8 ip 557fa5ed3ed0 sp 
7ff500037420 error 4 in chrome[557fa4a32000+5cd4000]
   traps: wget[35886] general protection ip:7fbe54e7d2ff sp:7ffc7aa235a0 
error:0 in ld-2.27.so[7fbe54e7+27000]
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=d9b05c55-71bb-4f4f-bdfd-43dd79de4c1d ro reboot=pci pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:2ddfedce idx:2 val:-1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1766316] Re: Can't find Nvidia graphics card

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Can't find Nvidia graphics card

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have a nvidia titan installed and when I first added it I could use
  it but now the computer wont even recognize it's there when I run the
  command lspci | grep VGA

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-119-generic 4.4.0-119.143
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 23 11:30 seq
   crw-rw 1 root audio 116, 33 Apr 23 11:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  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:
  Date: Mon Apr 23 11:41:12 2018
  HibernationDevice: RESUME=/dev/mapper/walden--vg-swap_1
  InstallationDate: Installed on 2017-05-02 (355 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge T430
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-119-generic 
root=/dev/mapper/hostname--vg-root ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-119-generic N/A
   linux-backports-modules-4.4.0-119-generic  N/A
   linux-firmware 1.157.16
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 01/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 0KX11M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 17
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd01/09/2017:svnDellInc.:pnPowerEdgeT430:pvr:rvnDellInc.:rn0KX11M:rvrA04:cvnDellInc.:ct17:cvr:
  dmi.product.name: PowerEdge T430
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile

2018-06-22 Thread Bug Watch Updater

Launchpad has imported 16 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=101665.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-06-30T17:13:52+00:00 Kenxeth wrote:

Hello,

I have a Dell XPS 15 9560 with a GTX 1050 Mobile (GP107M) and an Intel
Kabylake CPU.  Using Kernel 4.11.3 on the Arch installer image, whenever
I run 'lspci', it blocks indefinitely and never prints any output.

After running lspci, dmesg contains:

[   54.819264] nouveau :01:00.0: Refused to change power state, currently 
in D3
[   54.879968] nouveau :01:00.0: Refused to change power state, currently 
in D3
[   54.879973] nouveau :01:00.0: Refused to change power state, currently 
in D3
[   54.879974] nouveau :01:00.0: DRM: resuming object tree...

Eventually the scheduler gets cranky about the hung process and starts spewing
[  245.385522] INFO: task lspci:576 blocked for more than 120 seconds.
and a backtrace every 2 minutes.

Blacklisting nouveau makes lspci work.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736/comments/0


On 2017-06-30T18:08:43+00:00 Ilia Mirkin wrote:

I believe including a full dmesg (from boot) would be helpful to show
what may be going wrong.

Note that running with nouveau.runpm=0 will prevent the suspend from
happening. However that will, of course, cause the GPU to remain on. [I
believe it will remain on without nouveau loading as well, but with this
new PCIe PM stuff, I'm not sure anymore.]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736/comments/1


On 2017-07-04T12:22:14+00:00 Peter Wu wrote:

With the "new PCIe PM stuff", if nouveau is not loaded and something
else enabled automatic runtime PM (via powertop, via TLP or manually by
writing "auto" to /sys/bus/pci/devices/.../power/control) for the Nvidia
PCI devices, then indeed the problematic ACPI methods could be
triggered.

Kenneth, can you upload your acpidump?
sudo pacman -S acpidump && sudo acpidump > acpidump.txt

Most likely you are affected by
https://bugzilla.kernel.org/show_bug.cgi?id=156341

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736/comments/2


On 2017-07-10T20:44:39+00:00 Karolherbst-g wrote:

this is because lspci reads the config file, which then triggers a full
GPU wake up, which is a silly thing to do in the first place.

What we need is something like this in the kernel:
https://github.com/karolherbst/linux/commit/cb918e4c926990dfcfce92e1ecd905e0896de605
and then make use of those in userspace, so that we don't need to read
config every time anymore.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736/comments/3


On 2017-11-13T18:39:53+00:00 Etienne URBAH wrote:

I am trying to use 'nouveau' with GP107M [GeForce GTX 1050 Ti Mobile].

With Linux Kernel 4.13.0-16 from Ubuntu 17.10 Artful, 'lspci'
systematically makes immediately 1 CPU freeze.

Therefore, I am testing Linux kernels from http://kernel.ubuntu.com
/~kernel-ppa/mainline

With Linux kernel 4.14.0-rc7, this issue does NOT show up :

$ lspci -nn -v -s 1:0
01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 134
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

With Linux kernel 4.14.0-rc8, 'lspci' systematically makes immediately
the whole computer freeze.

With Linux kernel 4.14.0 (released yesterday), 'lspci' systematically
fails to answer, and makes the whole computer freeze after some time.

So, there is probably a regression.

I have also reported this issue at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736/comments/10


On 2017-11-21T23:21:53+00:00 Etienne URBAH wrote:

With following Linux kernels, 'lspci' systematically fails to answer, and makes 
the whole machine immediately freeze :
-

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-06-22 Thread Emerson Novais Oliveira

I have a same problem too. My system is too slow and so overheated.

My machine:
Ubuntu 18.04
Vostro 3500
Intel Core i5 540m
NVidia GT-310m

Please, help me!

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Confirmed
Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-06-22 Thread Danny Vilca

go several months with the BIOS problem I have a Lenovo Y50-70 try to reinstall
some version of Linux via USB without any success.
my last hope was to try to install Linux from a network since the BIOS allows
to start from an OS network but apparently this option is also not possible, I
was told that having the recovery of OS windows I can start from the bios with
the system recovery.
IF SOMEONE HAD THE ISOS OF THE RECOVERY AND HOST THEM IN ANY SERVER, IT WOULD
BE OF GREAT HELP, or some other suggestion I already ran out of options until I
tried to install ubuntu in my cell phone any contribution helps me. Thank you
whatsapp +51992701807

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-edge source package in Xenial:
Fix Released
Status in linux-oem source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released

Bug description:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

1. Boot into Ubuntu
2. Download
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
3. Install the downloaded package:
$ sudo dpkg -i
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
4. Make sure the kernel is installed without any error. Once installed,
reboot.
5. At grub, choose the newly installed kernel. You can choose the "recovery"
mode.
6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
7. In case your BIOS is not recovered, reboot to the new kernel, then reboot
*once again* to the new kernel, do not enter BIOS settings before the reboot.
After the second reboot, check BIOS.
8. If your BIOS issue remains, download another kernel from
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
and use dpkg to install it, then repeat steps 4 to 6.

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-30
Lenovo G50-70
Lenovo G50-80
Lenovo S20-30
Lenovo U31-70
Lenovo Y50-70
Lenovo Y70-70
Lenovo Yoga Thinkpad (20C0)
Lenovo Yoga 2 11" - 20332
Lenovo Yoga 3 11"
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Toshiba Satellite L70-A-13M
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw, 0xef6015
w25q32dw, 0xef6016
w25q64dw, 0xef6017
w25q128fw, 0xef6018

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo

[Kernel-packages] [Bug 1778282] Re: 'Precision Track Pad' not detected as input source

2018-06-22 Thread Morgan Gallant

Reported on bugzilla.kernel.org/ as per recommendations of apport-
collect. Please close.

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

Title:
  'Precision Track Pad' not detected as input source

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own the Razer Blade 15 (2018) laptop with the Microsoft Precision
  Track pad, and the 4.16 or the 4.17 kernel was not able to detect the
  track pad.

  I do believe that this is affecting all Razer Blade 15 laptops, due to
  the nature of the issue.

  I tried both the 4.16 and 4.17 kernel, both did not detect the track
  pad. However, the 4.17 kernel didn't work with my WiFi card, so went
  back to 4.16.

  I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going 
through it myself, it appears that 'Razer Razer Blade' is sometimes being 
tagged as a mouse ([   326.038] (II) event11 - Razer Razer Blade: is tagged by 
udev as: Mouse). Weird.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.16.0-041600-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1778282] Re: 'Precision Track Pad' not detected as input source

2018-06-22 Thread Morgan Gallant

apport information

** Tags added: apport-collected bionic

** Description changed:

  I own the Razer Blade 15 (2018) laptop with the Microsoft Precision
  Track pad, and the 4.16 or the 4.17 kernel was not able to detect the
  track pad.
  
  I do believe that this is affecting all Razer Blade 15 laptops, due to
  the nature of the issue.
  
  I tried both the 4.16 and 4.17 kernel, both did not detect the track
  pad. However, the 4.17 kernel didn't work with my WiFi card, so went
  back to 4.16.
  
- I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going
- through it myself, it appears that 'Razer Razer Blade' is sometimes
- being tagged as a mouse ([   326.038] (II) event11 - Razer Razer Blade:
- is tagged by udev as: Mouse). Weird.
+ I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going 
through it myself, it appears that 'Razer Razer Blade' is sometimes being 
tagged as a mouse ([   326.038] (II) event11 - Razer Razer Blade: is tagged by 
udev as: Mouse). Weird.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-06-22 (0 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
+ Tags:  bionic
+ Uname: Linux 4.16.0-041600-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  'Precision Track Pad' not detected as input source

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own the Razer Blade 15 (2018) laptop with the Microsoft Precision
  Track pad, and the 4.16 or the 4.17 kernel was not able to detect the
  track pad.

  I do believe that this is affecting all Razer Blade 15 laptops, due to
  the nature of the issue.

  I tried both the 4.16 and 4.17 kernel, both did not detect the track
  pad. However, the 4.17 kernel didn't work with my WiFi card, so went
  back to 4.16.

  I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going 
through it myself, it appears that 'Razer Razer Blade' is sometimes being 
tagged as a mouse ([   326.038] (II) event11 - Razer Razer Blade: is tagged by 
udev as: Mouse). Weird.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.16.0-041600-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

2018-06-22 Thread Carl Reinke

4422d80 does NOT have the bug.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1778286] Re: Backport namespaced fscaps to xenial 4.4

2018-06-22 Thread Seth Forshee

** Summary changed:

- Backport unprivileged fscaps to xenial 4.4
+ Backport namespaced fscaps to xenial 4.4

** Description changed:

  SRU Justification
  
- Impact: Support for using filesystem capabilities was added upstream in
- Linux 4.14. This is a useful feature that allows unprivileged containers
- to set fscaps that are valid only in user namespaces where a specific
- kuid is mapped to root. This allows for e.g. support for Linux distros
- within lxd which make use of filesystem capabilities.
+ Impact: Support for using filesystem capabilities in unprivileged user
+ namespaces was added upstream in Linux 4.14. This is a useful feature
+ that allows unprivileged containers to set fscaps that are valid only in
+ user namespaces where a specific kuid is mapped to root. This allows for
+ e.g. support for Linux distros within lxd which make use of filesystem
+ capabilities.
  
  Fix: Backport upstream commit 8db6c34f1dbc "Introduce v3 namespaced file
  capabilities" and any subsequent fixes to xenial 4.4.
  
  Test Case: Test use of fscaps within a lxd container.
  
  Regression Potential: This has been upstream since 4.14 (and thus is
  present in bionic), and the backport to xenial 4.4 was not difficult, so
  regression potential is low.

** Description changed:

  SRU Justification
  
  Impact: Support for using filesystem capabilities in unprivileged user
  namespaces was added upstream in Linux 4.14. This is a useful feature
  that allows unprivileged containers to set fscaps that are valid only in
  user namespaces where a specific kuid is mapped to root. This allows for
  e.g. support for Linux distros within lxd which make use of filesystem
  capabilities.
  
  Fix: Backport upstream commit 8db6c34f1dbc "Introduce v3 namespaced file
  capabilities" and any subsequent fixes to xenial 4.4.
  
  Test Case: Test use of fscaps within a lxd container.
  
  Regression Potential: This has been upstream since 4.14 (and thus is
- present in bionic), and the backport to xenial 4.4 was not difficult, so
- regression potential is low.
+ present in bionic), and the backport to xenial 4.4 was straightforward,
+ so regression potential is low.

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

Title:
  Backport namespaced fscaps to xenial 4.4

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

Bug description:
  SRU Justification

  Impact: Support for using filesystem capabilities in unprivileged user
  namespaces was added upstream in Linux 4.14. This is a useful feature
  that allows unprivileged containers to set fscaps that are valid only
  in user namespaces where a specific kuid is mapped to root. This
  allows for e.g. support for Linux distros within lxd which make use of
  filesystem capabilities.

  Fix: Backport upstream commit 8db6c34f1dbc "Introduce v3 namespaced
  file capabilities" and any subsequent fixes to xenial 4.4.

  Test Case: Test use of fscaps within a lxd container.

  Regression Potential: This has been upstream since 4.14 (and thus is
  present in bionic), and the backport to xenial 4.4 was
  straightforward, so regression potential is low.

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

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

[Kernel-packages] [Bug 1778286] [NEW] Backport namespaced fscaps to xenial 4.4

2018-06-22 Thread Seth Forshee

Public bug reported:

SRU Justification

Impact: Support for using filesystem capabilities in unprivileged user
namespaces was added upstream in Linux 4.14. This is a useful feature
that allows unprivileged containers to set fscaps that are valid only in
user namespaces where a specific kuid is mapped to root. This allows for
e.g. support for Linux distros within lxd which make use of filesystem
capabilities.

Fix: Backport upstream commit 8db6c34f1dbc "Introduce v3 namespaced file
capabilities" and any subsequent fixes to xenial 4.4.

Test Case: Test use of fscaps within a lxd container.

Regression Potential: This has been upstream since 4.14 (and thus is
present in bionic), and the backport to xenial 4.4 was straightforward,
so regression potential is low.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Fix Released

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Backport namespaced fscaps to xenial 4.4

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

Bug description:
  SRU Justification

  Impact: Support for using filesystem capabilities in unprivileged user
  namespaces was added upstream in Linux 4.14. This is a useful feature
  that allows unprivileged containers to set fscaps that are valid only
  in user namespaces where a specific kuid is mapped to root. This
  allows for e.g. support for Linux distros within lxd which make use of
  filesystem capabilities.

  Fix: Backport upstream commit 8db6c34f1dbc "Introduce v3 namespaced
  file capabilities" and any subsequent fixes to xenial 4.4.

  Test Case: Test use of fscaps within a lxd container.

  Regression Potential: This has been upstream since 4.14 (and thus is
  present in bionic), and the backport to xenial 4.4 was
  straightforward, so regression potential is low.

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

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

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

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 1778282

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

Title:
  'Precision Track Pad' not detected as input source

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own the Razer Blade 15 (2018) laptop with the Microsoft Precision
  Track pad, and the 4.16 or the 4.17 kernel was not able to detect the
  track pad.

  I do believe that this is affecting all Razer Blade 15 laptops, due to
  the nature of the issue.

  I tried both the 4.16 and 4.17 kernel, both did not detect the track
  pad. However, the 4.17 kernel didn't work with my WiFi card, so went
  back to 4.16.

  I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going
  through it myself, it appears that 'Razer Razer Blade' is sometimes
  being tagged as a mouse ([   326.038] (II) event11 - Razer Razer
  Blade: is tagged by udev as: Mouse). Weird.

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

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

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

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 1773232

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

Title:
  Not booting at all times

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I'm running Linux kernel 4.17rc5. (this problem is also with the 4.16
  kernel and 4.15). My computer randomly freezes up after a hour of less
  and sometimes it works for more then a day. But when I check the
  kern.log or syslog it does not show any messages at the time of
  crashing. So is there a way that I can find you why it crashes?

  Also, after a crash it sometimes refuses to boot at all. It will give
  me a black screen. After restarting for 20 or more times it boots up.
  Sometimes my password doesn't work while booting even though I use the
  same (correct) password after the restart.

  I have made a video on this issue here: 
https://www.youtube.com/watch?v=gqH8ySXOUmk=youtu.be
  (the video is a bit out of focus, forgot the manual focus. I have speeded up 
someparts to make it more pleasant to watch)

  I'd like to include some logs but Can't find any relevant logs since
  it does not log during the period of the error. I Have attached a
  picture of my screen that it will sometimes show.

  The moment it did boot up I was using kernel 4.15 (but with that version not 
all of my screens work)
  After the reboot I used the kernel 4.17r5 again and it did work.
  This happens to me a lot and it can take a lot of restarting in order to boot.

  In the video it didnt show the problem that my password would not be
  recognised. However this sometimes happens too.

  One more bug I'm having is that my thrird screen is not being recognised to 
it sets a lower screen resolution. I have solved this with forcing the screen 
resolution to 1080x1920 but then the menu bar is not shown correctly. and I 
have to drag the screen to the right place in the settings in order to have the 
menu's correctly.
  (video: https://youtu.be/Tq-TEeAAIGA) this is what I have to do at startup
  Is there anything more I can do to make this bug report more specific?
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.17.0-041700rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.17.0-041700rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1778282] [NEW] 'Precision Track Pad' not detected as input source

2018-06-22 Thread Morgan Gallant

Public bug reported:

I own the Razer Blade 15 (2018) laptop with the Microsoft Precision
Track pad, and the 4.16 or the 4.17 kernel was not able to detect the
track pad.

I do believe that this is affecting all Razer Blade 15 laptops, due to
the nature of the issue.

I tried both the 4.16 and 4.17 kernel, both did not detect the track
pad. However, the 4.17 kernel didn't work with my WiFi card, so went
back to 4.16.

I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going
through it myself, it appears that 'Razer Razer Blade' is sometimes
being tagged as a mouse ([   326.038] (II) event11 - Razer Razer Blade:
is tagged by udev as: Mouse). Weird.

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


** Tags: trackpad

** Attachment added: "A .zip file containing all necessary debug information 
regarding my machine."
   
https://bugs.launchpad.net/bugs/1778282/+attachment/5155723/+files/Log%20Files.zip

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

Title:
  'Precision Track Pad' not detected as input source

Status in linux package in Ubuntu:
  New

Bug description:
  I own the Razer Blade 15 (2018) laptop with the Microsoft Precision
  Track pad, and the 4.16 or the 4.17 kernel was not able to detect the
  track pad.

  I do believe that this is affecting all Razer Blade 15 laptops, due to
  the nature of the issue.

  I tried both the 4.16 and 4.17 kernel, both did not detect the track
  pad. However, the 4.17 kernel didn't work with my WiFi card, so went
  back to 4.16.

  I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going
  through it myself, it appears that 'Razer Razer Blade' is sometimes
  being tagged as a mouse ([   326.038] (II) event11 - Razer Razer
  Blade: is tagged by udev as: Mouse). Weird.

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

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

[Kernel-packages] [Bug 1773232] Re: Not booting at all times

2018-06-22 Thread steven krol

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

Title:
  Not booting at all times

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I'm running Linux kernel 4.17rc5. (this problem is also with the 4.16
  kernel and 4.15). My computer randomly freezes up after a hour of less
  and sometimes it works for more then a day. But when I check the
  kern.log or syslog it does not show any messages at the time of
  crashing. So is there a way that I can find you why it crashes?

  Also, after a crash it sometimes refuses to boot at all. It will give
  me a black screen. After restarting for 20 or more times it boots up.
  Sometimes my password doesn't work while booting even though I use the
  same (correct) password after the restart.

  I have made a video on this issue here: 
https://www.youtube.com/watch?v=gqH8ySXOUmk=youtu.be
  (the video is a bit out of focus, forgot the manual focus. I have speeded up 
someparts to make it more pleasant to watch)

  I'd like to include some logs but Can't find any relevant logs since
  it does not log during the period of the error. I Have attached a
  picture of my screen that it will sometimes show.

  The moment it did boot up I was using kernel 4.15 (but with that version not 
all of my screens work)
  After the reboot I used the kernel 4.17r5 again and it did work.
  This happens to me a lot and it can take a lot of restarting in order to boot.

  In the video it didnt show the problem that my password would not be
  recognised. However this sometimes happens too.

  One more bug I'm having is that my thrird screen is not being recognised to 
it sets a lower screen resolution. I have solved this with forcing the screen 
resolution to 1080x1920 but then the menu bar is not shown correctly. and I 
have to drag the screen to the right place in the settings in order to have the 
menu's correctly.
  (video: https://youtu.be/Tq-TEeAAIGA) this is what I have to do at startup
  Is there anything more I can do to make this bug report more specific?
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.17.0-041700rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.17.0-041700rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1778265] Re: Bionic update: upstream stable patchset 2018-06-22

2018-06-22 Thread Kamal Mostafa

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:
  
     upstream stable patchset 2018-06-22 (ported from v4.14.39 and v4.16.7)
     from git://git.kernel.org/
+ 
+ drm/amd/display: Disallow enabling CRTC without primary plane with FB
+ drm/amd/display: Fix deadlock when flushing irq
+ drm/i915/audio: set minimum CD clock to twice the BCLK
+ drm/i915/fbdev: Enable late fbdev initial configuration
+ drm/edid: Reset more of the display info
+ module: Fix display of wrong module .text address
+ PCI / PM: Do not clear state_saved in pci_pm_freeze() when smart suspend is 
set
+ ASoC: dmic: Fix clock parenting
+ block: do not use interruptible wait anywhere
+ serial: mvebu-uart: Fix local flags handling on termios update
+ powerpc/eeh: Fix race with driver un/bind
+ arm/arm64: KVM: Add PSCI version selection API
+ tick/sched: Do not mess with an enqueued hrtimer
+ x86/microcode: Do not exit early from __reload_late()
+ x86/microcode/intel: Save microcode patch unconditionally
+ x86/smpboot: Don't use mwait_play_dead() on AMD systems
+ x86/ipc: Fix x32 version of shmid64_ds and msqid64_ds
+ tools/lib/subcmd/pager.c: do not alias select() params
+ objtool, perf: Fix GCC 8 -Wrestrict error
+ drm/i915: Enable display WA#1183 from its correct spot
+ drm/amdgpu: set COMPUTE_PGM_RSRC1 for SGPR/VGPR clearing shaders
+ earlycon: Use a pointer table to fix __earlycon_table stride
+ fpga-manager: altera-ps-spi: preserve nCONFIG state
+ libceph: validate con->state at the top of try_write()
+ libceph: reschedule a tick in finish_hunting()
+ libceph: un-backoff on tick when we have a authenticated session
+ ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
+ crypto: drbg - set freed buffers to NULL
+ KVM: arm/arm64: Close VMID generation race
+ ARM: socfpga_defconfig: Remove QSPI Sector 4K size force
+ ARM: amba: Don't read past the end of sysfs "driver_override" buffer
+ ARM: amba: Fix race condition with driver_override
+ ARM: amba: Make driver_override output consistent with other buses
+ PCI: aardvark: Fix PCIe Max Read Request Size setting
+ PCI: aardvark: Use ISR1 instead of ISR0 interrupt in legacy irq mode
+ PCI: aardvark: Set PIO_ADDR_LS correctly in advk_pcie_rd_conf()
+ PCI: aardvark: Fix logic in advk_pcie_{rd,wr}_conf()
+ ANDROID: binder: prevent transactions into own process.
+ vfio: ccw: process ssch with interrupts disabled
+ bfq-iosched: ensure to clear bic/bfqq pointers when preparing request
+ scsi: sd: Defer spinning up drive while SANITIZE is in progress
+ kobject: don't use WARN for registration failures
+ mtd: rawnand: tango: Fix struct clk memory leak
+ mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
+ mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
+ mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
+ mtd: spi-nor: cadence-quadspi: Fix page fault kernel panic
+ ALSA: hda/realtek - change the location for one of two front mics
+ ALSA: hda/realtek - Update ALC255 depop optimize
+ ALSA: hda/realtek - Add some fixes for ALC233
+ ALSA: hda: Hardening for potential Spectre v1
+ ALSA: seq: oss: Hardening for potential Spectre v1
+ ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
+ ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
+ ALSA: pcm: Return negative delays from SNDRV_PCM_IOCTL_DELAY.
+ ALSA: control: Hardening for potential Spectre v1
+ ALSA: rme9652: Hardening for potential Spectre v1
+ ALSA: hdspm: Hardening for potential Spectre v1
+ ALSA: asihpi: Hardening for potential Spectre v1
+ ALSA: opl3: Hardening for potential Spectre v1
+ ALSA: hda - Skip jack and others for non-existing PCM streams
+ ALSA: dice: fix error path to destroy initialized stream data
+ ALSA: dice: fix OUI for TC group
+ tty: Use __GFP_NOFAIL for tty_ldisc_get()
+ tty: Avoid possible error pointer dereference at tty_ldisc_restore().
+ tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
+ tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
+ tty: Don't call panic() at tty_ldisc_init()
+ drm/virtio: fix vq wait_event condition
+ virtio_console: reset on out of memory
+ virtio_console: move removal code
+ virtio_console: drop custom control queue cleanup
+ virtio_console: free buffers after reset
+ virtio_console: don't tie bufs to a vq
+ virtio: add ability to iterate over vqs
+ ALSA: usb-audio: Skip broken EU on Dell dock USB-audio
+ USB: Increment wakeup count on remote wakeup.
+ usb: core: Add quirk for HP v222w 16GB Mini
+ USB: serial: cp210x: add ID for NI USB serial

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

This change was made by a bot.

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

** Tags added: bionic

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

Title:
  hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a problem that hibernation did not work correctly. After
  running "sudo pm-hibernate" and "sudo systemctl hibernate" commands
  the laptop swithced off, making me think that every thing was good.
  After rebooting it start as it was not hibernated. I did some research
  and tested some solutions but no luck. I did some tests that may help
  resolve this problem that I will attach them here.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3937 F pulseaudio
majdis 4358 F pulseaudio
  Date: Fri Jun 22 21:31:38 2018
  DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook 
PC:F.34
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1527718789
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12
  InstallationDate: Installed on 2018-06-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcCwd: /
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=4d8fb0a7-28ed-4aed-b0d8-9334257e7192 ro 
resume=UUID=/dev/68bfd3fc-e77d-406c-851d-acecfd2f3a12 no_console_suspend 
initcall_debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] hibernate/resume failure 
[non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/28/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1670
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd09/28/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1670:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

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

Title:
  snd_hda_codec_realtek hdaudioC0D0: Unable to sync register

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  I'm running Ubuntu MATE 16.04 running kernel `4.4.0-128-generic`.

  Since applying updates this morning I'm now unable to shut my machine
  down cleanly. If I shut down or restart, the error
  `snd_hda_codec_realtek hdaudioC0D0: unable to sync register` is output
  3 times and the machine doesn't power down. I have to finish the
  shutdown manually by holding the power button.

  Wasn't sure which debug steps to follow for this error, but this is
  the corresponding extract from `/var/log/kern.log`:

  ```
  Jun 22 21:14:04 leonard kernel: [   37.378508] snd_hda_codec_hdmi 
hdaudioC0D2: Unable to sync register 0x2f0d00. -5
  Jun 22 21:14:04 leonard kernel: [   37.378876] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.379239] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.379602] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.405753] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000. -5
  Jun 22 21:14:04 leonard kernel: [   37.405873] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000. -5
  Jun 22 21:14:04 leonard NetworkManager[904]:   [1529698444.9269] 
ModemManager disappeared from bus
  ```

  I made the report using `ubuntu-bug linux` so hopefully this will
  provide the necessary debug info. If I need to post more info, let me
  know what you need.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-128-generic 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1660 F pulseaudio
  CurrentDesktop: MATE
  Date: Fri Jun 22 21:19:43 2018
  HibernationDevice: RESUME=UUID=6bc8046c-253e-4b27-bb37-27d8e02c255d
  InstallationDate: Installed on 2017-01-25 (513 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:1112 Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N24_25BU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic.efi.signed 
root=UUID=f03f5e5c-4a97-462b-8e17-63e66a434dc9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-128-generic N/A
   linux-backports-modules-4.4.0-128-generic  N/A
   linux-firmware 1.157.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N24_25BU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd12/01/2016:svnNotebook:pnN24_25BU:pvrNotApplicable:rvnNotebook:rnN24_25BU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: N24_25BU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1778274] [NEW] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register

2018-06-22 Thread Chris Shaw

Public bug reported:

Hi.

I'm running Ubuntu MATE 16.04 running kernel `4.4.0-128-generic`.

Since applying updates this morning I'm now unable to shut my machine
down cleanly. If I shut down or restart, the error
`snd_hda_codec_realtek hdaudioC0D0: unable to sync register` is output 3
times and the machine doesn't power down. I have to finish the shutdown
manually by holding the power button.

Wasn't sure which debug steps to follow for this error, but this is the
corresponding extract from `/var/log/kern.log`:

```
Jun 22 21:14:04 leonard kernel: [   37.378508] snd_hda_codec_hdmi hdaudioC0D2: 
Unable to sync register 0x2f0d00. -5
Jun 22 21:14:04 leonard kernel: [   37.378876] snd_hda_codec_hdmi hdaudioC0D2: 
HDMI: invalid ELD buf size -1
Jun 22 21:14:04 leonard kernel: [   37.379239] snd_hda_codec_hdmi hdaudioC0D2: 
HDMI: invalid ELD buf size -1
Jun 22 21:14:04 leonard kernel: [   37.379602] snd_hda_codec_hdmi hdaudioC0D2: 
HDMI: invalid ELD buf size -1
Jun 22 21:14:04 leonard kernel: [   37.405753] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000. -5
Jun 22 21:14:04 leonard kernel: [   37.405873] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000. -5
Jun 22 21:14:04 leonard NetworkManager[904]:   [1529698444.9269] 
ModemManager disappeared from bus
```

I made the report using `ubuntu-bug linux` so hopefully this will
provide the necessary debug info. If I need to post more info, let me
know what you need.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-128-generic 4.4.0-128.154
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  chris  1660 F pulseaudio
CurrentDesktop: MATE
Date: Fri Jun 22 21:19:43 2018
HibernationDevice: RESUME=UUID=6bc8046c-253e-4b27-bb37-27d8e02c255d
InstallationDate: Installed on 2017-01-25 (513 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:1112 Acer, Inc 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N24_25BU
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic.efi.signed 
root=UUID=f03f5e5c-4a97-462b-8e17-63e66a434dc9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-128-generic N/A
 linux-backports-modules-4.4.0-128-generic  N/A
 linux-firmware 1.157.19
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Tag 12345
dmi.board.name: N24_25BU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd12/01/2016:svnNotebook:pnN24_25BU:pvrNotApplicable:rvnNotebook:rnN24_25BU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: N24_25BU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug xenial

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

Title:
  snd_hda_codec_realtek hdaudioC0D0: Unable to sync register

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  I'm running Ubuntu MATE 16.04 running kernel `4.4.0-128-generic`.

  Since applying updates this morning I'm now unable to shut my machine
  down cleanly. If I shut down or restart, the error
  `snd_hda_codec_realtek hdaudioC0D0: unable to sync register` is output
  3 times and the machine doesn't power down. I have to finish the
  shutdown manually by holding the power button.

  Wasn't sure which debug steps to follow for this error, but this is
  the corresponding extract from `/var/log/kern.log`:

  ```
  Jun 22 21:14:04 leonard kernel: [   37.378508] snd_hda_codec_hdmi 
hdaudioC0D2: Unable to sync register 0x2f0d00. -5
  Jun 22 21:14:04 leonard kernel: [   37.378876] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.379239] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.379602] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.405753] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000. -5
  Jun 22 21:14:04 leonard kernel: [   37.405873] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000.

[Kernel-packages] [Bug 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

2018-06-22 Thread Jeff Lane

Closing this out, it hasn't been commented on in 3 years, is far older
than that, and tg3 has been pretty heavily tested across many server
makes in the years since.


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

** Changed in: dell-poweredge
   Status: Triaged => 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/1331513

Title:
  14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

Status in The Dell-poweredge project:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  we have a problem with Dell PowerEdge machines, having the Broadcom
  5720 chip. We have this problem on generation 12 systems, across
  different models (R420, R620), with several combinations of bios
  firmwares, lifecycle firmwares, etc... We see this on several versions
  of the linux kernel, ranging from 3.2.x up tot 3.11, with several
  versions of the tg3 driver, including a manually compiled latest
  version (3.133d) loaded in a 3.11. The latest machine, where we can
  reproduce the problem has Ubuntu Precise installed, but we also see
  this behaviour on Debian machines. We run Xen on it, running HVM hosts
  on it. Storage is handled over iSCSI (and it is the iSCSI interface we
  can trigger this bug on in a reproducible way, while we have the
  impression it also happens on other interfaces, but there we don't
  have a solid case where we have e reproducible setup).

  All this info actually points into the direction of the tg3 driver
  and/or hardware below it not handling certain datastreams or data
  patterns correctly, and finally crashing the system. It seems
  unrelated to the version of kernel running, xen-version running,
  amount of VM's running, firmwares and revisions running, etc...

  We have been trying to pinpoint this for over a year now, being unable
  to actually create a scenario where we could reproduce this. As of
  this week, we finally found a specific setup where we could trigger
  the error within a reasonable time.

  The error is triggered by running a certain VM on the Xen stack, and
  inside that VM, importing a mysqldump in a running mysql on that VM.
  The VM has it's traffic on an iSCSI volume, so this effectually
  generates a datastream over the eth1 interface of the machine.  Within
  a short amount of time, the system will crash in 2 steps. We first see
  a timeout on the tg3 driver on the eth1 interface (dmesg output
  section attached). This sometimes repeats two or three times, and
  finally, step 2, the machine freezes and reboots.

  While debugging, we noticed that the bug goes away when we disable sg
  offloading with ethtool.

  If you need any additional info, feel free to ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Jun 18 16:36 seq
   crw-rw---T 1 root audio 116, 33 Jun 18 16:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Jun 18 16:47:27 2014
  HibernationDevice: RESUME=UUID=f3577e02-64e3-4cab-b6e7-f30efa111565
  InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release 
amd64 (20140204)
  MachineType: Dell Inc. PowerEdge R420
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: placeholder root=UUID=bbc71780-90bf-4647-b579-e48d5d8c2bce 
ro vga=0x317
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-19-generic N/A
   linux-backports-modules-3.11.0-19-generic  N/A
   linux-firmware 1.79.12
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-saucy
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.2
  dmi.board.name: 0JD6X3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.2:bd01/20/2014:svnDellInc.:pnPowerEdgeR420:pvr:rvnDellInc.:rn0JD6X3:rvrA00:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R420
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1773232] Re: Not booting at all times

2018-06-22 Thread steven krol

When trying to do: make -j`nproc` deb-pkg

I get the following error

unisteven@Stevens-PC:~/Desktop/Bisect/linux$ sudo make -j`nproc` deb-pkg
[sudo] password for unisteven: 
Makefile:928: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, 
libelf-devel or elfutils-libelf-devel"
  CHK include/config/kernel.release
make clean
  CLEAN   .
  CLEAN   arch/x86/purgatory
  CLEAN   arch/x86/tools
  CLEAN   .tmp_versions
  TAR linux-4.15.0-rc1+.tar.gz
make KBUILD_SRC=
Makefile:928: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, 
libelf-devel or elfutils-libelf-devel"
  CHK include/config/kernel.release
  HOSTCC  scripts/basic/fixdep
  CHK include/generated/uapi/linux/version.h
  HOSTCC  scripts/basic/bin2c
  HOSTCC  arch/x86/tools/relocs_32.o
  HOSTCC  arch/x86/tools/relocs_64.o
  HOSTCC  arch/x86/tools/relocs_common.o
  CHK include/generated/utsrelease.h
  CC  scripts/mod/empty.o
  HOSTCC  scripts/selinux/genheaders/genheaders
  HOSTCC  scripts/selinux/mdp/mdp
  HOSTCC  scripts/mod/mk_elfconfig
  CC  scripts/mod/devicetable-offsets.s
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/conmakehash
  CHK scripts/mod/devicetable-offsets.h
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/recordmcount
  HOSTCC  scripts/sortextable
  HOSTLD  arch/x86/tools/relocs
  HOSTCC  scripts/asn1_compiler
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/sign-file
scripts/sign-file.c:25:10: fatal error: openssl/opensslv.h: No such file or 
directory
 #include 
  ^~~~
compilation terminated.
scripts/Makefile.host:90: recipe for target 'scripts/sign-file' failed
make[3]: *** [scripts/sign-file] Error 1
make[3]: *** Waiting for unfinished jobs
  HOSTCC  scripts/mod/sumversion.o
  CC  arch/x86/purgatory/purgatory.o
  AS  arch/x86/purgatory/stack.o
  AS  arch/x86/purgatory/setup-x86_64.o
  CC  arch/x86/purgatory/sha256.o
  AS  arch/x86/purgatory/entry64.o
  CC  arch/x86/purgatory/string.o
  LD  arch/x86/purgatory/purgatory.ro
  BIN2C   arch/x86/purgatory/kexec-purgatory.c
  CHK include/generated/timeconst.h
  CC  kernel/bounds.s
  HOSTLD  scripts/mod/modpost
Makefile:576: recipe for target 'scripts' failed
make[2]: *** [scripts] Error 2
make[2]: *** Waiting for unfinished jobs
  CHK include/generated/bounds.h
  CC  arch/x86/kernel/asm-offsets.s
  GEN scripts/gdb/linux/constants.py
  CHK include/generated/asm-offsets.h
  CALLscripts/checksyscalls.sh
scripts/package/Makefile:86: recipe for target 'deb-pkg' failed
make[1]: *** [deb-pkg] Error 2
Makefile:1339: recipe for target 'deb-pkg' failed
make: *** [deb-pkg] Error 2

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

Title:
  Not booting at all times

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I'm running Linux kernel 4.17rc5. (this problem is also with the 4.16
  kernel and 4.15). My computer randomly freezes up after a hour of less
  and sometimes it works for more then a day. But when I check the
  kern.log or syslog it does not show any messages at the time of
  crashing. So is there a way that I can find you why it crashes?

  Also, after a crash it sometimes refuses to boot at all. It will give
  me a black screen. After restarting for 20 or more times it boots up.
  Sometimes my password doesn't work while booting even though I use the
  same (correct) password after the restart.

  I have made a video on this issue here: 
https://www.youtube.com/watch?v=gqH8ySXOUmk=youtu.be
  (the video is a bit out of focus, forgot the manual focus. I have speeded up 
someparts to make it more pleasant to watch)

  I'd like to include some logs but Can't find any relevant logs since
  it does not log during the period of the error. I Have attached a
  picture of my screen that it will sometimes show.

  The moment it did boot up I was using kernel 4.15 (but with that version not 
all of my screens work)
  After the reboot I used the kernel 4.17r5 again and it did work.
  This happens to me a lot and it can take a lot of restarting in order to boot.

  In the video it didnt show the problem that my password would not be
  recognised. However this sometimes happens too.

  One more bug I'm having is that my thrird screen is not being recognised to 
it sets a lower screen resolution. I have solved this with forcing the screen 
resolution to 1080x1920 but then the menu bar is not shown correctly. and I 
have to drag the screen to the right place in the settings in order to have the 
menu's correctly.
  (video: https://youtu.be/Tq-TEeAAIGA) this is what I have to do at startup
  Is there anything more I can do to make this bug report more specific?
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64

[Kernel-packages] [Bug 1776819] Re: linux: 3.13.0-153.203 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => 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/1776819

Title:
  linux: 3.13.0-153.203 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: bug 1776820 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776820] Re: linux-lts-trusty: 3.13.0-153.203~precise1 -proposed tracker

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

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

Title:
  linux-lts-trusty: 3.13.0-153.203~precise1 -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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776819
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778270] Re: hibernate/resume failure [non-free: wl]

2018-06-22 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  New

Bug description:
  I have a problem that hibernation did not work correctly. After
  running "sudo pm-hibernate" and "sudo systemctl hibernate" commands
  the laptop swithced off, making me think that every thing was good.
  After rebooting it start as it was not hibernated. I did some research
  and tested some solutions but no luck. I did some tests that may help
  resolve this problem that I will attach them here.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3937 F pulseaudio
majdis 4358 F pulseaudio
  Date: Fri Jun 22 21:31:38 2018
  DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook 
PC:F.34
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1527718789
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12
  InstallationDate: Installed on 2018-06-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcCwd: /
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=4d8fb0a7-28ed-4aed-b0d8-9334257e7192 ro 
resume=UUID=/dev/68bfd3fc-e77d-406c-851d-acecfd2f3a12 no_console_suspend 
initcall_debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] hibernate/resume failure 
[non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/28/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1670
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd09/28/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1670:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1776346] Re: linux-azure: 4.15.0-1014.14~16.04.1 -proposed tracker

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

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

Title:
  linux-azure: 4.15.0-1014.14~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776345] Re: linux-kvm: 4.15.0-1012.12 -proposed tracker

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

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

Title:
  linux-kvm: 4.15.0-1012.12 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776344] Re: linux-gcp: 4.15.0-1010.10 -proposed tracker

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

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

Title:
  linux-gcp: 4.15.0-1010.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778270] Re: hibernate/resume failure [non-free: wl]

last file with results of tests that I did

** Attachment added: "dmesg-core-reboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778270/+attachment/5155683/+files/dmesg-core-reboot.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/1778270

Title:
  hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  New

Bug description:
  I have a problem that hibernation did not work correctly. After
  running "sudo pm-hibernate" and "sudo systemctl hibernate" commands
  the laptop swithced off, making me think that every thing was good.
  After rebooting it start as it was not hibernated. I did some research
  and tested some solutions but no luck. I did some tests that may help
  resolve this problem that I will attach them here.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3937 F pulseaudio
majdis 4358 F pulseaudio
  Date: Fri Jun 22 21:31:38 2018
  DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook 
PC:F.34
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1527718789
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12
  InstallationDate: Installed on 2018-06-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcCwd: /
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=4d8fb0a7-28ed-4aed-b0d8-9334257e7192 ro 
resume=UUID=/dev/68bfd3fc-e77d-406c-851d-acecfd2f3a12 no_console_suspend 
initcall_debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] hibernate/resume failure 
[non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/28/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1670
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd09/28/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1670:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1778270] Re: hibernate/resume failure [non-free: wl]

other file with result of tests

** Attachment added: "dmesg-core-platform.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778270/+attachment/5155682/+files/dmesg-core-platform.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/1778270

Title:
  hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  New

Bug description:
  I have a problem that hibernation did not work correctly. After
  running "sudo pm-hibernate" and "sudo systemctl hibernate" commands
  the laptop swithced off, making me think that every thing was good.
  After rebooting it start as it was not hibernated. I did some research
  and tested some solutions but no luck. I did some tests that may help
  resolve this problem that I will attach them here.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3937 F pulseaudio
majdis 4358 F pulseaudio
  Date: Fri Jun 22 21:31:38 2018
  DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook 
PC:F.34
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1527718789
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12
  InstallationDate: Installed on 2018-06-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcCwd: /
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=4d8fb0a7-28ed-4aed-b0d8-9334257e7192 ro 
resume=UUID=/dev/68bfd3fc-e77d-406c-851d-acecfd2f3a12 no_console_suspend 
initcall_debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] hibernate/resume failure 
[non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/28/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1670
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd09/28/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1670:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1778270] [NEW] hibernate/resume failure [non-free: wl]

Public bug reported:

I have a problem that hibernation did not work correctly. After running
"sudo pm-hibernate" and "sudo systemctl hibernate" commands the laptop
swithced off, making me think that every thing was good. After rebooting
it start as it was not hibernated. I did some research and tested some
solutions but no luck. I did some tests that may help resolve this
problem that I will attach them here.

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: wl
Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm3937 F pulseaudio
  majdis 4358 F pulseaudio
Date: Fri Jun 22 21:31:38 2018
DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook 
PC:F.34
ExecutablePath: /usr/share/apport/apportcheckresume
ExecutableTimestamp: 1527718789
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12
InstallationDate: Installed on 2018-06-21 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterpreterPath: /usr/bin/python3.6
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcCwd: /
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=4d8fb0a7-28ed-4aed-b0d8-9334257e7192 ro 
resume=UUID=/dev/68bfd3fc-e77d-406c-851d-acecfd2f3a12 no_console_suspend 
initcall_debug
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] hibernate/resume failure 
[non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 09/28/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.34
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1670
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd09/28/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1670:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 05931120461620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops hibernate resume

** Attachment added: "lsmod.output.txt"
   
https://bugs.launchpad.net/bugs/1778270/+attachment/5155662/+files/lsmod.output.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/1778270

Title:
  hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  New

Bug description:
  I have a problem that hibernation did not work correctly. After
  running "sudo pm-hibernate" and "sudo systemctl hibernate" commands
  the laptop swithced off, making me think that every thing was good.
  After rebooting it start as it was not hibernated. I did some research
  and tested some solutions but no luck. I did some tests that may help
  resolve this problem that I will attach them here.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3937 F pulseaudio
majdis 4358 F pulseaudio
  Date: Fri Jun 22 21:31:38 2018
  DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook 
PC:F.34
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1527718789
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12
  InstallationDate: Installed on 2018-06-21 (0 days

[Kernel-packages] [Bug 1778270] Re: hibernate/resume failure [non-free: wl]

this file has a result of some tests that I did

** Attachment added: "dmesg-devices-platform.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778270/+attachment/5155681/+files/dmesg-devices-platform.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/1778270

Title:
  hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  New

Bug description:
  I have a problem that hibernation did not work correctly. After
  running "sudo pm-hibernate" and "sudo systemctl hibernate" commands
  the laptop swithced off, making me think that every thing was good.
  After rebooting it start as it was not hibernated. I did some research
  and tested some solutions but no luck. I did some tests that may help
  resolve this problem that I will attach them here.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3937 F pulseaudio
majdis 4358 F pulseaudio
  Date: Fri Jun 22 21:31:38 2018
  DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook 
PC:F.34
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1527718789
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12
  InstallationDate: Installed on 2018-06-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcCwd: /
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=4d8fb0a7-28ed-4aed-b0d8-9334257e7192 ro 
resume=UUID=/dev/68bfd3fc-e77d-406c-851d-acecfd2f3a12 no_console_suspend 
initcall_debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] hibernate/resume failure 
[non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/28/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1670
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd09/28/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1670:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1776340] Re: linux-oem: 4.15.0-1009.12 -proposed tracker

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

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

Title:
  linux-oem: 4.15.0-1009.12 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776341] Re: linux-aws: 4.15.0-1011.11 -proposed tracker

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

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

Title:
  linux-aws: 4.15.0-1011.11 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776342] Re: linux-azure: 4.15.0-1014.14 -proposed tracker

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

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

Title:
  linux-azure: 4.15.0-1014.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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 stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776338] Re: linux: 4.15.0-24.26 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => 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/1776338

Title:
  linux: 4.15.0-24.26 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1776346 (linux-azure), bug 1776347 (linux-azure-edge), bug 
1776348 (linux-hwe-edge)
  derivatives: bug 1776339 (linux-raspi2), bug 1776340 (linux-oem), bug 1776341 
(linux-aws), bug 1776342 (linux-azure), bug 1776344 (linux-gcp), bug 1776345 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778265] [NEW] Bionic update: upstream stable patchset 2018-06-22

2018-06-22 Thread Kamal Mostafa

Public bug reported:

SRU Justification

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

   upstream stable patchset 2018-06-22 (ported from v4.14.39 and v4.16.7)
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
- 
-upstream stable patchset 2018-06-22
-from git://git.kernel.org/
+    upstream stable patchset 2018-06-22 (ported from v4.14.39 and v4.16.7)
+    from git://git.kernel.org/

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

Title:
  Bionic update: upstream stable patchset 2018-06-22

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2018-06-22 (ported from v4.14.39 and v4.16.7)
     from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1776337] Re: linux-oem: 4.13.0-1031.35 -proposed tracker

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

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

Title:
  linux-oem: 4.13.0-1031.35 -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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776333
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2018-06-22 Thread jmkeller

Same issue started post 18.04 upgrade.   AMD FX at 4.7 GHz goes into
thermal shutdown about a minute after getting booted up and into the
desktop.   I installed cpuefreqd and set the policy to power save high
(limiting the frequency scaling to about 50%) in order to keep the CPU
temp below the thermal cut off limit.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias:

[Kernel-packages] [Bug 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker

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

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

Title:
  linux-gcp: 4.13.0-1020.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff 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:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776333
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778261] [NEW] large KVM instances run out of IRQ routes

2018-06-22 Thread Andy Whitcroft

Public bug reported:

When starting large KVM instances with large numbers of attached devices
may run KVM out of IRQ routes.  Up the system limit to allow these
configurations to boot.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  large KVM instances run out of IRQ routes

Status in linux package in Ubuntu:
  In Progress

Bug description:
  When starting large KVM instances with large numbers of attached
  devices may run KVM out of IRQ routes.  Up the system limit to allow
  these configurations to boot.

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

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

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

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 1756700

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

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

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

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

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

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

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

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

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

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

[Kernel-packages] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

2018-06-22 Thread Kai-Heng Feng

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

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

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

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

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

[Kernel-packages] [Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => 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/1776333

Title:
  linux: 4.13.0-46.51 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

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

  backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 
(linux-oem)
  derivatives: bug 1776334 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-06-22 Thread whl2

Hi Kai-Feng,

Thank you for looking into this. I've done the steps you've described,
however I'm not sure everything worked as it should:

# powertop --auto-tune
modprobe cpufreq_stats failedLoaded 0 prior measurements
Cannot load from file /var/cache/powertop/saved_parameters.powertop
File will be loaded after taking minimum number of measurement(s) with battery 
only 
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask 7
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask 7
Devfreq not enabled
glob returned GLOB_ABORTED
Cannot load from file /var/cache/powertop/saved_parameters.powertop
File will be loaded after taking minimum number of measurement(s) with battery 
only 
Leaving PowerTOP


The kernel module is loaded

# lsmod|grep r8168
r8168 524288  0

kernel parameter is present

# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor pcie_aspm=force vt.handoff=1


Output of powertop without options attached. 


** Attachment added: "powertop.output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+attachment/5155647/+files/powertop.output

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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

[Kernel-packages] [Bug 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic

2018-06-22 Thread Deon Rodden

I am running Ubuntu 16.04 on a Dell Precision 5510 Laptop and it has
integrated bluetooth. Whenever I toggle on Bluetooth I get the same
error:

Jun 22 10:45:19 drhorrible colord-sane: [bjnp] udp_command: ERROR - no data 
received
Jun 22 10:45:19 drhorrible colord-sane: [bjnp] bjnp_init_device_structure: 
Cannot read mac address, skipping this scanner
Jun 22 10:45:26 drhorrible systemd[1]: Starting Load/Save RF Kill Switch 
Status...
Jun 22 10:45:26 drhorrible systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 22 10:45:26 drhorrible kernel: [ 5841.017815] usb 1-4: new full-speed USB 
device number 11 using xhci_hcd
Jun 22 10:45:26 drhorrible kernel: [ 5841.159093] usb 1-4: New USB device 
found, idVendor=8087, idProduct=0a2b
Jun 22 10:45:26 drhorrible kernel: [ 5841.159098] usb 1-4: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Jun 22 10:45:26 drhorrible kernel: [ 5841.160861] Bluetooth: hci0: Bootloader 
revision 0.0 build 2 week 52 2014
Jun 22 10:45:26 drhorrible kernel: [ 5841.167883] Bluetooth: hci0: Device 
revision is 5
Jun 22 10:45:26 drhorrible kernel: [ 5841.167886] Bluetooth: hci0: Secure boot 
is enabled
Jun 22 10:45:26 drhorrible kernel: [ 5841.167888] Bluetooth: hci0: OTP lock is 
enabled
Jun 22 10:45:26 drhorrible kernel: [ 5841.167889] Bluetooth: hci0: API lock is 
enabled
Jun 22 10:45:26 drhorrible kernel: [ 5841.167891] Bluetooth: hci0: Debug lock 
is disabled
Jun 22 10:45:26 drhorrible kernel: [ 5841.167894] Bluetooth: hci0: Minimum 
firmware build 1 week 10 2014
Jun 22 10:45:26 drhorrible kernel: [ 5841.168347] Bluetooth: hci0: Found device 
firmware: intel/ibt-11-5.sfi
Jun 22 10:45:28 drhorrible kernel: [ 5842.776460] Bluetooth: hci0: Waiting for 
firmware download to complete
Jun 22 10:45:28 drhorrible kernel: [ 5842.776820] Bluetooth: hci0: Firmware 
loaded in 1578932 usecs
Jun 22 10:45:28 drhorrible kernel: [ 5842.776952] Bluetooth: hci0: Waiting for 
device to boot
Jun 22 10:45:28 drhorrible kernel: [ 5842.788897] Bluetooth: hci0: Device 
booted in 11731 usecs
Jun 22 10:45:28 drhorrible kernel: [ 5842.788960] Bluetooth: hci0: Found Intel 
DDC parameters: intel/ibt-11-5.ddc
Jun 22 10:45:28 drhorrible kernel: [ 5842.792962] Bluetooth: hci0: Applying 
Intel DDC parameters completed
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Failed to obtain handles for 
"Service Changed" characteristic
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Not enough free handles to 
register service
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Error adding Link Loss service
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Not enough free handles to 
register service
Jun 22 10:45:28 drhorrible bluetoothd[16172]: message repeated 2 times: [ Not 
enough free handles to register service]
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Current Time Service could not be 
registered
Jun 22 10:45:28 drhorrible bluetoothd[16172]: gatt-time-server: Input/output 
error (5)
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Not enough free handles to 
register service
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Not enough free handles to 
register service
Jun 22 10:45:28 drhorrible systemd[1]: Reached target Bluetooth.
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Sap driver initialization failed.
Jun 22 10:45:28 drhorrible bluetoothd[16172]: sap-server: Operation not 
permitted (1)
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Failed to get connections: Not 
Powered (0x0f)
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Endpoint registered: sender=:1.57 
path=/MediaEndpoint/A2DPSource
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Endpoint registered: sender=:1.57 
path=/MediaEndpoint/A2DPSink
Jun 22 10:45:28 drhorrible bluetoothd[16172]: Failed to set mode: Blocked 
through rfkill (0x12)

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

Title:
  bluetoothd[650]: Failed to obtain handles for "Service Changed"
  characteristic

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain 
handles for "Service Changed" characteristic
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link 
Loss service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service 
could not be registered
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: 
Input/output error (5)
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register

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

Bionic SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093495.html

I should have a Xenial test kernel available for testing shortly.  It
requires some backporting of the patches.

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776927] Re: RTNL assertion failure on ipvlan

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093489.html

** Description changed:

- Running up two containers using ipvlan with IPv6 autoconf active
- triggers an assertion failure in the kernel (cloud image running on
- Brightbox)
+ == SRU Justification ==
+ Running up two containers using ipvlan with IPv6 autoconf active triggers
+ an assertion failure in the kernel (cloud image running on Brightbox).
+ This is a regression caused by commit e9997c2938b2.
+ 
+ This regression is fixed by commit 8230819494b3 but also requires commit 
94333fac44d1
+ as a prereq.
+ 
+ == Fixes ==
+ 94333fac44d1 ("ipvlan: drop ipv6 dependency")
+ 8230819494b3 ("ipvlan: use per device spinlock to protect addrs list updates")
+ 
+ == Regression Potential ==
+ Low.  Fixes a current regression.  The fix was also sent to stable, so
+ it has had additional upstream review.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
+ Running up two containers using ipvlan with IPv6 autoconf active triggers an 
assertion failure in the kernel (cloud image running on Brightbox)
  
  Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at 
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c (110)
  Jun 14 15:16:37 srv-x3w2q kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 
4.15.0-23-generic #25-Ubuntu
  Jun 14 15:16:37 srv-x3w2q kernel: Hardware name: Red Hat KVM, BIOS 
1.10.2-3.el7_4.1 04/01/2014
  Jun 14 15:16:37 srv-x3w2q kernel: Call Trace:
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel:  dump_stack+0x63/0x8b
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr_busy+0x96/0xa0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr6_event+0x77/0xd0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  notifier_call_chain+0x4c/0x70
  Jun 14 15:16:37 srv-x3w2q kernel:  atomic_notifier_call_chain+0x1a/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  inet6addr_notifier_call_chain+0x1b/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_add_addr+0x43d/0x5c0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_route+0xd7/0x120
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv+0x26c/0x740
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_rcv+0xe9/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  icmpv6_rcv+0x408/0x540
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input_finish+0xcc/0x460
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input+0x3f/0xb0
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_rcv_finish+0x92/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_rcv+0x346/0x550
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipvlan_handle_frame+0xbd/0x1c0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb_core+0x432/0xb40
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipv6_gro_receive+0x22b/0x390
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  ? __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  netif_receive_skb_internal+0x37/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  napi_gro_receive+0xc5/0xf0
  Jun 14 15:16:37 srv-x3w2q kernel:  receive_buf+0x275/0x1180 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  ? vring_unmap_one+0x1b/0x80
  Jun 14 15:16:37 srv-x3w2q kernel:  virtnet_poll+0xc4/0x289 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  net_rx_action+0x140/0x3a0
  Jun 14 15:16:37 srv-x3w2q kernel:  __do_softirq+0xdf/0x2b2
  Jun 14 15:16:37 srv-x3w2q kernel:  irq_exit+0xb6/0xc0
  Jun 14 15:16:37 srv-x3w2q kernel:  do_IRQ+0x82/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  common_interrupt+0x84/0x84
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel: RIP: 0010:native_safe_halt+0x6/0x10
  Jun 14 15:16:37 srv-x3w2q kernel: RSP: 0018:ac5ec0377e80 EFLAGS: 0246 
ORIG_RAX: ffd9
  Jun 14 15:16:37 srv-x3w2q kernel: RAX: a4196060 RBX: 0001 
RCX: 
  Jun 14 15:16:37 srv-x3w2q kernel: RDX:  RSI:  
RDI: 
  Jun 14 15:16:37 srv-x3w2q kernel: RBP: ac5ec0377e80 R08:  
R09: a4c08528
  Jun 14 15:16:37 srv-x3w2q kernel: R10: 91d27ffb1ca8 R11:  
R12: 0001
  Jun 14 15:16:37 srv-x3w2q kernel: R13:  R14:  
R15: 
  
  Fix is apparently at https://www.spinics.net/lists/netdev/msg485566.html
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: User Name 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  AlsaDevices:
-  total 0
-

[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093493.html

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

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

** Description changed:

+ 
+ == SRU Justification ==
+ The r8152 module is used in a thunderbolt-connected docking station and
+ ax88179_178a by an external USB dongle.
+ 
+ Despite having two nics connected the bug reporter can't install Bionic.
+ 
+ This SRU request is to add the modules to the debian installer.
+ 
+ == Fix ==
+ UBUNTU: [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
+ 
+ == Regression Potential ==
+ Low.  This is adding a module to the installer.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
+ 
+ 
  r8152 is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.
  
  Despite having two nics connected i can't install Bionic. :-)
  
  This is probably a subset of the modules to be included when fixing LP:
  #1503218.

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

Title:
  Please include ax88179_178a and r8152 modules in d-i udeb

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  
  == SRU Justification ==
  The r8152 module is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected the bug reporter can't install
  Bionic.

  This SRU request is to add the modules to the debian installer.

  == Fix ==
  UBUNTU: [Config:] d-i: Add ax88179_178a and r8152 to nic-modules

  == Regression Potential ==
  Low.  This is adding a module to the installer.

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





  r8152 is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected i can't install Bionic. :-)

  This is probably a subset of the modules to be included when fixing
  LP: #1503218.

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

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

[Kernel-packages] [Bug 1775786] Re: Update to ocxl driver for 18.04.1

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093488.html

** Description changed:

+ == SRU Justification ==
+ IBM is requesting these patches in Bionic.  ocxl (opencapi) is a relatively
+ new driver which was added to Ubuntu 18.04; It's specific to POWER9 systems.
+ 
+ == Regression Potential ==
+ Medium.  There are 10 patches, but all are limited to powerpc and the ocxl 
driver.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by IBM.
+ 
+ 
  ---Problem Description---
  Update to ocxl driver
-  
+ 
  ---uname output---
  4.15.0-22-generic
-  
+ 
  ---Additional Hardware Info---
- opencapi adapter needed 
+ opencapi adapter needed
  
-  Machine Type = any POWER9 system 
-  
+  Machine Type = any POWER9 system
+ 
  ---Debugger---
  A debugger is not configured
-  
  
  == Comment: #1 - Frederic Barrat  - 2018-06-05 
03:46:00 ==
  ocxl (opencapi) is a relatively new driver which was added to Ubuntu 18.04; 
It's specific to POWER9 systems.
  
  We'd like to add the following 9 commits for Ubuntu 18.04.1:
  
  The following 2 patches are already in the main linux tree:
  474cca5fd894de99afc69274e8b25524ae62d7ee
  misc: ocxl: use put_device() instead of device_unregister()
  
  e7666d046ac0eda535282a5fd3b188f31d0f4afd
  ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL
  
  The remaining commits are in the powerpc-next tree and will be merged in
  the next merge window (i.e. in a week or so). See
  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=next
  
  819844285ef2b5d15466f5b5062514135ffba06c
  powerpc: Add TIDR CPU feature for POWER9
  
  3449f191ca9be1a6ac9757b8ab55f239092362e5
  powerpc: Use TIDR CPU feature to control TIDR allocation
  
  71cc64a85d8d99936f6851709a07f18c87a0adab
  powerpc: use task_pid_nr() for TID allocation
  
  19df39581ce99eb1fcfb119945810c9c5bc3f8d4
  ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action
  
  e948e06fc63a1c1e36ec4c8e5c510b881ff19c26
  ocxl: Expose the thread_id needed for wait on POWER9
  
  02a8e5bc1c06045f36423bd9632ad9f40da18d3f
  ocxl: Add an IOCTL so userspace knows what OCXL features are available
  
  721c551d31fb441ff3be701ad3be14cf6e0aca3f
  ocxl: Document new OCXL IOCTLs
  
  Another commit ID to add to the list (fixes a commit from previous list), 
from the 'next' tree:
  2e5c93d6bb2f7bc17eb82748943a1b9f6b068520
  ocxl: Fix missing unlock on error in afu_ioctl_enable_p9_wait()

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

Title:
  Update to ocxl driver for 18.04.1

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  IBM is requesting these patches in Bionic.  ocxl (opencapi) is a relatively
  new driver which was added to Ubuntu 18.04; It's specific to POWER9 systems.

  == Regression Potential ==
  Medium.  There are 10 patches, but all are limited to powerpc and the ocxl 
driver.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.


  ---Problem Description---
  Update to ocxl driver

  ---uname output---
  4.15.0-22-generic

  ---Additional Hardware Info---
  opencapi adapter needed

   Machine Type = any POWER9 system

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

  == Comment: #1 - Frederic Barrat  - 2018-06-05 
03:46:00 ==
  ocxl (opencapi) is a relatively new driver which was added to Ubuntu 18.04; 
It's specific to POWER9 systems.

  We'd like to add the following 9 commits for Ubuntu 18.04.1:

  The following 2 patches are already in the main linux tree:
  474cca5fd894de99afc69274e8b25524ae62d7ee
  misc: ocxl: use put_device() instead of device_unregister()

  e7666d046ac0eda535282a5fd3b188f31d0f4afd
  ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL

  The remaining commits are in the powerpc-next tree and will be merged
  in the next merge window (i.e. in a week or so). See
  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=next

  819844285ef2b5d15466f5b5062514135ffba06c
  powerpc: Add TIDR CPU feature for POWER9

  3449f191ca9be1a6ac9757b8ab55f239092362e5
  powerpc: Use TIDR CPU feature to control TIDR allocation

  71cc64a85d8d99936f6851709a07f18c87a0adab
  powerpc: use task_pid_nr() for TID allocation

  19df39581ce99eb1fcfb119945810c9c5bc3f8d4
  ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

  e948e06fc63a1c1e36ec4c8e5c510b881ff19c26
  ocxl: Expose the thread_id needed for wait on POWER9

  02a8e5bc1c06045f36423bd9632ad9f40da18d3f
  ocxl: Add an IOCTL so userspace knows what OCXL features are available

  721c551d31fb441ff3be701ad3be14cf6e0aca3f
  ocxl: Document new OCXL IOCTLs

  Another commit ID to add to the list (fixes a commit from previous list), 
from the 'next' tree:

[Kernel-packages] [Bug 1777840] Re: uprobes: fix SIGSEGVs with setjmp/longjmp

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093487.html

** Description changed:

- Description:  uprobes: fix SIGSEGVs with setjmp/longjmp
+ == SRU Justification ==
+ This commit fixes SIGSEGVs with setjmp/longjmp.
  
  Symptom:
   Setting a user space return probe on a function that does not
   return because of a longjmp call may cause SIGSEGV or SIGILL.
  
- Problem: 
+ Problem:
   Userspace can do whatever it wants with its stack. Especially
   stack modifications performed with longjmp cannot be handled 100%
   correctly within the uprobes kernel part, which may lead to user
   space observed crashed.
  
- Solution: 
+ Solution:
Implement arch_uretprobe_is_alive() which improves the situation
a lot and works for many situations.
  
+ This commit has also been cc'd to upstream stable, but it has not landed
+ in Bionic as of yet.
+ 
+ == Fix ==
+ 783c3b53b950 ("s390/uprobes: implement arch_uretprobe_is_alive()")
+ 
+ == Regression Potential ==
+ Low.  Limited to s390.  The commit has also been cc'd to upstream
+ stable, so it has had additional upstream review.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
  Upstream-ID:  783c3b53b9506db3e05daacfe34e0287eebb09d8

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

Title:
  uprobes: fix SIGSEGVs with setjmp/longjmp

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  This commit fixes SIGSEGVs with setjmp/longjmp.

  Symptom:
   Setting a user space return probe on a function that does not
   return because of a longjmp call may cause SIGSEGV or SIGILL.

  Problem:
   Userspace can do whatever it wants with its stack. Especially
   stack modifications performed with longjmp cannot be handled 100%
   correctly within the uprobes kernel part, which may lead to user
   space observed crashed.

  Solution:
Implement arch_uretprobe_is_alive() which improves the situation
a lot and works for many situations.

  This commit has also been cc'd to upstream stable, but it has not landed
  in Bionic as of yet.

  == Fix ==
  783c3b53b950 ("s390/uprobes: implement arch_uretprobe_is_alive()")

  == Regression Potential ==
  Low.  Limited to s390.  The commit has also been cc'd to upstream
  stable, so it has had additional upstream review.

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


  Upstream-ID:  783c3b53b9506db3e05daacfe34e0287eebb09d8

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

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

[Kernel-packages] [Bug 1777857] Re: [LTCTest][OPAL][OP920] INFO: rcu_sched self-detected stall on CPU

SRU Request Submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093483.html

** Description changed:

+ == SRU Justification ==
+ IBM is seeing kernel traces during testing.  This is due to a missing
+ backport of some kernel fixes in the RTC driver, which is commit
+ 682e6b4da5cb.  Commit 682e6b4da5cb was also cc'd to upstream stable, but
+ it has not landed in Bionic as of yet.  It is also a fix to upstream
+ commit 628daa8d5abf.
+ 
+ Commit 34dd25de9fe3 is also needed as a prereq to define
+ OPAL_BUSY_DELAY_MS.
+ 
+ == Fixes ==
+ 34dd25de9fe3 ("powerpc/powernv: define a standard delay for OPAL_BUSY type 
retry loops")
+ 682e6b4da5cb ("rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops")
+ 
+ == Regression Potential ==
+ Low.  Limited to powerpc.  Fixes a current regression.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2018-05-23 
01:15:30 ==
  Install a P9 Open Power Hardware with the latest OP920 Firmware images 
provided in the following link:
  
http://pfd.austin.ibm.com/releasenotes/openpower9/OP920/OP920_1808A/OP920_1808N_RelNote_Main.html
  
  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.1"
  VERSION_ID="ibm-v2.1-438-g0030304-r12-0-g5ee4fb0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.1"
  BUILD_ID="ibm-v2.1-438-g0030304-r12"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
  IBM-witherspoon-ibm-OP9-v2.0-2.14
- op-build-v2.0-11-gb248194-dirty
- buildroot-2018.02.1-6-ga8d1126
- skiboot-v6.0.1
- hostboot-8ab6717d-pfc036fa
- occ-77bb5e6
- linux-4.16.8-openpower2-pb532d68
- petitboot-v1.7.1-p1188545
- machine-xml-7cd20a6
- hostboot-binaries-276bb70
- capp-ucode-p9-dd2-v4
- sbe-a596975
- hcode-b8173e8
+ op-build-v2.0-11-gb248194-dirty
+ buildroot-2018.02.1-6-ga8d1126
+ skiboot-v6.0.1
+ hostboot-8ab6717d-pfc036fa
+ occ-77bb5e6
+ linux-4.16.8-openpower2-pb532d68
+ petitboot-v1.7.1-p1188545
+ machine-xml-7cd20a6
+ hostboot-binaries-276bb70
+ capp-ucode-p9-dd2-v4
+ sbe-a596975
+ hcode-b8173e8
  
  Seeing the following messages in the dmesg logs.
  
  [   16.377405] ipmi_si: Unable to find any System Interface(s)
  [   17.384118] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [ 1372.711730] INFO: rcu_sched self-detected stall on CPU
  [ 1372.711787]  32-: (5249 ticks this GP) idle=182/141/0 
softirq=1093/1093 fqs=2623
  [ 1372.711863]   (t=5250 jiffies g=22430 c=22429 q=953)
  [ 1372.711921] Task dump for CPU 32:
  [ 1372.711922] kworker/32:1R  running task0  1123  2 
0x0804
  [ 1372.711930] Workqueue: events rtc_timer_do_work
  [ 1372.711931] Call Trace:
  [ 1372.711934] [c03fd2b97350] [c014a8f8] 
sched_show_task.part.16+0xd8/0x110 (unreliable)
  [ 1372.711939] [c03fd2b973c0] [c01aa8bc] 
rcu_dump_cpu_stacks+0xd4/0x138
  [ 1372.711942] [c03fd2b97410] [c01a9988] 
rcu_check_callbacks+0x8e8/0xb40
  [ 1372.711945] [c03fd2b97540] [c01b7c28] 
update_process_times+0x48/0x90
  [ 1372.711948] [c03fd2b97570] [c01cf974] 
tick_sched_handle.isra.5+0x34/0xd0
  [ 1372.711950] [c03fd2b975a0] [c01cfa70] 
tick_sched_timer+0x60/0xe0
  [ 1372.711953] [c03fd2b975e0] [c01b87d4] 
__hrtimer_run_queues+0x144/0x370
  [ 1372.711956] [c03fd2b97660] [c01b972c] 
hrtimer_interrupt+0xfc/0x350
  [ 1372.711959] [c03fd2b97730] [c00249f0] 
__timer_interrupt+0x90/0x260
  [ 1372.711962] [c03fd2b97780] [c0024e08] timer_interrupt+0x98/0xe0
  [ 1372.711965] [c03fd2b977b0] [c0009054] 
decrementer_common+0x114/0x120
  [ 1372.711970] --- interrupt: 901 at opal_get_rtc_time+0x98/0x110
-LR = opal_return+0x14/0x48
+    LR = opal_return+0x14/0x48
  [ 1372.711972] [c03fd2b97aa0] [c0a457b8] 
opal_get_rtc_time+0x98/0x110 (unreliable)
  [ 1372.711975] [c03fd2b97ae0] [c0a3f98c] 
__rtc_read_time+0x7c/0x180
  [ 1372.711977] [c03fd2b97b60] [c0a41738] 
rtc_timer_do_work+0x78/0x250
  [ 1372.711980] [c03fd2b97c90] [c0134378] 
process_one_work+0x298/0x5a0
  [ 1372.711982] [c03fd2b97d20] [c0134718] worker_thread+0x98/0x630
  [ 1372.711985] [c03fd2b97dc0] [c013d348] kthread+0x1a8/0x1b0
  [ 1372.711988] [c03fd2b97e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84
  
  == Comment: #1 - PAVAMAN SUBRAMANIYAM  - 2018-05-23
  01:31:06 ==
- 
  
  == Comment: #2 - Application Cdeadmin  - 2018-05-23 
01:33:40 ==
  cde00 (cdead...@us.ibm.com)

[Kernel-packages] [Bug 1777194] Re: Hard LOCKUP observed on stressing Ubuntu 18 04

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093481.html

** Description changed:

- --Problem Description-- 
+ 
+ == SRU Justification ==
+ IBM has seen hard lockups when running stress tests against Bionic.
+ These test sometimes lead to rcu_stalls.  IBM found that this bug is
+ resolved with commits 6bed3237624e and ac61c1156623.
+ 
+ == Fixes ==
+ 6bed3237624e ("powerpc: use NMI IPI for smp_send_stop")
+ ac61c1156623 ("powerpc: Fix smp_send_stop NMI IPI handling")
+ 
+ == Regression Potential ==
+ Low.  Limited to powerpc.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ --Problem Description--
  Hard LOCKUP on stressing Ubuntu 18 04
  
  ---Issue observed---
  Hard LOCKUP on stressing Ubuntu 18 04 using Ubuntu 18 04, sometimes leads to 
rcu_stalls.
  
  Apr 17 00:00:23 lep8d kernel: [ 4309.786755] Watchdog CPU:3 Hard LOCKUP
  Apr 17 00:00:23 lep8d kernel: [ 4309.786759] Modules linked in: algif_rng 
salsa20_generic userio camellia_generic cast6_generic cast_common snd_seq 
snd_seq_device snd_timer snd soundcore vhost_net serpent_generic tap 
twofish_generic twofish_common vhost_vsock vmw_vsock_virtio_transport_common 
vhost vsock lrw unix_diag algif_skcipher cuse sctp tgr192 wp512 rmd320 rmd256 
rmd160 hci_vhci rmd128 bluetooth ecdh_generic dccp_ipv4 md4 uhid hid algif_hash 
dccp af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc 
ebtable_filter ebtables devlink ip6table_filter ip6_tables iptable_filter 
kvm_hv kvm binfmt_misc uio_pdrv_genirq uio vmx_crypto ibmpowernv 
powernv_op_panel ipmi_powernv
  Apr 17 00:00:23 lep8d kernel: [ 4309.786899]  ipmi_devintf ipmi_msghandler 
powernv_rng leds_powernv crct10dif_vpmsum sch_fq_codel ip_tables x_tables 
autofs4 ses enclosure scsi_transport_sas btrfs xor zstd_compress raid6_pq uas 
usb_storage crc32c_vpmsum tg3 ipr
  Apr 17 00:00:23 lep8d kernel: [ 4309.786944] CPU: 3 PID: 28361 Comm: 
stress-ng-hrtim Not tainted 4.15.0-15-generic #16-Ubuntu
  Apr 17 00:00:23 lep8d kernel: [ 4309.786950] NIP:  c0d0c8b8 LR: 
c0120dbc CTR: c0024480
  Apr 17 00:00:23 lep8d kernel: [ 4309.786956] REGS: c7f7fd80 TRAP: 
0900   Not tainted  (4.15.0-15-generic)
  Apr 17 00:00:23 lep8d kernel: [ 4309.786957] MSR:  90009033 
  CR: 28000442  XER: 2000
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] CFAR: c0120db8 SOFTE: 0
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR00: c0120dbc 
c02d51377ba0 c16eb400 c02d512b0f88
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR04:  
0001 01f40668 0001
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR08: 0001 
 8003 
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR12: c0024480 
c7a22100  000186a0
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR16: 7fffed3687e0 
0abda98e5db8 8005 00040100
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR20:  
418004fc 003c 0843
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR24: c02d512b0f88 
 c02d51377d30 c02d52d47c00
  Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR28: c02d51377d50 
c02d51377d50 c02d52f04500 c02d512b0f88
  Apr 17 00:00:23 lep8d kernel: [ 4309.787035] NIP [c0d0c8b8] 
_raw_spin_lock+0x38/0xe0
  Apr 17 00:00:23 lep8d kernel: [ 4309.787045] LR [c0120dbc] 
dequeue_signal+0xcc/0x260
  Apr 17 00:00:23 lep8d kernel: [ 4309.787046] Call Trace:
  Apr 17 00:00:23 lep8d kernel: [ 4309.787052] [c02d51377bd0] 
[c0120dac] dequeue_signal+0xbc/0x260
  Apr 17 00:00:23 lep8d kernel: [ 4309.787059] [c02d51377c20] 
[c012459c] get_signal+0x13c/0x7a0
  Apr 17 00:00:23 lep8d kernel: [ 4309.787066] [c02d51377d10] 
[c001dacc] do_signal+0x7c/0x2c0
  Apr 17 00:00:23 lep8d kernel: [ 4309.787072] [c02d51377e00] 
[c001deb0] do_notify_resume+0xd0/0x100
  Apr 17 00:00:23 lep8d kernel: [ 4309.787083] [c02d51377e30] 
[c000b7c4] ret_from_except_lite+0x70/0x74
  Apr 17 00:00:23 lep8d kernel: [ 4309.787085] Instruction dump:
  Apr 17 00:00:23 lep8d kernel: [ 4309.787090] 7c0802a6 6000 fbe1fff8 
f821ffd1 7c7f1b78 3940 994d028c 814d0008
  Apr 17 00:00:23 lep8d kernel: [ 4309.787102] 7d201829 2c09 40c20010 
7d40192d <40c2fff0> 7c2004ac 2fa9 409e001c
  Apr 17 00:00:23 lep8d kernel: [ 4313.015781] kauditd_printk_skb: 13 callbacks 
suppressed
  
  ---uname output---
  # uname -a
  Linux lep8d 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 
ppc64le ppc64le

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

2018-06-22 Thread Boris

Since 16.04.4 LTS with Kernel 4.4.0-128-generic/x86_64 the problems
seems to be fixed. Our VM with more than one VHD are running without
problems for two weeks now. Neither backups nor cluster failovers are
crashing the VM.

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless

[Kernel-packages] [Bug 1776340] Re: linux-oem: 4.15.0-1009.12 -proposed tracker

2018-06-22 Thread Brad Figg

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 22. June 2018 15:02 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 22. June 2018 15:02 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-oem: 4.15.0-1009.12 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778222] Re: Ubuntu LIVECD kernel panic

2018-06-22 Thread Kai-Heng Feng

The kernel version is 4.13, which is used in 17.10 but not 18.04.

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

Title:
  Ubuntu LIVECD kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I’ve encounter a problem, not sure if it’s a bug or an intentional
  change to the Linux kernel. I normally don’t mess with the kernel as
  suggested by many on the Internet. But with new releases of Linux Mint
  19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s.
  With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a
  try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot
  of the LiveCD locks up with a kernel panic.

  So I tried the Linux Mint 19.0 LiveCD and had the same failure.
  Looking further at the problem I started installing different kernels
  in my Linux Mint 18.3  system. I found that my system will operate
  with different kernels up to an including 4.11. When I tried kernels
  4.13 or 4.15 both failed to boot with the same kernel panic.
  Everything locks up and I have to do a power off, power on operation
  to recover. So kernel 4.11 is the last one I can use. I found that the
  LiveCD’s both use kernel 4.15 which does not work on my system.

  I have included a picture of the screen when the boot fails. Would
  like to use the latest versions but the kernel problem prevents me
  from doing so.

  This is my uname data: uname -a
  Linux   4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  I have the dmidecode data and the lspci data if needed for kernel
  4.11.(From a good boot)

  With further testing I have found that, Linux Mint 19.0 LiveCD (in
  compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option,
  will both boot into a usable live operating system. I’m afraid though
  that if I installed either to my hard drive that neither would boot. I
  would like to have help resolving this problem so I can continue to
  use Linux. Thanks!

  Ps.there are no newer bios updates for my computer.

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

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

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

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 1778222

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

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

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

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

** Tags added: artful

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

Title:
  Ubuntu LIVECD kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I’ve encounter a problem, not sure if it’s a bug or an intentional
  change to the Linux kernel. I normally don’t mess with the kernel as
  suggested by many on the Internet. But with new releases of Linux Mint
  19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s.
  With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a
  try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot
  of the LiveCD locks up with a kernel panic.

  So I tried the Linux Mint 19.0 LiveCD and had the same failure.
  Looking further at the problem I started installing different kernels
  in my Linux Mint 18.3  system. I found that my system will operate
  with different kernels up to an including 4.11. When I tried kernels
  4.13 or 4.15 both failed to boot with the same kernel panic.
  Everything locks up and I have to do a power off, power on operation
  to recover. So kernel 4.11 is the last one I can use. I found that the
  LiveCD’s both use kernel 4.15 which does not work on my system.

  I have included a picture of the screen when the boot fails. Would
  like to use the latest versions but the kernel problem prevents me
  from doing so.

  This is my uname data: uname -a
  Linux   4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  I have the dmidecode data and the lspci data if needed for kernel
  4.11.(From a good boot)

  With further testing I have found that, Linux Mint 19.0 LiveCD (in
  compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option,
  will both boot into a usable live operating system. I’m afraid though
  that if I installed either to my hard drive that neither would boot. I
  would like to have help resolving this problem so I can continue to
  use Linux. Thanks!

  Ps.there are no newer bios updates for my computer.

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

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

[Kernel-packages] [Bug 1778222] [NEW] Ubuntu LIVECD kernel panic

2018-06-22 Thread k4lmcisme

Public bug reported:

I’ve encounter a problem, not sure if it’s a bug or an intentional
change to the Linux kernel. I normally don’t mess with the kernel as
suggested by many on the Internet. But with new releases of Linux Mint
19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s.
With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a
try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot of
the LiveCD locks up with a kernel panic.

So I tried the Linux Mint 19.0 LiveCD and had the same failure. Looking
further at the problem I started installing different kernels in my
Linux Mint 18.3 system. I found that my system will operate with
different kernels up to an including 4.11. When I tried kernels 4.13 or
4.15 both failed to boot with the same kernel panic. Everything locks up
and I have to do a power off, power on operation to recover. So kernel
4.11 is the last one I can use. I found that the LiveCD’s both use
kernel 4.15 which does not work on my system.

I have included a picture of the screen when the boot fails. Would like
to use the latest versions but the kernel problem prevents me from doing
so.

This is my uname data: uname -a
Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

I have the dmidecode data and the lspci data if needed for kernel
4.11.(From a good boot)

With further testing I have found that, Linux Mint 19.0 LiveCD (in
compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option,
will both boot into a usable live operating system. I’m afraid though
that if I installed either to my hard drive that neither would boot. I
would like to have help resolving this problem so I can continue to use
Linux. Thanks!

Ps.there are no newer bios updates for my computer.

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

** Tags: artful kernel panic

** Attachment added: "IMG_20180607_092725987_LL.jpg"

https://bugs.launchpad.net/bugs/1778222/+attachment/5155504/+files/IMG_20180607_092725987_LL.jpg

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

Title:
Ubuntu LIVECD kernel panic

Status in linux package in Ubuntu:
Incomplete

Bug description:
I’ve encounter a problem, not sure if it’s a bug or an intentional
change to the Linux kernel. I normally don’t mess with the kernel as
suggested by many on the Internet. But with new releases of Linux Mint
19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s.
With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a
try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot
of the LiveCD locks up with a kernel panic.

So I tried the Linux Mint 19.0 LiveCD and had the same failure.
Looking further at the problem I started installing different kernels
in my Linux Mint 18.3 system. I found that my system will operate
with different kernels up to an including 4.11. When I tried kernels
4.13 or 4.15 both failed to boot with the same kernel panic.
Everything locks up and I have to do a power off, power on operation
to recover. So kernel 4.11 is the last one I can use. I found that the
LiveCD’s both use kernel 4.15 which does not work on my system.

I have included a picture of the screen when the boot fails. Would
like to use the latest versions but the kernel problem prevents me
from doing so.

This is my uname data: uname -a
Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

I have the dmidecode data and the lspci data if needed for kernel
4.11.(From a good boot)

Ps.there are no newer bios updates for my computer.

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

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

[Kernel-packages] [Bug 1778172] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build

2018-06-22 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-24-generic
  Date: Fri Jun 22 09:57:36 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function 'init_timer' 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-09-12 (282 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1778172] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build

2018-06-22 Thread Marc Deslauriers

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

** Information type changed from Private Security to Public

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-24-generic
  Date: Fri Jun 22 09:57:36 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function 'init_timer' 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-09-12 (282 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1777676] Re: No rdepends for linux-modules-extra-4.15.0-1013-azure

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  No rdepends for linux-modules-extra-4.15.0-1013-azure

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  The package "linux-image-azure" installs "linux-
  image-4.15.0-1013-azure".  There are no packages that have a
  dependency for "linux-modules-extra-4.15.0-1013-azure", so there is no
  way to keep the "linux-modules-extra-*" packages up-to-date when using
  an azure image.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-modules-extra-4.15.0-1013-azure 4.15.0-1013.13~16.04.2
  ProcVersionSignature: User Name 4.15.0-1013.13~16.04.2-azure 4.15.18
  Uname: Linux 4.15.0-1013-azure x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Jun 19 11:58:45 2018
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1774595] Re: getxattr04 in LTP syscall test failed with X/X-LTS kernel

The fix for this issue:
5a93790d4e2df73e30c965ec6e49be82fc3ccfce

Has been included in the stable-update:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775771

Therefore I'm closing this.
Thanks

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

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

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

Title:
  getxattr04 in LTP syscall test failed with X/X-LTS kernel

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

Bug description:
  The "getxattr04" from the LTP syscall tests has failed on a testing
  node with Xenial kernel installed.

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp
8. echo "getxattr04" > /tmp/jobs
9. ./runltp -f /tmp/jobs

  <<>>
  tag=getxattr04 stime=1527682633
  cmdline="getxattr04"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-128-generic 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Jun  1 03:06:15 2018
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-128-generic N/A
   linux-backports-modules-4.4.0-128-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1776340] Re: linux-oem: 4.15.0-1009.12 -proposed tracker

2018-06-22 Thread Łukasz Zemczak

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

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

Title:
  linux-oem: 4.15.0-1009.12 -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 upload-to-ppa 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 is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1776340] Re: linux-oem: 4.15.0-1009.12 -proposed tracker

2018-06-22 Thread Łukasz Zemczak

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-oem: 4.15.0-1009.12 -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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1759723] Comment bridged from LTC Bugzilla

2018-06-22 Thread bugproxy

--- Comment From rajanikanth...@in.ibm.com 2018-06-22 05:45 EDT---
Hi,

We have verified this bug on "4.15.0-24-generic #26-Ubuntu"  kernel,
it's working fine.

root@boslcp4:~# uname -a
Linux boslcp4 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
root@boslcp4:~#

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

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Problem Description:
  ===
  Performed HOTPLUG cpu attach operation for the guest and guest console 
becomes unresponsive.

  Steps to re-create:
  ==
  1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels
   
  2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.15.0-12-generic

  root@boslcp3g3:/kte/tools/setup.d# uname -a
  Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g3:/kte/tools/setup.d# uname -r
  4.15.0-12-generic

  3. Started HTX & stress-ng for on guest for 10-15 min

  4. Cleaned up the tests to perform hot-plug and ensure enough memory
  and cpu was there (killed all Process using kill)

  5. Performed cpu hot-plug and guest went into hung state

  Before Hotplug:

  root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu
64

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  



  root@boslcp3:~#  

  6. After this operation, guest becomes unrepsonsive as below

  
  root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more 
than 120 seconds.
  [ 3626.146375]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3626.146699]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 
seconds.
  [ 3626.147016]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 
seconds.
  [ 3626.147361]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds.
  [ 3626.147686]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds.
  [ 3626.147937]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds.
  [ 3626.148173]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds.
  [ 3626.148406]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  root@boslcp3g3:~#
  root@boslcp3g3:~# ps -ef | grep stress-ng
  [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds.
  [ 3746.978221]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3746.978534]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978607]

[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages

2018-06-22 Thread ByungYeol Woo

I experienced simmilar problem of "vxlan: non-ECT with TOS=0x02" with Intel NIC.
I issued to bugzilla and intel community, but I couldn't found a solution.

Could you please check following URLs?:

https://communities.intel.com/thread/120521
https://bugzilla.kernel.org/show_bug.cgi?id=198489


** Bug watch added: Linux Kernel Bug Tracker #198489
   https://bugzilla.kernel.org/show_bug.cgi?id=198489

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

Title:
  4.4.0-127.153 generates many "sit: non-ECT" messages

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  A regression was introduce in Xenial linux-image-4.4.0-127-generic.  It
  was found that this regression was introduced by mainline commit
  b699d0035836.  This commit was applied to Xenial via the 4.4.128 upstream 
stable
  updates.

  Upstream decided to revert this commit in mainline commit f4eb17e1efe5,
  which was added in v4.12-rc5.

  == Fix ==
  f4eb17e1efe5 ("Revert "sit: reload iphdr in ipip6_rcv"")

  == Regression Potential ==
  Low.  This is a revert request to resolve a regression.  The revert was
  also performed upstream.

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



  Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a
  Xenial VM with a sit tunnel, I get such messages:

  May 22 10:49:38 gw kernel: [   68.121601] sit: non-ECT from 0.0.0.0
  with TOS=0x5

  Those are logged quite often:

  # grep -cF 'sit: non-ECT' /var/log/syslog
  9108

  Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the
  issue.

  # lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  # apt-cache policy linux-image-4.4.0-127-generic
  linux-image-4.4.0-127-generic:
    Installed: 4.4.0-127.153
    Candidate: 4.4.0-127.153
    Version table:
   *** 4.4.0-127.153 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-127-generic 4.4.0-127.153
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 20:08 seq
   crw-rw 1 root audio 116, 33 May 22 20:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Tue May 22 21:18:45 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 
kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-127-generic N/A
   linux-backports-modules-4.4.0-127-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 21:33 seq
   crw-rw 1 root audio 116, 33 May 22 21:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package:

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-06-22 Thread Daniel van Vugt

Here's a patch for 18.04.

Next: We await sponsorship of the patch, which means it will enter
"bionic-proposed" for testing.

Then: You will all be asked to test the proposed update to verify it
works before it reaches other users.

** Patch added: "bluez_5.48-0ubuntu3.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+attachment/5155469/+files/bluez_5.48-0ubuntu3.1.debdiff

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

2018-06-22 Thread bugproxy

--- Comment From pavra...@in.ibm.com 2018-06-22 05:24 EDT---
(In reply to comment #24)
>
> Hello bugproxy, or anyone else affected,
>
> Accepted makedumpfile into xenial-proposed. The package will build now and
> be available at
> https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.3-2~16.04.1 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to
> enable and use -proposed.Your feedback will aid us getting this update out
> to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-xenial to verification-done-xenial. If it does not fix
> the bug for you, please add a comment stating that, and change the tag to
> verification-failed-xenial. In either case, without details of your testing
> we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance!
>
> Also available on artful-proposed.

Tried with proposed package, dump capture is successful.

root@ltc-garri3:~# uname -a
Linux ltc-garri3 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
root@ltc-garri3:~# df -Th
Filesystem Type  Size  Used Avail Use% Mounted on
udev   devtmpfs  211G 0  211G   0% /dev
tmpfs  tmpfs  45G   20M   45G   1% /run
/dev/sda2  xfs   929G  1.6G  927G   1% /
tmpfs  tmpfs 222G 0  222G   0% /dev/shm
tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
tmpfs  tmpfs 222G 0  222G   0% /sys/fs/cgroup
tmpfs  tmpfs  45G 0   45G   0% /run/user/1000

root@ltc-garri3:/var/crash# cd 201806220415
root@ltc-garri3:/var/crash/201806220415# ls
dmesg.201806220415  dump.201806220415
root@ltc-garri3:/var/crash/201806220415# tail dmesg.201806220415
[  207.574328] Instruction dump:
[  207.574359] 3842e720 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
39490664
[  207.574612] 3921 912a 7c0004ac 3940 <992a> 38210020 e8010010 
7c0803a6
[  207.574870] ---[ end trace 11a9e3d935ec528f ]---
[  207.734198]
[  207.734265] Sending IPI to other CPUs
[  207.735462] IPI complete
[  207.736681] kexec: waiting for cpu 8 (physical 32) to enter OPAL
[  207.737915] kexec: waiting for cpu 9 (physical 33) to enter OPAL
[  207.739214] kexec: waiting for cpu 43 (physical 99) to enter OPAL

Thanks.
Pavithra

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

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

Title:
  Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-06-22 Thread Daniel van Vugt

** Description changed:

- STEPS TO REPRODUCE:
- 1. Connect to Bluetooth audio device
- 2. Suspend & Resume
- 3. Reconnect to Bluetooth device.
+ [Impact]
+ 
+ Users of Bluetooth audio have no sound after they suspend and resume the
+ system.
+ 
+ [Test Case]
+ 
+  1. Connect to Bluetooth audio device
+  2. Suspend & Resume
+  3. Reconnect to Bluetooth device.
+ 
+ [Regression Potential]
+ 
+ Medium. TODO: Describe the patch in more detail
+ 
+ [Other Info]
+  
+ Already released to cosmic as part of bluez version 5.50.
  
  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.
  
  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  
  Workaround is to run sudo systemctl restart bluetooth after resume.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
-   UP RUNNING PSCAN 
-   RX bytes:5025 acl:32 sco:0 events:202 errors:0
-   TX bytes:5785 acl:32 sco:0 commands:103 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
+   UP RUNNING PSCAN
+   RX bytes:5025 acl:32 sco:0 events:202 errors:0
+   TX bytes:5785 acl:32 sco:0 commands:103 errors:0

** Description changed:

  [Impact]
  
  Users of Bluetooth audio have no sound after they suspend and resume the
  system.
  
  [Test Case]
  
-  1. Connect to Bluetooth audio device
-  2. Suspend & Resume
-  3. Reconnect to Bluetooth device.
+  1. Connect to Bluetooth audio device
+  2. Suspend & Resume
+  3. Reconnect to Bluetooth device.
  
  [Regression Potential]
  
- Medium. TODO: Describe the patch in more detail
+ Low. Although common Bluetooth code is modified in the fix, it has been
+ released as a patch in other distros for some time already.
  
  [Other Info]
-  
+ 
  Already released to cosmic as part of bluez version 5.50.
  
  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.
  
  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  
  Workaround is to run sudo systemctl restart bluetooth after resume.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package:

[Kernel-packages] [Bug 1776829] Re: linux-aws: 4.4.0-1062.71 -proposed tracker

4.4.0-1062.71 - aws
Regression test CMPL, RTB.

Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3, 
only spotted on t2.small, passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387), 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in 
ubuntu-cloud container), failed on c3.large, passed on the others
  ubuntu_quota_smoke_test - test should be disabled for AWS (bug 1777813)

Skipped / blacklisted:
 * ubuntu_ltp
 * ubuntu_nbd_smoke_test
 * ubuntu_seccomp
 * ubuntu_sysdig_smoke_test
 * ubuntu_zram_smoke_test

Note: ubuntu_ltp_syscalls test must be reviewed on the Jenkins server,
the hang issue (bug 179) will prevent it from copy the test report


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

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

** Tags added: regression-testing-passed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776822
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776819] Re: linux: 3.13.0-153.203 -proposed tracker

2018-06-22 Thread Taihsiang Ho

Hardware Certification have begun testing this -proposed kernel.

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

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

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

Title:
  linux: 3.13.0-153.203 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: bug 1776820 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776822] Re: linux: 4.4.0-130.156 -proposed tracker

2018-06-22 Thread Taihsiang Ho

Hardware Certification have begun testing this -proposed kernel.

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

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

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

Title:
  linux: 4.4.0-130.156 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1776823 (linux-lts-xenial), bug 1776824 (linux-aws)
  derivatives: bug 1776357 (linux-euclid), bug 1776826 (linux-kvm), bug 1776359 
(linux-raspi2), bug 1776361 (linux-snapdragon), bug 1776829 (linux-aws)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with T/X/A/B kernel

On Xenial, this test will time out as well, but with slightly different
error message:

  <<>>
  tag=fanotify09 stime=1529071345
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s  
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=9636 fd=23
  fanotify09.c:197: PASS: group 1 got no event
  fanotify09.c:197: PASS: group 2 got no event
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Cannot kill test processes!
  Congratulation, likely test hit a kernel bug.
  Exitting uncleanly...
  <<>>
  initiation_status="ok"
  duration=350 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

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

Title:
  fanotify09 in LTP syscall test failed with T/X/A/B kernel

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

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  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  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1774595] Re: getxattr04 in LTP syscall test failed with X/X-LTS kernel

Passed on Xenial in this cycle.

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

Title:
  getxattr04 in LTP syscall test failed with X/X-LTS kernel

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

Bug description:
  The "getxattr04" from the LTP syscall tests has failed on a testing
  node with Xenial kernel installed.

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp
8. echo "getxattr04" > /tmp/jobs
9. ./runltp -f /tmp/jobs

  <<>>
  tag=getxattr04 stime=1527682633
  cmdline="getxattr04"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-128-generic 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Jun  1 03:06:15 2018
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-128-generic N/A
   linux-backports-modules-4.4.0-128-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1772624] Re: Broadcom BCM4356 wifi chipset firmware is not working

2018-06-22 Thread Jean-Pierre Thomasset

I still have the issue with the latest version of the linux-firmware
package (1.173.1). However the firmware (brcm/brcmfmac4356-pcie.bin) in
the official linux-firmware repository solves my issue.

The fix was introduced in the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=fe4a9d49d44c40a7bc32cdd9529e6a5c8ac92519

Regards,
Jean-Pierre.

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

Title:
  Broadcom BCM4356 wifi chipset firmware is not working

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  After upgrading to Ubuntu 18.04 I got an issue with the wifi chipset
  (Broadcom BCM4356) not initializing properly.

  Here is the error I got when loading the driver brcmfmac:

  ```
  [ 8189.092819] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [ 8189.093100] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [ 8191.568544] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for 
query command
  [ 8191.568562] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr 
failed, -5
  [ 8191.568570] brcmfmac: brcmf_bus_started: failed: -5
  [ 8191.568588] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding
  ```

  As seen here https://answers.launchpad.net/ubuntu/+question/668329, I
  reverted to the previous linux-firmware version and then the wifi
  chipset is working:

  Previous firmware package: https://packages.ubuntu.com/artful-updates
  /linux-firmware

  ```
  [10087.698214] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [10087.698634] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [10088.104176] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.clm_blob failed with error -2
  [10088.104186] brcmfmac: brcmf_c_process_clm_blob: no clm_blob 
available(err=-2), device may have limited channels available
  [10088.105170] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016
  [10088.179872] brcmfmac :04:00.0 wlp4s0: renamed from wlan0
  ```

  The problem seems to have been reported to the linux-wireless mailing
  list but no fix has been committed apparently :
  https://www.spinics.net/lists/linux-wireless/msg168687.html

  System information:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
Installé : 4.15.0-20.21
Candidat : 4.15.0-20.21
   Table de version :
   *** 4.15.0-20.21 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  linux-firmware:
Installé : 1.173
Candidat : 1.173
   Table de version :
   *** 1.173 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  Regards,
  Jean Pierre.

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

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

[Kernel-packages] [Bug 1776345] Re: linux-kvm: 4.15.0-1012.12 -proposed tracker

2018-06-22 Thread Brad Figg

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-kvm: 4.15.0-1012.12 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

2018-06-22 Thread Bas Zoetekouw

I just noticed that this 4.17 kernel is from Debian Experimental.  No
idea what this was installed on my system though...

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

Title:
  xhci hangs; reset results in NULL pointer dereference

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

Bug description:
  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
cd $xhci
echo Resetting devices from $xhci...
for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1
  [252243.476067]  raid0 multipath linear dm_mirror dm_region_hash dm_log 
usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt fb_sys_fops ptp aesni_intel psmouse drm pps_core rtsx_pci aes_x86_64 
ahci crypto_simd glue_helper libahci wmi cryptd video
  [252243.476089] CPU: 2 PID: 1787 Comm:

[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with T/X/A/B kernel

** Summary changed:

- fanotify09 in LTP syscall test failed with T/A/B kernel
+ fanotify09 in LTP syscall test failed with T/X/A/B kernel

** Tags added: xenial

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

Title:
  fanotify09 in LTP syscall test failed with T/X/A/B kernel

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

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  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  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

2018-06-22 Thread Bas Zoetekouw

I just encountered this bug again in cosmic with kernel
4.17.0-041700rc1-generic.  Definitely not fixed in 4.17.

Note that with kernel 4.15, the xhci hang occurs too, but then I can
reset the bus without causing a kernel Oops.

I'll attach the Oops for 4.17

** Attachment added: "kernel oops"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763594/+attachment/5155455/+files/oops.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/1763594

Title:
  xhci hangs; reset results in NULL pointer dereference

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

Bug description:
  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
cd $xhci
echo Resetting devices from $xhci...
for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1
  [252243.476067]  raid0 multipath linear dm_mirror dm_region_hash dm_log 
usbhid hid crct10dif_pclmul crc32_pclmul

[Kernel-packages] [Bug 1767948] Re: Unable to connect to 802.1x secured connection since kernel update

2018-06-22 Thread tik0

This bug seems to be fixed upstream as well as by the latest vanilla 
kernel/upgrade:
4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux


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

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

Title:
  Unable to connect to 802.1x secured connection since kernel update

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After a simple upgrade with 16.04.1-Ubuntu to kernel 4.13.0-39.44, the 
authentication against 802.1x secured networks does not work anymore.
  If I boot via an older kernel (4.13.0-37), networking works like a charm.
  Other connections like DHCP, static IP or Radius authentication works as well.
  This is also the reason why I filed the bug against the kernel, and not the 
network-manager or wpa_supplicant.
  I have a vanilla ubuntu installation on a Lenovo T440s.
  Network security settings are attached.
  The /var/log/syslog is as follows (subjective information obfuscated by 
'?!?!?!?!?!'):

  Apr 30 08:59:24 lappy NetworkManager[14860]:   [1525071564.8544] device 
(enp0s25): Activation: starting connection '?!?!?!?!?!' (?!?!?!?!?!)
  Apr 30 08:59:24 lappy NetworkManager[14860]:   [1525071564.8545] audit: 
op="connection-activate" uuid="?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!" 
name="?!?!?!?!?!" pid=2099 uid=1000 result="success"
  Apr 30 08:59:24 lappy NetworkManager[14860]:   [1525071564.8546] device 
(enp0s25): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 30 08:59:24 lappy kernel: [110298.394202] e1000e: enp0s25 NIC Link is Down
  Apr 30 08:59:24 lappy NetworkManager[14860]:   [1525071564.9303] device 
(enp0s25): set MAC address to ?!?!?!?!?!?!?!?!?!?!
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.1148] device 
(enp0s25): link disconnected (deferring action for 4 seconds)
  Apr 30 08:59:25 lappy kernel: [110298.579437] IPv6: ADDRCONF(NETDEV_UP): 
enp0s25: link is not ready
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.1182] device 
(enp0s25): state change: prepare -> config (reason 'none') [40 50 0]
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.1189] device 
(enp0s25): Activation: (ethernet) connection 'CITEC-KS' has security, but 
secrets are required.
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.1190] device 
(enp0s25): state change: config -> need-auth (reason 'none') [50 60 0]
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.1668] device 
(enp0s25): state change: need-auth -> prepare (reason 'none') [60 40 0]
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.1675] device 
(enp0s25): state change: prepare -> config (reason 'none') [40 50 0]
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.1677] device 
(enp0s25): Activation: (ethernet) connection 'CITEC-KS' requires no security. 
No secrets needed.
  Apr 30 08:59:25 lappy wpa_supplicant[1314]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 30 08:59:25 lappy wpa_supplicant[1314]: dbus: Failed to construct signal
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2162] device 
(enp0s25): supplicant interface state: starting -> ready
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2162] 
Config: added 'password' value ''
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2162] 
Config: added 'key_mgmt' value 'IEEE8021X'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2162] 
Config: added 'eapol_flags' value '0'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2163] 
Config: added 'eap' value 'PEAP'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2163] 
Config: added 'fragment_size' value '1266'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2163] 
Config: added 'phase2' value 'auth=MSCHAPV2'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2163] 
Config: added 'ca_cert' value '?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2163] 
Config: added 'identity' value '?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2163] 
Config: added 'anonymous_identity' value 'anonymous'
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2168] 
sup-iface[0x17d6780,enp0s25]: config: set interface ap_scan to 0
  Apr 30 08:59:25 lappy wpa_supplicant[1314]: enp0s25: Associated with 
?!?!?!?!?!?!?!?!?!?!
  Apr 30 08:59:25 lappy wpa_supplicant[1314]: WMM AC: Missing IEs
  Apr 30 08:59:25 lappy NetworkManager[14860]:   [1525071565.2236] device 
(enp0s25): supplicant interface state: ready -> associated
  Apr 30 08:59:28 lappy wpa_supplicant[1314]: enp0s25: CTRL-EVENT-EAP-STARTED 
EAP authentication started
  Apr 30 08:59:28 lappy NetworkManager[14860]:

[Kernel-packages] [Bug 1777389] Re: Xenial update to 4.4.138 stable release

2018-06-22 Thread Kleber Sacilotto de Souza

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

Title:
  Xenial update to 4.4.138 stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

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

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

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

[Kernel-packages] [Bug 1766780] Re: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel

2018-06-22 Thread Kleber Sacilotto de Souza

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

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

Title:
  test_250_config_security_perf_events_restrict in kernel security test
  failed with 4.15 KVM kernel

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

Bug description:
  == Justification ==
  In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
  CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
  meet the security team's requirement.

  == Test ==
  Before enabling the config, test case test_190_config_kernel_fortify and
  test_250_config_security_perf_events_restrict will fail in the kernel
  security testsuite for the kernel SRU regression test.

  It will pass with these two patches applied, tested on a KVM node.

  == Fix ==
  Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
  Set CONFIG_FORTIFY_SOURCE to "y".

  == Regression Potential ==
  Minimal.
  No code changes, just two config changes without disabling any other configs.

  BugLink: https://bugs.launchpad.net/bugs/1766780
  BugLink: https://bugs.launchpad.net/bugs/1766774

  --
  test_250_config_security_perf_events_restrict from the kernel security test 
suite failed with 4.15.0-1008 KVM kernel.

   FAIL: test_250_config_security_perf_events_restrict 
(__main__.KernelSecurityTest)
    Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 2313, in 
test_250_config_security_perf_events_restrict
    self.assertEqual(expected, self._test_config(config_name))
    AssertionError: True != False

  The CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set.
  $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_SECURITY_PERF_EVENTS_RESTRICT
  # CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
  ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
  Uname: Linux 4.15.0-1008-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 04:41:49 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1766774] Re: test_190_config_kernel_fortify in kernel security test failed with 4.15 KVM kernel

2018-06-22 Thread Kleber Sacilotto de Souza

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

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

Title:
  test_190_config_kernel_fortify in kernel security test failed with
  4.15 KVM kernel

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

Bug description:
  == Justification ==
  In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
  CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
  meet the security team's requirement.

  == Test ==
  Before enabling the config, test case test_190_config_kernel_fortify and
  test_250_config_security_perf_events_restrict will fail in the kernel
  security testsuite for the kernel SRU regression test.

  It will pass with these two patches applied, tested on a KVM node.

  == Fix ==
  Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
  Set CONFIG_FORTIFY_SOURCE to "y".

  == Regression Potential ==
  Minimal.
  No code changes, just two config changes without disabling any other configs.

  BugLink: https://bugs.launchpad.net/bugs/1766780
  BugLink: https://bugs.launchpad.net/bugs/1766774

  --
  Test test_190_config_kernel_fortify from the kernel security test suite 
failed with 4.15.0-1008 KVM kernel.

    ==
    FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
    Ensure CONFIG_FORTIFY_SOURCE is set
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 2186, in 
test_190_config_kernel_fortify
    self.assertTrue(self._test_config(config_name))
    AssertionError: False is not true

  The CONFIG_FORTIFY_SOURCE is not set.
  $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
  # CONFIG_FORTIFY_SOURCE is not set

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
  ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
  Uname: Linux 4.15.0-1008-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 04:28:13 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1776344] Re: linux-gcp: 4.15.0-1010.10 -proposed tracker

2018-06-22 Thread Brad Figg

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-gcp: 4.15.0-1010.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1690085]

2018-06-22 Thread dagecko

(In reply to Artem Hluvchynskyi from comment #366)
> So AMD has finally published the revision guide for 17h family, which
> includes errata:
> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
> 
> Would be cool if someone with more knowledge about that kind of stuff could
> have a quick look through and see if this issue could be related to anything
> in there. So far "1109 MWAIT Instruction May Hang a Thread" sounds somewhat
> related.

"1033 A Lock Operation May Cause the System to Hang" seems also related
since some logs were refering about locking issues.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package:

[Kernel-packages] [Bug 1690085]

2018-06-22 Thread castro8583bennett

Hello James, does this issue already fixed? If not, do we have other
sources sources that might help this to be fixed? Thank you!

Carlo B.
https://ultimatewebtraffic.com/

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this

[Kernel-packages] [Bug 1777779] Re: ubuntu_ltp_syscalls test will hang in the end on T/X AWS

This will hang with X-generic on AWS cloud as well, but not X-generic on
our bare-metals

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

Title:
  ubuntu_ltp_syscalls test will hang in the end on T/X AWS

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

Bug description:
  The ubuntu_ltp_syscalls test will hang on Trusty (and Xenial) AWS,
  even though all the tests have been ran.

    INFO: ltp-pan reported some tests FAIL
    LTP Version: 20180515

  ###

    Done executing testcases.
    LTP Version:  20180515
   ###
    stderr:
    rm: cannot remove ‘/tmp/ltp-X72GtnsMYy/Q4ynCy/mntpoint’: Device or resource 
busy
  10:19:14 INFO |   END ERROR   ubuntu_ltp_syscalls.syscalls
ubuntu_ltp_syscalls.syscallstimestamp=1529403554localtime=Jun 19 
10:19:14
  10:19:14 DEBUG| Persistent state client._record_indent now set to 1
  10:19:14 DEBUG| Persistent state client.unexpected_reboot deleted
  10:19:14 INFO | END GOOD  timestamp=1529403554
localtime=Jun 19 10:19:14
  10:19:14 DEBUG| Persistent state client._record_indent now set to 0
  10:19:14 INFO | Report successfully generated at 
/home/ubuntu/autotest/client/results/default/job_report.html

  If you log onto the node, you will see a zombie process. The jenkins
  job will continue when you have that zombie process's parent killed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-1024-aws 4.4.0-1024.25
  ProcVersionSignature: User Name 4.4.0-1024.25-aws 4.4.134
  Uname: Linux 4.4.0-1024-aws x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Jun 20 05:58:27 2018
  Ec2AMI: ami-221f5c5a
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: c3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T kernel