[Kernel-packages] [Bug 1901129] [NEW] Fix broken Realtek 8821C BT after S3

[Kai-Heng Feng]

Public bug reported:

[Impact]
Realtek 8821C Bluetooth controller may stop working after S3.

[Fix]
Use the new firmware from Realtek.
Link: 
https://lore.kernel.org/linux-firmware/20201013084718.3077-1-max.c...@realtek.com/

[Test]
With the new firmware, the BT controller works and can pass 1000 cycles
of S3.
 
[Regression Potentianl]
It's always hit-or-miss for firmware update. Since Realtek asked us to
use this firmware, we can only trusth them.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-firmware (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: linux-firmware (Ubuntu Groovy)
 Importance: Medium
 Status: Confirmed


** Tags: oem-priority originate-from-1893308 stella

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

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

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

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

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

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

** Tags added: oem-priority originate-from-1893308 stella

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

Title:
  Fix broken Realtek 8821C BT after S3

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Focal:
  Confirmed
Status in linux-firmware source package in Groovy:
  Confirmed

Bug description:
  [Impact]
  Realtek 8821C Bluetooth controller may stop working after S3.

  [Fix]
  Use the new firmware from Realtek.
  Link: 
https://lore.kernel.org/linux-firmware/20201013084718.3077-1-max.c...@realtek.com/

  [Test]
  With the new firmware, the BT controller works and can pass 1000 cycles
  of S3.
   
  [Regression Potentianl]
  It's always hit-or-miss for firmware update. Since Realtek asked us to
  use this firmware, we can only trusth them.

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

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

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Christopher M . Peñalver]

Henry Wertz, a hardware failure causing collatoral logging wouldn't be
considered something for a developer to change here, but I'll mark this
Confirmed for now should a bug exist. Feel free to mark this Status
Invalid if you like.

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell Inspiron 1545 dmesg, I get:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This will be like 2-10 seconds apart, then it could be 5 minutes or
  more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kernel.

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => High

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

Title:
  Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
  laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

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

Bug description:
  I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
  to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.

  I've been unsuccessful to pair with 2 different bluetooth mice.
  However bluetooth seems to work with other devices. I'm under the
  impression that this problem only happens with Bluetooth LE devices.

  Trying to pair using bluetoothctl fails with the
  org.bluez.Error.AuthenticationCanceled error:

  [bluetooth]# pair E5:5B:67:2A:09:76
  Attempting to pair with E5:5B:67:2A:09:76
  [CHG] Device E5:5B:67:2A:09:76 Connected: yes
  [CHG] Device E5:5B:67:2A:09:76 Connected: no
  Failed to pair: org.bluez.Error.AuthenticationCanceled

  A quick google search for org.bluez.Error.AuthenticationCanceled
  reported nothing relevant.

  Running btmon while trying to pair with the device gives me the
  following:

  Bluetooth monitor ver 5.53
  = Note: Linux version 5.4.0-40-generic (x86_64)   
0.998188
  = Note: Bluetooth subsystem version 2.22  
0.998193
  = New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0) 
 [hci0] 0.998194
  = Open Index: E8:6F:38:9C:2B:3C   
 [hci0] 0.998195
  = Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)   
 [hci0] 0.998197
  @ MGMT Open: bluetoothd (privileged) version 1.14 
   {0x0001} 0.998198
  @ MGMT Open: btmon (privileged) version 1.14  
   {0x0002} 0.998310
  @ MGMT Command: Pair Device (0x0019) plen 8   
{0x0001} [hci0] 8.162442
  LE Address: E5:5B:67:2A:09:76 (Static)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8   
  #1 [hci0] 8.162527
  Own address type: Public (0x00)
  Filter policy: Ignore not in white list (0x01)
  PHYs: 0x01
  Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
  > HCI Event: Command Complete (0x0e) plen 4   
  #2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
  Status: Success (0x00)
  < HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6   
  #3 [hci0] 8.284654
  Extended scan: Enabled (0x01)
  Filter duplicates: Enabled (0x01)
  Duration: 0 msec (0x)
  Period: 0.00 sec (0x)
  > HCI Event: Command Complete (0x0e) plen 4   
  #4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
  Status: Success (0x00)
  > HCI Event: LE Meta Event (0x3e) plen 52 
  #5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
  Num reports: 1
  Entry 0
Event type: 0x0013
  Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
  Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)

[Kernel-packages] [Bug 1853050] Re: Realtek RTL8822BE [10ec:b822] Subsystem [1a3b:2950] Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)

[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/1853050

Title:
  Realtek RTL8822BE [10ec:b822] Subsystem [1a3b:2950] Wifi fails to
  connect (RTL8822BE, linux 5.3.0 w/ rtwpci)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Wifi just fails to connect to an access point after upgrading from
  Ubuntu 19.04 to 19.10.

  Some outputs:
  uname -a
  Linux mothership 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

   lspci -nnk | grep 0280 -A3
  03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter [10ec:b822]
Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950]
Kernel driver in use: rtw_pci
Kernel modules: rtwpci

  The typical failure looks like this in journalctl:

  Nov 18 23:04:13 mothership kernel: wlp3s0: send auth to d4:60:e3:15:4d:71 
(try 3/3)
  Nov 18 23:04:13 mothership kernel: [ cut here ]
  Nov 18 23:04:13 mothership kernel: purge skb(s) not reported by firmware
  Nov 18 23:04:13 mothership kernel: WARNING: CPU: 5 PID: 0 at 
drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 
[rtw88]
  Nov 18 23:04:13 mothership kernel: Modules linked in: nf_conntrack_netlink 
xt_owner xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype 
bpfilter aufs overlay binfmt_misc nvidia_uvm(O
  Nov 18 23:04:13 mothership kernel:  spi_pxa2xx_platform videobuf2_memops 
asus_wmi videobuf2_v4l2 i915 mxm_wmi wmi_bmof sparse_keymap serio_raw 
videobuf2_common cfg80211 dw_dmac soundcore dw_dmac_core videodev input_leds 
drm_kms_helper joydev ipmi_devintf libarc4 mc ipmi_
  Nov 18 23:04:13 mothership kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: P   
 W  OE 5.3.0-23-generic #25-Ubuntu
  Nov 18 23:04:13 mothership kernel: Hardware name: ASUSTeK COMPUTER INC. 
X705UDR/X705UDR, BIOS X705UDR.300 08/29/2017
  Nov 18 23:04:13 mothership kernel: RIP: 
0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88]
  Nov 18 23:04:13 mothership kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 
f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 cd b3 c0 e8 
f6 fa 7b f6 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 3f 1c f7 48 8d 7b e0 49 89 c4 e8
  Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b4020ce48 EFLAGS: 00010286
  Nov 18 23:04:13 mothership kernel: RAX:  RBX: 
913317bed848 RCX: 0006
  Nov 18 23:04:13 mothership kernel: RDX: 0007 RSI: 
0082 RDI: 91331eb57440
  Nov 18 23:04:13 mothership kernel: RBP: a25b4020ce60 R08: 
1754 R09: 0004
  Nov 18 23:04:13 mothership kernel: R10:  R11: 
0001 R12: 91331eb5b600
  Nov 18 23:04:13 mothership kernel: R13: 913317bed848 R14: 
c0adb7d0 R15: 913317bed848
  Nov 18 23:04:13 mothership kernel: FS:  () 
GS:91331eb4() knlGS:
  Nov 18 23:04:13 mothership kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 18 23:04:13 mothership kernel: CR2: 7fb4eee0b000 CR3: 
0003818bc005 CR4: 003606e0
  Nov 18 23:04:13 mothership kernel: Call Trace:
  Nov 18 23:04:13 mothership kernel:  
  Nov 18 23:04:13 mothership kernel:  call_timer_fn+0x32/0x130
  Nov 18 23:04:13 mothership kernel:  __run_timers.part.0+0x177/0x270
  Nov 18 23:04:13 mothership kernel:  ? enqueue_hrtimer+0x3d/0x90
  Nov 18 23:04:13 mothership kernel:  ? recalibrate_cpu_khz+0x10/0x10
  Nov 18 23:04:13 mothership kernel:  ? ktime_get+0x42/0xa0
  Nov 18 23:04:13 mothership kernel:  run_timer_softirq+0x2a/0x50
  Nov 18 23:04:13 mothership kernel:  __do_softirq+0xe1/0x2d6
  Nov 18 23:04:13 mothership kernel:  ? hrtimer_interrupt+0x13b/0x220
  Nov 18 23:04:13 mothership kernel:  irq_exit+0xae/0xb0
  Nov 18 23:04:13 mothership kernel:  smp_apic_timer_interrupt+0x7b/0x140
  Nov 18 23:04:13 mothership kernel:  apic_timer_interrupt+0xf/0x20
  Nov 18 23:04:13 mothership kernel:  
  Nov 18 23:04:13 mothership kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x420
  Nov 18 23:04:13 mothership kernel: Code: ff e8 5f 73 83 ff 80 7d c7 00 74 17 
9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 ce 89 ff fb 66 0f 
1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18
  Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b400f3e38 EFLAGS: 
0246 ORIG_RAX: ff13
  Nov 18 23:04:13 mothership kernel: RAX: 91331eb6a740 RBX: 
b895a740 RCX: 001f
  Nov 18 23:04:13 mothership kernel: RDX:  RSI: 
4041ceb5 RDI: 

[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

[You-Sheng Yang]

kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tag/?h=ath-202010011934

firmware: 
https://github.com/kvalo/ath11k-firmware/tree/master/QCA6390/hw2.0/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1
board file: 
https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/board-2.bin
To be placed under /lib/firmware/ath11k/QCA6390/hw2.0

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

Title:
  Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.6 source package in Focal:
  Incomplete
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1842 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.

   enx00e04c6801fa  no wireless extensions.
  MachineType: Dell Inc. XPS 13 9310
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=580a1e2b-9a42-4f3b-b20f-ddbed7b572f5 ro
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  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.6.0-1010-oem N/A
   linux-backports-modules-5.6.0-1010-oem  N/A
   linux-firmware  1.187+lp1867862.1
  RfKill:

  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 05/14/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.9
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.9:bd05/14/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

[Kai-Heng Feng]

Is it a regression? Did it work in older release like 16.04?

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

Title:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

  PIONEER BD-RW   BDR-205

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:11:53 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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

[Kernel-packages] [Bug 1901115] Re: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

[Daniel van Vugt]

I'm not sure we should allow failure to start the daemon to be
classified as an install failure...

Okt 23 07:08:46 atom systemd[1]: bluetooth.service: 
Killing process 636 (bluetoothd) with signal SIGKILL.
Okt 23 07:08:46 atom systemd[1]: 
bluetooth.service: Failed with result 
'exit-code'.
Okt 23 07:08:46 atom systemd[1]: bluetooth.service: Unit process 636 
(bluetoothd) remains running after unit stopped.
Okt 23 07:08:46 atom systemd[1]: Failed to start 
Bluetooth service.
dpkg: error processing package bluez (--configure):
 installed bluez package post-installation script subprocess returned error 
exit status 1
Setting up libwind0-heimdal:amd64 (7.7.0+dfsg-2) ...

** Summary changed:

- package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
+ package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1 
[Failed to start Bluetooth service.]

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

Title:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1 [Failed to start Bluetooth service.]

Status in bluez package in Ubuntu:
  New

Bug description:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1
  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
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 07:08:46 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
  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.10
  SourcePackage: bluez
  Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 10/03/2019
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05YMV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3180
  dmi.product.sku: 07B2
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

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

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

[Kernel-packages] [Bug 1901115] Re: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

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

Title:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

Status in bluez package in Ubuntu:
  New

Bug description:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1
  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
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 07:08:46 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
  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.10
  SourcePackage: bluez
  Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 10/03/2019
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05YMV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3180
  dmi.product.sku: 07B2
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

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

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

[Kernel-packages] [Bug 1901115] [NEW] package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

[Akbarbek Musayev]

Public bug reported:

package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
package post-installation script subprocess returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: bluez 5.55-0ubuntu1
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
CasperMD5CheckResult: skip
Date: Fri Oct 23 07:08:46 2020
ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 3180
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
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.10
SourcePackage: bluez
Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
dmi.bios.date: 10/03/2019
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.0
dmi.board.name: 05YMV0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 3180
dmi.product.sku: 07B2
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

** Affects: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1901115

Title:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

Status in bluez package in Ubuntu:
  New

Bug description:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1
  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
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 07:08:46 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
  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.10
  SourcePackage: bluez
  Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 10/03/2019
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05YMV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3180
  dmi.product.sku: 07B2
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1900910] Re: [nouveau] Screen freeze after closing lid and suspend

[Daniel van Vugt]

> If this project is active, then change the status of this bug to
something appropriate, and I'll support you.

OK in that case I can reopen this bug and we next request that you:

 1. Uninstall the proprietary Nvidia driver.

 2. Reproduce the original bug.

 3. Test newer kernel versions and tell us which, if any, fix the problem:
https://kernel.ubuntu.com/~kernel-ppa/mainline/

> Installing the proprietary version is a workaround. (Which has its own
> problems...after awakening from Suspend, screen icon text is illegible.)

I know that problem - it is specific to the Nvidia driver. But I am not
aware of any official bug report for it yet. Please open a new bug for
that.

** Changed in: linux (Ubuntu)
   Status: Won't Fix => 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/1900910

Title:
  [nouveau] Screen freeze after closing lid and suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I 
get only a black screen (and the power light is on) when I open the laptop lid.
  I tried various 3-finger salutes, and nothing changes. There is no cursor. I 
cannot get to the console screens. The only thing that works is holding the 
power button until the laptop shuts off.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44
  Uname: Linux 5.4.0-7642-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 21 14:25:22 2020
  DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703]
  InstallationDate: Installed on 2017-11-01 (1085 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic 
root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash 
snd_hda_intel.probe_mask=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10RSA1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Serval WS
  dmi.product.sku: Not Applicable
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login

[Daniel van Vugt]

Eduard,

For 'amdgpu' that's also this bug. I will add a tag to request a focal
fix for that kernel issue. The fix should come from upstream kernel
5.4.69.

** Tags added: rls-ff-incoming

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

Title:
  Showing two cursors after login

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Showing two cursors after login to ubuntu-desktop.

  One cursor moves and is scaled, and one is stationary mid screen and
  not scaled.

  The moving cursor does not appear on screenshots, making it difficult
  to upload a screenshot.

  Previously reported:
  https://gitlab.gnome.org/GNOME/mutter/issues/904
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428

  Package: mutter 3.36.1-3ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 20:06:53 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions

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

[Kernel-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

[Daniel van Vugt]

** Tags added: focal

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

Title:
  Internal mic stops working when plugging in headphones

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

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

[bugproxy]

--- Comment From y...@cn.ibm.com 2020-10-22 21:30 EDT---
Based on this comments, can I say the issue is fixed in Ubuntu20.04?

(In reply to comment #29)
> The focal part of this ticket is addressed by:
> "Focal update: v5.4.69 upstream stable release"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900624
> And LP 1900624 is Fix Committed and the patches are already applied to focal
> master-next.
> Hence aligning the status of this ticket to LP 1900624 and updating it to
> Fix Committed.

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

Title:
  dasd_fba io error and kernel panic

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released

Bug description:
  Generated I/O errors every hour in syslog and caused kernel panic with 
workloads running
   
  ---uname output---
  Linux ubuntutest01 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC 
2020 s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  distro provided. up-to-date from Ubuntu18.04.
   
  Machine Type = z15 
   
  ---System Hang---
   The hourly generated I/O errors didn't impact the system up and running. 
When there are workloads on it, it will cause kernel panic and rebooted the 
server. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   After migrated from 16.04 to 18.04, will see the i/o errors. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Device driver error code:
   [52297.898232] dasd.5c0c98: 0.0.0100: default ERP has run out of retries and 
failed
  [52297.898244] dasd(fba): I/O status report for device 0.0.0100:
 dasd(fba): in req: 2e142bcd CS: 0x20 DS: 0x0C
 dasd(fba): device 0.0.0100: Failing CCW: a84f6c9f
 dasd(fba): SORRY - NO VALID SENSE AVAILABLE
  [52297.898255] dasd(fba): Related CP in req: 2e142bcd
 dasd(fba): CCW d15f44d3: 63400010 7FE2BBA0 DAT: 
0200 008150F2  0017
 dasd(fba): CCW b09ad76e: 4348 7FE2BBB0 DAT: 
0506 
 dasd(fba): CCW c44dfb20: 41600C00 F360 DAT: 
       
 dasd(fba): CCW a84f6c9f: 4348 7FE2BBB8 DAT: 
0510 0006
 dasd(fba): CCW 22dac88c: 4160  DAT:
 dasd(fba): CCW 69686544: 4348 7FE2BBC0 DAT: 
0502 0016
 dasd(fba): CCW 7bb6a17c: 41200400 F360 DAT: 
       
  [52297.898278] print_req_error: I/O error, dev dasda, sector 8474866
   
  *Additional Instructions for y...@cn.ibm.com: 
  -Attach sysctl -a output output to the bug.

  [reply] [?]
  Internal Only
  Comment 1 QI YE 2020-03-12 02:29:20 CDT

  The z/VM version 6.4

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

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

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Henry Wertz]

"1) Do you actually have superflous key strokes, along with that which is 
logged in dmesg?"
Nope, totally asymptomatic.

"2) Could you please test the latest mainline kernel (now 5.9.1) and advise to 
the results?"
Here ya go.  I can attach entire dmesg if you want, but from 5.9.1 dmesg:
[  256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
[  256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known.
[  265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
[  265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known.

"3) Did you personally test this with your Inspiron 1545 in a prior version of 
Ubuntu"
No.  I don't think it started logging this (at least often enough to notice) 
until my battery went from holding like a minute or two of battery life to 
holding 0, which only happened in the last 2-4 weeks. 

Honestly, I'd be totally fine if it was closed "wontfix" (I guess
launchpad doesn't have that) or "invalid", the kernel's logging a non-
standard keystroke sent by the Dell, which seems legitimate and harmless
(it'd be a nuisance if it was every second but it's not close to that);
in addition the Dell is effectively sending it in response to a hardware
failure, so I could see "if you don't want this in your kernel log,
replace your battery" being a legitimate response. Let me know and I'll
set it!

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my Dell Inspiron 1545 dmesg, I get:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This will be like 2-10 seconds apart, then it could be 5 minutes or
  more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kernel.

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1900929] Re: after install, invoking nvidia-settings shows no driver

[Daniel Letzeisen]

Please run the following command to gather logs for the system:
apport-collect 1900929

** Changed in: nvidia-settings (Ubuntu)
   Status: New => Incomplete

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

Title:
  after install, invoking nvidia-settings shows no driver

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  Incomplete

Bug description:
  Using MUON, installed the nvidia driver metapackage for 450.
  [note; this bug applies to all packages, 390, 330, etc].

  Using terminal, when invoking nvidia-settings, the nvidia window is
  completely blank and the following errors are reported...

  (process:18974): Gtk-WARNING **: 08:23:46.948: Locale not supported by C 
library.
  Using the fallback 'C' locale.
  ERROR: NVIDIA driver is not loaded
  ERROR: Unable to load info from any available system
  (nvidia-settings:18974): GLib-GObject-CRITICAL **: 08:23:47.413: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  ** Message: 08:23:47.420: PRIME: No offloading required. Abort
  ** Message: 08:23:47.420: PRIME: is it supported? no

  
  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.4.0-52-generic
  OS Type: 64-bit
  Processors: 6 × AMD FX(tm)-6300 Six-Core Processor
  Memory: 31.3 GiB of RAM

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Christopher Yates]

Ahhh.  I do have 3 tunnels up as well.  Good find!

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  

[Kernel-packages] [Bug 1900889] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000

[Simon Déziel]

Indeed, I have no way of reproducing reliably, unfortunately. I've
installed the PPA your provided (thanks!):

# dmesg | grep ZFS
[   18.284162] ZFS: Loaded module v0.8.3-1ubuntu12.5~lp1900889, ZFS pool 
version 5000, ZFS filesystem version 5

So far, no problem to report and I'll let you know how it goes over the
next few days.

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

Title:
  BUG: kernel NULL pointer dereference, address: 

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  While zfs send'ing from Bionic to Focal, my send/recv hung midway and
  I found this in the receiver's dmesg:

  BUG: kernel NULL pointer dereference, address: 
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x) - not-present page
  PGD 0 P4D 0 
  Oops:  [#1] SMP PTI
  CPU: 0 PID: 94310 Comm: receive_writer Tainted: P   O  
5.4.0-52-generic #57-Ubuntu
  Hardware name: System manufacturer System Product Name/C60M1-I, BIOS 0502 
05/22/2014
  RIP: 0010:abd_verify+0xa/0x40 [zfs]
  Code: ff 85 c0 74 12 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 00 5b 5d c3 e8 
04 ff ff ff eb e7 c3 90 55 48 89 e5 41 54 53 48 89 fb <8b> 3f e8 0f ff ff ff 85 
c0 75 22 44 8b 63 1c 48 8b 7b 20 4d 85 e4
  RSP: 0018:b797c555baa8 EFLAGS: 00010286
  RAX: 4000 RBX:  RCX: 
  RDX: 4000 RSI: 4000 RDI: 
  RBP: b797c555bab8 R08: 0253 R09: 
  R10: 953b56a17848 R11:  R12: 4000
  R13: 953ad201d280 R14: 4000 R15: 
  FS:  () GS:953b56a0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2:  CR3: 000151ab4000 CR4: 06f0
  Call Trace:
   abd_borrow_buf+0x19/0x60 [zfs]
   abd_borrow_buf_copy+0x1a/0x50 [zfs]
   zio_crypt_copy_dnode_bonus+0x30/0x130 [zfs]
   arc_buf_untransform_in_place.isra.0+0x2b/0x40 [zfs]
   arc_buf_fill+0x1f0/0x4a0 [zfs]
   arc_untransform+0x22/0x90 [zfs]
   dbuf_read_verify_dnode_crypt+0xed/0x160 [zfs]
   ? atomic_cmpxchg+0x16/0x30 [zfs]
   dbuf_read_impl+0x3ea/0x610 [zfs]
   dbuf_read+0xcb/0x5f0 [zfs]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? do_raw_spin_unlock+0x9/0x10 [zfs]
   ? __raw_spin_unlock+0x9/0x10 [zfs]
   dmu_bonus_hold_by_dnode+0x92/0x190 [zfs]
   receive_object+0x442/0xae0 [zfs]
   ? __list_del_entry.isra.0+0x22/0x30 [zfs]
   ? atomic_dec+0xd/0x20 [spl]
   receive_process_record+0x170/0x1c0 [zfs]
   receive_writer_thread+0x9a/0x150 [zfs]
   ? receive_process_record+0x1c0/0x1c0 [zfs]
   thread_generic_wrapper+0x83/0xa0 [spl]
   kthread+0x104/0x140
   ? clear_bit+0x20/0x20 [spl]
   ? kthread_park+0x90/0x90
   ret_from_fork+0x22/0x40
  Modules linked in: ip6table_filter ip6_tables xt_conntrack iptable_filter 
bpfilter zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) 
nls_iso8859_1 zlua(PO) eeepc_wmi asus_wmi sparse_keymap wmi_bmof video ccp 
radeon kvm r8169 realtek k10temp ttm i2c_piix4 drm_kms_helper i2c_algo_bit 
fb_sys_fops syscopyarea sysfillrect sysimgblt wmi sch_fq_codel nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 veth bridge 8021q garp mrp stp llc xt_tcpudp 
xt_owner xt_LOG nf_log_ipv6 nf_log_ipv4 nf_log_common drm ip_tables x_tables 
autofs4 btrfs libcrc32c xor zstd_compress raid6_pq hid_generic usbhid hid ahci 
libahci mac_hid
  CR2: 
  ---[ end trace 374aa76997d6bc9b ]---
  RIP: 0010:abd_verify+0xa/0x40 [zfs]
  Code: ff 85 c0 74 12 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 00 5b 5d c3 e8 
04 ff ff ff eb e7 c3 90 55 48 89 e5 41 54 53 48 89 fb <8b> 3f e8 0f ff ff ff 85 
c0 75 22 44 8b 63 1c 48 8b 7b 20 4d 85 e4
  RSP: 0018:b797c555baa8 EFLAGS: 00010286
  RAX: 4000 RBX:  RCX: 
  RDX: 4000 RSI: 4000 RDI: 
  RBP: b797c555bab8 R08: 0253 R09: 
  R10: 953b56a17848 R11:  R12: 4000
  R13: 953ad201d280 R14: 4000 R15: 
  FS:  () GS:953b56a0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2:  CR3: 000151ab4000 CR4: 06f0

  The receiving side uses ZFS native encryption and had the key manually
  loaded before sending/receiving. The sending side is unencrypted. The
  recv hung after 611MiB out of the 990.4 MB delta.

  
  Additional information:

  sending side is a laptop running Bionic:

  $ uname -a
  Linux simon-lemur 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l| grep zfs
  ii  libzfs2linux   0.7.5-1ubuntu16.10 
 amd64OpenZFS 

[Kernel-packages] [Bug 1426216] Re: pci driver messages - BAR 13: no space for

[Luiz Carlos Maciel Franco]

it is related to usb controllers

i have a dell g7 7588 model and i brought a typec hud and plugged into
my thunderbolt port

to the hub i connected mouse|keyboard and rebooted machine

this error has gone

my usb port is 3.1, and bios is latest

with pendrive noerror

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

Title:
  pci driver messages - BAR 13: no space for

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  pci driver messages - BAR 13: no space for 

  ---uname output---
  3.18.0-12-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
  Install Ubuntu 15.04 daily build running bare-metal
  After the installation following messages are seen in dmesg. 
  Not sure if these indicate a problem. Can some one look at these and confirm 
if this is problem or can be ignored ?

  Messages from dmesg log

  [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4
  [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit]
  [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit]
  [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe081ff]
  [0.714581] pci 0001:00:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0817f]
  [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 
0x3fe08180-0x3fe08183]
  [0.714595] pci 0001:01:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 
0x3b101000-0x3b101fff 64bit pref]
  [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 
0x3b102000-0x3b102fff 64bit pref]
  [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 
0x3b103000-0x3b103fff 64bit pref]
  [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0807f]
  [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 
0x3fe08080-0x3fe080ff]
  [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 
0x3fe08100-0x3fe0817f]
  [0.714611] pci 0001:02:01.0: BAR 13: no space for [io  size 0x1000]
  [0.714613] pci 0001:02:01.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714614] pci 0001:02:08.0: BAR 13: no space for [io  size 0x1000]
  [0.714616] pci 0001:02:08.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714618] pci 0001:02:09.0: BAR 13: no space for [io  size 0x1000]
  [0.714619] pci 0001:02:09.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714622] pci 0001:03:00.0: BAR 6: assigned [mem 
0x3fe08000-0x3fe08003 pref]
  [0.714624] pci 0001:03:00.1: BAR 6: assigned [mem 
0x3fe08004-0x3fe08007 pref]
  [0.714627] pci 0001:03:00.0: BAR 2: assigned [mem 
0x3fe08008-0x3fe080083fff 64bit]
  [0.714641] pci 0001:03:00.1: BAR 2: assigned [mem 
0x3fe080084000-0x3fe080087fff 64bit]
  [0.714656] pci 0001:03:00.0: BAR 0: assigned [mem 
0x3fe080088000-0x3fe080088fff 64bit]
  [0.714670] pci 0001:03:00.1: BAR 0: assigned [mem 
0x3fe080089000-0x3fe080089fff 64bit]
  [0.714685] pci 0001:03:00.0: BAR 4: no space for [io  size 0x0100]
  [0.714686] pci 0001:03:00.0: BAR 4: failed to assign [io  size 0x0100]
  [0.714688] pci 0001:03:00.1: BAR 4: no space for [io  size 0x0100]
  [0.714690] pci 0001:03:00.1: BAR 4: failed to assign [io  size 0x0100]
  [0.714691] pci 0001:02:01.0: PCI bridge to [bus 03]

  # lspci 
  :00:00.0 PCI bridge: IBM Device 03dc
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:03:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0003:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:01.0 PCI bridge: PLX 

[Kernel-packages] [Bug 1426216] Re: pci driver messages - BAR 13: no space for

[Luix Carlos Maciel Franco]

I have a Dell G7 7588

This is related to usb controllers post/resume

you can buy a hub, in my case typec model, so the error has gone

mouse and keyboard connected to the hub

one thing is that pen drive works without problem

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

Title:
  pci driver messages - BAR 13: no space for

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  pci driver messages - BAR 13: no space for 

  ---uname output---
  3.18.0-12-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
  Install Ubuntu 15.04 daily build running bare-metal
  After the installation following messages are seen in dmesg. 
  Not sure if these indicate a problem. Can some one look at these and confirm 
if this is problem or can be ignored ?

  Messages from dmesg log

  [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4
  [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit]
  [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit]
  [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe081ff]
  [0.714581] pci 0001:00:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0817f]
  [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 
0x3fe08180-0x3fe08183]
  [0.714595] pci 0001:01:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 
0x3b101000-0x3b101fff 64bit pref]
  [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 
0x3b102000-0x3b102fff 64bit pref]
  [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 
0x3b103000-0x3b103fff 64bit pref]
  [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0807f]
  [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 
0x3fe08080-0x3fe080ff]
  [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 
0x3fe08100-0x3fe0817f]
  [0.714611] pci 0001:02:01.0: BAR 13: no space for [io  size 0x1000]
  [0.714613] pci 0001:02:01.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714614] pci 0001:02:08.0: BAR 13: no space for [io  size 0x1000]
  [0.714616] pci 0001:02:08.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714618] pci 0001:02:09.0: BAR 13: no space for [io  size 0x1000]
  [0.714619] pci 0001:02:09.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714622] pci 0001:03:00.0: BAR 6: assigned [mem 
0x3fe08000-0x3fe08003 pref]
  [0.714624] pci 0001:03:00.1: BAR 6: assigned [mem 
0x3fe08004-0x3fe08007 pref]
  [0.714627] pci 0001:03:00.0: BAR 2: assigned [mem 
0x3fe08008-0x3fe080083fff 64bit]
  [0.714641] pci 0001:03:00.1: BAR 2: assigned [mem 
0x3fe080084000-0x3fe080087fff 64bit]
  [0.714656] pci 0001:03:00.0: BAR 0: assigned [mem 
0x3fe080088000-0x3fe080088fff 64bit]
  [0.714670] pci 0001:03:00.1: BAR 0: assigned [mem 
0x3fe080089000-0x3fe080089fff 64bit]
  [0.714685] pci 0001:03:00.0: BAR 4: no space for [io  size 0x0100]
  [0.714686] pci 0001:03:00.0: BAR 4: failed to assign [io  size 0x0100]
  [0.714688] pci 0001:03:00.1: BAR 4: no space for [io  size 0x0100]
  [0.714690] pci 0001:03:00.1: BAR 4: failed to assign [io  size 0x0100]
  [0.714691] pci 0001:02:01.0: PCI bridge to [bus 03]

  # lspci 
  :00:00.0 PCI bridge: IBM Device 03dc
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:03:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0003:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Seamus Ryan]

@juergh I may have (somewhat) found the trigger.

As previously noted, my internal clients have a static route to the remote 
wireguard networks via my raspberry pi. This is defined in my internal router 
(Unifi)
ie:
client > router > static route (10.241.0.0/24) to pi eth0 IP > pi > tunnel > VPS

If have disabled this route, so now none of my clients can send data over the 
tunnel. Only the Pi which is running the tunnel itself is able to communicate 
over said tunnel.
No crashes at all.

So, with this in mind, setup an internal client with a static route to
your wireguard network and start sending traffic to the remote site.
This should (hopefully) trigger the issue.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 

[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

[navycat]

On 20.10 release not fixed

[8.265780] blk_update_request: I/O error, dev sr0, sector 9180400 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[8.265817] attempt to access beyond end of device
[8.265819] sr0: rw=0, want=9180408, limit=9180400
[8.265820] Buffer I/O error on dev sr0, logical block 1147550, async page 
read
[   14.977657] sr 3:0:0:0: [sr0] tag#19 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE cmd_age=4s
[   14.977661] sr 3:0:0:0: [sr0] tag#19 Sense Key : Medium Error [current] 
[   14.977663] sr 3:0:0:0: [sr0] tag#19 Add. Sense: L-EC uncorrectable error
[   14.977667] sr 3:0:0:0: [sr0] tag#19 CDB: Read(10) 28 00 00 23 04 c0 00 00 
40 00

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

Title:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

  PIONEER BD-RW   BDR-205

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:11:53 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Henry Wertz]

"1) Do you actually have superflous key strokes, along with that which is 
logged in dmesg?"
Nope, totally asymptomatic.

"2) Could you please test the latest mainline kernel (now 5.9.1) and advise to 
the results?"
Here ya go.  I can attach entire dmesg if you want, but from 5.9.1 dmesg:
[  256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
[  256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known.
[  265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
[  265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known.

"3) Did you personally test this with your Inspiron 1545 in a prior version of 
Ubuntu"
No.  I don't think it started logging this (at least often enough to notice) 
until my battery went from holding like a minute or two of battery life to 
holding 0, which only happened in the last 2-4 weeks. 

Honestly, I'd be totally fine if it was closed "wontfix" (I guess
launchpad doesn't have that) or "invalid", the kernel's logging a non-
standard keystroke sent by the Dell, which seems legitimate and harmless
(it'd be a nuisance if it was every second but it's not close to that);
in addition the Dell is effectively sending it in response to a hardware
failure, so I could see "if you don't want this in your kernel log,
replace your battery" being a legitimate response. Let me know and I'll
set it!

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my Dell Inspiron 1545 dmesg, I get:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This will be like 2-10 seconds apart, then it could be 5 minutes or
  more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kernel.

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled

[navycat]

On 20.10 release not fixed

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

Title:
  EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is
  disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but 
ECC is disabled
  [4.589410] EDAC sbridge: Couldn't find mci handler
  [4.589411] EDAC sbridge: Failed to register device with error -19.

  but x79 doesn't have ecc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:19:05 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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

[Kernel-packages] [Bug 1898912] Re: ath3k: probe of 2-1.3:1.0 failed with error -110

[navycat]

Fixed on 20.10 release

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

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

Title:
  ath3k: probe of 2-1.3:1.0 failed with error -110

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Bluetooth AR3011 doesn't work in 20.10 but works in 20.04

  dmesg.log
  [   10.300282] Bluetooth: Can't change to loading configuration err
  [   10.300332] ath3k: probe of 2-1.3:1.0 failed with error -110
  [   10.300424] usbcore: registered new interface driver ath3k

  
  lsusb | grep Blue
  0cf3:3002 Qualcomm Atheros Communications AR3011 Bluetooth

  blueman-manager
  error: No adapter(s) found

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat1983 F pulseaudio
   /dev/snd/controlC0:  navycat1983 F pulseaudio
   /dev/snd/controlC1:  navycat1983 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 20:08:25 2020
  InstallationDate: Installed on 2020-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run mythtv on Ubuntu 20.04 and I used a custom remote control keymap
  in /etc/rc_keymaps to correctly map buttons on my IR remote.  The
  above kernel seems to break custom keymap loading for my remote
  (certain buttons no longer work in mythtv).  Reverting to kernel
  5.4.0-48 corrects the problem.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  linux-image-5.4.0-52-generic:
Installed: 5.4.0-52.57
Candidate: 5.4.0-52.57
Version table:
   *** 5.4.0-52.57 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  belongs to the linux source package

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  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.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pdaniel1552 F pulseaudio
   /dev/snd/controlC0:  pdaniel1552 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Oct 22 16:16:58 2020
  InstallationDate: Installed on 2017-04-17 (1284 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7792
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=38b7dfb0-9848-4919-890b-fdc027e936f1 ro radeon.dpm=0 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: Upgraded to focal on 2020-05-11 (164 days ago)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FM2-A75IA-E53 (MS-7792)
  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.:bvrV2.4:bd02/12/2015:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7792
  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://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions

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

[Kernel-packages] [Bug 1899721] Re: Dell XPS 9300 stops responding

[Skpr]

I'm still getting lock ups. See attached dmesg using:

journalctl -b -1 --no-hostname -k > ~/dmesg.txt

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

Title:
  Dell XPS 9300 stops responding

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on a new Dell XPS 13 9300 a few weeks ago and
  have been experiencing a number of hangs, where keyboard and mouse
  stop responding, requiring a reboot.

  I have two LG 27" monitors connected, one of which acts as a usb hub
  for an external apple keyboard and trackpad.

  I've attached a journal from the last boot that crashed using

journalctl -b -1 --no-hostname -k > dmesg.txt

  Any help would be appreciated.

  Regards,

  Kim

  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:  kim3083 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 14 13:36:34 2020
  InstallationDate: Installed on 2020-09-16 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 13 9300
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=17be153f-3281-48bf-86c6-7d4af7253015 ro quiet splash pci=noaer 
mitigations=off vt.handoff=7
  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: 08/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0WX9VX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd08/13/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1901089] [NEW] Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

[pdaniel]

Public bug reported:

I run mythtv on Ubuntu 20.04 and I used a custom remote control keymap
in /etc/rc_keymaps to correctly map buttons on my IR remote.  The above
kernel seems to break custom keymap loading for my remote (certain
buttons no longer work in mythtv).  Reverting to kernel 5.4.0-48
corrects the problem.

Description:Ubuntu 20.04.1 LTS
Release:20.04

linux-image-5.4.0-52-generic:
  Installed: 5.4.0-52.57
  Candidate: 5.4.0-52.57
  Version table:
 *** 5.4.0-52.57 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status

belongs to the linux source package

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-52-generic 5.4.0-52.57
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.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pdaniel1552 F pulseaudio
 /dev/snd/controlC0:  pdaniel1552 F pulseaudio
CasperMD5CheckResult: skip
Date: Thu Oct 22 16:16:58 2020
InstallationDate: Installed on 2017-04-17 (1284 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7792
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=38b7dfb0-9848-4919-890b-fdc027e936f1 ro radeon.dpm=0 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: Upgraded to focal on 2020-05-11 (164 days ago)
dmi.bios.date: 02/12/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FM2-A75IA-E53 (MS-7792)
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.:bvrV2.4:bd02/12/2015:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7792
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug focal

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

Status in linux package in Ubuntu:
  New

Bug description:
  I run mythtv on Ubuntu 20.04 and I used a custom remote control keymap
  in /etc/rc_keymaps to correctly map buttons on my IR remote.  The
  above kernel seems to break custom keymap loading for my remote
  (certain buttons no longer work in mythtv).  Reverting to kernel
  5.4.0-48 corrects the problem.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  linux-image-5.4.0-52-generic:
Installed: 5.4.0-52.57
Candidate: 5.4.0-52.57
Version table:
   *** 5.4.0-52.57 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  belongs to the linux source package

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  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.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pdaniel1552 F pulseaudio
   /dev/snd/controlC0:  pdaniel1552 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Oct 22 16:16:58 2020
  InstallationDate: Installed on 2017-04-17 (1284 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7792
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=38b7dfb0-9848-4919-890b-fdc027e936f1 ro radeon.dpm=0 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:
   

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Christopher M . Peñalver]

Henry Wertz, please answer all of the following:

1) Do you actually have superflous key strokes, along with that which is
logged in dmesg?

2) Could you please test the latest mainline kernel (now 5.9.1) and
advise to the results?

3) Did you personally test this with your Inspiron 1545 in a prior
version of Ubuntu (not someone else, somewhere else)? If so, what is the
earliest version and what were the results?

** Tags added: latest-bios-a14

** Description changed:

- I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
+ On my Dell Inspiron 1545 dmesg, I get:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  
- This pair will be like 2-10 seconds apart, then it could be 5 minutes or
- more between pairs.
+ This will be like 2-10 seconds apart, then it could be 5 minutes or more
+ between pairs.
  
  I've been running 5.7.19 kernel (installed via mainline), but did boot
- 5.4.0-52-generic to file this since it's a supported kerenl (I seriously
- doubted it would make a difference since this has apparently been logged
- since at least the 2.6.x kernel series, and it didn't.)
- 
- I consider this bug pretty minor to possibly invalid; these keystroke
- messages spam up the kernel log a little but not too badly (since I'm
- not getting them every second like the original poster in #549741, but
- rather getting one, getting another a few seconds later, then it may be
- 5 minutes or more before I get another pair of them a few seconds
- apart.).
+ 5.4.0-52-generic to file this since it's a supported kernel.
  
  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
- (near network manager, volume, etc.) I think it sends this 0x8d each
- time the battery status changes.  Not sure what the point of the 0x8d
- is, but it's harmless for Linux to ignore, it's well aware of the status
- changes via ACPI anyway.
+ (near network manager, volume, etc.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
  
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  hwertz 3637 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
-  
+ 
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
-  TERM=screen.xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=screen.xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-52-generic N/A
-  linux-backports-modules-5.4.0-52-generic  N/A
-  linux-firmware1.173.19
+  linux-restricted-modules-5.4.0-52-generic N/A
+  linux-backports-modules-5.4.0-52-generic  N/A
+  linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell 

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

[Henry Wertz]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1901083/+attachment/5425627/+files/Lspci.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425636/+files/WifiSyslog.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/1901083

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425629/+files/ProcCpuinfo.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Henry Wertz]

(uname -a:
Linux inspiron-1545.local 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 
14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
)

I've been using 5.7.19 by default, but I'm on 5.4.0-52-generic for this
since it's a supported kernel.  (These atkbd messages are identical in
both.)

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1901083/+attachment/5425624/+files/CRDA.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1901083/+attachment/5425628/+files/Lsusb.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425632/+files/ProcModules.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425631/+files/ProcInterrupts.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1901083/+attachment/5425634/+files/RfKill.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425625/+files/CurrentDmesg.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1901083/+attachment/5425635/+files/UdevDb.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425633/+files/PulseList.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425626/+files/IwConfig.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

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

[Henry Wertz]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1901083/+attachment/5425630/+files/ProcCpuinfoMinimal.txt

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Henry Wertz]

apport information

** Tags added: apport-collected staging

** Description changed:

  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  
  This pair will be like 2-10 seconds apart, then it could be 5 minutes or
  more between pairs.
  
  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I seriously
  doubted it would make a difference since this has apparently been logged
  since at least the 2.6.x kernel series, and it didn't.)
  
  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may be
  5 minutes or more before I get another pair of them a few seconds
  apart.).
  
  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the status
  changes via ACPI anyway.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
  
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.18
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  hwertz 3637 F pulseaudio
+ CurrentDesktop: GNOME-Flashback:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-09-09 (774 days ago)
+ InstallationMedia:
+  
+ MachineType: Dell Inc. Inspiron 1545
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=screen.xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
+ ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-52-generic N/A
+  linux-backports-modules-5.4.0-52-generic  N/A
+  linux-firmware1.173.19
+ StagingDrivers: ashmem_linux
+ Tags:  bionic staging
+ Uname: Linux 5.4.0-52-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
+ _MarkForUpload: True
+ dmi.bios.date: 12/07/2009
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A14
+ dmi.board.name: 0G848F
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
+ dmi.product.name: Inspiron 1545
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on 

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Henry Wertz]

** Description changed:

  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  
  This pair will be like 2-10 seconds apart, then it could be 5 minutes or
  more between pairs.
  
  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I seriously
  doubted it would make a difference since this has apparently been logged
  since at least the 2.6.x kernel series, and it didn't.)
  
  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may be
  5 minutes or more before I get another pair of them a few seconds
  apart.).
  
  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
- time the battery status changes.
+ time the battery status changes.  Not sure what the point of the 0x8d
+ is, but it's harmless for Linux to ignore, it's well aware of the status
+ changes via ACPI anyway.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
-  
+ 
  ProcEnviron:
-  TERM=screen.xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=screen.xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  In dmesg, I get a pair like:
+ I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  
  This pair will be like 2-10 seconds apart, then it could be 5 minutes or
  more between pairs.
  
  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I seriously
  doubted it would make a difference since this has apparently been logged
  since at least the 2.6.x kernel series, and it didn't.)
  
  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may be
  5 minutes or more before I get another pair of them a few seconds
  apart.).
  
  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the status
  changes via ACPI anyway.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Christopher M . Peñalver]

Henry Wertz, thank you for reporting this and helping make Ubuntu
better.

Could you please boot into a Ubuntu kernel (not third party kernel) and execute 
the following command only once, as it will automatically gather debugging 
information, in a terminal:
apport-collect 1901083

** Package changed: linux-signed-hwe-5.4 (Ubuntu) => linux (Ubuntu)

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1895202] Re: touchpad suddenly not detected, appearing as PS/2 mouse in devices

[Allen Gooch]

This problem persists with Ubuntu 20.10 released today.

The modprobe/rmmod/modprobe method above still works there, however it
is very inconvenient to have to perform those steps after each reboot.
Unfortunate, as Ubuntu has been the distro that I've used and
recommended to others for the last four years based on "it just works".

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

Title:
  touchpad suddenly not detected, appearing as PS/2 mouse in devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can't even recall making any upgrades. Lenovo X1 Extreme.

~ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics TM3418-002id=12   [slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=9[slave  
keyboard (3)]
  ↳ AT Raw Set 2 keyboard   id=10   [slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=11   [slave  
keyboard (3)]
  ➜  ~ cat /var/log/Xorg.0.log | grep -i synaptics
  [12.190] (II) config/udev: Adding input device Synaptics TM3418-002 
(/dev/input/event7)
  [12.190] (**) Synaptics TM3418-002: Applying InputClass "libinput 
touchpad catchall"
  [12.190] (II) Using input driver 'libinput' for 'Synaptics TM3418-002'
  [12.190] (**) Synaptics TM3418-002: always reports core events
  [12.192] (II) event7  - Synaptics TM3418-002: is tagged by udev as: 
Touchpad
  [12.193] (II) event7  - Synaptics TM3418-002: device is a touchpad
  [12.194] (II) event7  - Synaptics TM3418-002: device removed
  [12.194] (II) XINPUT: Adding extended input device "Synaptics TM3418-002" 
(type: TOUCHPAD, id 12)
  [12.194] (**) Synaptics TM3418-002: (accel) selected scheme none/0
  [12.194] (**) Synaptics TM3418-002: (accel) acceleration factor: 2.000
  [12.194] (**) Synaptics TM3418-002: (accel) acceleration threshold: 4
  [12.195] (II) event7  - Synaptics TM3418-002: is tagged by udev as: 
Touchpad
  [12.195] (II) event7  - Synaptics TM3418-002: device is a touchpad
  [12.196] (II) config/udev: Adding input device Synaptics TM3418-002 
(/dev/input/mouse0)
  [34.235] (II) event7  - Synaptics TM3418-002: device removed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-47-generic 5.4.0-47.51
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ole2093 F pulseaudio
   /dev/snd/controlC0:  ole2093 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 10 21:45:53 2020
  InstallationDate: Installed on 2019-03-30 (530 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=37b4f683-cd0d-4eb9-b05a-973790230aa4 ro i8042.reset quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-47-generic N/A
   linux-backports-modules-5.4.0-47-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET48W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET48W(1.30):bd05/15/2020:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1901083] [NEW] Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  In dmesg, I get a pair like:
[  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
[  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known.
[  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
[  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known.

This pair will be like 2-10 seconds apart, then it could be 5 minutes or
more between pairs.

I've been running 5.7.19 kernel (installed via mainline), but did boot
5.4.0-52-generic to file this since it's a supported kerenl (I seriously
doubted it would make a difference since this has apparently been logged
since at least the 2.6.x kernel series, and it didn't.)

I consider this bug pretty minor to possibly invalid; these keystroke
messages spam up the kernel log a little but not too badly (since I'm
not getting them every second like the original poster in #549741, but
rather getting one, getting another a few seconds later, then it may be
5 minutes or more before I get another pair of them a few seconds
apart.).

My battery packed up quite a while ago and shows 0% charge.. it has
begun every so often "dropping off" and back on a few seconds later,
both in gkrellm, and whatever app shows the battery icon in top right
(near network manager, volume, etc.) I think it sends this 0x8d each
time the battery status changes.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
Date: Thu Oct 22 15:13:25 2020
InstallationDate: Installed on 2018-09-09 (774 days ago)
InstallationMedia:
 
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
https://bugs.launchpad.net/bugs/1901083
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 1003309] Re: Boot fails after installing updates, error: “cryptsetup: evms_activate is not available"

[Guilherme G. Piccoli]

This is a somewhat old LP bug, but for completeness it worth mentioning here 
that recently some patches were merged on initramfs-tools and cryptsetup, that 
allow a good experience booting with LUKS-encrypted rootfs on top of a degraded 
RAID1 array; for details, please check: 
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980
(this is specially in response to comment #70, from phi-phong-nguyen).
Cheers,


Guilherme

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

Title:
  Boot fails after installing updates, error: “cryptsetup: evms_activate
  is not available"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run 12.04 LTS on a virtualbox image. I use LUKS and LVM for whole
  disk encryption.

  After installing recent kernel updates, my system no longer boots. It
  says: "cryptsetup: evms_activate is not available" when it would
  normally ask for passphrase.

  If I boot the previous kernel, I do not get this error.

  This appears to be a bug in the new kernel package?

  Until this is fixed, is there any workaround that will let me boot my
  system with the new kernel?

  
  More info:
  Maybe this issue is related to this bug: 
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/957602 ?
  However, this is a much more recent kernel.

  This kernel works: 3.2.0-23-generic, while this one fails:
  3.2.0-24-generic

  
  I have tried doing this:
  sudo su -
  cd /boot/grub
  update-initramfs -u
  update-grub
  reboot

  This did not solve the issue.


  
  It seems that the new kernel does not include evms support, while the older 
kernel does.
  Is this something that has been officially removed from the Ubuntu provided 
kernel? If so, why? I am pretty sure this breaks a lot of Ubuntu deployments 
using LUKS and dmcrypt.


  My /etc/fstab is available here:
  http://p.adora.dk/P2400.html

  My /etc/crypttab is available here:
  http://p.adora.dk/P2401.html
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 
82801AA-ICH]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tdn2056 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 21'
 Mixer name : 'SigmaTel STAC9700,83,84'
 Components : 'AC97a:83847600'
 Controls  : 34
 Simple ctrls  : 24
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=f1d46fd3-d40c-43e3-b4a3-74fa5f699952
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_DK:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_DK.UTF-8
   SHELL=/bin/zsh
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic 
root=/dev/mapper/barbera-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  Tags:  precise precise
  Uname: Linux 3.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin photo plugdev sambashare sudo users 
video
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled

[Ian]

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

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

Title:
  bcache: Issues with large IO wait in bch_mca_scan() when shrinker is
  enabled

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1898786

  [Impact]

  Systems that utilise bcache can experience extremely high IO wait
  times when under constant IO pressure. The IO wait times seem to stay
  at a consistent 1 second, and never drop as long as the bcache
  shrinker is enabled.

  If you disable the shrinker, then IO wait drops significantly to
  normal levels.

  We did some perf analysis, and it seems we spend a huge amount of time
  in bch_mca_scan(), likely waiting for the mutex ">bucket_lock".

  Looking at the recent commits in Bionic, we found the following commit
  merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through
  upstream stable:

  commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b
  Author: Coly Li 
  Date: Wed Nov 13 16:03:24 2019 +0800
  Subject: bcache: at least try to shrink 1 node in bch_mca_scan()
  Link: 
https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b

  It mentions in the description that:

  > If sc->nr_to_scan is smaller than c->btree_pages, after the above
  > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is
  > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make
  > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring
  > and releasing mutex c->bucket_lock.

  This seems to be what is going on here, but the above commit only
  addresses when nr is 0.

  From what I can see, the problems we are experiencing are when nr is 1
  or 2, and again, we just waste time in bch_mca_scan() waiting on
  c->bucket_lock, only to release c->bucket_lock since the shrinker loop
  never executes since there is no work to do.

  [Fix]

  The following commits fix the problem, and all landed in 5.6-rc1:

  commit 125d98edd11464c8e0ec9eaaba7d682d0f832686
  Author: Coly Li 
  Date: Fri Jan 24 01:01:40 2020 +0800
  Subject: bcache: remove member accessed from struct btree
  Link: 
https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686

  commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795
  Author: Coly Li 
  Date: Fri Jan 24 01:01:41 2020 +0800
  Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan()
  Link: 
https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795

  commit e3de04469a49ee09c89e80bf821508df458ccee6
  Author: Coly Li 
  Date: Fri Jan 24 01:01:42 2020 +0800
  Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan()
  Link: 
https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6

  The first commit is a dependency of the other two. The first commit
  removes a "recently accessed" marker, used to indicate if a particular
  cache has been used recently, and if it has been, not consider it for
  cache eviction. The commit mentions that under heavy IO, all caches
  will end up being recently accessed, and nothing will ever be shrunk.

  The second commit changes a previous design decision of skipping the
  first 3 caches to shrink, since it is a common case to call
  bch_mca_scan() with nr being 1, or 2, just like 0 was common in the
  very first commit I mentioned. This time, if we land on 1 or 2, the
  loop exits and nothing happens, and we waste time waiting on locks,
  just like the very first commit I mentioned. The fix is to try shrink
  caches from the tail of the list, and not the beginning.

  The third commit fixes a minor issue where we don't want to re-arrange
  the linked list c->btree_cache, which is what the second commit ended
  up doing, and instead, just shrink the cache at the end of the linked
  list, and not change the order.

  One minor backport / context adjustment was required in the first
  commit for Bionic, and the rest are all clean cherry picks to Bionic
  and Focal.

  [Testcase]

  This is kind of hard to test, since the problem shows up in production
  environments that are under constant IO pressure, with many different
  items entering and leaving the cache.

  The Launchpad git server is currently suffering this issue, and has
  been sitting at a constant IO wait of 1 second / slightly over 1
  second which was causing slow response times, which was leading to
  build failures when git clones ended up timing out.

  We installed a test kernel, which is available in the following PPA:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf294907-test

  Once the test kernel had been installed, IO wait times with the
  

[Kernel-packages] [Bug 1900910] Re: [nouveau] Screen freeze after closing lid and suspend

[Chelmite]

I'm (sort of) happy that I can use my computer again.

If this project is active, then change the status of this bug to
something appropriate, and I'll support you.

Philosophically, I'd prefer to be running an open-source version of the
software, but I need to get stuff done in the meantime.

Installing the proprietary version is a workaround. (Which has its own
problems...after awakening from Suspend, screen icon text is illegible.)

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

Title:
  [nouveau] Screen freeze after closing lid and suspend

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I 
get only a black screen (and the power light is on) when I open the laptop lid.
  I tried various 3-finger salutes, and nothing changes. There is no cursor. I 
cannot get to the console screens. The only thing that works is holding the 
power button until the laptop shuts off.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44
  Uname: Linux 5.4.0-7642-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 21 14:25:22 2020
  DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703]
  InstallationDate: Installed on 2017-11-01 (1085 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic 
root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash 
snd_hda_intel.probe_mask=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10RSA1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Serval WS
  dmi.product.sku: Not Applicable
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login

[Eduard Hasenleithner]

Which is the tracking issue for the required focal (20.04) kernel update
to fix this bug?

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

Title:
  Showing two cursors after login

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Showing two cursors after login to ubuntu-desktop.

  One cursor moves and is scaled, and one is stationary mid screen and
  not scaled.

  The moving cursor does not appear on screenshots, making it difficult
  to upload a screenshot.

  Previously reported:
  https://gitlab.gnome.org/GNOME/mutter/issues/904
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428

  Package: mutter 3.36.1-3ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 20:06:53 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions

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

[Kernel-packages] [Bug 1900847] Re: Fix non-working Intel NVMe after S3

[Ian]

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

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

Title:
  Fix non-working Intel NVMe after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
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:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact] 
  Intel NVMe has a 10% chance to stop working after S3.

  [Fix]
  Enable ACS quirk on Intel CML root port.

  [Test]
  With the patch applied, Intel NVMe mostly works after S3. There's still a
  1/1000 chance the issue happens. Intel is investigating the root cause.

  [Regression Potential]
  ACS works at hardware level, so I can't really assess the risk of
  regression. Since Intel confirmed CML also needs ACS quirk, we can only
  trust them until they devise a real fix.

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

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

[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled

[Ian]

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

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

Title:
  bcache: Issues with large IO wait in bch_mca_scan() when shrinker is
  enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1898786

  [Impact]

  Systems that utilise bcache can experience extremely high IO wait
  times when under constant IO pressure. The IO wait times seem to stay
  at a consistent 1 second, and never drop as long as the bcache
  shrinker is enabled.

  If you disable the shrinker, then IO wait drops significantly to
  normal levels.

  We did some perf analysis, and it seems we spend a huge amount of time
  in bch_mca_scan(), likely waiting for the mutex ">bucket_lock".

  Looking at the recent commits in Bionic, we found the following commit
  merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through
  upstream stable:

  commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b
  Author: Coly Li 
  Date: Wed Nov 13 16:03:24 2019 +0800
  Subject: bcache: at least try to shrink 1 node in bch_mca_scan()
  Link: 
https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b

  It mentions in the description that:

  > If sc->nr_to_scan is smaller than c->btree_pages, after the above
  > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is
  > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make
  > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring
  > and releasing mutex c->bucket_lock.

  This seems to be what is going on here, but the above commit only
  addresses when nr is 0.

  From what I can see, the problems we are experiencing are when nr is 1
  or 2, and again, we just waste time in bch_mca_scan() waiting on
  c->bucket_lock, only to release c->bucket_lock since the shrinker loop
  never executes since there is no work to do.

  [Fix]

  The following commits fix the problem, and all landed in 5.6-rc1:

  commit 125d98edd11464c8e0ec9eaaba7d682d0f832686
  Author: Coly Li 
  Date: Fri Jan 24 01:01:40 2020 +0800
  Subject: bcache: remove member accessed from struct btree
  Link: 
https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686

  commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795
  Author: Coly Li 
  Date: Fri Jan 24 01:01:41 2020 +0800
  Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan()
  Link: 
https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795

  commit e3de04469a49ee09c89e80bf821508df458ccee6
  Author: Coly Li 
  Date: Fri Jan 24 01:01:42 2020 +0800
  Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan()
  Link: 
https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6

  The first commit is a dependency of the other two. The first commit
  removes a "recently accessed" marker, used to indicate if a particular
  cache has been used recently, and if it has been, not consider it for
  cache eviction. The commit mentions that under heavy IO, all caches
  will end up being recently accessed, and nothing will ever be shrunk.

  The second commit changes a previous design decision of skipping the
  first 3 caches to shrink, since it is a common case to call
  bch_mca_scan() with nr being 1, or 2, just like 0 was common in the
  very first commit I mentioned. This time, if we land on 1 or 2, the
  loop exits and nothing happens, and we waste time waiting on locks,
  just like the very first commit I mentioned. The fix is to try shrink
  caches from the tail of the list, and not the beginning.

  The third commit fixes a minor issue where we don't want to re-arrange
  the linked list c->btree_cache, which is what the second commit ended
  up doing, and instead, just shrink the cache at the end of the linked
  list, and not change the order.

  One minor backport / context adjustment was required in the first
  commit for Bionic, and the rest are all clean cherry picks to Bionic
  and Focal.

  [Testcase]

  This is kind of hard to test, since the problem shows up in production
  environments that are under constant IO pressure, with many different
  items entering and leaving the cache.

  The Launchpad git server is currently suffering this issue, and has
  been sitting at a constant IO wait of 1 second / slightly over 1
  second which was causing slow response times, which was leading to
  build failures when git clones ended up timing out.

  We installed a test kernel, which is available in the following PPA:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf294907-test

  Once the test kernel had been installed, IO wait times with the
  

[Kernel-packages] [Bug 1899582] Re: ceph: fix inode number handling on arches with 32-bit ino_t

[Ian]

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

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

Title:
  ceph: fix inode number handling on arches with 32-bit ino_t

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * A problem occurs with 32-bit ino_t values on 64-bit architectures
  (like s390x).

  * Without this patch, cephfs kernel client does not work properly on
  s390x: the initial symtom is missing the first created file/directory
  on cephfs mount point as reported in
  https://tracker.ceph.com/issues/46828.

  [Fix]

  * cherry-pick for groovy: ebce3eb2f7ef9f6ef01a60874ebd232450107c9a
  ebce3eb2f7ef "ceph: fix inode number handling on arches with 32-bit
  ino_t"

  * backport for focal: https://launchpadlibrarian.net/501822049/0001
  -ceph-fix-inode-number-handling-on-arches-with-32-bit.patch

  [Test Case]

  * IBM Development team and Test team have carried out simple testing
  and stress testing by automatically creating many Ceph clusters on
  s390x (with different configuration each time), doing the cephfs
  kernel mounting, checking inode numbers, running stress tests. The
  same procedures were done on x86_64 arch by Test team.

  [Regression Potential]

  * There is a certain regression risk with this patch, since:

  * common ceph filesystem code in fs/ceph/ is modified

  * the inode handling is touched

  * ceph is used for supplemental volumes

  * and as the original author of this patch (Jeff Layton) wrote in the
  commit message, the potential issue might happen on 32-bit arches only
  and he also provided workaround for those arches.

  [Other]

  * The above patch/commit was upstream accepted with kernel 5.9.

  * Cherry picking the patch/commit to groovy works fine, hence this
  SRU.

  * For focal a cherry pick does not apply cleanly, hence a backport got
  added to LP 1899582.

  __

  Backport provided for git-commit to 20.04 kernel.

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

  Backport patch attached for commit ebce3eb upstream.

  It was applied and tested on top of Ubuntu commit :

  linux (5.4.0-48.52) focal; urgency=medium

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

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

[Kernel-packages] [Bug 1899726] Re: Fix system reboot when disconnecting WiFi

[Ian]

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

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

Title:
  Fix system reboot when disconnecting WiFi

Status in HWE Next:
  New
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:
  [Impact] 
  Hardware triggrs reboot when disconnecting WiFi connection. 

  [Fix]
  There's a DMA bug in Intel WiFi 9000 needs to be limits to 6 RX queue
  max.

  [Test]
  With the patch applied, a 1000 times of connect/disconnect loop doesn't
  bring the system down.

  [Regression Potential]
  Not that I can think of. Hypothetically reducing RX queue rings will
  reduce the RX speed, but the wireless transfter is a lot slower then DMA
  operation, so we won't see any difference.

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

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

[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd

[Ian]

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

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

Title:
  Improve descriptions for XFAIL cases in kselftests/net/psock_snd

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
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:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  == SRU Justification ==
  The test output in psock_snd.sh is confusing sometimes. Here is an output 
example:
    raw csum_off with bad offset (fails)
    ./psock_snd: write: Invalid argument

  The first line is the test case description, and the second is the test 
execution output.
  It feels like this test has failed, but it has passed instead.
  The "fails" here means this test is expected to fail. But you will have to 
check the source code to know this fact.

  == Fix ==
  * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in 
psock_snd.sh

  Change "fails" in the test case description to "expected to fail", so
  that the test output can be more understandable.

  This test case exists after Bionic, and it can be cherry-picked.

  == Regression Potential ==
  Low, minor changes for test case description only.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1901024

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

Title:
  Crash on startup using linux 5.8.0-25

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 20.04 on my new Lenovo ThinkPad L15 and upgraded it to 
Ubuntu 20.10 for a newer kernel to fix minor compatibility issues with AMD 
Renoir.
  When using the newer kernel it freezes before splash. I did my best to follow 
instructions to create a crash file but none were ever created.
  Booting to recovery mode with 5.8 works, 5.4 kernel works. Booting from USB 
the (safe graphics) option works but not the default. On that USB I have latest 
available daily build (Oct 21 2020) of 20.10. I tried a fresh reinstall of 
Ubuntu 20.10 and still getting stuck.

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

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

[Kernel-packages] [Bug 1901024] Re: Crash on startup using linux 5.8.0-25

[Rauno]

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

Title:
  Crash on startup using linux 5.8.0-25

Status in linux package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 20.04 on my new Lenovo ThinkPad L15 and upgraded it to 
Ubuntu 20.10 for a newer kernel to fix minor compatibility issues with AMD 
Renoir.
  When using the newer kernel it freezes before splash. I did my best to follow 
instructions to create a crash file but none were ever created.
  Booting to recovery mode with 5.8 works, 5.4 kernel works. Booting from USB 
the (safe graphics) option works but not the default. On that USB I have latest 
available daily build (Oct 21 2020) of 20.10. I tried a fresh reinstall of 
Ubuntu 20.10 and still getting stuck.

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

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

[Kernel-packages] [Bug 1901024] [NEW] Crash on startup using linux 5.8.0-25

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I installed Ubuntu 20.04 on my new Lenovo ThinkPad L15 and upgraded it to 
Ubuntu 20.10 for a newer kernel to fix minor compatibility issues with AMD 
Renoir.
When using the newer kernel it freezes before splash. I did my best to follow 
instructions to create a crash file but none were ever created.
Booting to recovery mode with 5.8 works, 5.4 kernel works. Booting from USB the 
(safe graphics) option works but not the default. On that USB I have latest 
available daily build (Oct 21 2020) of 20.10. I tried a fresh reinstall of 
Ubuntu 20.10 and still getting stuck.

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


** Tags: bot-comment groovy
-- 
Crash on startup using linux 5.8.0-25
https://bugs.launchpad.net/bugs/1901024
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 1897464] Re: Problems with disk size with zfs

[Colin Ian King]

So we have multiple levels of information here.

If you have 64GB of "drive space" I believe you are referring to the
partition size. If one allocates a whole pool to this then some of the
space is used as overhead to make the pool.  This includes labelling,
alignment usage, metaslab allocation overhead, slop space reservations
and other sundries. For example, a 1000 GiB disk with just a single pool
may end up with ~960 GiB of usable pool space [ see
https://wintelguy.com/2017/zfs-storage-overhead.html and
https://wintelguy.com/zfs-calc.pl ]

Next you have zfs file systems inside the pool. Again there is some
overhead for this.

Secondly, the file system stats that are shown by the desktop are most
probably not ZFS aware and probably just use the generic statvfs()
family of system calls to get file system sizes. This probably won't
show the correct free space as ZFS can't properly represent this data
over these with these older system calls because we may have compression
on and dedup that can skew the stats.  The only real way to figure out
the disc size and free space with zfs is with zpool list.

Note also that zpool list shows the size in GiB (Gibibytes) based on 1K
= 1024.  The GUI disk tool shows the size in GB (Gigabytes) based on 1K
= 1000.  Hence zpool list size will appear also to be smaller. Use zpool
list -p to show the sizes in bytes.


** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Problems with disk size with zfs

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  I created a VM that has 64GB of hard drive space and I used zfs during
  install.

  Now here is what I see via desktop GUI:
  Disks => 69 GB
  Computer => 23.6 GB

  Two pools:
  zpool list
  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
  bpool  1.88G   427M  1.46G- - 0%22%  1.00xONLINE  
-
  rpool59G  38.7G  20.3G- -36%65%  1.00xONLINE  
-

  
  As a result I run out of space.

  So I am confused, why is my disk size only 23.6 GB ?

  Definitely seems like a bug in how Computer shows the disk size.

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

-- 
Mailing list: https://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 1899678] Re: No wifi after installation - does not work with secure boot enabled

[Steve Langasek]

On Thu, Oct 22, 2020 at 08:35:48AM -, fossfreedom wrote:
> modinfo wl returns a sig_key signature

Ok, but is that value also in the output of mokutil --list-enrolled?  You
didn't say.

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

Title:
  No wifi after installation - does not work with secure boot enabled

Status in bcmwl package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  After installation I noted that my broadcom wifi was not available.
  This is a regression from 20.04 where installation automatically
  installed the broadcom driver.

  So I tried to force the installation again - see trace below.

  The dialog message to enter the secure password appeared - however on
  reboot a confirmation to change the MOK state was not seen - the
  distro booted straight in.

  sudo apt install --reinstall bcmwl-kernel-source 
  [sudo] password for dad: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to 
upgrade.
  Need to get 1,546 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 
bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB]
  Fetched 1,546 kB in 0s (5,232 kB/s)   
  (Reading database ... 202371 files and directories currently installed.)
  Preparing to unpack 
.../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ...
  Removing all DKMS Modules
  Done.
  Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over 
(6.30.223.271+bdcom-0ubuntu7) ...
  Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ...
  Loading new bcmwl-6.30.223.271+bdcom DKMS files...
  Building for 5.8.0-22-generic
  Building for architecture x86_64
  Building initial module for 5.8.0-22-generic
  Done.

  wl.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/

  depmod

  DKMS: install completed.
  modprobe: ERROR: could not insert 'wl': Operation not permitted
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct 13 18:32:47 2020
  InstallationDate: Installed on 2020-10-13 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 
(20201013)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[bugproxy]

--- Comment From stefan.haberl...@de.ibm.com 2020-10-22 11:52 EDT---
*** Bug 188223 has been marked as a duplicate of this bug. ***

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

Title:
  dasd_fba io error and kernel panic

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released

Bug description:
  Generated I/O errors every hour in syslog and caused kernel panic with 
workloads running
   
  ---uname output---
  Linux ubuntutest01 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC 
2020 s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  distro provided. up-to-date from Ubuntu18.04.
   
  Machine Type = z15 
   
  ---System Hang---
   The hourly generated I/O errors didn't impact the system up and running. 
When there are workloads on it, it will cause kernel panic and rebooted the 
server. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   After migrated from 16.04 to 18.04, will see the i/o errors. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Device driver error code:
   [52297.898232] dasd.5c0c98: 0.0.0100: default ERP has run out of retries and 
failed
  [52297.898244] dasd(fba): I/O status report for device 0.0.0100:
 dasd(fba): in req: 2e142bcd CS: 0x20 DS: 0x0C
 dasd(fba): device 0.0.0100: Failing CCW: a84f6c9f
 dasd(fba): SORRY - NO VALID SENSE AVAILABLE
  [52297.898255] dasd(fba): Related CP in req: 2e142bcd
 dasd(fba): CCW d15f44d3: 63400010 7FE2BBA0 DAT: 
0200 008150F2  0017
 dasd(fba): CCW b09ad76e: 4348 7FE2BBB0 DAT: 
0506 
 dasd(fba): CCW c44dfb20: 41600C00 F360 DAT: 
       
 dasd(fba): CCW a84f6c9f: 4348 7FE2BBB8 DAT: 
0510 0006
 dasd(fba): CCW 22dac88c: 4160  DAT:
 dasd(fba): CCW 69686544: 4348 7FE2BBC0 DAT: 
0502 0016
 dasd(fba): CCW 7bb6a17c: 41200400 F360 DAT: 
       
  [52297.898278] print_req_error: I/O error, dev dasda, sector 8474866
   
  *Additional Instructions for y...@cn.ibm.com: 
  -Attach sysctl -a output output to the bug.

  [reply] [?]
  Internal Only
  Comment 1 QI YE 2020-03-12 02:29:20 CDT

  The z/VM version 6.4

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

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

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

[Christopher M . Peñalver]

Philippe Coval, one thing that would be helpful is if you could make a
short video from a cell phone of the computer screen right before the
problem begins, as it starts ,and little bit as it is happening. This
helps developers root cause the issue better.

** Tags added: eoan

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Executenor]

@Javier Ah ok that makes sense, i hope it is really fixed with ubuntu
20.10 then it could be used with the a new hwe for ubuntu 20.04.

-- 
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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

[Brian Murray]

** Changed in: ubuntu-release-notes
   Status: New => Invalid

-- 
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 Committed
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 1900854] Re: radeon: GPU lockup when restarting a video on RV730

[Philippe Coval]

1)
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/192


2) It is also occurs on 19.10, 
I don't remember any working setup, 
may I try under windows 10
or could it be a hardware problem ?


Extra info, displaying videos in firefox is not causing any issue,
I suspect it uses different acceleration.


** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues 
#192
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/192

** Changed in: linux
   Importance: Undecided => Unknown

** Changed in: linux
   Status: New => Unknown

** Changed in: linux
 Remote watch: None => 
gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues #192

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1893504] Re: System froze

[Paolo Menezes Carrara]

If there is any other info that I can provide please just ask.

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

Title:
  System froze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After of about 8 to 12 hours of use the system simply freezes.
  No mouse or keyboard response. Even video playing on the page stops 
responding.
  There is nothing special to be done to cause the problem, sometimes the 
system freezes at idle sometimes, sometimes it freezes while I'm using it.

  Hardware:
  CPU: Ryzen Threadripper 3970x
  Memory: 128GB Corsair Vengeance LPX
  Motherboard: Asus Zenith Extreme 2
  NVMe: SSD Samsung 970 EVO Plus 1TB, M.2 NVMe

  System:
  Ubuntu 5.4.0-42.46-generic 5.4.44

  lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pcarrara   2332 F pulseaudio
   /dev/snd/controlC1:  pcarrara   2332 F pulseaudio
   /dev/snd/controlC0:  pcarrara   2332 F pulseaudio
   /dev/snd/pcmC0D7p:   pcarrara   2332 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 29 02:07:36 2020
  InstallationDate: Installed on 2020-08-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=9e72229e-3b67-433e-94f7-4cb8f323faeb ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx: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/1893504/+subscriptions

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

[Kernel-packages] [Bug 1893504] Re: System froze

[Paolo Menezes Carrara]

Hi, sorry the late response.

So, I installed Ubuntu 20.04.1 LTS.
Updated the kernel to the 5.9.0.
The system froze at 4 days and 10 hours.

uname -a
Linux hell 5.9.0-050900rc3-generic #202008302030 SMP Mon Aug 31 00:36:25 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

last
pcarrara :1   :1   Sun Oct 18 01:34 - crash (4+10:24)

The syslog was:
Oct 22 11:54:34 hell tracker-store[1039548]: OK
Oct 22 11:54:34 hell systemd[2501]: tracker-store.service: Succeeded.
Oct 22 11:55:02 hell dbus-daemon[2514]: [session uid=1000 pid=2514] Activating 
via systemd: service name='org.freedesktop.Tracker1' 
unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=2511 
comm="/usr/libexec/tracker-miner-fs ")
Oct 22 11:55:02 hell systemd[2501]: Starting Tracker metadata database store 
and lookup manager...
Oct 22 11:55:02 hell dbus-daemon[2514]: [session uid=1000 pid=2514] 
Successfully activated service 'org.freedesktop.Tracker1'
Oct 22 11:55:02 hell systemd[2501]: Started Tracker metadata database store and 
lookup manager.
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Oct
 22 11:58:44 hell systemd-modules-load[831]: Inserted module 'lp'
Oct 22 11:58:44 hell systemd-modules-load[831]: Inserted module 'ppdev'
Oct 22 11:58:44 hell systemd-modules-load[831]: Inserted module 'parport_pc'
Oct 22 11:58:44 hell systemd-sysctl[851]: Not setting 
net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Oct 22 11:58:44 hell systemd-sysctl[851]: Not setting 
net/ipv4/conf/default/promote_secondaries (explicit setting exists).
Oct 22 11:58:44 hell systemd[1]: Starting Flush Journal to Persistent Storage...

The logs after the "..." are fron the restart process (hard reset).

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

Title:
  System froze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After of about 8 to 12 hours of use the system simply freezes.
  No mouse or keyboard response. Even video playing on the page stops 
responding.
  There is nothing special to be done to cause the problem, sometimes the 
system freezes at idle sometimes, sometimes it freezes while I'm using it.

  Hardware:
  CPU: Ryzen Threadripper 3970x
  Memory: 128GB Corsair Vengeance LPX
  Motherboard: Asus Zenith Extreme 2
  NVMe: SSD Samsung 970 EVO Plus 1TB, M.2 NVMe

  System:
  Ubuntu 5.4.0-42.46-generic 5.4.44

  lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pcarrara   2332 F pulseaudio
   /dev/snd/controlC1:  pcarrara   2332 F pulseaudio
   /dev/snd/controlC0:  pcarrara   2332 F pulseaudio
   /dev/snd/pcmC0D7p:   pcarrara   2332 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 29 02:07:36 2020
  InstallationDate: Installed on 2020-08-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=9e72229e-3b67-433e-94f7-4cb8f323faeb ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx: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/1893504/+subscriptions

-- 
Mailing list: 

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

[Bill (franksmcb)]

This is confirmed working correctly on Ubuntu MATE with 20201022 re-
spin.

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
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 1025388] Re: Internal mic stops working when plugging in headphones

[O Gopal]

For a fix that worked for me, see
https://askubuntu.com/questions/1218136/internal-microphone-doesnt-work-
when-using-headphones/1285982#1285982.

The fix:

 1. Run

  sudo apt install alsa-tools-gui

  hdajackretask

 2. Select the appropriate sound card up top in Select a codec.

 3. Then make the Black Mic (headphone jack) override Not connected.

 4. Lower right corner, select Install boot override.

 5. Then reboot and test.

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

Title:
  Internal mic stops working when plugging in headphones

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

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

[Francesco Guarneri]

> sudo update-initramfs -u

This is what I was missing. Thank you so much!

-- 
You 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:
  New
Status in linux package in Ubuntu:
  Confirmed
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:
  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)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug

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

[fossfreedom]

I can confirm that sound is no longer muted for the ISO and is not muted on
installation.

So thanks and congrats!

On Thu, 22 Oct 2020, 14:30 Launchpad Bug Tracker, <
1897...@bugs.launchpad.net> wrote:

> This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3
>
> ---
> alsa-lib (1.2.3.2-1ubuntu3) groovy; 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 16:46:14 +0800
>
> ** Changed in: alsa-lib (Ubuntu Groovy)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
>   New
> Status in alsa-lib package in Ubuntu:
>   Fix Released
> Status in alsa-lib source package in Focal:
>   Fix Committed
> 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
>

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
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 

[Kernel-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

[O Gopal]

Same issue as #22 etc. Ubuntu 20.04. Lenovo X1 Carbon, 5th generation.
When I plug in earphones that have no microphone, the internal
microphone no longer works.

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

Title:
  Internal mic stops working when plugging in headphones

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1897464] Re: Problems with disk size with zfs

[Colin Ian King]

** Summary changed:

- Problmes with disk size with zfs
+ Problems with disk size with zfs

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

Title:
  Problems with disk size with zfs

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I created a VM that has 64GB of hard drive space and I used zfs during
  install.

  Now here is what I see via desktop GUI:
  Disks => 69 GB
  Computer => 23.6 GB

  Two pools:
  zpool list
  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
  bpool  1.88G   427M  1.46G- - 0%22%  1.00xONLINE  
-
  rpool59G  38.7G  20.3G- -36%65%  1.00xONLINE  
-

  
  As a result I run out of space.

  So I am confused, why is my disk size only 23.6 GB ?

  Definitely seems like a bug in how Computer shows the disk size.

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

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

[Kernel-packages] [Bug 1852116] Re: zfs send / recv properties failing

[Colin Ian King]

This bug has not been responded to from comment #1, so I'm marking this
bug as Won't Fix. If this is still and issue please re-open the bug and
we will re-visit this bug report.

** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  zfs send / recv properties failing

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  Running Ubuntu 19.10 on both the send and recv systems.

  I can't send properties. If I don't include the -p switch, all is
  good.

  If I include the -p switch it looks like it is going to work, but it
  hangs like this:

  sudo /usr/sbin/zfs send -vp -I tank/vm@2019-11-02_22-41-35__daily__batch1 
tank/vm@2019-11-05_18-26-01__daily__batch1 | /bin/ssh back1 sudo /usr/sbin/zfs 
recv -vu backup/vm
  send from @2019-11-02_22-41-35__daily__batch1 to 
tank/vm@2019-11-05_18-24-41__daily__batch1 estimated size is 4.12G
  send from @2019-11-05_18-24-41__daily__batch1 to 
tank/vm@2019-11-05_18-26-01__daily__batch1 estimated size is 2.50M
  total estimated size is 4.13G
  TIME SENT SNAPSHOT tank/vm@2019-11-05_18-24-41__daily__batch1
  receiving incremental stream of tank/vm@2019-11-05_18-24-41__daily__batch1 
into backup/vm@2019-11-05_18-24-41__daily__batch1
  20:03:24 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:25 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:26 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:27 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:28 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:29 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:30 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1

  Then I have to kill it.

  Any thoughts?
  thanks,
  Geoff

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Seamus Ryan]

RE IPv6, there is some manual config.

I have each vlan/network assigned a /64. On my pi's they get an address
in that /64 (different networks for eth0 and wlan0) but they do have a
static assignment as well (should have included that earlier:

interface eth0
metric 300
static ip6_address=2403:::XXX0::11/64
static ip6_routers=2403:::XXX0::1
static ip_address=192.168.200.11/24
static routers=192.168.200.1


interface wlan0
metric 400
static ip6_address=2403:::XXX3::11/64
static ip6_routers=2403:::XXX3::1
static ip_address=192.168.209.11/24
static routers=192.168.209.1

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Seamus Ryan]

So exactly what type of payload triggers the issues, that i cant work
out.

I know the traffic profile, vast majority of it is monitoring related as my VPS 
is running grafana/influx and my internal clients are sending data over this 
tunnel using telegraf.
There is also a fair bit of ICMP etc traffic, so all "monitoring" related.

For a bit of clarity, my Pi essentially acts as an internal router to link to 
my VPS. 
So clients send traffic originating from 192.168.x.x to 192.168.200.11 
(internal static routes) to reach the 10.241.0.x network.

Will ping you offline to see if I can provide a level of access to
troubleshoot in real time.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 

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

[Von]

Hi Francesco

I have the same laptop with Ubuntu installed and I am using #211 patch
too. It works for me after running:

$ sudo rmmod i2c_hid
$ sudo insmod /path/to/i2c-hid.ko polling_mode=1
$ sudo cp /path/to/i2c-hid.ko /lib/modules/$(uname 
-r)/kernel/drivers/hid/i2c-hid/i2c-hid.ko
$ sudo depmod

then append i2c_hid.polling_mode=1 to kernel commandline

  use a text editor to open /etc/default/grub as root, then change the line
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i2c_hid.polling_mode=1"
  ,finally save the changes

then run:

$ sudo update-grub2
$ sudo update-initramfs -u

reboot the laptop and everything shall be fine

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
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:
  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)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: 

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Juerg Haefliger]

@seamoose Thanks. That's pretty much the config that I had. I've now setup an 
external VM and created a wireguard tunnel from my Pi 3B+ but it still won't 
fail running iperf3. Is there a specific payload that you're transferring? 
Also, your IPv6 config, is that just the default or did you do some manual 
configuration? On my Pi:
$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether b8:27:eb:3e:ab:fb brd ff:ff:ff:ff:ff:ff
inet 192.168.99.67/24 brd 192.168.99.255 scope global dynamic eth0
   valid_lft 860949sec preferred_lft 860949sec
inet6 fe80::ba27:ebff:fe3e:abfb/64 scope link 
   valid_lft forever preferred_lft forever
3: wlan0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether b8:27:eb:6b:fe:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.99.57/24 brd 192.168.99.255 scope global dynamic wlan0
   valid_lft 860949sec preferred_lft 860949sec
inet6 fe80::ba27:ebff:fe6b:feae/64 scope link 
   valid_lft forever preferred_lft forever
4: wg0:  mtu 1420 qdisc noqueue state UNKNOWN 
group default qlen 1000
link/none 
inet 10.241.0.1/24 scope global wg0
   valid_lft forever preferred_lft forever


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

** No longer affects: linux-raspi (Ubuntu Eoan)

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

** No longer affects: linux-raspi2 (Ubuntu Focal)

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

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27: 

[Kernel-packages] [Bug 1897751] Re: Introduce the new NVIDIA 455 series

[Alberto Milone]

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

** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
   Status: New => In Progress

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

Title:
  Introduce the new NVIDIA 455 series

Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  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]

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  rtl8723ae wireless card doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  rtl8723ae wireless card is detected with included kernel module and it
  loads without errors, but it doesn't detect or show any available
  wireless network.
  
/lib/modules/5.4.0-52-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/rtl8723ae.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-extra-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/controlC1:  roberto1515 F pulseaudio
   /dev/snd/controlC0:  roberto1515 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 22 09:14:29 2020
  InstallationDate: Installed on 2020-08-31 (51 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ' ' ' '
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/DISCO-ROOT 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)
  WifiSyslog:
   
  dmi.bios.date: 07/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1492IIA.20I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1492
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ' '
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1492IIA.20I:bd07/01/2014:svn'':pn'':pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvn'':ct10:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ' '
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV:1.0
  dmi.sys.vendor: ' '

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3

---
alsa-lib (1.2.3.2-1ubuntu3) groovy; 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 16:46:14 +0800

** Changed in: alsa-lib (Ubuntu Groovy)
   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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
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 1901025] [NEW] rtl8723ae wireless card doesn't work

[Roberto De Oliveira]

Public bug reported:

rtl8723ae wireless card is detected with included kernel module and it
loads without errors, but it doesn't detect or show any available
wireless network.
/lib/modules/5.4.0-52-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/rtl8723ae.ko

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-modules-extra-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/controlC1:  roberto1515 F pulseaudio
 /dev/snd/controlC0:  roberto1515 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 22 09:14:29 2020
InstallationDate: Installed on 2020-08-31 (51 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ' ' ' '
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/DISCO-ROOT 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)
WifiSyslog:
 
dmi.bios.date: 07/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1492IIA.20I
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1492
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ' '
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1492IIA.20I:bd07/01/2014:svn'':pn'':pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvn'':ct10:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: ' '
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: REV:1.0
dmi.sys.vendor: ' '

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  rtl8723ae wireless card doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  rtl8723ae wireless card is detected with included kernel module and it
  loads without errors, but it doesn't detect or show any available
  wireless network.
  
/lib/modules/5.4.0-52-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/rtl8723ae.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-extra-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/controlC1:  roberto1515 F pulseaudio
   /dev/snd/controlC0:  roberto1515 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 22 09:14:29 2020
  InstallationDate: Installed on 2020-08-31 (51 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ' ' ' '
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/DISCO-ROOT 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)
  WifiSyslog:
   
  dmi.bios.date: 07/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1492IIA.20I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1492
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ' '
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1492IIA.20I:bd07/01/2014:svn'':pn'':pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvn'':ct10:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ' '
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV:1.0
  dmi.sys.vendor: ' '

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

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

[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab

[Alex]

Seems a same bug on Ubuntu 20.04 kernel 5.4.0-52. The bug reproduces for me 
only under high load of CPU(for example, java compilation process)
-
[10798.058030] bpfilter: Loaded bpfilter_umh pid 17193
[10798.058119] Started bpfilter
[14269.588116] BUG: unable to handle page fault for address: 919d84135500
[14269.588119] #PF: supervisor read access in kernel mode
[14269.588119] #PF: error_code(0x) - not-present page
[14269.588120] PGD 1f4c01067 P4D 1f4c01067 PUD 0 
[14269.588122] Oops:  [#1] SMP NOPTI
[14269.588123] CPU: 5 PID: 21991 Comm: Chrome_ChildIOT Kdump: loaded Not 
tainted 5.4.0-52-generic #57-Ubuntu
[14269.588123] Hardware name: Gigabyte Technology Co., Ltd. B365M D3H/B365M 
D3H-CF, BIOS F3c 11/28/2019
[14269.588126] RIP: 0010:lock_page_memcg+0x1f/0x90
[14269.588127] Code: 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00 00 55 48 89 
e5 41 55 41 54 53 0f 1f 44 00 00 48 89 fb 4c 8b 67 38 4d 85 e4 74 36 <41> 8b 84 
24 00 05 00 00 85 c0 7e 2d 4d 8d ac 24 b8 04 00 00 4c 89
[14269.588128] RSP: 0018:b6ca43047bc8 EFLAGS: 00010286
[14269.588129] RAX: eaf69e86afc0 RBX: eaf69e86afc0 RCX: 8005
[14269.588129] RDX:  RSI:  RDI: eaf69e86afc0
[14269.588130] RBP: b6ca43047be0 R08: eaf69e86afc0 R09: 
[14269.588130] R10: 0001 R11: 91bdaf7d5000 R12: 919d84135000
[14269.588131] R13: 55986f674000 R14: 8007a1abf005 R15: 55986f675000
[14269.588132] FS:  7f7768299700() GS:91bd8f34() 
knlGS:
[14269.588132] CS:  0010 DS:  ES:  CR0: 80050033
[14269.588133] CR2: 919d84135500 CR3: 0001f420a002 CR4: 003606e0
[14269.588134] DR0:  DR1:  DR2: 
[14269.588134] DR3:  DR6: fffe0ff0 DR7: 0400
[14269.588134] Call Trace:
[14269.588137]  page_remove_rmap+0xa5/0x310
[14269.588139]  ? tlb_flush_mmu+0x3a/0x140
[14269.588140]  zap_pte_range.isra.0+0x273/0x7f0
[14269.588141]  unmap_page_range+0x2da/0x4a0
[14269.588142]  unmap_single_vma+0x7f/0xf0
[14269.588143]  unmap_vmas+0x79/0xf0
[14269.588144]  exit_mmap+0xb4/0x1b0
[14269.588146]  mmput+0x5d/0x130
[14269.588147]  do_exit+0x306/0xac0
[14269.588148]  __x64_sys_exit+0x1b/0x20
[14269.588150]  do_syscall_64+0x57/0x190
[14269.588152]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[14269.588153] RIP: 0033:0x559870c0bee5
[14269.588155] Code: Bad RIP value.
[14269.588155] RSP: 002b:7f77682979a0 EFLAGS: 0246 ORIG_RAX: 
003c
[14269.588156] RAX: ffda RBX:  RCX: 559870c0bee5
[14269.588156] RDX: 0001 RSI: 0009 RDI: 
[14269.588157] RBP: 7f7768297d20 R08: 008c R09: 000e
[14269.588157] R10:  R11: 0246 R12: 7f7768297d30
[14269.588158] R13:  R14: 0003 R15: 
[14269.588159] Modules linked in: xt_tcpudp xt_state xt_conntrack nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter ip6_tables 
iptable_filter bpfilter cpuid snd_hda_codec_hdmi intel_rapl_msr 
intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio mei_hdcp 
snd_hda_intel crct10dif_pclmul snd_intel_dspcfg ghash_clmulni_intel aesni_intel 
crypto_simd cryptd snd_hda_codec glue_helper rapl snd_hda_core intel_cstate 
snd_usb_audio snd_usbmidi_lib snd_hwdep mc snd_pcm nls_iso8859_1 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq wmi_bmof i915 snd_seq_device snd_timer 
input_leds snd joydev soundcore drm_kms_helper i2c_algo_bit mei_me fb_sys_fops 
mei syscopyarea sysfillrect sysimgblt acpi_pad mac_hid acpi_tad sch_fq_codel 
parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid 
hid crc32_pclmul nvme e1000e nvme_core i2c_i801 ahci libahci wmi video
[14269.588179] CR2: 919d84135500

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

Title:
  Regression on NFS: unable to handle page fault in mempool_alloc_slab

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

Bug description:
  On kernel 5.4.0-40-generic in focal I'm getting errors like this on
  several machines with different hardware in the first hour after boot:

  Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for 
address: 9083e222e632
  Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode
  Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page
  Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0
  Jul 04 16:58:32 hostname kernel: Oops:  [#1] SMP NOPTI
  Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: 
G  

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

[Ubuntu Kernel Bot]

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

apport-collect 1900927

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

Title:
   Affinity broken due to vector space exhaustion.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HW AS-2123BT-HTR AMD EPYC 7351

  is stable with 18.04 but when we did an update for security the we have this 
error.
   

  No Issues with this Ubuntu 18.04 Linux efsql4 4.15.0-46-generic #49-Ubuntu 
SMP Wed Feb 6 09:33:07 UTC 
  2019 x86_64 x86_64 x86_64 GNU/Linux
   
   
  We are seeing the following error  with this kernel after the update.
  Linux incwosql1 4.15.0-118-generic #119-Ubuntu SMP Tue Sep 8 12:30:01 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
   
   
  [  337.056983] irq 99: Affinity broken due to vector space exhaustion.
  [  337.056993] irq 100: Affinity broken due to vector space exhaustion.
  [  337.057001] irq 101: Affinity broken due to vector space exhaustion.
  [  337.057008] irq 102: Affinity broken due to vector space exhaustion.
  [  337.057035] irq 107: Affinity broken due to vector space exhaustion.
  [  337.057073] irq 114: Affinity broken due to vector space exhaustion.
  [  337.057080] irq 115: Affinity broken due to vector space exhaustion.
  [  337.057097] irq 118: Affinity broken due to vector space exhaustion.
  [  337.057103] irq 119: Affinity broken due to vector space exhaustion.
  [  337.057115] irq 121: Affinity broken due to vector space exhaustion.
  [  337.057121] irq 122: Affinity broken due to vector space exhaustion.
  [  337.057128] irq 123: Affinity broken due to vector space exhaustion.
  [  337.057156] irq 128: Affinity broken due to vector space exhaustion.

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

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

[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages

[Christopher M . Peñalver]

Henry Wertz (hwertz10), as this report is closed, it will help immensely if you 
use Ubuntu with the computer the problem is reproducible with and file a new 
report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  [Dell Latitude 131L] keyboard not recognized properly; logs fill up
  with messages

Status in linux package in Ubuntu:
  Invalid

Bug description:
  hi

  Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips),
  updated twice a day at the moment.

  Linux seems not to recognize the keyboard in my laptop well. Starting early 
in the boot process (well before X kicks in) I see error messages on the 
screen. The same messages then swamp the logs. A sample:
  =
  [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on 
isa0060/serio0).
  [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on 
isa0060/serio0).
  [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on 
isa0060/serio0).
  [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  =
  This goes on every second until shut down.

  It's been there for a while now, but I haven't made -or found- a bug report 
about it yet. I did some googling and it seems related to not-so-standard 
handling of hotkeys (which you would find on a laptop) by the bios. However, I 
have not found a solution.
  It is possible to 'shut up' the messages by assigning e00d to an unused 
keycode, but that is just hiding the symptom. Also that kills the screen saver 
/ blackout and it breaks my repeating keys, so not an option really.

  WORKAROUND: - shutdown the pc
  - Remove both battery and AC
  - push the 'on' switch several times
  - Plug the battery and AC back in

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1529 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16'
     Mixer name : 'SigmaTel STAC9200'
     Components : 'HDA:14f12bfa,14f100c3,0009 
HDA:83847690,102801f6,00102201'
     Controls  : 6
     Simple ctrls  : 4
  CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  MachineType: Dell Inc. Latitude 131L
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic 
root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Regression: No
  RelatedPackageVersions: linux-firmware 1.33
  Reproducible: Yes
  Tags: lucid
  TestedUpstream: Yes
  Uname: Linux 2.6.32-17-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 05/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.1
  dmi.board.name: 0PM607??
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Latitude 131L
  dmi.product.version: Not Specified
  

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

[Christopher M . Peñalver]

** Attachment added: "pinball-table-gnu-pincab-2020-rzr-9J5CHTFWnTc.mp4"
   
https://bugs.launchpad.net/linux/+bug/1900854/+attachment/5425486/+files/pinball-table-gnu-pincab-2020-rzr-9J5CHTFWnTc.mp4

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

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

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

[Christopher M . Peñalver]

Philippe Coval, could you please address all of the following:

1) In order for upstream to help you, could you please make a net new
bug report (not link a report you didn't make) via
https://gitlab.freedesktop.org/xorg/driver/xf86-video-
ati/-/issues/new?issue%5Bassignee_id%5D=%5Bmilestone_id%5D= ? Once
done, please advise on the URL.

2) To confirm, did this issue not occur in Ubuntu 19.10 before you
upgraded?

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

** Changed in: linux
   Importance: Unknown => Undecided

** Changed in: linux
   Status: Unknown => New

** Changed in: linux
 Remote watch: gitlab.freedesktop.org/drm/amd/-/issues #630 => None

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

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

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1900927] Re: Affinity broken due to vector space exhaustion.

[Paul White]

** Package changed: ubuntu => linux (Ubuntu)

** Tags added: bionic

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

Title:
   Affinity broken due to vector space exhaustion.

Status in linux package in Ubuntu:
  New

Bug description:
  HW AS-2123BT-HTR AMD EPYC 7351

  is stable with 18.04 but when we did an update for security the we have this 
error.
   

  No Issues with this Ubuntu 18.04 Linux efsql4 4.15.0-46-generic #49-Ubuntu 
SMP Wed Feb 6 09:33:07 UTC 
  2019 x86_64 x86_64 x86_64 GNU/Linux
   
   
  We are seeing the following error  with this kernel after the update.
  Linux incwosql1 4.15.0-118-generic #119-Ubuntu SMP Tue Sep 8 12:30:01 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
   
   
  [  337.056983] irq 99: Affinity broken due to vector space exhaustion.
  [  337.056993] irq 100: Affinity broken due to vector space exhaustion.
  [  337.057001] irq 101: Affinity broken due to vector space exhaustion.
  [  337.057008] irq 102: Affinity broken due to vector space exhaustion.
  [  337.057035] irq 107: Affinity broken due to vector space exhaustion.
  [  337.057073] irq 114: Affinity broken due to vector space exhaustion.
  [  337.057080] irq 115: Affinity broken due to vector space exhaustion.
  [  337.057097] irq 118: Affinity broken due to vector space exhaustion.
  [  337.057103] irq 119: Affinity broken due to vector space exhaustion.
  [  337.057115] irq 121: Affinity broken due to vector space exhaustion.
  [  337.057121] irq 122: Affinity broken due to vector space exhaustion.
  [  337.057128] irq 123: Affinity broken due to vector space exhaustion.
  [  337.057156] irq 128: Affinity broken due to vector space exhaustion.

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

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

[Kernel-packages] [Bug 1900927] [NEW] Affinity broken due to vector space exhaustion.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

HW AS-2123BT-HTR AMD EPYC 7351

is stable with 18.04 but when we did an update for security the we have this 
error.
 

No Issues with this Ubuntu 18.04 Linux efsql4 4.15.0-46-generic #49-Ubuntu SMP 
Wed Feb 6 09:33:07 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
 
 
We are seeing the following error  with this kernel after the update.
Linux incwosql1 4.15.0-118-generic #119-Ubuntu SMP Tue Sep 8 12:30:01 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
 
 
[  337.056983] irq 99: Affinity broken due to vector space exhaustion.
[  337.056993] irq 100: Affinity broken due to vector space exhaustion.
[  337.057001] irq 101: Affinity broken due to vector space exhaustion.
[  337.057008] irq 102: Affinity broken due to vector space exhaustion.
[  337.057035] irq 107: Affinity broken due to vector space exhaustion.
[  337.057073] irq 114: Affinity broken due to vector space exhaustion.
[  337.057080] irq 115: Affinity broken due to vector space exhaustion.
[  337.057097] irq 118: Affinity broken due to vector space exhaustion.
[  337.057103] irq 119: Affinity broken due to vector space exhaustion.
[  337.057115] irq 121: Affinity broken due to vector space exhaustion.
[  337.057121] irq 122: Affinity broken due to vector space exhaustion.
[  337.057128] irq 123: Affinity broken due to vector space exhaustion.
[  337.057156] irq 128: Affinity broken due to vector space exhaustion.

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


** Tags: bot-comment
-- 
 Affinity broken due to vector space exhaustion.
https://bugs.launchpad.net/bugs/1900927
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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

[Iain Lane]

ah I see, OK - I will upload, thanks!

can you update the test case to say that this version of alsa-utils is
needed please? maybe provide a PPA link for people to install it with,
until that is accepted into focal?

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

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed

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 1900854] Re: radeon: GPU lockup when restarting a video on RV730

[Christopher M . Peñalver]

** Description changed:

- Hi,
+ To reproduce type at a terminal or open with same file locally:
+ mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4
  
- I suspect there is an issue with radeon driver for video acceleration,
- I haven't investigated yet but I would investigate resources releases of VPU 
driver.
+ Stop the video by clicking Esc. Run again and the process will be stuck
+ on creating window frame for a while, then the video will start to show,
+ but the video's first frame looks like blinking in this triangle mess.
+ The system is still usable, and audio is still playing.
  
+ Log when issue occurred:
+ https://launchpadlibrarian.net/502954026/CurrentDmesg.txt
  
- As suggested on other (obsolete) bug:
- 
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130?comments=all
- 
- 
- I thought it was a VLC bug but actually it's also replicated using mpv:
- 
- Just run
- 
- mpv
- 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4
- 
- It appears to work as expected
- 
- Stop with Esc
- 
- and run again
- 
- Process will be stuck on creating window frame 
- and then once windows is starting to show the video,
- desktop's frame buffer will become garbage:
- 
- video's first frame looks like blicking in this triangle mess.
- 
- 
- system is still usable,
- audio is still playing.
- 
- I logged using ssh and reported details using:
- 
- ubuntu-bug linux
- 
- 
- I hope collected data is not mixed with my client's host.
- 
- I can give more details or test patches.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 20.10
- Package: linux-image-5.8.0-25-generic 5.8.0-25.26
- 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
- CasperMD5CheckResult: skip
- CurrentDmesg:
-  Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
-  Error executing command as another user: Not authorized
-  
-  This incident has been reported.
- Date: Wed Oct 21 16:02:27 2020
- IwConfig:
-  lono wireless extensions.
-  
-  enp2s0no wireless extensions.
-  
-  docker0   no wireless extensions.
- MachineType: Dell Inc. Precision T1500
- ProcEnviron:
-  TERM=screen.xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- ProcFB: 0 radeondrmfb
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
- RelatedPackageVersions:
-  linux-restricted-modules-5.8.0-25-generic N/A
-  linux-backports-modules-5.8.0-25-generic  N/A
-  linux-firmware1.190
- RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
- SourcePackage: linux
- UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
- acpidump:
-  Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: pam_authenticate failed: 
Authentication failure
-  Error executing command as another user: Not authorized
-  
-  This incident has been reported.
- dmi.bios.date: 01/13/2011
- dmi.bios.release: 8.15
- dmi.bios.vendor: Dell Inc.
- dmi.bios.version: 2.4.0
- dmi.board.name: 0XC7MM
- dmi.board.vendor: Dell Inc.
- dmi.board.version: A00
- dmi.chassis.type: 3
- dmi.chassis.vendor: Dell Inc.
- dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
- dmi.product.family: 0
- dmi.product.name: Precision T1500
- dmi.product.sku: 0
- dmi.product.version: 00
- dmi.sys.vendor: Dell Inc.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  rzr4431 F pulseaudio
-  /dev/snd/controlC1:  rzr4431 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rzr4431 F pulseaudio
+  /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
+  /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
-  lono wireless extensions.
-  
-  enp2s0no wireless extensions.
-  
-  docker0   no wireless extensions.
+  lono wireless extensions.
+ 
+  enp2s0no wireless extensions.
+ 
+  docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
-  

[Kernel-packages] [Bug 1900889] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000

[Colin Ian King]

I think this may be a race condition, in which case duplicating this
issue and testing a fix may be problematic.

I've created a potential fix and tested this against our internal
regression tests, so it may be worth tying this to see if the issue
occurs with the fix.

To try this out do the following:

sudo add-apt-repository ppa:colin-king/zfs-src-1900889
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install zfs-dkms

This will pull in the fixed version including the kernel ZFS driver -
the DKMS ZFS driver may take several minutes to build.  Once done, a
reboot is required.

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

Title:
  BUG: kernel NULL pointer dereference, address: 

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  While zfs send'ing from Bionic to Focal, my send/recv hung midway and
  I found this in the receiver's dmesg:

  BUG: kernel NULL pointer dereference, address: 
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x) - not-present page
  PGD 0 P4D 0 
  Oops:  [#1] SMP PTI
  CPU: 0 PID: 94310 Comm: receive_writer Tainted: P   O  
5.4.0-52-generic #57-Ubuntu
  Hardware name: System manufacturer System Product Name/C60M1-I, BIOS 0502 
05/22/2014
  RIP: 0010:abd_verify+0xa/0x40 [zfs]
  Code: ff 85 c0 74 12 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 00 5b 5d c3 e8 
04 ff ff ff eb e7 c3 90 55 48 89 e5 41 54 53 48 89 fb <8b> 3f e8 0f ff ff ff 85 
c0 75 22 44 8b 63 1c 48 8b 7b 20 4d 85 e4
  RSP: 0018:b797c555baa8 EFLAGS: 00010286
  RAX: 4000 RBX:  RCX: 
  RDX: 4000 RSI: 4000 RDI: 
  RBP: b797c555bab8 R08: 0253 R09: 
  R10: 953b56a17848 R11:  R12: 4000
  R13: 953ad201d280 R14: 4000 R15: 
  FS:  () GS:953b56a0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2:  CR3: 000151ab4000 CR4: 06f0
  Call Trace:
   abd_borrow_buf+0x19/0x60 [zfs]
   abd_borrow_buf_copy+0x1a/0x50 [zfs]
   zio_crypt_copy_dnode_bonus+0x30/0x130 [zfs]
   arc_buf_untransform_in_place.isra.0+0x2b/0x40 [zfs]
   arc_buf_fill+0x1f0/0x4a0 [zfs]
   arc_untransform+0x22/0x90 [zfs]
   dbuf_read_verify_dnode_crypt+0xed/0x160 [zfs]
   ? atomic_cmpxchg+0x16/0x30 [zfs]
   dbuf_read_impl+0x3ea/0x610 [zfs]
   dbuf_read+0xcb/0x5f0 [zfs]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? do_raw_spin_unlock+0x9/0x10 [zfs]
   ? __raw_spin_unlock+0x9/0x10 [zfs]
   dmu_bonus_hold_by_dnode+0x92/0x190 [zfs]
   receive_object+0x442/0xae0 [zfs]
   ? __list_del_entry.isra.0+0x22/0x30 [zfs]
   ? atomic_dec+0xd/0x20 [spl]
   receive_process_record+0x170/0x1c0 [zfs]
   receive_writer_thread+0x9a/0x150 [zfs]
   ? receive_process_record+0x1c0/0x1c0 [zfs]
   thread_generic_wrapper+0x83/0xa0 [spl]
   kthread+0x104/0x140
   ? clear_bit+0x20/0x20 [spl]
   ? kthread_park+0x90/0x90
   ret_from_fork+0x22/0x40
  Modules linked in: ip6table_filter ip6_tables xt_conntrack iptable_filter 
bpfilter zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) 
nls_iso8859_1 zlua(PO) eeepc_wmi asus_wmi sparse_keymap wmi_bmof video ccp 
radeon kvm r8169 realtek k10temp ttm i2c_piix4 drm_kms_helper i2c_algo_bit 
fb_sys_fops syscopyarea sysfillrect sysimgblt wmi sch_fq_codel nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 veth bridge 8021q garp mrp stp llc xt_tcpudp 
xt_owner xt_LOG nf_log_ipv6 nf_log_ipv4 nf_log_common drm ip_tables x_tables 
autofs4 btrfs libcrc32c xor zstd_compress raid6_pq hid_generic usbhid hid ahci 
libahci mac_hid
  CR2: 
  ---[ end trace 374aa76997d6bc9b ]---
  RIP: 0010:abd_verify+0xa/0x40 [zfs]
  Code: ff 85 c0 74 12 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 00 5b 5d c3 e8 
04 ff ff ff eb e7 c3 90 55 48 89 e5 41 54 53 48 89 fb <8b> 3f e8 0f ff ff ff 85 
c0 75 22 44 8b 63 1c 48 8b 7b 20 4d 85 e4
  RSP: 0018:b797c555baa8 EFLAGS: 00010286
  RAX: 4000 RBX:  RCX: 
  RDX: 4000 RSI: 4000 RDI: 
  RBP: b797c555bab8 R08: 0253 R09: 
  R10: 953b56a17848 R11:  R12: 4000
  R13: 953ad201d280 R14: 4000 R15: 
  FS:  () GS:953b56a0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2:  CR3: 000151ab4000 CR4: 06f0

  The receiving side uses ZFS native encryption and had the key manually
  loaded before sending/receiving. The sending side is unencrypted. The
  recv hung after 611MiB out of the 990.4 MB delta.

  
  Additional information:

  sending side is a laptop running Bionic:

  $ uname -a
  

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

[Christopher M . Peñalver]

** Tags removed: needs-upstream-testing
** Tags added: focal

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

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

[Francesco Guarneri]

Hi! Managed to reproduce the steps described in #211 (using the updated
archive provided in #217) and #212. The touchpad seems to be working
after running

$ sudo rmmod i2c-hid
$ sudo insmod full-path/i2c-hid.ko polling_mode=1

I need to provide the full path to the i2c-hid.ko module, otherwise the system 
returns "could not load module "i2c-hid.ko: No such file or directory"; not 
sure if this is already an issue.
However, I am not sure how to add the boot parameter to GRUB. I followed this 
(https://wiki.ubuntu.com/Kernel/KernelBootParameters) and tried adding either 
one of these three options:

i2c-hid.polling_mode=1
full-path/i2c-hid.polling_mode=1
full-path/i2c-hid.ko.polling_mode=1

but neither seems to be working. Am i doing something wrong? Using
Ubuntu 20.04.1 with kernel 5.8.16. Also, total noob and first time
writing here, so hopefully not causing issues.

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
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:
  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)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  

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

[Hui Wang]

@Iain,

For focal, after we merge this SRU:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1899745, we
will have this bug too. But for focal, the #1899745 will not be in the
iso, so users will not notice this problem. If we merge #1899745 to
20.04.2 iso, users will meet this bug.

So for focal, this fix is not very urgent, even we merge the #1899745,
it will not introduce this issue immediately.

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Incomplete
Status in alsa-lib source package in Groovy:
  Fix Committed

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 1900849] Re: kernel bug

[Jouni Mettala]

This is not a bug in ubuntu kernel. There is no need to collect
information for debugging kernel. This is rather support request or bug
in linux mint repository. So I am setting this to invalid.

You could try to find linux mint support channels.

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

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

Title:
  kernel bug

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  No more kernel updates since version: 4.15-115.
  Why ?

  Linux madjid-desktop 4.15.0-115-generic # 116-Ubuntu SMP Wed Aug 26
  14:04:49 UTC 2020 x86


  
  madjid@madjid-desktop:~$ sudo lspci -vnvn
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor DRAM Controller [8086:0150] (rev 09)
Subsystem: ASRock Incorporation Motherboard [1849:0150]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore
Kernel modules: ie31200_edac

  00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: ASRock Incorporation Xeon E3-1200 v2/3rd 
Gen Core processor PCI Express Root Port [1849:0151]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: fee04004  Data: 4021
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <256ns, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt+ ABWMgmt+
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete+, EqualizationPhase1+
 EqualizationPhase2+, EqualizationPhase3+, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   

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

[Sebastien Bacher]

(the upload got rejected since it was already uploaded by someone who
didn't bother updating the bug)

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Incomplete
Status in alsa-lib source package in Groovy:
  Fix Committed

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] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

[Iain Lane]

I don't see the same problem on the Focal ISO - do we need to fix this
in Focal?

** Changed in: alsa-lib (Ubuntu Focal)
   Status: In Progress => Incomplete

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Incomplete
Status in alsa-lib source package in Groovy:
  Fix Committed

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] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

[Sebastien Bacher]

Thanks Hui, I've sponsored the fix to G, let's see how it goes there

** Changed in: alsa-lib (Ubuntu Groovy)
   Status: In Progress => Fix Committed

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  Fix Committed

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