[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-30 Thread Heinrich Schuchardt
With ubuntu-x13s-settings installed I can boot into kernel
6.8.0-31-generic.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2016881] Re: zfs-linux FTBFS for riscv64 on Focal

2024-04-25 Thread Heinrich Schuchardt
I would suggest not to invest in enabling a new feature in Focal now
that we have two newer LTS releases. Setting to won't fix.

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

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

Title:
  zfs-linux FTBFS for riscv64 on Focal

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in zfs-linux source package in Focal:
  Won't Fix

Bug description:
  [Impact]
   * riscv64 builds fail completely, so users on that architecture can't use 
ZFS.

  [Test Plan]
   * Build zfs-linux on target architecture. No test failure is expected.

  [Where problems could occur]
   * Test failures and bugs that are exclusive to RISCV64 might show up

  [Other Info]
   * Upstream introduced support riscv64 with 4254e407294b
   * Builds succeed on Jammy and newer, Focal is missing the enablement patch

  --
  [Original Description]
  Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single patch 
missing: 
https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-24 Thread Heinrich Schuchardt
@glathe

We used to have packate linux-image-laptop-23.10 which provided file
/usr/share/initramfs-tools/modules.d/laptop. This contained
qcom_q6v5_pas.  It have recreated this file manually but this does not
resolve my problems.

Which follow up package provided with the X13s installer image defines
the modules to be included in the initrd?

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

2024-04-24 Thread Heinrich Schuchardt
On my LicheeRV Dock it dos not work for me with HDMI plugged in at
start. I just get

[   67.521944] sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY
[   67.613930] sun4i-drm display-engine: Couldn't bind all pipelines components

and no output. On the Nezha D1 I did not have this issue.

When Alexandre wrote the tests it was explicitly foreseen to plug in
HDMI after login. So this must have worked previously.

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2063309] Re: RISC-V: nouveau 0000:05:00.0: timer: stalled at ffffffffffffffff

2024-04-24 Thread Heinrich Schuchardt
When connected before boot the HDMI output works fine.

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

Title:
  RISC-V: nouveau :05:00.0: timer: stalled at 

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  After connecting a monitor to an SiFive HiFive Unmatched board running
  kernel 6.8.0-28-generic I saw:

  nouveau :05:00.0: timer: stalled at 
  nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-28-generic 6.8.0-28.28.1
  ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1
  Uname: Linux 6.8.0-28-generic riscv64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20210714
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Wed Apr 24 09:43:12 2024
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2063309/+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 2063309] [NEW] RISC-V: nouveau 0000:05:00.0: timer: stalled at ffffffffffffffff

2024-04-24 Thread Heinrich Schuchardt
Public bug reported:

After connecting a monitor to an SiFive HiFive Unmatched board running
kernel 6.8.0-28-generic I saw:

nouveau :05:00.0: timer: stalled at 
nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-28-generic 6.8.0-28.28.1
ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1
Uname: Linux 6.8.0-28-generic riscv64
ApportVersion: 2.28.1-0ubuntu2
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20210714
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Wed Apr 24 09:43:12 2024
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug cloud-image noble riscv64

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

Title:
  RISC-V: nouveau :05:00.0: timer: stalled at 

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  After connecting a monitor to an SiFive HiFive Unmatched board running
  kernel 6.8.0-28-generic I saw:

  nouveau :05:00.0: timer: stalled at 
  nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-28-generic 6.8.0-28.28.1
  ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1
  Uname: Linux 6.8.0-28-generic riscv64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20210714
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Wed Apr 24 09:43:12 2024
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2063309/+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 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

2024-04-24 Thread Heinrich Schuchardt
With 6.8.0-31-generic I am not able to get any HDMI output on the Nezha D1 
either.
Unplugging and reconnecting did not help.

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2063300] Re: On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected

2024-04-24 Thread Heinrich Schuchardt
The problem did not occur on every boot.

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

Title:
  On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not
  detected

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
  after reconnecting the USB Hub. It should have been detected while
  booting.

  $ lsusb -t
  /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  |__ Port 001: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M
  |__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M
  |__ Port 004: Dev 010, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
  /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  /:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M

  $ dmesg | grep -i usb
  [0.200341] usbcore: registered new interface driver usbfs
  [0.200487] usbcore: registered new interface driver hub
  [0.200635] usbcore: registered new device driver usb
  [   54.280232] ehci-platform 420.usb: EHCI Host Controller
  [   54.280305] ehci-platform 420.usb: new USB bus registered, assigned 
bus number 1
  [   54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420
  [   54.280897] ehci-platform 4101000.usb: EHCI Host Controller
  [   54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned 
bus number 2
  [   54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000
  [   54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
  [   54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.302466] usb usb1: Product: EHCI Host Controller
  [   54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.302495] usb usb1: SerialNumber: 420.usb
  [   54.312820] hub 1-0:1.0: USB hub found
  [   54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
  [   54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.329444] usb usb2: Product: EHCI Host Controller
  [   54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.329474] usb usb2: SerialNumber: 4101000.usb
  [   54.340294] hub 2-0:1.0: USB hub found
  [   54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform
  [   54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, 
bcdDevice= 1.00
  [   54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [   54.767133] usb 1-1: Product: USB2.0 HUB
  [   54.769892] hub 1-1:1.0: USB hub found
  [   55.201407] usb 1-1.2: new full-speed USB device number 3 using 
ehci-platform
  [   55.429317] usb 1-1.2: device descriptor read/all, error -32
  [   55.641464] usb 1-1.2: new full-speed USB device number 4 using 
ehci-platform
  [   55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller
  [   55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned 
bus number 3
  [   55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400
  [   55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller
  [   55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned 
bus number 4
  [   55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400
  [   55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.794158] usb usb3: Product: Generic Platform OHCI controller
  [   55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.794189] usb usb3: SerialNumber: 4101400.usb
  [   55.802158] hub 3-0:1.0: USB hub found
  [   55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.841574] usb usb4: Product: Generic Platform OHCI controller
  [   55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.841605] usb usb4: SerialNumber: 4200400.usb
  [   55.849788] hub 4-0:1.0: USB hub found
  [   57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not 
allowed for exclusive requests
  [   57.572184] musb-hdrc musb-hdrc.2.auto: MUSB HDRC host driver
  [   57.572253] musb-hdrc musb-hdrc.2.auto: new USB bus registered, assigned 
bus number 5
  [   57.650728] usb usb5: New USB device 

[Kernel-packages] [Bug 2063300] [NEW] On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected

2024-04-24 Thread Heinrich Schuchardt
Public bug reported:

A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
after reconnecting the USB Hub. It should have been detected while
booting.

$ lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
|__ Port 001: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M
|__ Port 004: Dev 010, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M

$ dmesg | grep -i usb
[0.200341] usbcore: registered new interface driver usbfs
[0.200487] usbcore: registered new interface driver hub
[0.200635] usbcore: registered new device driver usb
[   54.280232] ehci-platform 420.usb: EHCI Host Controller
[   54.280305] ehci-platform 420.usb: new USB bus registered, assigned bus 
number 1
[   54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420
[   54.280897] ehci-platform 4101000.usb: EHCI Host Controller
[   54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned bus 
number 2
[   54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000
[   54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
[   54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
[   54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   54.302466] usb usb1: Product: EHCI Host Controller
[   54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
[   54.302495] usb usb1: SerialNumber: 420.usb
[   54.312820] hub 1-0:1.0: USB hub found
[   54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
[   54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
[   54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   54.329444] usb usb2: Product: EHCI Host Controller
[   54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
[   54.329474] usb usb2: SerialNumber: 4101000.usb
[   54.340294] hub 2-0:1.0: USB hub found
[   54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform
[   54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, 
bcdDevice= 1.00
[   54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   54.767133] usb 1-1: Product: USB2.0 HUB
[   54.769892] hub 1-1:1.0: USB hub found
[   55.201407] usb 1-1.2: new full-speed USB device number 3 using ehci-platform
[   55.429317] usb 1-1.2: device descriptor read/all, error -32
[   55.641464] usb 1-1.2: new full-speed USB device number 4 using ehci-platform
[   55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller
[   55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned bus 
number 3
[   55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400
[   55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller
[   55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned bus 
number 4
[   55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400
[   55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
[   55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   55.794158] usb usb3: Product: Generic Platform OHCI controller
[   55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
[   55.794189] usb usb3: SerialNumber: 4101400.usb
[   55.802158] hub 3-0:1.0: USB hub found
[   55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
[   55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   55.841574] usb usb4: Product: Generic Platform OHCI controller
[   55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
[   55.841605] usb usb4: SerialNumber: 4200400.usb
[   55.849788] hub 4-0:1.0: USB hub found
[   57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not 
allowed for exclusive requests
[   57.572184] musb-hdrc musb-hdrc.2.auto: MUSB HDRC host driver
[   57.572253] musb-hdrc musb-hdrc.2.auto: new USB bus registered, assigned bus 
number 5
[   57.650728] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
[   57.650766] usb usb5: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   57.650784] usb usb5: Product: MUSB HDRC host driver
[   57.650799] usb usb5: Manufacturer: Linux 6.8.0-31-generic musb-hcd
[   57.650814] usb usb5: SerialNumber: musb-hdrc.2.auto
[   57.711752] hub 5-0:1.0: USB hub found
[   61.089405] usb 1-1.2: device descriptor read/64, error -71
[   66.477463] usb 1-1.2: device descriptor read/64, error 

[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

2024-04-24 Thread Heinrich Schuchardt
With 6.8.0-31-generic I am not able to get any HDMI output on the LicheeRV Dock.
Unplugging and reconnecting did not help.

[0.133313] platform 546.tcon-top: Fixed dependency cycle(s) with 
/soc/hdmi@550
[0.141438] platform 546.tcon-top: Fixed dependency cycle(s) with 
/soc/hdmi@550
[0.141784] platform 550.hdmi: Fixed dependency cycle(s) with 
/soc/tcon-top@546
[0.151475] platform 550.hdmi: Fixed dependency cycle(s) with /connector
[0.151769] platform connector: Fixed dependency cycle(s) with 
/soc/hdmi@550
[   63.119552] sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY
[   63.287954] sun8i-dw-hdmi 550.hdmi: Detected HDMI TX controller v2.12a 
with HDCP (sun8i_dw_hdmi_phy)
[   63.298653] sun8i-dw-hdmi 550.hdmi: registered DesignWare HDMI I2C bus 
driver
[   63.299605] sun4i-drm display-engine: bound 550.hdmi (ops 
sun8i_dw_hdmi_ops [sun8i_drm_hdmi])
[   72.732580] rc rc0: dw_hdmi as /devices/platform/soc/550.hdmi/rc/rc0
[   72.733035] input: dw_hdmi as 
/devices/platform/soc/550.hdmi/rc/rc0/input1

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2062548] [NEW] RISC-V: [drm] Display Core failed to initialize with v3.2.266!

2024-04-19 Thread Heinrich Schuchardt
Public bug reported:

On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:

[  +0.000917] [drm] Display Core failed to initialize with v3.2.266!
[  +0.24] Unable to handle kernel access to user memory without uaccess 
routines at virtual address 0008

A Radeon R230 works fine but that is using another firmware driver.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
Uname: Linux 6.8.0-20-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
 {
   "result": "skip"
 }
Date: Fri Apr 19 13:00:35 2024
InstallationDate: Installed on 2024-04-18 (1 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64 
(20240418)
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug noble riscv64

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

Title:
  RISC-V: [drm] Display Core failed to initialize with v3.2.266!

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:

  [  +0.000917] [drm] Display Core failed to initialize with v3.2.266!
  [  +0.24] Unable to handle kernel access to user memory without uaccess 
routines at virtual address 0008

  A Radeon R230 works fine but that is using another firmware driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
  ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
  Uname: Linux 6.8.0-20-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Apr 19 13:00:35 2024
  InstallationDate: Installed on 2024-04-18 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64 
(20240418)
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+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 2062548] Re: RISC-V: [drm] Display Core failed to initialize with v3.2.266!

2024-04-19 Thread Heinrich Schuchardt
** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+attachment/5768195/+files/dmesg.txt

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

Title:
  RISC-V: [drm] Display Core failed to initialize with v3.2.266!

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:

  [  +0.000917] [drm] Display Core failed to initialize with v3.2.266!
  [  +0.24] Unable to handle kernel access to user memory without uaccess 
routines at virtual address 0008

  A Radeon R230 works fine but that is using another firmware driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
  ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
  Uname: Linux 6.8.0-20-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Apr 19 13:00:35 2024
  InstallationDate: Installed on 2024-04-18 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64 
(20240418)
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-10 Thread Heinrich Schuchardt
-- 
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/2060868

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-10 Thread Heinrich Schuchardt
6.8.0-22-generic with earlycon=efifb stops after the output in the
appended screenshot.

** Attachment added: "sc20240410_223341.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+attachment/5763528/+files/sc20240410_223341.jpg

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] UdevDb.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] WifiSyslog.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

** Summary changed:

- Lenovo X13s fails to boot on 6.8.0-20-generic
+ Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] RfKill.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcCpuinfoMinimal.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcModules.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcCpuinfo.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcInterrupts.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lsusb-v.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2060868/+attachment/5763518/+files/Lsusb-v.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/2060868

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lsusb-t.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2060868/+attachment/5763517/+files/Lsusb-t.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/2060868

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lsusb.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] AlsaInfo.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] CurrentDmesg.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lspci.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] IwConfig.txt

2024-04-10 Thread Heinrich Schuchardt
apport information

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

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] [NEW] Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-10 Thread Heinrich Schuchardt
Public bug reported:

The last kernel that successfully boots on my Lenovo X13s system is
6.5.0-1004-laptop.

With 6.8.0-20-generic no output whatsoever is shown.
--- 
ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: arm64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:zfsdt  2886 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2023-12-12 (120 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212)
Lspci-vt:
 -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller BG5 
(DRAM-less)
 -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
 -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
MachineType: LENOVO 21BXCTO1WW
Package: linux (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcFB: 0 msmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-1004-laptop N/A
 linux-backports-modules-6.5.0-1004-laptop  N/A
 linux-firmware 20240318.git3b128b60-0ubuntu2
Tags: noble
Uname: Linux 6.5.0-1004-laptop aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
acpidump:
 
dmi.bios.date: 12/05/2023
dmi.bios.release: 1.59
dmi.bios.vendor: LENOVO
dmi.bios.version: N3HET87W (1.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version:
 SDK0T76463 WIN
 ptal8
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.23
dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
dmi.product.family: ThinkPad X13s Gen 1
dmi.product.name: 21BXCTO1WW
dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
dmi.product.version: ThinkPad X13s Gen 1
dmi.sys.vendor: LENOVO

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


** Tags: apport-collected noble

** Tags added: apport-collected noble

** Description changed:

  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.
  
  With 6.8.0-20-generic no output whatsoever is shown.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.28.0-0ubuntu1
+ Architecture: arm64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/seq:zfsdt  2886 F pipewire
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 24.04
+ InstallationDate: Installed on 2023-12-12 (120 days ago)
+ InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
+ Lspci-vt:
+  -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
+  -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
+  -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
+ MachineType: LENOVO 21BXCTO1WW
+ Package: linux (not installed)
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+ ProcFB: 0 msmdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
+ RelatedPackageVersions:
+  linux-restricted-modules-6.5.0-1004-laptop N/A
+  linux-backports-modules-6.5.0-1004-laptop  N/A
+  linux-firmware 20240318.git3b128b60-0ubuntu2
+ Tags: noble
+ Uname: Linux 6.5.0-1004-laptop aarch64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ acpidump:
+  
+ dmi.bios.date: 12/05/2023
+ dmi.bios.release: 1.59
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N3HET87W (1.59 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 21BXCTO1WW
+ dmi.board.vendor: LENOVO
+ dmi.board.version:
+  SDK0T76463 WIN
+  ptal8
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.23
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
+ dmi.product.family: ThinkPad 

[Kernel-packages] [Bug 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

2024-02-23 Thread Heinrich Schuchardt
** Package changed: linux-riscv (Ubuntu) => lxd-agent-loader (Ubuntu)

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

Title:
  lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

Status in lxd-agent-loader package in Ubuntu:
  New

Bug description:
  Starting the lxd-agent.service service fails with kernel
  6.5.0-9-generic.

  # /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
  available for device config

  [ 1239.456813] 9pnet_virtio: no channels available for device config
  Couldn't mount virtiofs or 9p, failing.

  
  The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

  Removing the 9pnet_virtio module does not resolve the issue.

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Feb 23 12:28:11 2024
  InstallationDate: Installed on 2023-12-04 (81 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 
(20231204)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+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 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

2024-02-23 Thread Heinrich Schuchardt
The installed snap version is 5.20-f3dd836.

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

Title:
  lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Starting the lxd-agent.service service fails with kernel
  6.5.0-9-generic.

  # /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
  available for device config

  [ 1239.456813] 9pnet_virtio: no channels available for device config
  Couldn't mount virtiofs or 9p, failing.

  
  The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

  Removing the 9pnet_virtio module does not resolve the issue.

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Feb 23 12:28:11 2024
  InstallationDate: Installed on 2023-12-04 (81 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 
(20231204)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2054814/+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 2054814] [NEW] lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

2024-02-23 Thread Heinrich Schuchardt
Public bug reported:

Starting the lxd-agent.service service fails with kernel
6.5.0-9-generic.

# /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
available for device config

[ 1239.456813] 9pnet_virtio: no channels available for device config
Couldn't mount virtiofs or 9p, failing.


The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

Removing the 9pnet_virtio module does not resolve the issue.

Best regards

Heinrich

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
 {
   "result": "skip"
 }
Date: Fri Feb 23 12:28:11 2024
InstallationDate: Installed on 2023-12-04 (81 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug noble riscv64

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

Title:
  lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Starting the lxd-agent.service service fails with kernel
  6.5.0-9-generic.

  # /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
  available for device config

  [ 1239.456813] 9pnet_virtio: no channels available for device config
  Couldn't mount virtiofs or 9p, failing.

  
  The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

  Removing the 9pnet_virtio module does not resolve the issue.

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Feb 23 12:28:11 2024
  InstallationDate: Installed on 2023-12-04 (81 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 
(20231204)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2054814/+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 2054325] Re: nouveau 0000:05:00.0: timeout on HiFive SiFive Unmatched

2024-02-19 Thread Heinrich Schuchardt
The error occurred with a monitor that was in a low power state.

Rebooting with the monitor powered on showed no issues.

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

Title:
  nouveau :05:00.0: timeout on HiFive SiFive Unmatched

Status in linux-riscv-6.5 package in Ubuntu:
  New

Bug description:
  Booting the SiFive Unmatched no output on the monitor was shown.
  Zillions of messages like the following were written:

  [  +0.007867] [ cut here ]
  [  +0.13] nouveau :05:00.0: timeout
  [  +0.000374] WARNING: CPU: 2 PID: 2028 at 
drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12a 
[nouveau]
  [  +0.008579] Modules linked in: tls binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_timer snd soundc>
  [  +0.000245] CPU: 2 PID: 2028 Comm: kworker/2:3 Tainted: GW  
6.5.0-17-generic #17.1.1~22.04.1-Ubuntu
  [  +0.11] Hardware name: SiFive HiFive Unmatched A00 (DT)
  [  +0.07] Workqueue: events drm_fb_helper_damage_work [drm_kms_helper]
  [  +0.000715] epc : g84_bar_flush+0x11a/0x12a [nouveau]
  [  +0.006843]  ra : g84_bar_flush+0x11a/0x12a [nouveau]
  [  +0.006368] epc : 026becf8 ra : 026becf8 sp : 
ffc80172b6c0
  [  +0.08]  gp : 822603c8 tp : ffd89ae05100 t0 : 
820bd738
  [  +0.06]  t1 :  t2 : 2d2d2d2d2d2d2d2d s0 : 
ffc80172b720
  [  +0.05]  s1 : ffd887482000 a0 :  a1 : 

  [  +0.06]  a2 :  a3 :  a4 : 

  [  +0.06]  a5 :  a6 :  a7 : 

  [  +0.05]  s2 : 0007 s3 : ffd89d6d19b8 s4 : 
00020022
  [  +0.06]  s5 : 0046 s6 : 0046 s7 : 

  [  +0.06]  s8 : 1000 s9 : 1000 s10: 
ffc80172b9c8
  [  +0.06]  s11: ffd887144000 t3 :  t4 : 

  [  +0.06]  t5 :  t6 : ffc80172b4b8
  [  +0.04] status: 00020100 badaddr: 0058 cause: 
0003
  [  +0.10] [] g84_bar_flush+0x11a/0x12a [nouveau]
  [  +0.006810] [] nvkm_bar_flush+0x1a/0x2c [nouveau]
  [  +0.006619] [] nv50_instobj_release+0x34/0x90 [nouveau]
  [  +0.006681] [] gf100_vmm_pgt_mem+0x11a/0x1c0 [nouveau]
  [  +0.006721] [] nvkm_vmm_iter.constprop.0+0x37e/0x44e 
[nouveau]
  [  +0.006638] [] nvkm_vmm_ptes_get_map+0x36/0x98 [nouveau]
  [  +0.006891] [] nvkm_vmm_map_locked+0x190/0x2bc [nouveau]
  [  +0.006817] [] nvkm_vmm_map+0x46/0x7e [nouveau]
  [  +0.006676] [] nvkm_vram_map+0x68/0x98 [nouveau]
  [  +0.006690] [] gf100_mem_map+0x98/0x12c [nouveau]
  [  +0.006985] [] nvkm_umem_map+0x50/0xc4 [nouveau]
  [  +0.007003] [] nvkm_object_map+0x1e/0x42 [nouveau]
  [  +0.006670] [] nvkm_ioctl_map+0x76/0xf2 [nouveau]
  [  +0.007303] [] nvkm_ioctl+0xaa/0x208 [nouveau]
  [  +0.006766] [] nvkm_client_ioctl+0x18/0x26 [nouveau]
  [  +0.006833] [] nvif_object_map_handle+0x90/0xf6 [nouveau]
  [  +0.007200] [] nouveau_ttm_io_mem_reserve+0x13a/0x222 
[nouveau]
  [  +0.007131] [] ttm_bo_vmap+0x82/0x120 [ttm]
  [  +0.000263] [] drm_gem_ttm_vmap+0x18/0x22 [drm_ttm_helper]
  [  +0.24] [] drm_gem_vmap+0x1e/0x40 [drm]
  [  +0.001963] [] drm_gem_vmap_unlocked+0x30/0x50 [drm]
  [  +0.000915] [] drm_client_buffer_vmap+0x26/0x44 [drm]
  [  +0.001034] [] 
drm_fbdev_generic_helper_fb_dirty+0xa2/0x190 [drm_kms_helper]
  [  +0.000717] [] drm_fb_helper_fb_dirty+0x86/0x174 
[drm_kms_helper]
  [  +0.000286] [] drm_fb_helper_damage_work+0x1c/0x26 
[drm_kms_helper]
  [  +0.000272] [] process_one_work+0x1f6/0x390
  [  +0.24] [] worker_thread+0x8a/0x456
  [  +0.11] [] kthread+0xc4/0xe4
  [  +0.12] [] ret_from_fork+0xe/0x20
  [  +0.14] ---[ end trace  ]---
  [  +0.133717] nouveau :05:00.0: timer: stalled at 
  [  +0.007740] [ cut here ]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17.1.1~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-17.17.1.1~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Mon Feb 19 15:47:49 2024
  SourcePackage: linux-riscv-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2054325] [NEW] nouveau 0000:05:00.0: timeout on HiFive SiFive Unmatched

2024-02-19 Thread Heinrich Schuchardt
Public bug reported:

Booting the SiFive Unmatched no output on the monitor was shown.
Zillions of messages like the following were written:

[  +0.007867] [ cut here ]
[  +0.13] nouveau :05:00.0: timeout
[  +0.000374] WARNING: CPU: 2 PID: 2028 at 
drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12a 
[nouveau]
[  +0.008579] Modules linked in: tls binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_timer snd soundc>
[  +0.000245] CPU: 2 PID: 2028 Comm: kworker/2:3 Tainted: GW  
6.5.0-17-generic #17.1.1~22.04.1-Ubuntu
[  +0.11] Hardware name: SiFive HiFive Unmatched A00 (DT)
[  +0.07] Workqueue: events drm_fb_helper_damage_work [drm_kms_helper]
[  +0.000715] epc : g84_bar_flush+0x11a/0x12a [nouveau]
[  +0.006843]  ra : g84_bar_flush+0x11a/0x12a [nouveau]
[  +0.006368] epc : 026becf8 ra : 026becf8 sp : ffc80172b6c0
[  +0.08]  gp : 822603c8 tp : ffd89ae05100 t0 : 820bd738
[  +0.06]  t1 :  t2 : 2d2d2d2d2d2d2d2d s0 : ffc80172b720
[  +0.05]  s1 : ffd887482000 a0 :  a1 : 
[  +0.06]  a2 :  a3 :  a4 : 
[  +0.06]  a5 :  a6 :  a7 : 
[  +0.05]  s2 : 0007 s3 : ffd89d6d19b8 s4 : 00020022
[  +0.06]  s5 : 0046 s6 : 0046 s7 : 
[  +0.06]  s8 : 1000 s9 : 1000 s10: ffc80172b9c8
[  +0.06]  s11: ffd887144000 t3 :  t4 : 
[  +0.06]  t5 :  t6 : ffc80172b4b8
[  +0.04] status: 00020100 badaddr: 0058 cause: 
0003
[  +0.10] [] g84_bar_flush+0x11a/0x12a [nouveau]
[  +0.006810] [] nvkm_bar_flush+0x1a/0x2c [nouveau]
[  +0.006619] [] nv50_instobj_release+0x34/0x90 [nouveau]
[  +0.006681] [] gf100_vmm_pgt_mem+0x11a/0x1c0 [nouveau]
[  +0.006721] [] nvkm_vmm_iter.constprop.0+0x37e/0x44e 
[nouveau]
[  +0.006638] [] nvkm_vmm_ptes_get_map+0x36/0x98 [nouveau]
[  +0.006891] [] nvkm_vmm_map_locked+0x190/0x2bc [nouveau]
[  +0.006817] [] nvkm_vmm_map+0x46/0x7e [nouveau]
[  +0.006676] [] nvkm_vram_map+0x68/0x98 [nouveau]
[  +0.006690] [] gf100_mem_map+0x98/0x12c [nouveau]
[  +0.006985] [] nvkm_umem_map+0x50/0xc4 [nouveau]
[  +0.007003] [] nvkm_object_map+0x1e/0x42 [nouveau]
[  +0.006670] [] nvkm_ioctl_map+0x76/0xf2 [nouveau]
[  +0.007303] [] nvkm_ioctl+0xaa/0x208 [nouveau]
[  +0.006766] [] nvkm_client_ioctl+0x18/0x26 [nouveau]
[  +0.006833] [] nvif_object_map_handle+0x90/0xf6 [nouveau]
[  +0.007200] [] nouveau_ttm_io_mem_reserve+0x13a/0x222 
[nouveau]
[  +0.007131] [] ttm_bo_vmap+0x82/0x120 [ttm]
[  +0.000263] [] drm_gem_ttm_vmap+0x18/0x22 [drm_ttm_helper]
[  +0.24] [] drm_gem_vmap+0x1e/0x40 [drm]
[  +0.001963] [] drm_gem_vmap_unlocked+0x30/0x50 [drm]
[  +0.000915] [] drm_client_buffer_vmap+0x26/0x44 [drm]
[  +0.001034] [] drm_fbdev_generic_helper_fb_dirty+0xa2/0x190 
[drm_kms_helper]
[  +0.000717] [] drm_fb_helper_fb_dirty+0x86/0x174 
[drm_kms_helper]
[  +0.000286] [] drm_fb_helper_damage_work+0x1c/0x26 
[drm_kms_helper]
[  +0.000272] [] process_one_work+0x1f6/0x390
[  +0.24] [] worker_thread+0x8a/0x456
[  +0.11] [] kthread+0xc4/0xe4
[  +0.12] [] ret_from_fork+0xe/0x20
[  +0.14] ---[ end trace  ]---
[  +0.133717] nouveau :05:00.0: timer: stalled at 
[  +0.007740] [ cut here ]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-17-generic 6.5.0-17.17.1.1~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-17.17.1.1~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic riscv64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Mon Feb 19 15:47:49 2024
SourcePackage: linux-riscv-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug jammy riscv64 uec-images

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

Title:
  nouveau :05:00.0: timeout on HiFive SiFive Unmatched

Status in linux-riscv-6.5 package in Ubuntu:
  New

Bug description:
  Booting the SiFive Unmatched no output on the monitor was shown.
  Zillions of messages like the following were written:

  [  +0.007867] [ cut here ]
  [  +0.13] nouveau :05:00.0: timeout
  [  +0.000374] WARNING: CPU: 2 PID: 2028 at 
drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 

[Kernel-packages] [Bug 2048864] Re: Remove armhf support

2024-02-01 Thread Heinrich Schuchardt
Flash-kernel contains a database matching device-tree machine values
with devicetree names.

There is no necessity to remove entries for architectures that are not
supported in Ubuntu. We should try to minimize the differences to
Debian. So setting this to won't fix for flash-kernel.

** Changed in: flash-kernel (Ubuntu Noble)
   Status: New => Won't Fix

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

Title:
  Remove armhf support

Status in flash-kernel package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in flash-kernel source package in Noble:
  Won't Fix
Status in linux-raspi source package in Noble:
  New

Bug description:
  Noble and newer don't support armhf for Pi anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2048864/+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 2049952] [NEW] `kded5' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

2024-01-19 Thread Heinrich Schuchardt
Public bug reported:

When booting I see a message:
`kded5' uses wireless extensions which will stop working for Wi-Fi 7 hardware; 
use nl80211
which is described in https://bugs.kde.org/show_bug.cgi?id=466467

Fedora suggests to disable the outdated wireless extensions:
https://fedoraproject.org/wiki/Changes/RemoveWirelessExtensions

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:zfsdt  3088 F pipewire
 /dev/snd/controlC0:  zfsdt  3091 F wireplumber
 /dev/snd/controlC1:  zfsdt  3091 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Jan 19 22:29:55 2024
InstallationDate: Installed on 2021-07-01 (932 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 001 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic 
root=/dev/mapper/vgubuntu-root ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.6.0-14-generic N/A
 linux-backports-modules-6.6.0-14-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2023
dmi.bios.release: 1.63
dmi.bios.vendor: LENOVO
dmi.bios.version: R0UET83W (1.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KV0008GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.63
dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
dmi.product.family: ThinkPad E585
dmi.product.name: 20KV0008GE
dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
dmi.product.version: ThinkPad E585
dmi.sys.vendor: LENOVO

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

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


** Tags: amd64 apport-bug noble

** Also affects: kded (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  `kded5' uses wireless extensions which will stop working for Wi-Fi 7
  hardware; use nl80211

Status in kded package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  When booting I see a message:
  `kded5' uses wireless extensions which will stop working for Wi-Fi 7 
hardware; use nl80211
  which is described in https://bugs.kde.org/show_bug.cgi?id=466467

  Fedora suggests to disable the outdated wireless extensions:
  https://fedoraproject.org/wiki/Changes/RemoveWirelessExtensions

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  3088 F pipewire
   /dev/snd/controlC0:  zfsdt  3091 F wireplumber
   /dev/snd/controlC1:  zfsdt  3091 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 19 22:29:55 2024
  InstallationDate: Installed on 2021-07-01 (932 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic 

[Kernel-packages] [Bug 2049441] [NEW] zfs-dkms: GPL-incompatible module zfs.ko uses GPL-only symbol 'PageHuge'

2024-01-15 Thread Heinrich Schuchardt
Public bug reported:

I try to install package zfs-dkms on a riscv64 system running Ubuntu
24.04. Installation fails with "GPL-incompatible module zfs.ko uses GPL-
only symbol 'PageHuge'". See appended make.log.

Installed kernel:

Architecture: riscv64
Source: linux-riscv
Version: 6.5.0-9.9.1

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: zfs-dkms 2.2.2-0ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
 {
   "result": "skip"
 }
Date: Tue Jan 16 01:06:40 2024
InstallationDate: Installed on 2023-12-04 (42 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204)
PackageArchitecture: all
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug noble riscv64

** Attachment added: "make.log"
   https://bugs.launchpad.net/bugs/2049441/+attachment/5739731/+files/make.log

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

Title:
  zfs-dkms: GPL-incompatible module zfs.ko uses GPL-only symbol
  'PageHuge'

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I try to install package zfs-dkms on a riscv64 system running Ubuntu
  24.04. Installation fails with "GPL-incompatible module zfs.ko uses
  GPL-only symbol 'PageHuge'". See appended make.log.

  Installed kernel:

  Architecture: riscv64
  Source: linux-riscv
  Version: 6.5.0-9.9.1

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: zfs-dkms 2.2.2-0ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Tue Jan 16 01:06:40 2024
  InstallationDate: Installed on 2023-12-04 (42 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 
(20231204)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2049441/+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 2043061] Re: System suspension is encountered on Ubuntu 23.10 RISC-V image on VisionFive 2

2023-11-08 Thread Heinrich Schuchardt
** Changed in: linux-riscv (Ubuntu)
 Assignee: (unassigned) => Heinrich Schuchardt (xypron)

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

Title:
  System suspension is encountered on Ubuntu 23.10 RISC-V image on
  VisionFive 2

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  After the user has installed and used Ubuntu 23.10 on VisionFive 2 (Model 
1.3B), his system is always suspended with slow or no response. 
  StarFive FAE has reproduced the issue in the following practices. 
  1. Install the Ubuntu system on VisionFive 2. 
  2. Type in the account "ubuntu" several times with deliberate mistakes. 
  3. The system is suspended with no response. 
  Find the screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2043061/+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 2039782] Re: Stalls on CPUs/tasks on VisionFive 2 with external GPU

2023-11-01 Thread Heinrich Schuchardt
@opvolger

Thank you for confirming the issue.

The upstreaming of PCIe for the StarFive VisionFive 2 board is not
finalized yet. The kernel team will revisit this issue once there is
proper upstream support. They picked up what was available on the kernel
list which brought us NVMe support for which I am grateful.

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

Title:
  Stalls on CPUs/tasks on VisionFive 2 with external GPU

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
  board using
  https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
  server-riscv64.img.gz

  I have connected an Nvidia GT710 graphics card to the NVMe connector
  and see rcu_sched stalls. I have not  observed this behavior on
  StarFive VisionFive 2 1.3B boards without an external GPU.

  The U-Boot installed on SPI flash is
  
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

  [   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
  [   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
  [   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 
ncpus=4)
  [   93.140996] Task dump for CPU 0:
  [   93.149549] task:swapper/0   state:R  running task stack:0 
pid:0 ppid:0  flags:0x
  [   93.164907] Call Trace:
  [   93.172715] [] __schedule+0x27a/0x82e
  [   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
  [   93.200202] rcu: Possible timer handling issue on cpu=0 
timer-softirq=890
  [   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
  [   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, 
OOM is now expected behavior.
  [   93.243573] rcu: RCU grace-period kthread stack dump:
  [   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
  [   93.268895] Call Trace:
  [   93.277340] [] __schedule+0x27a/0x82e
  [   93.288646] [] schedule+0x4e/0xde
  [   93.299623] [] schedule_timeout+0x8c/0x15e
  [   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
  [   93.323170] [] rcu_gp_kthread+0x11a/0x142
  [   93.334901] [] kthread+0xc4/0xe4
  [   93.345833] [] ret_from_fork+0xe/0x20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2039782/+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 2039782] Re: Stalls on CPUs/tasks on VisionFive 2 with external GPU

2023-11-01 Thread Heinrich Schuchardt
** Changed in: linux-riscv (Ubuntu)
   Status: New => Confirmed

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

Title:
  Stalls on CPUs/tasks on VisionFive 2 with external GPU

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
  board using
  https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
  server-riscv64.img.gz

  I have connected an Nvidia GT710 graphics card to the NVMe connector
  and see rcu_sched stalls. I have not  observed this behavior on
  StarFive VisionFive 2 1.3B boards without an external GPU.

  The U-Boot installed on SPI flash is
  
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

  [   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
  [   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
  [   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 
ncpus=4)
  [   93.140996] Task dump for CPU 0:
  [   93.149549] task:swapper/0   state:R  running task stack:0 
pid:0 ppid:0  flags:0x
  [   93.164907] Call Trace:
  [   93.172715] [] __schedule+0x27a/0x82e
  [   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
  [   93.200202] rcu: Possible timer handling issue on cpu=0 
timer-softirq=890
  [   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
  [   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, 
OOM is now expected behavior.
  [   93.243573] rcu: RCU grace-period kthread stack dump:
  [   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
  [   93.268895] Call Trace:
  [   93.277340] [] __schedule+0x27a/0x82e
  [   93.288646] [] schedule+0x4e/0xde
  [   93.299623] [] schedule_timeout+0x8c/0x15e
  [   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
  [   93.323170] [] rcu_gp_kthread+0x11a/0x142
  [   93.334901] [] kthread+0xc4/0xe4
  [   93.345833] [] ret_from_fork+0xe/0x20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2039782/+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 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

2023-10-31 Thread Heinrich Schuchardt
File lib/firmware/brcm/brcmfmac43430-sdio.bin.zst is contained in the
24.04 package. Looks ok.

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

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

Title:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [Impact]

  /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
  StarFive VisionFive board which uses the starfive kernel flavor.

  The file was available in Jammy and only recently removed from Mantic.

  File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding
  it cyfmac43430-sdio.clm_blob which file WHENCE links to
  brcmfmac43430-sdio.bin. So this file needs to change.

  [Fix]

  Include cypress/cyfmac firmware files in firmware packages.

  [Test Case]

  Check that wifi is functional.

  [Where Problems Could Occur]

  Potential wifi problems on platforms that are using the brcmfmac
  driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2034705] Re: efivar fails to read variables

2023-10-25 Thread Heinrich Schuchardt
Upstream has accepted the patch and added it to the v6.5 stable series.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.5.9=63565e1cbfb59da059dd322054840eb6a0019e65

** Changed in: linux-meta (Ubuntu)
   Importance: Undecided => High

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  New
Status in linux-meta-riscv package in Ubuntu:
  In Progress

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support

2023-10-20 Thread Heinrich Schuchardt
@itrue
The issue is described on 
https://wiki.ubuntu.com/RISC-V/PolarFire%20SoC%20FPGA%20Icicle%20Kit.

Upstream kernel patches are still under discussion. Reopening the issue
does not help unless there are upstream patches that we can merge into
our kernel.

Here is the latest work on cleaning up the code:

[PATCH v9 0/22] Refactoring Microchip PCIe driver and add StarFive PCIe
https://lore.kernel.org/linux-riscv/20231020104341.63157-1-minda.c...@starfivetech.com/

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

Title:
  [FFe] PolarFire Icicle Kit: enable PCIe support

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it
  is not usable. Please, add the following patches:

  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/
  riscv: dts: microchip: add pci dma ranges for the icicle
  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/
  riscv: dts: microchip: move the mpfs' pci node to
  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/
  riscv: dts: microchip: icicle: update pci address
  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/
  riscv: dts: microchip: icicle: re-jig fabric peripheral
  # 
https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/
 
  riscv: dts: microchip: add fabric address translation
  # 
https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/
  PCI: microchip: add fabric address translation properties

  All patches are strictly restricted to the PolarFire Icicle Kit and
  have no impact on any other RISC-V boards that we support.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+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 2039782] [NEW] Stalls on CPUs/tasks on VisionFive 2 with external GPU

2023-10-19 Thread Heinrich Schuchardt
Public bug reported:

I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
board using
https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
server-riscv64.img.gz

I have connected an Nvidia GT710 graphics card to the NVMe connector and
see rcu_sched stalls. I have not  observed this behavior on StarFive
VisionFive 2 1.3B boards without an external GPU.

The U-Boot installed on SPI flash is
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

[   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
[   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 ncpus=4)
[   93.140996] Task dump for CPU 0:
[   93.149549] task:swapper/0   state:R  running task stack:0 pid:0 
ppid:0  flags:0x
[   93.164907] Call Trace:
[   93.172715] [] __schedule+0x27a/0x82e
[   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
[   93.200202] rcu: Possible timer handling issue on cpu=0 timer-softirq=890
[   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
[   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM 
is now expected behavior.
[   93.243573] rcu: RCU grace-period kthread stack dump:
[   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
[   93.268895] Call Trace:
[   93.277340] [] __schedule+0x27a/0x82e
[   93.288646] [] schedule+0x4e/0xde
[   93.299623] [] schedule_timeout+0x8c/0x15e
[   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
[   93.323170] [] rcu_gp_kthread+0x11a/0x142
[   93.334901] [] kthread+0xc4/0xe4
[   93.345833] [] ret_from_fork+0xe/0x20

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

** Attachment added: "boot.log.txt"
   
https://bugs.launchpad.net/bugs/2039782/+attachment/5711125/+files/boot.log.txt

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

Title:
  Stalls on CPUs/tasks on VisionFive 2 with external GPU

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
  board using
  https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
  server-riscv64.img.gz

  I have connected an Nvidia GT710 graphics card to the NVMe connector
  and see rcu_sched stalls. I have not  observed this behavior on
  StarFive VisionFive 2 1.3B boards without an external GPU.

  The U-Boot installed on SPI flash is
  
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

  [   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
  [   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
  [   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 
ncpus=4)
  [   93.140996] Task dump for CPU 0:
  [   93.149549] task:swapper/0   state:R  running task stack:0 
pid:0 ppid:0  flags:0x
  [   93.164907] Call Trace:
  [   93.172715] [] __schedule+0x27a/0x82e
  [   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
  [   93.200202] rcu: Possible timer handling issue on cpu=0 
timer-softirq=890
  [   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
  [   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, 
OOM is now expected behavior.
  [   93.243573] rcu: RCU grace-period kthread stack dump:
  [   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
  [   93.268895] Call Trace:
  [   93.277340] [] __schedule+0x27a/0x82e
  [   93.288646] [] schedule+0x4e/0xde
  [   93.299623] [] schedule_timeout+0x8c/0x15e
  [   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
  [   93.323170] [] rcu_gp_kthread+0x11a/0x142
  [   93.334901] [] kthread+0xc4/0xe4
  [   93.345833] [] ret_from_fork+0xe/0x20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2039782/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

2023-10-11 Thread Heinrich Schuchardt
With u-boot-starfive - 2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa4 from
ppa:ubuntu-risc-v-team/release the problem is resolved.

** Changed in: linux-riscv (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  Invalid

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
  [ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
  [ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
  [ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
  m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
  [ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

  [ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
  [ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
  [ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
  [ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
  [ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
  [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
  [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
  [ 4050.616858] [] walk_component+0x26/0x194
  [ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
  [ 4050.629575] [] path_parentat+0x48/0x96
  [ 4050.634890] [] __filename_parentat+0x9e/0x188
  [ 4050.640813] [] do_renameat2+0xc8/0x4e2
  [ 4050.646128] [] sys_renameat2+0x5a/0x76
  [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
  [ 4050.657018] [] ret_from_exception+0x0/0x64
  [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
  [ 4050.670148] ---[ end trace  ]---
  [ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
  [ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.670368] Oops [#2]
  [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D  
  6.5.0-9-generic #9.1-Ubuntu
  [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.670574]  ra : lookup_fast+0x36/0xfc
  [ 4050.670582] 

[Kernel-packages] [Bug 2038920] Re: Nezha D1: usb 1-1: device descriptor read/64, error -71

2023-10-11 Thread Heinrich Schuchardt
** Summary changed:

- Nezahl D1: usb 1-1: device descriptor read/64, error -71
+ Nezha D1: usb 1-1: device descriptor read/64, error -71

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

Title:
  Nezha D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB keyboard and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

2023-10-10 Thread Heinrich Schuchardt
This patch for upstream U-Boot seems to resolve the issue:
https://lore.kernel.org/u-boot/20231011044813.122941-1-heinrich.schucha...@canonical.com/T/#u.
I will retest the image.

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

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
  [ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
  [ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
  [ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
  m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
  [ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

  [ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
  [ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
  [ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
  [ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
  [ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
  [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
  [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
  [ 4050.616858] [] walk_component+0x26/0x194
  [ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
  [ 4050.629575] [] path_parentat+0x48/0x96
  [ 4050.634890] [] __filename_parentat+0x9e/0x188
  [ 4050.640813] [] do_renameat2+0xc8/0x4e2
  [ 4050.646128] [] sys_renameat2+0x5a/0x76
  [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
  [ 4050.657018] [] ret_from_exception+0x0/0x64
  [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
  [ 4050.670148] ---[ end trace  ]---
  [ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
  [ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.670368] Oops [#2]
  [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D  
  6.5.0-9-generic #9.1-Ubuntu
  [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.670574]  ra : lookup_fast+0x36/0xfc
  [ 4050.670582] epc : 80315146 ra 

[Kernel-packages] [Bug 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

2023-10-10 Thread Heinrich Schuchardt
The problem seems to be related to a U-Boot reporting the wrong memory
size on a VisionFive 2 with 4GiB.

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

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
  [ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
  [ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
  [ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
  m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
  [ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

  [ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
  [ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
  [ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
  [ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
  [ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
  [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
  [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
  [ 4050.616858] [] walk_component+0x26/0x194
  [ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
  [ 4050.629575] [] path_parentat+0x48/0x96
  [ 4050.634890] [] __filename_parentat+0x9e/0x188
  [ 4050.640813] [] do_renameat2+0xc8/0x4e2
  [ 4050.646128] [] sys_renameat2+0x5a/0x76
  [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
  [ 4050.657018] [] ret_from_exception+0x0/0x64
  [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
  [ 4050.670148] ---[ end trace  ]---
  [ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
  [ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.670368] Oops [#2]
  [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D  
  6.5.0-9-generic #9.1-Ubuntu
  [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.670574]  ra : lookup_fast+0x36/0xfc
  [ 4050.670582] epc : 80315146 ra : 803042bc sp : 
ffc80212bb70
  [ 4050.670587]  gp : 

[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

2023-10-10 Thread Heinrich Schuchardt
** Tags added: iso-testing

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

2023-10-10 Thread Heinrich Schuchardt
echo blacklist jh7110_tdm > /etc/modprobe.d/blacklist-jh7110_tdm.conf
did not solve the issue. I still get oopses like:

[  201.478403] Oops [#1]
[  201.480681] Modules linked in: tls cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core cdns3_starfive ofpart cmdlinepart spi_nor mtd 
axp20x_pek pwm_starfive dw_axi_dmac_platform sfctemp uio_pdrv_genirq uio drm 
dm_multipath efi_pstore backlight ip_tables x_tables autofs4 btrfs 
blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive stmmac_platform stmmac nvme xhci_pci axp20x_regulator 
xhci_pci_renesas nvme_core dw_mmc_starfive pcs_xpcs phylink nvme_common 
dw_mmc_pltfm clk_starfive_jh7110_aon clk_starfive_jh7110_isp 
clk_starfive_jh7110_vout pinctrl_starfive_jh7110_aon dw_mmc axp20x_i2c axp20x 
spi_cadence_quadspi jh7110_trng phy_jh7110_usb
[  201.548071] CPU: 0 PID: 612 Comm: systemd-network Not tainted 
6.5.0-9-generic #9.1-Ubuntu
[  201.556251] Hardware name: StarFive VisionFive 2 v1.3B (DT)
[  201.561824] epc : __d_lookup_rcu+0x4a/0x100
[  201.566024]  ra : lookup_fast+0x36/0xfc
[  201.569870] epc : 80315146 ra : 803042bc sp : 
ffc800ecb8b0
[  201.577091]  gp : 822602d8 tp : ffd8c6f6d100 t0 : 
ffc800ecba58
[  201.584320]  t1 :  t2 : 0008 s0 : 
ffc800ecb8e0
[  201.591547]  s1 : ffc800ecb970 a0 : ffd8c49b8000 a1 : 
ffc800ecb980
[  201.598772]  a2 : ffc800ecb9b4 a3 : 0001 a4 : 
3b91a71338836970
[  201.605996]  a5 : 3b91a71338836970 a6 : 361d a7 : 

[  201.613222]  s2 : 0001 s3 : ffd8c49b8000 s4 : 
f000
[  201.620444]  s5 : 0001 s6 : ffc800ecbca8 s7 : 

[  201.627666]  s8 : ffd8c705ca00 s9 : 000a s10: 
7fff
[  201.634887]  s11: 003fc689f768 t3 : ffd8c49b8000 t4 : 
00060361d211
[  201.642109]  t5 : ffc800ecb9b4 t6 : ffd8c24b102d
[  201.647420] status: 00020120 badaddr: ff933883696c cause: 
000d
[  201.655337] [] __d_lookup_rcu+0x4a/0x100
[  201.660834] [] walk_component+0x26/0x194
[  201.666325] [] path_lookupat+0x76/0x196
[  201.671730] [] filename_lookup+0x96/0x166
[  201.677306] [] kern_path+0x38/0x60
[  201.682274] [] unix_find_other+0x50/0x36a
[  201.687850] [] unix_dgram_sendmsg+0x43c/0x81a
[  201.693771] [] sock_sendmsg+0x4e/0x98
[  201.699004] [] sys_sendmsg+0x1d8/0x20a
[  201.704664] [] ___sys_sendmsg+0x90/0xd6
[  201.710066] [] __sys_sendmsg+0x84/0xd2
[  201.715380] [] sys_sendmsg+0x1e/0x2c
[  201.720521] [] do_trap_ecall_u+0xd6/0x154
[  201.726099] [] ret_from_exception+0x0/0x64
[  201.731773] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
[  201.739422] Unable to handle kernel paging request at virtual address 
ffbf0099039c
[  201.739559] Unable to handle kernel paging request at virtual address 
00678895ce42
[  201.740238] ---[ end trace  ]---

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

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 

[Kernel-packages] [Bug 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

2023-10-10 Thread Heinrich Schuchardt
-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/2038928

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
  [ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
  [ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
  [ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
  m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
  [ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

  [ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
  [ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
  [ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
  [ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
  [ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
  [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
  [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
  [ 4050.616858] [] walk_component+0x26/0x194
  [ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
  [ 4050.629575] [] path_parentat+0x48/0x96
  [ 4050.634890] [] __filename_parentat+0x9e/0x188
  [ 4050.640813] [] do_renameat2+0xc8/0x4e2
  [ 4050.646128] [] sys_renameat2+0x5a/0x76
  [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
  [ 4050.657018] [] ret_from_exception+0x0/0x64
  [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
  [ 4050.670148] ---[ end trace  ]---
  [ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
  [ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.670368] Oops [#2]
  [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D  
  6.5.0-9-generic #9.1-Ubuntu
  [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.670574]  ra : lookup_fast+0x36/0xfc
  [ 4050.670582] epc : 80315146 ra : 803042bc sp : 
ffc80212bb70
  [ 4050.670587]  gp : 822602d8 tp : ffd8cb66d100 t0 : 
ffc80212bdb8
  [ 4050.670591]  t1 :  t2 : 

[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

2023-10-10 Thread Heinrich Schuchardt
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+attachment/5708302/+files/syslog

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2038933] [NEW] sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

2023-10-10 Thread Heinrich Schuchardt
Public bug reported:

I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
output is not working.

There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get the
HDMI PHY".

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20231010
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Tue Oct 10 14:42:06 2023
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug cloud-image mantic riscv64

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

2023-10-10 Thread Heinrich Schuchardt
Trying again booting the preinstalled image the reported error did not
come up.

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

Title:
  probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044

Status in bcache-tools package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Running http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on
  QEMU with

  qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
  device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
  file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

  a crash was reported:

  Starting systemd-udevd version 253.5-1ubuntu6
  [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.921064] Hardware name: riscv-virtio,qemu (DT)
  [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
  [3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
  [3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
  [3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
  [3.922751]  a2 : 00022560 a3 : 7fff a4 : 

  [3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
  [3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
  [3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
  [3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
  [3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

  [3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
  [3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.934742] Hardware name: riscv-virtio,qemu (DT)
  [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
  [3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
  [3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
  [3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
  [3.936606]  a2 : 00022560 a3 : 7fff a4 : 

  [3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
  [3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
  [3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
  [3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
  [3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

  [3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
  [3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.952680] Hardware name: riscv-virtio,qemu (DT)
  [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
  [3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
  [3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
  [3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
  [3.954302]  a2 : 00022560 a3 : 7fff a4 : 

  [3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
  [3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
  [3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
  [3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
  [3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

  [3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
  [3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
  Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   
635 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic 

[Kernel-packages] [Bug 2038928] [NEW] Unable to handle kernel paging request at virtual address ffffff8a012abe1a

2023-10-10 Thread Heinrich Schuchardt
Public bug reported:

I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

[ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
[ 4050.426326] Oops [#1]
[ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
[ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
[ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
[ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
[ 4050.521997]  ra : lookup_fast+0x36/0xfc
[ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
[ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
[ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
[ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
[ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

[ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
[ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
[ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
[ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
[ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
[ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
[ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
[ 4050.616858] [] walk_component+0x26/0x194
[ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
[ 4050.629575] [] path_parentat+0x48/0x96
[ 4050.634890] [] __filename_parentat+0x9e/0x188
[ 4050.640813] [] do_renameat2+0xc8/0x4e2
[ 4050.646128] [] sys_renameat2+0x5a/0x76
[ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
[ 4050.657018] [] ret_from_exception+0x0/0x64
[ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
[ 4050.670148] ---[ end trace  ]---
[ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
[ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
[ 4050.670368] Oops [#2]
[ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
[ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D
6.5.0-9-generic #9.1-Ubuntu
[ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
[ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
[ 4050.670574]  ra : lookup_fast+0x36/0xfc
[ 4050.670582] epc : 80315146 ra : 803042bc sp : 
ffc80212bb70
[ 4050.670587]  gp : 822602d8 tp : ffd8cb66d100 t0 : 
ffc80212bdb8
[ 4050.670591]  t1 :  t2 : 812002e8 s0 : 
ffc80212bba0
[ 4050.670595]  s1 : ffc80212bcd0 a0 : ffd8c9fd8a80 a1 : 
ffc80212bce0
[ 4050.670600]  a2 : ffc80212bd14 a3 : 0001 a4 : 
00015635
[ 4050.670604]  a5 : 00015635 a6 : 00035238 a7 : 

[ 4050.670608]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
[ 4050.670612]  s5 : 

[Kernel-packages] [Bug 2038920] Re: Nezahl D1: usb 1-1: device descriptor read/64, error -71

2023-10-10 Thread Heinrich Schuchardt
** Description changed:

  On the Nezha D1 board USB does not work correctly.
  
- I have connected a USB key board and get errors like:
+ I have connected a USB keyboard and get errors like:
  
  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
-  LANG=C.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=vt220
+  LANG=C.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nezahl D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB keyboard and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038920] Re: Nezahl D1: usb 1-1: device descriptor read/64, error -71

2023-10-10 Thread Heinrich Schuchardt
I was able to use the keyboard after removing and plugging in again.

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

Title:
  Nezahl D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB key board and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038920] [NEW] Nezahl D1: usb 1-1: device descriptor read/64, error -71

2023-10-10 Thread Heinrich Schuchardt
Public bug reported:

On the Nezha D1 board USB does not work correctly.

I have connected a USB key board and get errors like:

[ 4458.313671] usb 1-1: device descriptor read/64, error -71
[ 4459.189686] usb 1-1: device descriptor read/64, error -71
[ 4460.157594] usb 4-1: device descriptor read/64, error -62
[ 4460.461621] usb 4-1: device descriptor read/64, error -62
[ 4460.953646] usb 4-1: device descriptor read/64, error -62
[ 4461.257626] usb 4-1: device descriptor read/64, error -62

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20231010
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Tue Oct 10 12:20:40 2023
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug cloud-image mantic riscv64

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

Title:
  Nezahl D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB key board and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

2023-10-10 Thread Heinrich Schuchardt
$ uname -a
Linux ubuntu 6.5.0-9-generic #9.1-Ubuntu SMP Sat Oct  7 17:18:31 UTC 2023 
riscv64 riscv64 riscv64 GNU/Linux

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

Title:
  probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Running http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on
  QEMU with

  qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
  device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
  file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

  a crash was reported:

  Starting systemd-udevd version 253.5-1ubuntu6
  [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.921064] Hardware name: riscv-virtio,qemu (DT)
  [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
  [3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
  [3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
  [3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
  [3.922751]  a2 : 00022560 a3 : 7fff a4 : 

  [3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
  [3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
  [3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
  [3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
  [3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

  [3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
  [3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.934742] Hardware name: riscv-virtio,qemu (DT)
  [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
  [3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
  [3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
  [3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
  [3.936606]  a2 : 00022560 a3 : 7fff a4 : 

  [3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
  [3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
  [3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
  [3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
  [3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

  [3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
  [3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.952680] Hardware name: riscv-virtio,qemu (DT)
  [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
  [3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
  [3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
  [3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
  [3.954302]  a2 : 00022560 a3 : 7fff a4 : 

  [3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
  [3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
  [3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
  [3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
  [3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

  [3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
  [3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
  Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   
635 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  

[Kernel-packages] [Bug 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

2023-10-10 Thread Heinrich Schuchardt
** Attachment added: "syslog.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038893/+attachment/5708199/+files/syslog.gz

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

Title:
  probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Running http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on
  QEMU with

  qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
  device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
  file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

  a crash was reported:

  Starting systemd-udevd version 253.5-1ubuntu6
  [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.921064] Hardware name: riscv-virtio,qemu (DT)
  [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
  [3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
  [3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
  [3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
  [3.922751]  a2 : 00022560 a3 : 7fff a4 : 

  [3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
  [3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
  [3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
  [3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
  [3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

  [3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
  [3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.934742] Hardware name: riscv-virtio,qemu (DT)
  [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
  [3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
  [3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
  [3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
  [3.936606]  a2 : 00022560 a3 : 7fff a4 : 

  [3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
  [3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
  [3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
  [3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
  [3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

  [3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
  [3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.952680] Hardware name: riscv-virtio,qemu (DT)
  [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
  [3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
  [3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
  [3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
  [3.954302]  a2 : 00022560 a3 : 7fff a4 : 

  [3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
  [3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
  [3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
  [3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
  [3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

  [3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
  [3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
  Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   
635 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 

[Kernel-packages] [Bug 2038893] [NEW] probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

2023-10-10 Thread Heinrich Schuchardt
Public bug reported:

Running http://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on QEMU
with

qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

a crash was reported:

Starting systemd-udevd version 253.5-1ubuntu6
[3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
[3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
[3.921064] Hardware name: riscv-virtio,qemu (DT)
[3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
[3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
[3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
[3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
[3.922751]  a2 : 00022560 a3 : 7fff a4 : 

[3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
[3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
[3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
[3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
[3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

[3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
[3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
[3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
[3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
[3.934742] Hardware name: riscv-virtio,qemu (DT)
[3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
[3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
[3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
[3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
[3.936606]  a2 : 00022560 a3 : 7fff a4 : 

[3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
[3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
[3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
[3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
[3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

[3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
[3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
[3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
[3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
[3.952680] Hardware name: riscv-virtio,qemu (DT)
[3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
[3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
[3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
[3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
[3.954302]  a2 : 00022560 a3 : 7fff a4 : 

[3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
[3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
[3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
[3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
[3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

[3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
[3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   635 
MB/s

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20231010
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Tue Oct 10 07:42:51 2023
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-riscv (Ubuntu)
 Importance: Undecided
  

[Kernel-packages] [Bug 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

2023-10-06 Thread Heinrich Schuchardt
linux-firmware - 20230919.git3672ccab-0ubuntu3 is available in
ppa:xypron/gnu-efi

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

Title:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
  StarFive VisionFive board which uses the starfive kernel flavor.

  The file was available in Jammy and only recently removed from Mantic.

  File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding
  it cyfmac43430-sdio.clm_blob which file WHENCE links to
  brcmfmac43430-sdio.bin. So this file needs to change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

2023-10-06 Thread Heinrich Schuchardt
** Patch added: 
"linux-firmware-20230919.git3672ccab-0ubuntu2..20230919.git3672ccab-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+attachment/5707392/+files/linux-firmware-20230919.git3672ccab-0ubuntu2..20230919.git3672ccab-0ubuntu3.debdiff

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

Title:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
  StarFive VisionFive board which uses the starfive kernel flavor.

  The file was available in Jammy and only recently removed from Mantic.

  File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding
  it cyfmac43430-sdio.clm_blob which file WHENCE links to
  brcmfmac43430-sdio.bin. So this file needs to change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2037065] Re: Wifi not working on StarFive VisionFive

2023-10-05 Thread Heinrich Schuchardt
*** This bug is a duplicate of bug 2038546 ***
https://bugs.launchpad.net/bugs/2038546

** This bug has been marked a duplicate of bug 2038546
   /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

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

Title:
  Wifi not working on StarFive VisionFive

Status in linux-starfive package in Ubuntu:
  New

Bug description:
  I am currently testing http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20230920/mantic-preinstalled-server-
  riscv64+visionfive.img.xz according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/448/builds/287116/testcases/1754/results

  'nmcli dev wifi list' and 'ip a' do not show the WiFi device.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-5.19.0-1014-starfive 5.19.0-1014.16
  ProcVersionSignature: Ubuntu 5.19.0-1014.16-starfive 5.19.17
  Uname: Linux 5.19.0-1014-starfive riscv64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230920
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Sep 22 09:05:10 2023
  ProcCpuinfoMinimal:
   processor: 1
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  SourcePackage: linux-starfive
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-starfive/+bug/2037065/+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 2038546] [NEW] /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

2023-10-05 Thread Heinrich Schuchardt
Public bug reported:

/lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
StarFive VisionFive board which uses the starfive kernel flavor.

The file was available in Jammy and only recently removed from Mantic.

File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it
cyfmac43430-sdio.clm_blob which file WHENCE links to
brcmfmac43430-sdio.bin. So this file needs to change.

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


** Tags: iso-testing mantic riscv64

** Tags added: iso-testing mantic riscv64

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

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

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

Title:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
  StarFive VisionFive board which uses the starfive kernel flavor.

  The file was available in Jammy and only recently removed from Mantic.

  File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding
  it cyfmac43430-sdio.clm_blob which file WHENCE links to
  brcmfmac43430-sdio.bin. So this file needs to change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2034705] Re: efivar fails to read variables

2023-09-22 Thread Heinrich Schuchardt
With kernel 6.5.0-6-generic #6.1-Ubuntu SMP Thu Sep 21 12:51:18 from
ppa:esmil/ppa efivar works fine.

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  Invalid
Status in linux-meta-riscv package in Ubuntu:
  In Progress

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2037065] [NEW] Wifi not working on StarFive VisionFive

2023-09-22 Thread Heinrich Schuchardt
Public bug reported:

I am currently testing http://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/20230920/mantic-preinstalled-server-
riscv64+visionfive.img.xz according to
http://iso.qa.ubuntu.com/qatracker/milestones/448/builds/287116/testcases/1754/results

'nmcli dev wifi list' and 'ip a' do not show the WiFi device.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-5.19.0-1014-starfive 5.19.0-1014.16
ProcVersionSignature: Ubuntu 5.19.0-1014.16-starfive 5.19.17
Uname: Linux 5.19.0-1014-starfive riscv64
ApportVersion: 2.27.0-0ubuntu2
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20230920
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Fri Sep 22 09:05:10 2023
ProcCpuinfoMinimal:
 processor  : 1
 hart   : 0
 isa: rv64imafdc
 mmu: sv39
 uarch  : sifive,u74-mc
SourcePackage: linux-starfive
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug cloud-image iso-testing mantic riscv64

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

Title:
  Wifi not working on StarFive VisionFive

Status in linux-starfive package in Ubuntu:
  New

Bug description:
  I am currently testing http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20230920/mantic-preinstalled-server-
  riscv64+visionfive.img.xz according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/448/builds/287116/testcases/1754/results

  'nmcli dev wifi list' and 'ip a' do not show the WiFi device.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-5.19.0-1014-starfive 5.19.0-1014.16
  ProcVersionSignature: Ubuntu 5.19.0-1014.16-starfive 5.19.17
  Uname: Linux 5.19.0-1014-starfive riscv64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230920
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Sep 22 09:05:10 2023
  ProcCpuinfoMinimal:
   processor: 1
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  SourcePackage: linux-starfive
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-starfive/+bug/2037065/+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 2037000] Re: No HDMI output with 6.5.0-2-generic

2023-09-21 Thread Heinrich Schuchardt
$ uname -a
Linux ubuntu 6.5.0-2-generic #2.1-Ubuntu SMP Tue Sep  5 14:10:40 UTC 2023 
riscv64 riscv64 riscv64 GNU/Linux

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

Title:
  No HDMI output with 6.5.0-2-generic

Status in linux-meta-riscv package in Ubuntu:
  New

Bug description:
  I am currently testing the mantic preinstalled server image for the
  LicheeRV Dock.

  After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is
  missing. Before we build the final images this needs to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/2037000/+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 2037000] [NEW] No HDMI output with 6.5.0-2-generic

2023-09-21 Thread Heinrich Schuchardt
Public bug reported:

I am currently testing the mantic preinstalled server image for the
LicheeRV Dock.

After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is
missing. Before we build the final images this needs to be fixed.

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

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

Title:
  No HDMI output with 6.5.0-2-generic

Status in linux-meta-riscv package in Ubuntu:
  New

Bug description:
  I am currently testing the mantic preinstalled server image for the
  LicheeRV Dock.

  After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is
  missing. Before we build the final images this needs to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/2037000/+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 2013743] Re: USB not working on Nezha D1

2023-09-21 Thread Heinrich Schuchardt
Same error exists with Linux ubuntu 6.2.0-19-generic on Nezha D1 board.

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

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

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

Title:
  USB not working on Nezha D1

Status in linux-allwinner package in Ubuntu:
  New
Status in linux-meta package in Ubuntu:
  New

Bug description:
  I am testing the Allwinner Nezha D1 board according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results

  Hitting a key on the USB keyboard (that was plugged in at boot)
  results in

  [  760.275027] usb 3-1: device descriptor read/64, error -71
  [  761.671031] usb 1-1: device descriptor read/64, error -62
  [  761.975011] usb 1-1: device descriptor read/64, error -62
  [  762.466981] usb 1-1: device descriptor read/64, error -62
  [  762.770995] usb 1-1: device descriptor read/64, error -62
  [  763.514994] usb 1-1: device not accepting address 17, error -62
  [  764.122989] usb 1-1: device not accepting address 18, error -62
  [  764.129829] usb usb1-port1: unable to enumerate USB device

  lsusb does not show the keyboard:

  $ lsusb
  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3
  ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7
  Uname: Linux 5.19.0-1003-allwinner riscv64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230329
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Mar 31 14:31:08 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2035604] [NEW] iwlfifi crashes on 6.5.0-5-generic

2023-09-14 Thread Heinrich Schuchardt
Public bug reported:

I am running Ubuntu Mantic. Since the upgrade of the kernel to 6.5 my WiFI card
Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
does not work anymore.

[  +0.000149]  libcrc32c raid1 raid0 multipath linear amdgpu amdxcp iommu_v2 
drm_buddy gpu_sched i2c_algo_bit drm_suballoc_helper drm_ttm_helper ttm 
drm_display_helper crct10dif_pclmul crc32_pclmul cec polyval_clmulni 
polyval_generic rc_core ghash_clmulni_intel sha512_ssse3 aesni_intel 
drm_kms_helper sdhci_pci crypto_simd nvme ucsi_acpi ahci psmouse cryptd cqhci 
drm xhci_pci typec_ucsi r8169 nvme_core libahci xhci_pci_renesas sdhci realtek 
nvme_common typec video wmi
[  +0.76] CPU: 7 PID: 1078 Comm: modprobe Tainted: GW  
6.5.0-5-generic #5-Ubuntu
[  +0.05] Hardware name: LENOVO 20KV0008GE/20KV0008GE, BIOS R0UET83W (1.63 
) 02/08/2023
[  +0.03] RIP: 0010:iwl_fwrt_dump_lmac_error_log+0x526/0x6c0 [iwlwifi]
[  +0.38] Code: 83 6e 01 00 00 42 0f b6 84 bb 28 07 00 00 8d 50 90 83 fa 03 
0f 86 86 fc ff ff 3d 84 00 00 00 0f 85 3d fc ff ff e9 76 fc ff ff <0f> 0b 49 8b 
7c 24 40 48 c7 c2 20 81 0c c2 31 f6 e8 25 68 fd ff 49
[  +0.03] RSP: 0018:9ff8013e7738 EFLAGS: 00010286
[  +0.05] RAX: fff0 RBX: 9296c6c72f78 RCX: 
[  +0.03] RDX:  RSI:  RDI: 
[  +0.02] RBP: 9ff8013e7808 R08:  R09: 
[  +0.03] R10:  R11:  R12: 9296861a8028
[  +0.02] R13: 004f2530 R14: 9ff8013e7740 R15: 
[  +0.03] FS:  7fe04e4b8040() GS:9299c0fc() 
knlGS:
[  +0.04] CS:  0010 DS:  ES:  CR0: 80050033
[  +0.02] CR2: 55f6f4c3b038 CR3: 00010f5c4000 CR4: 003506e0
[  +0.04] Call Trace:
[  +0.03]  
[  +0.04]  ? show_regs+0x6d/0x80
[  +0.08]  ? __warn+0x89/0x160
[  +0.06]  ? iwl_fwrt_dump_lmac_error_log+0x526/0x6c0 [iwlwifi]
[  +0.39]  ? report_bug+0x17e/0x1b0
[  +0.08]  ? handle_bug+0x51/0xa0
[  +0.06]  ? exc_invalid_op+0x18/0x80
[  +0.05]  ? asm_exc_invalid_op+0x1b/0x20
[  +0.09]  ? iwl_fwrt_dump_lmac_error_log+0x526/0x6c0 [iwlwifi]
[  +0.37]  ? iwl_fwrt_dump_lmac_error_log+0xc9/0x6c0 [iwlwifi]
[  +0.42]  iwl_fwrt_dump_error_logs.part.0+0x1a/0x290 [iwlwifi]
[  +0.37]  iwl_fwrt_dump_error_logs+0x19/0x50 [iwlwifi]
[  +0.36]  iwl_mvm_nic_error+0x7a/0x130 [iwlmvm]
[  +0.48]  iwl_trans_sync_nmi_with_addr+0x7d/0x170 [iwlwifi]
[  +0.31]  iwl_trans_pcie_sync_nmi+0x47/0x80 [iwlwifi]
[  +0.32]  iwl_fw_dbg_error_collect+0x64/0xf0 [iwlwifi]
[  +0.37]  iwl_mvm_load_ucode_wait_alive+0x541/0x670 [iwlmvm]
[  +0.38]  ? __pfx_iwl_alive_fn+0x10/0x10 [iwlmvm]
[  +0.50]  ? srso_return_thunk+0x5/0x10
[  +0.07]  iwl_run_unified_mvm_ucode+0xbb/0x290 [iwlmvm]
[  +0.37]  ? __pfx_iwl_wait_init_complete+0x10/0x10 [iwlmvm]
[  +0.36]  ? iwl_write32+0x36/0x90 [iwlwifi]
[  +0.28]  ? srso_return_thunk+0x5/0x10
[  +0.06]  iwl_run_init_mvm_ucode+0x1f2/0x3e0 [iwlmvm]
[  +0.35]  ? iwl_read32+0x24/0x90 [iwlwifi]
[  +0.30]  ? iwl_trans_pcie_start_hw+0x8e/0x300 [iwlwifi]
[  +0.70]  iwl_mvm_start_get_nvm+0xaf/0x2b0 [iwlmvm]
[  +0.41]  iwl_op_mode_mvm_start+0x820/0xac0 [iwlmvm]
[  +0.43]  _iwl_op_mode_start+0xae/0xe0 [iwlwifi]
[  +0.31]  iwl_opmode_register+0x6d/0xf0 [iwlwifi]
[  +0.30]  ? __pfx_iwl_mvm_init+0x10/0x10 [iwlmvm]
[  +0.36]  iwl_mvm_init+0x26/0xff0 [iwlmvm]
[  +0.35]  ? __pfx_iwl_mvm_init+0x10/0x10 [iwlmvm]
[  +0.35]  do_one_initcall+0x5e/0x340
[  +0.10]  do_init_module+0x68/0x260
[  +0.06]  load_module+0xba1/0xcf0
[  +0.04]  ? srso_return_thunk+0x5/0x10
[  +0.09]  ? vfree+0xff/0x2d0
[  +0.08]  init_module_from_file+0x96/0x100
[  +0.04]  ? init_module_from_file+0x96/0x100
[  +0.11]  idempotent_init_module+0x11c/0x2b0
[  +0.08]  __x64_sys_finit_module+0x64/0xd0
[  +0.06]  do_syscall_64+0x5c/0x90
[  +0.06]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[  +0.04] RIP: 0033:0x7fe04db25c5d
[  +0.35] Code: ff 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 01 f0 
ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[  +0.03] RSP: 002b:7ffc3b946868 EFLAGS: 0246 ORIG_RAX: 
0139
[  +0.04] RAX: ffda RBX: 55a564602ee0 RCX: 7fe04db25c5d
[  +0.03] RDX: 0004 RSI: 55a563e5f727 RDI: 0002
[  +0.02] RBP: 55a563e5f727 R08: 0040 R09: ff88
[  +0.03] R10: ffc0 R11: 0246 R12: 0004
[  +0.03] R13: 55a564602d40 R14: 55a564603a40 R15: 55a56460c650
[  +0.08]  
[  +0.02] ---[ end trace  ]---
[  +0.03] iwlwifi :04:00.0: HW error, resetting 

[Kernel-packages] [Bug 2034705] Re: efivar fails to read variables

2023-09-09 Thread Heinrich Schuchardt
Patch sent upstream https://lore.kernel.org/linux-
efi/20230909180812.10904-1-heinrich.schucha...@canonical.com/T/#u.

Without this patch the Ubuntu installer on systems using U-Boot (e.g.
riscv64) will fail.

** Changed in: linux-meta-riscv (Ubuntu)
 Assignee: Heinrich Schuchardt (xypron) => (unassigned)

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  Invalid
Status in linux-meta-riscv package in Ubuntu:
  In Progress

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2034705] Re: efivar fails to read variables

2023-09-08 Thread Heinrich Schuchardt
** Patch added: "Draft Linux patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/2034705/+attachment/5699289/+files/0001-efivarfs-fix-statfs-on-efivarfs.patch

** Changed in: linux-meta-riscv (Ubuntu)
 Assignee: (unassigned) => Heinrich Schuchardt (xypron)

** Changed in: linux-meta-riscv (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-meta-riscv (Ubuntu)
   Status: New => In Progress

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  Invalid
Status in linux-meta-riscv package in Ubuntu:
  In Progress

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2034705] Re: efivar fails to read variables

2023-09-08 Thread Heinrich Schuchardt
U-Boot currently does not implement QueryVariableInfo at runtime. This
function is not needed for a read only efivarfs. I think it would be
more appropriate to check if GetVariable is enabled in
efi.runtime_supported_mask.

** Changed in: efivar (Ubuntu)
   Status: New => Invalid

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  Invalid
Status in linux-meta-riscv package in Ubuntu:
  New

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2034705] Re: efivar fails to read variables

2023-09-08 Thread Heinrich Schuchardt
Kernel commit d86ffcb1 ("efivarfs: expose used and total size")
introduced an EFI runtime call QueryVariableInfo().

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  New
Status in linux-meta-riscv package in Ubuntu:
  New

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2034705] Re: efivar fails to read variables

2023-09-08 Thread Heinrich Schuchardt
In U-Boot's EFI_RT_PROPERTIES_TABLE_VERSION the flag
EFI_RT_SUPPORTED_QUERY_VARIABLE_INFO is not set.

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  New
Status in linux-meta-riscv package in Ubuntu:
  New

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2034705] Re: efivar fails to read variables

2023-09-08 Thread Heinrich Schuchardt
The problem is due to the kernel not supporting the deprecated statfs()
call on the efivarfs file system.

To demonstrate this I have created the following program (statfs.c):

#include 
#include 

int main(int argc, char *argv[])
{
struct statfs s;
int ret;

if (argc < 2) {
printf("usage: %s \n", argv[0]);
return 1;
}

ret = statfs(argv[1], );
if (ret == -1) {
perror("statfs");
return 1;
} else {
printf("%s type: 0x%llx\n", argv[1],
   (unsigned long long)s.f_type);
}
return 0;
}

When I run it I get the following output:

$ ./statfs /sys/firmware/efi
/sys/firmware/efi type: 0x62656572
$ ./statfs /sys/firmware/efi/efivars/
statfs: Invalid argument
$ mount | grep efivarfs
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(ro,nosuid,nodev,noexec,relatime)

Though efivarfs is mounted on /sys/firmware/efi/efivars the statfs call
fails.


** Also affects: linux-meta-riscv (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  New
Status in linux-meta-riscv package in Ubuntu:
  New

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT

2023-07-17 Thread Heinrich Schuchardt
>> Kernels that use u-boot (direct), abootimg, piboot will have to stay
as they are - unless they gain zboot image format boot support.

Hello Dimitri,

zboot kernels are regualr EFI binaries. Where did you see problems in
booting them with U-Boot's bootefi command?

Best regards

Heinrich

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

Title:
  Add support for kernels compiled with CONFIG_EFI_ZBOOT

Status in grub2 package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the 
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header. 
Our GRUB fails to boot such a kernel.

  We should eliminate the following check:

  grub-core/loader/efi/linux.c:75:
    if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
  return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");

  This will allow any EFI binary to be run using the linux command.

  [Test plan]
  TBD

  [Where problems could occur]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 1959525] Re: Occasional no display output on 6900XT or if been idle for too long

2023-07-03 Thread Heinrich Schuchardt
My problems only occur when running a KDE Wayland session, not with KDE
X11 sessions.

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

Title:
  Occasional no display output on 6900XT or if been idle for too long

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  ## No output at boot
  The dmesg I attached is from when nothing showed at boot.

  Journal output:
  $ journalctl -r --grep amdgpu
  -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 
15:58:40 EST. --
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with 
error -110
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_init+0x77/0x1000 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_pci_probe+0x12a/0x1b0 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_driver_load_kms.cold+0x46/0x83 
[amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_driver_unload_kms+0x43/0x70 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_device_fini+0xc5/0x1e5 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_device_ip_fini.isra.0+0x206/0x2cd 
[amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  gmc_v10_0_sw_fini+0x33/0x40 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_bo_fini+0x12/0x50 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_ttm_fini+0xab/0x100 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid 
amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper 
crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel 
sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci 
xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi
  Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* 
Fail to stop psp ring
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: 
finishing device.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error 
during GPU init
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* 
hw_init of IP block  failed -110
  Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] 
*ERROR* KCQ enable failed
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is 
initialized successfully!
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios 
provided pptable
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if 
version not matched
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if 
version = 0x003d, smu fw if version = 0x0040, smu fw version = 
0x003a4700 (58.71.0)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: 
securedisplay ta ucode is not available
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to 
load VCN firmware
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready.
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 
0x0084 - 0x
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 
0x - 0x1FFF
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 
0x0080 - 0x0083FEFF (16368M used)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not 
presented.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not 
presented.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS 
from VFCT
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory 
Zone (TMZ) feature not supported
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 
0007)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga 
console
  Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu kernel modesetting enabled.
  Jan 30 15:50:24 Y4M1-II kernel: Kernel command line: 

[Kernel-packages] [Bug 1975592] Re: Enable Nezha board

2023-06-08 Thread Heinrich Schuchardt
Dear Dimitri,

it is unclear to me why U-Boot should have any influence on the
(non-)inclusion of a driver in the initramfs. Could you, please, add the
missing information.

There is no guarantee that any update of U-Boot runs after the kernel
change. A user can choose only to update the kernel. They could even run
a custom U-Boot. Please avoid linking the kernel upgrade to any
assumptions about U-Boot.

Best regards

Heinrich

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

Title:
  Enable Nezha board

Status in linux-allwinner package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in u-boot-nezha package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  integrate linux-allwinner patches into linux-riscv kernel

  [Test]
  * Newly built images should boot and work on both nezha and licheerv
  * Upgraded systems using old images should reboot and work on both nezha and 
licheerv
  * Once this migrates, mantic+ livecd-rootfs can be improved to use generic 
kernel

  [Implementation details]
  * linux[-image]-allwinner depends on new enough generic kernel with allwinner 
support pull request applied; and on an updated u-boot-nezha package

  * new enough u-boot-nezha package ensures that MMC driver is included
  in the initramfs, and triggers initramfs update at the end of the apt
  transaction

  * End result, nezha/licheerv systems switch from tracking allwinner
  kernel to tracking generic kernel with initrd that contains MMC driver
  which used to be built-in.

  [Regression potential]
  Ensure this new build of linux-riscv doesn't regress on existing supported 
systems (sifive & qemu)

  scope:
  linux-riscv https://lists.ubuntu.com/archives/kernel-team/2023-May/139655.html
  u-boot-nezha patch attached
  linux-meta-riscv patch attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/1975592/+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 2018657] Re: Sound output fails

2023-05-06 Thread Heinrich Schuchardt
As the error message seems to be created on the last frame, the main
question is why there is not sound output at all.

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

Title:
  Sound output fails

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  I am running Ubuntu Lunar on the LicheeRV dock with a loudspeaker
  connected.

  The 'aplay -l' command shows that a playback device exists:

  # aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sun20icodec [sun20i-codec], device 0: sun20i-codec 
snd-soc-dummy-dai-0 [sun20i-codec snd-soc-dummy-dai-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

  But playback fails:

  $ sudo aplay PinkPanther30.wav 
  Playing WAVE 'PinkPanther30.wav' : Signed 16 bit Little Endian, Rate 22050 
Hz, Mono
  aplay: pcm_write:2127: write error: Input/output error

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
  ProcVersionSignature: Ubuntu 5.19.0-1009.9-allwinner 5.19.17
  Uname: Linux 5.19.0-1009-allwinner riscv64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230415.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Sat May  6 18:37:23 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2018657/+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 2018657] Re: Sound output fails

2023-05-06 Thread Heinrich Schuchardt
After several successful calls in file alsa-lib/src/pcm/pcm.c, function
snd_pcm_hw_writei()

   ioctl(fd, SNDRV_PCM_IOCTL_WRITEI_FRAMES, )

returns an error EIO with fd pointing to /dev/snd/pcmC0D0p.

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

Title:
  Sound output fails

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  I am running Ubuntu Lunar on the LicheeRV dock with a loudspeaker
  connected.

  The 'aplay -l' command shows that a playback device exists:

  # aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sun20icodec [sun20i-codec], device 0: sun20i-codec 
snd-soc-dummy-dai-0 [sun20i-codec snd-soc-dummy-dai-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

  But playback fails:

  $ sudo aplay PinkPanther30.wav 
  Playing WAVE 'PinkPanther30.wav' : Signed 16 bit Little Endian, Rate 22050 
Hz, Mono
  aplay: pcm_write:2127: write error: Input/output error

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
  ProcVersionSignature: Ubuntu 5.19.0-1009.9-allwinner 5.19.17
  Uname: Linux 5.19.0-1009-allwinner riscv64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230415.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Sat May  6 18:37:23 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2018657/+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 2018657] [NEW] Sound output fails

2023-05-06 Thread Heinrich Schuchardt
Public bug reported:

I am running Ubuntu Lunar on the LicheeRV dock with a loudspeaker
connected.

The 'aplay -l' command shows that a playback device exists:

# aplay -l
 List of PLAYBACK Hardware Devices 
card 0: sun20icodec [sun20i-codec], device 0: sun20i-codec snd-soc-dummy-dai-0 
[sun20i-codec snd-soc-dummy-dai-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

But playback fails:

$ sudo aplay PinkPanther30.wav 
Playing WAVE 'PinkPanther30.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, 
Mono
aplay: pcm_write:2127: write error: Input/output error

Best regards

Heinrich

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
ProcVersionSignature: Ubuntu 5.19.0-1009.9-allwinner 5.19.17
Uname: Linux 5.19.0-1009-allwinner riscv64
ApportVersion: 2.26.1-0ubuntu2
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20230415.1
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Sat May  6 18:37:23 2023
ProcCpuinfoMinimal:
 processor  : 0
 hart   : 0
 isa: rv64imafdc
 mmu: sv39
 uarch  : thead,c906
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
SourcePackage: linux-allwinner
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug cloud-image lunar riscv64

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

Title:
  Sound output fails

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  I am running Ubuntu Lunar on the LicheeRV dock with a loudspeaker
  connected.

  The 'aplay -l' command shows that a playback device exists:

  # aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sun20icodec [sun20i-codec], device 0: sun20i-codec 
snd-soc-dummy-dai-0 [sun20i-codec snd-soc-dummy-dai-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

  But playback fails:

  $ sudo aplay PinkPanther30.wav 
  Playing WAVE 'PinkPanther30.wav' : Signed 16 bit Little Endian, Rate 22050 
Hz, Mono
  aplay: pcm_write:2127: write error: Input/output error

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
  ProcVersionSignature: Ubuntu 5.19.0-1009.9-allwinner 5.19.17
  Uname: Linux 5.19.0-1009-allwinner riscv64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230415.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Sat May  6 18:37:23 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2018657/+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 1959525] Re: Occasional no display output on 6900XT or if been idle for too long

2023-05-02 Thread Heinrich Schuchardt
Cf. https://gitlab.freedesktop.org/drm/amd/-/issues/2447

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2447
   https://gitlab.freedesktop.org/drm/amd/-/issues/2447

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

Title:
  Occasional no display output on 6900XT or if been idle for too long

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  ## No output at boot
  The dmesg I attached is from when nothing showed at boot.

  Journal output:
  $ journalctl -r --grep amdgpu
  -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 
15:58:40 EST. --
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with 
error -110
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_init+0x77/0x1000 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_pci_probe+0x12a/0x1b0 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_driver_load_kms.cold+0x46/0x83 
[amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_driver_unload_kms+0x43/0x70 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_device_fini+0xc5/0x1e5 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_device_ip_fini.isra.0+0x206/0x2cd 
[amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  gmc_v10_0_sw_fini+0x33/0x40 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_bo_fini+0x12/0x50 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_ttm_fini+0xab/0x100 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid 
amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper 
crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel 
sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci 
xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi
  Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* 
Fail to stop psp ring
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: 
finishing device.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error 
during GPU init
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* 
hw_init of IP block  failed -110
  Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] 
*ERROR* KCQ enable failed
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is 
initialized successfully!
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios 
provided pptable
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if 
version not matched
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if 
version = 0x003d, smu fw if version = 0x0040, smu fw version = 
0x003a4700 (58.71.0)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: 
securedisplay ta ucode is not available
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to 
load VCN firmware
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready.
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 
0x0084 - 0x
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 
0x - 0x1FFF
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 
0x0080 - 0x0083FEFF (16368M used)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not 
presented.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not 
presented.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS 
from VFCT
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory 
Zone (TMZ) feature not supported
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 
0007)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga 
console
  Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu 

[Kernel-packages] [Bug 2018286] Re: amdgpu driver failing repeatedly

2023-05-02 Thread Heinrich Schuchardt
*** This bug is a duplicate of bug 1959525 ***
https://bugs.launchpad.net/bugs/1959525

** This bug has been marked a duplicate of bug 1959525
   Occasional no display output on 6900XT or if been idle for too long

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

Title:
  amdgpu driver failing repeatedly

Status in linux package in Ubuntu:
  New

Bug description:
  From time to time my KDE desktop becomes unresponsive. In the kernel
  log I find errors like the following repeating incessantly:

  03:34.977226 kernel: [ 8355.577322] [drm] PTB located at 0x00F400A0
  03:34.977232 kernel: [ 8355.577356] [drm] PSP is resuming...
  03:34.996756 kernel: [ 8355.597239] [drm] reserve 0x40 from 0xf47fc0 
for PSP TMR
  03:35.204496 kernel: [ 8355.805718] amdgpu :05:00.0: amdgpu: RAS: 
optional ras ta ucode is not available
  03:35.236504 kernel: [ 8355.836957] amdgpu :05:00.0: amdgpu: RAP: 
optional rap ta ucode is not available
  03:35.236523 kernel: [ 8355.836962] amdgpu :05:00.0: amdgpu: 
SECUREDISPLAY: securedisplay ta ucode is not available
  03:35.876947 kernel: [ 8356.474483] [drm] kiq ring mec 2 pipe 1 q 0
  03:36.168521 kernel: [ 8356.767847] amdgpu :05:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
  03:36.168545 kernel: [ 8356.768191] [drm:amdgpu_gfx_enable_kcq [amdgpu]] 
*ERROR* KCQ enable failed
  03:36.168552 kernel: [ 8356.768542] [drm:amdgpu_device_ip_resume_phase2 
[amdgpu]] *ERROR* resume of IP block  failed -110
  03:36.168554 kernel: [ 8356.768895] amdgpu :05:00.0: amdgpu: GPU 
reset(179) failed
  03:36.168559 kernel: [ 8356.769009] amdgpu :05:00.0: amdgpu: GPU reset 
end with ret = -110
  03:36.168565 kernel: [ 8356.769017] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* GPU Recovery Failed: -110
  03:46.328574 kernel: [ 8366.926277] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* ring sdma0 timeout, signaled seq=19364, emitted seq=19366
  03:46.328593 kernel: [ 8366.927059] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* Process information: process  pid 0 thread  pid 0
  03:46.328599 kernel: [ 8366.927731] amdgpu :05:00.0: amdgpu: GPU reset 
begin!
  03:46.501074 kernel: [ 8367.098277] amdgpu :05:00.0: amdgpu: GPU reset 
succeeded, trying to resume
  03:46.501094 kernel: [ 8367.098806] [drm] PCIE GART of 1024M enabled.
  03:46.501099 kernel: [ 8367.098811] [drm] PTB located at 0x00F400A0
  03:46.501109 kernel: [ 8367.098848] [drm] PSP is resuming...
  03:46.521070 kernel: [ 8367.118736] [drm] reserve 0x40 from 0xf47fc0 
for PSP TMR
  03:46.728491 kernel: [ 8367.326740] amdgpu :05:00.0: amdgpu: RAS: 
optional ras ta ucode is not available
  03:46.760475 kernel: [ 8367.358158] amdgpu :05:00.0: amdgpu: RAP: 
optional rap ta ucode is not available
  03:46.760482 kernel: [ 8367.358161] amdgpu :05:00.0: amdgpu: 
SECUREDISPLAY: securedisplay ta ucode is not available
  03:47.384498 kernel: [ 8367.985147] [drm] kiq ring mec 2 pipe 1 q 0
  03:47.680540 kernel: [ 8368.279937] amdgpu :05:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
  03:47.680561 kernel: [ 8368.280273] [drm:amdgpu_gfx_enable_kcq [amdgpu]] 
*ERROR* KCQ enable failed
  03:47.680565 kernel: [ 8368.280618] [drm:amdgpu_device_ip_resume_phase2 
[amdgpu]] *ERROR* resume of IP block  failed -110
  03:47.680570 kernel: [ 8368.280976] amdgpu :05:00.0: amdgpu: GPU 
reset(180) failed
  03:47.680575 kernel: [ 8368.281055] amdgpu :05:00.0: amdgpu: GPU reset 
end with ret = -110
  03:47.680580 kernel: [ 8368.281058] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* GPU Recovery Failed: -110
  03:57.848521 kernel: [ 8378.446230] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* ring sdma0 timeout, signaled seq=19366, emitted seq=19367

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.2.0-21-generic 6.2.0-21.21
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zfsdt  3122 F wireplumber
   /dev/snd/controlC0:  zfsdt  3122 F wireplumber
   /dev/snd/seq:zfsdt  3115 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue May  2 11:13:11 2023
  InstallationDate: Installed on 2021-07-01 (669 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 

[Kernel-packages] [Bug 2018286] Re: amdgpu driver failing repeatedly

2023-05-02 Thread Heinrich Schuchardt
Cf. https://gitlab.freedesktop.org/drm/amd/-/issues/2447

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

Title:
  amdgpu driver failing repeatedly

Status in linux package in Ubuntu:
  New

Bug description:
  From time to time my KDE desktop becomes unresponsive. In the kernel
  log I find errors like the following repeating incessantly:

  03:34.977226 kernel: [ 8355.577322] [drm] PTB located at 0x00F400A0
  03:34.977232 kernel: [ 8355.577356] [drm] PSP is resuming...
  03:34.996756 kernel: [ 8355.597239] [drm] reserve 0x40 from 0xf47fc0 
for PSP TMR
  03:35.204496 kernel: [ 8355.805718] amdgpu :05:00.0: amdgpu: RAS: 
optional ras ta ucode is not available
  03:35.236504 kernel: [ 8355.836957] amdgpu :05:00.0: amdgpu: RAP: 
optional rap ta ucode is not available
  03:35.236523 kernel: [ 8355.836962] amdgpu :05:00.0: amdgpu: 
SECUREDISPLAY: securedisplay ta ucode is not available
  03:35.876947 kernel: [ 8356.474483] [drm] kiq ring mec 2 pipe 1 q 0
  03:36.168521 kernel: [ 8356.767847] amdgpu :05:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
  03:36.168545 kernel: [ 8356.768191] [drm:amdgpu_gfx_enable_kcq [amdgpu]] 
*ERROR* KCQ enable failed
  03:36.168552 kernel: [ 8356.768542] [drm:amdgpu_device_ip_resume_phase2 
[amdgpu]] *ERROR* resume of IP block  failed -110
  03:36.168554 kernel: [ 8356.768895] amdgpu :05:00.0: amdgpu: GPU 
reset(179) failed
  03:36.168559 kernel: [ 8356.769009] amdgpu :05:00.0: amdgpu: GPU reset 
end with ret = -110
  03:36.168565 kernel: [ 8356.769017] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* GPU Recovery Failed: -110
  03:46.328574 kernel: [ 8366.926277] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* ring sdma0 timeout, signaled seq=19364, emitted seq=19366
  03:46.328593 kernel: [ 8366.927059] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* Process information: process  pid 0 thread  pid 0
  03:46.328599 kernel: [ 8366.927731] amdgpu :05:00.0: amdgpu: GPU reset 
begin!
  03:46.501074 kernel: [ 8367.098277] amdgpu :05:00.0: amdgpu: GPU reset 
succeeded, trying to resume
  03:46.501094 kernel: [ 8367.098806] [drm] PCIE GART of 1024M enabled.
  03:46.501099 kernel: [ 8367.098811] [drm] PTB located at 0x00F400A0
  03:46.501109 kernel: [ 8367.098848] [drm] PSP is resuming...
  03:46.521070 kernel: [ 8367.118736] [drm] reserve 0x40 from 0xf47fc0 
for PSP TMR
  03:46.728491 kernel: [ 8367.326740] amdgpu :05:00.0: amdgpu: RAS: 
optional ras ta ucode is not available
  03:46.760475 kernel: [ 8367.358158] amdgpu :05:00.0: amdgpu: RAP: 
optional rap ta ucode is not available
  03:46.760482 kernel: [ 8367.358161] amdgpu :05:00.0: amdgpu: 
SECUREDISPLAY: securedisplay ta ucode is not available
  03:47.384498 kernel: [ 8367.985147] [drm] kiq ring mec 2 pipe 1 q 0
  03:47.680540 kernel: [ 8368.279937] amdgpu :05:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
  03:47.680561 kernel: [ 8368.280273] [drm:amdgpu_gfx_enable_kcq [amdgpu]] 
*ERROR* KCQ enable failed
  03:47.680565 kernel: [ 8368.280618] [drm:amdgpu_device_ip_resume_phase2 
[amdgpu]] *ERROR* resume of IP block  failed -110
  03:47.680570 kernel: [ 8368.280976] amdgpu :05:00.0: amdgpu: GPU 
reset(180) failed
  03:47.680575 kernel: [ 8368.281055] amdgpu :05:00.0: amdgpu: GPU reset 
end with ret = -110
  03:47.680580 kernel: [ 8368.281058] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* GPU Recovery Failed: -110
  03:57.848521 kernel: [ 8378.446230] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* ring sdma0 timeout, signaled seq=19366, emitted seq=19367

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.2.0-21-generic 6.2.0-21.21
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zfsdt  3122 F wireplumber
   /dev/snd/controlC0:  zfsdt  3122 F wireplumber
   /dev/snd/seq:zfsdt  3115 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue May  2 11:13:11 2023
  InstallationDate: Installed on 2021-07-01 (669 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 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: LENOVO 20KV0008GE
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2018286] [NEW] amdgpu driver failing repeatedly

2023-05-02 Thread Heinrich Schuchardt
Public bug reported:

>From time to time my KDE desktop becomes unresponsive. In the kernel log
I find errors like the following repeating incessantly:

03:34.977226 kernel: [ 8355.577322] [drm] PTB located at 0x00F400A0
03:34.977232 kernel: [ 8355.577356] [drm] PSP is resuming...
03:34.996756 kernel: [ 8355.597239] [drm] reserve 0x40 from 0xf47fc0 
for PSP TMR
03:35.204496 kernel: [ 8355.805718] amdgpu :05:00.0: amdgpu: RAS: optional 
ras ta ucode is not available
03:35.236504 kernel: [ 8355.836957] amdgpu :05:00.0: amdgpu: RAP: optional 
rap ta ucode is not available
03:35.236523 kernel: [ 8355.836962] amdgpu :05:00.0: amdgpu: SECUREDISPLAY: 
securedisplay ta ucode is not available
03:35.876947 kernel: [ 8356.474483] [drm] kiq ring mec 2 pipe 1 q 0
03:36.168521 kernel: [ 8356.767847] amdgpu :05:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
03:36.168545 kernel: [ 8356.768191] [drm:amdgpu_gfx_enable_kcq [amdgpu]] 
*ERROR* KCQ enable failed
03:36.168552 kernel: [ 8356.768542] [drm:amdgpu_device_ip_resume_phase2 
[amdgpu]] *ERROR* resume of IP block  failed -110
03:36.168554 kernel: [ 8356.768895] amdgpu :05:00.0: amdgpu: GPU reset(179) 
failed
03:36.168559 kernel: [ 8356.769009] amdgpu :05:00.0: amdgpu: GPU reset end 
with ret = -110
03:36.168565 kernel: [ 8356.769017] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
GPU Recovery Failed: -110
03:46.328574 kernel: [ 8366.926277] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=19364, emitted seq=19366
03:46.328593 kernel: [ 8366.927059] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process  pid 0 thread  pid 0
03:46.328599 kernel: [ 8366.927731] amdgpu :05:00.0: amdgpu: GPU reset 
begin!
03:46.501074 kernel: [ 8367.098277] amdgpu :05:00.0: amdgpu: GPU reset 
succeeded, trying to resume
03:46.501094 kernel: [ 8367.098806] [drm] PCIE GART of 1024M enabled.
03:46.501099 kernel: [ 8367.098811] [drm] PTB located at 0x00F400A0
03:46.501109 kernel: [ 8367.098848] [drm] PSP is resuming...
03:46.521070 kernel: [ 8367.118736] [drm] reserve 0x40 from 0xf47fc0 
for PSP TMR
03:46.728491 kernel: [ 8367.326740] amdgpu :05:00.0: amdgpu: RAS: optional 
ras ta ucode is not available
03:46.760475 kernel: [ 8367.358158] amdgpu :05:00.0: amdgpu: RAP: optional 
rap ta ucode is not available
03:46.760482 kernel: [ 8367.358161] amdgpu :05:00.0: amdgpu: SECUREDISPLAY: 
securedisplay ta ucode is not available
03:47.384498 kernel: [ 8367.985147] [drm] kiq ring mec 2 pipe 1 q 0
03:47.680540 kernel: [ 8368.279937] amdgpu :05:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
03:47.680561 kernel: [ 8368.280273] [drm:amdgpu_gfx_enable_kcq [amdgpu]] 
*ERROR* KCQ enable failed
03:47.680565 kernel: [ 8368.280618] [drm:amdgpu_device_ip_resume_phase2 
[amdgpu]] *ERROR* resume of IP block  failed -110
03:47.680570 kernel: [ 8368.280976] amdgpu :05:00.0: amdgpu: GPU reset(180) 
failed
03:47.680575 kernel: [ 8368.281055] amdgpu :05:00.0: amdgpu: GPU reset end 
with ret = -110
03:47.680580 kernel: [ 8368.281058] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
GPU Recovery Failed: -110
03:57.848521 kernel: [ 8378.446230] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=19366, emitted seq=19367

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.2.0-21-generic 6.2.0-21.21
ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
Uname: Linux 6.2.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  zfsdt  3122 F wireplumber
 /dev/snd/controlC0:  zfsdt  3122 F wireplumber
 /dev/snd/seq:zfsdt  3115 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue May  2 11:13:11 2023
InstallationDate: Installed on 2021-07-01 (669 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 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: LENOVO 20KV0008GE
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-21-generic 
root=/dev/mapper/vgubuntu-root ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-21-generic N/A
 linux-backports-modules-6.2.0-21-generic  N/A
 linux-firmware20230323.gitbcdcfbcf-0ubuntu1
RfKill:
 1: phy0: Wireless LAN
Soft blocked: 

[Kernel-packages] [Bug 2016881] Re: Building for Focal fails on riscv64

2023-05-01 Thread Heinrich Schuchardt
We don't support any RISC-V boards on Bionic.

** Changed in: zfs-linux (Ubuntu Bionic)
   Status: Confirmed => Invalid

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

Title:
  Building for Focal fails on riscv64

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Invalid
Status in zfs-linux source package in Focal:
  Confirmed

Bug description:
  Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a
  single patch missing:
  https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2016881] Re: Building for Focal fails on riscv64

2023-04-18 Thread Heinrich Schuchardt
** Patch added: "zfs-linux-0.8.3-1ubuntu12.15..0.8.3-1ubuntu12.16.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+attachment/5664989/+files/zfs-linux-0.8.3-1ubuntu12.15..0.8.3-1ubuntu12.16.debdiff

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

Title:
  Building for Focal fails on riscv64

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a
  single patch missing:
  https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2016881] [NEW] Building for Focal fails on riscv64

2023-04-18 Thread Heinrich Schuchardt
Public bug reported:

Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single
patch missing:
https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

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

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

Title:
  Building for Focal fails on riscv64

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a
  single patch missing:
  https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2013743] Re: USB not working on Nezha D1

2023-04-17 Thread Heinrich Schuchardt
Kernel 5.19.0-1009-allwinner does not show this issue.

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

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

Title:
  USB not working on Nezha D1

Status in linux-allwinner package in Ubuntu:
  Fix Released

Bug description:
  I am testing the Allwinner Nezha D1 board according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results

  Hitting a key on the USB keyboard (that was plugged in at boot)
  results in

  [  760.275027] usb 3-1: device descriptor read/64, error -71
  [  761.671031] usb 1-1: device descriptor read/64, error -62
  [  761.975011] usb 1-1: device descriptor read/64, error -62
  [  762.466981] usb 1-1: device descriptor read/64, error -62
  [  762.770995] usb 1-1: device descriptor read/64, error -62
  [  763.514994] usb 1-1: device not accepting address 17, error -62
  [  764.122989] usb 1-1: device not accepting address 18, error -62
  [  764.129829] usb usb1-port1: unable to enumerate USB device

  lsusb does not show the keyboard:

  $ lsusb
  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3
  ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7
  Uname: Linux 5.19.0-1003-allwinner riscv64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230329
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Mar 31 14:31:08 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2012559] Re: 6.2 kernel won't boot, may be nvidia related?

2023-04-04 Thread Heinrich Schuchardt
The upgrade of 515 worked fine I now can work with kernel
6.2.0-18-generic.

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

** Changed in: nvidia-graphics-drivers-515 (Ubuntu Lunar)
   Status: In Progress => 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/2012559

Title:
  6.2 kernel won't boot, may be nvidia related?

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Invalid
Status in nvidia-graphics-drivers-515 source package in Lunar:
  Fix Released

Bug description:
  After installing most recent Lunar updates, linux-
  image-6.2.0-18-generic won't boot. First attempt to boot hung with
  gpu-manager service and other services blocked, something related to
  nvidia seemed to be going wrong. Subsequent attempts blocked at
  systemd-modules, I believe. Reverting to 6.1, boots fine.

  It did boot up enough on one attempt that I was able to SSH in, even
  though I couldn't log in on the console because it never got the point
  of starting up the session manager or init on the other VTs. I'm
  attaching a journalctl log from before the first reboot attempt.
  Perhaps there is something illuminating in there; I honestly can't
  tell.

  Note that while trying to get it to finish booting the first time when
  I was SSH'd in I did kill some processes, so you'll see that in the
  log.

  But just to reiterate, I attempted booting several times after that
  and it never came up to the point of being on the network.

  I thought maybe it might be a DisplayLink issue, but the problem
  persisted even when I rebooted without the DisplayLink hub plugged in.

  Note also that as I said above I had to revert to 6.1 to get it to
  boot, so you'll see that as the last (successful) boot attempt in the
  log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-18-generic 6.2.0-18.18
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 22 16:33:06 2023
  InstallationDate: Installed on 2019-01-02 (1540 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.1.0-16-generic N/A
   linux-backports-modules-6.1.0-16-generic  N/A
   linux-firmware20230316.gitc761dbe8-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+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 2007829] Re: USB keyboard not detected

2023-04-03 Thread Heinrich Schuchardt
*** This bug is a duplicate of bug 2013743 ***
https://bugs.launchpad.net/bugs/2013743

** This bug has been marked a duplicate of bug 2013743
   USB not working on Nezha D1

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

Title:
  USB keyboard not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am currently testing the Nezha image according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271832/testcases/1755/results

  When I plugin a USB keyboard after the system is up it is correctly
  discovered.

  When I power up the device with a plugged in USB keyboard it is not
  detected. See the relevant kernel messages below.

  
  [  +0.000651] usbcore: registered new interface driver usbfs
  [  +0.000162] usbcore: registered new interface driver hub
  [  +0.000128] usbcore: registered new device driver usb
  [  +0.001479] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
  [  +0.000489] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
  [  +0.000532] uhci_hcd: USB Universal Host Controller Interface driver
  [  +0.000787] usbcore: registered new interface driver uas
  [  +0.000157] usbcore: registered new interface driver usb-storage
  [  +0.000300] usbcore: registered new interface driver usbserial_generic
  [  +0.000104] usbserial: USB Serial support registered for generic
  [  +0.000118] usbcore: registered new interface driver ch341
  [  +0.94] usbserial: USB Serial support registered for ch341-uart
  [  +0.007873] ehci-platform 4101000.usb: EHCI Host Controller
  [  +0.005820] ehci-platform 4101000.usb: new USB bus registered, assigned bus 
number 1
  [  +0.008338] ehci-platform 4101000.usb: irq 107, io mem 0x04101000
  [  +0.014689] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
  [  +0.006889] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.17
  [  +0.008389] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007304] usb usb1: Product: EHCI Host Controller
  [  +0.004955] usb usb1: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd
  [  +0.006776] usb usb1: SerialNumber: 4101000.usb
  [  +0.006016] hub 1-0:1.0: USB hub found
  [  +0.006124] ehci-platform 420.usb: EHCI Host Controller
  [  +0.005820] ehci-platform 420.usb: new USB bus registered, assigned bus 
number 2
  [  +0.008177] ehci-platform 420.usb: irq 109, io mem 0x0420
  [  +0.019500] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
  [  +0.006924] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.17
  [  +0.008406] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007308] usb usb2: Product: EHCI Host Controller
  [  +0.004956] usb usb2: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd
  [  +0.006773] usb usb2: SerialNumber: 420.usb
  [  +0.006015] hub 2-0:1.0: USB hub found
  [  +0.030690] ohci-platform 4101400.usb: Generic Platform OHCI controller
  [  +0.006797] ohci-platform 4101400.usb: new USB bus registered, assigned bus 
number 3
  [  +0.008115] ohci-platform 4101400.usb: irq 108, io mem 0x04101400
  [  +0.069475] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 5.17
  [  +0.008365] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007300] usb usb3: Product: Generic Platform OHCI controller
  [  +0.006002] usb usb3: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd
  [  +0.006775] usb usb3: SerialNumber: 4101400.usb
  [  +0.005758] hub 3-0:1.0: USB hub found
  [  +0.006081] ohci-platform 4200400.usb: Generic Platform OHCI controller
  [  +0.006750] ohci-platform 4200400.usb: new USB bus registered, assigned bus 
number 4
  [  +0.008506] ohci-platform 4200400.usb: irq 110, io mem 0x04200400
  [  +0.068747] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 5.17
  [  +0.008395] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007335] usb usb4: Product: Generic Platform OHCI controller
  [  +0.006003] usb usb4: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd
  [  +0.006778] usb usb4: SerialNumber: 4200400.usb
  [  +0.006154] hub 4-0:1.0: USB hub found
  [  +0.016572] usb 2-1: new high-speed USB device number 2 using ehci-platform
  [  +0.613864] usb 4-1: new low-speed USB device number 2 using ohci-platform
  [  +0.207989] usb 4-1: device descriptor read/64, error -62
  [  +0.304014] usb 4-1: device descriptor read/64, error -62
  [  +0.29] usb 4-1: new low-speed USB device number 3 using ohci-platform
  [  +0.208012] usb 4-1: device descriptor read/64, error -62
  [  +0.303984] usb 4-1: device descriptor read/64, error -62
  [  +0.112175] usb usb4-port1: attempt power cycle
  [  +0.511829] usb 4-1: new low-speed USB device number 4 using ohci-platform
  [  +0.431956] usb 4-1: device not accepting address 

[Kernel-packages] [Bug 2013743] Re: USB not working on Nezha D1

2023-04-03 Thread Heinrich Schuchardt
@Kai-Heng Feng (kaihengfeng)
Concerning your question in LP #2007829: If this is a regression cannot be 
answered as the test case did not cover it.

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

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

Title:
  USB not working on Nezha D1

Status in linux-allwinner package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Allwinner Nezha D1 board according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results

  Hitting a key on the USB keyboard (that was plugged in at boot)
  results in

  [  760.275027] usb 3-1: device descriptor read/64, error -71
  [  761.671031] usb 1-1: device descriptor read/64, error -62
  [  761.975011] usb 1-1: device descriptor read/64, error -62
  [  762.466981] usb 1-1: device descriptor read/64, error -62
  [  762.770995] usb 1-1: device descriptor read/64, error -62
  [  763.514994] usb 1-1: device not accepting address 17, error -62
  [  764.122989] usb 1-1: device not accepting address 18, error -62
  [  764.129829] usb usb1-port1: unable to enumerate USB device

  lsusb does not show the keyboard:

  $ lsusb
  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3
  ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7
  Uname: Linux 5.19.0-1003-allwinner riscv64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230329
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Mar 31 14:31:08 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2013743] Re: USB not working on Nezha D1

2023-03-31 Thread Heinrich Schuchardt
** Tags added: iso-testing

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

Title:
  USB not working on Nezha D1

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  I am testing the Allwinner Nezha D1 board according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results

  Hitting a key on the USB keyboard (that was plugged in at boot)
  results in

  [  760.275027] usb 3-1: device descriptor read/64, error -71
  [  761.671031] usb 1-1: device descriptor read/64, error -62
  [  761.975011] usb 1-1: device descriptor read/64, error -62
  [  762.466981] usb 1-1: device descriptor read/64, error -62
  [  762.770995] usb 1-1: device descriptor read/64, error -62
  [  763.514994] usb 1-1: device not accepting address 17, error -62
  [  764.122989] usb 1-1: device not accepting address 18, error -62
  [  764.129829] usb usb1-port1: unable to enumerate USB device

  lsusb does not show the keyboard:

  $ lsusb
  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3
  ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7
  Uname: Linux 5.19.0-1003-allwinner riscv64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230329
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Mar 31 14:31:08 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2013743] [NEW] USB not working on Nezha D1

2023-03-31 Thread Heinrich Schuchardt
Public bug reported:

I am testing the Allwinner Nezha D1 board according to
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results

Hitting a key on the USB keyboard (that was plugged in at boot) results
in

[  760.275027] usb 3-1: device descriptor read/64, error -71
[  761.671031] usb 1-1: device descriptor read/64, error -62
[  761.975011] usb 1-1: device descriptor read/64, error -62
[  762.466981] usb 1-1: device descriptor read/64, error -62
[  762.770995] usb 1-1: device descriptor read/64, error -62
[  763.514994] usb 1-1: device not accepting address 17, error -62
[  764.122989] usb 1-1: device not accepting address 18, error -62
[  764.129829] usb usb1-port1: unable to enumerate USB device

lsusb does not show the keyboard:

$ lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3
ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7
Uname: Linux 5.19.0-1003-allwinner riscv64
ApportVersion: 2.26.0-0ubuntu2
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20230329
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Fri Mar 31 14:31:08 2023
ProcCpuinfoMinimal:
 processor  : 0
 hart   : 0
 isa: rv64imafdc
 mmu: sv39
 uarch  : thead,c906
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
SourcePackage: linux-allwinner
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug cloud-image lunar riscv64

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

Title:
  USB not working on Nezha D1

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  I am testing the Allwinner Nezha D1 board according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results

  Hitting a key on the USB keyboard (that was plugged in at boot)
  results in

  [  760.275027] usb 3-1: device descriptor read/64, error -71
  [  761.671031] usb 1-1: device descriptor read/64, error -62
  [  761.975011] usb 1-1: device descriptor read/64, error -62
  [  762.466981] usb 1-1: device descriptor read/64, error -62
  [  762.770995] usb 1-1: device descriptor read/64, error -62
  [  763.514994] usb 1-1: device not accepting address 17, error -62
  [  764.122989] usb 1-1: device not accepting address 18, error -62
  [  764.129829] usb usb1-port1: unable to enumerate USB device

  lsusb does not show the keyboard:

  $ lsusb
  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3
  ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7
  Uname: Linux 5.19.0-1003-allwinner riscv64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230329
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Mar 31 14:31:08 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2013743] Re: USB not working on Nezha D1

2023-03-31 Thread Heinrich Schuchardt
After unplugging and replugging the keyboard:

$ lsusb
Bus 001 Device 019: ID 046a:0011 Cherry GmbH G83 (RS 6000) Keyboard
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

But that is not how it is meant to work.

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

Title:
  USB not working on Nezha D1

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  I am testing the Allwinner Nezha D1 board according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results

  Hitting a key on the USB keyboard (that was plugged in at boot)
  results in

  [  760.275027] usb 3-1: device descriptor read/64, error -71
  [  761.671031] usb 1-1: device descriptor read/64, error -62
  [  761.975011] usb 1-1: device descriptor read/64, error -62
  [  762.466981] usb 1-1: device descriptor read/64, error -62
  [  762.770995] usb 1-1: device descriptor read/64, error -62
  [  763.514994] usb 1-1: device not accepting address 17, error -62
  [  764.122989] usb 1-1: device not accepting address 18, error -62
  [  764.129829] usb usb1-port1: unable to enumerate USB device

  lsusb does not show the keyboard:

  $ lsusb
  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3
  ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7
  Uname: Linux 5.19.0-1003-allwinner riscv64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230329
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Mar 31 14:31:08 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2012559] Re: 6.2 kernel won't boot, may be nvidia related?

2023-03-25 Thread Heinrich Schuchardt
Duplicate bug report LP #2012706 contains some more logs.

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

Title:
  6.2 kernel won't boot, may be nvidia related?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing most recent Lunar updates, linux-
  image-6.2.0-18-generic won't boot. First attempt to boot hung with
  gpu-manager service and other services blocked, something related to
  nvidia seemed to be going wrong. Subsequent attempts blocked at
  systemd-modules, I believe. Reverting to 6.1, boots fine.

  It did boot up enough on one attempt that I was able to SSH in, even
  though I couldn't log in on the console because it never got the point
  of starting up the session manager or init on the other VTs. I'm
  attaching a journalctl log from before the first reboot attempt.
  Perhaps there is something illuminating in there; I honestly can't
  tell.

  Note that while trying to get it to finish booting the first time when
  I was SSH'd in I did kill some processes, so you'll see that in the
  log.

  But just to reiterate, I attempted booting several times after that
  and it never came up to the point of being on the network.

  I thought maybe it might be a DisplayLink issue, but the problem
  persisted even when I rebooted without the DisplayLink hub plugged in.

  Note also that as I said above I had to revert to 6.1 to get it to
  boot, so you'll see that as the last (successful) boot attempt in the
  log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-18-generic 6.2.0-18.18
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 22 16:33:06 2023
  InstallationDate: Installed on 2019-01-02 (1540 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.1.0-16-generic N/A
   linux-backports-modules-6.1.0-16-generic  N/A
   linux-firmware20230316.gitc761dbe8-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+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 2012706] Re: linux-image-6.2.0-18-generic: booting with Nvidia drivers fails

2023-03-25 Thread Heinrich Schuchardt
*** This bug is a duplicate of bug 2012559 ***
https://bugs.launchpad.net/bugs/2012559

** This bug has been marked a duplicate of bug 2012559
   6.2 kernel won't boot, may be nvidia related?

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

Title:
  linux-image-6.2.0-18-generic: booting with Nvidia drivers fails

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update to 6.2.0-18-generic booting with Nvidia drivers
  fails. The last message is:

  Job gpu-manager.service start running (3min 22s / no limit)

  With 6.1.0-16-generic the problem does not occur.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-18-generic 6.2.0-18.18
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 24 09:29:48 2023
  InstallationDate: Installed on 2021-05-26 (666 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic 
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G 
hugepages=4
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.1.0-16-generic N/A
   linux-backports-modules-6.1.0-16-generic  N/A
   linux-firmware20230316.gitc761dbe8-0ubuntu1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4204
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  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/2012706/+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 2012706] [NEW] linux-image-6.2.0-18-generic: booting with Nvidia drivers fails

2023-03-24 Thread Heinrich Schuchardt
Public bug reported:

After the update to 6.2.0-18-generic booting with Nvidia drivers fails.
The last message is:

Job gpu-manager.service start running (3min 22s / no limit)

With 6.1.0-16-generic the problem does not occur.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-18-generic 6.2.0-18.18
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Mar 24 09:29:48 2023
InstallationDate: Installed on 2021-05-26 (666 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic 
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G 
hugepages=4
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.1.0-16-generic N/A
 linux-backports-modules-6.1.0-16-generic  N/A
 linux-firmware20230316.gitc761dbe8-0ubuntu1
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4204
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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

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


** Tags: amd64 apport-bug lunar

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

Title:
  linux-image-6.2.0-18-generic: booting with Nvidia drivers fails

Status in linux package in Ubuntu:
  New

Bug description:
  After the update to 6.2.0-18-generic booting with Nvidia drivers
  fails. The last message is:

  Job gpu-manager.service start running (3min 22s / no limit)

  With 6.1.0-16-generic the problem does not occur.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-18-generic 6.2.0-18.18
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 24 09:29:48 2023
  InstallationDate: Installed on 2021-05-26 (666 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic 
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G 
hugepages=4
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.1.0-16-generic N/A
   linux-backports-modules-6.1.0-16-generic  N/A
   linux-firmware20230316.gitc761dbe8-0ubuntu1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4204
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  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/2012706/+subscriptions


-- 
Mailing list: 

  1   2   3   >