date:20201103

SRU submission:
https://lists.ubuntu.com/archives/kernel-team/2020-November/thread.html#114535

** Changed in: linux (Ubuntu Hirsute)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
(unassigned)

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

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

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

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  Undetected Data corruption in MPI workloads that use VSX for
  reductions on POWER9 DD2.1 systems

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  * A data integrity issue was observed on POWER 9 (DD2.1) systems.

  * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with
  kernel 5.8.0-26 kernel.

  * The root cause is found in the compiling of p9_hmi_special_emu().

  * When doing a VMX store (in __get_user_atomic_128_aligned()) to a
  buffer (vbuf), the buffer is not 128 bit aligned.

  [Fix]

  * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1
  VSX CI load emulation"

  * d1781f237047 "selftests/powerpc: Make alignment handler test P9N
  DD2.1 vector CI load workaround"

  [Test Case]

  * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu
  20.04, 20.10 or 21.04 installed.

  * It's best to test this based on a sample application and test case
"selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround"

  [Regression Potential]

  * The regression risk is relatively moderate, because:

  * it only happens with special VSX (vector) instructions in use, e.g.
  in p9_hmi_special_emu

  * it happens on bare metal only and only on POWER 9 (DD2.1)

  * and the changes are very overseeable (in total one effective code
  line per patch/commit)

  * Since only p9_hmi_special_emu is touched, this will break in case of
  any regressions, but this is already broken based on this bug.

  [Other]

  * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and
  20.10 / 5.8.0-26.

  * Since the development of Hirsute is already open the SRU is
  requested for Hirsute, too.

  * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2.

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

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

[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter

2020-11-03 Thread Chris Guiver

I tried each of

sddm-theme-debian-elarun - 'Debian Elarun' Theme for SDDM X11 display manager
sddm-theme-debian-maui - 'Debian Maui' theme for SDDM X11 display manager
sddm-theme-elarun - 'Elarun' Theme for SDDM X11 display manager
sddm-theme-lubuntu - Lubuntu theme for SDDM X11 display manager
sddm-theme-maldives - 'Maldives' theme for SDDM X11 display manager
sddm-theme-maui - 'Maui' theme for SDDM X11 display manager
sddm-theme-maya - 'Maya' theme for SDDM X11 display manager

and it was the same (flashing effect) for each theme (I skipped trying
`sddm-theme-breeze` as it was going to pull in a lot of KF5 etc, I can’t
see why it would be different, let me know if it’s worth trying)

I added & made default `xdm` and the login flashing disappeared.

This however had the effect of changing the theme used by the panel (I noticed 
it too on *hp dc7700*). I don’t consider this an issue though; they are easily 
changed back in *Appearances*. Changes are
– sddm
* qt style - breeze
* lxqt-theme - Lubuntu Arc
– xdm
* qt style - fusion
* lxqt-theme - frost

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

Title:
  lubuntu groovy; flashing of sddm greeter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu groovy QA-test install on
  dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)

  
  On reboot, the login greeter (sddm) screen isn't nice, with areas of the 
screen flashing white/black/white/black (maybe white & black each second like a 
":" might flash on the clock, only the ":" on the clock is static)

  likely package at fault should be xserver-xorg-video-nouveau

  Photo can be seen at

  https://photos.app.goo.gl/SYPytVxtkKBEj9NY8

  The
  - drop down for session (not selected Lubuntu)
  - language drop down (not US flag)
  - white/black on login picture (not grey name)

  flashes black & white on a cycle...

  The top panel items will eventually stop flashing (ie. session &
  layout) but time or certain actions cause the flashing white then
  black in cycle to occur again.

  ** Expected Result

  No flashing, its irritating & potentially a problem for some with
  certain health conditions.

  ** Not new issue, it's occurred in the past

  hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt)

  I've had this issue before on eoan on hp dx6120 i believe but cannot
  find bug report. The bug was likely not filed as that box was i386 &
  support was being dropped when I noticed it so I didn't see any point.

  It's not new, and no doubt relates to Nvidia cards, and I'm convinced
  I've filed this before on dx6120 so if not eoan, disco, but I've not
  yet found it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  guiverc1095 F pulseaudio
   /dev/snd/controlC0:  guiverc1095 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 11:13:50 2020
  InstallationDate: Installed on 2021-09-17 (-365 days ago)
  InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 990
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Arc

[Kernel-packages] [Bug 1902694] Re: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems

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

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: New

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

Title:
  Undetected Data corruption in MPI workloads that use VSX for
  reductions on POWER9 DD2.1 systems

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux source package in Hirsute:
  New

Bug description:
  SRU Justification:

  [Impact]

  * A data integrity issue was observed on POWER 9 (DD2.1) systems.

  * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with
  kernel 5.8.0-26 kernel.

  * The root cause is found in the compiling of p9_hmi_special_emu().

  * When doing a VMX store (in __get_user_atomic_128_aligned()) to a
  buffer (vbuf), the buffer is not 128 bit aligned.

  [Fix]

  * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1
  VSX CI load emulation"

  * d1781f237047 "selftests/powerpc: Make alignment handler test P9N
  DD2.1 vector CI load workaround"

  [Test Case]

  * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu
  20.04, 20.10 or 21.04 installed.

  * It's best to test this based on a sample application and test case
"selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround"

  [Regression Potential]

  * The regression risk is relatively moderate, because:

  * it only happens with special VSX (vector) instructions in use, e.g.
  in p9_hmi_special_emu

  * it happens on bare metal only and only on POWER 9 (DD2.1)

  * and the changes are very overseeable (in total one effective code
  line per patch/commit)

  * Since only p9_hmi_special_emu is touched, this will break in case of
  any regressions, but this is already broken based on this bug.

  [Other]

  * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and
  20.10 / 5.8.0-26.

  * Since the development of Hirsute is already open the SRU is
  requested for Hirsute, too.

  * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2.

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

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

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-11-03 Thread Kai-Heng Feng

Dan,
Given that it's a kernel regression, would it be possible to try mainline 
kernel and do a kernel bisection if issue persists?

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

Title:
  NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Running focal on a desktop, I accidentally clicked "Enable networking"
  in nm-applet, disabling my networking.  When I clicked it again to
  reenable it, my networking did not return.  After unsuccessfully
  poking at it for a while, I rebooted and saw the below (and still no
  networking).  `rmmod r8169; modprobe r8169` had no (apparent) effect,
  nor did further reboots.  I rebooted onto two different kernels, both
  exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic.

  I was finally only able to restore networking by _rebooting into
  Windows_ and then rebooting back into Ubuntu.

  (My supposition is that NetworkManager/the kernel set *waves hands*
  something on the network card that persists across boots when it was
  disabled, and that wasn't correctly unset when I reenabled networking
  (or on following boots), but Windows _does_ correctly handle that case
  on boot, and reset it to a working state.)

  Apr 23 10:07:43 surprise kernel: [ cut here ]
  Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit 
queue 0 timed out
  Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260
  Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_>
  Apr 23 10:07:43 surprise kernel:  autofs4 btrfs xor zstd_compress raid6_pq 
libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj 
hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km>
  Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P 
  OE 5.4.0-26-generic #30-Ubuntu
  Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. 
B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019
  Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260
  Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 
e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 
3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7
  Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286
  Apr 23 10:07:43 surprise kernel: RAX:  RBX: 8a7578b00400 
RCX: 
  Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 
RDI: 0300
  Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 
R09: 0004
  Apr 23 10:07:43 surprise kernel: R10:  R11: 0001 
R12: 0001
  Apr 23 10:07:43 surprise kernel: R13:  R14: 8a758cadc480 
R15: 8a758cadc000
  Apr 23 10:07:43 surprise kernel: FS:  () 
GS:8a758ee4() knlGS:
  Apr 23 10:07:43 surprise kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 
CR4: 003406e0
  Apr 23 10:07:43 surprise kernel: Call Trace:
  Apr 23 10:07:43 surprise kernel:  
  Apr 23 10:07:43 surprise kernel:  ? pfifo_fast_enqueue+0x150/0x150
  Apr 23 10:07:43 surprise kernel:  call_timer_fn+0x32/0x130
  Apr 23 10:07:43 surprise kernel:  __run_timers.part.0+0x180/0x280
  Apr 23 10:07:43 surprise kernel:  ? tick_sched_handle+0x33/0x60
  Apr 23 10:07:43 surprise kernel:  ? tick_sched_timer+0x3d/0x80
  Apr 23 10:07:43 surprise kernel:  ? ktime_get+0x3e/0xa0
  Apr 23 10:07:43 surprise kernel:  run_timer_softirq+0x2a/0x50
  Apr 23 10:07:43 surprise kernel:  __do_softirq+0xe1/0x2d6
  Apr 23 10:07:43 surprise kernel:  ? hrtimer_interrupt+0x13b/0x220
  Apr 23 10:07:43 surprise kernel:  irq_exit+0xae/0xb0
  Apr 23 10:07:43 surprise kernel:  smp_apic_timer_interrupt+0x7b/0x140
  Apr 23 10:07:43 surprise kernel:  apic_timer_interrupt+0xf/0x20
  Apr 23 10:07:43 surprise kernel:  
  Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450
  Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 
58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 
44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d
  Apr 2

[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel

2020-11-03 Thread You-Sheng Yang

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  HP Zbook Studio G7 boots into corrupted screen with PSR featured panel

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  Sreen divided into half after installing Focal 5.4.0-48-generic under
  Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
  Graphics Mode. Screenshot attached as
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
  .

  With some more investigatin, https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
  ("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
  for bug 1849947 is the root cause. This was landed to all Ubuntu
  kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
  unstable currently.

  It seems this panel must have PSR enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 964 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Sep 28 01:50:54 2020
  InstallationDate: Installed on 2020-09-22 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
  MachineType: HP HP ZBook Studio G7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash 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.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: HP
  dmi.bios.version: S91 Ver. 85.28.01
  dmi.board.name: 8736
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.32.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Studio G7
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-03 Thread Hui Wang

@smurf,

What is generated after building? If it is *.deb file, just need to run
'sudo dpkg -i *.deb; reboot'

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems

2020-11-03 Thread Patricia Domingues

** Description changed:

- == Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
- ==
+ SRU Justification:
  
- ---Problem Description---
+ [Impact]
  
- A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52 and
- 20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in the
- compiling of  p9_hmi_special_emu().  When doing a VMX store (in
- __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
- 128 bit aligned.
+ * A data integrity issue was observed on POWER 9 (DD2.1) systems.
  
- The fixes of this bug are accepted upstream:
- 1.
- 
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
- ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load 
emulation")
- 2.
- 
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
- ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")
+ * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with
+ kernel 5.8.0-26 kernel.
+ 
+ * The root cause is found in the compiling of p9_hmi_special_emu().
+ 
+ * When doing a VMX store (in __get_user_atomic_128_aligned()) to a
+ buffer (vbuf), the buffer is not 128 bit aligned.
+ 
+ [Fix]
+ 
+ * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1
+ VSX CI load emulation"
+ 
+ * d1781f237047 "selftests/powerpc: Make alignment handler test P9N DD2.1
+ vector CI load workaround"
+ 
+ [Test Case]
+ 
+ * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu
+ 20.04, 20.10 or 21.04 installed.
+ 
+ * It's best to test this based on a sample application and test case
+   "selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround"
+ 
+ [Regression Potential]
+ 
+ * The regression risk is relatively moderate, because:
+ 
+ * it only happens with special VSX (vector) instructions in use, e.g. in
+ p9_hmi_special_emu
+ 
+ * it happens on bare metal only and only on POWER 9 (DD2.1)
+ 
+ * and the changes are very overseeable (in total one effective code line
+ per patch/commit)
+ 
+ * Since only p9_hmi_special_emu is touched, this will break in case of
+ any regressions, but this is already broken based on this bug.
+ 
+ [Other]
+ 
+ * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and
+ 20.10 / 5.8.0-26.
+ 
+ * Since the development of Hirsute is already open the SRU is requested
+ for Hirsute, too.
+ 
+ * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2.

** Summary changed:

- Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for 
reductions on POWER9 DD2.1 systems
+ Undetected Data corruption in MPI workloads that use VSX for reductions on 
POWER9 DD2.1 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/1902694

Title:
  Undetected Data corruption in MPI workloads that use VSX for
  reductions on POWER9 DD2.1 systems

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

Bug description:
  SRU Justification:

  [Impact]

  * A data integrity issue was observed on POWER 9 (DD2.1) systems.

  * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with
  kernel 5.8.0-26 kernel.

  * The root cause is found in the compiling of p9_hmi_special_emu().

  * When doing a VMX store (in __get_user_atomic_128_aligned()) to a
  buffer (vbuf), the buffer is not 128 bit aligned.

  [Fix]

  * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1
  VSX CI load emulation"

  * d1781f237047 "selftests/powerpc: Make alignment handler test P9N
  DD2.1 vector CI load workaround"

  [Test Case]

  * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu
  20.04, 20.10 or 21.04 installed.

  * It's best to test this based on a sample application and test case
"selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround"

  [Regression Potential]

  * The regression risk is relatively moderate, because:

  * it only happens with special VSX (vector) instructions in use, e.g.
  in p9_hmi_special_emu

  * it happens on bare metal only and only on POWER 9 (DD2.1)

  * and the changes are very overseeable (in total one effective code
  line per patch/commit)

  * Since only p9_hmi_special_emu is touched, this will break in case of
  any regressions, but this is already broken based on this bug.

  [Other]

  * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and
  20.10 / 5.8.0-26.

  * Since the development of Hirsute is already open the SRU is
  requested for Hirsute, too.

  * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2.

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

-- 
Mailing list: https://launchpad.net/~kernel

[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation

2020-11-03 Thread dongdong tao

I've just submitted a patch[1] to upstream for review to help with this problem.
The key is to speed up the writeback rate when the fragmentation is high.
Here are the comments from the patch:

Current way to calculate the writeback rate only considered the
dirty sectors, this usually works fine when the fragmentation
is not high, but it will give us unreasonable small rate when
we are under a situation that very few dirty sectors consumed
a lot dirty buckets. In some case, the dirty bucekts can reached
to CUTOFF_WRITEBACK_SYNC while the dirty data(sectors) noteven
reached the writeback_percent, the writeback rate will still
be the minimum value (4k), thus it will cause all the writes to be
stucked in a non-writeback mode because of the slow writeback.

This patch will try to accelerate the writeback rate when the
fragmentation is high. It calculate the propotional_scaled value
based on below:
(dirty_sectors / writeback_rate_p_term_inverse) * fragment
As we can see, the higher fragmentation will result a larger
proportional_scaled value, thus cause a larger writeback rate.
The fragment value is calculated based on below:
(dirty_buckets *  bucket_size) / dirty_sectors
If you think about it, the value of fragment will be always
inside [1, bucket_size].

This patch only considers the fragmentation when the number of
dirty_buckets reached to a dirty threshold(configurable by
writeback_fragment_percent, default is 50), so bcache will
remain the original behaviour before the dirty buckets reached
the threshold.


[1] https://marc.info/?l=linux-bcache&m=160441418209114&w=1

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

Title:
  Bcache bypasse writeback on caching device with fragmentation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  An upstream bug has been opened on the matter for quite some time now [0].
  I can reproduce easily on our production compute node instance, which are 
trusty host with xenial hwe kernels (4.15.0-101-generic).
  However due to heavy backport and such, doing real tracing is a bit hard 
there.

  I was able to reproduce the behavior on a hwe-bionic kernel as well.
  Since most of our critical deployments use bcache, I think this is a kinda 
nasty bug to have.

  Reproducing the issue is relatively easy with the script provided in the bug 
[1].
  The script used to capture the stats is this one [2].

  [0]: https://bugzilla.kernel.org/show_bug.cgi?id=206767
  [1]: https://pastebin.ubuntu.com/p/YnnvvSRhXK/
  [2]: https://pastebin.ubuntu.com/p/XfVpzg32sN/

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

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

[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter

2020-11-03 Thread Chris Guiver

Lubuntu hirsute install on
dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)

wxl suggested (https://discourse.lubuntu.me/t/login-screen-
flashes/1634/14?u=guiverc) exploration of this, so I did a clean install
so I can play

It's worse than any groovy install, something may have changed, as the
response is different (& worse) .. the whole screen is flashing (except
for top panel)  [instead of just small portions of the 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/1895905

Title:
  lubuntu groovy; flashing of sddm greeter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu groovy QA-test install on
  dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)

  
  On reboot, the login greeter (sddm) screen isn't nice, with areas of the 
screen flashing white/black/white/black (maybe white & black each second like a 
":" might flash on the clock, only the ":" on the clock is static)

  likely package at fault should be xserver-xorg-video-nouveau

  Photo can be seen at

  https://photos.app.goo.gl/SYPytVxtkKBEj9NY8

  The
  - drop down for session (not selected Lubuntu)
  - language drop down (not US flag)
  - white/black on login picture (not grey name)

  flashes black & white on a cycle...

  The top panel items will eventually stop flashing (ie. session &
  layout) but time or certain actions cause the flashing white then
  black in cycle to occur again.

  ** Expected Result

  No flashing, its irritating & potentially a problem for some with
  certain health conditions.

  ** Not new issue, it's occurred in the past

  hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt)

  I've had this issue before on eoan on hp dx6120 i believe but cannot
  find bug report. The bug was likely not filed as that box was i386 &
  support was being dropped when I noticed it so I didn't see any point.

  It's not new, and no doubt relates to Nvidia cards, and I'm convinced
  I've filed this before on dx6120 so if not eoan, disco, but I've not
  yet found it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  guiverc1095 F pulseaudio
   /dev/snd/controlC0:  guiverc1095 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 11:13:50 2020
  InstallationDate: Installed on 2021-09-17 (-365 days ago)
  InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 990
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  guiverc 950 F pulseaudio
   /dev/snd/controlC0:  guiverc 950 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-09-17 (-365 days ago)
  InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  Ls

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

So, the 5.4.0-48 error is the same as the one that appears with 5.9 (and
the one we see with PCI GPUs):

```
[0.00] Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc 
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 
2020 (Ubuntu 5.4.0-48.52-generic 5.4.60)
…
[3.366387] PCI Interrupt Link [LKLN] enabled at IRQ 21
[3.426007] [drm] radeon kernel modesetting enabled.
[3.435680] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 0: 
0xe000 -> 0xefff
[3.456237] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 2: 
0xfebe -> 0xfebe
[3.478847] checking generic (e000 13) vs hw (e000 1000)
[3.478853] fb0: switching to radeondrmfb from VESA VGA
[3.490892] Console: switching to colour dummy device 80x25
[3.490909] radeon :01:00.0: vgaarb: deactivate vga console
[3.491182] PCI Interrupt Link [LNKD] enabled at IRQ 19
[3.491321] [drm] initializing kernel modesetting (RV730 0x1002:0x9495 
0x1002:0x0028 0x00).
[3.491325] [drm] Forcing AGP to PCIE mode
[3.491353] resource sanity check: requesting [mem 0x000c-0x000d], 
which spans more than PCI Bus :00 [mem 0x000d-0x000d window]
[3.491359] caller pci_map_rom+0x71/0x18c mapping multiple BARs
[3.492982] ATOM BIOS: RV730XT
[3.493101] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[3.493104] radeon :01:00.0: GTT: 1024M 0x4000 - 
0x7FFF
[3.493108] [drm] Detected VRAM RAM=1024M, BAR=256M
[3.493110] [drm] RAM width 128bits DDR
[3.493193] [TTM] Zone  kernel: Available graphics memory: 8231890 KiB
[3.493195] [TTM] Zone   dma32: Available graphics memory: 2097152 KiB
[3.493198] [TTM] Initializing pool allocator
[3.493203] [TTM] Initializing DMA pool allocator
[3.493221] [drm] radeon: 1024M of VRAM memory ready
[3.493223] [drm] radeon: 1024M of GTT memory ready.
[3.493230] [drm] Loading RV730 Microcode
[3.493316] [drm] Internal thermal controller without fan control
[3.512582] [drm] radeon: dpm initialized
[3.512696] [drm] GART: num cpu pages 262144, num gpu pages 262144
[3.534540] [drm] PCIE GART of 1024M enabled (table at 0x0014C000).
[3.534726] radeon :01:00.0: WB enabled
[3.534730] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x(ptrval)
[3.534733] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x(ptrval)
[3.541143] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x0005c598 and cpu addr 0x(ptrval)
[3.541147] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.541149] [drm] Driver supports precise vblank timestamp query.
[3.541151] radeon :01:00.0: radeon: MSI limited to 32-bit
[3.541204] [drm] radeon: irq initialized.
…
[5.677888] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
[5.677934] radeon :01:00.0: disabling GPU acceleration
[5.696050] [drm] Radeon Display Connectors
[5.696054] [drm] Connector 0:
[5.696055] [drm]   VGA-1
[5.696057] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 
0x7e4c
[5.696059] [drm]   Encoders:
[5.696061] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[5.696062] [drm] Connector 1:
[5.696063] [drm]   HDMI-A-1
[5.696064] [drm]   HPD2
[5.696066] [drm]   DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 
0x7f1c
[5.696068] [drm]   Encoders:
[5.696069] [drm] DFP2: INTERNAL_UNIPHY1
[5.696070] [drm] Connector 2:
[5.696072] [drm]   DVI-I-1
[5.696073] [drm]   HPD1
[5.696074] [drm]   DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 
0x7e2c
[5.696076] [drm]   Encoders:
[5.696077] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[5.696079] [drm] DFP1: INTERNAL_UNIPHY
…
[5.905120] [drm] fb mappable at 0xE034D000
[5.905124] [drm] vram apper at 0xE000
[5.905126] [drm] size 8294400
[5.905127] [drm] fb depth is 24
[5.905129] [drm]pitch is 7680
[5.905201] fbcon: radeondrmfb (fb0) is primary device
[5.933430] Console: switching to colour frame buffer device 240x67
…
[5.983571] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[5.996432] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on 
minor 0
…
…
[   36.254301] [ cut here ]
[   36.254305] trying to bind memory to uninitialized GART !
[   36.254467] WARNING: CPU: 3 PID: 2559 at 
drivers/gpu/drm/radeon/radeon_gart.c:299 radeon_gart_bind+0xef/0x100 [radeon]
[   36.254469] Modules linked in: zram snd_hda_intel snd_intel_dspcfg 
snd_usb_audio snd_hda_codec snd_hda_core snd_usbmidi_lib snd_hwdep mc snd_pcm 
snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi snd_seq 
edac_mce_amd snd_seq_device snd_t

[Kernel-packages] [Bug 1894232] Re: blank black screen or cursor on top left corner on a black screen problem

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

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

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

Title:
  blank black screen or cursor on top left corner on a black screen
  problem

Status in linux package in Ubuntu:
  Expired

Bug description:
  i am currently using linux mint 20 ulyana with linux version 5.4.0-45
  in which i am facing a problem of a blank black screen on boot or
  either a black screen with a dash on top left corner.Its been
  happening for last one week since i just started using linux this very
  week.

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

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

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

** Attachment added: "dmesg on Linux 5.4.0-48-generic on Ubuntu 20.04, K10 
platform, ATI Radeon HD 4670  (truncated because it was weighting 62MB)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430878/+files/dmesg.ubuntu-20.04.linux-5.4.0-48-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.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/1899304

Title:
  Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop,
  makes GNOME desktop fail to start and games going from 70fps to 7fps,
  slow file loading, audio issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
  2020).

  There is two kernels available on this system:

  - 5.4.0-47-generic
  - 5.4.0-48-generic

  With kernel 5.4.0-47-generic:

  - GNOME shell loads properly on Radeon X1950 PRO,
  - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution.

  Everything looks consistent with the limits and the age of the
  hardware.

  With kernel 5.4.0-48-generic:

  - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen 
is displayed and keyboard shortcuts does not respond, or the top bar is stuck 
between the center and the top of the screen and the shell does not respond, or 
the top bar on the top of the screen but the shell does not respond, to get a 
desktop I run `sudo systemctl stop display-manager` then `startx 
/usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone 
xterm started with startx leads to same issues.
  - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution.

  Note: for unknown reasons, GNOME Shell loads properly on the ATI
  Radeon 9500 but not on the Radeon X1950 PRO.

  Everything is slow. When the game is running, a very high load is
  reported by htop, which does not look like the experience seen on the
  5.4.0-47-generic kernel. When the game is running cycling between
  windows using Alt-Tab takes a lot of second while it's immediate on
  5.4.0-47-generic kernel. Also, even without the game running or on a
  lightweight desktop like LXDE, cycling windows is not smooth and
  window refreshing is slow enough to be noticeable.

  About the hardware, note that:

  - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 
939),
  - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale),
  - there is 3GB of DDR RAM,
  - there is no on-disk swap but zram-based swap in compressed ram is used,
  - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 
port,
  - /tmp is a tmpfs ram disk,
  - CPU is set to performance profile,
  - the install is not really messy and not many packages are installed, this 
USB key is purposed for hardware/system testing and to diagnose such issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  illwieckz   7503 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 11 01:47:48 2020
  InstallationDate: Installed on 2020-07-09 (93 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s11   no wireless extensions.

   lono wireless extensions.
  MachineType: MSI MS-6702E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080011
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-6702E
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnTo

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

Related and similar issue with PCI graphic cards (not AGP ones):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795

While PCI graphic cards are broken on AMD K8/K10 platform for years
(I've reproduced on Linux 4.4, 4.8 and 4.15 from Ubuntu 16.04 Xenial),
AGP cards started to break on Ubuntu with 5.4.0-48-generic (was still
working with 5.4.0-47-generic).

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

Title:
  Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop,
  makes GNOME desktop fail to start and games going from 70fps to 7fps,
  slow file loading, audio issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
  2020).

  There is two kernels available on this system:

  - 5.4.0-47-generic
  - 5.4.0-48-generic

  With kernel 5.4.0-47-generic:

  - GNOME shell loads properly on Radeon X1950 PRO,
  - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution.

  Everything looks consistent with the limits and the age of the
  hardware.

  With kernel 5.4.0-48-generic:

  - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen 
is displayed and keyboard shortcuts does not respond, or the top bar is stuck 
between the center and the top of the screen and the shell does not respond, or 
the top bar on the top of the screen but the shell does not respond, to get a 
desktop I run `sudo systemctl stop display-manager` then `startx 
/usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone 
xterm started with startx leads to same issues.
  - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution.

  Note: for unknown reasons, GNOME Shell loads properly on the ATI
  Radeon 9500 but not on the Radeon X1950 PRO.

  Everything is slow. When the game is running, a very high load is
  reported by htop, which does not look like the experience seen on the
  5.4.0-47-generic kernel. When the game is running cycling between
  windows using Alt-Tab takes a lot of second while it's immediate on
  5.4.0-47-generic kernel. Also, even without the game running or on a
  lightweight desktop like LXDE, cycling windows is not smooth and
  window refreshing is slow enough to be noticeable.

  About the hardware, note that:

  - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 
939),
  - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale),
  - there is 3GB of DDR RAM,
  - there is no on-disk swap but zram-based swap in compressed ram is used,
  - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 
port,
  - /tmp is a tmpfs ram disk,
  - CPU is set to performance profile,
  - the install is not really messy and not many packages are installed, this 
USB key is purposed for hardware/system testing and to diagnose such issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  illwieckz   7503 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 11 01:47:48 2020
  InstallationDate: Installed on 2020-07-09 (93 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s11   no wireless extensions.

   lono wireless extensions.
  MachineType: MSI MS-6702E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080011
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-6702E
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pv

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

** Attachment added: "dmesg on Linux 5.10.0-051000rc1-generic on Ubuntu 20.04, 
K10 platform, ATI Radeon HD 4670 AGP"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430875/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.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/1899304

Title:
  Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop,
  makes GNOME desktop fail to start and games going from 70fps to 7fps,
  slow file loading, audio issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
  2020).

  There is two kernels available on this system:

  - 5.4.0-47-generic
  - 5.4.0-48-generic

  With kernel 5.4.0-47-generic:

  - GNOME shell loads properly on Radeon X1950 PRO,
  - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution.

  Everything looks consistent with the limits and the age of the
  hardware.

  With kernel 5.4.0-48-generic:

  - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen 
is displayed and keyboard shortcuts does not respond, or the top bar is stuck 
between the center and the top of the screen and the shell does not respond, or 
the top bar on the top of the screen but the shell does not respond, to get a 
desktop I run `sudo systemctl stop display-manager` then `startx 
/usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone 
xterm started with startx leads to same issues.
  - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution.

  Note: for unknown reasons, GNOME Shell loads properly on the ATI
  Radeon 9500 but not on the Radeon X1950 PRO.

  Everything is slow. When the game is running, a very high load is
  reported by htop, which does not look like the experience seen on the
  5.4.0-47-generic kernel. When the game is running cycling between
  windows using Alt-Tab takes a lot of second while it's immediate on
  5.4.0-47-generic kernel. Also, even without the game running or on a
  lightweight desktop like LXDE, cycling windows is not smooth and
  window refreshing is slow enough to be noticeable.

  About the hardware, note that:

  - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 
939),
  - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale),
  - there is 3GB of DDR RAM,
  - there is no on-disk swap but zram-based swap in compressed ram is used,
  - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 
port,
  - /tmp is a tmpfs ram disk,
  - CPU is set to performance profile,
  - the install is not really messy and not many packages are installed, this 
USB key is purposed for hardware/system testing and to diagnose such issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  illwieckz   7503 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 11 01:47:48 2020
  InstallationDate: Installed on 2020-07-09 (93 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s11   no wireless extensions.

   lono wireless extensions.
  MachineType: MSI MS-6702E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080011
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-6702E
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cv

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

** Attachment added: "dmesg on Linux 5.9 vanilla on Ubuntu 20.04, K10 platform, 
ATI Radeon HD 4670 AGP"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430874/+files/dmesg.ubuntu-20.04.linux-5.9-vanilla_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.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/1899304

Title:
  Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop,
  makes GNOME desktop fail to start and games going from 70fps to 7fps,
  slow file loading, audio issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
  2020).

  There is two kernels available on this system:

  - 5.4.0-47-generic
  - 5.4.0-48-generic

  With kernel 5.4.0-47-generic:

  - GNOME shell loads properly on Radeon X1950 PRO,
  - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution.

  Everything looks consistent with the limits and the age of the
  hardware.

  With kernel 5.4.0-48-generic:

  - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen 
is displayed and keyboard shortcuts does not respond, or the top bar is stuck 
between the center and the top of the screen and the shell does not respond, or 
the top bar on the top of the screen but the shell does not respond, to get a 
desktop I run `sudo systemctl stop display-manager` then `startx 
/usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone 
xterm started with startx leads to same issues.
  - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution.

  Note: for unknown reasons, GNOME Shell loads properly on the ATI
  Radeon 9500 but not on the Radeon X1950 PRO.

  Everything is slow. When the game is running, a very high load is
  reported by htop, which does not look like the experience seen on the
  5.4.0-47-generic kernel. When the game is running cycling between
  windows using Alt-Tab takes a lot of second while it's immediate on
  5.4.0-47-generic kernel. Also, even without the game running or on a
  lightweight desktop like LXDE, cycling windows is not smooth and
  window refreshing is slow enough to be noticeable.

  About the hardware, note that:

  - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 
939),
  - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale),
  - there is 3GB of DDR RAM,
  - there is no on-disk swap but zram-based swap in compressed ram is used,
  - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 
port,
  - /tmp is a tmpfs ram disk,
  - CPU is set to performance profile,
  - the install is not really messy and not many packages are installed, this 
USB key is purposed for hardware/system testing and to diagnose such issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  illwieckz   7503 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 11 01:47:48 2020
  InstallationDate: Installed on 2020-07-09 (93 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s11   no wireless extensions.

   lono wireless extensions.
  MachineType: MSI MS-6702E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080011
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-6702E
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

For some reason I was able to compile v5.4 and v5.5 from torvalds
branchs with `make -j$(nproc) deb-pkg` but starting with v5.6 I had to
use `make -j$(nproc) bindeb-pkg`, in the end I lacked some modules (like
my network driver, that did not helped me) but radeon one was there so
tests could have been done.

The GNOME desktop opened properly with 5.4, 5.5, 5.6, 5.7 and 5.8. But
when v5.9, I just got the desktop (GDM is configured to autologin)
restarting again and again, only showing me a mouse cursor before dying.

The errors in dmesg were similar to the one I found with PCI devices
(not AGP ones!) on the same AMD K8 or K10-based motherboard I reproduce
issue with AGP devices.

Also, the errors in vanilla 5.9 look to be the same as the one seen in
5.10-rc1 from mainline PPA.

Here is a sample of captured dmesg error on vanilla 5.9:

```
[5.242322] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
[5.242359] radeon :01:00.0: disabling GPU acceleration
…

[   34.558885] [ cut here ]
[   34.558889] trying to bind memory to uninitialized GART !
[   34.559048] WARNING: CPU: 1 PID: 2516 at 
drivers/gpu/drm/radeon/radeon_gart.c:299 radeon_gart_bind+0xdf/0xf0 [radeon]
[   34.559050] Modules linked in: zram snd_usb_audio snd_hda_intel 
snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core snd_hwdep snd_pcm 
snd_seq_midi kvm_amd snd_seq_midi_event ccp joydev kvm snd_seq snd_rawmidi 
input_leds snd_timer snd_seq_device snd soundcore k10temp mac_hid serio_raw 
binfmt_misc sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables btrfs 
blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear 
uas usb_storage hid_generic usbhid hid radeon i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm psmouse forcedeth 
i2c_nforce2
[   34.559107] CPU: 1 PID: 2516 Comm: gnome-shell Not tainted 5.9.0 #1
[   34.559109] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./AM2NF3-VSTA, BIOS P3.20 10/09/2009
[   34.559178] RIP: 0010:radeon_gart_bind+0xdf/0xf0 [radeon]
[   34.559184] Code: 00 48 89 ef 48 8b 40 60 e8 0e 2f 44 df 31 c0 48 83 c4 08 
5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 c7 c7 38 6f 6b c0 e8 23 0c 6d de <0f> 0b b8 
ea ff ff ff eb dc 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00
[   34.559187] RSP: 0018:c030838f7a28 EFLAGS: 00010282
[   34.559191] RAX:  RBX: a0cf6b88eb80 RCX: 0027
[   34.559193] RDX: 0027 RSI: 0086 RDI: a0cf6fc98d08
[   34.559196] RBP: c030838f7b28 R08: a0cf6fc98d00 R09: 0004
[   34.559198] R10:  R11: 0001 R12: c030838f7b28
[   34.559201] R13: a0cf6a622868 R14: a0cf6c7cc6e8 R15: c030838f7b28
[   34.559204] FS:  7f46ae245cc0() GS:a0cf6fc8() 
knlGS:
[   34.559207] CS:  0010 DS:  ES:  CR0: 80050033
[   34.559210] CR2: 56494261c1c8 CR3: 00040bfe6000 CR4: 06e0
[   34.559212] Call Trace:
[   34.559286]  radeon_ttm_backend_bind+0x58/0x210 [radeon]
[   34.559305]  ttm_tt_bind+0x32/0x60 [ttm]
[   34.559321]  ttm_bo_handle_move_mem+0x236/0x590 [ttm]
[   34.559339]  ttm_bo_validate+0x16c/0x180 [ttm]
[   34.559407]  ? drm_ioctl_kernel+0xe9/0xf0 [drm]
[   34.559422]  ttm_bo_init_reserved+0x2ae/0x320 [ttm]
[   34.559438]  ttm_bo_init+0x6d/0xf0 [ttm]
[   34.559504]  ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon]
[   34.559569]  radeon_bo_create+0x184/0x210 [radeon]
[   34.559634]  ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon]
[   34.559703]  radeon_gem_object_create+0xa9/0x180 [radeon]
[   34.559773]  ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon]
[   34.559840]  radeon_gem_create_ioctl+0x66/0x120 [radeon]
[   34.559850]  ? tomoyo_path_number_perm+0x66/0x1d0
[   34.559918]  ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon]
[   34.559968]  drm_ioctl_kernel+0xaa/0xf0 [drm]
[   34.560021]  drm_ioctl+0x1ec/0x390 [drm]
[   34.560090]  ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon]
[   34.560152]  radeon_drm_ioctl+0x49/0x80 [radeon]
[   34.560160]  __x64_sys_ioctl+0x83/0xb0
[   34.560167]  do_syscall_64+0x33/0x80
[   34.560174]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   34.560179] RIP: 0033:0x7f46b369550b
[   34.560183] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
[   34.560186] RSP: 002b:7ffdb7421658 EFLAGS: 0246 ORIG_RAX: 
0010
[   34.560189] RAX: ffda RBX: 7ffdb74216d0 RCX: 7f46b369550b
[   34.560192] RDX: 7ffdb74216d0 RSI: c020645d RDI: 000e
[   34.560194] RBP: c020645d R08: 0011 R09: 0005
[   34.560197] R10: 56494245c010 R11: 0246 R12: 0

[Kernel-packages] [Bug 1902578] Re: Ethernet no link lights after reboot (Intel i225-v 2.5G)

2020-11-03 Thread Sandy Patterson

** 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/1902578

Title:
  Ethernet no link lights after reboot (Intel i225-v 2.5G)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've found that on stock focal the ethernet device on my ASUS ROG
  Strix B550-F wifi motherboard gets no link lights after rebooting. I
  am able to cold boot it with the network cable unplugged and then the
  ethernet works as expected after re-plugging the ethernet.

  Workaround:
  I have installed the latest mainline kernel from 
https://github.com/pimlie/ubuntu-mainline-kernel.sh which appears to solve the 
issue. (vmlinuz-5.9.3-050903-generic)

  This issue looks similar although I wasn't able to find the firmware for my 
motherboard so I didn't try the solution:
  
https://askubuntu.com/questions/1244745/ubuntu-20-04-intel-network-connectivity-issue-bug-in-igc

  I found here that I could cold boot and it would work:
  https://ubuntuforums.org/showthread.php?t=2444239

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   3328 F pulseaudio
   /dev/snd/controlC1:  apatterson   3328 F pulseaudio
   /dev/snd/controlC2:  apatterson   3328 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  2 14:10:10 2020
  InstallationDate: Installed on 2020-10-23 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUS System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=5254abc1-6ff1-4753-96c8-97b84156de0b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1004:bd08/13/2020:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  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/1902578/+subscriptions

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

[Kernel-packages] [Bug 1902578] Re: Ethernet no link lights after reboot (Intel i225-v 2.5G)

2020-11-03 Thread Sandy Patterson

I believe the bisect is done:

Building this commit causes the ethernet to work after reboots. (a PHY
problem seems to make sense as there's no link lights).

bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0 is the first new commit
commit bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0
Author: Sasha Neftin 
Date:   Wed Jan 8 10:19:24 2020 +0200

igc: Add PHY power management control

PHY power management control should provide a reliable and accurate
indication of PHY reset completion and decrease the delay time
after a PHY reset

Signed-off-by: Sasha Neftin 
Tested-by: Aaron Brown 
Signed-off-by: Jeff Kirsher 

 drivers/net/ethernet/intel/igc/igc_defines.h |  1 +
 drivers/net/ethernet/intel/igc/igc_phy.c | 16 +++-
 drivers/net/ethernet/intel/igc/igc_regs.h|  1 +
 3 files changed, 17 insertions(+), 1 deletion(-)

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

Title:
  Ethernet no link lights after reboot (Intel i225-v 2.5G)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've found that on stock focal the ethernet device on my ASUS ROG
  Strix B550-F wifi motherboard gets no link lights after rebooting. I
  am able to cold boot it with the network cable unplugged and then the
  ethernet works as expected after re-plugging the ethernet.

  Workaround:
  I have installed the latest mainline kernel from 
https://github.com/pimlie/ubuntu-mainline-kernel.sh which appears to solve the 
issue. (vmlinuz-5.9.3-050903-generic)

  This issue looks similar although I wasn't able to find the firmware for my 
motherboard so I didn't try the solution:
  
https://askubuntu.com/questions/1244745/ubuntu-20-04-intel-network-connectivity-issue-bug-in-igc

  I found here that I could cold boot and it would work:
  https://ubuntuforums.org/showthread.php?t=2444239

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   3328 F pulseaudio
   /dev/snd/controlC1:  apatterson   3328 F pulseaudio
   /dev/snd/controlC2:  apatterson   3328 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  2 14:10:10 2020
  InstallationDate: Installed on 2020-10-23 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUS System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=5254abc1-6ff1-4753-96c8-97b84156de0b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1004:bd08/13/2020:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  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/1902578/+subscriptions

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

[Kernel-packages] [Bug 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems

** Tags removed: severity-medium
** Tags added: severity-high

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

Title:
  Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX
  for reductions on POWER9 DD2.1 systems

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

Bug description:
  == Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
  ==

  ---Problem Description---

  A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52
  and 20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in
  the compiling of  p9_hmi_special_emu().  When doing a VMX store (in
  __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
  128 bit aligned.

  The fixes of this bug are accepted upstream:
  1.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
  ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load 
emulation")
  2.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
  ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")

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

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

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

** 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/1899304

Title:
  Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop,
  makes GNOME desktop fail to start and games going from 70fps to 7fps,
  slow file loading, audio issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
  2020).

  There is two kernels available on this system:

  - 5.4.0-47-generic
  - 5.4.0-48-generic

  With kernel 5.4.0-47-generic:

  - GNOME shell loads properly on Radeon X1950 PRO,
  - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution.

  Everything looks consistent with the limits and the age of the
  hardware.

  With kernel 5.4.0-48-generic:

  - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen 
is displayed and keyboard shortcuts does not respond, or the top bar is stuck 
between the center and the top of the screen and the shell does not respond, or 
the top bar on the top of the screen but the shell does not respond, to get a 
desktop I run `sudo systemctl stop display-manager` then `startx 
/usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone 
xterm started with startx leads to same issues.
  - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution.

  Note: for unknown reasons, GNOME Shell loads properly on the ATI
  Radeon 9500 but not on the Radeon X1950 PRO.

  Everything is slow. When the game is running, a very high load is
  reported by htop, which does not look like the experience seen on the
  5.4.0-47-generic kernel. When the game is running cycling between
  windows using Alt-Tab takes a lot of second while it's immediate on
  5.4.0-47-generic kernel. Also, even without the game running or on a
  lightweight desktop like LXDE, cycling windows is not smooth and
  window refreshing is slow enough to be noticeable.

  About the hardware, note that:

  - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 
939),
  - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale),
  - there is 3GB of DDR RAM,
  - there is no on-disk swap but zram-based swap in compressed ram is used,
  - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 
port,
  - /tmp is a tmpfs ram disk,
  - CPU is set to performance profile,
  - the install is not really messy and not many packages are installed, this 
USB key is purposed for hardware/system testing and to diagnose such issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  illwieckz   7503 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 11 01:47:48 2020
  InstallationDate: Installed on 2020-07-09 (93 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s11   no wireless extensions.

   lono wireless extensions.
  MachineType: MSI MS-6702E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080011
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-6702E
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-6702E
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://

[Kernel-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2.1

---
alsa-lib (1.2.2-2.1ubuntu2.1) focal; urgency=medium

  * d/p/0001-ucm-add-a-check-for-the-empty-configuration.patch
  - Fix the failure on init the HDA-Intel sound card, because there
is no init mixer values in the ucm, the alsa-lib should return
error and then let alsautils init this sound card in the legacy
HDA way. (LP: #1897934)

 -- Hui Wang   Thu, 22 Oct 2020 11:50:50 +0100

** Changed in: alsa-lib (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  Invalid
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the latest alsa-lib (v1.2.3+)

  [Test]
  Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  muted.

  Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  not muted.

  [Regression Potential]
  This could make the ucm audio fail to initialize, but this possibility is
  very low, since this patch is from upstream, and I tested on a ucm based
  machine, the audio is good.

  
  On boot into the live session - or on first install the sound level is muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions

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

[Kernel-packages] [Bug 1897934] Update Released

2020-11-03 Thread Chris Halse Rogers

The verification of the Stable Release Update for alsa-lib has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  Invalid
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the latest alsa-lib (v1.2.3+)

  [Test]
  Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  muted.

  Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  not muted.

  [Regression Potential]
  This could make the ucm audio fail to initialize, but this possibility is
  very low, since this patch is from upstream, and I tested on a ucm based
  machine, the audio is good.

  
  On boot into the live session - or on first install the sound level is muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1

** 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/1902795

Title:
  PCI graphics broken on AMD K8/K10 platform (while it works on Intel)
  verified from Linux 4.4 to 5.10-rc1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

This bug was fixed in the package systemd - 245.4-4ubuntu3.3

---
systemd (245.4-4ubuntu3.3) focal; urgency=medium

  [ Rafael David Tinoco ]
  * d/p/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch:
Reworded and reintroduced patch to fully explain delta is NOT a fix to
LP: #1861941 if the bcache-tools patch exists, but should be kept anyway
as the change makes sense for a better experience to end user.
(LP: #1861941)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f8f64b3b58a04a83b1c426818b9affc41e0bff6c

  [ Dan Streetman ]
  * d/p/lp1882596-man-fix-some-manvolnum.patch:
- fix some man section references (LP: #1882596)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3959ec95eff78d38ec4409807f151572afe83fe9
  * d/p/lp1895418-correct-resolved-conf-cache-default.patch:
- fix resolved.conf default Cache= value (LP: #1895418)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ebe274a2b01658ee39b372d7033c35209510b028
  * d/p/lp1897744-resolve-enable-RES_TRUSTAD-towards-the-127.0.0.53-st.patch:
- add resolv.conf 'trust-ad' option (LP: #1897744)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f6acc8c620b80adab7b048352d85e722b5ba8214
  * d/t/*:
- Update tests to fix false negatives (LP: #1892358)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cee6c31a6caec7888270c9fa8757105ab950ed0c

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a1c1a2bb0ff27faf84fe94583631dfd0f1f4ed8f

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9417ce996766c133c2a33d4102ce1494f3166774

 -- Dan Streetman   Thu, 08 Oct 2020 16:14:56
-0400

** Changed in: systemd (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-

[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

This bug was fixed in the package systemd - 237-3ubuntu10.43

---
systemd (237-3ubuntu10.43) bionic; urgency=medium

  [ Guilherme G. Piccoli ]
  * d/p/lp1830746-bump-mlock-ulimit-to-64Mb.patch:
- Bump the memlock limit to match Focal and newer releases (LP: #1830746)
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61adb797642f3dd2e5c14f7914c2949c665cefe8

  [ Victor Manuel Tapia King ]
  * d/p/lp1896614-core-Avoid-race-when-starting-dbus-services.patch:
- Fix race when starting dbus services (LP: #1896614)
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=373cb6ccd6978a7112bbfd7e5cf4f703a9f8448e

  [ Dan Streetman ]
  * d/t/*,
d/p/lp1892358/0001-test-increase-qemu-timeout-for-TEST-08-and-TEST-09.patch,
d/p/lp1892358/0002-test-increase-timeout-for-TEST-17-UDEV-WANTS.patch,
d/p/lp1892358/0003-test-increase-qemu-timeout-for-TEST-18-and-TEST-19.patch:
- Increase QEMU_TIMEOUT on 'upstream' autopkgtest tests
- Pull latest tests from newer releases to fix false negatives
- Blacklist flaky 'upstream' TEST-03
  (LP: #1892358)
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9fd8391c2499e163515b629a8ca5790898fc599d
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1756b3e1c3e625ed7162cff4909e7a29c315051
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=37f8d73516a84e85e4057d6a92204b4a174af718
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=229ed2076eb773efc548035262b8b8009bf89207
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f2d7b1f952667316cc07a4b3c5010e66ace07a90
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=659befe61bbfeb7afc9efa24458c9745412d7c6d

 -- Victor Manuel Tapia King   Wed, 07 Oct
2020 16:30:03 -0400

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services

[Kernel-packages] [Bug 1892358] Update Released

2020-11-03 Thread Chris Halse Rogers

The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
    ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
    s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0%

[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

This bug was fixed in the package systemd - 245.4-4ubuntu3.3

---
systemd (245.4-4ubuntu3.3) focal; urgency=medium

  [ Rafael David Tinoco ]
  * d/p/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch:
Reworded and reintroduced patch to fully explain delta is NOT a fix to
LP: #1861941 if the bcache-tools patch exists, but should be kept anyway
as the change makes sense for a better experience to end user.
(LP: #1861941)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f8f64b3b58a04a83b1c426818b9affc41e0bff6c

  [ Dan Streetman ]
  * d/p/lp1882596-man-fix-some-manvolnum.patch:
- fix some man section references (LP: #1882596)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3959ec95eff78d38ec4409807f151572afe83fe9
  * d/p/lp1895418-correct-resolved-conf-cache-default.patch:
- fix resolved.conf default Cache= value (LP: #1895418)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ebe274a2b01658ee39b372d7033c35209510b028
  * d/p/lp1897744-resolve-enable-RES_TRUSTAD-towards-the-127.0.0.53-st.patch:
- add resolv.conf 'trust-ad' option (LP: #1897744)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f6acc8c620b80adab7b048352d85e722b5ba8214
  * d/t/*:
- Update tests to fix false negatives (LP: #1892358)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cee6c31a6caec7888270c9fa8757105ab950ed0c

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a1c1a2bb0ff27faf84fe94583631dfd0f1f4ed8f

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9417ce996766c133c2a33d4102ce1494f3166774

 -- Dan Streetman   Thu, 08 Oct 2020 16:14:56
-0400

** Changed in: systemd (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in bcache-tools source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  SRU TEAM: The last 2 commits show a summary for the merges/changes
  I added some specific (to Bionic) notes in the template.
  Thanks!

  [Impact]

   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.

   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.

   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
  devices can be addressed by their UUIDs and not the ordering they were
  assembled (MAAS depends on this feature, for example).

   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid
  should report those or not, and this discussion "died" after sometime.
  This last item is what the systemd update is all about: to disallow
  /dev/disk/by-XXX/ creation for bcache backing devices (a simple
  change that will reduce end users confusion).

  [Test Case]

   * The reproducer script is here:

     https://paste.ubuntu.com/p/37KGy2Smnp/

   * Bionic can't reproduce the issue with the 18.04 kernel, nor with
  the HWE kernel. Nevertheless, it is preferable that Bionic also do the
  same thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.

  specifically for the verification for systemd, the above script can be
  used, and then check that the bcache uuid symlink isn't present at
  /dev/disk/by-uuid; for example, after running the above reproducer
  script:

  root@lp1861941-f:~# ls -l /dev/bcache/by-uuid/
  total 0
  lrwxrwxrwx 1 root root 13 Nov  2 17:16 651c5532-0a15-4d56-acdf-9c8b2bb559f1 
-> ../../bcache0
  root@lp1861941-f:~# ls -l /dev/disk/by-uuid/$(ls /dev/bcache/by-uuid/)
  lrwxrwxrwx 1 root root 9 Nov  2 17:16 
/dev/disk/by-uuid/651c5532-0a15-4d56-acdf-9c8b2bb559f1 -> ../../vdc

  
  [Regression Potential]

   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
  depending on a wrapper script that heads bcache device superblock. If
  there is a bug in this wrapper the symlinks wouldn't work.

   * Previously we were thinking in asking the kernel team to remove the
  bcache udev event delta script they've done for previous case (LP:
  #1729145). It creates the udev

[Kernel-packages] [Bug 795997] Re: 8086:4238 [HP EliteBook 8540w] wifi led indicator blinks

2020-11-03 Thread Mark

The blinking light bug still exists in Ubuntu 20.04.1 LTS 64bit. 
Computer: HP Elitebook 8640W

The wifi on-off indicator light keeps blinking blue-red after a fresh
install.

The fix proposed by "Thomas Wagner (tomas-wagner) on 2012-07-27" does
fix the problem.

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

Title:
  8086:4238 [HP EliteBook 8540w] wifi led indicator blinks

Status in linux package in Ubuntu:
  Expired

Bug description:
  I do not know if it makes any harm, but after connecting to wifi
  accesspoint the wifi led indicator blinks (red-blue) instead of having
  instant blue. When it is disabled it is constant red. Under Windows it
  is blue all the time when connected.

  The following lines about wifi can be found in dmesg:

  [   17.328753] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 
in-tree:
  [   17.328756] iwlagn: Copyright(c) 2003-2010 Intel Corporation
  [   17.328830] iwlagn :44:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
  [   17.328839] iwlagn :44:00.0: setting latency timer to 64
  [   17.328873] iwlagn :44:00.0: Detected Intel(R) Centrino(R) Ultimate-N 
6300 AGN, REV=0x74
  [   17.345241] iwlagn :44:00.0: device EEPROM VER=0x436, CALIB=0x6
  [   17.345244] iwlagn :44:00.0: Device SKU: 0Xb
  [   17.345246] iwlagn :44:00.0: Valid Tx ant: 0X7, Valid Rx ant: 0X7
  [   17.347634] iwlagn :44:00.0: Tunable channels: 13 802.11bg, 24 802.11a 
channels
  [   17.347717] iwlagn :44:00.0: irq 48 for MSI/MSI-X
  [   17.416111] iwlagn :44:00.0: loaded firmware version 9.221.4.1 build 
25532
  [   17.416362] cfg80211: Ignoring regulatory request Set by core since the 
driver uses its own custom regulatory domain 
  [   17.424545] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
  [   34.341098] wlan0: authenticate with 00:25:9c:d6:94:18 (try 1)
  [   34.534824] wlan0: authenticate with 00:25:9c:d6:94:18 (try 2)
  [   34.535991] wlan0: authenticated
  [   34.536369] wlan0: associate with 00:25:9c:d6:94:18 (try 1)
  [   34.537228] wlan0: RX AssocResp from 00:25:9c:d6:94:18 (capab=0x11 
status=0 aid=1)
  [   34.537234] wlan0: associated
  [   34.543076] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   34.568857] padlock_aes: VIA PadLock not detected.
  [   60.576925] iwlagn :44:00.0: iwlagn_tx_agg_start on ra = 
00:25:9c:d6:94:18 tid = 0

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pkot   1530 F pulseaudio
  CRDA: Error: [Errno 2] Nie ma takiego pliku ani katalogu
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd752 irq 49'
 Mixer name : 'IDT 92HD75B3X5'
 Components : 'HDA:111d7603,103c1521,00100202 
HDA:11c11040,103c3066,00100200'
 Controls  : 19
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 16'
 Mixer name : 'Nvidia GPU 0a HDMI/DP'
 Components : 'HDA:10de000a,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Sat Jun 11 19:51:53 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlIdent:
   Socket 0:
 product info: "RICOH", "Bay8Controller", "", ""
 manfid: 0x, 0x
 function: 254 (unknown)
  PccardctlStatus:
   Socket 0:
 3.3V 16-bit PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   LANGUAGE=pl_PL:en
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=e1ae4207-8aba-4238-b680-459cfadf7b6d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.52
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to natty on 2011-05-14 (27 days ago)
  dmi.bios.date: 11/25/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.0E
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.0E:bd11/25/2010:svnHew

[Kernel-packages] [Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1

** Summary changed:

- PCI graphics seems to be broken since years on AMD K8/K10 platform (work on 
Intel)
+ PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified 
from Linux 4.4 to 5.10-rc1

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

Title:
  PCI graphics broken on AMD K8/K10 platform (while it works on Intel)
  verified from Linux 4.4 to 5.10-rc1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

Here may be the interesting dmesg part when running the ATI Radeon 4350
PCI card on the K10 AGP host with Ubuntu 20.04 Focal and Linux 5.10-rc1
kernel. Note that those messages repeats infinitely and very quickly in
a way the whole journal becomes full rapidly (dropping earlier entries):

```
[   46.802991] trying to bind memory to uninitialized GART !
[   46.803170] WARNING: CPU: 2 PID: 2610 at 
drivers/gpu/drm/radeon/radeon_gart.c:297 radeon_gart_bind+0xf1/0x100 [radeon]
[   46.803173] Modules linked in: zram snd_hda_codec_hdmi binfmt_misc 
snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core 
snd_usbmidi_lib snd_hwdep edac_mce_amd mc snd_seq_midi snd_pcm 
snd_seq_midi_event snd_rawmidi snd_seq joydev snd_seq_device snd_timer 
input_leds kvm_amd snd ccp soundcore kvm k10temp serio_raw mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear radeon i2c_algo_bit ttm 
drm_kms_helper syscopyarea hid_generic sysfillrect sysimgblt fb_sys_fops uas 
usbhid cec usb_storage hid rc_core psmouse drm forcedeth i2c_nforce2
[   46.803296] CPU: 2 PID: 2610 Comm: gnome-shell Not tainted 
5.10.0-051000rc1-generic #202010291359
[   46.803300] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./AM2NF3-VSTA, BIOS P3.20 10/09/2009
[   46.803376] RIP: 0010:radeon_gart_bind+0xf1/0x100 [radeon]
[   46.803383] Code: 00 4c 89 e7 48 8b 40 60 e8 7c 53 3b cd 31 c0 48 83 c4 10 
5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 c7 c7 48 1a 75 c0 e8 65 90 f6 cc <0f> 0b b8 
ea ff ff ff eb dc 66 0f 1f 44 00 00 0f 1f 44 00 00 55 48
[   46.803387] RSP: 0018:b0da81f57a38 EFLAGS: 00010282
[   46.803393] RAX:  RBX: 98801231c6e8 RCX: 98832fd18988
[   46.803396] RDX: ffd8 RSI: 0027 RDI: 98832fd18980
[   46.803400] RBP: b0da81f57a70 R08:  R09: b0da81f57818
[   46.803403] R10: b0da81f57810 R11: 8e752ca8 R12: 988007a4f580
[   46.803406] R13: b0da81f57b08 R14: 988011b19200 R15: 98801231c6e8
[   46.803411] FS:  7f6e1d3dbcc0() GS:98832fd0() 
knlGS:
[   46.803415] CS:  0010 DS:  ES:  CR0: 80050033
[   46.803418] CR2: 55b0490a78f8 CR3: 000106534000 CR4: 06e0
[   46.803421] Call Trace:
[   46.803501]  radeon_ttm_tt_bind+0x7e/0x110 [radeon]
[   46.803519]  ttm_bo_handle_move_mem+0x484/0x4a0 [ttm]
[   46.803534]  ttm_bo_validate+0x137/0x150 [ttm]
[   46.803552]  ttm_bo_init_reserved+0x29f/0x320 [ttm]
[   46.803567]  ttm_bo_init+0x69/0xe0 [ttm]
[   46.803639]  ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon]
[   46.803712]  radeon_bo_create+0x186/0x200 [radeon]
[   46.803784]  ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon]
[   46.803859]  radeon_gem_object_create+0xad/0x190 [radeon]
[   46.803934]  ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[   46.804090]  radeon_gem_create_ioctl+0x69/0x120 [radeon]
[   46.804182]  ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[   46.804279]  drm_ioctl_kernel+0xae/0xf0 [drm]
[   46.804353]  drm_ioctl+0x245/0x400 [drm]
[   46.804435]  ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[   46.804452]  ? usb_hcd_irq+0x2c/0x40
[   46.804521]  radeon_drm_ioctl+0x4e/0x80 [radeon]
[   46.804530]  __x64_sys_ioctl+0x91/0xc0
[   46.804537]  do_syscall_64+0x38/0x90
[   46.804546]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
```

I don't see wrong things in dmesg when running the 4.8 kernel on Xenial
(while experiencing the same bugs), or they are not obviously wrong
enough for me to notice them.

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both sup

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

I've added a screenshot (screen photo) of the GNOME desktop being stuck
and unresponsive while running the ATI Radeon 4350 PCI on the K8 AGP
host.

You'll notice this is the exact same symptom I get with ATI Radeon AGP cards on 
this host starting with kernel 5.4.0-48-generic and later (while that AGP card 
worked flawlessly on 5.4.0-47-generic), see #1899304
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

On the K8 PCie host, the display goes off immediately at kernel launch,
right after GRUB launches it, so there is absolutely nothing to see. If
I'm right, the lockup is so hard the system does not run in background
and I cannot connect through SSH (right, this is the same symptom I get
with the Nvidia PCI card).

I don't have access to recent enough (GL 3) Nvidia AGP cards to compare
symptoms with that GL 3 Nvidia PCI card.

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

** Attachment added: "Screenshot of GNOME desktop frozen on ATI Radeon HD 4350 
PCI on K8 AGP host"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430844/+files/20201103-001858-000.ati-radeon-hd4350pci+k8.jpg

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

I added two screenshots (screen photos) of graphical glitches taken
while running the Nvidia Geforce 8400GS rev.2 PCI on K8 AGP and K10 AGP
hosts. That's the last thing an user can see (it remains on screen), the
desktop never displays. In those case I get dmesg logs through SSH.

On the K8 PCie host, the display goes off immediately at kernel launch,
right after GRUB launches it, so there is absolutely nothing to see. If
I'm right, the lockup is so hard the system does not run in background
and I cannot connect through SSH.

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions

2020-11-03 Thread Eric Mazoob

The problem goes away after the screen times out and I have to log back
in.

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

Title:
  [i915] Noise-like lines of graphics corruption when moving windows in
  Xorg sessions

Status in Mutter:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
  unattended for a while, and then got the error message and now have
  funny lines on activity, e.g. red lines flashing on top of gnome-shell
  bar when switching windows, or white blocks/lines around typing text.

  This is the second or third time it happened, reboot fixes it until
  the error pops up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 19:14:11 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS 
rev.2 PCI on K10 AGP host"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430843/+files/20201102-174932-000.nvidia-geforce-8400gsr2-pci+k10.jpg

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS 
rev.2 PCI on K8 AGP host"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430842/+files/20201103-002441-000.nvidia-geforce-8400gsr2-pci+k8.jpg

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

The interesting thing on Nvidia GS 8400GS rev.2 may be:

[   20.107995] nouveau :03:00.0: DRM: GPU lockup - switching to software 
fbcon
[   20.180130] nouveau :03:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[   20.195263] [drm] Initialized nouveau 1.3.1 20120801 for :03:00.0 on 
minor 0

You'll find the same lines in 4.8 (Xenial) and 5.10-rc1 (Focal) dmesg,
either on K8 (the one with AGP port) and K10 (which also has AGP port).

I forgot to say I also tested this configuration and then, reproduced
the bug for both Nvidia and ATI PCI cards:

Ubuntu 20.04 Focal LTS Linux 5.10.0-051000rc1-generic (from mainline
Ubuntu PPA).

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

** Attachment added: "dmesg on Linux 5.10-rc1 on Ubuntu 20.04, K10 platform, 
Nvidia Geforce 8400GS rev.2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430839/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_Nvidia-Geforce-8400GSr2-PCI.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/1902795

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

** Attachment added: "dmesg on Linux 4.8.0-36 on Ubuntu 16.04, K8 platform, 
Nvidia Geforce 8400GS rev.2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430841/+files/dmesg.ubuntu-16.04.linux-4.8.0-36-generic_MSI-MS-6702E+K8_Nvidia-Geforce-8400GSr2-PCI.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/1902795

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

** Attachment added: "dmesg on Linux 4.8.0-36 on Ubuntu 16.04, K8 platform, ATI 
Radeon HD 4350 PCI"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430840/+files/dmesg.ubuntu-16.04.linux-4.8.0-36-generic_MSI-MS-6702E+K8_ATI-Radeon-HD-4350-PCI.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/1902795

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

** Attachment added: "dmesg on Linux 5.10-rc1 on Ubuntu 20.04, K10 platform, 
ATI Radeon HD 4350 PCI"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430838/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4350-PCI.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/1902795

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

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

2020-11-03 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 1902795

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

Hmm, minor issues in the host list, fixed:

- K10 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
- K8 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual 
core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
- K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
- Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR3 1066MHz, PCIe + PCI

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

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  New

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
  Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
  Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
  Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
  Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

  All those configurations fail with those two PCI GPUs on AMD K8/K10
  platforms.

  I got some logs and screenshots, so I will add them.

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

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

[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc

This is the network config. Let me know if you need more info.

** Attachment added: "network-config.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+attachment/5430820/+files/network-config.png

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

Title:
  [linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We identified an issue with the Linux netvsc driver when used in IP
  forwarding mode.  The problem is that the RSS hash value is not
  propagated to the outgoing packet, and so such packets go out on
  channel 0.  This produces an imbalance across outgoing channels, and a
  possible overload on the single host-side CPU that is processing
  channel 0.   The problem does not occur when Accelerated Networking is
  used because the packets go out through the Mellanox driver.  Because
  it is tied to IP forwarding, the problem is presumably most likely to
  be visible in a virtual appliance device that is doing network load
  balancing or other kinds of packet filtering and redirection.

  We would like to request fixes to this issue in 16.04, 18.04 and
  20.04.

  Two fixes are already in the upstream v5.5+, so they’re already in
  5.8.0-1011.11.

  For 5.4.0-1031.32, the 2 fixes can apply cleanly:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan 
backported them here:
  https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795
  https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a
  (The 2 patches are on the branch 
https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1)

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

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

[Kernel-packages] [Bug 1902795] [NEW] PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)

Public bug reported:

This is an issue I found while investigating #1899304
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

The big concern is that if AGP is disabled, there is no fallback display
option on those platforms.

After having discovered some K8 and K10 computers running AGP cards
stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to try
some PCI cards to know if problems came from AGP or something else, and
I've discovered another issue instead.

Note that I'm not talking about PCI express, but good old PCI.

The other issue I found is that PCI graphics on AMD K8/K10 platform is
broken since years. This got probably unnoticed because such hardware
works on Intel platform and those cards are not very common, so the
chance to fulfill all the requirements to reproduce the bug are not that
high.

To make the test significant enough I used two PCI devices from two
makers, and some that are not so old: they both support OpenGL 3.3, have
512MB of VRAM, and one of them even have HDMI.

- PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
- PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

I've driven tests on four computers:

- K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual 
core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
- K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
- K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
- Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

I tested two Ubuntu versions and multiple kernels:

Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic
Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic
Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic
Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic
Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic

All those configurations fail with those two PCI GPUs on AMD K8/K10
platforms.

I got some logs and screenshots, so I will add them.

** 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/1902795

Title:
  PCI graphics seems to be broken since years on AMD K8/K10 platform
  (work on Intel)

Status in linux package in Ubuntu:
  New

Bug description:
  This is an issue I found while investigating #1899304
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304

  The big concern is that if AGP is disabled, there is no fallback
  display option on those platforms.

  After having discovered some K8 and K10 computers running AGP cards
  stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to
  try some PCI cards to know if problems came from AGP or something
  else, and I've discovered another issue instead.

  Note that I'm not talking about PCI express, but good old PCI.

  The other issue I found is that PCI graphics on AMD K8/K10 platform is
  broken since years. This got probably unnoticed because such hardware
  works on Intel platform and those cards are not very common, so the
  chance to fulfill all the requirements to reproduce the bug are not
  that high.

  To make the test significant enough I used two PCI devices from two
  makers, and some that are not so old: they both support OpenGL 3.3,
  have 512MB of VRAM, and one of them even have HDMI.

  - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA
  - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA

  I've driven tests on four computers:

  - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU 
(dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI
  - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU 
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
  - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single 
core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI
  - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU 
(dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI

  Both PCI GPU work on the Intel based computer, and I get performances that 
looks correct for those GPU given they are PCI ones. You can find real-life use 
case test result here (look for “PCI”):
  https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix

  I tested two Ubuntu versions and multiple kernels:

  Ubuntu 20.04 Focal LTS Linux 5.4.

[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc

To use Azure UDR, I referred to this page:
https://campus.barracuda.com/product/cloudgenfirewall/doc/72516173/how-
to-configure-azure-route-tables-udr-using-azure-portal-and-arm/

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

Title:
  [linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We identified an issue with the Linux netvsc driver when used in IP
  forwarding mode.  The problem is that the RSS hash value is not
  propagated to the outgoing packet, and so such packets go out on
  channel 0.  This produces an imbalance across outgoing channels, and a
  possible overload on the single host-side CPU that is processing
  channel 0.   The problem does not occur when Accelerated Networking is
  used because the packets go out through the Mellanox driver.  Because
  it is tied to IP forwarding, the problem is presumably most likely to
  be visible in a virtual appliance device that is doing network load
  balancing or other kinds of packet filtering and redirection.

  We would like to request fixes to this issue in 16.04, 18.04 and
  20.04.

  Two fixes are already in the upstream v5.5+, so they’re already in
  5.8.0-1011.11.

  For 5.4.0-1031.32, the 2 fixes can apply cleanly:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan 
backported them here:
  https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795
  https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a
  (The 2 patches are on the branch 
https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1)

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

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

[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc

Here is how I reproduce the bug:

Create 3 Ubuntu 16.04 VMs (VM-1, VM gateway, VM-2) on Azure in the same
Resource Group. The kernel should be the linux-azure kernel
4.15.0-1098.109~16.04.1 (or newer). I use Gen1 VM but Gen2 should also
has the same issue; I use the "East US 2" region, but the issue should
reproduce in any region.

Note: none of the VMs use Accelerated Networking, i.e. all of the 3 VMs
use the software NIC "NetVSC".

In my setup, VM-1 and VM-2 are "Standard D8s v3 (8 vcpus, 32 GiB
memory)", and VM-gateway is "Standard DS3 v2 (4 vcpus, 14 GiB memory)".
I happen to name the gateway VM "decui-dpdk", but here actually DPDK is
not used at all (I do intend to use this setup for DPDK in future).

The gateway VM has 3 NICs:
The main NIC (10.0.0.4) is not used in ip-forwarding.
NIC-1's IP is 192.168.80.5
NIC-2's IP is 192.168.81.5.
The gateway VM receives packets from VM-1(192.168.80.4) and forwards
the packets to VM-2 (192.168.81.4).
No firewall rule is used.

The client VM (VM-1, 192.168.80.4) has 1 NIC. It's running iperf2 client.
The server VM (VM-2, 192.168.81.4) has 1 NIC. It's running iperf2 server:
"nohup iperf -s &"

The client VM is sending traffic, through the gateway VM (192.168.80.5,
192.168.81.5), to the server VM.
Note: all the 3 subnets here are in the same VNET(Virtual Net) and 2 Azure UDR
(User Defined Routing) rules must be used to force the traffic to go through
the gateway VM. The IP-forwarding of the gateway VM's NIC-1 and NIC-2 must be
enabled from Azure portal (the setting can only changed when the VM is
"stopped"), and IP-forwarding must be enabled in the gateway VM (i.e. echo 1 >
/proc/sys/net/ipv4/ip_forward). I'll attach some screenshots showing the
network topology and the configuration.

iperf2 uses 512 TCP connections and I limit the bandwidth used by iperf to
<=70% of the per-VM bandwith limit (Note: if the VM uses >70% of the limit,
even with the 2 patches, the ping latency between VM-1 and VM-2 can still
easily go very high, e.g. >200ms -- we'll try to further investigate that).

It looks the per-VM bandwithd limit of the gateway VM (DS3_v2) is 2.6Gbps, so
70% of it is 1.8Gbps.

In the client VM, run something like:
iperf -c 192.168.81.4 -b 3.5m -t 120 -P512
(-b means the per-TCP-connection limit; -P512 means 512 connections, so the
total throughput should be around 3.5*512 = 1792 Mbps; "-t 120" means the test
lasts for 2 minutes. we can abort the test any time by Ctrl+C.)

In the "Server VM, run:
nohup iperf -s &
ping 192.168.80.4 (we can terminate the program by Ctrl+C), and observe the
latency.

In the gateway VM, run "nload" to check the current throughput (if the
current device is not the NIC we want to check, press Right Arrow and
Left Allow), and run "top" to check the CPU utilization (when there are
512 connections, the utilization should be still low, e.g. <25%).

When the iperf2 test is running, the ping latency between VM-1 and VM-2
can easily exceed 100ms or even >300ms, but with the 2 patches applied,
the latency typically should be <20ms.

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

Title:
[linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
New

Bug description:
We identified an issue with the Linux netvsc driver when used in IP
forwarding mode. The problem is that the RSS hash value is not
propagated to the outgoing packet, and so such packets go out on
channel 0. This produces an imbalance across outgoing channels, and a
possible overload on the single host-side CPU that is processing
channel 0. The problem does not occur when Accelerated Networking is
used because the packets go out through the Mellanox driver. Because
it is tied to IP forwarding, the problem is presumably most likely to
be visible in a virtual appliance device that is doing network load
balancing or other kinds of packet filtering and redirection.

We would like to request fixes to this issue in 16.04, 18.04 and
20.04.

Two fixes are already in the upstream v5.5+, so they’re already in
5.8.0-1011.11.

For 5.4.0-1031.32, the 2 fixes can apply cleanly:

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

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

For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:

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

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

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

[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio

I built the v5.5.0 version from torvalds's branch and it works.

So, if it does not work on Ubuntu's 5.4.0-48 I can assume it's was
broken by some Ubuntu custom patch or some backports, making it harder
for me to identify what may have introduced the regression.

I'll try to find the vanilla version that started to fail anyway, that
will be helpful.

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

Title:
  Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop,
  makes GNOME desktop fail to start and games going from 70fps to 7fps,
  slow file loading, audio issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
  2020).

  There is two kernels available on this system:

  - 5.4.0-47-generic
  - 5.4.0-48-generic

  With kernel 5.4.0-47-generic:

  - GNOME shell loads properly on Radeon X1950 PRO,
  - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution.

  Everything looks consistent with the limits and the age of the
  hardware.

  With kernel 5.4.0-48-generic:

  - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen 
is displayed and keyboard shortcuts does not respond, or the top bar is stuck 
between the center and the top of the screen and the shell does not respond, or 
the top bar on the top of the screen but the shell does not respond, to get a 
desktop I run `sudo systemctl stop display-manager` then `startx 
/usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone 
xterm started with startx leads to same issues.
  - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 
resolution,
  - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution.

  Note: for unknown reasons, GNOME Shell loads properly on the ATI
  Radeon 9500 but not on the Radeon X1950 PRO.

  Everything is slow. When the game is running, a very high load is
  reported by htop, which does not look like the experience seen on the
  5.4.0-47-generic kernel. When the game is running cycling between
  windows using Alt-Tab takes a lot of second while it's immediate on
  5.4.0-47-generic kernel. Also, even without the game running or on a
  lightweight desktop like LXDE, cycling windows is not smooth and
  window refreshing is slow enough to be noticeable.

  About the hardware, note that:

  - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 
939),
  - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale),
  - there is 3GB of DDR RAM,
  - there is no on-disk swap but zram-based swap in compressed ram is used,
  - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 
port,
  - /tmp is a tmpfs ram disk,
  - CPU is set to performance profile,
  - the install is not really messy and not many packages are installed, this 
USB key is purposed for hardware/system testing and to diagnose such issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  illwieckz   7503 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 11 01:47:48 2020
  InstallationDate: Installed on 2020-07-09 (93 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s11   no wireless extensions.

   lono wireless extensions.
  MachineType: MSI MS-6702E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080011
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-6702E
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnM

Re: [Kernel-packages] [Bug 1896482] Re: acpi event detection crashes (fwd)

2020-11-03 Thread Jim Cline

Hi Alex,
I see that I am currently running 5.4.0-48-generic, which I think is the 
same version that you originally sent me.  But livepatch alters the 
running kernel without changing its version number, doesn't it?
That's what makes me still wonder if it is the culprit.
thanks--Jim


On Tue, 3 Nov 2020, Jim Cline wrote:

>
>
>
> -- Forwarded message --
> Date: Mon, 02 Nov 2020 23:24:48 -
> From: Alex Hung <1896...@bugs.launchpad.net>
> To: gxgilt...@gmail.com
> Subject: [Bug 1896482] Re: acpi event detection crashes
>
> @jim,
>
> You can check your kernel version by "uname -r".
>
> I also built a rebased one:
> https://people.canonical.com/~alexhung/LP1896482/Ubuntu-5.4.0-52.57/

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

Title:
  acpi event detection crashes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  = SRU Justification =

  [Impact]

  The bug causes the EC driver to fail and ACPI events are no longer
  handled by Linux kernel, i.e lid close no longer triggers suspends.

  [Fix]

  Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid
  initialisation failures.

  The other three patches are prerequisite to apply 03e9a0e05739cf on
  focal kernel.

  [Test]

  Tested with Lenovo ThinkPad X1 Carbon Gen 8

  [Regression Potential]

  Low. The patches were cherry-picked from mainline kernel (two since 5.5
  and two since 5.7)

  = Original Bug Report =

  Right after booting, acpi lid open/close is detected as it should be
  by the kernel, but some time later it crashes, so I have to manually
  suspend the system.  The traceback is here:

  Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here 
]
  Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at 
kernel/workqueue.c:1416 __queue_work+0x337/0x3f0
  Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp 
snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic 
snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal 
intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common 
snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt 
snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel 
aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec 
glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep 
snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm 
videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw 
btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi 
processor_thermal_device bluetooth videodev
  Sep 20 11:35:33 laxmi kernel: [232492.303600]  drm_kms_helper mc wmi_bmof 
i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt 
ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch 
snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec 
snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid 
int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc 
ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme 
psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 
virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel
  Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: 
kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu
  Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 
20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020
  Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query 
acpi_ec_event_processor
  Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 
0010:__queue_work+0x337/0x3f0
  Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 
e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 
01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 
0b e9 fd fd
  Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 
EFLAGS: 00010087
  Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 
0002 RCX: 0004
  Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 
9a2475b03200 RDI: 9a2430215f00
  Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: 
 R09: 0007
  Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: 
 R12: 9a2475af4a00
  Sep 20 1

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

2020-11-03 Thread Brian Murray

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

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

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

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in grub2 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in grub2 source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Invalid

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

2020-11-03 Thread Matthieu Clemenceau

Update: I switched to Groovy and I'm now able to do a full reboot without 
interruption
Issue is resolved on Groovy.

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

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in grub2 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in grub2 source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Invalid

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1902001] Re: USB keyboard layout incorrect after unplugging and replugging

2020-11-03 Thread Sebastien Bacher

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

** This bug has been marked a duplicate of bug 1899509
   Mouse/touchpad settings not applied on hotplug/reconnect

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

Title:
  USB keyboard layout incorrect after unplugging and replugging

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-evdev package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel version: 5.4.0-52-generic (but problem began with 5.4.0-51-generic)
  Keyboard:   Bus 001 Device 018: ID 056e:1063 Elecom Co., Ltd ELECOM 
TK-FCP097

  Expected behaviour:
  USB keyboard layout remains the same when unplugging and replugging in same 
keyboard
  (This was the behaviour on 5.4.0-48-generic and earlier.)

  What happened instead:
  USB keyboard layout changes from:
  < _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,jp,us,us", ",,intl,", 
"grp_led:scroll"

  to:
  > _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,us", ",intl", 
"grp:alt_shift_toggle,grp_led:scroll"
  (output of xprop -root | grep XKB )

  The keyboard layout is reset to the correct layout after logging out
  and back in (or after suspend/resume); however, unplugging and
  replugging the keyboard in causes the same unexpected behaviour.

  Same problem occurs with a different USB keyboard: Bus 001 Device 019:
  ID 0d62:8070 Darfon Electronics Corp. ELECOM Wired Keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler 18578 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 29 16:35:31 2020
  InstallationDate: Installed on 2020-02-05 (266 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Latitude 5500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=fa5c4fdb-0e37-4ef5-b109-3c129736f66c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-12 (170 days ago)
  dmi.bios.date: 07/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd07/06/2020:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc

2020-11-03 Thread Joseph Salisbury

It would be great if we can get the fixes into the next SRU cycle, which
is the last one for 2020.

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

Title:
  [linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We identified an issue with the Linux netvsc driver when used in IP
  forwarding mode.  The problem is that the RSS hash value is not
  propagated to the outgoing packet, and so such packets go out on
  channel 0.  This produces an imbalance across outgoing channels, and a
  possible overload on the single host-side CPU that is processing
  channel 0.   The problem does not occur when Accelerated Networking is
  used because the packets go out through the Mellanox driver.  Because
  it is tied to IP forwarding, the problem is presumably most likely to
  be visible in a virtual appliance device that is doing network load
  balancing or other kinds of packet filtering and redirection.

  We would like to request fixes to this issue in 16.04, 18.04 and
  20.04.

  Two fixes are already in the upstream v5.5+, so they’re already in
  5.8.0-1011.11.

  For 5.4.0-1031.32, the 2 fixes can apply cleanly:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan 
backported them here:
  https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795
  https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a
  (The 2 patches are on the branch 
https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1)

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

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

[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc

I'll provide the instructions to reproduce the bug on Azure.

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

Title:
  [linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We identified an issue with the Linux netvsc driver when used in IP
  forwarding mode.  The problem is that the RSS hash value is not
  propagated to the outgoing packet, and so such packets go out on
  channel 0.  This produces an imbalance across outgoing channels, and a
  possible overload on the single host-side CPU that is processing
  channel 0.   The problem does not occur when Accelerated Networking is
  used because the packets go out through the Mellanox driver.  Because
  it is tied to IP forwarding, the problem is presumably most likely to
  be visible in a virtual appliance device that is doing network load
  balancing or other kinds of packet filtering and redirection.

  We would like to request fixes to this issue in 16.04, 18.04 and
  20.04.

  Two fixes are already in the upstream v5.5+, so they’re already in
  5.8.0-1011.11.

  For 5.4.0-1031.32, the 2 fixes can apply cleanly:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan 
backported them here:
  https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795
  https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a
  (The 2 patches are on the branch 
https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1)

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

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

[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc

Since the 5.0 linux-azure kernel is not maintained anymore, IMO we don't
have to fix this bug for it.

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

Title:
  [linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We identified an issue with the Linux netvsc driver when used in IP
  forwarding mode.  The problem is that the RSS hash value is not
  propagated to the outgoing packet, and so such packets go out on
  channel 0.  This produces an imbalance across outgoing channels, and a
  possible overload on the single host-side CPU that is processing
  channel 0.   The problem does not occur when Accelerated Networking is
  used because the packets go out through the Mellanox driver.  Because
  it is tied to IP forwarding, the problem is presumably most likely to
  be visible in a virtual appliance device that is doing network load
  balancing or other kinds of packet filtering and redirection.

  We would like to request fixes to this issue in 16.04, 18.04 and
  20.04.

  Two fixes are already in the upstream v5.5+, so they’re already in
  5.8.0-1011.11.

  For 5.4.0-1031.32, the 2 fixes can apply cleanly:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan 
backported them here:
  https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795
  https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a
  (The 2 patches are on the branch 
https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1)

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

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

[Kernel-packages] [Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved

2020-11-03 Thread Ian Johnson

** Tags added: uc20

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

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

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

[Kernel-packages] [Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

2020-11-03 Thread Nishant

Hi, we have two machines at the office with this issue and I don't have
access to either of them. I think the patch landed in the upstream
kernel v5.4.73. When can we expect the fix for Focal through the
updates?

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

Title:
   Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic
  #23-Ubuntu) but was advised to report a new bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-22-generic 5.8.0-22.23
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2131 F pulseaudio
   /dev/snd/controlC1:  tim2131 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct 14 13:15:38 2020
  InstallationDate: Installed on 2020-06-03 (132 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20RV
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic 
root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet 
splash i8042.nopnp=1 pci=nocrs 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.8.0-22-generic N/A
   linux-backports-modules-5.8.0-22-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago)
  dmi.bios.date: 06/19/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CJCN29WW
  dmi.board.name: LVA/LVAB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
  dmi.product.family: Lenovo ThinkBook 14-IML
  dmi.product.name: 20RV
  dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
  dmi.product.version: Lenovo ThinkBook 14-IML
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1902694] mpe.py - test script for vmlinux misalignment

--- Comment (attachment only) From wa...@us.ibm.com 2020-11-03 13:57 
EDT---


** Attachment added: "mpe.py - test script for vmlinux misalignment"
   https://bugs.launchpad.net/bugs/1902694/+attachment/5430774/+files/mpe.py

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

Title:
  Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX
  for reductions on POWER9 DD2.1 systems

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

Bug description:
  == Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
  ==

  ---Problem Description---

  A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52
  and 20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in
  the compiling of  p9_hmi_special_emu().  When doing a VMX store (in
  __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
  128 bit aligned.

  The fixes of this bug are accepted upstream:
  1.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
  ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load 
emulation")
  2.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
  ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")

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

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

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

--- Comment From wa...@us.ibm.com 2020-11-03 13:56 EDT---
Hello Patricia,
We have this script(mpe.py) which will detect if a vmlinux has the alignment 
issue or not.  We ran it against 16.04, 18.04, 20.04 and 21.04 kernels, and we 
only found the misalignment in 20.04 and 21.04.  16.04's kernel doesn't have 
the p9_hmi_special_emu().

16.04:
user@ltc-zz9:/tmp/test/boot$ ~/mpe.py vmlinux-4.4.0-193-generic 
System.map-4.4.0-193-generic
Couldn't find p9_hmi_special_emu in objdump output
Error: couldn't find stvx!
18.04:
user@ltc-zz9:/tmp/test/boot$ ~/mpe.py vmlinux-4.15.0-122-generic 
System.map-4.15.0-122-generic
Couldn't find p9_hmi_special_emu in objdump output
stvx found using register r25:
c002988c:ce c9 00 7c stvxv0,0,r25
addi found using offset 32:
c0029884:20 00 21 3b addir25,r1,32
OK - offset is aligned
20.04:
user@ltc-zz9:/tmp/test/boot$ ~/mpe.py vmlinux-5.4.0-52-generic 
System.map-5.4.0-52-generic
stvx found using register r28:
c002cbec:ce e1 00 7c stvxv0,0,r28
addi found using offset 40:
c002cbe4:28 00 81 3b addir28,r1,40

!! Offset is misaligned - bug present !!

20.10:
user@ltc-zz9:/tmp/test/boot$ ~/mpe.py vmlinux-5.8.0-26-generic 
System.map-5.8.0-26-generic
stvx found using register r9:
c0025a78:ce 49 00 7c stvxv0,0,r9
addi found using offset 40:
c0025a70:28 00 21 39 addir9,r1,40

!! Offset is misaligned - bug present !!


I will attach the mpe.py script.

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

Title:
  Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX
  for reductions on POWER9 DD2.1 systems

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

Bug description:
  == Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
  ==

  ---Problem Description---

  A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52
  and 20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in
  the compiling of  p9_hmi_special_emu().  When doing a VMX store (in
  __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
  128 bit aligned.

  The fixes of this bug are accepted upstream:
  1.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
  ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load 
emulation")
  2.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
  ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")

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

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

[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

** Branch linked: lp:~brian-murray/apport/system-slice

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Confirmed
Status in bluez source package in Focal:
  Invalid

Bug description:
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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

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

[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL

Kernel SRU request submitted for focal:
https://lists.ubuntu.com/archives/kernel-team/2020-November/thread.html#114528
changing status to 'In Progress' for focal.

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

** Changed in: linux (Ubuntu Focal)
 Assignee: Frank Heimes (fheimes) => (unassigned)

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

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  [20.04 FEAT] Support/enhancement of NVMe IPL

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  In Progress
Status in s390-tools source package in Focal:
  New
Status in linux source package in Groovy:
  In Progress
Status in s390-tools source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in s390-tools source package in Hirsute:
  Fix Released

Bug description:
  SRU Justification: (focal)
  ==

  [Impact]

  * The base for being able to IPL (boot) NVMe devices on s390x was
  introduced with kernel 5.8.

  * This got now requested (for hardware enablement reasons) for Ubuntu
  20.04 LTS as well.

  * On top a brand new commit got upstream accepted that introduces
  support for NVMe IPL kernel parameters, which is not yet in groovy.

  [Fix]

  * cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
  3737e8ee4f2f "s390: nvme ipl"

  * cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d 
"s390: nvme reipl"
does not apply cleanly, hence the following backport:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch

  * cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
  d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"

  [Test Case]

  * IBM z15 or LinuxONE III hardware is needed with an NVMe device
  attached to a LPAR.

  * Install the patched kernel on focal/20.04 installation and make sure
  that zipl re-ran (the patched version of zipl with the s390-tools
  commit mentioned in this LP bug - or take the s390-tools version for
  groovy for testing purposes).

  * If everything is in place (means patched kernel, as well as patched 
s390-tools/zipl) an installation from scratch on an NVMe devices should be 
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.

  [Regression Potential]

  * There is a certain regression risk with these patches, because:

  * the 'zipl' (s390x-specific) boot-loader is touched

  * if something is wrong there, in worst-case systems where the
  modified zipl ran may no longer be bootable!

  * The modifications are targetted towards nvme devices ('blkext'
  driver), but they are closely related to zFCP devices and share some
  code parts,

  * hence in worst case they could have an impact on zFCP devices, too.

  * But this is very unlikely, since a (largely) separate IPL type
  'nvme' got introduced and NVMe ipl is handled in separate case
  statements and functions.

  * The patches are all upstream accepted (the first two with 5.8, that
  last with v5.10-rc1, hence the latter one is as of today in linux-
  next).

  * A patched focal kernel was build and shared for further testing. I
  did some regression testing with the patched kernel on non-NVMe
  systems - the NVMe based tests need to be done by IBM (due to the lack
  of hardware).

  * All modifications are limited to the s390x architecture and there
  again to the unique way of booting aka IPL
  (arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
  arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).

  [Other]

  * The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
  "s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
  proven to work with groovy.

  * New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
  parameters".

  * The entire set of commits/patches is only new for focal.

  * The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
  groovy/20.10 was handled by a separate request.

  _

  
  SRU Justification: (groovy)
  ==

  [Impact]

  * The basics for being able to IPL (boot) from NVMe devices on s390x
  were introduced with kernel 5.8.

  * This was tested and is proven to work with groovy.

  * Now a patch was requested to be added to groovy that introduces
  support for NVMe IPL kernel parameters.

  [Fix]

  * d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
  support NVMe IPL kernel parameters"

  [Test Case]

  * IBM z15 or LinuxONE III hardwar

[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL

** Description changed:

+ SRU Justification: (focal)
+ ==
+
+ [Impact]
+
+ * The base for being able to IPL (boot) NVMe devices on s390x was
+ introduced with kernel 5.8.
+
+ * This got now requested (for hardware enablement reasons) for Ubuntu
+ 20.04 LTS as well.
+
+ * On top a brand new commit got upstream accepted that introduces
+ support for NVMe IPL kernel parameters, which is not yet in groovy.
+
+ [Fix]
+
+ * cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
+ 3737e8ee4f2f "s390: nvme ipl"
+
+ * cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
+ does not apply cleanly, hence the following backport:
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
+
+ * cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
+ d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
+
+ [Test Case]
+
+ * IBM z15 or LinuxONE III hardware is needed with an NVMe device
+ attached to a LPAR.
+
+ * Install the patched kernel on focal/20.04 installation and make sure
+ that zipl re-ran (the patched version of zipl with the s390-tools commit
+ mentioned in this LP bug - or take the s390-tools version for groovy for
+ testing purposes).
+
+ * If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
+ With the 20.04.2 image that should be the case.
+
+ [Regression Potential]
+
+ * There is a certain regression risk with these patches, because:
+
+ * the 'zipl' (s390x-specific) boot-loader is touched
+
+ * if something is wrong there, in worst-case systems where the modified
+ zipl ran may no longer be bootable!
+
+ * The modifications are targetted towards nvme devices ('blkext'
+ driver), but they are closely related to zFCP devices and share some
+ code parts,
+
+ * hence in worst case they could have an impact on zFCP devices, too.
+
+ * But this is very unlikely, since a (largely) separate IPL type 'nvme'
+ got introduced and NVMe ipl is handled in separate case statements and
+ functions.
+
+ * The patches are all upstream accepted (the first two with 5.8, that
+ last with v5.10-rc1, hence the latter one is as of today in linux-next).
+
+ * A patched focal kernel was build and shared for further testing. I did
+ some regression testing with the patched kernel on non-NVMe systems -
+ the NVMe based tests need to be done by IBM (due to the lack of
+ hardware).
+
+ * All modifications are limited to the s390x architecture and there
+ again to the unique way of booting aka IPL (arch/s390/include/asm/ipl.h,
+ arch/s390/include/uapi/asm/ipl.h, arch/s390/kernel/ipl.c and
+ arch/s390/boot/ipl_parm.c).
+
+ [Other]
+
+ * The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
+ "s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
+ proven to work with groovy.
+
+ * New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
+ parameters".
+
+ * The entire set of commits/patches is only new for focal.
+
+ * The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
+ groovy/20.10 was handled by a separate request.
+
+ _
+
+
SRU Justification: (groovy)
==

[Impact]

* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.

* This was tested and is proven to work with groovy.

* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.

[Fix]

* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"

[Test Case]

* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.

* Just check if NVMe kernel parameters can be passed over.

* Due to the lack of hardware this test needs to be done by IBM.

[Regression Potential]

* There is a certain regression risk with this patch, since:

* The handling of 'scpdata' is changed, and with that the way how kernel
cmd-line parameters are extracted from the NVMe IPL block, that is
passed by the firmware to the kernel at boot time.

* If broken such a hand over will not work for NVMe anymore - which
wouldn't be a very big problem for now, since booting w/o still works
fine (as it does today).

* But in worst case it could break the hand over of cmd-line parameters
for FCP devices, since some code is shared or even harm ipl in general.

* The patch is upstream accepted (with v5.10-rc1 - as of today in linux-
next) and a patched groovy kernel was build and shared for further
testing.

* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL (s390/boot/ipl*).

[Othe

[Kernel-packages] [Bug 1899993] Re: EFI: Fails when BootCurrent entry does not exist

2020-11-03 Thread dann frazier

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

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

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

** Also affects: curtin (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: Triaged

** Also affects: curtin (Ubuntu Hirsute)
   Importance: Medium
   Status: Invalid

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

** Also affects: curtin (Ubuntu Focal)
   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/183

Title:
  EFI: Fails when BootCurrent entry does not exist

Status in curtin package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Triaged
Status in curtin source package in Xenial:
  New
Status in linux source package in Xenial:
  New
Status in curtin source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in curtin source package in Focal:
  New
Status in linux source package in Focal:
  New
Status in curtin source package in Groovy:
  New
Status in linux source package in Groovy:
  New
Status in curtin source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Triaged

Bug description:
  Split out of bug 1894217.

  We're seeing a situation where curtin fails when the variable
  BootCurrent references does not exist.

  At boot, efibootmgr -v shows:

  BootCurrent: 0003
  Timeout: 10 seconds
  BootOrder: 0003,0004,0005,0006,0001

  Note that there are actually no individual boot entries in this
  output. BootCurrent and BootOrder are referencing Boot entries that do
  not apepar to exist.

  Later, curtin tries to set a new BootOrder that places the value of
  BootCurrent at the front. This causes efibootmgr to error out,
  apparently escalating to an installation failure:

  UEFI efibootmgr output after install:
  {'current': '0003', 'timeout': '10 seconds', 'order': [''], 
'entries': {'': {'name
  ': 'ubuntu', 'path': 
'HD(1,GPT,0937ffdf-628c-4161-8b2f-5920235669c6,0x800,0x10)/File(\\EFI\\ub
  untu\\shimx64.efi)'}}}
  Setting currently booted 0003 as the first UEFI loader.
  New UEFI boot order: 0003,
  Running command ['mount', '--bind', '/dev', 
'/tmp/tmp6ha4_iz2/target/dev'] with allowed re
  turn codes [0] (capture=False)
  Running command ['mount', '--bind', '/proc', 
'/tmp/tmp6ha4_iz2/target/proc'] with allowed 
  return codes [0] (capture=False)
  Running command ['mount', '--bind', '/run', 
'/tmp/tmp6ha4_iz2/target/run'] with allowed re
  turn codes [0] (capture=False)
  Running command ['mount', '--bind', '/sys', 
'/tmp/tmp6ha4_iz2/target/sys'] with allowed re
  turn codes [0] (capture=False)
  Running command ['mount', '--bind', '/sys/firmware/efi/efivars', 
'/tmp/tmp6ha4_iz2/target/
  sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
  Running command ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp6ha4_iz2/target', 
  'efibootmgr', '-o', '0003,'] with allowed return codes [0] (capture=False)
  Invalid BootOrder order entry value0003
   ^
  efibootmgr: entry 0003 does not exist

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

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

[Kernel-packages] [Bug 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems

2020-11-03 Thread Patricia Domingues

Hi Waiki, thanks for raising this bug.
Please, could you share a test scenario for the verification of these patches -
how it can be tested? This is needed for every kernel SRU. Thanks in advance.

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

Title:
Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX
for reductions on POWER9 DD2.1 systems

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

Bug description:
== Comment: #0 - Waiki Wright - 2020-11-02 17:00:07
==

---Problem Description---

A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52
and 20.10 - 5.8.0-26 kernel on Power 9. The root cause is found in
the compiling of p9_hmi_special_emu(). When doing a VMX store (in
__get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
128 bit aligned.

The fixes of this bug are accepted upstream:
1.

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load
emulation")
2.

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
workaround")

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

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

[Kernel-packages] [Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved

2020-11-03 Thread Ian Johnson

** Changed in: snapd
   Status: New => Confirmed

** Changed in: snapd
   Importance: Undecided => Medium

** Changed in: snapd
 Assignee: (unassigned) => Ian Johnson (anonymouse67)

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

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

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

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

2020-11-03 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 1902748

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

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

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

[Kernel-packages] [Bug 1902748] [NEW] ubuntu-seed / ubuntu-boot partition detection could be improved

2020-11-03 Thread Dimitri John Ledkov

Public bug reported:

ubuntu-seed / ubuntu-boot partition detection could be improved

Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
ubuntu-seed partition by label or by UEFI variable that was set by sd-
boot.

sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
boot.

https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

This is nice, but not unique enough. It would be nice if we were able to
modify sd-boot stub to export something more specific that ideally maps
to a sysfs path.

For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

That way initrd would be able to resolve better which block device to
key off.

Given that EFI device handle is passed to the kernel, doesn't kernel
also know where it came from? or not?

** Affects: snapd
 Importance: Undecided
 Status: New

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

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

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

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

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  New
Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

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

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

Re: [Kernel-packages] [Bug 1901282] Re: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

2020-11-03 Thread Philippe Bureau

No, i don't think so

Le 24/10/2020 à 12:03, Jouni Mettala a écrit :
> There is external module version mismatch in DpkgTerminalLog.txt:
>
> make -j12 KERNELRELEASE=5.8.0-25-generic -j12 TTM_NAME=amdttm 
> SCHED_NAME=amd-sched kdir=/lib/modules/5.8.0-25-generic/build -C 
> /lib/modules/5.8.0-25-generic/build 
> M=/var/lib/dkms/amdgpu/5.6.0.15-1098277/build(bad exit status: 2)
> Error! Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)
> Consult /var/lib/dkms/amdgpu/5.6.0.15-1098277/build/make.log for more 
> information.
>
> Have you installed some additional drivers?
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => 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/1901282

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: bloqué en boucle sur le traitement des actions
  différées (« triggers »), abandon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After 20.10 update

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lilipfem   2047 F pulseaudio
   /dev/snd/controlC1:  lilipfem   2047 F pulseaudio
   /dev/snd/controlC0:  lilipfem   2047 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Oct 24 07:42:50 2020
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  InstallationDate: Installed on 2020-09-19 (34 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=d00e80d3-285e-4cda-bc15-ac896b699919 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
  dmi.bios.date: 07/14/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

2020-11-03 Thread Kai-Heng Feng

campus, does it work but flaky? Then it sounds like a different bug.

Can you please attach dmesg under v5.10?

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

Title:
  RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal
  Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  Device is unable to scan for networks and error occurs whe

[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

2020-11-03 Thread campus

Unfortunately, kernel 5.10 rc1 doesn't fix the bug for me (Lenovo Y530-15ICH 
with bios version 8JCN54WW released 06/15/2020). After several reboots the 
network keeps disconnecting,
However the solution presented by Pablo "options rtw88_pci disable_aspm=1" 
works with the ubuntu stock kernel (currently 5.8.0-26)

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

Title:
  RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal
  Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R

[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series

2020-11-03 Thread Alberto Milone

** Description changed:

  [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]
  
  [Changelog]
  
-   * New upstream release:
- - Added support for the following GPUs:
- GeForce RTX 3070
- - Added support for using an NVIDIA-driven display as a PRIME
-   Display Offload sink with a PRIME Display Offload source driven
-   by the xf86-video-intel driver.
- - Fixed a bug in a Vulkan barrier optimization that allowed some
-   back-to-back copies to run unordered.
- - Fixed a performance regression in the NVIDIA X driver which
-   affected some X11 RENDER extension use cases.
- - Added AMD Secure Memory Encryption compatibility.
-   * debian/templates/control.in:
- - Set support level to NFB instead of Beta.
- - Add support for CUDA 11.
+   * New upstream release:
+ - Added support for the following GPUs:
+ GeForce RTX 3070
+ - Added support for using an NVIDIA-driven display as a PRIME
+   Display Offload sink with a PRIME Display Offload source driven
+   by the xf86-video-intel driver.
+ - Fixed a bug in a Vulkan barrier optimization that allowed some
+   back-to-back copies to run unordered.
+ - Fixed a performance regression in the NVIDIA X driver which
+   affected some X11 RENDER extension use cases.
+ - Added AMD Secure Memory Encryption compatibility.
+   * debian/templates/control.in:
+ - Set support level to NFB instead of Beta.
+ - Add support for CUDA 11.
  
  Note: this will be the initial release for Bionic and Focal.
+ 
+ 
+ Changelog entries for the linux-restricted-modules:
+ 
+ UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual
+ package
+ 
+ Make all the NVIDIA drivers, except for 390, provide the 
nvidia-prebuilt-kernel
+ virtual package.
+ 
+ This allows adding a generic dependency on the signed modules.

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

Title:
  Introduce the new NVIDIA 455 series

Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  In Progress
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-455 source package in Bionic:
  In Progress
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-455 source package in Focal:
  In Progress
Status in linux-restricted-modules source package in Groovy:
  New
Status in nvidia-graphics-drivers-455 source package in Groovy:
  In Progress

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]

  [Changelog]

    * New upstream release:
  - Added support for the following GPUs:
  GeForce RTX 3070
  - Added support for using an NVIDIA-driven display as a PRIME
    Display Offload sink with a PRIME Display Offload source driven
    by the xf86-video-intel driver.
  - Fixed a bug in a Vulkan barrier optimization that allowed some
    back-to-back copies to run unordered.
  - Fixed a performance regression in the NVIDIA X driver which
    affected some X11 RENDER extension use cases.
  - Added AMD Secure Memory Encryption compatibility.
    *

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2020-11-03 Thread Kai Mast

Georgi, if you can afford it I would switch from the TB16 to the WD19TB.
The latter works much better from my experience and what I read online.

I have a new issue now with the WD19TB though where GNOME constantly
reconfigures the Thunderbolt device (the Thunderbolt icon in the top
right notification area frequently appears). It usually does not cause
any issues, but it seems like something is happening that should not
happen.

I wonder if there are at least two different bugs here...

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

Title:
  USB over thunderbolt turns off every once in a while

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9
  [279283.191730] usb 3-1.1.3: USB disconnect, device number 6
  [279283.260810] usb 3-1.1.5: USB disconnect, device number 7
  [279283.261350] usb 3-1.5: USB disconnect, device number 4

  Here's dmesg output during the USB host controller reset:

  279389.813889] xhci_hcd :0e:00.0: remove, state 1 

  
  [279389.813894] usb usb4: USB disconnect, device number 1 

   
  [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered 

   
  [279389.814107] xhci_hcd :0e:00.0: remove, state 1

   
  [279389.814110] usb usb3: USB disconnect, device number 1 

   
  [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered 

   
  [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller   

   
  [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus 
number 3
 
  [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 
0x100 quirks 0x1410 

  [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 

   
  [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1  
 
  [279389.949982] usb usb3: Product: xHCI Host Controller

[Kernel-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

2020-11-03 Thread Sebastien Bacher

Is there any work needed on bluez or linux there?

** Tags removed: rls-gg-incoming

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

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

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

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

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Incomplete
Status in linux-raspi package in Ubuntu:
  Incomplete
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  Incomplete
Status in linux-raspi source package in Groovy:
  Incomplete
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Kernel-packages] [Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions

2020-11-03 Thread Eric Mazoob

I'm on 20.10 using KDE, 5.8.0-26-generic, on a dell xps 13 2-in-1 and
the problem is rather severe.

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

Title:
  [i915] Noise-like lines of graphics corruption when moving windows in
  Xorg sessions

Status in Mutter:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
  unattended for a while, and then got the error message and now have
  funny lines on activity, e.g. red lines flashing on top of gnome-shell
  bar when switching windows, or white blocks/lines around typing text.

  This is the second or third time it happened, reboot fixes it until
  the error pops up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 19:14:11 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):b

[Kernel-packages] [Bug 1902701] [NEW] zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/z/zfs-linux/20201016_104632_e52aa@/log.gz
arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/z/zfs-linux/20201016_144759_7735c@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/z/zfs-linux/20201016_111820_ceeb8@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/z/zfs-linux/20201016_082202_1adb7@/log.gz

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

** Affects: zfs-linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

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

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

** Changed in: zfs-linux (Ubuntu Focal)
 Assignee: (unassigned) => Stefan Bader (smb)

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

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

Title:
  zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8
  5.8.0-25.26~20.04.1

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Focal:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/z/zfs-linux/20201016_104632_e52aa@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/z/zfs-linux/20201016_144759_7735c@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/z/zfs-linux/20201016_111820_ceeb8@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/z/zfs-linux/20201016_082202_1adb7@/log.gz

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

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

[Kernel-packages] [Bug 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems

Even if this was submitted as medium, I bump it to high.

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

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

Title:
  Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX
  for reductions on POWER9 DD2.1 systems

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

Bug description:
  == Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
  ==

  ---Problem Description---

  A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52
  and 20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in
  the compiling of  p9_hmi_special_emu().  When doing a VMX store (in
  __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
  128 bit aligned.

  The fixes of this bug are accepted upstream:
  1.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
  ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load 
emulation")
  2.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
  ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")

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

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

[Kernel-packages] [Bug 1902694] [NEW] Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems

Public bug reported:

== Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
==

---Problem Description---

A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52 and
20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in the
compiling of  p9_hmi_special_emu().  When doing a VMX store (in
__get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
128 bit aligned.

The fixes of this bug are accepted upstream:
1.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation")
2.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")

** Affects: ubuntu-power-systems
 Importance: High
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-189000 severity-medium 
targetmilestone-inin2010

** Tags added: architecture-ppc64le bugnameltc-189000 severity-medium
targetmilestone-inin2010

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** 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/1902694

Title:
  Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX
  for reductions on POWER9 DD2.1 systems

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

Bug description:
  == Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
  ==

  ---Problem Description---

  A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52
  and 20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in
  the compiling of  p9_hmi_special_emu().  When doing a VMX store (in
  __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
  128 bit aligned.

  The fixes of this bug are accepted upstream:
  1.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
  ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load 
emulation")
  2.
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
  ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")

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

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

[Kernel-packages] [Bug 1902694] [NEW] Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems

You have been subscribed to a public bug:

== Comment: #0 - Waiki Wright  - 2020-11-02 17:00:07
==

---Problem Description---

A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52 and
20.10 - 5.8.0-26 kernel on Power 9.  The root cause is found in the
compiling of  p9_hmi_special_emu().  When doing a VMX store (in
__get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
128 bit aligned.

The fixes of this bug are accepted upstream:
1.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation")
2.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load 
workaround")

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-189000 severity-medium 
targetmilestone-inin2010
-- 
Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for 
reductions on POWER9 DD2.1 systems
https://bugs.launchpad.net/bugs/1902694
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 1902531] Re: [linux-azure] IP forwarding issue in netvsc

2020-11-03 Thread Marcelo Cerri

The 5.0 linux-azure kernel is not maintained anymore. Do you have any
scenario that is still using this kernel?

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

Title:
  [linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We identified an issue with the Linux netvsc driver when used in IP
  forwarding mode.  The problem is that the RSS hash value is not
  propagated to the outgoing packet, and so such packets go out on
  channel 0.  This produces an imbalance across outgoing channels, and a
  possible overload on the single host-side CPU that is processing
  channel 0.   The problem does not occur when Accelerated Networking is
  used because the packets go out through the Mellanox driver.  Because
  it is tied to IP forwarding, the problem is presumably most likely to
  be visible in a virtual appliance device that is doing network load
  balancing or other kinds of packet filtering and redirection.

  We would like to request fixes to this issue in 16.04, 18.04 and
  20.04.

  Two fixes are already in the upstream v5.5+, so they’re already in
  5.8.0-1011.11.

  For 5.4.0-1031.32, the 2 fixes can apply cleanly:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan 
backported them here:
  https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795
  https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a
  (The 2 patches are on the branch 
https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1)

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

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

[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc

2020-11-03 Thread Marcelo Cerri

Thanks for reporting the issue and for providing the back ported fixes.

Do you have any instructions that we can use to reproduce and test the
problem?

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

Title:
  [linux-azure] IP forwarding issue in netvsc

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We identified an issue with the Linux netvsc driver when used in IP
  forwarding mode.  The problem is that the RSS hash value is not
  propagated to the outgoing packet, and so such packets go out on
  channel 0.  This produces an imbalance across outgoing channels, and a
  possible overload on the single host-side CPU that is processing
  channel 0.   The problem does not occur when Accelerated Networking is
  used because the packets go out through the Mellanox driver.  Because
  it is tied to IP forwarding, the problem is presumably most likely to
  be visible in a virtual appliance device that is doing network load
  balancing or other kinds of packet filtering and redirection.

  We would like to request fixes to this issue in 16.04, 18.04 and
  20.04.

  Two fixes are already in the upstream v5.5+, so they’re already in
  5.8.0-1011.11.

  For 5.4.0-1031.32, the 2 fixes can apply cleanly:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 5.0.0-1036.38, we need 1 more patch applied first, so the list is:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e

  For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan 
backported them here:
  https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795
  https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a
  (The 2 patches are on the branch 
https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1)

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

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

[Kernel-packages] [Bug 1823859] Re: NULL pointer dereference in split_swap_cluster

2020-11-03 Thread Marcelo Cerri

Thanks for reporting this bug, Hóka.

The commit posted by Jacob mentions that the bug happens when HDD is
used as a swap device. Do you have something like that in your
environment? Also if you have a reproduce that can trigger the problem
let me know.

Thank you.

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

Title:
  NULL pointer dereference in split_swap_cluster

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We have encountered the following oops on one of our VMs:

  Apr  7 14:02:19 rancher1 kernel: [2089793.273674] BUG: unable to handle 
kernel NULL pointer dereference at 0007
  Apr  7 14:02:19 rancher1 kernel: [2089793.282782] IP: 
split_swap_cluster+0x4f/0x70
  Apr  7 14:02:19 rancher1 kernel: [2089793.330631] PGD 0 P4D 0
  Apr  7 14:02:19 rancher1 kernel: [2089793.338279] Oops: 0002 [#1] SMP PTI
  Apr  7 14:02:19 rancher1 kernel: [2089793.350774] Modules linked in: ufs 
msdos xfs cmac arc4 md4 nls_utf8 cifs ccm fscache xt_tcpudp xt_set 
ip_set_hash_net ip_set iptable_raw vxlan ip6_udp_tunnel udp_tunnel xt_nat 
xt_mark xfrm6_mode_tunnel xfrm4_mode_tunnel esp4 ansi_cprng veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter nf_nat br_netfilter bridge 
stp llc nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack 
iptable_security ip_tables x_tables aufs overlay mlx4_en pci_hyperv hv_balloon 
serio_raw joydev ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul
  Apr  7 14:02:19 rancher1 kernel: [2089793.618910]  crc32_pclmul 
ghash_clmulni_intel pcbc hid_generic aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd hid_hyperv pata_acpi hyperv_fb cfbfillrect hyperv_keyboard 
cfbimgblt hid cfbcopyarea hv_netvsc hv_utils
  Apr  7 14:02:19 rancher1 kernel: [2089793.692250] CPU: 0 PID: 47 Comm: 
kswapd0 Not tainted 4.15.0-1040-azure #44-Ubuntu
  Apr  7 14:02:19 rancher1 kernel: [2089793.725316] Hardware name: Microsoft 
Corporation Virtual Machine/Virtual Machine, BIOS 090007  06/02/2017
  Apr  7 14:02:19 rancher1 kernel: [2089793.762206] RIP: 
0010:split_swap_cluster+0x4f/0x70
  Apr  7 14:02:19 rancher1 kernel: [2089793.781768] RSP: 0018:aaf900fbfbe0 
EFLAGS: 00010246
  Apr  7 14:02:19 rancher1 kernel: [2089793.800432] RAX:  RBX: 
007290de RCX: 007290de
  Apr  7 14:02:19 rancher1 kernel: [2089793.824572] RDX: aaf905001000 RSI: 
00118df9 RDI: 007290de
  Apr  7 14:02:19 rancher1 kernel: [2089793.854139] RBP: aaf900fbfbe8 R08: 
0001 R09: 9c647ffd4d00
  Apr  7 14:02:19 rancher1 kernel: [2089793.882588] R10: 9c647ffd4000 R11: 
0001 R12: f61ac463
  Apr  7 14:02:19 rancher1 kernel: [2089793.909530] R13: f61ac4630080 R14: 
f61ac4638000 R15: f61ac4630040
  Apr  7 14:02:19 rancher1 kernel: [2089793.935871] FS:  () 
GS:9c647fc0() knlGS:
  Apr  7 14:02:19 rancher1 kernel: [2089793.966483] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr  7 14:02:19 rancher1 kernel: [2089793.987904] CR2: 0007 CR3: 
3240a005 CR4: 001606f0
  Apr  7 14:02:19 rancher1 kernel: [2089794.017641] Call Trace:
  Apr  7 14:02:19 rancher1 kernel: [2089794.028683]  
split_huge_page_to_list+0x76e/0x7f0
  Apr  7 14:02:19 rancher1 kernel: [2089794.051250]  
deferred_split_scan+0x177/0x2d0
  Apr  7 14:02:19 rancher1 kernel: [2089794.065213]  
shrink_slab.part.50+0x20b/0x440
  Apr  7 14:02:19 rancher1 kernel: [2089794.083856]  shrink_node+0x2fc/0x310
  Apr  7 14:02:19 rancher1 kernel: [2089794.097963]  kswapd+0x32a/0x770
  Apr  7 14:02:19 rancher1 kernel: [2089794.110523]  kthread+0x105/0x140
  Apr  7 14:02:19 rancher1 kernel: [2089794.122680]  ? 
mem_cgroup_shrink_node+0x190/0x190
  Apr  7 14:02:19 rancher1 kernel: [2089794.139139]  ? 
kthread_destroy_worker+0x50/0x50
  Apr  7 14:02:19 rancher1 kernel: [2089794.155543]  ret_from_fork+0x35/0x40
  Apr  7 14:02:19 rancher1 kernel: [2089794.167841] Code: c1 e3 07 48 c1 eb 10 
48 8d 1c d8 48 89 df e8 49 9f 79 00 80 63 07 fb 48 85 db 74 17 48 89 df c6 07 
00 0f 1f 40 00 31 c0 5b 5d c3 <80> 24 25 07 00 00 00 fb 31 c0 5b 5d c3 b8 f0 ff 
ff ff eb e9 0f
  Apr  7 14:02:19 rancher1 kernel: [2089794.237196] RIP: 
split_swap_cluster+0x4f/0x70 RSP: aaf900fbfbe0
  Apr  7 14:02:19 rancher1 kernel: [2089794.259910] CR2: 0007
  Apr  7 14:02:19 rancher1 kernel: [2089794.270891] ---[ end trace 
5b797d89aee7fc1b ]---

  The machine become unstable after this until reboot, like reading some
  namespaced process' command arguments hung, so it is possible that
  there was some

[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL

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

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

Title:
  [20.04 FEAT] Support/enhancement of NVMe IPL

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  New
Status in s390-tools source package in Focal:
  New
Status in linux source package in Groovy:
  In Progress
Status in s390-tools source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in s390-tools source package in Hirsute:
  Fix Released

Bug description:
  SRU Justification: (groovy)
  ==

  [Impact]

  * The basics for being able to IPL (boot) from NVMe devices on s390x
  were introduced with kernel 5.8.

  * This was tested and is proven to work with groovy.

  * Now a patch was requested to be added to groovy that introduces
  support for NVMe IPL kernel parameters.

  [Fix]

  * d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
  support NVMe IPL kernel parameters"

  [Test Case]

  * IBM z15 or LinuxONE III hardware is needed with an NVMe device
  attached to a LPAR.

  * Just check if NVMe kernel parameters can be passed over.

  * Due to the lack of hardware this test needs to be done by IBM.

  [Regression Potential]

  * There is a certain regression risk with this patch, since:

  * The handling of 'scpdata' is changed, and with that the way how
  kernel cmd-line parameters are extracted from the NVMe IPL block, that
  is passed by the firmware to the kernel at boot time.

  * If broken such a hand over will not work for NVMe anymore - which
  wouldn't be a very big problem for now, since booting w/o still works
  fine (as it does today).

  * But in worst case it could break the hand over of cmd-line
  parameters for FCP devices, since some code is shared or even harm ipl
  in general.

  * The patch is upstream accepted (with v5.10-rc1 - as of today in
  linux-next) and a patched groovy kernel was build and shared for
  further testing.

  * All modifications are limited to the s390x architecture and there
  again to the unique way of booting aka IPL (s390/boot/ipl*).

  [Other]

  * This is in preparation for getting IPL (boot) from NVMe device
  support on s390x backported to focal (for hardware enablement
  reasons).

  * Without having this patch in groovy, one may face a regression
  during upgrade from groovy to focal.

  * Since it's planned to have the hirsute kernel on 5.1x, it will have
  this patch sooner or later.

  * However, since the today's hirsute kernel is just based on groovy,
  I've added hirsute to the SRU.

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

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

[Kernel-packages] [Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead

2020-11-03 Thread Mike Harris

Follow post of a work around that automatically enables the resolution I
want.

I added a file named: 45custom_xrandr_settings
in folder: /etc/X11/Xsession.d

containing:
xrandr --newmode "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync 
-vsync
xrandr --addmode HDMI-1-1 "Mode 0"

This will cause X11 to use the 2560x1440 resolution after reboot.

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

Title:
  [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440
  not listed, defaults to 1920x1080 instead

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The PG278QR monitor supports 2560x1440.  After installing Ubuntu 20.4,
  the max resolution presented in the Settings app is 1920x1080, and
  this resolution is the one that it uses.  Switching between the Nvidia
  driver or the Intel driver (laptop has low-power intel gpu too)
  doesn't correct the problem.

  Digging in deeper, based on
  
https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs

  Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to
  use get-edid | parse-edid.

  After applying the mode that I wanted manually via xrandr --newmode
  and xrandr --addmode, I was able to select the max resolution of the
  monitor and works correctly, until reboot.  I will add it to my
  xorg.conf next.

  Here is information I collected:

  output from xrandr after fresh boot:

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
 1920x1080 60.01*+  60.0159.9759.9659.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  59.9959.9459.9559.82  
 1280x1024 60.02  
 1440x900  59.89  
 1400x900  59.9659.88  
 1280x960  60.00  
 1440x810  60.0059.97  
 1368x768  59.8859.85  
 1360x768  59.8059.96  
 1280x800  59.9959.9759.8159.91  
 1152x864  60.00  
 1280x720  60.0059.9959.8659.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y 
axis) 598mm x 336mm
 1920x1080 60.00*   50.0059.94  
 1280x720  60.0050.0059.94  
 1024x768  60.00  
 800x600   60.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   60.0059.94  
  DP-1-1 disconnected (normal left inverted right x axis y axis)

  output from get-edid | parse-edid:
  ~$ sudo get-edid | parse-edid
  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  No EDID on bus 1
  No EDID on bus 2
  No EDID on bus 3
  No EDID on bus 5
  No EDID on bus 6
  No EDID on bus 7
  No EDID on bus 9
  No EDID on bus 10
  3 potential busses found: 0 4 8
  Will scan through until the first EDID is found.
  Pass a bus number as an option to this program to go only for that one.
  Bus 0 doesn't really have an EDID...
  256-byte EDID successfully retrieved from i2c bus 4
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "ROG PG278QR"
ModelName "ROG PG278QR"
VendorName "AUS"
# Monitor Manufactured week 47 of 2016
# EDID version 1.3
# Digital Display
DisplaySize 600 340
Gamma 2.20
Option "DPMS" "false"
Horizsync 30-140
VertRefresh 24-60
# Maximum pixel clock is 300MHz

#Extension block found. Parsing...
Modeline"Mode 1" 148.500 1920 2008 2052 2200 108

[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL

** Changed in: linux (Ubuntu Hirsute)
   Status: Fix Released => In Progress

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

Title:
  [20.04 FEAT] Support/enhancement of NVMe IPL

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  New
Status in s390-tools source package in Focal:
  New
Status in linux source package in Groovy:
  In Progress
Status in s390-tools source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in s390-tools source package in Hirsute:
  Fix Released

Bug description:
  SRU Justification: (groovy)
  ==

  [Impact]

  * The basics for being able to IPL (boot) from NVMe devices on s390x
  were introduced with kernel 5.8.

  * This was tested and is proven to work with groovy.

  * Now a patch was requested to be added to groovy that introduces
  support for NVMe IPL kernel parameters.

  [Fix]

  * d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
  support NVMe IPL kernel parameters"

  [Test Case]

  * IBM z15 or LinuxONE III hardware is needed with an NVMe device
  attached to a LPAR.

  * Just check if NVMe kernel parameters can be passed over.

  * Due to the lack of hardware this test needs to be done by IBM.

  [Regression Potential]

  * There is a certain regression risk with this patch, since:

  * The handling of 'scpdata' is changed, and with that the way how
  kernel cmd-line parameters are extracted from the NVMe IPL block, that
  is passed by the firmware to the kernel at boot time.

  * If broken such a hand over will not work for NVMe anymore - which
  wouldn't be a very big problem for now, since booting w/o still works
  fine (as it does today).

  * But in worst case it could break the hand over of cmd-line
  parameters for FCP devices, since some code is shared or even harm ipl
  in general.

  * The patch is upstream accepted (with v5.10-rc1 - as of today in
  linux-next) and a patched groovy kernel was build and shared for
  further testing.

  * All modifications are limited to the s390x architecture and there
  again to the unique way of booting aka IPL (s390/boot/ipl*).

  [Other]

  * This is in preparation for getting IPL (boot) from NVMe device
  support on s390x backported to focal (for hardware enablement
  reasons).

  * Without having this patch in groovy, one may face a regression
  during upgrade from groovy to focal.

  * Since it's planned to have the hirsute kernel on 5.1x, it will have
  this patch sooner or later.

  * However, since the today's hirsute kernel is just based on groovy,
  I've added hirsute to the SRU.

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

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

[Kernel-packages] [Bug 1901505] Re: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0)

2020-11-03 Thread Goro

As I said in previous post i'm not sure that this is the same problem as
with me, but look very similar because of the Haswell Processor and I'm
unable to get a working Desktop environment.

Same computer works just fine with Ubuntu 20.04, which have older
kernel.

My experience with Ubuntu 20.10 live is that it cannot boot every time and its 
locks up, but it boots fine in safe gfx mode.
In safe gfx mode I installed it on clean disk, and when try boot it - sometimes 
just log into gnome shell and it locks up.
Error in dmesg is i915 GPU hang.
In wayland it works better so I can click on menus but sometimes it freeze for 
few seconds and continue( GPU reset) and when you run program that use xwayland 
it got a total lock up.
I installed cinnamon desktop and it locks immediately after login, Cinnamon 
with software rendering works just fine. I tried Xubuntu it hang as well. With 
"nomodeset" kernel parameter it works fine but only in 1024x768, tested it with 
Ubuntu, Cinnamon and Xubuntu.

So I search for solution and find this thread over FDO, with a lot of
people with Haswell GT1 video having the same problem since kernel 5.6 I
think.

https://gitlab.freedesktop.org/drm/intel/-/issues/2024

Other peoples with same problem, also there are several threads over
Arch linux forums

https://bugzilla.redhat.com/show_bug.cgi?id=1843274
https://bugzilla.redhat.com/show_bug.cgi?id=1886438

My Processor is Intel Pentium G3258 AE and is Desktop CPU.
Other components I think doesn't really matter in this case.

and my errors from DMESG

[   31.037041] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in 
gnome-shell [1441]
[   31.037044] GPU hangs can indicate a bug anywhere in the entire gfx stack, 
including userspace.
[   31.037045] Please file a _new_ bug report at 
https://gitlab.freedesktop.org/drm/intel/issues/new.
[   31.037047] Please see 
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for 
details.
[   31.037048] drm/i915 developers can then reassign to the right component if 
it's not a kernel issue.
[   31.037049] The GPU crash dump is required to analyze GPU hangs, so please 
always attach it.
[   31.037050] GPU crash dump saved to /sys/class/drm/card0/error
[   31.037859] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on 
rcs0
[   31.140859] i915 :00:02.0: [drm] gnome-shell[1441] context reset due to 
GPU hang
[   34.080734] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in Xorg 
[1290]
[   34.080924] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on 
rcs0
[   34.183350] i915 :00:02.0: [drm] Xorg[1290] context reset due to GPU hang
[   39.819821] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in 
gnome-shell [1441]
[   39.821530] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on 
rcs0
[   39.924378] i915 :00:02.0: [drm] gnome-shell[1441] context reset due to 
GPU hang
[   45.912749] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in 
gnome-shell [1441]
[   45.912822] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on 
rcs0
[   46.014840] i915 :00:02.0: [drm] gnome-shell[1441] context reset due to 
GPU hang

I can attach crash dump ass well.

** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #2024
   https://gitlab.freedesktop.org/drm/intel/-/issues/2024

** Bug watch added: Red Hat Bugzilla #1843274
   https://bugzilla.redhat.com/show_bug.cgi?id=1843274

** Bug watch added: Red Hat Bugzilla #1886438
   https://bugzilla.redhat.com/show_bug.cgi?id=1886438

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

Title:
  upgrade to 20.10 broke haswell laptop (no regular boot, no
  /dev/dri/card0)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop installed with kubuntu focal is not booting after upgrade to
  20.10 (that apparently went smooth without any error).

  - laptop hangs on boot
  - no splash screen is displayed
  - laptop can boot in recovery mode
  - in this case you do not get /dev/dri/card0 - if X is started it starts on 
llvmpipe
  - i915 driver is loaded, no error about it in journal or dmesg

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

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

[Kernel-packages] [Bug 1892816] Re: memory-hotplug test from ubuntu_kernel_selftests failed on X-4.15 / B-4.15 / F-5.4 ARM64 (execution permission issue)

2020-11-03 Thread Po-Hsu Lin

** Summary changed:

- [Potential Regression] memory-hotplug test from ubuntu_kernel_selftests 
failed on X-4.15 / B-4.15 / F-5.4 ARM64
+ memory-hotplug test from ubuntu_kernel_selftests failed on X-4.15 / B-4.15 / 
F-5.4 ARM64 (execution permission issue)

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

Title:
  memory-hotplug test from ubuntu_kernel_selftests failed on X-4.15 /
  B-4.15 / F-5.4 ARM64 (execution permission issue)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on 4.15.0-114.115~16.04.1, test failed with:

./mem-on-off-test.sh -r 2 && echo "selftests: memory-hotplug [PASS]" || 
echo "selftests: memory-hotplug [FAIL]"
/bin/sh: 1: ./mem-on-off-test.sh: Permission denied
selftests: memory-hotplug [FAIL]

  Note that this test was marked as passed (test skipped) with
  4.15.0-112.113~16.04.1 on both ThunderX and Moonshot node:

  skip all tests: memory hotplug is not supported
  selftests: memory-hotplug [PASS]

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

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

[Kernel-packages] [Bug 1901505] Re: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0)

2020-11-03 Thread Goro

I have similar or same problem and I have haswell too... I will explain
my problem at large in next post but first try these things.

First when boot and it hangs, try go switch to different VT - ctrl+alt +
F3 or F4 then enter

sudo dmesg

at the bottom you will ikely find this...

i915 :00:02.0: [drm] GPU HANG

Then try another one  - boot kernel with  "nomodeset" parameter (without
quotes)  - for me it produce a working system but only with 1024x768
resolution

And third one  - can you specify what Haswell processor you have?

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

Title:
  upgrade to 20.10 broke haswell laptop (no regular boot, no
  /dev/dri/card0)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop installed with kubuntu focal is not booting after upgrade to
  20.10 (that apparently went smooth without any error).

  - laptop hangs on boot
  - no splash screen is displayed
  - laptop can boot in recovery mode
  - in this case you do not get /dev/dri/card0 - if X is started it starts on 
llvmpipe
  - i915 driver is loaded, no error about it in journal or dmesg

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

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

[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL

** Information type changed from Private to Public

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

Title:
  [20.04 FEAT] Support/enhancement of NVMe IPL

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  New
Status in s390-tools source package in Focal:
  New
Status in linux source package in Groovy:
  In Progress
Status in s390-tools source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in s390-tools source package in Hirsute:
  Fix Released

Bug description:
  SRU Justification: (groovy)
  ==

  [Impact]

  * The basics for being able to IPL (boot) from NVMe devices on s390x
  were introduced with kernel 5.8.

  * This was tested and is proven to work with groovy.

  * Now a patch was requested to be added to groovy that introduces
  support for NVMe IPL kernel parameters.

  [Fix]

  * d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
  support NVMe IPL kernel parameters"

  [Test Case]

  * IBM z15 or LinuxONE III hardware is needed with an NVMe device
  attached to a LPAR.

  * Just check if NVMe kernel parameters can be passed over.

  * Due to the lack of hardware this test needs to be done by IBM.

  [Regression Potential]

  * There is a certain regression risk with this patch, since:

  * The handling of 'scpdata' is changed, and with that the way how
  kernel cmd-line parameters are extracted from the NVMe IPL block, that
  is passed by the firmware to the kernel at boot time.

  * If broken such a hand over will not work for NVMe anymore - which
  wouldn't be a very big problem for now, since booting w/o still works
  fine (as it does today).

  * But in worst case it could break the hand over of cmd-line
  parameters for FCP devices, since some code is shared or even harm ipl
  in general.

  * The patch is upstream accepted (with v5.10-rc1 - as of today in
  linux-next) and a patched groovy kernel was build and shared for
  further testing.

  * All modifications are limited to the s390x architecture and there
  again to the unique way of booting aka IPL (s390/boot/ipl*).

  [Other]

  * This is in preparation for getting IPL (boot) from NVMe device
  support on s390x backported to focal (for hardware enablement
  reasons).

  * Without having this patch in groovy, one may face a regression
  during upgrade from groovy to focal.

  * Since it's planned to have the hirsute kernel on 5.1x, it will have
  this patch sooner or later.

  * However, since the today's hirsute kernel is just based on groovy,
  I've added hirsute to the SRU.

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

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

[Kernel-packages] [Bug 1902613] Re: drm/i915/dp_mst - only read the base capability in DPCD.

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  drm/i915/dp_mst - only read the base capability in DPCD.

Status in HWE Next:
  New
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  [Impact]
  Currently DRM driver assume the source device caps is higher than the MST 
device
  caps. With this commit, the statement would be broken.

  e.g. the source device only support DP1.2 and the mst device support
  DP1.4.

  The source device can't output the video to the external monitor on
  the docking station.

  [Fix]
  Revert the previous patch and only read the base capability from DPCD.

  [test]
  With the patch, The machine(DP1.2) connect with the external monitor on 
docking station(SC) and
  can output the video to the external monitor on docking station(SC-DP1.4).

  [Regression Potential]
  Can't output 4k@60hz on the docking station(SC).

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

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

[Kernel-packages] [Bug 1902687] [NEW] e1000e: fix issues with S01x

2020-11-03 Thread Timo Aaltonen

Public bug reported:

[Impact]

1. Cold boot system to desktop

2. Press power button to suspend the system

3. Press power button to resume the system.

4. Check the log, you will only find

 e1000e :00:1f.6 eno2: Hardware Error

5. Press power button to suspend the system again

6. System will *auto resume* from the suspend. Then check the logs, you
*will find* follow logs.

[ 120.895527] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x730
[e1000e] returns -2

[ 120.895529] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150
returns -2

[ 120.895530] PM: Device :00:1f.6 failed to suspend async: error
-2

[ 121.539907] PM: Some devices failed to suspend, or early wake
event detected

[Fix]

Four patches from upstream list.
 
 e1000e: fix S0ix flow to allow S0i3.2 subset entry
 e1000e: allow turning s0ix flows on for systems with ME
 e1000e: Add Dell's Comet Lake systems into s0ix heuristics
 e1000e: Add more Dell CML systems into s0ix heuristics

[Test case]

Repeat above.


Not really an SRU as the target is the unstable/devel kernel and oem-5.10 for 
focal (-oem-20.04-edge).

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: In Progress

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

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

Title:
  e1000e: fix issues with S01x

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  1. Cold boot system to desktop

  2. Press power button to suspend the system

  3. Press power button to resume the system.

  4. Check the log, you will only find

   e1000e :00:1f.6 eno2: Hardware Error

  5. Press power button to suspend the system again

  6. System will *auto resume* from the suspend. Then check the logs,
  you *will find* follow logs.

  [ 120.895527] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x730
  [e1000e] returns -2

  [ 120.895529] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150
  returns -2

  [ 120.895530] PM: Device :00:1f.6 failed to suspend async:
  error -2

  [ 121.539907] PM: Some devices failed to suspend, or early wake
  event detected

  [Fix]

  Four patches from upstream list.
   
   e1000e: fix S0ix flow to allow S0i3.2 subset entry
   e1000e: allow turning s0ix flows on for systems with ME
   e1000e: Add Dell's Comet Lake systems into s0ix heuristics
   e1000e: Add more Dell CML systems into s0ix heuristics

  [Test case]

  Repeat above.

  
  Not really an SRU as the target is the unstable/devel kernel and oem-5.10 for 
focal (-oem-20.04-edge).

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

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

[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]

2020-11-03 Thread Luis Alberto Pabón

I realised what an idiotic question that was as I submitted the form.
Please disregard 😬

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

Title:
Cannot boot with thunderbolt dock connected before kernel loads
[groovy] [focal with groovy hwe kernel]

Status in linux package in Ubuntu:
Confirmed

Bug description:
Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays
through the dock (HDMI and VGA). My system uses graphical boot via
plymouth. Dell logo remains on screen while ubuntu loads into gdm3
(when it is booting normally). I'm using LUKS.

This is a regression from focal and kernel 5.4.

If I boot the laptop with the thunderbolt dock connected, the system
will get past the Dell logo, go to a black screen and remain there.
The screen is powered up as I can see some light on the edges. It
won't boot up or respond to any keys.

After force-shutdown via power key long press, on the next boot the
grub menu will appear. The system will boot normally then (with the
dock still connected).

If I boot the system with the dock disconnected, it will correctly go
into disk encryption password prompt. If at that point I connect the
dock and wait without entering the password, the system will correctly
set up the dock: the displays lit up and the mouse and keyboard
plugged into it become active. The system boots normally.

I'm trying to bisect in which kernel version this happened. I'll put
results in a comment.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-generic 5.8.0.25.30
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: luis 3332 F pulseaudio
/dev/snd/controlC0: luis 3332 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Oct 23 16:27:30 2020
InstallationDate: Installed on 2019-08-17 (432 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic
root=/dev/mapper/vglinux-root ro quiet splash
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.8.0-25-generic N/A
linux-backports-modules-5.8.0-25-generic N/A
linux-firmware1.190
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]

2020-11-03 Thread Luis Alberto Pabón

Excellent stuff that is. Just to clarify, will this come in the default
5.4.0 kernel for Ubuntu 20.04.1 or the hwe kernel as the link to the fix
suggests?

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

Title:
Cannot boot with thunderbolt dock connected before kernel loads
[groovy] [focal with groovy hwe kernel]

Status in linux package in Ubuntu:
Confirmed

This is a regression from focal and kernel 5.4.

After force-shutdown via power key long press, on the next boot the
grub menu will appear. The system will boot normally then (with the
dock still connected).

I'm trying to bisect in which kernel version this happened. I'll put
results in a comment.

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

[Kernel-packages] [Bug 1900951] Re: ptrace10 from ubuntu_ltp_syscalls failed on B

2020-11-03 Thread Po-Hsu Lin

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

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

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

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

Title:
  ptrace10 from ubuntu_ltp_syscalls failed on B

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

Bug description:
  Issue found on B-AWS 4.15.0-1087.92

  This is a new test case added a week ago [1]. Test failed with:
   startup='Wed Oct 21 13:10:37 2020'
   tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
   ptrace10.c:60: TFAIL: The rd0 wasn't set on second PTRACE_POKEUSER 

   HINT: You _MAY_ be missing kernel fixes, see:
   
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd14406b78e6

   Summary:
   passed 0
   failed 1
   skipped 0
   warnings 0
   tag=ptrace10 stime=1603285837 dur=0 exit=exited stat=1 core=no cu=0 cs=0


  [1] https://github.com/linux-test-
  project/ltp/blob/master/testcases/kernel/syscalls/ptrace/ptrace10.c

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

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

[Kernel-packages] [Bug 1877654] Re: Add XDP support to hv_netvsc driver