[Kernel-packages] [Bug 1907318] Re: GNOME lockups in nouveau

2021-04-10 Thread Launchpad Bug Tracker
[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/1907318

Title:
  GNOME lockups in nouveau

Status in linux package in Ubuntu:
  Expired

Bug description:
  Running Firefox Nightly on a Thinkpad T510 and experiencing lockups in
  Wayland and in Xorg. SSHing into the machine works, but the mouse is
  unresponsive on the device.

  Here are some traces:

  Dec 08 19:47:48 ThinkPad-T510 kernel: [ cut here ]
  Dec 08 19:47:48 ThinkPad-T510 kernel: refcount_t: underflow; use-after-free.
  Dec 08 19:47:48 ThinkPad-T510 kernel: WARNING: CPU: 3 PID: 1755 at 
lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0
  Dec 08 19:47:48 ThinkPad-T510 kernel: Modules linked in: nfnetlink rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep lz4 zram zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua>
  Dec 08 19:47:48 ThinkPad-T510 kernel:  drm_kms_helper glue_helper psmouse 
libahci sdhci_pci i2c_i801 cqhci i2c_smbus lpc_ich firewire_core syscopyarea 
crc_itu_t sdhci sysfillrect sysimgblt fb_sys_fops ce>
  Dec 08 19:47:48 ThinkPad-T510 kernel: CPU: 3 PID: 1755 Comm: Xwayland 
Tainted: P   O  5.8.0-25-generic #26-Ubuntu
  Dec 08 19:47:48 ThinkPad-T510 kernel: Hardware name: LENOVO 43147PU/43147PU, 
BIOS 6MET92WW (1.52 ) 09/26/2012
  Dec 08 19:47:48 ThinkPad-T510 kernel: RIP: 
0010:refcount_warn_saturate+0xae/0xf0
  Dec 08 19:47:48 ThinkPad-T510 kernel: Code: d9 e0 69 01 01 e8 37 8d b1 ff 0f 
0b 5d c3 80 3d c6 e0 69 01 00 75 91 48 c7 c7 48 af 1f b6 c6 05 b6 e0 69 01 01 
e8 17 8d b1 ff <0f> 0b 5d c3 80 3d a4 e0 69 01 0>
  Dec 08 19:47:48 ThinkPad-T510 kernel: RSP: 0018:a533874f3cc8 EFLAGS: 
00010282
  Dec 08 19:47:48 ThinkPad-T510 kernel: RAX:  RBX: 
0002 RCX: 8afff3d98cd8
  Dec 08 19:47:48 ThinkPad-T510 kernel: RDX: ffd8 RSI: 
0027 RDI: 8afff3d98cd0
  Dec 08 19:47:48 ThinkPad-T510 kernel: RBP: a533874f3cc8 R08: 
0004 R09: 046d
  Dec 08 19:47:48 ThinkPad-T510 kernel: R10:  R11: 
0001 R12: 0004
  Dec 08 19:47:48 ThinkPad-T510 kernel: R13: 8afee6895800 R14: 
8affe1684800 R15: 8affe1992000
  Dec 08 19:47:48 ThinkPad-T510 kernel: FS:  7fc1b91f6a40() 
GS:8afff3d8() knlGS:
  Dec 08 19:47:48 ThinkPad-T510 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 08 19:47:48 ThinkPad-T510 kernel: CR2: 7ffa033700c0 CR3: 
0001d46b2006 CR4: 000206e0
  Dec 08 19:47:48 ThinkPad-T510 kernel: Call Trace:
  Dec 08 19:47:48 ThinkPad-T510 kernel:  ttm_bo_put+0x3f/0x50 [ttm]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  nouveau_gem_new+0x8a/0x120 [nouveau]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  ? nouveau_gem_new+0x120/0x120 [nouveau]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  nouveau_gem_ioctl_new+0x5b/0xd0 
[nouveau]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  ? nouveau_gem_new+0x120/0x120 [nouveau]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  drm_ioctl_kernel+0xae/0xf0 [drm]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  drm_ioctl+0x238/0x3d0 [drm]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  ? nouveau_gem_new+0x120/0x120 [nouveau]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  ? hrtimer_start_range_ns+0x84/0xd0
  Dec 08 19:47:48 ThinkPad-T510 kernel:  nouveau_drm_ioctl+0x66/0xc0 [nouveau]
  Dec 08 19:47:48 ThinkPad-T510 kernel:  ksys_ioctl+0x8e/0xc0
  Dec 08 19:47:48 ThinkPad-T510 kernel:  __x64_sys_ioctl+0x1a/0x20
  Dec 08 19:47:48 ThinkPad-T510 kernel:  do_syscall_64+0x49/0xc0
  Dec 08 19:47:48 ThinkPad-T510 kernel:  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 08 19:47:48 ThinkPad-T510 kernel: RIP: 0033:0x7fc1b990313b
  Dec 08 19:47:48 ThinkPad-T510 kernel: Code: 89 d8 49 8d 3c 1c 48 f7 d8 49 39 
c4 72 b5 e8 1c ff ff ff 85 c0 78 ba 4c 89 e0 5b 5d 41 5c c3 f3 0f 1e fa b8 10 
00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8>
  Dec 08 19:47:48 ThinkPad-T510 kernel: RSP: 002b:7fff362bd6e8 EFLAGS: 
0246 ORIG_RAX: 0010
  Dec 08 19:47:48 ThinkPad-T510 kernel: RAX: ffda RBX: 
7fff362bd740 RCX: 7fc1b990313b
  Dec 08 19:47:48 ThinkPad-T510 kernel: RDX: 7fff362bd740 RSI: 
c0306480 RDI: 000e
  Dec 08 19:47:48 ThinkPad-T510 kernel: RBP: c0306480 R08: 
 R09: 564a23c97760
  Dec 08 19:47:48 ThinkPad-T510 kernel: R10: 564a23ce4630 R11: 
0246 R12: 7fff362bd740
  Dec 08 19:47:48 ThinkPad-T510 kernel: R13: 000e R14: 
564a23383860 R15: 1000
  Dec 08 19:47:48 ThinkPad-T510 kernel: ---[ end trace 52a24d448f20dca6 ]---

  Dec 08 19:57:17 ThinkPad-T510 kernel: [ cut here ]
  Dec 08 19:57:17 ThinkPad-T510 kernel: refcount

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-04-10 Thread James Hennig
Hey there @Coiby Xu thank you,

I think I understand what you mean, basically use your Github for this,
standalone_i2c_hid, but copy the i2c drivers from the cloned Manjaro
kernel 5.9.16-1 ../src/linux-5.9/drivers/hid/i2c-hid/ directory into the
../i2c-hid_standalone/ directory in your project (replacing all 3 source
files without the Makefile), then compile it and replace the according
module in my running system.

Just as a reference, directly dropping in
/lib/modules/5.9.16-1-MANJARO/kernel/drivers/hid/i2c-hid/i2c-hid.ko.xz
into the respective 5.11.6-1-MANJARO ../i2c-hid/ directory, then running
"mkinitcpio -P linux511" (to use the new module.. if this is how to do
it?) does not work, in case anyone was wondering. Touchpad immediately
froze on bootup.

**

I was able to compile the Manjaro 5.9.16-1 source files into a module
(on 5.11.6-1 using linux511-headers) using your provided Makefile and
followed the instructions to copy the compiled module into the
5.11.6-1-MANJARO ../i2c-hid/ directory. Also added the GRUB options and
ran "sudo update-grub". It functioned, but did not fix the issue. Froze
after 2 reboots.

I also tried compiling the Github project as it is, using the provided source 
files (on 5.11.6-1 using linux511-headers) and it spit out:
ERROR: modpost "irq_to_desc" (in ../i2c-hid-standalone/i2c-hid.ko) undefined !
../i2c-hid-standalone/Module.symvers Error 1

Also I wanted to point out in your README the instruction to append
"i2c_hid.polling_mode=1" to GRUB_CMDLINE_LINUX. Shouldn't this be
appended to GRUB_CMDLINE_LINUX_DEFAULT? I don't really know, I've just
never seen the non-_DEFAULT line used before. In either case, produces
same results.

Thanks for all your help, it was worth a shot. Maybe your code needs to
be updated for recent kernels?

I am still trying to play with the idea of focusing on the pinctrl-amd.c
driver, but really need some help with what to do with that driver. I am
not sure the culprit is the i2c_hid driver, but rather this driver.
Maybe I'm wrong, but it certainly is the next place to look...

Fun things to try!

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Vi

[Kernel-packages] [Bug 1469480] Re: HP pavillon zd7000 doesn't detect wifi board

2021-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: b43-fwcutter (Ubuntu)
   Status: New => Confirmed

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

Title:
  HP pavillon  zd7000 doesn't detect wifi board

Status in b43-fwcutter package in Ubuntu:
  Confirmed

Bug description:
  I send you more information about the system and the hardware :
  02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g 
Wireless LAN Controller [14e4:4320] (rev 03)
Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN [103c:12f4]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- http://archive.ubuntu.com/ubuntu/ precise/multiverse i386 Packages
  100 /var/lib/dpkg/status
  davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ sudo dmidecode -s bios-version
  [sudo] password for davide: 
  F.34 
  davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ sudo dmidecode -s 
bios-release-date 
  07/12/2004

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firmware-b43-installer 1:015-9
  ProcVersionSignature: Ubuntu 3.2.0-67.70-lowlatency-pae 3.2.60
  Uname: Linux 3.2.0-67-lowlatency-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Sun Jun 28 08:44:52 2015
  InstallationMedia: Ubuntu-Studio 12.04.3 "Precise Pangolin" - Release i386 
(20130820)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: b43-fwcutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1469480/+subscriptions

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


[Kernel-packages] [Bug 1913410] Re: aws: update Xen hibernation patch set

2021-04-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  aws: update Xen hibernation patch set

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  Amazon maintains a custom patch to enable hibernation in Xen guests
  that is not upstream yet. This patch set has been updated in AWS AL2
  and we should sync up the patch set in our AWS kernels.

  [Test case]

  Tests have been performed (simply doing multiple hibernate/resume
  cycles) with the new patch set applied and they have shown significant
  improvement in terms of reliability.

  [Fix]

  Backport/apply the new Xen hibernation patch set from AWS AL2.

  [Regression potential]

  The patch set is affecting only Xen (in particular the guest code) and
  only hibernation, so the risk of regressions is restricted to this
  particular scenario (Xen + hibernation).

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

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


[Kernel-packages] [Bug 1902864] Re: aws: update patch to batch hibernate and resume IO requests

2021-04-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  aws: update patch to batch hibernate and resume IO requests

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  During hibernation and resume the kernel is submitting an individual
  IO request for each page of data. In the aws kernel we are using a
  custom SAUCE patch to batch IO requests together in order to achieve
  better performance.

  Recently a patch designed to achieve the same goal has been applied
  upstream. This patch has been acknowledged by Amazon and it has shown
  a performance improvement.

  Moreover, this patch looks much cleaner compared to the custom patch
  that we are using and it's upstream, so it makes sense to drop the
  previous patch and apply this new one.

  [Test case]

  Hibernate + resume and measure the time required to perform these
  operations.

  Performance result reported by Amazon:

  One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
  around 21 minutes before the change, and 1 minutes after the change on
  a system with limited storage IOPS.

  [Fix]

  Apply the following upstream commit:

   55c4478a8f0ecedc0c1a0c9379380249985c372a ("PM: hibernate: Batch
  hibernate and resume IO requests")

  Drop the custom aws SAUCE patch:

   11c3fa3b29722124f5c9122671983614383686db ("UBUNTU: SAUCE: [aws] PM /
  hibernate: Speed up hibernation by batching requests")

  [Regression potential]

  Upstream patch that allows to drop a custom patch that is doing the
  same thing. The only potential regression would be a performance drop,
  but according to Amazon's tests and our tests, we didn't notice any
  performance regression. Any other kind of regression would be
  considered as upstream regressions.

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

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


[Kernel-packages] [Bug 1918694] Re: aws: fix hibernation issues on c5.18xlarge

2021-04-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  aws: fix hibernation issues on c5.18xlarge

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Hibernation is still unreliable on c5.18xlarge instances, usually the
  system hibernates correctly, but on resume it either perfoms a regular
  reboot instead of resuming from hibernation, or the system is
  completely stuck after the hibernated kernel is loaded in memory (more
  exactly the system is stuck when the resume callbacks of the
  hibernated kernel are executed).

  [Test plan]

  Create a c5.18xlarge instance, run the memory stress test script (the
  same test script that we are using to stress test hibernation),
  trigger the hibernate event, trigger the resume event. Repeat a couple
  of times and the problem is very likely to happen.

  [Fix]

  Amazon pointed out two fixes that should address both issues:
  1) upstream patch "PM: hibernate: flush swap writer after marking": this 
prevents the regular reboot issue, because it ensures that the I/O is always 
flushed after, not before, writing the hibernation signature

  2) we need to reserve more space for HVC_BOOT_ARRAY_SIZE: this is a
  temporary solution (SAUCE PATCH for now), suggested by Amazon, they
  are working on a proper (more elegant) fix, but doubling the size of
  HVC_BOOT_ARRAY_SIZE seems to resolve the problem, we have tested this
  change extensively in the AWS cloud and it seems to prevent the
  "system stuck on resume" issue from happening

  [Regression potential]

  The first patch is touching only the hibernation code, so potential
  regressions could be experienced only in the hibernation scenario. The
  second patch is more like a hack at the moment and it's affecting
  kvmclock. Increasing the size of HVC_BOOT_ARRAY_SIZE could potentially
  introduce regressions on small sized kvm systems and a better solution
  would be to allocate the array hv_clock_boot dynamically. And this is
  actually the proper fix that Amazon is currently working on. When the
  fix will be published upstream we should apply that one and drop this
  SAUCE PATCH.

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

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


[Kernel-packages] [Bug 1922350] Re: missing amdgpu firmware reported when updating

2021-04-10 Thread RoyK
I just saw this on an HP EliteBook 725 G2

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

Title:
  missing amdgpu firmware reported when updating

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing the following:

  update-initramfs: Generating /boot/initrd.img-5.11.0-13-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ta.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sos.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_toc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_asd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_rlc.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec2.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_me.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_pfp.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ce.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec2.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_me.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_pfp.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_ce.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_sdma.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sdma.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_vcn.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_smc.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_dmcub.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_dmcub.bin for 
module amdgpu
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for cups (2.3.3op2-3ubuntu3) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.67.5-2) ...
  Processing triggers for libc-bin (2.33-0ubuntu4) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-1ubuntu3) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-11-generic 5.11.0-11.12
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dad2584 F pulseaudio
   /dev/snd/controlC0:  dad2584 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr  2 12:27:30 2021
  InstallationDate: Installed on 2021-02-08 (52 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210208)
  MachineType: TUXEDO TUXEDO Pulse 15 Gen1
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic 
root=UUID=dca66736-5282-45e6-a144-59d3339a8d0f ro quiet splash
  RebootRequiredPkgs: network-manager
  RelatedPackage

Re: [Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2021-04-10 Thread ANDREA MATTANA
It is not available on Ubuntu 18.04,need to upgrade distro to 20.04 or try
to upgrade just the lib from the 20.04 repos.

Il sab 10 apr 2021, 16:50 milaad <1810...@bugs.launchpad.net> ha
scritto:

> i cant find libevdev2 package for manjaro , any help?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1823320).
> https://bugs.launchpad.net/bugs/1810183
>
> Title:
>   numpad on touchpad doesn't work in ASUS Zenbook 14
>
> Status in Linux:
>   New
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10
> alongside windows 10.
>   The numeric keypads are within the touchpad and are supposed to be
> turned on by a button on the touchpad. This works well in Windows but
> doesn't work in Ubuntu.
>   I have tried to search for any related problems/solutions online but I
> haven't been able to.
>   I will appreciate any suggestion or help.
>   Thanks,
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.10-0ubuntu13.1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.10
>   InstallationDate: Installed on 2018-12-30 (4 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   Package: linux (not installed)
>   Tags:  cosmic
>   Uname: Linux 4.19.11-041911-generic x86_64
>   UnreportableReason: The running kernel is not an Ubuntu kernel
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.10-0ubuntu13.1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.10
>   InstallationDate: Installed on 2018-12-30 (4 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   Package: linux (not installed)
>   Tags:  cosmic
>   Uname: Linux 4.18.10-041810-generic x86_64
>   UnreportableReason: The running kernel is not an Ubuntu kernel
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions
>

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54

2021-04-10 Thread Bob
Yep, real shame this bug was forgotten. :(

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

Title:
  Radeon mobility HD3450 (RV620) heavy screen flickering after trying to
  upgrade kernel 4.15.0-54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450.
  Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic.
  This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX 
and so on.
  I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 
kernel). I cannot upgrade to newer kernels.
  Seems that the fixes for bug #1791312 broke my kind of card.

  here is a video:
  https://youtu.be/9Rez7s0V6iA

  here is another user with same problem:
  https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005

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

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


[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2021-04-10 Thread milaad
i cant find libevdev2 package for manjaro , any help?

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1891768] Re: hfs+ filesystems fail reading / writing large files

2021-04-10 Thread Richard J Uschold
FYI: MX Linux currently is the most downloaded distro on distro watch.

I erroneously assumed that there was only ONE Linux kernel bug fix team.
My mistake.

So, what is the process where kernel bugs fixed by Ubuntu migrate to the
other distro kernels and vice versa?

How do I figure out what official bug number fixed my hfs+ bug, as there
is no reference to hfs in 5.11 change log?

Thanks

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

Title:
  hfs+ filesystems fail reading / writing large files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed a problem reading hfs+ partitions on a USB flash drive after
  I installed Ubuntu 20.04 on two laptop machines. I have a Mini Mac
  that I share files via an USB flash drive formatted with hfs+ from the
  laptops with Ubuntu installed. I had no issues with Ubuntu Mate 18.10.

  I noticed that very large files, typicality larger than 100 MB, would
  have read errors or sometimes have a zero file size. One particular
  file about 500MB fails nearly every time. Other files, down to about
  100MB fail sometimes.

  I bought a new USB flash drive, but have the same failures on that.
  I have an identical flash drive formatted with ext4 which has no issues. I'm 
currently booting to Ubuntu Mate 18.10 to write the hfs+ USB flash drive.

  
  1007 ceres ~ cat /proc/version_signature
  Ubuntu 5.4.0-42.46-generic 5.4.44

  1000 ceres ~ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  1005 admin@ceres ~ sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error
  pcilib: sysfs_read_vpd: read failed: Input/output error
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uschcld1581 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-17 (91 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c06c Logitech, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-576
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=75021464-0e3f-4ad2-a466-cf655a6c4dd7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip fax floppy plugdev tape video www-data
  _MarkForUpload: True
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.47
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: KBL
  dmi.board.version: V1.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:svnAcer:pnAspireE5-576:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire E 15
  dmi.product.name: Aspire E5-576
  dmi.product.sku: 
  dmi.product.version: V1.47
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1923291] Re: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2021-04-10 Thread Colin Ian King
If you can attach /var/lib/dkms/zfs/0.8.3/build/make.log to the bug
report that would be useful. I'm fairly confident that the failure to
build the 20.10 zfs 0.8.x is because it not compatible with a 5.11
kernel.

If you want the lest 5.11 kernel then I suggest moving to Ubuntu 21.04
as this has a 5.11 kernel and ZFS 2.0.x that is supported on the 5.11
kernels.


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

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

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

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

Title:
  package zfs-dkms (not installed) failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Trying to get new PC running, combination of Ryzen CPU, B550
  motherboard & zfs filesystems means I need to use recent kernel, but
  cannot install zfs

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: zfs-dkms (not installed)
  Uname: Linux 5.11.12-051112-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 10 16:59:29 2021
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2021-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: zfs-linux
  Title: package zfs-dkms (not installed) failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2021-04-10 Thread Aldric Degorre
#107 (sorry, my previous message was meant as an answer to #107 too!)

Incidentally, linux-oem-5.10 does not fix this my issue (with a WB19TB
dock).

Does this kernel work well with the TB16?

What are the relevant logs I should join to my bug report to linux-
oem-5.10? Is dmesg output enough?

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

   
  [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd  
 

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2021-04-10 Thread Aldric Degorre
#106 The described symptoms are so specific that it would be a really
surprising coincidence if my issue had a different cause with so
identical symptoms.

Are you sure this is really about the dock?
What if it was actually about the thunderbolt controller on the motherboard 
instead?
I assume most people who post here also have similar computers (being Dell 
consumers).

Another argument supporting this theory: the system switches to the
faulty mode after a suspend/resume of the computer. Nothing you do with
just the dock triggers the faulty mode until you suspend/resume the
computer and, after that, nothing you do with the dock (including
powering it down and up again) will switch the system back to the non-
faulty mode until the computer is powered down. Moreover the system
switches to faulty mode as soon as a computer suspend/resume occurs,
even if no thunderbolt dock was actually plugged in yet when the
computer was suspended.

Of course I don't know what are the results of the investigations so
far, so I may be completely wrong. But then it would be very interesting
to know the explanation.

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

[Kernel-packages] [Bug 1891768] Re: hfs+ filesystems fail reading / writing large files

2021-04-10 Thread Juerg Haefliger
Sorry but MX Linux (whatever that is) is not something we support with
an Ubuntu kernel. If you find a kernel problem in a supported Ubuntu
release we'll do our best to fix that.

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

Title:
  hfs+ filesystems fail reading / writing large files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed a problem reading hfs+ partitions on a USB flash drive after
  I installed Ubuntu 20.04 on two laptop machines. I have a Mini Mac
  that I share files via an USB flash drive formatted with hfs+ from the
  laptops with Ubuntu installed. I had no issues with Ubuntu Mate 18.10.

  I noticed that very large files, typicality larger than 100 MB, would
  have read errors or sometimes have a zero file size. One particular
  file about 500MB fails nearly every time. Other files, down to about
  100MB fail sometimes.

  I bought a new USB flash drive, but have the same failures on that.
  I have an identical flash drive formatted with ext4 which has no issues. I'm 
currently booting to Ubuntu Mate 18.10 to write the hfs+ USB flash drive.

  
  1007 ceres ~ cat /proc/version_signature
  Ubuntu 5.4.0-42.46-generic 5.4.44

  1000 ceres ~ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  1005 admin@ceres ~ sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error
  pcilib: sysfs_read_vpd: read failed: Input/output error
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uschcld1581 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-17 (91 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c06c Logitech, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-576
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=75021464-0e3f-4ad2-a466-cf655a6c4dd7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip fax floppy plugdev tape video www-data
  _MarkForUpload: True
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.47
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: KBL
  dmi.board.version: V1.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:svnAcer:pnAspireE5-576:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire E 15
  dmi.product.name: Aspire E5-576
  dmi.product.sku: 
  dmi.product.version: V1.47
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1923291] Re: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2021-04-10 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package zfs-dkms (not installed) failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Trying to get new PC running, combination of Ryzen CPU, B550
  motherboard & zfs filesystems means I need to use recent kernel, but
  cannot install zfs

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: zfs-dkms (not installed)
  Uname: Linux 5.11.12-051112-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 10 16:59:29 2021
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2021-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: zfs-linux
  Title: package zfs-dkms (not installed) failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1923291] [NEW] package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2021-04-10 Thread Adrian Tritschler
Public bug reported:

Trying to get new PC running, combination of Ryzen CPU, B550 motherboard
& zfs filesystems means I need to use recent kernel, but cannot install
zfs

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: zfs-dkms (not installed)
Uname: Linux 5.11.12-051112-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Apr 10 16:59:29 2021
ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2021-04-10 (0 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.3
SourcePackage: zfs-linux
Title: package zfs-dkms (not installed) failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy

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

Title:
  package zfs-dkms (not installed) failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Trying to get new PC running, combination of Ryzen CPU, B550
  motherboard & zfs filesystems means I need to use recent kernel, but
  cannot install zfs

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: zfs-dkms (not installed)
  Uname: Linux 5.11.12-051112-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 10 16:59:29 2021
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2021-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: zfs-linux
  Title: package zfs-dkms (not installed) failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1919315] Re: binary assembly failures with CONFIG_MODVERSIONS present

2021-04-10 Thread Andy Whitcroft
** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-focal 
verification-done-groovy

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

Title:
  binary assembly failures with CONFIG_MODVERSIONS present

Status in linux-restricted-modules package in Ubuntu:
  Fix Released

Bug description:
  LRM and the end-user system are intended to assemble the package in
  the same manner to ensure we have reproducible binaries.  This is
  needed so that pre-generated signatures are applicable.  It seems for
  (at least some installations) when CONFIG_MODVERSIONS is set that
  though the LRM assembly completes correctly in the face of seemingly
  benign errors, that the final end-user assembly only works for two of
  the four kernel modules.

  Cleaning up the errors for _only_ the end-user assembly renders the
  binaries identical to those produced in the main package and thus
  matching the signatures.  It is unclear as to the trigger leading to
  the failure to assemble on the end-user system.

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

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