[Kernel-packages] [Bug 1194305] Re: Joystick Trust 16784 detected on js0 but unresponsive

[Timo Aaltonen]

note that the only use for x-x-i-joystick is if you want to move the
cursor with the joystick instead the mouse... it's not needed for games
etc

** Package changed: xserver-xorg-input-joystick (Ubuntu) => linux
(Ubuntu)

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

Title:
  Joystick Trust 16784 detected on js0 but unresponsive

Status in linux package in Ubuntu:
  Incomplete
Status in Fedora:
  Won't Fix

Bug description:
  On Ubuntu 13.04
  Trust 16784 joystick is detected on /dev/input/js0, but if i cat it i don't 
get any input (this is a simple way to test an input device: if pressing 
buttons you see scrambled characters, it works). Also, any calibration program 
detects it but can't get any axis or button.
  After connecting it, the leds start to blink. Pressing the home button makes 
them steady, but nothing changes. That's to show the device is turned on. 
  On Windows it works normally.

  Tried it on Asus X501A laptop, both on usb2 and usb3 port.
  I'm using latest xserver-xorg-input-joystick (1:1.6.1-1build1) and latest 
kernel (3.8.0-25.37), with every joystick-related package installed.

  I attached some informations on this device

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

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

[Kernel-packages] [Bug 1072343] [NEW] Sidewinder X4 Macro Keys not working

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,

I've been sent here from brainstorm. I'm bought a Sidewinder X4, a very
popular low price keyboard USB Keyboard which works fine except for the
Macro keys, which don't work at all. It would be cool if you could fully
support it, especially since gaming will become more important to ubuntu
in the next few months than ever. And it's always a K.O. criteria for
gamers, when they can't use the peripherals they bought.

Regards,

Kay

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: gaming keyboard keys macro macros sidewinder support x4
-- 
Sidewinder X4 Macro Keys not working
https://bugs.launchpad.net/bugs/1072343
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1196234] [NEW] Maxkeyboard CapsLock LED issue

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

i'm using Maxkeyboard X9.

1224445.116407] usb 1-1.2: New USB device found, idVendor=05e3, idProduct=0608
[1224445.116414] usb 1-1.2: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
[1224445.116418] usb 1-1.2: Product: USB2.0 Hub
[1224445.117041] hub 1-1.2:1.0: USB hub found
[1224445.117483] hub 1-1.2:1.0: 4 ports detected
[1224445.390287] usb 1-1.2.2: new full-speed USB device number 28 using ehci-pci
[1224445.485808] usb 1-1.2.2: New USB device found, idVendor=0665, 
idProduct=6000
[1224445.485818] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[1224445.485823] usb 1-1.2.2: Product: Gaming keyboard
[1224445.485827] usb 1-1.2.2: Manufacturer: EST
[1224445.487341] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input64
[1224445.487704] hid-generic 0003:0665:6000.0028: input,hidraw2: USB HID v1.11 
Keyboard [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input0
[1224445.488773] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.1/input/input65
[1224445.489088] hid-generic 0003:0665:6000.0029: input,hidraw3: USB HID v1.11 
Device [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input1
[1224445.490269] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.2/input/input66
[1224445.490651] hid-generic 0003:0665:6000.002A: input,hidraw4: USB HID v1.11 
Keyboard [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input2

There is some issue with CapsLock LED - it doesnt work when i press the
caps button. but it works correctly with this command

# setleds -D +caps
# setleds -D -caps

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-input-kbd (not installed)
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sun Jun 30 16:49:00 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
InstallationDate: Installed on 2013-04-14 (76 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
MachineType: LENOVO 3626NP4
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-generic 
root=UUID=3a482650-c2b6-4c1b-9321-c32b8bac41d2 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-keyboard
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET62WW (1.32 )
dmi.board.name: 3626NP4
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6QET62WW(1.32):bd12/17/2010:svnLENOVO:pn3626NP4:pvrThinkPadX201:rvnLENOVO:rn3626NP4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3626NP4
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1
xserver.bootTime: Fri Jun 21 21:43:31 2013
xserver.configfile: default
xserver.errors: evdev: Microsoft® LifeCam HD-3000: Unable to open evdev device 
"/dev/input/event16".
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.3-0ubuntu6
xserver.video_driver: intel

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


** Tags: amd64 apport-bug raring ubuntu
-- 
Maxkeyboard CapsLock LED issue
https://bugs.launchpad.net/bugs/1196234
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1843118] Re: bionic/linux-gcp: 4.15.0-1042.45 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Promote to Security
- phase-changed: Wednesday, 11. September 2019 06:41 UTC
+ phase: Complete
+ phase-changed: Wednesday, 11. September 2019 06:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Ongoing -- packages not yet published
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

Title:
  bionic/linux-gcp: 4.15.0-1042.45 -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-lrm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Complete
  phase-changed: Wednesday, 11. September 2019 06:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1720563

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

Title:
  8bitdo FC30 Pro controller has 8 axes with firmware 4.00

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This controller only has 6 axes, but Ubuntu sees 8. The extra two look
  like pedals in jstest-gtk, and their input values get maxed out when I
  press left or right on the D-pad, or the L2 or R2 buttons.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1720561

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

Title:
  8bitdo FC30 Pro controller undetected with firmware 4.01

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When this controller was on firmware version 4.00, I was able to
  construct a udev rule so that Ubuntu could use it, although it did see
  2 more axes than the controller actually had -- might file another bug
  for that.

  Now that I've upgraded to firmware version 4.01, the controller's USB
  IDs are the same, but it never gets assigned a device file for some
  reason. I can't use it at all.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1194305

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

Title:
  Joystick Trust 16784 detected on js0 but unresponsive

Status in linux package in Ubuntu:
  Incomplete
Status in Fedora:
  Won't Fix

Bug description:
  On Ubuntu 13.04
  Trust 16784 joystick is detected on /dev/input/js0, but if i cat it i don't 
get any input (this is a simple way to test an input device: if pressing 
buttons you see scrambled characters, it works). Also, any calibration program 
detects it but can't get any axis or button.
  After connecting it, the leds start to blink. Pressing the home button makes 
them steady, but nothing changes. That's to show the device is turned on. 
  On Windows it works normally.

  Tried it on Asus X501A laptop, both on usb2 and usb3 port.
  I'm using latest xserver-xorg-input-joystick (1:1.6.1-1build1) and latest 
kernel (3.8.0-25.37), with every joystick-related package installed.

  I attached some informations on this device

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

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

[Kernel-packages] [Bug 786955] Re: Saulabi 4K Joystick (Buttons not working)

[Timo Aaltonen]

the bug is/was in the kernel, reopen if it still happens in 19.10

** Package changed: xserver-xorg-input-joystick (Ubuntu) => linux
(Ubuntu)

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

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

Title:
  Saulabi 4K Joystick (Buttons not working)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xserver-xorg-input-joystick

  Description:  Ubuntu 10.10
  Release:  10.10

  Directions: UP,DOWN,LEFT,RIGHT (Working)
  Buttons: 1,2,3,4,5,6,7,8,9,10 (Nothing)

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

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

[Kernel-packages] [Bug 1843533] Re: powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-

[Frank Heimes]

The commits went upstream with v5.3-rc8, hence they are both in Eoan's 
master-next tree (just checked) and are already available via the current eoan 
proposed kernel:
linux-generic | 5.3.0.10.11   | eoan-proposed   | s390x

Hence an SRU for Disco and Bionic is now needed.

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

Title:
  powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts
  (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions
  inside a transaction (CVE-2019-15030)

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

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-09-11 
00:49:28 ==
  There are two problems/CVEs for power that we'd appreciate adding:

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

  powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts

  When in userspace and MSR FP=0 the hardware FP state is unrelated to
  the current process. This is extended for transactions where if tbegin
  is run with FP=0, the hardware checkpoint FP state will also be
  unrelated to the current process. Due to this, we need to ensure this
  hardware checkpoint is updated with the correct state before we enable
  FP for this process.

  Unfortunately we get this wrong when returning to a process from a
  hardware interrupt. A process that starts a transaction with FP=0 can
  take an interrupt. When the kernel returns back to that process, we
  change to FP=1 but with hardware checkpoint FP state not updated. If
  this transaction is then rolled back, the FP registers now contain the
  wrong state.

  The process looks like this:
 Userspace:  Kernel

 Start userspace
  with MSR FP=0 TM=1
< -
 ...
 tbegin
 bne
 Hardware interrupt
  >
  
  
  ret_from_except
restore_math()
/* sees FP=0 */
  restore_fp()
tm_active_with_fp()
/* sees FP=1 (Incorrect) */
load_fp_state()
  FP = 0 -> 1
< -
 Return to userspace
   with MSR TM=1 FP=1
   with junk in the FP TM checkpoint
 TM rollback
 reads FP junk

  When returning from the hardware exception, tm_active_with_fp() is
  incorrectly making restore_fp() call load_fp_state() which is setting
  FP=1.

  The fix is to remove tm_active_with_fp().

  tm_active_with_fp() is attempting to handle the case where FP state
  has been changed inside a transaction. In this case the checkpointed
  and transactional FP state is different and hence we must restore the
  FP state (ie. we can't do lazy FP restore inside a transaction that's
  used FP). It's safe to remove tm_active_with_fp() as this case is
  handled by restore_tm_state(). restore_tm_state() detects if FP has
  been using inside a transaction and will set load_fp and call
  restore_math() to ensure the FP state (checkpoint and transaction) is
  restored.

  This is a data integrity problem for the current process as the FP
  registers are corrupted. It's also a security problem as the FP
  registers from one process may be leaked to another.

  Similarly for VMX.

  A simple testcase to replicate this will be posted to
  tools/testing/selftests/powerpc/tm/tm-poison.c

  This fixes CVE-2019-15031.

  Fixes: a7771176b439 ("powerpc: Don't enable FP/Altivec if not checkpointed")
  Cc: sta...@vger.kernel.org # 4.15+
  Signed-off-by: Gustavo Romero 
  Signed-off-by: Michael Neuling 
  Signed-off-by: Michael Ellerman 
  Link: 
https://lore.kernel.org/r/20190904045529.23002-2-grom...@linux.vnet.ibm.com
  .
  2.
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8205d5d98ef7f155de211f5e2eb6ca03d95a5a60

  powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction

  When we take an FP unavailable exception in a transaction we have to
  account for the hardware FP TM checkpointed registers being
  incorrect. In this case for this process we know the current and
  checkpointed FP registers must be the same (since FP wasn't used
  inside the transaction) hence in the thread_struct we copy the current
  FP registers to the checkpointed ones.

  This copy is done in tm_reclaim_thread(). We use thread->ckpt_regs.msr
  to determine if FP was on when in userspace. thread->ckpt_regs.msr
  represents the state o

[Kernel-packages] [Bug 1196234] Re: Maxkeyboard CapsLock LED issue

[Timo Aaltonen]

** Package changed: xserver-xorg-input-keyboard (Ubuntu) => linux
(Ubuntu)

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

Title:
  Maxkeyboard CapsLock LED issue

Status in linux package in Ubuntu:
  New

Bug description:
  i'm using Maxkeyboard X9.

  1224445.116407] usb 1-1.2: New USB device found, idVendor=05e3, idProduct=0608
  [1224445.116414] usb 1-1.2: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [1224445.116418] usb 1-1.2: Product: USB2.0 Hub
  [1224445.117041] hub 1-1.2:1.0: USB hub found
  [1224445.117483] hub 1-1.2:1.0: 4 ports detected
  [1224445.390287] usb 1-1.2.2: new full-speed USB device number 28 using 
ehci-pci
  [1224445.485808] usb 1-1.2.2: New USB device found, idVendor=0665, 
idProduct=6000
  [1224445.485818] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1224445.485823] usb 1-1.2.2: Product: Gaming keyboard
  [1224445.485827] usb 1-1.2.2: Manufacturer: EST
  [1224445.487341] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input64
  [1224445.487704] hid-generic 0003:0665:6000.0028: input,hidraw2: USB HID 
v1.11 Keyboard [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input0
  [1224445.488773] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.1/input/input65
  [1224445.489088] hid-generic 0003:0665:6000.0029: input,hidraw3: USB HID 
v1.11 Device [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input1
  [1224445.490269] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.2/input/input66
  [1224445.490651] hid-generic 0003:0665:6000.002A: input,hidraw4: USB HID 
v1.11 Keyboard [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input2

  There is some issue with CapsLock LED - it doesnt work when i press
  the caps button. but it works correctly with this command

  # setleds -D +caps
  # setleds -D -caps

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-input-kbd (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Sun Jun 30 16:49:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  InstallationDate: Installed on 2013-04-14 (76 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MachineType: LENOVO 3626NP4
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-generic 
root=UUID=3a482650-c2b6-4c1b-9321-c32b8bac41d2 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET62WW (1.32 )
  dmi.board.name: 3626NP4
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET62WW(1.32):bd12/17/2010:svnLENOVO:pn3626NP4:pvrThinkPadX201:rvnLENOVO:rn3626NP4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3626NP4
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Fri Jun 21 21:43:31 2013
  xserver.configfile: default
  xserver.errors: evdev: Microsoft® LifeCam HD-3000: Unable to open evdev 
device "/dev/input/event16".
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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

[Kernel-packages] [Bug 1072343] Re: Sidewinder X4 Macro Keys not working

[Timo Aaltonen]

** Package changed: xserver-xorg-input-keyboard (Ubuntu) => linux
(Ubuntu)

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

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

Title:
  Sidewinder X4 Macro Keys not working

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I've been sent here from brainstorm. I'm bought a Sidewinder X4, a
  very popular low price keyboard USB Keyboard which works fine except
  for the Macro keys, which don't work at all. It would be cool if you
  could fully support it, especially since gaming will become more
  important to ubuntu in the next few months than ever. And it's always
  a K.O. criteria for gamers, when they can't use the peripherals they
  bought.

  Regards,

  Kay

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

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

[Kernel-packages] [Bug 1840236]

[Jani-saarinen-g]

You mean Lakshmi if 103167 is same?

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  SRU Justification:

  [Impact]
  On IceLake platforms there might be a thin, horizon strap of corruption
  image at the top of screen randomly after some series of window
  operations and disappears within a second or so. This is found on
  multiple platforms and is quite annonying that results in bad user
  experience.

  [Fix]
  The upstream bug has been filed for previous platforms, e.g. GeminiLake
  for an year or so, still working in progress, and so far this only known
  work-around is to turn off framebuffer compression on affected platforms.

  [Test Case]
  The most easy way is to observe if such corruption appears during the
  transition from GDM to gnome-shell.

  [Regression Risk]
  Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
  and has been backported to B/D.

  === Original Description ==

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1840236]

[Lakshminarayana-vudum]

@Maarten, Is this issue related to Bug 111484? Since you investigated
Bug 111484 any suggestions here?

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  SRU Justification:

  [Impact]
  On IceLake platforms there might be a thin, horizon strap of corruption
  image at the top of screen randomly after some series of window
  operations and disappears within a second or so. This is found on
  multiple platforms and is quite annonying that results in bad user
  experience.

  [Fix]
  The upstream bug has been filed for previous platforms, e.g. GeminiLake
  for an year or so, still working in progress, and so far this only known
  work-around is to turn off framebuffer compression on affected platforms.

  [Test Case]
  The most easy way is to observe if such corruption appears during the
  transition from GDM to gnome-shell.

  [Regression Risk]
  Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
  and has been backported to B/D.

  === Original Description ==

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Maxkeyboard CapsLock LED issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i'm using Maxkeyboard X9.

  1224445.116407] usb 1-1.2: New USB device found, idVendor=05e3, idProduct=0608
  [1224445.116414] usb 1-1.2: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [1224445.116418] usb 1-1.2: Product: USB2.0 Hub
  [1224445.117041] hub 1-1.2:1.0: USB hub found
  [1224445.117483] hub 1-1.2:1.0: 4 ports detected
  [1224445.390287] usb 1-1.2.2: new full-speed USB device number 28 using 
ehci-pci
  [1224445.485808] usb 1-1.2.2: New USB device found, idVendor=0665, 
idProduct=6000
  [1224445.485818] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1224445.485823] usb 1-1.2.2: Product: Gaming keyboard
  [1224445.485827] usb 1-1.2.2: Manufacturer: EST
  [1224445.487341] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input64
  [1224445.487704] hid-generic 0003:0665:6000.0028: input,hidraw2: USB HID 
v1.11 Keyboard [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input0
  [1224445.488773] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.1/input/input65
  [1224445.489088] hid-generic 0003:0665:6000.0029: input,hidraw3: USB HID 
v1.11 Device [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input1
  [1224445.490269] input: EST Gaming keyboard as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.2/input/input66
  [1224445.490651] hid-generic 0003:0665:6000.002A: input,hidraw4: USB HID 
v1.11 Keyboard [EST Gaming keyboard] on usb-:00:1a.0-1.2.2/input2

  There is some issue with CapsLock LED - it doesnt work when i press
  the caps button. but it works correctly with this command

  # setleds -D +caps
  # setleds -D -caps

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-input-kbd (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Sun Jun 30 16:49:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  InstallationDate: Installed on 2013-04-14 (76 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MachineType: LENOVO 3626NP4
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-generic 
root=UUID=3a482650-c2b6-4c1b-9321-c32b8bac41d2 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET62WW (1.32 )
  dmi.board.name: 3626NP4
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET62WW(1.32):bd12/17/2010:svnLENOVO:pn3626NP4:pvrThinkPadX201:rvnLENOVO:rn3626NP4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3626NP4
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Fri Jun 21 21:43:31 2013
  xserver.configfile: default
  xserver.errors: evdev: Microsoft® LifeCam HD-3000: Unable to open evdev 
device "/dev/input/event16".
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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

[Kernel-packages] [Bug 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380

[Alex Tu]

Hi saviq,

Followed #7, the machine can S2I well, then after I installing multipass
again without running any instance, the S2I will fail.

hmm, it could be an issue of KVM, I will check that when I have spare
time.

Btw, the S2I will not be impacted with virtual box
6.0.12-133076~Ubuntu~bionic , but it's not using KVM anyway.

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

Title:
  linux-oem 4.15 can not suspend to idle XPS-13-9380

Status in OEM Priority Project:
  New
Status in linux-signed-oem package in Ubuntu:
  New

Bug description:
  it somehow s2i failed, from message , it seems the s2i process be
  blocked by thunderbolt device.

  dmesg:
  [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193141.012736] PM: noirq suspend of devices failed
  [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809
  [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118
  [193141.872317] thunderbolt :05:00.0: control channel starting...

  Not sure is it relative that I hot plug out WD19 docking before
  suspend.

  reproduce rate:
  random

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50
  ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18
  Uname: Linux 4.15.0-1045-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 00:02:08 2019
  InstallationDate: Installed on 2019-08-11 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed-oem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1840484/+subscriptions

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

[Kernel-packages] [Bug 1781879]

[qiao.bo]

This problem is not completely resolved: touchpad is not full functional
after waking from suspend. This has been confirmed by multiple users as
reported in #201175.

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

Title:
  Latest ASUS trackpad doesn't work in Ubuntu

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

Bug description:
  It seems there might be a new hardware variant of the elan trackpad in
  the newer ASUS machines.

  The issue is the shown here with some reasonably deep investigation.
  Is this something that I can do or am I reduced to having to find out
  a mouse if I want to use Linux?

  https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

  user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
   Virtual core pointer  id=2[master pointer  (3)]
     ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
     ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
     ↳ Logitech USB Receiver id=13   [slave  pointer  (2)]
   Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Video Bus id=9[slave  keyboard (3)]
  ↳ Power Button  id=10   [slave  keyboard (3)]
  ↳ Sleep Button  id=11   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=14   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=15   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
  ↳ Logitech USB Receiver id=17   [slave  keyboard (3)]

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

-- 
Mailing list: https://launchpad.net/~kernel-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]

[belliash]

And another example of calltrace:

Sep  5 21:25:32 BelliashPC kernel: NMI backtrace for cpu 1
Sep  5 21:25:32 BelliashPC kernel: CPU: 1 PID: 13564 Comm: DOM File Tainted: P  
DOT 5.2.11-gentoo #1
Sep  5 21:25:32 BelliashPC kernel: Hardware name: Gigabyte Technology Co., Ltd. 
B450 AORUS ELITE/B450 AORUS ELITE, BIOS F42a 07/31/2019
Sep  5 21:25:32 BelliashPC kernel: Call Trace:
Sep  5 21:25:32 BelliashPC kernel:  
Sep  5 21:25:32 BelliashPC kernel:  dump_stack+0x46/0x60
Sep  5 21:25:32 BelliashPC kernel:  nmi_cpu_backtrace.cold+0x14/0x53
Sep  5 21:25:32 BelliashPC kernel:  ? lapic_can_unplug_cpu.cold+0x42/0x42
Sep  5 21:25:32 BelliashPC kernel:  nmi_trigger_cpumask_backtrace+0x89/0x8b
Sep  5 21:25:32 BelliashPC kernel:  rcu_dump_cpu_stacks+0x7b/0xa9
Sep  5 21:25:32 BelliashPC kernel:  rcu_sched_clock_irq.cold+0x1a2/0x38d
Sep  5 21:25:32 BelliashPC kernel:  ? tick_sched_do_timer+0x50/0x50
Sep  5 21:25:32 BelliashPC kernel:  update_process_times+0x24/0x60
Sep  5 21:25:32 BelliashPC kernel:  tick_sched_timer+0x33/0x70
Sep  5 21:25:32 BelliashPC kernel:  __hrtimer_run_queues+0xe7/0x180
Sep  5 21:25:32 BelliashPC kernel:  hrtimer_interrupt+0x100/0x220
Sep  5 21:25:32 BelliashPC kernel:  smp_apic_timer_interrupt+0x56/0x90
Sep  5 21:25:32 BelliashPC kernel:  apic_timer_interrupt+0xf/0x20
Sep  5 21:25:32 BelliashPC kernel:  
Sep  5 21:25:32 BelliashPC kernel: RIP: 
0010:queued_spin_lock_slowpath+0x3f/0x1a0
Sep  5 21:25:32 BelliashPC kernel: Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 
89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 18 85 c0 74 0e 8b 07 84 c0 74 08 f3 
90 8b 07 <84> c0 75 f8 66 c7 07 01 00 c3 f6 c4 01 75 04 c6 47 01 00 48 c7 c0
Sep  5 21:25:32 BelliashPC kernel: RSP: 0018:a299085afc48 EFLAGS: 0202 
ORIG_RAX: ff13
Sep  5 21:25:32 BelliashPC kernel: RAX: 003c0101 RBX: a299085afd10 
RCX: 8a2ee8ff
Sep  5 21:25:32 BelliashPC kernel: RDX:  RSI:  
RDI: a299034fdb44
Sep  5 21:25:32 BelliashPC kernel: RBP: a299085afcc0 R08: a299085afcc0 
R09: 
Sep  5 21:25:32 BelliashPC kernel: R10:  R11:  
R12: 7fa4d675aa38
Sep  5 21:25:32 BelliashPC kernel: R13:  R14:  
R15: a299034fdb40
Sep  5 21:25:32 BelliashPC kernel:  futex_wait_setup+0x77/0x110
Sep  5 21:25:32 BelliashPC kernel:  futex_wait+0xcf/0x230
Sep  5 21:25:32 BelliashPC kernel:  ? ep_poll_callback+0x256/0x280
Sep  5 21:25:32 BelliashPC kernel:  do_futex+0x15e/0xc60
Sep  5 21:25:32 BelliashPC kernel:  ? pipe_write+0x382/0x410
Sep  5 21:25:32 BelliashPC kernel:  ? new_sync_write+0x12c/0x1d0
Sep  5 21:25:32 BelliashPC kernel:  __x64_sys_futex+0x137/0x170
Sep  5 21:25:32 BelliashPC kernel:  do_syscall_64+0x4a/0x110
Sep  5 21:25:32 BelliashPC kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep  5 21:25:32 BelliashPC kernel: RIP: 0033:0x7fa4e76c7067
Sep  5 21:25:32 BelliashPC kernel: Code: 5c 24 68 48 89 44 24 50 e8 96 38 00 00 
e8 c1 3d 00 00 89 de 41 89 c1 40 80 f6 80 45 31 d2 31 d2 4c 89 ff b8 ca 00 00 
00 0f 05 <48> 3d 00 f0 ff ff 77 71 44 89 cf e8 f9 3d 00 00 31 f6 4c 89 f7 e8
Sep  5 21:25:32 BelliashPC kernel: RSP: 002b:7fa4d7c5eac0 EFLAGS: 0246 
ORIG_RAX: 00ca
Sep  5 21:25:32 BelliashPC kernel: RAX: ffda RBX:  
RCX: 7fa4e76c7067
Sep  5 21:25:32 BelliashPC kernel: RDX:  RSI: 0080 
RDI: 7fa4d675aa38
Sep  5 21:25:32 BelliashPC kernel: RBP:  R08: 7fa4d675a9e0 
R09: 
Sep  5 21:25:32 BelliashPC kernel: R10:  R11: 0246 
R12: 7fa4d675aa10
Sep  5 21:25:32 BelliashPC kernel: R13: 7fa4d675a9e0 R14: 7fa4d7c5eaf0 
R15: 7fa4d675aa38

-- 
You 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 CP

[Kernel-packages] [Bug 1690085]

[belliash]

This happened also w/o vbox (I installed it few days ago) and nvidia
proprietary drivers. I used to use nouveau with the same results. I will
open a new ticket.

-- 
You 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 bug go to:
h

[Kernel-packages] [Bug 1690085]

[bp]

> Sep 10 21:13:56 BelliashPC kernel: Workqueue:  0x0 (events)
> Sep 10 21:13:56 BelliashPC kernel: RIP: 0010:worker_thread+0xfc/0x3b0
> Sep 10 21:13:56 BelliashPC kernel: Code: 0f 84 8e 02 00 00 48 8b 4c 24 18 49
> 39 4f 38 0f 85 a9 02 00 00 83 e0 fb 41 89 47 60 ff 4a 34 49 8b 17 49 8b 47
> 08 48 89 42 08 <48> 89 10 4d 89 3f 4d 89 7f 08 48 8b 45 20 4c 8d 6d 20 49 39
> c5 74
> Sep 10 21:13:56 BelliashPC kernel: RSP: 0018:aec608acfec0 EFLAGS:
> 00010002
> Sep 10 21:13:56 BelliashPC kernel: RAX: 000d RBX:
> 8d78aecdfa80 RCX: 8d789fa1b400
> Sep 10 21:13:56 BelliashPC kernel: RDX: 8d78a4112780 RSI:
> 8d78a91e56c0 RDI: 8d78aecdfa80
> Sep 10 21:13:56 BelliashPC kernel: RBP: 8d78aecdfa80 R08:
> 8d78aece0180 R09: 1800
> Sep 10 21:13:56 BelliashPC kernel: R10:  R11:
>  R12: 8d78a4112b68
> Sep 10 21:13:56 BelliashPC kernel: R13: 8d78aecdfaa0 R14:
> 8d78a4112b40 R15: 8d78a4112b40
> Sep 10 21:13:56 BelliashPC kernel: FS:  ()
> GS:8d78aecc() knlGS:
> Sep 10 21:13:56 BelliashPC kernel: CS:  0010 DS:  ES:  CR0:
> 80050033
> Sep 10 21:13:56 BelliashPC kernel: CR2: 00b0 CR3:
> 00069063a000 CR4: 00340ee0
> Sep 10 21:13:56 BelliashPC kernel: Call Trace:
> Sep 10 21:13:56 BelliashPC kernel:  kthread+0xf8/0x130
> Sep 10 21:13:56 BelliashPC kernel:  ? set_worker_desc+0xb0/0xb0
> Sep 10 21:13:56 BelliashPC kernel:  ? kthread_park+0x80/0x80
> Sep 10 21:13:56 BelliashPC kernel:  ret_from_fork+0x22/0x40
> Sep 10 21:13:56 BelliashPC kernel: Modules linked in: nvidia_drm(PO)
> nvidia_modeset(PO) nvidia(PO) vboxpci(O) vboxnetadp(O) vboxnetflt(O)
> vboxdrv(O)

You have proprietary crap loaded.

Try reproducing it with the latest upstream kernel and *without* that
nvidia* and vbox* gunk.

If you can, please open a separate bug and add me to CC.

Thx.

-- 
You 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

[Kernel-packages] [Bug 1690085]

[belliash]

Sep 10 21:13:56 BelliashPC kernel: BUG: kernel NULL pointer dereference, 
address: 000d
Sep 10 21:13:56 BelliashPC kernel: #PF: supervisor write access in kernel mode
Sep 10 21:13:56 BelliashPC kernel: #PF: error_code(0x0002) - not-present page
Sep 10 21:13:56 BelliashPC kernel: PGD 0 P4D 0 
Sep 10 21:13:56 BelliashPC kernel: Oops: 0002 [#1] SMP NOPTI
Sep 10 21:13:56 BelliashPC kernel: CPU: 11 PID: 30804 Comm: kworker/11:2 
Tainted: P   OT 5.2.13-gentoo #1
Sep 10 21:13:56 BelliashPC kernel: Hardware name: Gigabyte Technology Co., Ltd. 
B450 AORUS ELITE/B450 AORUS ELITE, BIOS F42a 07/31/2019
Sep 10 21:13:56 BelliashPC kernel: Workqueue:  0x0 (events)
Sep 10 21:13:56 BelliashPC kernel: RIP: 0010:worker_thread+0xfc/0x3b0
Sep 10 21:13:56 BelliashPC kernel: Code: 0f 84 8e 02 00 00 48 8b 4c 24 18 49 39 
4f 38 0f 85 a9 02 00 00 83 e0 fb 41 89 47 60 ff 4a 34 49 8b 17 49 8b 47 08 48 
89 42 08 <48> 89 10 4d 89 3f 4d 89 7f 08 48 8b 45 20 4c 8d 6d 20 49 39 c5 74
Sep 10 21:13:56 BelliashPC kernel: RSP: 0018:aec608acfec0 EFLAGS: 00010002
Sep 10 21:13:56 BelliashPC kernel: RAX: 000d RBX: 8d78aecdfa80 
RCX: 8d789fa1b400
Sep 10 21:13:56 BelliashPC kernel: RDX: 8d78a4112780 RSI: 8d78a91e56c0 
RDI: 8d78aecdfa80
Sep 10 21:13:56 BelliashPC kernel: RBP: 8d78aecdfa80 R08: 8d78aece0180 
R09: 1800
Sep 10 21:13:56 BelliashPC kernel: R10:  R11:  
R12: 8d78a4112b68
Sep 10 21:13:56 BelliashPC kernel: R13: 8d78aecdfaa0 R14: 8d78a4112b40 
R15: 8d78a4112b40
Sep 10 21:13:56 BelliashPC kernel: FS:  () 
GS:8d78aecc() knlGS:
Sep 10 21:13:56 BelliashPC kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Sep 10 21:13:56 BelliashPC kernel: CR2: 00b0 CR3: 00069063a000 
CR4: 00340ee0
Sep 10 21:13:56 BelliashPC kernel: Call Trace:
Sep 10 21:13:56 BelliashPC kernel:  kthread+0xf8/0x130
Sep 10 21:13:56 BelliashPC kernel:  ? set_worker_desc+0xb0/0xb0
Sep 10 21:13:56 BelliashPC kernel:  ? kthread_park+0x80/0x80
Sep 10 21:13:56 BelliashPC kernel:  ret_from_fork+0x22/0x40
Sep 10 21:13:56 BelliashPC kernel: Modules linked in: nvidia_drm(PO) 
nvidia_modeset(PO) nvidia(PO) vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O)
Sep 10 21:13:56 BelliashPC kernel: CR2: 000d
Sep 10 21:13:56 BelliashPC kernel: ---[ end trace 23be40ec0c6dea2a ]---
Sep 10 21:13:56 BelliashPC kernel: RIP: 0010:worker_thread+0xfc/0x3b0
Sep 10 21:13:56 BelliashPC kernel: Code: 0f 84 8e 02 00 00 48 8b 4c 24 18 49 39 
4f 38 0f 85 a9 02 00 00 83 e0 fb 41 89 47 60 ff 4a 34 49 8b 17 49 8b 47 08 48 
89 42 08 <48> 89 10 4d 89 3f 4d 89 7f 08 48 8b 45 20 4c 8d 6d 20 49 39 c5 74
Sep 10 21:13:56 BelliashPC kernel: RSP: 0018:aec608acfec0 EFLAGS: 00010002
Sep 10 21:13:56 BelliashPC kernel: RAX: 000d RBX: 8d78aecdfa80 
RCX: 8d789fa1b400
Sep 10 21:13:56 BelliashPC kernel: RDX: 8d78a4112780 RSI: 8d78a91e56c0 
RDI: 8d78aecdfa80
Sep 10 21:13:56 BelliashPC kernel: RBP: 8d78aecdfa80 R08: 8d78aece0180 
R09: 1800
Sep 10 21:13:56 BelliashPC kernel: R10:  R11:  
R12: 8d78a4112b68
Sep 10 21:13:56 BelliashPC kernel: R13: 8d78aecdfaa0 R14: 8d78a4112b40 
R15: 8d78a4112b40
Sep 10 21:13:56 BelliashPC kernel: FS:  () 
GS:8d78aecc() knlGS:
Sep 10 21:13:56 BelliashPC kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Sep 10 21:13:56 BelliashPC kernel: CR2: 00b0 CR3: 00069063a000 
CR4: 00340ee0
Sep 10 21:14:16 BelliashPC kernel: NVRM: GPU at PCI::06:00: 
GPU-4c9bfa83-5407-92ac-ce82-441bb9e3ac79
Sep 10 21:14:16 BelliashPC kernel: NVRM: GPU Board Serial Number: 
Sep 10 21:14:16 BelliashPC kernel: NVRM: Xid (PCI::06:00): 8, pid=3723, 
Channel 0010
Sep 10 21:14:18 BelliashPC kernel: rcu: INFO: rcu_sched detected stalls on 
CPUs/tasks:
Sep 10 21:14:18 BelliashPC kernel: rcu: \x090-...0: (0 ticks this GP) 
idle=f26/1/0x4000 softirq=1165408/1165408 fqs=5246 
Sep 10 21:14:18 BelliashPC kernel: \x09(detected by 6, t=21002 jiffies, 
g=3474865, q=223)
Sep 10 21:14:18 BelliashPC kernel: Sending NMI from CPU 6 to CPUs 0:
Sep 10 21:14:18 BelliashPC kernel: NMI backtrace for cpu 0
Sep 10 21:14:18 BelliashPC kernel: CPU: 0 PID: 26618 Comm: kworker/0:0 Tainted: 
P  DOT 5.2.13-gentoo #1
Sep 10 21:14:18 BelliashPC kernel: Hardware name: Gigabyte Technology Co., Ltd. 
B450 AORUS ELITE/B450 AORUS ELITE, BIOS F42a 07/31/2019
Sep 10 21:14:18 BelliashPC kernel: Workqueue: events vmstat_shepherd
Sep 10 21:14:18 BelliashPC kernel: RIP: 
0010:queued_spin_lock_slowpath+0x3d/0x1a0
Sep 10 21:14:18 BelliashPC kernel: Code: 3e f0 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 
e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 18 85 c0 74 0e 8b 07 84 c0 74 
08 f3 90 <8b> 07 84 c0 75 f8 66 c7 07 01 00 c3 f6 c4 01 75 04 c6 47 01 00 48
Sep 1

[Kernel-packages] [Bug 1843118] Re: bionic/linux-gcp: 4.15.0-1042.45 -proposed tracker

[Ubuntu Kernel Bot]

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-gcp: 4.15.0-1042.45 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Complete
  phase-changed: Wednesday, 11. September 2019 06:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

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

[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
-   trusty/linux-aws: bug 1842606, bug 1842793
-   trusty/linux-lts-xenial: bug 1842794, bug 1842607
+   trusty/linux-aws: bug 1842793, bug 1842606
+   trusty/linux-lts-xenial: bug 1842607, bug 1842794
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

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

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

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842793, bug 1842606
trusty/linux-lts-xenial: bug 1842607, bug 1842794
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1842819, bug 1842585
+   trusty/linux-azure: bug 1842585, bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1057.62 -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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1842585, bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

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

[Kernel-packages] [Bug 1843232] Re: eoan/linux: 5.3.0-10.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 10. September 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1843231
  variant: debs

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

Title:
  eoan/linux: 5.3.0-10.11 -proposed tracker

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

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

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

  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 10. September 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1843231
  variant: debs

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

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

[Kernel-packages] [Bug 1843018] Re: 5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a container

[Launchpad Bug Tracker]

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 in Ubuntu.
https://bugs.launchpad.net/bugs/1843018

Title:
  5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a
  container

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Using kernel 5.0.0-27-generic on Ubuntu 18.04 in a container, every
  pathname in /proc//maps is / instead of the mapped file path.

  This appears to be a regression in 5.0.0-27-generic; it works on
  5.0.0-25-generic. The problem can be reproduced in various Ubuntu
  releases, e.g. 18.04 and 19.04.

  5.0.0-25-generic (working):

  $ sudo docker run ubuntu cat /proc/1/maps
  56324a3f5000-56324a3fd000 r-xp  fc:01 665673 
/bin/cat
  56324a5fc000-56324a5fd000 r--p 7000 fc:01 665673 
/bin/cat
  56324a5fd000-56324a5fe000 rw-p 8000 fc:01 665673 
/bin/cat
  56324a8eb000-56324a90c000 rw-p  00:00 0  
[heap]
  7f8ab5f91000-7f8ab6178000 r-xp  fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab6178000-7f8ab6378000 ---p 001e7000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab6378000-7f8ab637c000 r--p 001e7000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab637c000-7f8ab637e000 rw-p 001eb000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab637e000-7f8ab6382000 rw-p  00:00 0
  7f8ab6382000-7f8ab63a9000 r-xp  fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab6583000-7f8ab65a7000 rw-p  00:00 0
  7f8ab65a9000-7f8ab65aa000 r--p 00027000 fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab65aa000-7f8ab65ab000 rw-p 00028000 fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab65ab000-7f8ab65ac000 rw-p  00:00 0
  7ffc25954000-7ffc25975000 rw-p  00:00 0  
[stack]
  7ffc259f1000-7ffc259f4000 r--p  00:00 0  
[vvar]
  7ffc259f4000-7ffc259f5000 r-xp  00:00 0  
[vdso]
  ff60-ff601000 r-xp  00:00 0  
[vsyscall]

  5.0.0-27-generic (broken):

  $ sudo docker run ubuntu cat /proc/1/maps
  55de0e052000-55de0e05a000 r-xp  fc:01 665673 /
  55de0e259000-55de0e25a000 r--p 7000 fc:01 665673 /
  55de0e25a000-55de0e25b000 rw-p 8000 fc:01 665673 /
  55de0fcb3000-55de0fcd4000 rw-p  00:00 0  
[heap]
  7f7a8d881000-7f7a8da68000 r-xp  fc:01 666073 /
  7f7a8da68000-7f7a8dc68000 ---p 001e7000 fc:01 666073 /
  7f7a8dc68000-7f7a8dc6c000 r--p 001e7000 fc:01 666073 /
  7f7a8dc6c000-7f7a8dc6e000 rw-p 001eb000 fc:01 666073 /
  7f7a8dc6e000-7f7a8dc72000 rw-p  00:00 0
  7f7a8dc72000-7f7a8dc99000 r-xp  fc:01 666055 /
  7f7a8de73000-7f7a8de97000 rw-p  00:00 0
  7f7a8de99000-7f7a8de9a000 r--p 00027000 fc:01 666055 /
  7f7a8de9a000-7f7a8de9b000 rw-p 00028000 fc:01 666055 /
  7f7a8de9b000-7f7a8de9c000 rw-p  00:00 0
  7ffc744bd000-7ffc744de000 rw-p  00:00 0  
[stack]
  7ffc7452d000-7ffc7453 r--p  00:00 0  
[vvar]
  7ffc7453-7ffc74531000 r-xp  00:00 0  
[vdso]

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

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

[Kernel-packages] [Bug 1842802] Re: bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

[AceLan Kao]

** Summary changed:

- bionic/linux-oem:  -proposed tracker
+ bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

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

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

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

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

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

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

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

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

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

Title:
  bionic/linux-oem: 4.15.0-1055.64 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Packaging
  phase-changed: Wednesday, 11. September 2019 09:20 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842569
  variant: debs

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

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

[Kernel-packages] [Bug 1842802] Re: bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Ready for Packaging
- phase-changed: Tuesday, 10. September 2019 14:00 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 11. September 2019 09:20 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842569
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1055.64 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Packaging
  phase-changed: Wednesday, 11. September 2019 09:20 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842569
  variant: debs

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

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

[Kernel-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Kleber Sacilotto de Souza]

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

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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

[Kernel-packages] [Bug 1842843] Re: bionic/linux-oracle-edge: -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-sru-cycle-2019.09.02-2
** Tags added: kernel-sru-cycle-2019.09.02-1

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

Title:
  bionic/linux-oracle-edge:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842556
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 05:07 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842555
  variant: debs

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

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

[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-sru-cycle-2019.09.02-2
** Tags added: kernel-sru-cycle-2019.09.02-1

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

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

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 16:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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

[Kernel-packages] [Bug 1842812] Re: bionic/linux-ibm-gt: 4.15.0-1036.38 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 09. September 2019 08:46 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 11. September 2019 10:02 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review
  replaces: bug 1842579
  variant: debs

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:02 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  replaces: bug 1842579
  variant: debs

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Holding before Promote to Proposed
- phase-changed: Friday, 06. September 2019 10:26 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 11. September 2019 09:58 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa meta:failed
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1842838] Re: bionic/linux-gcp: -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-sru-cycle-2019.09.02-2
** Tags added: kernel-sru-cycle-2019.09.02-1

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

Title:
  bionic/linux-gcp:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842590
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Packaging
  phase-changed: Monday, 09. September 2019 04:51 UTC
  reason:
prepare-package: Pending -- version not specified
  replaces: bug 1842549
  trackers:
bionic/linux-gcp-edge: bug 1842837
bionic/linux-gcp/gcp-kernel: bug 1842836
  variant: debs

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

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

[Kernel-packages] [Bug 1842585] Re: trusty/linux-azure: -proposed tracker

[Stefan Bader]

** Tags removed: kernel-sru-backport-of-1842587

** Tags added: kernel-sru-backport-of-1842587

** Tags removed: kernel-sru-backport-of-1842587

** Tags added: kernel-sru-backport-of-1842587

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

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

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

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

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

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

Title:
  trusty/linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842587
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Packaging
  phase-changed: Friday, 06. September 2019 05:47 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ł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 in Ubuntu.
https://bugs.launchpad.net/bugs/1842828

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 11. September 2019 09:58 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1842793] Re: trusty/linux-aws: -proposed tracker

[Stefan Bader]

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

** Tags removed: kernel-sru-cycle-2019.09.02-2

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

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

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

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

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

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

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

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

Title:
  trusty/linux-aws:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Packaging
  phase-changed: Friday, 06. September 2019 05:35 UTC
  reason:
prepare-package: Pending -- version not specified
  replaces: bug 1842606
  variant: debs

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

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

[Kernel-packages] [Bug 1840882] Re: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources

[AaronMa]

Tested on 5.0.0-28.30, no suspicious interrupts during s2idle.

mark verified done on disco kernel.

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

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

Title:
  [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses
  shared power resources

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

Bug description:
  SRU justification:

  [Impact]
  When system goes to suspend-to idle, it's power consumption is around 4+ w.

  [Fix]
  Some TBT and other ACPI devices share the same power resource, when system 
goes to s2idle.
  PME polling thread continue bringing up devices to D0 mode.
  Use cached ACPI device power state will avoid this issue.

  [Test]
  Verified on 2 hardware. Tests result are good.

  [Regression Potential]
  Medium, upstream patches cherry-picked.

  Since these hareware is only supported by 5.0+ kernel, I set B-OEM-
  OSP1 and disco+ kernel tag.

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

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

[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker

[Stefan Bader]

Confirmed with ppisati that this kernel is supposed to be fixed and
booting. So unblocking.

** Tags removed: kernel-block-proposed

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

Title:
  bionic/linux-snapdragon: 4.15.0-1062.69 -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:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Promote to Updates
  phase-changed: Wednesday, 11. September 2019 10:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1842712
  variant: debs

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

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

[Kernel-packages] [Bug 1842585] Re: trusty/linux-azure: -proposed tracker

[Stefan Bader]

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

** This bug has been marked a duplicate of bug 1842819
   trusty/linux-azure:  -proposed tracker

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

Title:
  trusty/linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842587
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Packaging
  phase-changed: Friday, 06. September 2019 05:47 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1841722] Re: [SRU][B/OEM-B/OEM-OSP1/D] UBUNTU: SAUCE: enable middle button for one more ThinkPad

[AaronMa]

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

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D] UBUNTU: SAUCE: enable middle button for one
  more ThinkPad

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

Bug description:
  SRU justification:

  [Impact]
  The touchpads of some ThinkPad had a tap middle button.
  But current 5.2- kernel doesn't support it.

  [Fix]
  Add device pnpid to support the middle button on these ThinkPads.

  [Test]
  Verified on 2 hardware. Tests result are good.

  [Regression Potential]
  low, change is limited to speific hardware.

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

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

[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Tags removed: block-proposed-bionic

** Tags removed: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Holding before Promote to Updates
- phase-changed: Monday, 09. September 2019 12:51 UTC
+ phase: Ready for Promote to Updates
+ phase-changed: Wednesday, 11. September 2019 10:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-updates: Stalled -- kernel-block/kernel-block-proposed tag 
present
+   promote-to-updates: Pending -- ready to copy
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1842712
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1062.69 -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:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Promote to Updates
  phase-changed: Wednesday, 11. September 2019 10:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1842712
  variant: debs

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

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

[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-sru-cycle-2019.09.02-1
** Tags added: kernel-sru-cycle-2019.09.02-2

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

Title:
  xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 09. September 2019 04:51 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,signed:depwait
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

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

[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-sru-cycle-2019.09.02-1
** Tags added: kernel-sru-cycle-2019.09.02-2

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

Title:
  xenial/linux-azure: 4.15.0-1057.62 -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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

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

[Kernel-packages] [Bug 1842592] Re: xenial/linux-deeplens: -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-sru-cycle-2019.09.02-1
** Tags added: kernel-sru-cycle-2019.09.02-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/1842592

Title:
  xenial/linux-deeplens:  -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842593
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Holding before Packaging
  phase-changed: Wednesday, 04. September 2019 04:59 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  variant: debs

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

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

[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1842585, bug 1842819
+   trusty/linux-azure: bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1057.62 -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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

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

[Kernel-packages] [Bug 1842580] Re: xenial/linux-oracle: -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-sru-cycle-2019.09.02-1
** Tags added: kernel-sru-cycle-2019.09.02-2

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

Title:
  xenial/linux-oracle:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842814
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Packaging
  phase-changed: Wednesday, 04. September 2019 04:53 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  variant: debs

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

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

[Kernel-packages] [Bug 1843232] Re: eoan/linux: 5.3.0-10.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 10. September 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1843231
  variant: debs

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

Title:
  eoan/linux: 5.3.0-10.11 -proposed tracker

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

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

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

  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 10. September 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1843231
  variant: debs

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ł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 in Ubuntu.
https://bugs.launchpad.net/bugs/1842828

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Pending -- package copies requested to Proposed 
lrm:missing,main:missing,meta:missing,signed:missing
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-snapdragon: 4.15.0-1062.69 -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:
  In Progress
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Promote to Updates
  phase-changed: Wednesday, 11. September 2019 10:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1842712
  variant: debs

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- package copies requested to Proposed 
lrm:missing,main:missing,meta:missing,signed:missing
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Pending -- package copies requested to Proposed 
lrm:missing,main:missing,meta:missing,signed:missing
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog

[Josep Pujadas-Jubany]

Similar problems with Acer TravelMate B118-M that has ElanTech touchpad 
ELAN0502.
My distro is Lubuntu 16.04.6 LTS 64 bit with 4.15.0-60-generic kernel 
(up-to-date).
Tried to upgrade the kernel to latest releases, but it claims for libssl1.1 
(used in 18.04) and 16.04 uses libssl1.0
I tested the laptop with Lubuntu 18.04.3 64bit (USB installation stick) that it 
comes with 5.0.0-23-generic kernel and it works!

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

Title:
  Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The trackpad is working, but syslog is full of kernel errors regarding
  "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id
  data (ff)" if the trackpad is touched.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlku   1269 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Sep 23 15:48:36 2018
  HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561
  InstallationDate: Installed on 2018-09-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80XR
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5RCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IAP
  dmi.modalias: 
dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP:
  dmi.product.family: ideapad 320-15IAP
  dmi.product.name: 80XR
  dmi.product.version: Lenovo ideapad 320-15IAP
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
-   promote-to-proposed: Pending -- package copies requested to Proposed 
lrm:missing,main:missing,meta:missing,signed:missing
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Ready for Promote to Updates
- phase-changed: Wednesday, 11. September 2019 10:25 UTC
+ phase: Holding before Promote to Security
+ phase-changed: Wednesday, 11. September 2019 10:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-updates: Pending -- ready to copy
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1842712
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1062.69 -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:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 11. September 2019 10:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1842712
  variant: debs

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

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

[Kernel-packages] [Bug 1806395] Re: i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)

[Josep Pujadas-Jubany]

Similar problems with Acer TravelMate B118-M that has ElanTech touchpad 
ELAN0502.
My distro is Lubuntu 16.04.6 LTS 64 bit with 4.15.0-60-generic kernel 
(up-to-date).
Tried to upgrade the kernel to latest releases, but it claims for libssl1.1 
(used in 18.04) and 16.04 uses libssl1.0
I tested the laptop with Lubuntu 18.04.3 64bit (USB installation stick) that it 
comes with 5.0.0-23-generic kernel and it works!

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

Title:
  i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report
  (67/65535)

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

Bug description:
  Hello,

  dmesg:
  [   15.337762] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report 
(67/65535)

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2647 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2647 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 10:19:29 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1840571] Re: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+

[Seiichi Nakashima]

Today I update 2 PCs use to software updater.

one PC that is i3-7100 UEFI to use CMS.
I update 2 ubuntu-18.04.3 at /dev/sda1 and /dev/sda2.
I reboot sometimes and shutdown, power on.
do not occur purple screen blink.

another PC that is amd cpu BIOS pc.
I update 2 ubuntu-18.04.3 at /dev/sda1 and /dev/sda3.
maybe /dev/sda3 work fine.
but /dev/sda1 ubuntu-18.04.3 occurs purple screen blink many times by reboot.

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

  I upload syslog file.

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-05-31 (83 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Tags: bionic third-party-packages
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (86 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1355 F pulseaudio
   /dev/snd/controlC1:  nakasima   1355 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (93 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic 
root=UUID=1c4b1b7d-1ae2-412e-ac5e-dca7d317b129 ro ipv6.disable=1 quiet splash 
ipv6.disable=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-27-generic N/A
   linux-backports-modules-5.0.0-27-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
 

[Kernel-packages] [Bug 1843533] Re: powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-

[Frank Heimes]

The commits are already incl. in Eoan master-next,
and with that they are already in eoan-proposed:
linux-generic | 5.3.0.10.11 | eoan-proposed | s390x

Hence SRU for Disco and Bionic is now needed.

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

Title:
  powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts
  (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions
  inside a transaction (CVE-2019-15030)

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

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-09-11 
00:49:28 ==
  There are two problems/CVEs for power that we'd appreciate adding:

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

  powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts

  When in userspace and MSR FP=0 the hardware FP state is unrelated to
  the current process. This is extended for transactions where if tbegin
  is run with FP=0, the hardware checkpoint FP state will also be
  unrelated to the current process. Due to this, we need to ensure this
  hardware checkpoint is updated with the correct state before we enable
  FP for this process.

  Unfortunately we get this wrong when returning to a process from a
  hardware interrupt. A process that starts a transaction with FP=0 can
  take an interrupt. When the kernel returns back to that process, we
  change to FP=1 but with hardware checkpoint FP state not updated. If
  this transaction is then rolled back, the FP registers now contain the
  wrong state.

  The process looks like this:
 Userspace:  Kernel

 Start userspace
  with MSR FP=0 TM=1
< -
 ...
 tbegin
 bne
 Hardware interrupt
  >
  
  
  ret_from_except
restore_math()
/* sees FP=0 */
  restore_fp()
tm_active_with_fp()
/* sees FP=1 (Incorrect) */
load_fp_state()
  FP = 0 -> 1
< -
 Return to userspace
   with MSR TM=1 FP=1
   with junk in the FP TM checkpoint
 TM rollback
 reads FP junk

  When returning from the hardware exception, tm_active_with_fp() is
  incorrectly making restore_fp() call load_fp_state() which is setting
  FP=1.

  The fix is to remove tm_active_with_fp().

  tm_active_with_fp() is attempting to handle the case where FP state
  has been changed inside a transaction. In this case the checkpointed
  and transactional FP state is different and hence we must restore the
  FP state (ie. we can't do lazy FP restore inside a transaction that's
  used FP). It's safe to remove tm_active_with_fp() as this case is
  handled by restore_tm_state(). restore_tm_state() detects if FP has
  been using inside a transaction and will set load_fp and call
  restore_math() to ensure the FP state (checkpoint and transaction) is
  restored.

  This is a data integrity problem for the current process as the FP
  registers are corrupted. It's also a security problem as the FP
  registers from one process may be leaked to another.

  Similarly for VMX.

  A simple testcase to replicate this will be posted to
  tools/testing/selftests/powerpc/tm/tm-poison.c

  This fixes CVE-2019-15031.

  Fixes: a7771176b439 ("powerpc: Don't enable FP/Altivec if not checkpointed")
  Cc: sta...@vger.kernel.org # 4.15+
  Signed-off-by: Gustavo Romero 
  Signed-off-by: Michael Neuling 
  Signed-off-by: Michael Ellerman 
  Link: 
https://lore.kernel.org/r/20190904045529.23002-2-grom...@linux.vnet.ibm.com
  .
  2.
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8205d5d98ef7f155de211f5e2eb6ca03d95a5a60

  powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction

  When we take an FP unavailable exception in a transaction we have to
  account for the hardware FP TM checkpointed registers being
  incorrect. In this case for this process we know the current and
  checkpointed FP registers must be the same (since FP wasn't used
  inside the transaction) hence in the thread_struct we copy the current
  FP registers to the checkpointed ones.

  This copy is done in tm_reclaim_thread(). We use thread->ckpt_regs.msr
  to determine if FP was on when in userspace. thread->ckpt_regs.msr
  represents the state of the MSR when exiting userspace. This is setup
  by check_if_tm_restore_req

[Kernel-packages] [Bug 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380

[Alex Tu]

just installed kvm+virt and initialated a vm instance then do S2I works well.
here list the installed packages version:

Start-Date: 2019-09-11  18:17:24
Commandline: apt-get install -y qemu-kvm libvirt-bin virtinst
Requested-By: alextu (1000)
Install: libusbredirparser1:amd64 (0.7.1-1, automatic), seabios:amd64 
(1.10.2-1ubuntu1, automatic), libgovirt2:amd64 (0.3.4-2, automatic), 
libnl-route-3-200:amd64 (3.2.29-0ubuntu3, automatic), libaugeas0:amd64 
(1.10.1-2, automatic), virtinst:amd64 (1:1.5.1-0ubuntu1.2), osinfo-db:amd64 
(0.20180929-1ubuntu0.1, automatic), ipxe-qemu:amd64 
(1.0.0+git-20180124.fbe8c52d-0ubuntu2.2, automatic), libxml2-utils:amd64 
(2.9.4+dfsg1-6.1ubuntu1.2, automatic), libibverbs1:amd64 (17.1-1ubuntu0.1, 
automatic), libosinfo-1.0-0:amd64 (1.1.0-1, automatic), 
spice-client-glib-usb-acl-helper:amd64 (0.34-1.1build1, automatic), 
msr-tools:amd64 (1.3-2build1, automatic), bridge-utils:amd64 (1.5-15ubuntu1, 
automatic), python-libvirt:amd64 (4.0.0-1, automatic), augeas-lenses:amd64 
(1.10.1-2, automatic), librbd1:amd64 (12.2.12-0ubuntu0.18.04.2, automatic), 
ibverbs-providers:amd64 (17.1-1ubuntu0.1, automatic), qemu-system-x86:amd64 
(1:2.11+dfsg-1ubuntu7.18, automatic), libaio1:amd64 (0.3.110-5ubuntu0.1, 
automatic), ebtables:amd64 (2.0.10.4-3.5ubuntu2.18.04.3, automatic), 
libusbredirhost1:amd64 (0.7.1-1, automatic), libnetcf1:amd64 (1:0.2.8-1ubuntu2, 
automatic), libvirt-clients:amd64 (4.0.0-1ubuntu8.12, automatic), 
librdmacm1:amd64 (17.1-1ubuntu0.1, automatic), libspice-server1:amd64 
(0.14.0-1ubuntu2.4, automatic), libvirt-daemon-driver-storage-rbd:amd64 
(4.0.0-1ubuntu8.12, automatic), libphodav-2.0-common:amd64 (2.2-2, automatic), 
libgovirt-common:amd64 (0.3.4-2, automatic), libvirt-bin:amd64 
(4.0.0-1ubuntu8.12), libxenstore3.0:amd64 (4.9.2-0ubuntu1, automatic), 
libgvnc-1.0-0:amd64 (0.7.2-1, automatic), qemu-utils:amd64 
(1:2.11+dfsg-1ubuntu7.18, automatic), libvirt-daemon-system:amd64 
(4.0.0-1ubuntu8.12, automatic), libcacard0:amd64 (1:2.5.0-3, automatic), 
python-ipaddr:amd64 (2.2.0-1, automatic), sharutils:amd64 (1:4.15.2-3, 
automatic), ipxe-qemu-256k-compat-efi-roms:amd64 
(1.0.0+git-20150424.a25a16d-0ubuntu2, automatic), virt-viewer:amd64 (6.0-2, 
automatic), libspice-client-glib-2.0-8:amd64 (0.34-1.1build1, automatic), 
libxen-4.9:amd64 (4.9.2-0ubuntu1, automatic), libvirt-glib-1.0-0:amd64 
(1.0.0-1, automatic), python-libxml2:amd64 (2.9.4+dfsg1-6.1ubuntu1.2, 
automatic), qemu-kvm:amd64 (1:2.11+dfsg-1ubuntu7.18), libvirt0:amd64 
(4.0.0-1ubuntu8.12, automatic), libfdt1:amd64 (1.4.5-3, automatic), 
libiscsi7:amd64 (1.17.0-1.1, automatic), libphodav-2.0-0:amd64 (2.2-2, 
automatic), cpu-checker:amd64 (0.7-0ubuntu7, automatic), qemu-block-extra:amd64 
(1:2.11+dfsg-1ubuntu7.18, automatic), gir1.2-libosinfo-1.0:amd64 (1.1.0-1, 
automatic), libspice-client-gtk-3.0-5:amd64 (0.34-1.1build1, automatic), 
librados2:amd64 (12.2.12-0ubuntu0.18.04.2, automatic), libgtk-vnc-2.0-0:amd64 
(0.7.2-1, automatic), qemu-system-common:amd64 (1:2.11+dfsg-1ubuntu7.18, 
automatic), libvirt-daemon:amd64 (4.0.0-1ubuntu8.12, automatic)
End-Date: 2019-09-11  18:17:41

Start-Date: 2019-09-11  19:46:26
Commandline: apt-get install virt-manager
Requested-By: alextu (1000)
Install: gir1.2-appindicator3-0.1:amd64 (12.10.1+18.04.20180322.1-0ubuntu1, 
automatic), gir1.2-spiceclientgtk-3.0:amd64 (0.34-1.1build1, automatic), 
gir1.2-gtk-vnc-2.0:amd64 (0.7.2-1, automatic), virt-manager:amd64 
(1:1.5.1-0ubuntu1.2), python-gi-cairo:amd64 (3.26.1-2ubuntu1, automatic), 
gir1.2-libvirt-glib-1.0:amd64 (1.0.0-1, automatic), 
gir1.2-spiceclientglib-2.0:amd64 (0.34-1.1build1, automatic)
End-Date: 2019-09-11  19:46:30

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

Title:
  linux-oem 4.15 can not suspend to idle XPS-13-9380

Status in OEM Priority Project:
  New
Status in linux-signed-oem package in Ubuntu:
  New

Bug description:
  it somehow s2i failed, from message , it seems the s2i process be
  blocked by thunderbolt device.

  dmesg:
  [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193141.012736] PM: noirq suspend of devices failed
  [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809
  [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118
  [193141.872317] thunderbolt :05:00.0: control channel starting...

  Not sure is it relative that I hot plug out WD19 docking before
  suspend.

  reproduce rate:
  random

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50
  ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18
  Uname: Linux 4.15.0-1045-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 00:02:08 2019
 

[Kernel-packages] [Bug 1842540] Re: disco/linux-raspi2: 5.0.0-1016.16 -proposed tracker

[Andy Whitcroft]

** 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) => Andy 
Whitcroft (apw)

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

Title:
  disco/linux-raspi2: 5.0.0-1016.16 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 12:00 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
-   trusty/linux-aws: bug 1842793, bug 1842606
-   trusty/linux-lts-xenial: bug 1842607, bug 1842794
+   trusty/linux-aws: bug 1842606
+   trusty/linux-lts-xenial: bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

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

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

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842606
trusty/linux-lts-xenial: bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

[Kai-Heng Feng]

Jimmy,

Can you please describe why it's failed? Have you enabled -proposed?

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

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek Wifi stops working after the driver changed from rtlwifi to
  rtw88.

  [Fix]
  Sync rtw88 to upstream version, and use MSI on the device.

  [Test]
  User confirmed the backport fixes the issue.

  [Regression Potential]
  Low. Currently only 8822be uses rtw88.

  === Original Bug Report ===
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the 
dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that 
wifi was no longer working because at work I exclusively use a wired Ethernet 
connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

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

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

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

[Kai-Heng Feng]

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

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

Title:
  brightness control not work with OLED panel

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1842540] Re: disco/linux-raspi2: 5.0.0-1016.16 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Ready for Promote to Proposed
- phase-changed: Tuesday, 10. September 2019 03:35 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 11. September 2019 12:00 UTC
  reason:
-   promote-to-proposed: Stalled -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  variant: debs

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

Title:
  disco/linux-raspi2: 5.0.0-1016.16 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 12:00 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1833484] Re: Sometimes touchpad automatically trigger double click

[Kai-Heng Feng]

Fixed by this commit upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=76380a607ba0b28627c9b4b55cd47a079a59624b

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

Title:
  Sometimes touchpad automatically trigger double click

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Dell machines which uses goodix touchpad IC emit double click event
  while touching the touchpad if designware i2c adapter is in runtime
  suspend.

  Goodix re-assert the interrupt if host doesn't read the data within
  100ms and designware takes a longer time to wake up from runtime
  suspend. In the case, it got a second interrupt during resuming, so
  it thinks it's a double click.

  [Fix]
  There is no simple way to fix this, it's a firmware issue and goodix
  agrees to fix this in their firmware on next release, but this issue is
  still affects the machines that don't come with an updated firmware. So,
  add a quirk to mark those machines and avoid the designware from entering
  runtime suspend.

  [Regression Potential]
  Low, it only affects the listed machines, and prevent designware from
  entering runtime suspend impacts the power consumption little or none
  during short or long idle.

  [MISC]
  This patch contains on going product name, so set it as SAUCE patch,
  will submit it to upstream and to Bionic kernel later.

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

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

[Kernel-packages] [Bug 1842815] Re: bionic/linux-fips: 4.15.0-1016.19 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

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

Title:
  bionic/linux-fips: 4.15.0-1016.19 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 12:27 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  replaces: bug 1842582
  variant: debs

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

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

[Kernel-packages] [Bug 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380

[Michał Sawicz]

If it doesn't require an instance to break S2I, that suggests something
in our daemon after all.

I wouldn't think we'd be doing anything low-level enough to cause this,
though…

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

Title:
  linux-oem 4.15 can not suspend to idle XPS-13-9380

Status in OEM Priority Project:
  New
Status in linux-signed-oem package in Ubuntu:
  New

Bug description:
  it somehow s2i failed, from message , it seems the s2i process be
  blocked by thunderbolt device.

  dmesg:
  [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193141.012736] PM: noirq suspend of devices failed
  [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809
  [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118
  [193141.872317] thunderbolt :05:00.0: control channel starting...

  Not sure is it relative that I hot plug out WD19 docking before
  suspend.

  reproduce rate:
  random

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50
  ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18
  Uname: Linux 4.15.0-1045-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 00:02:08 2019
  InstallationDate: Installed on 2019-08-11 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed-oem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1840484/+subscriptions

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

[Kernel-packages] [Bug 1842815] Re: bionic/linux-fips: 4.15.0-1016.19 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Packaging
- phase-changed: Friday, 06. September 2019 17:55 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Wednesday, 11. September 2019 12:27 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  replaces: bug 1842582
  variant: debs

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

Title:
  bionic/linux-fips: 4.15.0-1016.19 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 12:27 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  replaces: bug 1842582
  variant: debs

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

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

[Kernel-packages] [Bug 1829310] Re: kernel 5 fails to start systemd-networkd on old Dell Inspiron 1720

[bfluehr]

I had this same problem on a Dell Inspiron 6400, which has Broadcom
BCM4311 network controller and Broadcom BCM4401-B0 Ethernet controller.

Kernel 5.0.0-27 manifests the problem. Kernels 4.15.0-60 and 5.2.0-15
work fine.

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

Title:
  kernel 5 fails to start systemd-networkd on old Dell Inspiron 1720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux kernel 5.0.0-13
  Kubuntu 19.04
  hardware: old Dell laptop Inspiron 1720

  After upgrading an old Dell laptop Inspiron 1720 (from 2007 I think) from 
Kubuntu 18.10 to 19.04, the result is a broken system:
  booting takes + 5 minutes
  looking at the boot messages I see "Failed to start Dispatcher daemon for 
systemd-networkd" and consequently Network Manager fails to run.
  Eventually it reaches the desktop where it takes another 5 minutes to display 
the panel.
  In a terminal it fails to execute any network command (ifconfig, ip) as well 
as "sudo" and "lshw".

  If I boot with the previous kernel, the 4.18.0-18 of Kubuntu 18.10, it works 
without problem.
  For now I have set its grub to start by default the 4.18 kernel instead of 
the 5.0 one.

  I tried running "apport-cli -f -p linux --save
  kernel5.0onOldDellInspiron1720.apport" but that has been spitting out
  periods ("") for 10 minutes now and still hasn't finished.

  dmesg output attached.

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1843583] [NEW] linux: -proposed tracker

[Stefan Bader]

Public bug reported:

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

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

-- swm properties --
variant: debs

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.09.02-3 xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-propose

[Kernel-packages] [Bug 1843018] Re: 5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a container

[Mitch Dart]

Our developers are unable to debug our applications because they use the
vsdbg inside docker which makes use of the /proc//maps. Even after
enabling preview software for 5.0.0-28, the bug still exists. Our only
option at this point is to roll back the Kernel.

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

Title:
  5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a
  container

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Using kernel 5.0.0-27-generic on Ubuntu 18.04 in a container, every
  pathname in /proc//maps is / instead of the mapped file path.

  This appears to be a regression in 5.0.0-27-generic; it works on
  5.0.0-25-generic. The problem can be reproduced in various Ubuntu
  releases, e.g. 18.04 and 19.04.

  5.0.0-25-generic (working):

  $ sudo docker run ubuntu cat /proc/1/maps
  56324a3f5000-56324a3fd000 r-xp  fc:01 665673 
/bin/cat
  56324a5fc000-56324a5fd000 r--p 7000 fc:01 665673 
/bin/cat
  56324a5fd000-56324a5fe000 rw-p 8000 fc:01 665673 
/bin/cat
  56324a8eb000-56324a90c000 rw-p  00:00 0  
[heap]
  7f8ab5f91000-7f8ab6178000 r-xp  fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab6178000-7f8ab6378000 ---p 001e7000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab6378000-7f8ab637c000 r--p 001e7000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab637c000-7f8ab637e000 rw-p 001eb000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab637e000-7f8ab6382000 rw-p  00:00 0
  7f8ab6382000-7f8ab63a9000 r-xp  fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab6583000-7f8ab65a7000 rw-p  00:00 0
  7f8ab65a9000-7f8ab65aa000 r--p 00027000 fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab65aa000-7f8ab65ab000 rw-p 00028000 fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab65ab000-7f8ab65ac000 rw-p  00:00 0
  7ffc25954000-7ffc25975000 rw-p  00:00 0  
[stack]
  7ffc259f1000-7ffc259f4000 r--p  00:00 0  
[vvar]
  7ffc259f4000-7ffc259f5000 r-xp  00:00 0  
[vdso]
  ff60-ff601000 r-xp  00:00 0  
[vsyscall]

  5.0.0-27-generic (broken):

  $ sudo docker run ubuntu cat /proc/1/maps
  55de0e052000-55de0e05a000 r-xp  fc:01 665673 /
  55de0e259000-55de0e25a000 r--p 7000 fc:01 665673 /
  55de0e25a000-55de0e25b000 rw-p 8000 fc:01 665673 /
  55de0fcb3000-55de0fcd4000 rw-p  00:00 0  
[heap]
  7f7a8d881000-7f7a8da68000 r-xp  fc:01 666073 /
  7f7a8da68000-7f7a8dc68000 ---p 001e7000 fc:01 666073 /
  7f7a8dc68000-7f7a8dc6c000 r--p 001e7000 fc:01 666073 /
  7f7a8dc6c000-7f7a8dc6e000 rw-p 001eb000 fc:01 666073 /
  7f7a8dc6e000-7f7a8dc72000 rw-p  00:00 0
  7f7a8dc72000-7f7a8dc99000 r-xp  fc:01 666055 /
  7f7a8de73000-7f7a8de97000 rw-p  00:00 0
  7f7a8de99000-7f7a8de9a000 r--p 00027000 fc:01 666055 /
  7f7a8de9a000-7f7a8de9b000 rw-p 00028000 fc:01 666055 /
  7f7a8de9b000-7f7a8de9c000 rw-p  00:00 0
  7ffc744bd000-7ffc744de000 rw-p  00:00 0  
[stack]
  7ffc7452d000-7ffc7453 r--p  00:00 0  
[vvar]
  7ffc7453-7ffc74531000 r-xp  00:00 0  
[vdso]

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

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

[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

Title:
  bionic/linux: 4.15.0-63.72 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 10:11 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-aws: bug 1842806
bionic/linux-bluefield: bug 1842811
bionic/linux-fips: bug 1842815
bionic/linux-gke-4.15: bug 1842809
bionic/linux-ibm-gt: bug 1842812
bionic/linux-kvm: bug 1842810
bionic/linux-oem: bug 1842802
bionic/linux-oracle: bug 1842814
bionic/linux-raspi2: bug 1842799
bionic/linux-snapdragon: bug 1842801
bionic/linux/pc-kernel: bug 1842796
bionic/linux/pc-lowlatency-kernel: bug 1842797
xenial/linux-azure: bug 1842587
xenial/linux-gcp: bug 1842590
xenial/linux-hwe: bug 1842593
  variant: debs

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

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

[Kernel-packages] [Bug 1842783] Re: xenial/linux-aws: -proposed tracker

[Stefan Bader]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1842795
+ kernel-stable-master-bug: 1843583
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:53 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842597
  trackers:
xenial/linux-aws/aws-kernel: bug 1842782, bug 1842596
  variant: debs

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

** Tags added: kernel-sru-derivative-of-1843583

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

Title:
  xenial/linux-aws:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1843583
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:53 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842597
  trackers:
xenial/linux-aws/aws-kernel: bug 1842782, bug 1842596
  variant: debs

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

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

[Kernel-packages] [Bug 1842792] Re: xenial/linux-fips: -proposed tracker

[Stefan Bader]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1842795
+ kernel-stable-master-bug: 1843583
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:54 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842605
  variant: debs

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

** Tags added: kernel-sru-derivative-of-1843583

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

Title:
  xenial/linux-fips:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1843583
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:54 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842605
  variant: debs

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

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

[Kernel-packages] [Bug 1842784] Re: xenial/linux-kvm: -proposed tracker

[Stefan Bader]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1842795
+ kernel-stable-master-bug: 1843583
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:53 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842598
  variant: debs

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

** Tags added: kernel-sru-derivative-of-1843583

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

Title:
  xenial/linux-kvm:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1843583
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:53 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842598
  variant: debs

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

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

[Kernel-packages] [Bug 1842793] Re: trusty/linux-aws: -proposed tracker

[Stefan Bader]

** Tags removed: kernel-sru-backport-of-1842608

** Tags added: kernel-sru-backport-of-1842608

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1842608
+ kernel-stable-master-bug: 1843583
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Packaging
  phase-changed: Friday, 06. September 2019 05:35 UTC
  reason:
prepare-package: Pending -- version not specified
  replaces: bug 1842606
  variant: debs

** Tags removed: kernel-sru-backport-of-1842608

** Tags added: kernel-sru-backport-of-1843583

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

Title:
  trusty/linux-aws:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1843583
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Packaging
  phase-changed: Friday, 06. September 2019 05:35 UTC
  reason:
prepare-package: Pending -- version not specified
  replaces: bug 1842606
  variant: debs

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

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

[Kernel-packages] [Bug 1842788] Re: xenial/linux-raspi2: -proposed tracker

[Stefan Bader]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1842795
+ kernel-stable-master-bug: 1843583
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:53 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842600
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1842786, bug 1842599
  variant: debs

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

** Tags added: kernel-sru-derivative-of-1843583

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

Title:
  xenial/linux-raspi2:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1843583
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:53 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842600
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1842786, bug 1842599
  variant: debs

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

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

[Kernel-packages] [Bug 1842790] Re: xenial/linux-snapdragon: -proposed tracker

[Stefan Bader]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1842795
+ kernel-stable-master-bug: 1843583
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:54 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842603
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1842602, bug 1842789
  variant: debs

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

** Tags added: kernel-sru-derivative-of-1843583

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

Title:
  xenial/linux-snapdragon:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1843583
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 03:54 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1842603
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1842602, bug 1842789
  variant: debs

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

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

[Kernel-packages] [Bug 1843583] Re: xenial/linux: -proposed tracker

[Ubuntu Kernel Bot]

** Summary changed:

- linux:  -proposed tracker
+ xenial/linux:  -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ packages:
+   main: linux
+   meta: linux-meta
+   signed: linux-signed
+ phase: Ready for Packaging
+ phase-changed: Wednesday, 11. September 2019 12:57 UTC
+ reason:
+   prepare-package: Pending -- version not specified
+ trackers:
+   xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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

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

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Ready for Packaging
  phase-changed: Wednesday, 11. September 2019 12:57 UTC
  reason:
prepare-package: Pending -- version not specified
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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

[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-162.191 -proposed tracker

[Stefan Bader]

** Summary changed:

- xenial/linux:  -proposed tracker
+ xenial/linux: 4.4.0-162.191 -proposed tracker

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

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

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

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

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

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

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

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

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

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 11. September 2019 13:11 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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

[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose

[Gerard Krupa]

I'm seeing the same kernel panic on linux-aws 4.15.0.1048.47 as well

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

Title:
  Kernel Panic with linux-image-4.15.0-60-generic when specifying
  nameserver in docker-compose

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

Bug description:
  [Impact]
  Some fragmentation+NAT workloads will cause kernel BUG/Ooops.

  [Test case]
  sudo iptables -t nat -I POSTROUTING -j MASQUERADE
  sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6

  [Regression potential]
  This could make fragmented packets stop flowing. So, make sure fragmented 
pings still work.
  ping 192.168.122.1 -s 6 still works, even with the above nat rule.

  

  Hello,

  there are multiple inquries in the mailcow GitHub issues over at
  https://github.com/mailcow/mailcow-dockerized/issues/2904 that the
  latest kernel linux-image-4.15.0-60-generic causes kernel panics when
  "- dns" setting is used within the docker-compose.yml file, for yet
  some unclear reasons.

  Multiple users on different systems (e.g. virtualized ones on VMware
  ESXi and KVM) were able to reproduce the same issue. I was also able
  to reproduce this constantly on a completely new deployed Ubuntu 18.04
  VM (KVM) with a fresh mailcow installation.

  Steps to reproduce:
  1. Install a clean Ubuntu 18.04(.03) machine
  2. Upgrade the installation to linux-image-4.15.0-60-generic
  3. Setup mailcow as instructed at 
https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes 
less than a minute, easy to reproduce)
  4. Start mailcow with "dns"-settings specified in docker-compose file (Make 
sure using the older docker-compose version with dns settings: 
https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
  5. Wait a few minutes, then kernel crash appears

  Using this workaround it appears to be stable again:
  https://github.com/mailcow/mailcow-
  dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2

  I've attached the apport file to this bug. Please let me know if you
  need any kind of further information. (As this is my first bug report
  here, I hope I have included all required information helping you
  finding the cause.)

  Kind regards,
  Patrik

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

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

[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-162.191 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Packaging
- phase-changed: Wednesday, 11. September 2019 12:57 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 11. September 2019 13:11 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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

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

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

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 11. September 2019 13:11 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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

[Kernel-packages] [Bug 1757202] Re: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time

[Ivan Frederiks]

Same issue with Xubuntu 18.04.3
Used workaround with "Files" section, but I had to use 
/usr/lib/x86_64-linux-gnu/nvidia-430 path.
/usr/lib/x86_64-linux-gnu/nvidia/xorg and /usr/lib/x86_64-linux-gnu/xorg do not 
exist in my system.

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

Title:
  xubuntu / bionic / nvidia-driver-390 can only be used by one user at a
  time

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  In XUbuntu 18.04 bionic, with the nvidia-driver-390, ony one user can use the 
nvidia driver at a time. 
  A second user logged-in gets stuck at 640x480 and llvmpipe for OpenGL. 
  Before the update around 11-12 March 2018, it was possible for multiple users 
to use the nvidia driver.

  First User
  ==
  For the first user to log in, they get this:

  lsb_release -a:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  apt-cache policy nvidia-driver-390:
  nvidia-driver-390:
Installed: 390.42-0ubuntu1+gpu18.04.1
Candidate: 390.42-0ubuntu1+gpu18.04.1
Version table:
   *** 390.42-0ubuntu1+gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status
   390.42-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 
Packages

  lscpi:
  07:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] 
(rev a1)

  glxinfo | grep renderer:
  OpenGL renderer string: GeForce GTX 660/PCIe/SSE2

  xrandr:
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
819mm x 461mm
 1920x1080 60.00*+  60.0059.9450.0023.9860.0050.04  
 1280x1024 75.02  
 1280x720  60.0059.9450.00  
 1024x768  75.0370.0760.00  
 800x600   75.0072.1960.32  
 720x576   50.00  
 720x480   59.94  
 640x480   75.0059.9459.93  
  DP-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)

  After switching to a second user
  

  glxinfo | grep renderer:
  OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits)

  xrandr:
  Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
  default connected 640x480+0+0 0mm x 0mm
 640x480   73.00*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202/+subscriptions

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

[Kernel-packages] [Bug 1842554] Re: disco/linux-kvm: 5.0.0-1016.17 -proposed tracker

[Andy Whitcroft]

** 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) => Andy 
Whitcroft (apw)

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

Title:
  disco/linux-kvm: 5.0.0-1016.17 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 13:30 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1842554] Re: disco/linux-kvm: 5.0.0-1016.17 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 09. September 2019 14:26 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 11. September 2019 13:30 UTC
  reason:
-   promote-to-proposed: Stalled -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  variant: debs

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

Title:
  disco/linux-kvm: 5.0.0-1016.17 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Promote to Proposed
  phase-changed: Wednesday, 11. September 2019 13:30 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

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

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:0x

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.4

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP

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

[Tom Brezinski]

apport information

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359]

[Kernel-packages] [Bug 1843487] Re: UIO: mutex used in interrupt handler causes crash

[Tom Brezinski]

apport information

** Tags added: apport-collected

** Description changed:

  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18
  
  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.
  
  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:0x7f8a46a4803f
  [ 1941.409360] RSP: 002b:7f8a45d91db0 EFLAGS: 0293 ORIG_RAX: 
0017
  [ 1941.409361] RAX: ffda RBX: 0400 RCX: 
7f8a46a4803f
  [ 1941.409362] RDX:  RSI: 7f8a45d91e30 RDI: 
0400
  [ 1941.409362] RBP: 7f8a45d91e30 R08: 7f8a45d91e20 R09: 
0

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:0x7f

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:0x

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359]

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

[Tom Brezinski]

apport information

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.40935

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

[Tom Brezinski]

apport information

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

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 194

[Kernel-packages] [Bug 1843487] Re: UIO: mutex used in interrupt handler causes crash

[Tom Brezinski]

The following commit in the kernel mainline fixes this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3d27c4de8d4fb2d4099ff324671792aa2578c6f9

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after