date:20201221

@Piotr Tomaszewski (nfm886) can confirm my touchpad is the MSFT0001:00
06CB:7F28. I booted kernel 5.10.1 into recovery and then resumed regular
boot and my touchpad 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/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

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

2020-12-21 Thread wangjun

all the changes are extract from the master branch of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git .

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

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

2020-12-21 Thread wangjun

on fedora 33,with kernel 5.10.2 , i use this patch ,then touchpad work!



diff -Narup a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
--- a/drivers/gpio/gpiolib-acpi.c   2020-12-14 06:41:30.0 +0800
+++ b/drivers/gpio/gpiolib-acpi.c   2020-12-22 14:31:53.078877803 +0800
@@ -205,6 +205,68 @@ static void acpi_gpiochip_request_irqs(s
acpi_gpiochip_request_irq(acpi_gpio, event);
 }
 
+static enum gpiod_flags
+acpi_gpio_to_gpiod_flags(const struct acpi_resource_gpio *agpio, int polarity)
+{
+   /* GpioInt() implies input configuration */
+   if (agpio->connection_type == ACPI_RESOURCE_GPIO_TYPE_INT)
+   return GPIOD_IN;
+
+   switch (agpio->io_restriction) {
+   case ACPI_IO_RESTRICT_INPUT:
+   return GPIOD_IN;
+   case ACPI_IO_RESTRICT_OUTPUT:
+   /*
+* ACPI GPIO resources don't contain an initial value for the
+* GPIO. Therefore we deduce that value from the pull field
+* and the polarity instead. If the pin is pulled up we assume
+* default to be high, if it is pulled down we assume default
+* to be low, otherwise we leave pin untouched. For active low
+* polarity values will be switched. See also
+* Documentation/firmware-guide/acpi/gpio-properties.rst.
+*/
+   switch (agpio->pin_config) {
+   case ACPI_PIN_CONFIG_PULLUP:
+   return polarity == GPIO_ACTIVE_LOW ? GPIOD_OUT_LOW : 
GPIOD_OUT_HIGH;
+   case ACPI_PIN_CONFIG_PULLDOWN:
+   return polarity == GPIO_ACTIVE_LOW ? GPIOD_OUT_HIGH : 
GPIOD_OUT_LOW;
+   default:
+   break;
+   }
+   break;
+   default:
+   break;
+   }
+
+   /*
+* Assume that the BIOS has configured the direction and pull
+* accordingly.
+*/
+   return GPIOD_ASIS;
+}
+
+static struct gpio_desc *acpi_request_own_gpiod(struct gpio_chip *chip,
+   struct acpi_resource_gpio 
*agpio,
+   unsigned int index,
+   const char *label)
+{
+   int polarity = GPIO_ACTIVE_HIGH;
+   enum gpiod_flags flags = acpi_gpio_to_gpiod_flags(agpio, polarity);
+   unsigned int pin = agpio->pin_table[index];
+   struct gpio_desc *desc;
+   int ret;
+
+   desc = gpiochip_request_own_desc(chip, pin, label, polarity, flags);
+   if (IS_ERR(desc))
+   return desc;
+
+   ret = gpio_set_debounce_timeout(desc, agpio->debounce_timeout);
+   if (ret)
+   gpiochip_free_own_desc(desc);
+
+   return ret ? ERR_PTR(ret) : desc;
+}
+
 static bool acpi_gpio_in_ignore_list(const char *controller_in, int pin_in)
 {
const char *controller, *pin_str;
@@ -290,8 +352,8 @@ static acpi_status acpi_gpiochip_alloc_e
if (!handler)
return AE_OK;
 
-   desc = gpiochip_request_own_desc(chip, pin, "ACPI:Event",
-GPIO_ACTIVE_HIGH, GPIOD_IN);
+   desc = acpi_request_own_gpiod(chip, agpio, 0, "ACPI:Event");
+
if (IS_ERR(desc)) {
dev_err(chip->parent,
"Failed to request GPIO for pin 0x%04X, err %ld\n",
@@ -526,39 +588,6 @@ static bool acpi_get_driver_gpio_data(st
return false;
 }
 
-static enum gpiod_flags
-acpi_gpio_to_gpiod_flags(const struct acpi_resource_gpio *agpio)
-{
-   switch (agpio->io_restriction) {
-   case ACPI_IO_RESTRICT_INPUT:
-   return GPIOD_IN;
-   case ACPI_IO_RESTRICT_OUTPUT:
-   /*
-* ACPI GPIO resources don't contain an initial value for the
-* GPIO. Therefore we deduce that value from the pull field
-* instead. If the pin is pulled up we assume default to be
-* high, if it is pulled down we assume default to be low,
-* otherwise we leave pin untouched.
-*/
-   switch (agpio->pin_config) {
-   case ACPI_PIN_CONFIG_PULLUP:
-   return GPIOD_OUT_HIGH;
-   case ACPI_PIN_CONFIG_PULLDOWN:
-   return GPIOD_OUT_LOW;
-   default:
-   break;
-   }
-   default:
-   break;
-   }
-
-   /*
-* Assume that the BIOS has configured the direction and pull
-* accordingly.
-*/
-   return GPIOD_ASIS;
-}
-
 static int
 __acpi_gpio_update_gpiod_flags(enum gpiod_flags *flags, enum gpiod_flags 
update)
 {
@@ -664,6 +693,7 @@ static int acpi_populate_gpio_lookup(str
lookup->desc = acpi_get_gpiod(agpio->resource_source.string_ptr,
  agpio->pin_table[pin_index]);

[Kernel-packages] [Bug 1908978] Re: ALSA: hda/realtek - Supported Dell fixed type headset

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

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

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

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

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

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

** Description changed:

  [Impact]
  Can't record sounds from external headset
  
  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
- The patch is provided by the realtek and is archived in the sound sub-system 
tree.
+ The patch is provided by the realtek and has been archived in the sound 
sub-system tree.
  Add "Dell Precision 3650 Tower" in the fix-up table.
  
  [Test Case]
  1. install manifest
  2. plug-in an external headset
  3. try to record sounds via external headset
  
  [Where problems could occur]
  Just add a supported device.

** Tags added: oem-priority originate-from-1904542 somerville

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

Title:
  ALSA: hda/realtek - Supported Dell fixed type headset

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]
  Can't record sounds from external headset

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
  The patch is provided by the realtek and has been archived in the sound 
sub-system tree.
  Add "Dell Precision 3650 Tower" in the fix-up table.

  [Test Case]
  1. install manifest
  2. plug-in an external headset
  3. try to record sounds via external headset

  [Where problems could occur]
  Just add a supported device.

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

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

[Kernel-packages] [Bug 1908978] Re: ALSA: hda/realtek - Supported Dell fixed type headset

** Summary changed:

- ALSA: usb-audio: Support ASUS PRIME TRX40 PRO-S
+ ALSA: hda/realtek - Supported Dell fixed type headset

** Description changed:

  [Impact]
  Can't record sounds from external headset
  
  [Fix]
- Add ASUS PRIME TRX40 PRO-S in the support list.
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
+ The fix is provided by the realtek and is archived in the sound sub-system 
tree. 
+ Add "Dell Precision 3650 Tower" in the fix-up table.
  
  [Test Case]
  1. install manifest
  2. plug-in an external headset
  3. try to record sounds via external headset
  
  [Where problems could occur]
  Just add a supported device.

** Description changed:

  [Impact]
  Can't record sounds from external headset
  
  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
- The fix is provided by the realtek and is archived in the sound sub-system 
tree. 
+ The patch is provided by the realtek and is archived in the sound sub-system 
tree.
  Add "Dell Precision 3650 Tower" in the fix-up table.
  
  [Test Case]
  1. install manifest
  2. plug-in an external headset
  3. try to record sounds via external headset
  
  [Where problems could occur]
  Just add a supported device.

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

Title:
  ALSA: hda/realtek - Supported Dell fixed type headset

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]
  Can't record sounds from external headset

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
  The patch is provided by the realtek and is archived in the sound sub-system 
tree.
  Add "Dell Precision 3650 Tower" in the fix-up table.

  [Test Case]
  1. install manifest
  2. plug-in an external headset
  3. try to record sounds via external headset

  [Where problems could occur]
  Just add a supported device.

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

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

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

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 1908978

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

Title:
ALSA: hda/realtek - Supported Dell fixed type headset

Status in linux package in Ubuntu:
Incomplete

Bug description:
[Impact]
Can't record sounds from external headset

[Fix]

https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
The fix is provided by the realtek and is archived in the sound sub-system
tree.
Add "Dell Precision 3650 Tower" in the fix-up table.

[Test Case]
1. install manifest
2. plug-in an external headset
3. try to record sounds via external headset

[Where problems could occur]
Just add a supported device.

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

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

[Kernel-packages] [Bug 1908978] [NEW] ALSA: hda/realtek - Supported Dell fixed type headset

Public bug reported:

[Impact]
Can't record sounds from external headset

[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
The fix is provided by the realtek and is archived in the sound sub-system
tree.
Add "Dell Precision 3650 Tower" in the fix-up table.

[Test Case]
1. install manifest
2. plug-in an external headset
3. try to record sounds via external headset

[Where problems could occur]
Just add a supported device.

** Affects: linux (Ubuntu)
Importance: Undecided
Status: 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/1908978

Title:
ALSA: hda/realtek - Supported Dell fixed type headset

Status in linux package in Ubuntu:
Incomplete

Bug description:
[Impact]
Can't record sounds from external headset

[Fix]

[Test Case]
1. install manifest
2. plug-in an external headset
3. try to record sounds via external headset

[Where problems could occur]
Just add a supported device.

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

[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM

2020-12-21 Thread Po-Hsu Lin

This issue does not exist on Oracle 4.15.0-1059.65~16.04.1 anymore.

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

Title:
  vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
  B-oracle-4.15 / X-KVM / B-KVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  When running kvm-unit-tests under a guest, it will be paused, requiring a
  reset. When running the same test on a host (vmx_nm_test), it will fail.

  [Test case]
  Grab kvm-unit-tests, build it and run:

  TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu
  host,+vmx -append "vmx_nm_test"

  If done inside a guest, when the host runs the bionic 4.15 kernel, the guest
  will pause.

  [Potential regressions]
  Nested KVM could stop working. Floating point could stop working on KVM
  guests, though the code that relied on this was already removed from
  Bionic.

  
  --

  
  This issue was first spotted on Mar.16 [1]

  The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both
  VM.Standard2.1 and VM.Standard2.16, this is not a regression since it
  can be reproduced with 4.15.0-1031-oracle #34~16.04.1:

  Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test'
   BUILD_HEAD=4671e4ba
   timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd 
/tmp/tmp.h2DFw8L0AF
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 477000
   cr4 = 20

   Test suite: vmx_nm_test
  client_loop: send disconnect: Broken pipe
  (node disconnected here)

  Before the test started, this can be found in syslog:
  Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF 
CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for 
details.

  After that, noting was printed and node disconnected.

  If you try to run this case manually, it will stop at:
  # ./vmx_nm_test
  BUILD_HEAD=4671e4ba
  ready!!!
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 
-cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM
  enabling ap
  (stopped here, even the "enabling apic" string was not printed)

  It looks like this is a new test case added since the cycle of
  4.15.0-1037.41~16.04.1-oracle

  [1] https://bugs.launchpad.net/ubuntu-kernel-
  tests/+bug/1867623/comments/2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1
  ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18
  Uname: Linux 4.15.0-1031-oracle x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Mon Apr 13 05:18:03 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oracle
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

@Rex, yes, and I've updated my PPA with kernels rebuilt with that fix
cherry-picked. Tested oem-5.10 and Groovy 5.8 so far. Looks promising
and will proceed to SRU.

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  In Progress
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.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

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

Title:
  System froze

Status in linux package in Ubuntu:
  Expired

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 1900910] Re: [nouveau] Screen freeze after closing lid and suspend

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

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

Status in linux package in Ubuntu:
  Expired

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 1900927] Re: Affinity broken due to vector space exhaustion.

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

Title:
   Affinity broken due to vector space exhaustion.

Status in linux package in Ubuntu:
  Expired

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 1899882] Re: hdmi monitor on

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1899882

Title:
  hdmi monitor on

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  XPS 13 9300 -- 50H3P53 -- Dell laptop
  WD19TB --- 4BWNW43 -- Dell Thunderbolt dock
  S2319HS -- B4TYZ13 -- Dell 23" external monitor

  External monitor remains black when waking system after suspending.  
  Works OK when log out then log in or when reboot.  
  Using HDMI cable from dock to monitor.

  From /var/log/syslog:

  Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here 
]
  Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == PORT_A 
|| port == PORT_E))
  Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at 
drivers/gpu/drm/i915/display/intel_ddi.c:3179 
intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915]
  Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp 
ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport 
cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al
  g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops 
bluetooth videobuf2_v4l2 videobuf2_common videodev mc ecdh_generic ecc 
nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common snd_soc_hd
  ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress 
snd_hda_codec_realtek
   ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp 
snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio intel_rapl_msr 
snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl
  amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event 
snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq aesni_intel 
dell_smbios crypto_simd dcdbas cryptd glue_helper rapl
  Oct 14 21:09:41 lt9 kernel: [32059.746719]  intel_cstate iwlmvm input_leds 
serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof 
dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t
  rigger industrialio_triggered_buffer iwlwifi kfifo_buf hid_sensor_iio_common 
rtsx_pci_ms 8250_dw memstick soundcore industrialio ucsi_acpi 
processor_thermal_device intel_rapl_common mei_me typec_ucsi cros_ec_i
  shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec 
int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc
   ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_
  hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 
crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper intel_lpss_pci 
i2c_i801 intel_lpss nvme_core syscopyarea idma64
  Oct 14 21:09:41 lt9 kernel: [32059.746764]  sysfillrect virt_dma sysimgblt 
fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid hid video 
pinctrl_icelake pinctrl_intel
  Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg 
Tainted: GW 5.4.0-48-generic #52-Ubuntu
  Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS 13 
9300/0RMFN5, BIOS 1.2.0 08/13/2020
  Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: 
0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915]
  Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 00 00 
00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 c7 43 79 
77 c0 e8 0c c5 bd db <0f> 0b e9 ae fe ff ff 41 8b 54 24 70 8b 75 a8 4c 89 e7 e8 
8a c7 ff
  Oct 14 21:09:41 lt9 kernel: [32059.746849] RSP: 0018:b3bf01253850 EFLAGS: 
00010282
  Oct 14 21:09:41 lt9 kernel: [32059.746852] RAX:  RBX: 
9f1eebeca000 RCX: 
  Oct 14 21:09:41 lt9 kernel: [32059.746854] RDX: 0035 RSI: 
9dd955d5 RDI: 0246
  Oct 14 21:09:41 lt9 kernel: [32059.746855] RBP: b3bf012538a8 R08: 
9dd955a0 R09: 0035
  Oct 14 21:09:41 lt9 kernel: [32059.746857] R10: 9dd95980 R11: 
9dd9559f R12: 9f1eebeca000
  Oct 14 21:09:41 lt9 kernel: [32059.746858] R13: 9f1e1bb67000 R14: 
9f1eebb8 R15: 9f1eebeca120
  Oct 14 21:09:41 lt9 kernel: [32059.746861] FS:  7fd341ab0a80() 
GS:9f1eff78() knlGS:
  Oct 14 21:09:41 lt9 kernel: [32059.746863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 14 21:09:41 lt9 kernel: [32059.746865] CR2: 0177088fa000 CR3: 
00046e046003 CR4: 00760ee0
  Oct 14 21:09:41 lt9 kernel: [32059.746866] PKRU: 5554
  Oct 14 21:09:41 lt9 kernel: [

[Kernel-packages] [Bug 1908885] Re: Fix drm_WARN_ON(common_len <= 0)

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

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

Title:
  Fix drm_WARN_ON(common_len <= 0)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]

  The TGL machine could show drm_WARN_ON(common_len <= 0) when connect with the 
TBT dock(WD19TB).
  [ cut here ]
  i915 :00:02.0: drm_WARN_ON(common_len <= 0)
  WARNING: CPU: 4 PID: 194 at drivers/gpu/drm/i915/display/intel_dp.c:2385 
intel_dp_compute_link_config+0x820/0x900 [i915]
  Modules linked in: i915(+) i2c_algo_bit drm_kms_helper crc32_pclmul 
syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core nvme e1000e(+) c_i801 
ahci i2c_smbus
  thunderbolt(+) xhci_pci xhci_pci_renesas wmi video backlight 
pinctrl_tigerlake pinctrl_intel
  CPU: 4 PID: 194 Comm: systemd-udevd Not tainted 5.10.0-051000rc7-generic 
#202012062330
  Hardware name: Dell Inc. OptiPlex 7090 UFF - China HDD Protection/, BIOS 
0.6.4 11/07/2020
  RIP: 0010:intel_dp_compute_link_config+0x820/0x900 [i915]
  Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 b9 b9 60 dc 48 c7 c1 b5 6d 83 c0 
4c 89 f2 48 c7 c7 d0 69 83 c0 48 89 c6 e8 a5 84 f2 db <0f> 0b ff e9 60 f8 ff ff 
48 8b
  c2 60 04 82
  RSP: 0018:ba120061f6b0 EFLAGS: 00010282
  RAX:  RBX: 956df17c2000 RCX: 
  RDX: 002f RSI: 9e1b1dcf RDI: 0246
  RBP: ba120061f720 R08: 9e1b1da0 R09: 002f
  R10: 9e1b2180 R11: 9e1b1db2 R12: 956df1e4
  R13: 956df17c6000 R14: 956e029a99e0 R15: 956df17c6000
  FS: 7fbd08cdd880() GS:956e0e50() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: 5635d4c41678 CR3: 000271c64006 CR4: 00770ee0
  PKRU: 5554
  Call Trace:
  ? dev_printk+0x5d/0x74
  intel_dp_compute_config+0x11b/0x570 [i915]
  intel_ddi_compute_config+0x9f/0xe0 [i915]
  intel_modeset_pipe_config+0x212/0x9c0 [i915]
  intel_atomic_check+0x263/0x12c0 [i915]
  ? __drm_dbg+0x87/0x90 [drm]
  drm_atomic_check_only+0x2c7/0x450 [drm]
  drm_atomic_commit+0x18/0x50 [drm]
  intel_modeset_init_nogem+0x486/0xb10 [i915]
  i915_driver_probe+0x3e8/0x6e0 [i915]
  ? mutex_lock+0x13/0x40
  i915_pci_probe+0x5a/0x140 [i915]
  local_pci_probe+0x48/0x80
  pci_device_probe+0x10f/0x1c0
  really_probe+0x1db/0x440
  driver_probe_device+0xe9/0x160
  device_driver_attach+0x5d/0x70
  __driver_attach+0x8f/0x150
  ? device_driver_attach+0x70/0x70
  bus_for_each_dev+0x7e/0xc0
  driver_attach+0x1e/0x20
  bus_add_driver+0x152/0x1f0
  driver_register+0x74/0xd0
  __pci_register_driver+0x54/0x60
  i915_init+0x61/0x75 [i915]
  ? 0xc08a1000
  do_one_initcall+0x4a/0x1fa
  ? _cond_resched+0x19/0x30
  ? kmem_cache_alloc_trace+0x17e/0x2f0
  do_init_module+0x62/0x240
  load_module+0xfbe/0x11e0
  __do_sys_finit_module+0xbe/0x120
  ? __do_sys_finit_module+0xbe/0x120
  __x64_sys_finit_module+0x1a/0x20
  do_syscall_64+0x38/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fbd0925f89d
  Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 73 01 c3 48 8b 0d 
c3 f5 0c 00 f7 d8 64 89 01 48
  RSP: 002b:7fffa60dc628 EFLAGS: 0246 ORIG_RAX: 0139
  RAX: ffda RBX: 5635d4c942b0 RCX: 7fbd0925f89d
  RDX:  RSI: 7fbd0913cded RDI: 0014
  RBP: 0002 R08:  R09: 
  R10: 0014 R11: 0246 R12: 7fbd0913cded
  R13:  R14: 5635d4c92b70 R15: 5635d4c942b0
  ---[ end trace c48f367c543f3384 ]-—

  [Fix]

  Kernel driver patchset https://patchwork.freedesktop.org/series/82173/
  targeting v5.11.

  [Test Case]

  1. Boot with kernel built with these patches applied.
  2. check the dmesg.

  [Where problems could occur]

  The fix could resolve the drm_WARN_ON.
  It ease the symptom that can't output the video with the TBT dock(WD19TB) at 
the first boot, but it may not fix.

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

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

[Kernel-packages] [Bug 1908916] Re: brcmfmac bug while going to sleep

2020-12-21 Thread Nir Yeffet

Workaround:
$ cat /etc/pm/sleep.d/20_brcmfmac 
#!/bin/sh

case "${1}" in
suspend)
rmmod brcmfmac 
;;
resume)
modprobe brcmfmac
;;
esac

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

Title:
  brcmfmac bug while going to sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439355] BUG: kernel NULL 
pointer dereference, address: 0050
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439365] #PF: supervisor read 
access in kernel mode
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439368] #PF: error_code(0x) 
- not-present page
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439371] PGD 0 P4D 0 
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439379] Oops:  [#1] SMP PTI
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439386] CPU: 2 PID: 869 Comm: 
wpa_supplicant Tainted: G   OE 5.4.0-58-generic #64-Ubuntu
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439389] Hardware name: Apple 
Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS 184.0.0.0.0 04/11/2019
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439427] RIP: 
0010:brcmf_remove_interface+0x4e/0x80 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439433] Code: 00 00 75 4c 44 8b 
47 60 41 89 f4 bf 02 00 00 00 48 c7 c2 90 b8 8e c0 48 c7 c6 90 3b 8e c0 e8 19 
dc ff ff 48 8b 3b 48 8b 47 08 <48> 8b 40 50 48 85 c0 74 0b 48 89 df e8 71 b9 b3 
d6 48 8b 3b 8b 73
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439437] RSP: 
0018:aa0f00bab9a8 EFLAGS: 00010286
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439441] RAX:  
RBX: 95ffd50b1000 RCX: 0001
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439445] RDX: c08eb890 
RSI: c08e3b90 RDI: 95ffd6a647a0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439448] RBP: aa0f00bab9b8 
R08:  R09: 
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439451] R10: 017f4b2f6a93 
R11: 0396353f R12: 0001
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439454] R13: 000a 
R14:  R15: 95ffd59a8000
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439458] FS:  
7f1031058140() GS:95ffdeb0() knlGS:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439462] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439465] CR2: 0050 
CR3: 000453dd2003 CR4: 003606e0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439468] Call Trace:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439495]  
brcmf_p2p_del_vif+0x256/0x280 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439517]  
brcmf_cfg80211_del_iface+0x194/0x210 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439599]  
nl80211_del_interface+0x4f/0x110 [cfg80211]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439609]  
genl_family_rcv_msg+0x1b9/0x470
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439618]  genl_rcv_msg+0x4c/0xa0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439624]  ? 
_cond_resched+0x19/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439630]  ? 
genl_family_rcv_msg+0x470/0x470
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439635]  
netlink_rcv_skb+0x50/0x120
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439641]  genl_rcv+0x29/0x40
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439646]  
netlink_unicast+0x187/0x220
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439652]  
netlink_sendmsg+0x222/0x3e0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439660]  sock_sendmsg+0x65/0x70
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439666]  
sys_sendmsg+0x212/0x280
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439673]  
___sys_sendmsg+0x88/0xd0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439681]  ? dentry_free+0x37/0x70
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439688]  ? 
security_file_free+0x54/0x60
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439695]  ? 
get_max_files+0x20/0x20
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439703]  ? 
__cgroup_bpf_run_filter_setsockopt+0xae/0x2d0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439708]  ? 
_cond_resched+0x19/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439714]  ? aa_sk_perm+0x43/0x170
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439722]  __sys_sendmsg+0x5c/0xa0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439730]  
__x64_sys_sendmsg+0x1f/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439738]  
do_syscall_64+0x57/0x190
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439745]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439750] RIP: 0033:0x7f10313e8747
  Dec 20 10:59:18 nir-MacBookPro

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

Could you try to boot in recovery mode and then resume the normal boot
process? I think i have the MSFT0001:00 06CB:7F28 touchpad installed but
i'll check these days.

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

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

2020-12-21 Thread Wes Newell

As you can see there's no reference to ir-keytable running in that
kernel. Ran the same on good kernel 5.8.7 and here's a snippet from the
output of it.

Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: 
/usr/lib/udev/rules.d/60-ir-keytable.rules:5 RUN '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s $name'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Running command 
"/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3"
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Starting 
'/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: Successfully forked off '(spawn)' 
as PID 1477.
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Processing device 
(SEQNUM=4086, ACTION=add)
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Device (SEQNUM=4086, 
ACTION=add) processed
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: sd-device-monitor: 
Passed 194 byte to netlink monitor
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) '/etc/rc_keymaps/rc6_mce.toml: error: cannot 
open: No such file or directory'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) 'Old keytable cleared'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) 'Wrote 163 keycode(s) to driver'
Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: Device 
(SEQNUM=4089, ACTION=add) is queued
Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: sd-device-monitor: 
Passed 138 byte to netlink monitor
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Processing device 
(SEQNUM=4089, ACTION=add)
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be FDec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: 
/usr/lib/udev/rules.d/60-ir-keytable.rules:5 RUN '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s $name'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Running command 
"/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3"
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Starting 
'/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: Successfully forked off '(spawn)' 
as PID 1477.
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Processing device 
(SEQNUM=4086, ACTION=add)
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Device (SEQNUM=4086, 
ACTION=add) processed
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: sd-device-monitor: 
Passed 194 byte to netlink monitor
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) '/etc/rc_keymaps/rc6_mce.toml: error: cannot 
open: No such file or directory'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) 'Old keytable cleared'
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) 'Wrote 163 keycode(s) to driver'
Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: Device 
(SEQNUM=4089, ACTION=add) is queued
Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: sd-device-monitor: 
Passed 138 byte to netlink monitor
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Processing device 
(SEQNUM=4089, ACTION=add)
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Device 
(SEQNUM=4089, ACTION=add) processed
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: sd-device-monitor: 
Passed 138 byte to netlink monitor
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) 'Protocols changed to nec rc-6 '
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Process '/usr/bin/ir-keytable 
-a /etc/rc_maps.cfg -s rc3' succeeded.
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Device (SEQNUM=4082, 
ACTION=add) processedilled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Device 
(SEQNUM=4089, ACTION=add) processed
Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: sd-device-monitor: 
Passed 138 byte to netlink monitor
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a 
/etc/rc_maps.cfg -s rc3'(err) 'Protocols change

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

2020-12-21 Thread Piotr Tomaszewski

@Robin Windey (r0wi), unfortunately it does not works with my touchpad.
Tried kernel you linked on PopOS 20.10 and Ubuntu 20.04.1. Both results
are same, touchpad not works. What is yours touchpad?

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

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

2020-12-21 Thread albertoiNET

On Ubuntu 20.10 I installed with kernel 5.10.1 with your instructions
@Robin Windey (r0wi) and neither works touchpad

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

[Kernel-packages] [Bug 1881109] Re: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.

2020-12-21 Thread Frank Heimes

Hello Max, glad to read that.
That's what I hoped, after the significant patch set of LP 1887124 landed.
I'm closing this bug on our side, too.
Thx

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

** Changed in: ubuntu-z-systems
   Status: Incomplete => 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/1881109

Title:
  [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be
  triggered by scsi errors.

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  We can reproduce a crash in the block layer with lots of stress on
  lots of SCSI disks (on an XIV storage server).

  We seem to have several scsi stalls in the logs/errors (needs to be
  analyzed further) but in the end we do crash with this this calltrace.

  [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403
  [20832.901159] Fault in home space mode while using kernel ASCE.
  [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 
S:03fc1cc78800 P:0400 
  [20832.901264] Oops: 0011 ilc:2 [#1] SMP 
  [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables 
iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw 
vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm 
drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress 
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash 
dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 
libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common 
zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup
  [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 
5.4.0-29-generic #33-Ubuntu
  [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR)
  [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be 
(try_to_wake_up+0x4e/0x700)
  [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 
0003
  [20832.901750] 004c 040003fd005a4600 
0003
  [20832.901753]0003 7fe00dea8454  
7fe00dea7b00
  [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 
7fe0021c7a60
  [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la  
%r9,2388(%r2)
01d3cbd559b6: 582003acl   
%r2,940
   #01d3cbd559ba: a718lhi %r1,0
   >01d3cbd559be: ba129000cs  
%r1,%r2,0(%r9)
01d3cbd559c2: a77401c9brc 
7,01d3cbd55d54
01d3cbd559c6: e310b0080004lg  
%r1,8(%r11)
01d3cbd559cc: b9800018ngr 
%r1,%r8
01d3cbd559d0: a774001fbrc 
7,01d3cbd55a0e
  [20832.901784] Call Trace:
  [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474)
  [20832.901823]  [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 
  [20832.901827]  [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 
  [20832.901829]  [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 
  [20832.901830]  [<01d3cbd7515a>] __wake_up+0x2a/0x40 
  [20832.901835]  [<01d3cc1e8640>] wbt_done+0x90/0xe0 
  [20832.901837]  [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 
  [20832.901841]  [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 
  [20832.901848]  [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 
  [20832.901849]  [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 
  [20832.901850]  [<01d3cc57e710>] __do_softirq+0x100/0x360 
  [20832.901853]  [<01d3cbd2525e>] irq_exit+0x9e/0xc0 
  [20832.901856]  [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 
  [20832.901859]  [<01d3cc57dc28>] ext_int_handler+0x128/0x12c 
  [20832.901860]  [<01d3cc57d306>] sie_exit+0x0/0x46 
  [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30)
  [20832.901870]  [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 
  [20832.901875]  [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 
  [20832.901880]  [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 
  [20832.901881]  [<01d3cbf86304>] ksys_ioctl+0x8

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

This change was made by a bot.

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

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

Title:
  Touchpad is not present in input devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop Model : HP Pavilion Gaming Laptop 15-ec1071nf
  Touchpad : HP Imagepad, supposedly a Synaptics touchpad (TBC)
  First appearance : Fresh Ubuntu 18.04 install, immediately upgraded to 20.04.

  Tested with both available kernels : 
  ii  linux-image-5.3.0-28-generic   5.3.0-28.30~18.04.1
   amd64Signed kernel image generic
  ii  linux-image-5.4.0-58-generic   5.4.0-58.64
   amd64Signed kernel image generic

  
  See attached file.
  Bug summited with the help of 
https://wiki.ubuntu.com/DebuggingTouchpadDetection

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rgo1450 F pulseaudio
   /dev/snd/controlC1:  rgo1450 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 17:21:08 2020
  InstallationDate: Installed on 2020-12-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
  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=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=9265c5e1-5392-458a-8f41-967a63493630 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-12-21 (0 days ago)
  dmi.bios.date: 07/22/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87B1
  dmi.board.vendor: HP
  dmi.board.version: 31.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd07/22/2020:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx
  dmi.product.sku: 1X2T6EA#ABF
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1908919] Re: Touchpad is not present in input devices

2020-12-21 Thread Romain GONCALVES

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

Title:
  Touchpad is not present in input devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop Model : HP Pavilion Gaming Laptop 15-ec1071nf
  Touchpad : HP Imagepad, supposedly a Synaptics touchpad (TBC)
  First appearance : Fresh Ubuntu 18.04 install, immediately upgraded to 20.04.

  Tested with both available kernels : 
  ii  linux-image-5.3.0-28-generic   5.3.0-28.30~18.04.1
   amd64Signed kernel image generic
  ii  linux-image-5.4.0-58-generic   5.4.0-58.64
   amd64Signed kernel image generic

  
  See attached file.
  Bug summited with the help of 
https://wiki.ubuntu.com/DebuggingTouchpadDetection

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rgo1450 F pulseaudio
   /dev/snd/controlC1:  rgo1450 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 17:21:08 2020
  InstallationDate: Installed on 2020-12-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
  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=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=9265c5e1-5392-458a-8f41-967a63493630 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-12-21 (0 days ago)
  dmi.bios.date: 07/22/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87B1
  dmi.board.vendor: HP
  dmi.board.version: 31.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd07/22/2020:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx
  dmi.product.sku: 1X2T6EA#ABF
  dmi.sys.vendor: HP

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

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

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

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

Title:
  brcmfmac bug while going to sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439355] BUG: kernel NULL 
pointer dereference, address: 0050
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439365] #PF: supervisor read 
access in kernel mode
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439368] #PF: error_code(0x) 
- not-present page
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439371] PGD 0 P4D 0 
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439379] Oops:  [#1] SMP PTI
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439386] CPU: 2 PID: 869 Comm: 
wpa_supplicant Tainted: G   OE 5.4.0-58-generic #64-Ubuntu
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439389] Hardware name: Apple 
Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS 184.0.0.0.0 04/11/2019
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439427] RIP: 
0010:brcmf_remove_interface+0x4e/0x80 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439433] Code: 00 00 75 4c 44 8b 
47 60 41 89 f4 bf 02 00 00 00 48 c7 c2 90 b8 8e c0 48 c7 c6 90 3b 8e c0 e8 19 
dc ff ff 48 8b 3b 48 8b 47 08 <48> 8b 40 50 48 85 c0 74 0b 48 89 df e8 71 b9 b3 
d6 48 8b 3b 8b 73
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439437] RSP: 
0018:aa0f00bab9a8 EFLAGS: 00010286
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439441] RAX:  
RBX: 95ffd50b1000 RCX: 0001
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439445] RDX: c08eb890 
RSI: c08e3b90 RDI: 95ffd6a647a0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439448] RBP: aa0f00bab9b8 
R08:  R09: 
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439451] R10: 017f4b2f6a93 
R11: 0396353f R12: 0001
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439454] R13: 000a 
R14:  R15: 95ffd59a8000
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439458] FS:  
7f1031058140() GS:95ffdeb0() knlGS:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439462] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439465] CR2: 0050 
CR3: 000453dd2003 CR4: 003606e0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439468] Call Trace:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439495]  
brcmf_p2p_del_vif+0x256/0x280 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439517]  
brcmf_cfg80211_del_iface+0x194/0x210 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439599]  
nl80211_del_interface+0x4f/0x110 [cfg80211]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439609]  
genl_family_rcv_msg+0x1b9/0x470
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439618]  genl_rcv_msg+0x4c/0xa0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439624]  ? 
_cond_resched+0x19/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439630]  ? 
genl_family_rcv_msg+0x470/0x470
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439635]  
netlink_rcv_skb+0x50/0x120
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439641]  genl_rcv+0x29/0x40
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439646]  
netlink_unicast+0x187/0x220
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439652]  
netlink_sendmsg+0x222/0x3e0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439660]  sock_sendmsg+0x65/0x70
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439666]  
sys_sendmsg+0x212/0x280
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439673]  
___sys_sendmsg+0x88/0xd0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439681]  ? dentry_free+0x37/0x70
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439688]  ? 
security_file_free+0x54/0x60
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439695]  ? 
get_max_files+0x20/0x20
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439703]  ? 
__cgroup_bpf_run_filter_setsockopt+0xae/0x2d0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439708]  ? 
_cond_resched+0x19/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439714]  ? aa_sk_perm+0x43/0x170
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439722]  __sys_sendmsg+0x5c/0xa0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439730]  
__x64_sys_sendmsg+0x1f/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439738]  
do_syscall_64+0x57/0x190
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439745]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439750] RIP: 0033:0x7f10313e8747
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439755] Code: 64 89 02 48 c7 c0 
ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 0

[Kernel-packages] [Bug 1908919] [NEW] Touchpad is not present in input devices

2020-12-21 Thread Romain GONCALVES

Public bug reported:

Laptop Model : HP Pavilion Gaming Laptop 15-ec1071nf
Touchpad : HP Imagepad, supposedly a Synaptics touchpad (TBC)
First appearance : Fresh Ubuntu 18.04 install, immediately upgraded to 20.04.

Tested with both available kernels : 
ii  linux-image-5.3.0-28-generic   5.3.0-28.30~18.04.1  
 amd64Signed kernel image generic
ii  linux-image-5.4.0-58-generic   5.4.0-58.64  
 amd64Signed kernel image generic


See attached file.
Bug summited with the help of https://wiki.ubuntu.com/DebuggingTouchpadDetection

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-58-generic 5.4.0-58.64
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rgo1450 F pulseaudio
 /dev/snd/controlC1:  rgo1450 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 21 17:21:08 2020
InstallationDate: Installed on 2020-12-21 (0 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
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=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=9265c5e1-5392-458a-8f41-967a63493630 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-58-generic N/A
 linux-backports-modules-5.4.0-58-generic  N/A
 linux-firmware1.187.6
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-12-21 (0 days ago)
dmi.bios.date: 07/22/2020
dmi.bios.vendor: AMI
dmi.bios.version: F.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B1
dmi.board.vendor: HP
dmi.board.version: 31.20
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd07/22/2020:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.20:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx
dmi.product.sku: 1X2T6EA#ABF
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug eoan focal

** Attachment added: "cat /proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1908919/+attachment/5445595/+files/devices

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

Title:
  Touchpad is not present in input devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop Model : HP Pavilion Gaming Laptop 15-ec1071nf
  Touchpad : HP Imagepad, supposedly a Synaptics touchpad (TBC)
  First appearance : Fresh Ubuntu 18.04 install, immediately upgraded to 20.04.

  Tested with both available kernels : 
  ii  linux-image-5.3.0-28-generic   5.3.0-28.30~18.04.1
   amd64Signed kernel image generic
  ii  linux-image-5.4.0-58-generic   5.4.0-58.64
   amd64Signed kernel image generic

  
  See attached file.
  Bug summited with the help of 
https://wiki.ubuntu.com/DebuggingTouchpadDetection

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rgo1450 F pulseaudio
   /dev/snd/controlC1:  rgo1450 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 17:21:08 2020
  InstallationDate: Installed on 2020-12-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
  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=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=9265c5e1-5392-458a-8f41-967a63493630 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-12-21 (0 days ago)
  dmi.bios.date: 07/22/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87B1
  d

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

is a bit OT but..

QCA9984 (QNAP QWA-AC2600)

https://www.qnap.com/i/_attach_file/product/photo/800_500
/338_1524021711_QWA-AC2600_Front.png

QCA9984 (Netgear R7800)

https://www.netgear.de/images/Products/Networking/WirelessRouters/R7800/R7800_Hero_Transparent.png

The R7800 is running DD-WRT (v3.0-r44719) with kvalo Firmware

VHT80 4x4

1 Stream Download

[ 5] 63.00-63.36 sec 36.1 MBytes 843 Mbits/sec

2 Stream Download

[ 5] 0.00-60.03 sec 3.24 GBytes 464 Mbits/sec
[ 8] 0.00-60.03 sec 3.15 GBytes 451 Mbits/sec
[SUM] 0.00-60.03 sec 6.40 GBytes 915 Mbits/sec

1 Stream Upload

[ 5] 0.00-60.00 sec 6.52 GBytes 933 Mbits/sec

2 Stream Upload

[ 5] 0.00-60.00 sec 3.28 GBytes 469 Mbits/sec
[ 7] 0.00-60.00 sec 3.29 GBytes 470 Mbits/sec
[SUM] 0.00-60.00 sec 6.56 GBytes 939 Mbits/sec

all direct WLAN <--> LAN throughput

https://ibb.co/2sw3FDh

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 246

[Kernel-packages] [Bug 1908916] [NEW] brcmfmac bug while going to sleep

2020-12-21 Thread Nir Yeffet

Public bug reported:

Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439355] BUG: kernel NULL pointer 
dereference, address: 0050
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439365] #PF: supervisor read 
access in kernel mode
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439368] #PF: error_code(0x) - 
not-present page
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439371] PGD 0 P4D 0 
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439379] Oops:  [#1] SMP PTI
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439386] CPU: 2 PID: 869 Comm: 
wpa_supplicant Tainted: G   OE 5.4.0-58-generic #64-Ubuntu
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439389] Hardware name: Apple Inc. 
MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS 184.0.0.0.0 04/11/2019
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439427] RIP: 
0010:brcmf_remove_interface+0x4e/0x80 [brcmfmac]
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439433] Code: 00 00 75 4c 44 8b 
47 60 41 89 f4 bf 02 00 00 00 48 c7 c2 90 b8 8e c0 48 c7 c6 90 3b 8e c0 e8 19 
dc ff ff 48 8b 3b 48 8b 47 08 <48> 8b 40 50 48 85 c0 74 0b 48 89 df e8 71 b9 b3 
d6 48 8b 3b 8b 73
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439437] RSP: 
0018:aa0f00bab9a8 EFLAGS: 00010286
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439441] RAX:  
RBX: 95ffd50b1000 RCX: 0001
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439445] RDX: c08eb890 
RSI: c08e3b90 RDI: 95ffd6a647a0
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439448] RBP: aa0f00bab9b8 
R08:  R09: 
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439451] R10: 017f4b2f6a93 
R11: 0396353f R12: 0001
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439454] R13: 000a 
R14:  R15: 95ffd59a8000
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439458] FS:  
7f1031058140() GS:95ffdeb0() knlGS:
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439462] CS:  0010 DS:  ES: 
 CR0: 80050033
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439465] CR2: 0050 
CR3: 000453dd2003 CR4: 003606e0
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439468] Call Trace:
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439495]  
brcmf_p2p_del_vif+0x256/0x280 [brcmfmac]
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439517]  
brcmf_cfg80211_del_iface+0x194/0x210 [brcmfmac]
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439599]  
nl80211_del_interface+0x4f/0x110 [cfg80211]
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439609]  
genl_family_rcv_msg+0x1b9/0x470
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439618]  genl_rcv_msg+0x4c/0xa0
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439624]  ? _cond_resched+0x19/0x30
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439630]  ? 
genl_family_rcv_msg+0x470/0x470
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439635]  
netlink_rcv_skb+0x50/0x120
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439641]  genl_rcv+0x29/0x40
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439646]  
netlink_unicast+0x187/0x220
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439652]  
netlink_sendmsg+0x222/0x3e0
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439660]  sock_sendmsg+0x65/0x70
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439666]  
sys_sendmsg+0x212/0x280
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439673]  ___sys_sendmsg+0x88/0xd0
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439681]  ? dentry_free+0x37/0x70
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439688]  ? 
security_file_free+0x54/0x60
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439695]  ? get_max_files+0x20/0x20
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439703]  ? 
__cgroup_bpf_run_filter_setsockopt+0xae/0x2d0
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439708]  ? _cond_resched+0x19/0x30
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439714]  ? aa_sk_perm+0x43/0x170
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439722]  __sys_sendmsg+0x5c/0xa0
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439730]  
__x64_sys_sendmsg+0x1f/0x30
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439738]  do_syscall_64+0x57/0x190
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439745]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439750] RIP: 0033:0x7f10313e8747
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439755] Code: 64 89 02 48 c7 c0 
ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 
c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 
1c 48 89 74 24 10
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439759] RSP: 
002b:7fffeace23a8 EFLAGS: 0246 ORIG_RAX: 002e
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439763] RAX: ffda 
RBX: 563dd3d9d670 RCX: 7f10313e8747
Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439766] RDX:  
RSI: 7fff

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

2020-12-21 Thread bugproxy

--- Comment From max.bend...@ibm.com 2020-12-21 10:42 EDT---
We have re-run our test suite that originally produces this bug consistently 
and again were unable to reproduce. It looks like this issue has been fixed on 
the latest kernel.

```
bender@zt93ke:~$ uname -a
Linux zt93ke 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:13:08 UTC 2020 s390x 
s390x s390x GNU/Linux
bender@zt93ke:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
```

@Heinz-Werner Seeck good to close +1

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

Title:
  [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be
  triggered by scsi errors.

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  We can reproduce a crash in the block layer with lots of stress on
  lots of SCSI disks (on an XIV storage server).

  We seem to have several scsi stalls in the logs/errors (needs to be
  analyzed further) but in the end we do crash with this this calltrace.

  [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403
  [20832.901159] Fault in home space mode while using kernel ASCE.
  [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 
S:03fc1cc78800 P:0400 
  [20832.901264] Oops: 0011 ilc:2 [#1] SMP 
  [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables 
iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw 
vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm 
drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress 
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash 
dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 
libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common 
zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup
  [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 
5.4.0-29-generic #33-Ubuntu
  [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR)
  [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be 
(try_to_wake_up+0x4e/0x700)
  [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 
0003
  [20832.901750] 004c 040003fd005a4600 
0003
  [20832.901753]0003 7fe00dea8454  
7fe00dea7b00
  [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 
7fe0021c7a60
  [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la  
%r9,2388(%r2)
01d3cbd559b6: 582003acl   
%r2,940
   #01d3cbd559ba: a718lhi %r1,0
   >01d3cbd559be: ba129000cs  
%r1,%r2,0(%r9)
01d3cbd559c2: a77401c9brc 
7,01d3cbd55d54
01d3cbd559c6: e310b0080004lg  
%r1,8(%r11)
01d3cbd559cc: b9800018ngr 
%r1,%r8
01d3cbd559d0: a774001fbrc 
7,01d3cbd55a0e
  [20832.901784] Call Trace:
  [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474)
  [20832.901823]  [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 
  [20832.901827]  [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 
  [20832.901829]  [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 
  [20832.901830]  [<01d3cbd7515a>] __wake_up+0x2a/0x40 
  [20832.901835]  [<01d3cc1e8640>] wbt_done+0x90/0xe0 
  [20832.901837]  [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 
  [20832.901841]  [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 
  [20832.901848]  [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 
  [20832.901849]  [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 
  [20832.901850]  [<01d3cc57e710>] __do_softirq+0x100/0x360 
  [20832.901853]  [<00

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

apport information

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_REDIRECT ip_vs_rr

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

apport information

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_R

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

apport information

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

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

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in

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

apport information

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_REDIRECT ip_vs_rr xt

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

apport information

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_REDIRECT ip_vs_rr xt

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

apport information

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_REDIR

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

apport information

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_REDIREC

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

apport information

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_d

[Kernel-packages] [Bug 1908912] Re: "BUG: unable to handle page fault for address" 5.4.0-58-generic #64~18.04.1-Ubuntu

apport information

** Tags added: apport-collected uec-images

** Description changed:

  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04
  
  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_REDIRECT ip_vs_rr xt_ipvs ip_vs 
xt_nat xt_tcpudp veth vxlan ip6_udp_tunnel udp_tunnel iptable_mangle xt_mark 
xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype 
iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
bpfilter br_netfilter bridge stp llc rpcsec_gss_krb5 auth_rpcgss aufs nfsv4 
ceph libceph nfs lockd grace fscache ov

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

"have 1Gbit throughput in both directions (stable)" can you
describe,show me your setup? which antenna do you use?

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, 
PASSIVE-SCAN
   (5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-B

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

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 1908912

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

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI:

[Kernel-packages] [Bug 1908912] Re: "BUG: unable to handle page fault for address" 5.4.0-58-generic #64~18.04.1-Ubuntu

After this occurs, I can't execute any new processes, but current
processes continue to work. So if I have a shell session up already, it
will continue, however any command I run hangs indefinitely.

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

Title:
  "BUG: unable to handle page fault for address" 5.4.0-58-generic
  #64~18.04.1-Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  mezimm00@m5:~$ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
  linux-image-5.4.0-58-generic:
Installed: 5.4.0-58.64~18.04.1
Candidate: 5.4.0-58.64~18.04.1
Version table:
   *** 5.4.0-58.64~18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault 
for address: 0007fb39be0e
  Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
  Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
  Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
  Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
  Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof 
Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
  Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
  Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 
0010:lock_get_status+0x221/0x380
  Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 
30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 
91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 
30 fb ff
  Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
  Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
  Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
  Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
  Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
  Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
  Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
  Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
  Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
  Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
  Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
  Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
  Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
  Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
  Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
  Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
  Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
  Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
  Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 
00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 
c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 
89 d4 53
  Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
  Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
  Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
  Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
  Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
  Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
  Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_fil

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

I have already tested, I prefer to stay with the QCA firmware and
drivers that run for me stable and have for me fewer bugs

have 1Gbit throughput in both directions (stable)

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, 
PASS

[Kernel-packages] [Bug 1908912] [NEW] "BUG: unable to handle page fault for address" 5.4.0-58-generic #64~18.04.1-Ubuntu

Public bug reported:

mezimm00@m5:~$ lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04

mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic
linux-image-5.4.0-58-generic:
  Installed: 5.4.0-58.64~18.04.1
  Candidate: 5.4.0-58.64~18.04.1
  Version table:
 *** 5.4.0-58.64~18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status

Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault for 
address: 0007fb39be0e
Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in 
kernel mode
Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - 
not-present page
Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0
Dec 20 08:59:56 m5 kernel: [144210.719420] Oops:  [#1] SMP PTI
Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof Not 
tainted 5.4.0-58-generic #64~18.04.1-Ubuntu
Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge 
R930/0T55KM, BIOS 2.8.1 01/02/2020
Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 0010:lock_get_status+0x221/0x380
Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 30 
fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 91 
52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 30 
fb ff
Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 
00010286
Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 
939c33a080d8 RCX: 0001
Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 
91d75291 RDI: 938e2d796800
Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 
1000 R09: 93565c5a23b8
Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 
9394905b51d5 R12: 938e2d796800
Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 
0003b0a9 R15: 9390ce8a38a0
Dec 20 08:59:56 m5 kernel: [144210.719997] FS:  7ff9bcbb4040() 
GS:939c3fa8() knlGS:
Dec 20 08:59:56 m5 kernel: [144210.720050] CS:  0010 DS:  ES:  CR0: 
80050033
Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 
00e75d31a002 CR4: 001606e0
Dec 20 08:59:56 m5 kernel: [144210.720138] DR0:  DR1: 
 DR2: 
Dec 20 08:59:56 m5 kernel: [144210.720186] DR3:  DR6: 
fffe0ff0 DR7: 0400
Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace:
Dec 20 08:59:56 m5 kernel: [144210.720262]  locks_show+0x83/0xc0
Dec 20 08:59:56 m5 kernel: [144210.720297]  seq_read+0x2a4/0x420
Dec 20 08:59:56 m5 kernel: [144210.720330]  proc_reg_read+0x3e/0x60
Dec 20 08:59:56 m5 kernel: [144210.720361]  __vfs_read+0x1b/0x40
Dec 20 08:59:56 m5 kernel: [144210.721947]  vfs_read+0x8e/0x130
Dec 20 08:59:56 m5 kernel: [144210.723479]  ksys_read+0xa7/0xe0
Dec 20 08:59:56 m5 kernel: [144210.725009]  __x64_sys_read+0x1a/0x20
Dec 20 08:59:56 m5 kernel: [144210.726545]  do_syscall_64+0x57/0x190
Dec 20 08:59:56 m5 kernel: [144210.728064]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151
Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 00 
48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 c0 
75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 89 
d4 53
Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 
0246 ORIG_RAX: 
Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 
55f16fee7260 RCX: 7ff9bc48e151
Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 
55f16fee8d80 RDI: 0003
Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 
0001 R09: 55f16fee7340
Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 
0246 R12: 7ff9bc765760
Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 
55f16fee7260 R15: 0fff
Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter 
ip6_tables tcp_diag udp_diag inet_diag xt_REDIRECT ip_vs_rr xt_ipvs ip_vs 
xt_nat xt_tcpudp veth vxlan ip6_udp_tunnel udp_tunnel iptable_mangle xt_mark 
xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype 
iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
bpfilter br_netfilter bridge stp llc rpcsec_gss_krb5 auth_rpcgss aufs nfsv4 
ceph libceph nfs lockd grace fscache overlay ipmi_ssif intel_rapl_msr 
intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp dcdbas coretemp 
kvm_intel nls_iso8859_1 kvm rapl intel_cstate joydev input_le

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

if you like or need to compile, then i suggest to compile this.
https://github.com/greearb/ath10k-ct

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, 
PASSIVE-SCAN
   (5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

i hope it will be fixed upstream,then:-)
https://www.mail-archive.com/ath10k@lists.infradead.org/msg13295.html

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, 
PASSIVE-SCAN
   (5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, N

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

so we have something to do and have to rebuild our kernel all the time
:-)

only a small joke, I wish of course also that it is somehow fixed for
all

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, 
PASSIVE-SCAN
   (5270 - 5290

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

ok, but then then can add CONFIG_ATH_REG_DYNAMIC_USER_CERT_TESTING, 
CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS and CONFIG_CFG80211_CERTIFICATION_ONUS
to .config  for every build! Why they do not do that?

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT

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

2020-12-21 Thread Wes Newell

here goes.

root@mythfe0:/home/wes# journalctl -u systemd-udevd.service -f
-- Logs begin at Thu 2020-09-24 22:03:46 CDT. --
Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: 1-8: Device (SEQNUM=4105, 
ACTION=remove) processed
Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: 1-8: sd-device-monitor: Passed 355 
byte to netlink monitor
Dec 21 06:58:12 mythfe0 systemd-udevd[310]: Cleanup idle workers
Dec 21 06:58:12 mythfe0 systemd-udevd[1702]: Unload module index
Dec 21 06:58:12 mythfe0 systemd-udevd[1701]: Unload module index
Dec 21 06:58:12 mythfe0 systemd-udevd[1701]: Unloaded link configuration 
context.
Dec 21 06:58:12 mythfe0 systemd-udevd[1702]: Unloaded link configuration 
context.
Dec 21 06:58:12 mythfe0 systemd-udevd[310]: Worker [1701] exited
Dec 21 06:58:12 mythfe0 systemd-udevd[310]: Worker [1702] exited
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8: Device (SEQNUM=4106, 
ACTION=add) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: Validate module index
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: Check if link configuration needs 
reloading.
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: Successfully forked off 'n/a' as 
PID 1710.
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8: Worker [1710] is forked for 
processing SEQNUM=4106.
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Processing device 
(SEQNUM=4106, ACTION=add)
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: 
/usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from 
results of builtin command 'usb_id'
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8:1.0: Device (SEQNUM=4107, 
ACTION=add) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: lirc0: Device (SEQNUM=4108, 
ACTION=add) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: input20: Device (SEQNUM=4109, 
ACTION=add) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: event8: Device (SEQNUM=4110, 
ACTION=add) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: wakeup39: Device (SEQNUM=4111, 
ACTION=add) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8:1.0: Device (SEQNUM=4112, 
ACTION=bind) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8: Device (SEQNUM=4113, 
ACTION=bind) is queued
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: 
/usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from 
results of builtin command 'hwdb --subsystem=usb'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: 
/usr/lib/udev/rules.d/50-udev-default.rules:48 MODE 0664
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: 
/usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of 
builtin command 'path_id'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: 
/usr/lib/udev/rules.d/69-libmtp.rules:2685 Running PROGRAM 'mtp-probe 
/sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Starting 'mtp-probe 
/sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: Successfully forked off '(spawn)' 
as PID 1712.
Dec 21 06:58:29 mythfe0 mtp-probe[1712]: checking bus 1, device 5: 
"/sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8"
Dec 21 06:58:29 mythfe0 mtp-probe[1712]: bus: 1, device: 5 was not an MTP device
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: 'mtp-probe 
/sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5'(out) '0'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Process 'mtp-probe 
/sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5' succeeded.
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Handling device node 
'/dev/bus/usb/001/005', devnum=c189:4
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Setting permissions 
/dev/bus/usb/001/005, uid=0, gid=0, mode=0664
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Creating symlink 
'/dev/char/189:4' to '../bus/usb/001/005'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: sd-device: Created db file 
'/run/udev/data/c189:4' for 
'/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Device (SEQNUM=4106, 
ACTION=add) processed
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: sd-device-monitor: Passed 744 
byte to netlink monitor
Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8:1.0: sd-device-monitor: Passed 
307 byte to netlink monitor
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8:1.0: Processing device 
(SEQNUM=4107, ACTION=add)
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To 
Be Filled By O.E.M.'
Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8:1.0: 
/usr/l

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

2020-12-21 Thread Azizkhan

Robin Windey (r0wi), I tried to do this via ur instructions and via
Mainline utility, but my touchpad isn't working...

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

[Kernel-packages] [Bug 1908894] Re: USB controllers disconnects after random time

2020-12-21 Thread james byerley

I had an initial talk on that question:
https://answers.launchpad.net/ubuntu/+question/694351

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

Title:
  USB controllers disconnects after random time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I installed Ubuntu on my new convertible laptop, I got issues with the 
USB. Just after boot my USB controller is working properly (I can connect usb 
sticks, mices, and my internal camera works) and at some point long after it 
suddenly stop working (mices suddenly stop moving even when used, webcam and 
sticks no more detected).
  This can happend few minuts after boot, or several days after.
  Yet I have not been able to find what triggers the failure. It happends at 
any time during normal usage of the computer, including during the usb usage.

  more concrete infos:
  after failure, I get
  $ dmesg

  [ 2671.894099] perf: interrupt took too long (2512 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79500
  [ 3262.197917] xhci_hcd :03:00.3: Mismatch between completed Set TR Deq 
Ptr command & xHCI internal state.
  [ 3262.197927] xhci_hcd :03:00.3: ep deq seg = 8dafef36, deq ptr 
= 5f96ce32
  [ 3262.198052] xhci_hcd :03:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x]
  [ 3267.250397] xhci_hcd :03:00.3: xHCI host not responding to stop 
endpoint command.
  [ 3267.250428] xhci_hcd :03:00.3: xHCI host controller not responding, 
assume dead
  [ 3267.250463] xhci_hcd :03:00.3: HC died; cleaning up
  [ 3267.250499] usb 1-3: USB disconnect, device number 2
  [ 3267.311251] usb 1-4: USB disconnect, device number 3

  and lsusb doesn't show my devices anymore, even the newly inserted
  ones

  config: Asus Zenbook flip 14 UM462DA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jimy   1523 F pulseaudio
   /dev/snd/controlC0:  jimy   1523 F pulseaudio
   /dev/snd/pcmC1D0p:   jimy   1523 F...m pulseaudio
   /dev/snd/timer:  jimy   1523 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Dec 21 11:51:08 2020
  InstallationDate: Installed on 2020-07-28 (146 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX462DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=ba0f4ac4-b614-4882-83d6-485690f9a61a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX462DA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX462DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX462DA.307:bd09/28/2020:svnASUSTeKCOMPUTERINC.:pnZenBookUX462DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX462DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX462DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

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

Title:
  USB controllers disconnects after random time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I installed Ubuntu on my new convertible laptop, I got issues with the 
USB. Just after boot my USB controller is working properly (I can connect usb 
sticks, mices, and my internal camera works) and at some point long after it 
suddenly stop working (mices suddenly stop moving even when used, webcam and 
sticks no more detected).
  This can happend few minuts after boot, or several days after.
  Yet I have not been able to find what triggers the failure. It happends at 
any time during normal usage of the computer, including during the usb usage.

  more concrete infos:
  after failure, I get
  $ dmesg

  [ 2671.894099] perf: interrupt took too long (2512 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79500
  [ 3262.197917] xhci_hcd :03:00.3: Mismatch between completed Set TR Deq 
Ptr command & xHCI internal state.
  [ 3262.197927] xhci_hcd :03:00.3: ep deq seg = 8dafef36, deq ptr 
= 5f96ce32
  [ 3262.198052] xhci_hcd :03:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x]
  [ 3267.250397] xhci_hcd :03:00.3: xHCI host not responding to stop 
endpoint command.
  [ 3267.250428] xhci_hcd :03:00.3: xHCI host controller not responding, 
assume dead
  [ 3267.250463] xhci_hcd :03:00.3: HC died; cleaning up
  [ 3267.250499] usb 1-3: USB disconnect, device number 2
  [ 3267.311251] usb 1-4: USB disconnect, device number 3

  and lsusb doesn't show my devices anymore, even the newly inserted
  ones

  config: Asus Zenbook flip 14 UM462DA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jimy   1523 F pulseaudio
   /dev/snd/controlC0:  jimy   1523 F pulseaudio
   /dev/snd/pcmC1D0p:   jimy   1523 F...m pulseaudio
   /dev/snd/timer:  jimy   1523 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Dec 21 11:51:08 2020
  InstallationDate: Installed on 2020-07-28 (146 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX462DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=ba0f4ac4-b614-4882-83d6-485690f9a61a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX462DA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX462DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX462DA.307:bd09/28/2020:svnASUSTeKCOMPUTERINC.:pnZenBookUX462DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX462DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX462DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1908894] [NEW] USB controllers disconnects after random time

2020-12-21 Thread james byerley

Public bug reported:

Since I installed Ubuntu on my new convertible laptop, I got issues with the 
USB. Just after boot my USB controller is working properly (I can connect usb 
sticks, mices, and my internal camera works) and at some point long after it 
suddenly stop working (mices suddenly stop moving even when used, webcam and 
sticks no more detected).
This can happend few minuts after boot, or several days after.
Yet I have not been able to find what triggers the failure. It happends at any 
time during normal usage of the computer, including during the usb usage.

more concrete infos:
after failure, I get
$ dmesg

[ 2671.894099] perf: interrupt took too long (2512 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79500
[ 3262.197917] xhci_hcd :03:00.3: Mismatch between completed Set TR Deq Ptr 
command & xHCI internal state.
[ 3262.197927] xhci_hcd :03:00.3: ep deq seg = 8dafef36, deq ptr = 
5f96ce32
[ 3262.198052] xhci_hcd :03:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x]
[ 3267.250397] xhci_hcd :03:00.3: xHCI host not responding to stop endpoint 
command.
[ 3267.250428] xhci_hcd :03:00.3: xHCI host controller not responding, 
assume dead
[ 3267.250463] xhci_hcd :03:00.3: HC died; cleaning up
[ 3267.250499] usb 1-3: USB disconnect, device number 2
[ 3267.311251] usb 1-4: USB disconnect, device number 3

and lsusb doesn't show my devices anymore, even the newly inserted ones

config: Asus Zenbook flip 14 UM462DA

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-58-generic 5.4.0-58.64
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jimy   1523 F pulseaudio
 /dev/snd/controlC0:  jimy   1523 F pulseaudio
 /dev/snd/pcmC1D0p:   jimy   1523 F...m pulseaudio
 /dev/snd/timer:  jimy   1523 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Dec 21 11:51:08 2020
InstallationDate: Installed on 2020-07-28 (146 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook UX462DA
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=ba0f4ac4-b614-4882-83d6-485690f9a61a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-58-generic N/A
 linux-backports-modules-5.4.0-58-generic  N/A
 linux-firmware1.187.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/28/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX462DA.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX462DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX462DA.307:bd09/28/2020:svnASUSTeKCOMPUTERINC.:pnZenBookUX462DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX462DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: ZenBook Flip
dmi.product.name: ZenBook UX462DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

Title:
  USB controllers disconnects after random time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I installed Ubuntu on my new convertible laptop, I got issues with the 
USB. Just after boot my USB controller is working properly (I can connect usb 
sticks, mices, and my internal camera works) and at some point long after it 
suddenly stop working (mices suddenly stop moving even when used, webcam and 
sticks no more detected).
  This can happend few minuts after boot, or several days after.
  Yet I have not been able to find what triggers the failure. It happends at 
any time during normal usage of the computer, including during the usb usage.

  more concrete infos:
  after failure, I get
  $ dmesg

  [ 2671.894099] perf: interrupt took too long (2512 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79500
  [ 3262.197917] xhci_hcd :03:00.3: Mismatch between completed Set TR Deq 
Ptr command & xHCI internal state.
  [ 3262.197927] xhci_hcd :03:00.3: e

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

2020-12-21 Thread Rex Tsai

It seems the V3 patch[1] is merged[2]. Is that patch enough to address
the problem we have?


[1] [v3] PCI: vmd: Offset Client VMD MSI-X vectors - Patchwork - 
https://patchwork.kernel.org/project/linux-pci/patch/20200914190128.5114-1-jonathan.derr...@intel.com/
[2] PCI: vmd: Offset Client VMD MSI-X vectors · torvalds/linux@f6b7bb8 - 
https://github.com/torvalds/linux/commit/f6b7bb847ca821a8aaa1b6da10ee65311e6f15bf

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Confirmed
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.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

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

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

Title:
  Touchpad suddenly stopped working and frequent frezzing of display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Acer swift3.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vishal 3996 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 16:09:27 2020
  MachineType: Acer Swift SF314-55G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a68fb301-a2a9-458a-b35d-cacea900e74d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Default string
  dmi.board.name: MILLER_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.07:bd12/24/2018:svnAcer:pnSwiftSF314-55G:pvrV1.07:rvnWL:rnMILLER_WL:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-55G
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1908893] [NEW] Touchpad suddenly stopped working and frequent frezzing of display

2020-12-21 Thread VISHAL KUMAR

Public bug reported:

I am using Acer swift3.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-58-generic 5.4.0-58.64
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vishal 3996 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 21 16:09:27 2020
MachineType: Acer Swift SF314-55G
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a68fb301-a2a9-458a-b35d-cacea900e74d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-58-generic N/A
 linux-backports-modules-5.4.0-58-generic  N/A
 linux-firmware1.187.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.07
dmi.board.asset.tag: Default string
dmi.board.name: MILLER_WL
dmi.board.vendor: WL
dmi.board.version: V1.07
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.07
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.07:bd12/24/2018:svnAcer:pnSwiftSF314-55G:pvrV1.07:rvnWL:rnMILLER_WL:rvrV1.07:cvnAcer:ct10:cvrV1.07:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-55G
dmi.product.sku: 
dmi.product.version: V1.07
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug focal

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1908893/+attachment/5445472/+files/devices

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

Title:
  Touchpad suddenly stopped working and frequent frezzing of display

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Acer swift3.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vishal 3996 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 16:09:27 2020
  MachineType: Acer Swift SF314-55G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a68fb301-a2a9-458a-b35d-cacea900e74d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Default string
  dmi.board.name: MILLER_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.07:bd12/24/2018:svnAcer:pnSwiftSF314-55G:pvrV1.07:rvnWL:rnMILLER_WL:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-55G
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] ERROR Link Training Unsuccessful

These patches have been merged into mainline via drm-next-2020-12-18 for
v5.11.

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

Title:
  failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
  Unsuccessful

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Won't Fix
Status in linux source package in Groovy:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.6 source package in Hirsute:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
  required on the host side to cover insertion loss. On such platforms the
  rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
  Repeater) non-transparent mode only, which is only supported in drm-tip
  currently. Without LTTPR support, link training may fail with following
  error messages depending on the data path configuration:

    i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
    i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  [Fix]

  Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
  ("drm/i915: Add support for LTTPR non-transparent link training mode")
  is required to fix this issue. It has been landed to drm-tip and will
  only be merged to mainline in v5.11.

  Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
  state to link training code") is included for link training functions
  prototype changes.

  [Test Case]

  On Dell OptiPlex and WD19 docking station, use following steps to verify:
  1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
  2. attach OptiPlex's power cord
  3. attach WD19's power cord
  4. attach DP to WD19
  5. attach WD19 to OptiPlex
  6. boot up and check if boot to GUI directly
  7. `dmesg` and check if aforementioned DRM link training error appears

  [Where problems could occur]

  The second patchset pulled for dependency doesn't have too much
  effective changes but refactoring some translation functions, so very
  unlikely to have regressions.

  For the major part, LTTPR support, when LTTPR is either not detected or
  not supported, it will fall back to use transparent mode as it was.
  Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
  link training, so this should be the right way to have best hardware
  support.

  == original bug description ==

  [Summary]
  When the monitor ONLY is connected to the WD19 (DP port) and WD19 is 
connected to the type c port than boot the machine, the monitor shows no video 
output after loaded i915.

  [Reproduce Steps]
  1. connect power cable of WD19
  2. connect DP cable from monitor to WD19
  3. connect power cable to target system.
  4. connect type c cable from WD19 to target system
  5. boot up

  [Results]
  Expected: video output as there is only one monitor connected.
  Actual: No video output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
  ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
  Uname: Linux 5.6.0-1033-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov 12 05:11:11 2020
  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-metapod+X40
  InstallationDate: Installed on 2020-11-03 (9 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-signed-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

As 5.8.0-34-generic, 5.10.0-9-generic are still affected, and so is
5.10-1008-oem.

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

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

** Changed in: linux-oem-5.10 (Ubuntu Groovy)
   Status: New => Invalid

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

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Confirmed
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.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

2020-12-21 Thread Sean Young

Thanks for that. It looks like on 5.8.8 it has not loaded the rc keymap
at all. It looks like a default mce keymap with the default rc-6
protocol enabled.

So for some reason /etc/rc_map.cfg did not get processed at all. That's
super odd. Let's try and  see what udevd does when you plug in the
device. On 5.8.8 As root, run:

udevadm control -l debug
journalctl -u systemd-udevd.service -f

Now plug in the device. There _should_ be some lines about ir-keytable.

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

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 1908885] Re: Fix drm_WARN_ON(common_len <= 0)

** Tags added: oem-priority originate-from-1898737 somerville

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => koba (kobako)

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

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

Title:
  Fix drm_WARN_ON(common_len <= 0)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]

  The TGL machine could show drm_WARN_ON(common_len <= 0) when connect with the 
TBT dock(WD19TB).
  [ cut here ]
  i915 :00:02.0: drm_WARN_ON(common_len <= 0)
  WARNING: CPU: 4 PID: 194 at drivers/gpu/drm/i915/display/intel_dp.c:2385 
intel_dp_compute_link_config+0x820/0x900 [i915]
  Modules linked in: i915(+) i2c_algo_bit drm_kms_helper crc32_pclmul 
syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core nvme e1000e(+) c_i801 
ahci i2c_smbus
  thunderbolt(+) xhci_pci xhci_pci_renesas wmi video backlight 
pinctrl_tigerlake pinctrl_intel
  CPU: 4 PID: 194 Comm: systemd-udevd Not tainted 5.10.0-051000rc7-generic 
#202012062330
  Hardware name: Dell Inc. OptiPlex 7090 UFF - China HDD Protection/, BIOS 
0.6.4 11/07/2020
  RIP: 0010:intel_dp_compute_link_config+0x820/0x900 [i915]
  Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 b9 b9 60 dc 48 c7 c1 b5 6d 83 c0 
4c 89 f2 48 c7 c7 d0 69 83 c0 48 89 c6 e8 a5 84 f2 db <0f> 0b ff e9 60 f8 ff ff 
48 8b
  c2 60 04 82
  RSP: 0018:ba120061f6b0 EFLAGS: 00010282
  RAX:  RBX: 956df17c2000 RCX: 
  RDX: 002f RSI: 9e1b1dcf RDI: 0246
  RBP: ba120061f720 R08: 9e1b1da0 R09: 002f
  R10: 9e1b2180 R11: 9e1b1db2 R12: 956df1e4
  R13: 956df17c6000 R14: 956e029a99e0 R15: 956df17c6000
  FS: 7fbd08cdd880() GS:956e0e50() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: 5635d4c41678 CR3: 000271c64006 CR4: 00770ee0
  PKRU: 5554
  Call Trace:
  ? dev_printk+0x5d/0x74
  intel_dp_compute_config+0x11b/0x570 [i915]
  intel_ddi_compute_config+0x9f/0xe0 [i915]
  intel_modeset_pipe_config+0x212/0x9c0 [i915]
  intel_atomic_check+0x263/0x12c0 [i915]
  ? __drm_dbg+0x87/0x90 [drm]
  drm_atomic_check_only+0x2c7/0x450 [drm]
  drm_atomic_commit+0x18/0x50 [drm]
  intel_modeset_init_nogem+0x486/0xb10 [i915]
  i915_driver_probe+0x3e8/0x6e0 [i915]
  ? mutex_lock+0x13/0x40
  i915_pci_probe+0x5a/0x140 [i915]
  local_pci_probe+0x48/0x80
  pci_device_probe+0x10f/0x1c0
  really_probe+0x1db/0x440
  driver_probe_device+0xe9/0x160
  device_driver_attach+0x5d/0x70
  __driver_attach+0x8f/0x150
  ? device_driver_attach+0x70/0x70
  bus_for_each_dev+0x7e/0xc0
  driver_attach+0x1e/0x20
  bus_add_driver+0x152/0x1f0
  driver_register+0x74/0xd0
  __pci_register_driver+0x54/0x60
  i915_init+0x61/0x75 [i915]
  ? 0xc08a1000
  do_one_initcall+0x4a/0x1fa
  ? _cond_resched+0x19/0x30
  ? kmem_cache_alloc_trace+0x17e/0x2f0
  do_init_module+0x62/0x240
  load_module+0xfbe/0x11e0
  __do_sys_finit_module+0xbe/0x120
  ? __do_sys_finit_module+0xbe/0x120
  __x64_sys_finit_module+0x1a/0x20
  do_syscall_64+0x38/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fbd0925f89d
  Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 73 01 c3 48 8b 0d 
c3 f5 0c 00 f7 d8 64 89 01 48
  RSP: 002b:7fffa60dc628 EFLAGS: 0246 ORIG_RAX: 0139
  RAX: ffda RBX: 5635d4c942b0 RCX: 7fbd0925f89d
  RDX:  RSI: 7fbd0913cded RDI: 0014
  RBP: 0002 R08:  R09: 
  R10: 0014 R11: 0246 R12: 7fbd0913cded
  R13:  R14: 5635d4c92b70 R15: 5635d4c942b0
  ---[ end trace c48f367c543f3384 ]-—

  [Fix]

  Kernel driver patchset https://patchwork.freedesktop.org/series/82173/
  targeting v5.11.

  [Test Case]

  1. Boot with kernel built with these patches applied.
  2. check the dmesg.

  [Where problems could occur]

  The fix could resolve the drm_WARN_ON.
  It ease the symptom that can't output the video with the TBT dock(WD19TB) at 
the first boot, but it may not fix.

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

-- 
Mailing

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

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 1908885

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

** Changed in: linux (Ubuntu Focal)
   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/1908885

Title:
  Fix drm_WARN_ON(common_len <= 0)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]

  The TGL machine could show drm_WARN_ON(common_len <= 0) when connect with the 
TBT dock(WD19TB).
  [ cut here ]
  i915 :00:02.0: drm_WARN_ON(common_len <= 0)
  WARNING: CPU: 4 PID: 194 at drivers/gpu/drm/i915/display/intel_dp.c:2385 
intel_dp_compute_link_config+0x820/0x900 [i915]
  Modules linked in: i915(+) i2c_algo_bit drm_kms_helper crc32_pclmul 
syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core nvme e1000e(+) c_i801 
ahci i2c_smbus
  thunderbolt(+) xhci_pci xhci_pci_renesas wmi video backlight 
pinctrl_tigerlake pinctrl_intel
  CPU: 4 PID: 194 Comm: systemd-udevd Not tainted 5.10.0-051000rc7-generic 
#202012062330
  Hardware name: Dell Inc. OptiPlex 7090 UFF - China HDD Protection/, BIOS 
0.6.4 11/07/2020
  RIP: 0010:intel_dp_compute_link_config+0x820/0x900 [i915]
  Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 b9 b9 60 dc 48 c7 c1 b5 6d 83 c0 
4c 89 f2 48 c7 c7 d0 69 83 c0 48 89 c6 e8 a5 84 f2 db <0f> 0b ff e9 60 f8 ff ff 
48 8b
  c2 60 04 82
  RSP: 0018:ba120061f6b0 EFLAGS: 00010282
  RAX:  RBX: 956df17c2000 RCX: 
  RDX: 002f RSI: 9e1b1dcf RDI: 0246
  RBP: ba120061f720 R08: 9e1b1da0 R09: 002f
  R10: 9e1b2180 R11: 9e1b1db2 R12: 956df1e4
  R13: 956df17c6000 R14: 956e029a99e0 R15: 956df17c6000
  FS: 7fbd08cdd880() GS:956e0e50() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: 5635d4c41678 CR3: 000271c64006 CR4: 00770ee0
  PKRU: 5554
  Call Trace:
  ? dev_printk+0x5d/0x74
  intel_dp_compute_config+0x11b/0x570 [i915]
  intel_ddi_compute_config+0x9f/0xe0 [i915]
  intel_modeset_pipe_config+0x212/0x9c0 [i915]
  intel_atomic_check+0x263/0x12c0 [i915]
  ? __drm_dbg+0x87/0x90 [drm]
  drm_atomic_check_only+0x2c7/0x450 [drm]
  drm_atomic_commit+0x18/0x50 [drm]
  intel_modeset_init_nogem+0x486/0xb10 [i915]
  i915_driver_probe+0x3e8/0x6e0 [i915]
  ? mutex_lock+0x13/0x40
  i915_pci_probe+0x5a/0x140 [i915]
  local_pci_probe+0x48/0x80
  pci_device_probe+0x10f/0x1c0
  really_probe+0x1db/0x440
  driver_probe_device+0xe9/0x160
  device_driver_attach+0x5d/0x70
  __driver_attach+0x8f/0x150
  ? device_driver_attach+0x70/0x70
  bus_for_each_dev+0x7e/0xc0
  driver_attach+0x1e/0x20
  bus_add_driver+0x152/0x1f0
  driver_register+0x74/0xd0
  __pci_register_driver+0x54/0x60
  i915_init+0x61/0x75 [i915]
  ? 0xc08a1000
  do_one_initcall+0x4a/0x1fa
  ? _cond_resched+0x19/0x30
  ? kmem_cache_alloc_trace+0x17e/0x2f0
  do_init_module+0x62/0x240
  load_module+0xfbe/0x11e0
  __do_sys_finit_module+0xbe/0x120
  ? __do_sys_finit_module+0xbe/0x120
  __x64_sys_finit_module+0x1a/0x20
  do_syscall_64+0x38/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fbd0925f89d
  Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 73 01 c3 48 8b 0d 
c3 f5 0c 00 f7 d8 64 89 01 48
  RSP: 002b:7fffa60dc628 EFLAGS: 0246 ORIG_RAX: 0139
  RAX: ffda RBX: 5635d4c942b0 RCX: 7fbd0925f89d
  RDX:  RSI: 7fbd0913cded RDI: 0014
  RBP: 0002 R08:  R09: 
  R10: 0014 R11: 0246 R12: 7fbd0913cded
  R13:  R14: 5635d4c92b70 R15: 5635d4c942b0
  ---[ end trace c48f367c543f3384 ]-—

  [Fix]

  Kernel driver patchset https://patchwork.freedesktop.org/series/82173/
  targeting v5.11.

  [Test Case]

  1. Boot with kernel built with these patches applied.
  2. check the dmesg.

  [Where problems could occur]

  The fix could re

[Kernel-packages] [Bug 1908885] [NEW] Fix drm_WARN_ON(common_len <= 0)

Public bug reported:

[Impact]

The TGL machine could show drm_WARN_ON(common_len <= 0) when connect with the 
TBT dock(WD19TB).
[ cut here ]
i915 :00:02.0: drm_WARN_ON(common_len <= 0)
WARNING: CPU: 4 PID: 194 at drivers/gpu/drm/i915/display/intel_dp.c:2385 
intel_dp_compute_link_config+0x820/0x900 [i915]
Modules linked in: i915(+) i2c_algo_bit drm_kms_helper crc32_pclmul syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core nvme e1000e(+) c_i801 ahci 
i2c_smbus
thunderbolt(+) xhci_pci xhci_pci_renesas wmi video backlight pinctrl_tigerlake 
pinctrl_intel
CPU: 4 PID: 194 Comm: systemd-udevd Not tainted 5.10.0-051000rc7-generic 
#202012062330
Hardware name: Dell Inc. OptiPlex 7090 UFF - China HDD Protection/, BIOS 0.6.4 
11/07/2020
RIP: 0010:intel_dp_compute_link_config+0x820/0x900 [i915]
Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 b9 b9 60 dc 48 c7 c1 b5 6d 83 c0 
4c 89 f2 48 c7 c7 d0 69 83 c0 48 89 c6 e8 a5 84 f2 db <0f> 0b ff e9 60 f8 ff ff 
48 8b
c2 60 04 82
RSP: 0018:ba120061f6b0 EFLAGS: 00010282
RAX:  RBX: 956df17c2000 RCX: 
RDX: 002f RSI: 9e1b1dcf RDI: 0246
RBP: ba120061f720 R08: 9e1b1da0 R09: 002f
R10: 9e1b2180 R11: 9e1b1db2 R12: 956df1e4
R13: 956df17c6000 R14: 956e029a99e0 R15: 956df17c6000
FS: 7fbd08cdd880() GS:956e0e50() knlGS:
CS: 0010 DS:  ES:  CR0: 80050033
CR2: 5635d4c41678 CR3: 000271c64006 CR4: 00770ee0
PKRU: 5554
Call Trace:
? dev_printk+0x5d/0x74
intel_dp_compute_config+0x11b/0x570 [i915]
intel_ddi_compute_config+0x9f/0xe0 [i915]
intel_modeset_pipe_config+0x212/0x9c0 [i915]
intel_atomic_check+0x263/0x12c0 [i915]
? __drm_dbg+0x87/0x90 [drm]
drm_atomic_check_only+0x2c7/0x450 [drm]
drm_atomic_commit+0x18/0x50 [drm]
intel_modeset_init_nogem+0x486/0xb10 [i915]
i915_driver_probe+0x3e8/0x6e0 [i915]
? mutex_lock+0x13/0x40
i915_pci_probe+0x5a/0x140 [i915]
local_pci_probe+0x48/0x80
pci_device_probe+0x10f/0x1c0
really_probe+0x1db/0x440
driver_probe_device+0xe9/0x160
device_driver_attach+0x5d/0x70
__driver_attach+0x8f/0x150
? device_driver_attach+0x70/0x70
bus_for_each_dev+0x7e/0xc0
driver_attach+0x1e/0x20
bus_add_driver+0x152/0x1f0
driver_register+0x74/0xd0
__pci_register_driver+0x54/0x60
i915_init+0x61/0x75 [i915]
? 0xc08a1000
do_one_initcall+0x4a/0x1fa
? _cond_resched+0x19/0x30
? kmem_cache_alloc_trace+0x17e/0x2f0
do_init_module+0x62/0x240
load_module+0xfbe/0x11e0
__do_sys_finit_module+0xbe/0x120
? __do_sys_finit_module+0xbe/0x120
__x64_sys_finit_module+0x1a/0x20
do_syscall_64+0x38/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7fbd0925f89d
Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 73 01 c3 48 8b 0d 
c3 f5 0c 00 f7 d8 64 89 01 48
RSP: 002b:7fffa60dc628 EFLAGS: 0246 ORIG_RAX: 0139
RAX: ffda RBX: 5635d4c942b0 RCX: 7fbd0925f89d
RDX:  RSI: 7fbd0913cded RDI: 0014
RBP: 0002 R08:  R09: 
R10: 0014 R11: 0246 R12: 7fbd0913cded
R13:  R14: 5635d4c92b70 R15: 5635d4c942b0
---[ end trace c48f367c543f3384 ]-—

[Fix]

Kernel driver patchset https://patchwork.freedesktop.org/series/82173/
targeting v5.11.

[Test Case]

1. Boot with kernel built with these patches applied.
2. check the dmesg.

[Where problems could occur]

The fix could resolve the drm_WARN_ON.
It ease the symptom that can't output the video with the TBT dock(WD19TB) at 
the first boot, but it may not fix.

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

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

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

** Affects: linux-oem-5.10 (Ubuntu Focal)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

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

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

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

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

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

** Description changed:

  [Impact]
  
  The TGL machine could show drm_WARN_ON(common_len <= 0) when connect with the 
TBT dock(WD19TB).
  [ cut here ]
  i915 :00:02.0: drm_WARN_ON(common_len <= 0)
  WARNING: CPU: 4 PID: 194 at drivers/gpu/drm/i915/display/intel_dp.c:2385 
intel_dp_compute_link_config+0x820/0x900 [i915]
  Modules linked in: i915(+) i2c_algo_bit drm_kms_helper crc32_pclmul 
syscopyarea sysfillrect sys

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

2020-12-21 Thread Piotr Tomaszewski

@Robin Windey (r0wi), I will try it. Thanks for the info

-- 
You 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
  ApportVersion: 2

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

i have also already asked the ubuntu-devs  
they only take upstream patches and leave the users in the rain

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, 
PASSIVE-SCAN
   (5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW,

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

there are other ways

-   reg->current_rd = 0x64;
+   reg->current_rd = 0x6c;

0x64 is the most restrictive domain and there the complete midband is missing
0x6c means world wide regdomain

and if you really want to use the cards without any restrictions then
the openwrt patch

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLU

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

@Piotr Tomaszewski (nfm886) i just installed headers (all), image
(generic) and modules (generic) from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.10.1/amd64/ via 'dpkg -i *.deb', rebooted with new
kernel 5.10.1 and everything worked. So no special config or parameter
tweaking was necessary for me.

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

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

2020-12-21 Thread Piotr Tomaszewski

@Robin Windey (r0wi), Hey, did you did something more like adding kernel
parameters or something, or just upgrade kernel is enough?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 15

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

This patch was not accepted by upstream per
https://www.spinics.net/lists/linux-pci/msg98817.html . Need to check if
there is another fix.

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
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:
  In Progress
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]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
   cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)

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

Bug description:
  linux-image-generic-hwe-20.04

  hello,

  since the update to Ubuntu 20.04.1 I can no longer change the
  regulatory domain of my QCA9984 cards.

  This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.

  Or if I build the kernel modules myself .. ("Atheros dynamic user
  regulatory testing")

  The card has "World" in the EEPROM and is sold worldwide.

  [2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate 
crc32 ea4c0777
  [4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
  [7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
  [7.149519] ath: EEPROM regdomain: 0x0
  [7.149520] ath: EEPROM indicates default country code should be used
  [7.149520] ath: doing EEPROM country->regdmn map search
  [7.149521] ath: country maps to regdmn code: 0x3a
  [7.149521] ath: Country alpha2 being used: US
  [7.149521] ath: Regpair used: 0x3a
  [7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp 
max-sta 512 raw 0 hwcrypto 1
  [7.297494] ath: EEPROM regdomain: 0x0
  [7.297495] ath: EEPROM indicates default country code should be used
  [7.297495] ath: doing EEPROM country->regdmn map search
  [7.297496] ath: country maps to regdmn code: 0x3a
  [7.297496] ath: Country alpha2 being used: US
  [7.297497] ath: Regpair used: 0x3a

  The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )

  global
  country DE: DFS-ETSI
   (2400 - 2483 @ 40), (N/A, 20), (N/A)
   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
   (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
   (5725 - 5875 @ 80), (N/A, 13), (N/A)
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  phy#1
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#0
  country US: DFS-FCC
   (2402 - 2472 @ 40), (N/A, 30), (N/A)
   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
   (5735 - 5835 @ 80), (N/A, 30), (N/A)
   (57240 - 63720 @ 2160), (N/A, 40), (N/A)

  phy#2 (self-managed)
  country DE: DFS-UNSET
   (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
   (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
   (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
   (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
   (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
   (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, 
PASSIVE-SCAN
   (5270 - 5290 @ 80), (

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