[Kernel-packages] [Bug 2038876] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned e

2023-10-09 Thread chopra
Public bug reported:

I have made an older version of the kernel immutable to prevent its
deletion, because the newer kernels will not boot. This has the side
effect of preventing hardlinks, which caused an error message. I don't
know if this is related.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.19
ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kevin  4659 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Mon Oct  9 21:45:10 2023
Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2022-04-01 (556 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Dynabook Inc. dynabook TECRA A50-F
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=1306d535-dd60-4b0c-91b2-d152242759e3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
SourcePackage: linux-firmware
Title: package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2023-07-05 (96 days ago)
dmi.bios.date: 06/21/2021
dmi.bios.release: 2.50
dmi.bios.vendor: Dynabook Inc.
dmi.bios.version: Version 2.50
dmi.board.asset.tag: 00
dmi.board.name: A0105/
dmi.board.vendor: Dynabook Inc.
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: Dynabook Inc.
dmi.chassis.version: Version 1.0
dmi.ec.firmware.release: 1.90
dmi.modalias: 
dmi:bvnDynabookInc.:bvrVersion2.50:bd06/21/2021:br2.50:efr1.90:svnDynabookInc.:pndynabookTECRAA50-F:pvrPT5B1U-01K006:rvnDynabookInc.:rnA0105/:rvrVersionA0:cvnDynabookInc.:ct10:cvrVersion1.0:skuPT5B1U:
dmi.product.family: dynabook TECRA
dmi.product.name: dynabook TECRA A50-F
dmi.product.sku: PT5B1U
dmi.product.version: PT5B1U-01K006
dmi.sys.vendor: Dynabook Inc.

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to
  install/upgrade: installed linux-firmware package post-installation
  script subprocess returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have made an older version of the kernel immutable to prevent its
  deletion, because the newer kernels will not boot. This has the side
  effect of preventing hardlinks, which caused an error message. I don't
  know if this is related.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin  4659 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Mon Oct  9 21:45:10 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-01 (556 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dynabook Inc. dynabook TECRA A50-F
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=1306d535-dd60-4b0c-91b2-d152242759e3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: linux-firmware
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.19 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2023-07-05 (96 days ago)
  dmi.bios.date: 

[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload

2021-02-02 Thread Manish Chopra
Hi Matthew,

We have verified the fix with proposed kernel.
I hope that I have corrected the "tags" appropriately.

Thanks,
Manish

** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy

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

Title:
  qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not
  supporting IPIP tx csum offload

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

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

  [Impact]

  For users with QLogic QL41xxx series NICs, such as the FastLinQ
  QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the
  4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will
  fail, due to these packets getting corrupted.

  Kubernetes uses IPIP tunnelled packets for internal DNS resolution,
  and this particular packet type is not supported for hardware tx
  checksum offload, and the packets end up corrupted when the qede
  driver attempts to checksum them.

  This only affects internal Kubernetes DNS, as regular DNS lookups to
  regular external domains will succeed, due to them not using IPIP
  packet types.

  [Fix]

  Marvell has developed a fix for the qede driver, which checks the
  packet type, and if it is IPPROTO_IPIP, then csum offloads are
  disabled for socket buffers of type IPIP.

  commit 5d5647dad259bb416fd5d3d87012760386d97530
  Author: Manish Chopra 
  Date: Mon Dec 21 06:55:30 2020 -0800
  Subject: qede: fix offload for IPIP tunnel packets
  Link: 
https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530

  This commit landed in mainline in 5.11-rc3. The commit was accepted
  into upstream stable 4.14.215, 4.19.167, 5.4.89 and 5.10.7.

  Note, this SRU isn't targeted for Bionic due to tx csum offload
  support only landing in 5.0 and onward, meaning the 4.15 kernel still
  works even without this patch. Because of this, Bionic can pick the
  patch up naturally from upstream stable.

  [Testcase]

  The system must have a QLogic QL41xxx series NIC fitted, and needs to
  be a part of a Kubernetes cluster.

  Firstly, get a list of all devices in the system:

  $ sudo ifconfig

  Next, set all devices down with:

  $ sudo ifconfig  down

  Next, bring up the QLogic QL41xxx device:

  $ sudo ifconfig  up

  Then, attempt to lookup an internal Kubernetes domain:

  $ nslookup 

  Without the patch, the connection will time out:

  ;; connection timed out; no servers could be reached

  If we look at packet traces with tcpdump, we see it leaves the source,
  but never arrives at the destination.

  There is a test kernel available in the following ppa:

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

  If you install it, then Kubernetes internal DNS lookups will succeed.

  [Where problems could occur]

  If a regression were to occur, then users of the qede driver would be
  affected. This is limited to those with QLogic QL41xxx series NICs.
  The patch explicitly checks for IPIP type packets, so only those
  particular packets would be affected.

  Since IPIP type packets are uncommon, it would not cause a total
  outage on regression, since most packets are not IPIP tunnelled. It
  could potentially cause problems for users who frequently handle VPN
  or Kubernetes internal DNS traffic.

  A workaround would be to use ethtool to disable tx csum offload for
  all packet types, or to revert to an older kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+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 1909062] Re: Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure

2020-12-25 Thread Manish Chopra
** Description changed:

- Customer is reporting a problem with QL41xxx and Ubuntu internal DNS
- server. The issue appeared when the customer updated to the latest
- Ubuntu kernel 20.04.1 LTS version 5.4.0-52-generic. Issue was not
- observed with 4.5 ubuntu-linux.
+ With QL41xxx and Ubuntu DNS server DNS failures are seen when updated to
+ the latest Ubuntu kernel 20.04.1 LTS version 5.4.0-52-generic. Issue was
+ not observed with 4.5 ubuntu-linux.
  
  Problem Definition:
- 
- Product: PowerEdge R740xd
- Serial: C7J90W2
- Hostname: xkubmin1r12
  OS Version: /etc/os-release shows Ubuntu 18.04.4 LTS, but Booted kernel is 
the latest Ubuntu 20.04.1 LTS version 5.4.0-52-generic
  NIC: 2 dual-port (4) QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE 
Controller [1077:8070] (rev 02)
- Firmware: 15.15.11
  Inbox driver qede v8.37.0.20
  
- 
- Completed Detailed Problem Description:
+ Complete Detailed Problem Description:
  Anything that uses the internal Kubernetes DNS server fails. If an external 
DNS server is used resolution works for non-Kubernetes IPs.
  
- Customer is experiencing the same issue described in this article.
+ Similar issue is described in this article.
  https://github.com/kubernetes/kubernetes/issues/95365
- 
- Customer Impact: Production site
- The QLogic Nic 41262 is their main nic for all of their 14G environment 
thousands of servers. Unclear how many of those hosts are Kubernetes, but the 
point is they want the QL41000 to work since it is very prevalent in the entire 
environment.
  
  Below patch recently on upstream fixes this -
  [Note that issue was introduced by driver's tunnel offload support which was 
added in after 4.5 kernel]
  
  commit 5d5647dad259bb416fd5d3d87012760386d97530
  Author: Manish Chopra 
  Date:   Mon Dec 21 06:55:30 2020 -0800
  
- qede: fix offload for IPIP tunnel packets
+ qede: fix offload for IPIP tunnel packets
  
- IPIP tunnels packets are unknown to device,
- hence these packets are incorrectly parsed and
- caused the packet corruption, so disable offlods
- for such packets at run time.
+ IPIP tunnels packets are unknown to device,
+ hence these packets are incorrectly parsed and
+ caused the packet corruption, so disable offlods
+ for such packets at run time.
  
- Signed-off-by: Manish Chopra 
- Signed-off-by: Sudarsana Kalluru 
- Signed-off-by: Igor Russkikh 
- Link: https://lore.kernel.org/r/20201221145530.7771-1-mani...@marvell.com
- Signed-off-by: Jakub Kicinski 
- 
+ Signed-off-by: Manish Chopra 
+ Signed-off-by: Sudarsana Kalluru 
+ Signed-off-by: Igor Russkikh 
+ Link: https://lore.kernel.org/r/20201221145530.7771-1-mani...@marvell.com
+ Signed-off-by: Jakub Kicinski 
  
  Thanks,
  Manish

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

Title:
  Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS
  failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With QL41xxx and Ubuntu DNS server DNS failures are seen when updated
  to the latest Ubuntu kernel 20.04.1 LTS version 5.4.0-52-generic.
  Issue was not observed with 4.5 ubuntu-linux.

  Problem Definition:
  OS Version: /etc/os-release shows Ubuntu 18.04.4 LTS, but Booted kernel is 
the latest Ubuntu 20.04.1 LTS version 5.4.0-52-generic
  NIC: 2 dual-port (4) QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE 
Controller [1077:8070] (rev 02)
  Inbox driver qede v8.37.0.20

  Complete Detailed Problem Description:
  Anything that uses the internal Kubernetes DNS server fails. If an external 
DNS server is used resolution works for non-Kubernetes IPs.

  Similar issue is described in this article.
  https://github.com/kubernetes/kubernetes/issues/95365

  Below patch recently on upstream fixes this -
  [Note that issue was introduced by driver's tunnel offload support which was 
added in after 4.5 kernel]

  commit 5d5647dad259bb416fd5d3d87012760386d97530
  Author: Manish Chopra 
  Date:   Mon Dec 21 06:55:30 2020 -0800

  qede: fix offload for IPIP tunnel packets

  IPIP tunnels packets are unknown to device,
  hence these packets are incorrectly parsed and
  caused the packet corruption, so disable offlods
  for such packets at run time.

  Signed-off-by: Manish Chopra 
  Signed-off-by: Sudarsana Kalluru 
  Signed-off-by: Igor Russkikh 
  Link: https://lore.kernel.org/r/20201221145530.7771-1-mani...@marvell.com
  Signed-off-by: Jakub Kicinski 

  Thanks,
  Manish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+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 1909062] Re: Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure

2020-12-22 Thread Manish Chopra
We don't have any logs to post, attached wire traces which we got from
customer as we were only interested in that. Having said that, this bug
is resolved with the above fix posted upstream, I guess we don't need
any further logs.

** Attachment added: "wire_traces.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+attachment/5446099/+files/wire_traces.zip

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

Title:
  Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS
  failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Customer is reporting a problem with QL41xxx and Ubuntu internal DNS
  server. The issue appeared when the customer updated to the latest
  Ubuntu kernel 20.04.1 LTS version 5.4.0-52-generic. Issue was not
  observed with 4.5 ubuntu-linux.

  Problem Definition:

  Product: PowerEdge R740xd
  Serial: C7J90W2
  Hostname: xkubmin1r12
  OS Version: /etc/os-release shows Ubuntu 18.04.4 LTS, but Booted kernel is 
the latest Ubuntu 20.04.1 LTS version 5.4.0-52-generic
  NIC: 2 dual-port (4) QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE 
Controller [1077:8070] (rev 02)
  Firmware: 15.15.11
  Inbox driver qede v8.37.0.20

  
  Completed Detailed Problem Description:
  Anything that uses the internal Kubernetes DNS server fails. If an external 
DNS server is used resolution works for non-Kubernetes IPs.

  Customer is experiencing the same issue described in this article.
  https://github.com/kubernetes/kubernetes/issues/95365

  Customer Impact: Production site
  The QLogic Nic 41262 is their main nic for all of their 14G environment 
thousands of servers. Unclear how many of those hosts are Kubernetes, but the 
point is they want the QL41000 to work since it is very prevalent in the entire 
environment.

  Below patch recently on upstream fixes this -
  [Note that issue was introduced by driver's tunnel offload support which was 
added in after 4.5 kernel]

  commit 5d5647dad259bb416fd5d3d87012760386d97530
  Author: Manish Chopra 
  Date:   Mon Dec 21 06:55:30 2020 -0800

  qede: fix offload for IPIP tunnel packets

  IPIP tunnels packets are unknown to device,
  hence these packets are incorrectly parsed and
  caused the packet corruption, so disable offlods
  for such packets at run time.

  Signed-off-by: Manish Chopra 
  Signed-off-by: Sudarsana Kalluru 
  Signed-off-by: Igor Russkikh 
  Link: https://lore.kernel.org/r/20201221145530.7771-1-mani...@marvell.com
  Signed-off-by: Jakub Kicinski 

  
  Thanks,
  Manish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+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 1389052] Re: at-spi2-registryd main process ended, respawning

2015-02-22 Thread chopra
This appears to be affecting me as well. No adverse effects noticed so far, it 
just gives me the same message you posted in the .xsession-errors file.
Using 14.10, unity desktop, installed a week ago.

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

Title:
  at-spi2-registryd main process ended, respawning

Status in linux package in Ubuntu:
  Expired

Bug description:
  In my current .xession-errors I spotted this

  $ tail .xsession-errors
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning
  upstart: at-spi2-registryd main process ended, respawning

  Worrying about that. What does it mean and how can we fix this? Thanks
  for your help!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael-heuberger   2178 F pulseaudio
   /dev/snd/controlC2:  michael-heuberger   2178 F pulseaudio
   /dev/snd/controlC0:  michael-heuberger   2178 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov  4 15:54:28 2014
  HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028
  InstallationDate: Installed on 2014-10-31 (3 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1389052/+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