[Kernel-packages] [Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu

2020-01-30 Thread Peder Stray
After booting into 5.3.0-26 on my Lenovo X390, it has started to loose
network connection when connected to the Thunderbolt 3 Gen 2 dock after
a while.  No traffic goes through.  Enabling wifi after it works fine,
but unselecting "Enable Networking" in network manager makes the whole
computer hang (can move mouse, but no input from keyboard is registered
anymore, or so it seems at least)

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

Title:
  Lenovo dock MAC Address pass through doesn't work in Ubuntu

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

Bug description:
  === SRU Justification ===
  [Impact]
  Lenovo dock doesn't support MAC passthrough.

  [Fix]
  Add support to Lenovo Dock MAC passthrough.

  [Test]
  MAC passthrough works once the patch is applied.

  [Regression Potential]
  Low. Apart from adding support to Lenovo Dock, this patch only did minor
  refactoring to existing behavior, no functional change to current code.

  === Original Bug Report ===
  Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 
the MAC address pass through does not work with a Lenovo Thunderbolt 3 
Workstation Dock.

  The dock's network port is recognized and working but it has its own
  MAC address even though MAC Address pass through is enabled in the
  BIOS.

  This is the dock in question:

  https://www.lenovo.com/us/en/accessories-and-monitors/top-tech
  /Thunderbolt-WS-230W-dock-US/p/40AN0230US

  and the laptop is a Lenovo P1. Debug files attached.

  Please let me know if further info is required.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rauer  2107 F pulseaudio
   /dev/snd/controlC1:  rauer  2107 F pulseaudio
   /dev/snd/controlC0:  rauer  2107 F pulseaudio
  CurrentDesktop: i3
  Date: Mon May  6 19:34:26 2019
  InstallationDate: Installed on 2019-04-09 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20MES1WH00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET39W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES1WH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES1WH00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working

2020-01-30 Thread Hui Wang
I tried "dtoverlay=dwc2,dr_mode=peripheral" and "dtoverlay=dwc2" with
ubuntu-5.3 kernel, I could see "[18977.499410] usb 1-1.1: device
descriptor read/64, error -110" sometimes too (not always happen), if I
run "rmmod g_ether/g_cdc; modprobe g_ether/g_cdc" many times, it could
work without those errors sometimes.So it looks like this issue has
nothing to do with "dr_mode=pheripheral", maybe it has sth to do the
power supplied to the board.

I also tested the Raspbian, the kernel is "Linux raspberrypi
4.19.57-v7l+ #1244 SMP Thu Jul 4 18:48:07 BST 2019 armv7l GNU/Linux",
the result is same as the ubuntu-5.3 kernel.

And I used a single usb typec cable to connect the board and a usb hub,
the usb hub connects to a laptop.

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

Title:
  Raspberry Pi 4B: USB OTG is not working

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  I am using Raspberry Pi 4B (4GB) and want to make use of the OTG
  functionality (g_ether).  I cross checked with Raspbian to make sure
  it is not a hardware issue.  Extract from dmesg of Ubuntu 19.10.1 with
  latest updates applied as of Jan 26th, 2020 via "apt-get update" and
  "apt-get full-upgrade":

  ...
  [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
  [1.517365] dwc_otg: FIQ enabled
  [1.517376] dwc_otg: NAK holdoff enabled
  [1.517386] dwc_otg: FIQ split-transaction FSM enabled
  [1.517399] Module dwc_common_port init
  ...
  [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using 
dummy regulator
  [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using 
dummy regulator
  [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to 
host
  [6.409098] dwc2 fe98.usb: DWC OTG Controller
  [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 
3
  [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98
  ...
  [  111.796714] udc-core: couldn't find an available UDC - added [g_ether] to 
list of pending drivers

  I think it is that "Configuration mismatch. dr_mode forced to host"
  log entry telling me that the port is acting as HOST mode instead of
  OTG mode.  I have try putting these in usercfg.txt

  "dtoverlay=dwc2"
  "dtoverlay=dwc2,dr_mode=otg"
  "dtoverlay=dwc2,dr_mode=peripheral"

  and it will give the same result, no OTG functionality.

  On the same hardware running Raspbian Buster, it initialise successfully.  
Corresponding dmesg:
  ...
  [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
  [0.570391] dwc_otg: FIQ enabled
  [0.570400] dwc_otg: NAK holdoff enabled
  [0.570409] dwc_otg: FIQ split-transaction FSM enabled
  [0.570421] Module dwc_common_port init
  ...
  [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using 
dummy regulator
  [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0
  [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using 
dummy regulator
  [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1
  [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter 
lpm_clock_gating=1
  [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1
  [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter 
hird_threshold_en=1
  [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in 
SPRAM
  [2.752511] dwc2 fe98.usb: DWC OTG Controller
  [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 
3
  [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98
  ...
  [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
  [2.851601] g_ether gadget: g_ether ready
  [2.854580] dwc2 fe98.usb: bound driver g_ether
  [2.998525] dwc2 fe98.usb: new device is high-speed
  [3.075025] dwc2 fe98.usb: new device is high-speed
  [3.139338] dwc2 fe98.usb: new address 10
  [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM)

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

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


[Kernel-packages] [Bug 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

2020-01-30 Thread Juerg Haefliger
** Also affects: linux-raspi2 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  New

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached

2020-01-30 Thread Juerg Haefliger
** Also affects: linux-raspi2 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

Title:
  RPI4 wifi unreliable when usb3 storage is attached

Status in linux-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2 source package in Eoan:
  New

Bug description:
  On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage
  device to one of the 2x usb3 ports (the ones closest to the ethernet
  port), wifi will sudden stop working. If you unplug the usb stick
  while running a ping, it will usually start working again almost
  instantaneously.

  Kernel version I have is: 5.3.0-1017-raspi2
  and I've confirmed this happens on both armhf and arm64

  The only thing I found in journalctl that looks suspicious is this, but it 
seems to have happened before plugging in the usb stick:
  Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from 
/dev/random: Resource temporarily unavailable

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

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


[Kernel-packages] [Bug 1861113] Re: xenial/linux-raspi2: 4.4.0-1129.138 -proposed tracker

2020-01-30 Thread 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

** 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: 1861122
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Packaging
- phase-changed: Wednesday, 29. January 2020 19:06 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Friday, 31. January 2020 06:01 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 186
  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/1861113

Title:
  xenial/linux-raspi2: 4.4.0-1129.138 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1861122
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 31. January 2020 06:01 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 186
  variant: debs

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

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


[Kernel-packages] [Bug 1861184] Re: bionic/linux-gcp: 5.0.0-1030.31 -proposed tracker

2020-01-30 Thread Khaled El Mously
** Summary changed:

- bionic/linux-gcp: 5.0.0-1030.31~18.04.1 -proposed tracker
+ bionic/linux-gcp: 5.0.0-1030.31 -proposed tracker

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

Title:
  bionic/linux-gcp: 5.0.0-1030.31 -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 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: 1861192
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Packaging
  phase-changed: Thursday, 30. January 2020 05:32 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
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1861183
  variant: debs

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

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


[Kernel-packages] [Bug 1861249] Re: clashing with i915 video driver

2020-01-30 Thread Nermeen Hussein
System:
  Host: nermeen-Inspiron-5567 Kernel: 5.0.0-37-generic x86_64 bits: 64 
  compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 
  Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:
  Type: Laptop System: Dell product: Inspiron 5567 v: N/A serial:  
  Mobo: Dell model: 05VRRG v: A00 serial:  UEFI: Dell v: 1.1.7 
  date: 09/11/2017 
Battery:
  ID-1: BAT0 charge: 42.0 Wh condition: 42.0/42.0 Wh (100%) 
  model: Samsung SDI DELL CYMGM74 status: Full 
CPU:
  Topology: Dual Core model: Intel Core i7-7500U bits: 64 type: MT MCP 
  arch: Kaby Lake rev: 9 L2 cache: 4096 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23232 
  Speed: 667 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 700 2: 700 
  3: 700 4: 700 
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel 
  bus ID: 00:02.0 
  Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] 
  vendor: Dell driver: amdgpu v: kernel bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati,modesetting 
  unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2) 
  v: 4.5 Mesa 19.2.1 direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
  Sound Server: ALSA v: k5.0.0-37-generic 
Network:
  Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel port: e000 
  bus ID: 02:00.0 
  IF: wlp2s0 state: up mac:  
  Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
  driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
  IF: enp3s0 state: down mac:  
Drives:
  Local Storage: total: 931.51 GiB used: 93.74 GiB (10.1%) 
  ID-1: /dev/sda vendor: Toshiba model: MQ01ABD100 size: 931.51 GiB 
  temp: 30 C 
Partition:
  ID-1: / size: 36.41 GiB used: 21.32 GiB (58.6%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 869.87 GiB used: 72.41 GiB (8.3%) fs: ext4 
  dev: /dev/sda2 
  ID-3: swap-1 size: 9.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4 
Sensors:
  System Temperatures: cpu: 41.0 C mobo: 32.0 C sodimm: 30.0 C gpu: amdgpu 
  temp: 42 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 230 Uptime: 16m Memory: 7.69 GiB used: 2.02 GiB (26.2%) 
  Init: systemd runlevel: 5 Compilers: gcc: 7.4.0 Shell: bash v: 4.4.20 
  inxi: 3.0.32 

Top

KD5RKO  
Level 1
Level 1 
Posts: 18   
Joined: Sat Nov 02, 2019 2:30 pm
Contact: Contact KD5RKO

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

Title:
  clashing with i915 video driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed the new kernel 5.3 but found a black screen at startup.
  Had to remove it and go back to the 5.0 kernel.

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

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


[Kernel-packages] [Bug 1861116] Re: xenial/linux-fips: 4.4.0-1029.34 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** 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: 1861122
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Holding before Promote to Proposed
- phase-changed: Friday, 31. January 2020 01:46 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 31. January 2020 05:37 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:depwait,signed:depwait
+   promote-to-proposed: Pending -- ready for review
  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/1861116

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 31. January 2020 05:37 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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


[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3

2020-01-30 Thread Bill (franksmcb)
These are not working on 5.3.0-28

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

Title:
  nvidia-drivers-390 fail to build with kernel 5.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released

Bug description:
  nvidia-graphics-drivers-390 fails to build against linux 5.3.

  SRU Request:

  [Test Case]
  1) Enable the -proposed repository, and install the new 390 NVIDIA driver 
(nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2).

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The update only fixes build issues with Linux versions 5.3.
  __
  With linux-image-5.0.0-23 I had no problems. Following an update 
linux-image-5.3.0-19 was installed, the DKMS build failed, and the system 
became unusable.

  Removing 5.3.0 brings the system back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  3 19:55:57 2019
  InstallationDate: Installed on 2019-06-09 (147 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+subscriptions

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


[Kernel-packages] [Bug 1861350] Re: focal/linux-raspi2-5.4: -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861352
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
- phase: Holding before Packaging
- phase-changed: Wednesday, 29. January 2020 22:41 UTC
+ phase: Ready for Packaging
+ phase-changed: Friday, 31. January 2020 04:42 UTC
  reason:
-   prepare-package: Holding -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  focal/linux-raspi2-5.4:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1861352
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Ready for Packaging
  phase-changed: Friday, 31. January 2020 04:42 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/1861350/+subscriptions

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


[Kernel-packages] [Bug 1861116] Re: xenial/linux-fips: 4.4.0-1029.34 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

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

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

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

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1861122
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 31. January 2020 01:46 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:depwait,signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1838443] Re: No flicker free boot since Ignoring BGRT: invalid version 0 (expected 1)

2020-01-30 Thread Daniel van Vugt
This same issue is mentioned in:

https://wiki.osdev.org/Broken_UEFI_implementations

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

Title:
  No flicker free boot since Ignoring BGRT: invalid version 0 (expected
  1)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On eoan dev here:

  Flicker free booting doesn't work since I get:
  Ignoring BGRT: invalid version 0 (expected 1)
  on dmesg on my Thinkpad x230t i7-3520M (Ivy Bridge).

  Second, if I add:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.fastboot=1"
  to /etc/default/grub then it doesn't show plymouth but displays the text 
Ubuntu loading screen and I need to press ALT+F1 so GDM will show up (see 
video: [1]). If I press escape while it is displaying text Ubuntu loading, it 
loads plymouth (see video: [2]) and shows the spinner (no lenovo word) and I 
don't need to press ALT+F1 since GDM shows after plymouth. So I guess there's a 
bug there, since it should display plymouth and not the Ubuntu loading text and 
boot directly to GDM.

  Now if I patch the kernel:
  diff --git a/drivers/firmware/efi/efi-bgrt.c b/drivers/firmware/efi/efi-bgrt.c
  index b07c17643210..5754e530af9a 100644
  --- a/drivers/firmware/efi/efi-bgrt.c
  +++ b/drivers/firmware/efi/efi-bgrt.c
  @@ -42,7 +42,7 @@ void __init efi_bgrt_init(struct acpi_table_header *table)
  return;
  }
  *bgrt = *(struct acpi_table_bgrt *)table;
  -   if (bgrt->version != 1) {
  +   if (bgrt->version != 1 && false) { /* don't check BGRT version */
  pr_notice("Ignoring BGRT: invalid version %u (expected 1)\n",
     bgrt->version);
  goto out;

  And linux-modules and linux-modules-extra is not installed in that
  kernel, then I have somewhat flicker free boot.  It shows the bgrt
  screen then goes black (probably grub loading), then shows the bgrt
  screen again with the spinner.  Nice! (see video: [3])

  So, I guess my Thinkpad is not setting bgrt version properly.  So can
  we have a kernel parameter to disable checking of bgrt version?

  Then again, if I install linux-modules and linux-modules-extra then I
  get the Ubuntu loading text when booting, but if I press esc I get the
  bgrt screen with spinner.  I think it's it's a bug somewhere in the
  linux-modules package.

  [1] https://youtu.be/tAgRf2c7J4A
  [2] https://youtu.be/1ystyzLhSaw
  [3] https://youtu.be/8AAkUDO2Kt8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic (not installed)
  ProcVersionSignature: Ubuntu 5.2.0-8.9+test1-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shemgp13358 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 30 23:49:49 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cc5ba738-82e8-404a-9bcc-f1dfed94fce0
  InstallationDate: Installed on 2015-09-28 (1401 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash i915.fastboot=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: Upgraded to eoan on 2019-07-26 (4 days ago)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB4WW(2.74):bd06/11/2019:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1836858] Re: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background

2020-01-30 Thread Daniel van Vugt
Or maybe you're describing bug 1861470. So please subscribe to that
instead.

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

Title:
  i915: Display flickers (monitor loses signal briefly) during
  "flickerfree" boot, while showing the BIOS logo on a black background

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am trying flickerfree boot in 19.10 [1], but find it actually
  flickers part way through:

1. BIOS logo on a black background.
2. Display mode resets, no image on a black background briefly.
3. BIOS logo on a black background.

  The flicker occurs seemingly during kernel startup since my
  peripherals are lit up before the problem occurs.

  Suspecting this might be related to FB handover:

    [2.751028] fb0: switching to inteldrmfb from EFI VGA

  I tried disabling that with a big hammer:

    i915.modeset=0

  so it stays in efifb, and that works -- no more flickering, providing
  I don't let i915 take over the framebuffer.

  [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jul 17 16:34:36 2019
  InstallationDate: Installed on 2019-05-02 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  MachineType: LENOVO 10M7CTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen

2020-01-30 Thread Daniel van Vugt
Yeah it might be related to this kernel change from a couple of weeks
ago:

  [Config] FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y (bug 1836858)

Again, I think I would prefer to keep it. Just stop grub from bringing
up the purple screen...

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen

2020-01-30 Thread Steve Langasek
** Package changed: grub (Ubuntu) => grub2 (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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0

2020-01-30 Thread Daniel van Vugt
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/intel/issues/673
   Importance: Unknown
   Status: Unknown

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

Title:
  system hang: i915 Resetting rcs0 for hang on rcs0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Incomplete

Bug description:
  System hangs, unknown cause, When this happens, the mouse pointer
  still moves, but I can't do anything else with the keys or clicking in
  the UI.  Only recover I have found is a hard power-off

  Last bit of kern.log below:

  Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: 
ecode 9:1:0x, hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
  Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report 
on bugs.freedesktop.org against DRI -> DRM/Intel
  Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required 
to analyze GPU hangs, so please always attach it.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to 
/sys/class/drm/card0/error
  Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting 
chip for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks 
suppressed
  Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
  Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 
01 00 00 00 ff 50 30  04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 
7d 8f 00
  Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 30 12:51:24 2020
  InstallationDate: Installed on 2018-06-18 (591 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1861470/+attachment/5324339/+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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

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

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1861470/+attachment/5324340/+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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen

2020-01-30 Thread Daniel van Vugt
I think I would prefer to see just the purple grub screen gone. So that
would be a grub change and no kernel changes?...

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

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

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen

2020-01-30 Thread Chris Guiver
I have seen this also (most likely with flavors), but ignored it sorry
(probably over ~two weeks??? but very subjective)

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] Lsusb-v.txt

2020-01-30 Thread Daniel van Vugt
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1861470/+attachment/5324333/+files/Lsusb-v.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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1861470/+attachment/5324334/+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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] AlsaInfo.txt

2020-01-30 Thread Daniel van Vugt
apport information

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

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1861470/+attachment/5324327/+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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] Lsusb-t.txt

2020-01-30 Thread Daniel van Vugt
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1861470/+attachment/5324332/+files/Lsusb-t.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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-30 Thread Daniel van Vugt
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1861470/+attachment/5324329/+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/1861470

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861470] [NEW] BIOS logo reappears mid-boot after the purple screen

2020-01-30 Thread Daniel van Vugt
Public bug reported:

BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
screen.

This seems to be happening reliably on multiple focal machines:

0. Turn on or reboot the machine.
1. See the BIOS logo.
2. See a blank purple screen (grub)
3. See the BIOS logo again (this bug)
4. See the purple screen with Ubuntu logo (plymouth)
5. See the login screen

I believe this is related to ACPI BGRT changes in the kernel. And I
guess it wouldn't even need fixing if we just eliminated the blank
purple grub screen (step 2)...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Fri Jan 31 11:31:44 2020
InstallationDate: Installed on 2020-01-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
SourcePackage: linux-signed-5.4
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dan1316 F pulseaudio
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-01-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
MachineType: LENOVO 20KFCTO1WW
Package: linux-signed-5.4
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-12-generic N/A
 linux-backports-modules-5.4.0-12-generic  N/A
 linux-firmware1.185
Tags:  focal
Uname: Linux 5.4.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/10/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N20ET51W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X280
dmi.product.name: 20KFCTO1WW
dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
dmi.product.version: ThinkPad X280
dmi.sys.vendor: LENOVO

** Affects: grub (Ubuntu)
 Importance: Medium
 Status: New

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

** Affects: linux-signed-5.4 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug apport-collected champagne flickerfreeboot focal

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

** Tags added: apport-collected

** Description changed:

  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.
  
  This seems to be happening reliably on multiple focal machines:
  
  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen
  
  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dan1316 F pulseaudio
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-01-30 (0 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
+ MachineType: LENOVO 20KFCTO1WW
+ Package: linux-signed-5.4
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-12-generic N/A
+  linux-backports-modules-5.4.0-12-generic  N/A
+  linux-firmware1.185
+ 

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

2020-01-30 Thread Daniel van Vugt
apport information

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Holding before Promote to Release
  phase-changed: Thursday, 30. January 2020 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-release: Holding -- master bug not ready for release
  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/1861410

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow 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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Holding before Promote to Release
  phase-changed: Thursday, 30. January 2020 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

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

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


[Kernel-packages] [Bug 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

2020-01-30 Thread Hui Wang
We had a similar bug: https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1861338

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

** Changed in: linux-raspi2 (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached

2020-01-30 Thread Hui Wang
We had a similar bug before, it said the issue could be reproduced with
specific ssd and usb->ssd case.

https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857760

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

Title:
  RPI4 wifi unreliable when usb3 storage is attached

Status in linux-raspi2 package in Ubuntu:
  Triaged

Bug description:
  On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage
  device to one of the 2x usb3 ports (the ones closest to the ethernet
  port), wifi will sudden stop working. If you unplug the usb stick
  while running a ping, it will usually start working again almost
  instantaneously.

  Kernel version I have is: 5.3.0-1017-raspi2
  and I've confirmed this happens on both armhf and arm64

  The only thing I found in journalctl that looks suspicious is this, but it 
seems to have happened before plugging in the usb stick:
  Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from 
/dev/random: Resource temporarily unavailable

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

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


[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

2020-01-30 Thread Daniel van Vugt
The simplest first test would be to try booting Ubuntu 20.04 from USB:

http://cdimage.ubuntu.com/daily-live/current/

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

2020-01-30 Thread Daniel van Vugt
Most likely this is a kernel bug so the next step would be to try some
newer or older kernels and see if any of them DO NOT have the same bug.
Then hopefully we can identify when things changed.

https://kernel.ubuntu.com/~kernel-ppa/mainline/

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1861116] Re: xenial/linux-fips: 4.4.0-1029.34 -proposed tracker

2020-01-30 Thread 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

** 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: 1861122
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Packaging
- phase-changed: Wednesday, 29. January 2020 17:06 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Friday, 31. January 2020 01:46 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
  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/1861116

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

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1861122
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 31. January 2020 01:46 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1836858] Re: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background

2020-01-30 Thread Daniel van Vugt
Maybe you're using a laptop that never hit the main problem I see here,
and only hit part of the issue which was fixed by the kernel patch. But
the "why" doesn't really matter, just so long as this bug stays open
while it is still being experienced.

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

Title:
  i915: Display flickers (monitor loses signal briefly) during
  "flickerfree" boot, while showing the BIOS logo on a black background

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am trying flickerfree boot in 19.10 [1], but find it actually
  flickers part way through:

1. BIOS logo on a black background.
2. Display mode resets, no image on a black background briefly.
3. BIOS logo on a black background.

  The flicker occurs seemingly during kernel startup since my
  peripherals are lit up before the problem occurs.

  Suspecting this might be related to FB handover:

    [2.751028] fb0: switching to inteldrmfb from EFI VGA

  I tried disabling that with a big hammer:

    i915.modeset=0

  so it stays in efifb, and that works -- no more flickering, providing
  I don't let i915 take over the framebuffer.

  [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jul 17 16:34:36 2019
  InstallationDate: Installed on 2019-05-02 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  MachineType: LENOVO 10M7CTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1859096] Re: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works)

2020-01-30 Thread Dauphin
with the last Focal's update, sound is OK.
kernel is: 5.4.0-12-generic
and nvidia driver is : 440.44-0ubuntu2

Thanks to all developpers.
Gilles

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

Title:
  No sound or Crazy sound on Display port since kernel change to 5.4
  (but 5.3.0-24 works)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not 
adjustable.
  I have either full volume or nothing. sound is crazy on my GTX1650 video card.

  If I use Nouveau driver I have no sound on my Display port.

  If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver.
  But no sound with nouveau driver. Same things append on Focal and on Ubuntu 
19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.44  Sun Dec  8 03:38:56 
UTC 2019
   GCC version:  gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 10 00:26:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.44, 5.4.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] 
[1458:3fcb]
  InstallationDate: Installed on 2020-01-05 (4 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200104)
  MachineType: Micro-Star International Co., Ltd. MS-7B51
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=0b5d6829-5bb4-40e3-9fee-0fdec99e5f5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B51
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1861463] [NEW] package nvidia-compute-utils-390 390.132-0ubuntu2 failed to install/upgrade: el subproceso instalado paquete nvidia-compute-utils-390 script post-installation dev

2020-01-30 Thread PABLO MARCELO PEREYRA
Public bug reported:

se encontraron errores en la instalacion de los paquetes relacionados con el 
controlador de nvidia que actualmente tengo:
root@ubuntu-G74Sx:/home/ubuntu# lspci -vnn | grep -i VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116M [GeForce GT 
560M] [10de:1251] (rev a1) (prog-if 00 [VGA controller])
root@ubuntu-G74Sx:/home/ubuntu#

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-compute-utils-390 390.132-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Thu Jan 30 20:59:40 2020
ErrorMessage: el subproceso instalado paquete nvidia-compute-utils-390 script 
post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2020-01-30 (0 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.8
SourcePackage: nvidia-graphics-drivers-390
Title: package nvidia-compute-utils-390 390.132-0ubuntu2 failed to 
install/upgrade: el subproceso instalado paquete nvidia-compute-utils-390 
script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to focal on 2020-01-30 (0 days ago)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package nvidia-compute-utils-390 390.132-0ubuntu2 failed to
  install/upgrade: el subproceso instalado paquete nvidia-compute-
  utils-390 script post-installation devolvió el código de salida de
  error 1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  se encontraron errores en la instalacion de los paquetes relacionados con el 
controlador de nvidia que actualmente tengo:
  root@ubuntu-G74Sx:/home/ubuntu# lspci -vnn | grep -i VGA
  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116M [GeForce 
GT 560M] [10de:1251] (rev a1) (prog-if 00 [VGA controller])
  root@ubuntu-G74Sx:/home/ubuntu#

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Thu Jan 30 20:59:40 2020
  ErrorMessage: el subproceso instalado paquete nvidia-compute-utils-390 script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.8
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-compute-utils-390 390.132-0ubuntu2 failed to 
install/upgrade: el subproceso instalado paquete nvidia-compute-utils-390 
script post-installation devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to focal on 2020-01-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1861463/+subscriptions

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


[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
- phase: Promote to Proposed
- phase-changed: Thursday, 30. January 2020 22:06 UTC
+ phase: Holding before Promote to Release
+ phase-changed: Thursday, 30. January 2020 23:36 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   promote-to-release: Holding -- master bug not ready for release
  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/1861410

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow 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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Holding before Promote to Release
  phase-changed: Thursday, 30. January 2020 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Holding -- master bug not ready for release
  variant: debs

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

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


[Kernel-packages] [Bug 1861119] Re: trusty/linux-aws: 4.4.0-1062.66 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Promote to Proposed
- phase-changed: Thursday, 30. January 2020 22:06 UTC
+ phase: Testing
+ phase-changed: Thursday, 30. January 2020 22:26 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 30. January 2020 22:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1861119] Re: trusty/linux-aws: 4.4.0-1062.66 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 30. January 2020 15:46 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 30. January 2020 22:06 UTC
  reason:
-   promote-to-proposed: Pending -- 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1861119

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 30. January 2020 22:06 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/1861119/+subscriptions

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


[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 30. January 2020 19:01 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 30. January 2020 22:06 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  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/1861410

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow 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 Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Promote to Proposed
  phase-changed: Thursday, 30. January 2020 22:06 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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


[Kernel-packages] [Bug 1861119] Re: trusty/linux-aws: 4.4.0-1062.66 -proposed tracker

2020-01-30 Thread 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1861119

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 30. January 2020 22:06 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/1861119/+subscriptions

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


[Kernel-packages] [Bug 1729901] Re: Alt Gr selects text

2020-01-30 Thread Łukasz Batek
This problem is still exist.

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

Title:
  Alt Gr selects text

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I search name on Facebook and other webpages on Ubuntu 16.04 LTS in 
polish and use Alt Gr with some polish letters it selects all text instead add 
new letter with a tail. That is only when I have activated automatic login in 
Ubuntu.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   wabi   1289 F...m pulseaudio
   /dev/snd/controlC0:  wabi   1289 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1559da2e-23ff-470f-929e-a84540b28777
  InstallationDate: Installed on 2016-09-21 (408 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=2e7ea815-6d0d-4d89-8747-7ca4fe8e08f8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-38-generic N/A
   linux-backports-modules-4.10.0-38-generic  N/A
   linux-firmware 1.157.13
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.10.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd11/25/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-P:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

2020-01-30 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft 
(apw)

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

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow 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 Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Promote to Proposed
  phase-changed: Thursday, 30. January 2020 22:06 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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


[Kernel-packages] [Bug 1861249] Re: clashing with i915 video driver

2020-01-30 Thread Terry Rudd
Could you please provide more information about your hardware and any
other details?

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

Title:
  clashing with i915 video driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed the new kernel 5.3 but found a black screen at startup.
  Had to remove it and go back to the 5.0 kernel.

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

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


[Kernel-packages] [Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

2020-01-30 Thread Richard Laager
There does seem to be a real bug here. The problem is that we don’t know
if it is on the ZoL side or the FreeBSD side. The immediate failure is
that “zfs recv” on the FreeBSD side is failing to receive the stream. So
that is the best place to start figuring out why. If it turns out that
ZoL is generating an invalid stream, then we can take this to ZoL.
Accordingly, my main goal here is to help you produce the best possible
bug report for FreeBSD to help them troubleshoot. I don’t run FreeBSD,
so I can’t test this myself to produce a test case. If you can produce a
test case, with an example send stream that FreeBSD can’t receive, that
gives them the best chance of finding the root cause.

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

Title:
  Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD
  12.0 as I have done since June each week, I found out it did not work
  anymore. The regression occurred after I reinstalled Ubuntu on my new
  nvme drive. I also had to reorganize my own datapools/datasets,
  because they either moved to the nvme drive or they had to be located
  on 2 HDDs instead of 3. I had one datapool that still works, the
  datapool containing my archives and it is the datapool, that has NOT
  been reorganized. I tried for a whole long day to get the backup
  working again, but I failed. I compared the properties from datapool
  and dataset, but did not see any problem there. Only a lot of new
  features and properties not present before and not present in FreeBSD.
  I used FreeBSD, because I use for backup an old 32-bits Pentium.

  I have two complaints:
  - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :(
  - the system transfers the dataset and at the end of a long transfer it 
decides to quit and the error messages are completely useless and self 
contradicting. 

  On the first try it say the dataset does exist and on the second try it says 
it does NOT exist. One of the two is completely wrong. Some consistency and 
some clearer error messages would be helpful for the user.
  See the following set of strange set error messages on two tries:

  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive zroot/hp-data/dummy
  cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists
  must specify -F to overwrite it
  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy
  cannot receive new filesystem stream: dataset does not exist

  A 2nd subset of my backup is stored on the laptop and that still
  works. I also compared the properties with those of my laptop, that
  still has its original datapools of begin of the year. I aligned the
  properties of FreeBSD with those of my laptop, but it did not help.

  I attach the properties of the datapool and dataset from both FreeBSD
  and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  3 13:35:08 2019
  InstallationDate: Installed on 2019-11-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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


[Kernel-packages] [Bug 1861182] Re: bionic/linux-azure: 5.0.0-1030.32 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  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/1861182

Title:
  bionic/linux-azure: 5.0.0-1030.32 -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-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:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  variant: debs

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

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


[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1860119'
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Signoff
- phase-changed: Thursday, 30. January 2020 14:16 UTC
+ phase: Signoff
+ phase-changed: Thursday, 30. January 2020 20:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- package in development blackout
security-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-azure-5.3: bug 1859819
  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/1859820

Title:
  eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: '1860119'
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Signoff
  phase-changed: Thursday, 30. January 2020 20:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- package in development blackout
security-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-azure-5.3: bug 1859819
  variant: debs

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

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


[Kernel-packages] [Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

2020-01-30 Thread Garrett Fields
BertN45,

Thanks for the continued followup.  Most of these ZFS variants run test
suites to ensure that new code has a limited ability to create
additional issues.  I would expect that cross OS compatibility is not
heavily tested (if at all).  You were in a position to witness this
problem, took effort to report, and did some preliminary followup tests.
All these helped tremendously.

Ubuntu uses code from the ZFS on Linux project.  Ubuntu has chosen
certain ways to use the ZOL code that fits their needs.  Ubuntu's
choices are reasonable, and should work.  I'm glad to see the FreeBSD
bug report.  This is likely the first time they are being made aware of
the situation.  As far as I know, the ZOL project is yet to know of the
issue.

With this report filed with one of the two organizations that actually
develop the code involved, an investigation can ensue.  At this point,
others can attempt to reproduce what you have detailed.

Thanks again for staying involved.  Feel free to monitor and contribute
to the issues as others continue to investigate.

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

Title:
  Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD
  12.0 as I have done since June each week, I found out it did not work
  anymore. The regression occurred after I reinstalled Ubuntu on my new
  nvme drive. I also had to reorganize my own datapools/datasets,
  because they either moved to the nvme drive or they had to be located
  on 2 HDDs instead of 3. I had one datapool that still works, the
  datapool containing my archives and it is the datapool, that has NOT
  been reorganized. I tried for a whole long day to get the backup
  working again, but I failed. I compared the properties from datapool
  and dataset, but did not see any problem there. Only a lot of new
  features and properties not present before and not present in FreeBSD.
  I used FreeBSD, because I use for backup an old 32-bits Pentium.

  I have two complaints:
  - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :(
  - the system transfers the dataset and at the end of a long transfer it 
decides to quit and the error messages are completely useless and self 
contradicting. 

  On the first try it say the dataset does exist and on the second try it says 
it does NOT exist. One of the two is completely wrong. Some consistency and 
some clearer error messages would be helpful for the user.
  See the following set of strange set error messages on two tries:

  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive zroot/hp-data/dummy
  cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists
  must specify -F to overwrite it
  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy
  cannot receive new filesystem stream: dataset does not exist

  A 2nd subset of my backup is stored on the laptop and that still
  works. I also compared the properties with those of my laptop, that
  still has its original datapools of begin of the year. I aligned the
  properties of FreeBSD with those of my laptop, but it did not help.

  I attach the properties of the datapool and dataset from both FreeBSD
  and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  3 13:35:08 2019
  InstallationDate: Installed on 2019-11-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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


[Kernel-packages] [Bug 1861330] Re: Battery status unknown on Lenovo X1 Carbon Extreme Gen 2

2020-01-30 Thread Lee Trager
** 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/1861330

Title:
  Battery status unknown on Lenovo X1 Carbon Extreme Gen 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Carbon Extreme Gen 2. When I first installed Focal
  on it battery status was working however its now stuck at 59% even
  though its been charging for days.

  $ cat /sys/class/power_supply/BAT0/status
  Unknown
  $ cat /sys/class/power_supply/BAT0/capacity
  59
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lee4054 F pulseaudio
   /dev/snd/controlC1:  lee4054 F pulseaudio
   /dev/snd/controlC0:  lee4054 F pulseaudio
   /dev/snd/pcmC0D0p:   lee4054 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-12-29 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220)
  MachineType: LENOVO 20QVCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/samsung--ssd-ROOT ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET41W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

2020-01-30 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

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

Title:
  eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: '1860119'
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Signoff
  phase-changed: Thursday, 30. January 2020 20:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- package in development blackout
security-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-azure-5.3: bug 1859819
  variant: debs

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

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


[Kernel-packages] [Bug 1861122] Re: xenial/linux: 4.4.0-174.204 -proposed tracker

2020-01-30 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 30. January 2020 14:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1861119
trusty/linux-lts-xenial: bug 1861121
xenial/linux-aws: bug 1861107
xenial/linux-cascade: bug 1861109
xenial/linux-fips: bug 1861116
xenial/linux-kvm: bug 1861110
xenial/linux-raspi2: bug 1861113
xenial/linux-snapdragon: bug 1861115
xenial/linux/caracalla-kernel: bug 1861103
xenial/linux/pc-kernel: bug 1861104
xenial/linux/stlouis-kernel: bug 1861105
  variant: debs

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

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


[Kernel-packages] [Bug 1861107] Re: xenial/linux-aws: 4.4.0-1102.113 -proposed tracker

2020-01-30 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  xenial/linux-aws: 4.4.0-1102.113 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 30. January 2020 13:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1861106
  variant: debs

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

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


[Kernel-packages] [Bug 1861110] Re: xenial/linux-kvm: 4.4.0-1066.73 -proposed tracker

2020-01-30 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  xenial/linux-kvm: 4.4.0-1066.73 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 30. January 2020 13:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1861115] Re: xenial/linux-snapdragon: 4.4.0-1133.141 -proposed tracker

2020-01-30 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 30. January 2020 13:19 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1861114
  variant: debs

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

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


[Kernel-packages] [Bug 1861182] Re: bionic/linux-azure: 5.0.0-1030.32 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  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/1861182

Title:
  bionic/linux-azure: 5.0.0-1030.32 -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-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:
  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: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  variant: debs

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

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


[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2020-01-30 Thread Seth Forshee
@ellisonleao: Eoan already has the firmware which was identified as
fixing this issue. If you are having a similar issue in eoan then it
must have a different cause. Please open a new bug for your issue.
Thanks!

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2020-01-30 Thread ellisonleao
Any updates on this for eoan release?

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 
0x6070 | flow_handler
  Dec 13 11:53:36 james-x1 kernel: [  856.845170] iwlwifi :02:00.0: Start 
IWL Error Log 

[Kernel-packages] [Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

2020-01-30 Thread BertN45
I did not blame you, I only noticed a seemingly missing process in the 
communication between both groups (ZOL/ZOF or Ubuntu/FreeBSD).
I said I already tried your proposed case in a different way. I'm always 
willing to try something else, but I need to understand why. I'm not a monkey, 
that has to follow your commands.

So I will not bother the free Ubuntu support anymore and I will stop
issuing bug-reports and enjoy the free software without being lectured.

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

Title:
  Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD
  12.0 as I have done since June each week, I found out it did not work
  anymore. The regression occurred after I reinstalled Ubuntu on my new
  nvme drive. I also had to reorganize my own datapools/datasets,
  because they either moved to the nvme drive or they had to be located
  on 2 HDDs instead of 3. I had one datapool that still works, the
  datapool containing my archives and it is the datapool, that has NOT
  been reorganized. I tried for a whole long day to get the backup
  working again, but I failed. I compared the properties from datapool
  and dataset, but did not see any problem there. Only a lot of new
  features and properties not present before and not present in FreeBSD.
  I used FreeBSD, because I use for backup an old 32-bits Pentium.

  I have two complaints:
  - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :(
  - the system transfers the dataset and at the end of a long transfer it 
decides to quit and the error messages are completely useless and self 
contradicting. 

  On the first try it say the dataset does exist and on the second try it says 
it does NOT exist. One of the two is completely wrong. Some consistency and 
some clearer error messages would be helpful for the user.
  See the following set of strange set error messages on two tries:

  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive zroot/hp-data/dummy
  cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists
  must specify -F to overwrite it
  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy
  cannot receive new filesystem stream: dataset does not exist

  A 2nd subset of my backup is stored on the laptop and that still
  works. I also compared the properties with those of my laptop, that
  still has its original datapools of begin of the year. I aligned the
  properties of FreeBSD with those of my laptop, but it did not help.

  I attach the properties of the datapool and dataset from both FreeBSD
  and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  3 13:35:08 2019
  InstallationDate: Installed on 2019-11-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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


[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-01-30 Thread Seth Arnold
** 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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such 

[Kernel-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-01-30 Thread Edwin Peer
> 3. mtr ping test
> ---
> GoodSystem..0.0% Loss; 0.2 Avg; 0.1 Best, 0.9 Worst, 0.1 StdDev
> BadSystem2...11.7% Loss; 0.1 Avg; 0.1 Best, 0.2 Worst, 0.0 StdDev

The mtr packet loss is an interesting result. What mtr options did you
use? Is this a UDP or ICMP test?

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In this particular case description, the nodes are USRP x310s. However, we 
have the same issue with N210 nodes dropping samples connected to the BCM57416 
NetXtreme-E Dual-Media 10G RDMA Ethernet device.

  There is no problem with the USRPs themselves, as we have tested them
  with normal 1G network cards and have no dropped samples.

  Personally I think its something to do with the 10G network card,
  possibly on a ubuntu driver???

  Note, Dell have said there is no hardware problem 

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

2020-01-30 Thread Seth Arnold
Very curious. I tried again with new kernel and no change in results:

$ cat /proc/version_signature
Ubuntu 5.4.0-12.15-generic 5.4.8
$ uname -a
Linux millbarge 5.4.0-12-generic #15-Ubuntu SMP Tue Jan 21 15:12:29 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

$ apt policy fatrace
fatrace:
  Installed: 0.13-2
  Candidate: 0.13-2
  Version table:
 *** 0.13-2 500
500 http://wopr/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status


journalctl -f output while testing:

Jan 30 19:00:48 millbarge audit[1440438]: SYSCALL arch=c03e syscall=59 
success=yes exit=0 a0=55f754fc09f0 a1=55f754fb00a0 a2=55f754fb5a70 a3=8 items=2 
ppid=22587 pid=1440438 auid=1000 uid=1000 gid=1000 euid=0 suid=0 fsuid=0 
egid=1000 sgid=1000 fsgid=1000 tty=pts2 ses=1 comm="sudo" exe="/usr/bin/sudo" 
key="execpriv"
Jan 30 19:00:48 millbarge audit: EXECVE argc=2 a0="sudo" a1="fatrace"
Jan 30 19:00:48 millbarge audit: CWD cwd="/home/sarnold"
Jan 30 19:00:48 millbarge audit: PATH item=0 name="/usr/bin/sudo" inode=51282 
dev=00:1b mode=0104755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=0 
cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
Jan 30 19:00:48 millbarge audit: PATH item=1 name="/lib64/ld-linux-x86-64.so.2" 
inode=9834 dev=00:1b mode=0100755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL 
cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
Jan 30 19:00:48 millbarge audit: PROCTITLE proctitle=7375646F0066617472616365
Jan 30 19:00:48 millbarge sudo[1440438]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
Jan 30 19:00:49 millbarge sudo[1440438]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
Jan 30 19:00:49 millbarge audit[1440438]: USER_AUTH pid=1440438 uid=1000 
auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_permit,pam_cap 
acct="sarnold" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 
res=success'
Jan 30 19:00:49 millbarge audit[1440438]: USER_ACCT pid=1440438 uid=1000 
auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_permit acct="sarnold" 
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Jan 30 19:00:49 millbarge sudo[1440438]:  sarnold : TTY=pts/2 ; 
PWD=/home/sarnold ; USER=root ; COMMAND=/usr/sbin/fatrace
Jan 30 19:00:49 millbarge audit[1440438]: USER_CMD pid=1440438 uid=1000 
auid=1000 ses=1 msg='cwd="/home/sarnold" cmd="fatrace" terminal=pts/2 
res=success'
Jan 30 19:00:49 millbarge audit[1440438]: CRED_REFR pid=1440438 uid=0 auid=1000 
ses=1 msg='op=PAM:setcred grantors=pam_permit,pam_cap acct="root" 
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Jan 30 19:00:49 millbarge sudo[1440438]: pam_unix(sudo:session): session opened 
for user root by sarnold(uid=0)
Jan 30 19:00:49 millbarge audit[1440438]: USER_START pid=1440438 uid=0 
auid=1000 ses=1 msg='op=PAM:session_open 
grantors=pam_env,pam_env,pam_permit,pam_umask,pam_unix acct="root" 
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Jan 30 19:00:57 millbarge bash[1005653]: Thu, 30 Jan 2020 19:00:57 + src 46 
(fix: 3) currently receiving: 0,3@0 0,9@0 0,16@0 0,22@0 0,23@0 0,26@0 2,1@1 
2,4@1 2,21@1 3,14@0 3,24@0 3,25@0
Jan 30 19:01:03 millbarge sudo[1440438]: pam_unix(sudo:session): session closed 
for user root
Jan 30 19:01:03 millbarge audit[1440438]: USER_END pid=1440438 uid=0 auid=1000 
ses=1 msg='op=PAM:session_close 
grantors=pam_env,pam_env,pam_permit,pam_umask,pam_unix acct="root" 
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Jan 30 19:01:03 millbarge audit[1440438]: CRED_DISP pid=1440438 uid=0 auid=1000 
ses=1 msg='op=PAM:setcred grantors=pam_permit acct="root" exe="/usr/bin/sudo" 
hostname=? addr=? terminal=/dev/pts/2 res=success'


tail -F /var/log/audit/audit.log output while testing:

type=SYSCALL msg=audit(1580410848.032:15175): arch=c03e syscall=59 
success=yes exit=0 a0=55f754fc09f0 a1=55f754fb00a0 a2=55f754fb5a70 a3=8 items=2 
ppid=22587 pid=1440438 auid=1000 uid=1000 gid=1000 euid=0 suid=0 fsuid=0 
egid=1000 sgid=1000 fsgid=1000 tty=pts2 ses=1 comm="sudo" exe="/usr/bin/sudo" 
key="execpriv"
type=EXECVE msg=audit(1580410848.032:15175): argc=2 a0="sudo" a1="fatrace"
type=CWD msg=audit(1580410848.032:15175): cwd="/home/sarnold"
type=PATH msg=audit(1580410848.032:15175): item=0 name="/usr/bin/sudo" 
inode=51282 dev=00:1b mode=0104755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL 
cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
type=PATH msg=audit(1580410848.032:15175): item=1 
name="/lib64/ld-linux-x86-64.so.2" inode=9834 dev=00:1b mode=0100755 ouid=0 
ogid=0 rdev=00:00 nametype=NORMAL cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 
cap_frootid=0
type=PROCTITLE msg=audit(1580410848.032:15175): 
proctitle=7375646F0066617472616365
type=USER_AUTH msg=audit(1580410849.140:15176): pid=1440438 uid=1000 auid=1000 
ses=1 msg='op=PAM:authentication grantors=pam_permit,pam_cap acct="sarnold" 
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
type=USER_ACCT 

[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-focal

** 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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 30. January 2020 15:12 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 30. January 2020 19:01 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
+   promote-to-proposed: Pending -- ready for review
  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/1861410

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow 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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 30. January 2020 19:01 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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


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

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

apport-collect 1861300

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

Title:
  Data Corruption with Sil 3114 and 3124 controlleurs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Silicon Image 3114 and 3124 seem to have data corruption at writing data 
(particularly with big files or when the writing concern lot of files).
  I used a PCI card with the Sil 3114 chip; when copying files and directories 
from a HDD to an other, data corruption appears and seems to be random in files.
  But every checks about the computer (RAM, HDD ...) have gone right.
  Don't know what happening really, but I supposed that the module which 
control the Sil 3114 (and so the Sil 3124, cause this module was written from 
the 3114's module) contain a bug.
  I've tried to enable the Sil 3114 module's option called "slow_down" which 
should solve some "problems", no difference with and without this option 
activated. The Sil 3124 module's doesn't have this option.

  Drives connected to Sil3124 controller seems to be affected by data
  corruption when at least 2 process attempts to writing at the same
  drive (obviously not in the same directory nor the same file), against
  Sil3114 which the bug seems to appears anytime.

  I have already posted a question :
  https://unix.stackexchange.com/questions/564067/file-corruption-
  between-2-hdd with more precisions about what have done until now.

  Now i use a PCI card based on the Sil 3124 controller, seems to have
  the same data corruption issue as the Sil 3114, but less pronounced
  (less often).

  Running Ubuntu 16.04 server i386 with Linux Kernel 4.4.211.

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

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


[Kernel-packages] [Bug 1861300] Re: Data Corruption with Sil 3114 and 3124 controlleurs

2020-01-30 Thread Brian Murray
** Tags added: xenial

** Package changed: 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/1861300

Title:
  Data Corruption with Sil 3114 and 3124 controlleurs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Silicon Image 3114 and 3124 seem to have data corruption at writing data 
(particularly with big files or when the writing concern lot of files).
  I used a PCI card with the Sil 3114 chip; when copying files and directories 
from a HDD to an other, data corruption appears and seems to be random in files.
  But every checks about the computer (RAM, HDD ...) have gone right.
  Don't know what happening really, but I supposed that the module which 
control the Sil 3114 (and so the Sil 3124, cause this module was written from 
the 3114's module) contain a bug.
  I've tried to enable the Sil 3114 module's option called "slow_down" which 
should solve some "problems", no difference with and without this option 
activated. The Sil 3124 module's doesn't have this option.

  Drives connected to Sil3124 controller seems to be affected by data
  corruption when at least 2 process attempts to writing at the same
  drive (obviously not in the same directory nor the same file), against
  Sil3114 which the bug seems to appears anytime.

  I have already posted a question :
  https://unix.stackexchange.com/questions/564067/file-corruption-
  between-2-hdd with more precisions about what have done until now.

  Now i use a PCI card based on the Sil 3124 controller, seems to have
  the same data corruption issue as the Sil 3114, but less pronounced
  (less often).

  Running Ubuntu 16.04 server i386 with Linux Kernel 4.4.211.

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

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


[Kernel-packages] [Bug 1861300] [NEW] Data Corruption with Sil 3114 and 3124 controlleurs

2020-01-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Silicon Image 3114 and 3124 seem to have data corruption at writing data 
(particularly with big files or when the writing concern lot of files).
I used a PCI card with the Sil 3114 chip; when copying files and directories 
from a HDD to an other, data corruption appears and seems to be random in files.
But every checks about the computer (RAM, HDD ...) have gone right.
Don't know what happening really, but I supposed that the module which control 
the Sil 3114 (and so the Sil 3124, cause this module was written from the 
3114's module) contain a bug.
I've tried to enable the Sil 3114 module's option called "slow_down" which 
should solve some "problems", no difference with and without this option 
activated. The Sil 3124 module's doesn't have this option.

Drives connected to Sil3124 controller seems to be affected by data
corruption when at least 2 process attempts to writing at the same drive
(obviously not in the same directory nor the same file), against Sil3114
which the bug seems to appears anytime.

I have already posted a question :
https://unix.stackexchange.com/questions/564067/file-corruption-
between-2-hdd with more precisions about what have done until now.

Now i use a PCI card based on the Sil 3124 controller, seems to have the
same data corruption issue as the Sil 3114, but less pronounced (less
often).

Running Ubuntu 16.04 server i386 with Linux Kernel 4.4.211.

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


** Tags: bot-comment i386 kernel-bug xenial
-- 
Data Corruption with Sil 3114 and 3124 controlleurs
https://bugs.launchpad.net/bugs/1861300
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 1861182] Re: bionic/linux-azure: 5.0.0-1030.32 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  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/1861182

Title:
  bionic/linux-azure: 5.0.0-1030.32 -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-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:
  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: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  variant: debs

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

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


[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

2020-01-30 Thread Tyler Hicks
FWIW, fatrace works fine for me under the same kernel and fatrace
version:

$ sudo fatrace
...
bash(51938): O /tmp/hi
bash(51938): CW /tmp/hi
...
tyhicks@elm:~$ cat /proc/version_signature 
Ubuntu 5.4.0-12.15-generic 5.4.8
$ apt policy fatrace
fatrace:
  Installed: 0.13-2
  Candidate: 0.13-2
  Version table:
 *** 0.13-2 500
500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  no fatrace output in focal

Status in fatrace package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)   

[Kernel-packages] [Bug 1861182] Re: bionic/linux-azure: 5.0.0-1030.32 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  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/1861182

Title:
  bionic/linux-azure: 5.0.0-1030.32 -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-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:
  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: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  variant: debs

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

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


[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 15:12 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  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/1861410

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 15:12 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  variant: debs

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

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


[Kernel-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-01-30 Thread Edwin Peer
With respect to one of these situations, this is the following system:

> Dell PowerEdge R440/0XP8V5, BIOS 2.2.11 06/14/2019
> 
> Note that a similar system does not have any issues:
> 
> Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.3.4 11/08/2016
> 
> So the NIC in the "bad" environment is:
> 
> BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01)
> Product Name: Broadcom Adv. Dual 10G SFP+ Ethernet
> 
> The NIC in the "good" environment is:
> 
> Broadcom Inc. and subsidiaries NetXtreme II BCM57810
> 10 Gigabit Ethernet [14e4:1006]
> Product Name: QLogic 57810 10 Gigabit Ethernet

There are more than one variable at play here. Does the problem follow
the NIC if you swap the NICs between systems? Are OS / kernel and driver
versions the same on both systems?

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In this 

[Kernel-packages] [Bug 1861419] Re: kworker takes a lot of CPU

2020-01-30 Thread corrado venturini
found same problem on
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-29-generic 5.3.0-29.31
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
and
Linux corrado-HP-p4-ff--0124 5.4.0-12-generic #15-Ubuntu SMP Tue Jan 21 
15:12:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861419

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

Title:
  kworker takes a lot of CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kworker takes a lot of CPU. no other app are active.

  top - 15:52:50 up 8 min,  1 user,  load average: 1,16, 1,24, 0,77
  Tasks: 204 total,   2 running, 202 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  4,9 us, 26,2 sy,  0,0 ni, 62,3 id,  0,0 wa,  0,0 hi,  6,6 si,  0,0 
st
  MiB Mem :   3867,1 total,   1737,2 free,895,9 used,   1234,0 buff/cache
  MiB Swap:   4096,0 total,   4096,0 free,  0,0 used.   2568,5 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
239 root  20   0   0  0  0 R  81,2   0,0   0:31.92 
kworker/0+
   1623 corrado   20   0  304848  53436  38048 S   6,2   1,3   0:13.02 Xorg
   1921 corrado   20   0  323484  10544   8768 S   6,2   0,3   0:00.42 
ibus-daem+
  1 root  20   0  167140  10868   7952 S   0,0   0,3   0:02.04 systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1613 F pulseaudio
   /dev/snd/controlC1:  corrado1613 F pulseaudio
  Date: Thu Jan 30 15:49:01 2020
  InstallationDate: Installed on 2019-12-28 (33 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=24e2ba6f-1b75-4b3c-835e-63387635551b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.sku: J4R70EA#ABZ
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1861182] Re: bionic/linux-azure: 5.0.0-1030.32 -proposed tracker

2020-01-30 Thread 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-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   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

** 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: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Packaging
- phase-changed: Thursday, 30. January 2020 17:16 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 30. January 2020 17:57 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
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  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/1861182

Title:
  bionic/linux-azure: 5.0.0-1030.32 -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-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:
  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: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 17:57 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  variant: debs

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

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


[Kernel-packages] [Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

2020-01-30 Thread Richard Laager
The FreeBSD bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243730

Like I said, boiling this down to a test case would likely help a lot.
Refusing to do so and blaming the people giving you free software and
free support isn’t helpful.

** Bug watch added: bugs.freebsd.org/bugzilla/ #243730
   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243730

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

Title:
  Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD
  12.0 as I have done since June each week, I found out it did not work
  anymore. The regression occurred after I reinstalled Ubuntu on my new
  nvme drive. I also had to reorganize my own datapools/datasets,
  because they either moved to the nvme drive or they had to be located
  on 2 HDDs instead of 3. I had one datapool that still works, the
  datapool containing my archives and it is the datapool, that has NOT
  been reorganized. I tried for a whole long day to get the backup
  working again, but I failed. I compared the properties from datapool
  and dataset, but did not see any problem there. Only a lot of new
  features and properties not present before and not present in FreeBSD.
  I used FreeBSD, because I use for backup an old 32-bits Pentium.

  I have two complaints:
  - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :(
  - the system transfers the dataset and at the end of a long transfer it 
decides to quit and the error messages are completely useless and self 
contradicting. 

  On the first try it say the dataset does exist and on the second try it says 
it does NOT exist. One of the two is completely wrong. Some consistency and 
some clearer error messages would be helpful for the user.
  See the following set of strange set error messages on two tries:

  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive zroot/hp-data/dummy
  cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists
  must specify -F to overwrite it
  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy
  cannot receive new filesystem stream: dataset does not exist

  A 2nd subset of my backup is stored on the laptop and that still
  works. I also compared the properties with those of my laptop, that
  still has its original datapools of begin of the year. I aligned the
  properties of FreeBSD with those of my laptop, but it did not help.

  I attach the properties of the datapool and dataset from both FreeBSD
  and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  3 13:35:08 2019
  InstallationDate: Installed on 2019-11-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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


[Kernel-packages] [Bug 1861182] Re: bionic/linux-azure: 5.0.0-1030.32 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Packaging
- phase-changed: Wednesday, 29. January 2020 23:43 UTC
+ phase: Packaging
+ phase-changed: Thursday, 30. January 2020 17:16 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
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  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/1861182

Title:
  bionic/linux-azure: 5.0.0-1030.32 -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: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Thursday, 30. January 2020 17: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
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  variant: debs

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

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


[Kernel-packages] [Bug 1861182] Re: bionic/linux-azure: 5.0.0-1030.32 -proposed tracker

2020-01-30 Thread Stefan Bader
** Summary changed:

- bionic/linux-azure:  -proposed tracker
+ bionic/linux-azure: 5.0.0-1030.32 -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-lrm
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-lrm
 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1861182

Title:
  bionic/linux-azure: 5.0.0-1030.32 -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: 1861192
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Thursday, 30. January 2020 17: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
  trackers:
bionic/linux-azure/azure-kernel: bug 1861180
  variant: debs

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

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


[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0

2020-01-30 Thread Timo Aaltonen
please test the kernel at

https://aaltoset.kapsi.fi/5.4-hangfix

should be enough to install linux-image* and linux-modules* packages;
first download them and then run 'sudo dpkg -i linux*.deb', and reboot
once they've been installed.

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

Title:
  system hang: i915 Resetting rcs0 for hang on rcs0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Invalid

Bug description:
  System hangs, unknown cause, When this happens, the mouse pointer
  still moves, but I can't do anything else with the keys or clicking in
  the UI.  Only recover I have found is a hard power-off

  Last bit of kern.log below:

  Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: 
ecode 9:1:0x, hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
  Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report 
on bugs.freedesktop.org against DRI -> DRM/Intel
  Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required 
to analyze GPU hangs, so please always attach it.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to 
/sys/class/drm/card0/error
  Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting 
chip for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks 
suppressed
  Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
  Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 
01 00 00 00 ff 50 30  04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 
7d 8f 00
  Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 30 12:51:24 2020
  InstallationDate: Installed on 2018-06-18 (591 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)

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

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


[Kernel-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-01-30 Thread diarmuid
Here is the Ettus benchmark tool
https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio

You would need an Ettus device to run those tests.

I cant test the affected node now as it is in production unfortunately.

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In this particular case description, the nodes are USRP x310s. However, we 
have the same issue with N210 nodes dropping samples connected to the BCM57416 
NetXtreme-E Dual-Media 10G RDMA Ethernet device.

  There is no problem with the USRPs themselves, as we have tested them
  with normal 1G network cards and have no dropped samples.

  Personally I think its something to do with the 10G network card,
  possibly on a ubuntu driver???

  Note, Dell have said there is no hardware problem with the 10G
  interfaces

  I have followed the 

[Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

2020-01-30 Thread Timo Aaltonen
so you have radeon graphics?

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

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

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

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


[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week

2020-01-30 Thread Colin Ian King
Running w/o swapfile and zswap and just stress-ng brk and stack
stressors with NO file I/O can also lock the system.

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

Title:
  4.15 kernel hard lockup about once a week

Status in linux package in Ubuntu:
  Incomplete
Status in zram-config package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in zram-config source package in Bionic:
  Confirmed

Bug description:
  My main server has been running into hard lockups about once a week
  ever since I switched to the 4.15 Ubuntu 18.04 kernel.

  When this happens, nothing is printed to the console, it's effectively
  stuck showing a login prompt. The system is running with panic=1 on
  the cmdline but isn't rebooting so the kernel isn't even processing
  this as a kernel panic.

  
  As this felt like a potential hardware issue, I had my hosting provider give 
me a completely different system, different motherboard, different CPU, 
different RAM and different storage, I installed that system on 18.04 and moved 
my data over, a week later, I hit the issue again.

  We've since also had a LXD user reporting similar symptoms here also on 
varying hardware:
https://github.com/lxc/lxd/issues/5197

  
  My system doesn't have a lot of memory pressure with about 50% of free memory:

  root@vorash:~# free -m
totalusedfree  shared  buff/cache   
available
  Mem:  31819   17574 402 513   13842   
13292
  Swap: 159092687   13222

  I will now try to increase console logging as much as possible on the
  system in the hopes that next time it hangs we can get a better idea
  of what happened but I'm not too hopeful given the complete silence on
  the console when this occurs.

  System is currently on:
Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  But I've seen this since the GA kernel on 4.15 so it's not a recent 
regression.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 23 16:12 seq
   crw-rw 1 root audio 116, 33 Oct 23 16:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/22822/fd/10: Permission denied
   Cannot stat file /proc/22831/fd/10: Permission denied
  DistroRelease: Ubuntu 18.04
  HibernationDevice:
   RESUME=none
   CRYPTSETUP=n
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S1200SP
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 
panic=1 verbose console=tty0 console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: S1200SP.86B.03.01.1029.012520180838
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S1200SP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H57532-271
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..:
  dmi.product.family: Family
  dmi.product.name: S1200SP
  dmi.product.version: 
  dmi.sys.vendor: Intel 

[Kernel-packages] [Bug 1861419] Re: kworker takes a lot of CPU

2020-01-30 Thread corrado venturini
same problem on same hardware with Ubuntu 20.04 alpha
corrado@corrado-HP-p4-ff--0124:~$ inxi -SMCx
System:Host: corrado-HP-p4-ff--0124 Kernel: 5.4.0-12-generic x86_64 bits: 
64 compiler: gcc 
   v: 9.2.1 Desktop: Gnome 3.34.3 Distro: Ubuntu 20.04 LTS (Focal 
Fossa) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC 
   v: 0991100600087 serial:  
   Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  
UEFI: Insyde 
   v: F.36 date: 12/18/2014 
CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP 
arch: Haswell 
   rev: 1 L2 cache: 3072 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19156 
   Speed: 2689 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 2687 2: 
2689 3: 2395 
   4: 2396 
corrado@corrado-HP-p4-ff--0124:~$

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

Title:
  kworker takes a lot of CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kworker takes a lot of CPU. no other app are active.

  top - 15:52:50 up 8 min,  1 user,  load average: 1,16, 1,24, 0,77
  Tasks: 204 total,   2 running, 202 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  4,9 us, 26,2 sy,  0,0 ni, 62,3 id,  0,0 wa,  0,0 hi,  6,6 si,  0,0 
st
  MiB Mem :   3867,1 total,   1737,2 free,895,9 used,   1234,0 buff/cache
  MiB Swap:   4096,0 total,   4096,0 free,  0,0 used.   2568,5 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
239 root  20   0   0  0  0 R  81,2   0,0   0:31.92 
kworker/0+
   1623 corrado   20   0  304848  53436  38048 S   6,2   1,3   0:13.02 Xorg
   1921 corrado   20   0  323484  10544   8768 S   6,2   0,3   0:00.42 
ibus-daem+
  1 root  20   0  167140  10868   7952 S   0,0   0,3   0:02.04 systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1613 F pulseaudio
   /dev/snd/controlC1:  corrado1613 F pulseaudio
  Date: Thu Jan 30 15:49:01 2020
  InstallationDate: Installed on 2019-12-28 (33 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=24e2ba6f-1b75-4b3c-835e-63387635551b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.sku: J4R70EA#ABZ
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1858583] Re: xenial/linux-cascade: 4.4.0-1013.15 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-cascade: 4.4.0-1013.15 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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: '1859718'
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Complete
  phase-changed: Thursday, 30. January 2020 15:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1858582
  variant: debs

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

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


[Kernel-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

2020-01-30 Thread Łukasz Zemczak
I have accepted nvidia-settings for bionic, but let's keep an eye out
for any eventual breakages of reverse-dependencies of libxnvctrl0. This
SRU dropped the (minor) NV_ID symbol without bumping the SONAME -
Alberto asserts that it is highly unlikely to cause any problems, but
just in case let's at least give a spin to these packages:

$ reverse-depends libxnvctrl0
Reverse-Depends
===
* conky-all [amd64]
* indicator-sensors [amd64 arm64 armhf ppc64el s390x]
* libhwloc-plugins
* libmyth [amd64 arm64 armhf ppc64el s390x]
* libxnvctrl-dev
* mate-sensors-applet-nvidia [amd64 armhf]
* nvidia-settings [amd64 arm64 armhf i386 ppc64el]
* psensor [amd64]
* xfce4-sensors-plugin [amd64 arm64 armhf ppc64el s390x]

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  In Progress
Status in nvidia-settings source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to collect information about X server
    crashes from coredumpctl, when available.
  - Updated the nvidia-drm kernel module for compatibility with the
    removal of the DRIVER_PRIME flag in recent Linux kernel versions.
  - Enabled parallel GLSL shader linking by default; i.e., allow
    GL_ARB_parallel_shader_compile to work without first calling
    glMaxShaderCompilerThreadsARB().
  - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC
    Compatible monitors on supported GPUs.For more details, see
    "Configuring Multiple Display Devices on One X Screen" in the 

[Kernel-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

2020-01-30 Thread Łukasz Zemczak
Hello Alberto, or anyone else affected,

Accepted nvidia-settings into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/440.44-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nvidia-settings (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  In Progress
Status in nvidia-settings source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to 

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

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

apport-collect 1861423

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

Title:
  The temperature rises when connected to electricity

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the kernel update, I have noticed a huge temperature increase
  when connected to electricity in all my laptops

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

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


[Kernel-packages] [Bug 1861119] Re: trusty/linux-aws: 4.4.0-1062.66 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-trusty

** 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: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 30. January 2020 13:49 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 30. January 2020 15:46 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 30. January 2020 15:46 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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


[Kernel-packages] [Bug 1858880] Re: focal/linux-5.4: 5.4.0-12.15 -proposed tracker

2020-01-30 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  focal/linux-5.4: 5.4.0-12.15 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules-5.4
main: linux-5.4
meta: linux-meta-5.4
signed: linux-signed-5.4
  phase: Holding before Promote to Release
  phase-changed: Thursday, 30. January 2020 15:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
focal/linux-5.4/pc-kernel: bug 1859023
focal/linux-5.4/pc-lowlatency-kernel: bug 1859024
focal/linux-oem-5.4: bug 1858879
focal/linux-raspi2-5.4: bug 1861410
  variant: debs

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

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


[Kernel-packages] [Bug 1858880] Re: focal/linux-5.4: 5.4.0-12.15 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules-5.4
main: linux-5.4
meta: linux-meta-5.4
signed: linux-signed-5.4
- phase: Testing
- phase-changed: Thursday, 16. January 2020 08:26 UTC
+ phase: Holding before Promote to Release
+ phase-changed: Thursday, 30. January 2020 15:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   regression-testing: Ongoing -- testing in progress
  trackers:
focal/linux-5.4/pc-kernel: bug 1859023
focal/linux-5.4/pc-lowlatency-kernel: bug 1859024
focal/linux-oem-5.4: bug 1858879
focal/linux-raspi2-5.4: bug 1861410
  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/1858880

Title:
  focal/linux-5.4: 5.4.0-12.15 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules-5.4
main: linux-5.4
meta: linux-meta-5.4
signed: linux-signed-5.4
  phase: Holding before Promote to Release
  phase-changed: Thursday, 30. January 2020 15:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
focal/linux-5.4/pc-kernel: bug 1859023
focal/linux-5.4/pc-lowlatency-kernel: bug 1859024
focal/linux-oem-5.4: bug 1858879
focal/linux-raspi2-5.4: bug 1861410
  variant: debs

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

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


[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

2020-01-30 Thread daniel CURTIS
Hello.

Today, I've noticed two entries about 'ecryptfs_decrypt_page' and
'ecryptfs_readpage' errors in `/var/log/syslog` file. I have no idea if
there was/is more such entries. However, it looks this way:

,[ ✖ Error ]
| kernel: [25312.360714] ecryptfs_decrypt_page: Error attempting to read lower 
page; rc = [-4]
| kernel: [25312.360724] ecryptfs_readpage: Error decrypting page; rc = [-4]
`

There was not any system slowdowns, freezing etc. Anyway, `/home`
partition was encrypted during installation with eCryptfs (vide
`/home/.ecryptfs/t4/.Private`). Here are some technical informations
about system:

,[ ✖ lsb_release ]
| Distributor ID:   Ubuntu
| Description:  Ubuntu 16.04.6 LTS
| Release:  16.04
| Codename: xenial
| ---
| Linux:4.4.0-173-generic
| Architecture: i686/x86_32
`

It seems, that I'm not only one Xenial user who's seeing these errors (I
mean another comments, for example #16 by Stefan Wagner etc).

Thanks, best regards.

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

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1861423] [NEW] The temperature rises when connected to electricity

2020-01-30 Thread Jose Manuel
Public bug reported:

After the kernel update, I have noticed a huge temperature increase when
connected to electricity in all my laptops

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

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

Title:
  The temperature rises when connected to electricity

Status in linux package in Ubuntu:
  New

Bug description:
  After the kernel update, I have noticed a huge temperature increase
  when connected to electricity in all my laptops

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

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


[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

2020-01-30 Thread Ubuntu Kernel Bot
** 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

** 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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
- phase: Packaging
- phase-changed: Thursday, 30. January 2020 14:17 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 30. January 2020 15:12 UTC
  reason:
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  variant: debs

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

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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: 1858880
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 30. January 2020 15:12 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  variant: debs

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

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


  1   2   3   >