[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY
For all previous kernels and the 6.8.0-31-generic in Noble detection have been an issue. As long as the cable is attached at boot it does work. -- 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 2061897] [NEW] Enable Milk-V Mars board
Public bug reported: Apply relevant patches to the linux-riscv kernel to support the Milk-V Mars board based on the StarFive JH7110 SoC. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- 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/2061897 Title: Enable Milk-V Mars board Status in linux-riscv package in Ubuntu: New Bug description: Apply relevant patches to the linux-riscv kernel to support the Milk-V Mars board based on the StarFive JH7110 SoC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2061897/+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 2046608] Re: The fan of VisionFive2 still works after I power it off.
If you look at page 2 of the schematic:
https://doc-en.rvspace.org/VisionFive2/PDF/SCH_RV002_V1.2A_20221216.pdf
you'll see that the fan is connected directly to the 5V power supply.
There is no way to turn it off but to cut the power to the whole board.
Marking as invalid.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/2046608
Title:
The fan of VisionFive2 still works after I power it off.
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Invalid
Bug description:
The fan of VisionFive2 still works after I power it off.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.4
ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
Date: Sat Dec 16 10:23:41 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.2
InstallationDate: Installed on 2023-09-19 (88 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64
(20231011)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 Silicon Motion, Inc. SM2263EN/SM2263XT
(DRAM-less) NVMe SSD Controllers
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS
802.11n Wireless Network Adapter
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 3, If 0, Class=Vendor Specific Class,
Driver=rtl8xxxu, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=tmux-256color
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046608/+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 2046714] Re: Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.
The naming is definitely confusing, but the starfive kernel was named
before the VisionFive 2 was about and is only needed for the VisionFive
V1 (and BeagleV Starlight) boards, where the JH7100 SoC needs some
special handling.
On the VisionFive 2 you should just use the generic kernel like the
image you downloaded.
** Changed in: linux-meta-starfive (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-starfive in Ubuntu.
https://bugs.launchpad.net/bugs/2046714
Title:
Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.
Status in linux-meta-starfive package in Ubuntu:
Invalid
Bug description:
I have installed Ubuntu Server on My VisionFive v2, the Kernel version is
6.5.0-14-generic, I notice the new Kernel linux-image-starfive(= 6.5.0.1005.7)
was released and I upgrade it, and then VisionFive v2 crashes while it boots.
the initramfs message:
ALERT! /dev/mapper/ubuntu--vg-ubuntu--lv does not exist. Dropping to a
shell!
Hope it could be fixed soon. Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-starfive 6.5.0.1005.7
ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Dec 18 07:00:45 2023
InstallationDate: Installed on 2023-09-19 (90 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64
(20231011)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=tmux-256color
SourcePackage: linux-meta-starfive
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-starfive/+bug/2046714/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
I don't have a good explanation, but in the past I've "fixed" such races by adding a `sync "$loop_device"` before using any of the newly created partitons. Maybe it's worth trying. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2043187] Re: Debug symbols in linux-modules package
** Description changed: On amd64 the linux-modules package contains debug symbols for the - vdso32.so and vdso64.so shared libraries: + vdso32.so, vdso64.so, and vdsox32.so shared libraries: https://packages.ubuntu.com/mantic-updates/amd64/linux-modules-6.5.0-10-generic/filelist https://packages.ubuntu.com/jammy-updates/amd64/linux-modules-5.15.0-88-generic/filelist https://packages.ubuntu.com/focal-updates/amd64/linux-modules-5.4.0-166-generic/filelist -- 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/2043187 Title: Debug symbols in linux-modules package Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Mantic: New Bug description: On amd64 the linux-modules package contains debug symbols for the vdso32.so, vdso64.so, and vdsox32.so shared libraries: https://packages.ubuntu.com/mantic-updates/amd64/linux-modules-6.5.0-10-generic/filelist https://packages.ubuntu.com/jammy-updates/amd64/linux-modules-5.15.0-88-generic/filelist https://packages.ubuntu.com/focal-updates/amd64/linux-modules-5.4.0-166-generic/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043187/+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 2043187] Re: Debug symbols in linux-modules package
** Description changed: On amd64 the linux-modules package contains debug symbols for the vdso32.so and vdso64.so shared libraries: - https://packages.ubuntu.com/mantic-updates/amd64/linux- - modules-6.5.0-10-generic/filelist + https://packages.ubuntu.com/mantic-updates/amd64/linux-modules-6.5.0-10-generic/filelist + https://packages.ubuntu.com/focal-updates/amd64/linux-modules-5.4.0-166-generic/filelist ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: On amd64 the linux-modules package contains debug symbols for the vdso32.so and vdso64.so shared libraries: https://packages.ubuntu.com/mantic-updates/amd64/linux-modules-6.5.0-10-generic/filelist + https://packages.ubuntu.com/jammy-updates/amd64/linux-modules-5.15.0-88-generic/filelist https://packages.ubuntu.com/focal-updates/amd64/linux-modules-5.4.0-166-generic/filelist ** Also affects: linux (Ubuntu Jammy) 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/2043187 Title: Debug symbols in linux-modules package Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Mantic: New Bug description: On amd64 the linux-modules package contains debug symbols for the vdso32.so and vdso64.so shared libraries: https://packages.ubuntu.com/mantic-updates/amd64/linux-modules-6.5.0-10-generic/filelist https://packages.ubuntu.com/jammy-updates/amd64/linux-modules-5.15.0-88-generic/filelist https://packages.ubuntu.com/focal-updates/amd64/linux-modules-5.4.0-166-generic/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043187/+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 2043187] Re: Debug symbols in linux-modules package
** Also affects: linux (Ubuntu Mantic) 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/2043187 Title: Debug symbols in linux-modules package Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Bug description: On amd64 the linux-modules package contains debug symbols for the vdso32.so and vdso64.so shared libraries: https://packages.ubuntu.com/mantic-updates/amd64/linux- modules-6.5.0-10-generic/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043187/+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 2043187] [NEW] Debug symbols in linux-modules package
Public bug reported: On amd64 the linux-modules package contains debug symbols for the vdso32.so and vdso64.so shared libraries: https://packages.ubuntu.com/mantic-updates/amd64/linux- modules-6.5.0-10-generic/filelist ** Affects: linux (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/2043187 Title: Debug symbols in linux-modules package Status in linux package in Ubuntu: New Bug description: On amd64 the linux-modules package contains debug symbols for the vdso32.so and vdso64.so shared libraries: https://packages.ubuntu.com/mantic-updates/amd64/linux- modules-6.5.0-10-generic/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043187/+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
This is a test kernel that only contains JH7110 patches but not yet the D1 patches, so this is expected behaviour for that kernel. ** Changed in: linux-meta-riscv (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/2037000 Title: No HDMI output with 6.5.0-2-generic Status in linux-meta-riscv package in Ubuntu: Invalid 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 2024935] Re: cpu 2.7x slower on ubuntu server 23.04 riscv64 Nezha/Sipeed images compared to 22.10 on mangopi mq-pro
*** This bug is a duplicate of bug 2021364 ***
https://bugs.launchpad.net/bugs/2021364
Hey, sorry for not noticing before. You're right this was a bug and
should be fixed in the 6.2 kernel in Lunar. It will also be backported
to Jammy soon.
** This bug has been marked a duplicate of bug 2021364
Linux 6.2 fails to reboot with current u-boot-nezha
--
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/2024935
Title:
cpu 2.7x slower on ubuntu server 23.04 riscv64 Nezha/Sipeed images
compared to 22.10 on mangopi mq-pro
Status in linux-allwinner package in Ubuntu:
New
Bug description:
I think I found a bug/regression with the ubuntu server 23.04 riscv64
Nezha/Sipeed kernels.
Somehow, the CPU speed on my mangopi mq pro seems to have decreased by 2.7x
compared to the 22.10 image.
The allwinner D1 should run at 1Ghz, and execute a single add per cycle.
On 22.10 I was able to confirm that executing `1024*1024*1024` add
instructions took roughly a second, but on 23.04 it took 2.7 seconds (both
fresh installs, with the same code [1]).
There were no resource hungry background processes running, when I
checked top.
I also binary patched the opensbi image afterward, to disable mcountinhibit
for `rdcycle`, and confirmed that even the hardware cycle counter was slower
than 1Ghz. [2]
One second had 410398820 cycles instead of something closer to the expected
1073741824.
On suggestion from the #ubuntu webchat, I also tested adding
`mitigations=off` to the linux cmd options, but that didn't change
anything.
[1]
// test.c
#include
#include
int main(void)
{
for (int i = 0; i < 10; ++i) {
clock_t beg = clock();
extern void foo(void);
foo();
printf("%f\n", (clock() - beg) * 1.0/CLOCKS_PER_SEC);
}
}
// test.S
.text
.global foo
foo:
li t0, (1024*1024*1024/(8*32))
1:
.rept 32
add a1, a1, a0
add a2, a2, a1
add a3, a3, a2
add a4, a4, a3
add a5, a5, a4
add a6, a6, a5
add a7, a7, a6
add a0, a0, a7
.endr
addit0, t0, -1
bnezt0, 1b
ret
$ gcc -Ofast -march=rv64gc test.* && ./a.out
[2] https://github.com/camel-cdr/rvv-d1/#extra-enable-rdcycle
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
ProcVersionSignature: User Name 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.2
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Fri Jun 23 20:10:14 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=st-256color
XDG_RUNTIME_DIR=
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/2024935/+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 1967130] Re: rcu_sched detected stalls on CPUs/tasks
This should now be fixed by the upstream commit:
3f105a742725 ("riscv: Sync efi page table's kernel mappings before switching")
--
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/1967130
Title:
rcu_sched detected stalls on CPUs/tasks
Status in linux-riscv package in Ubuntu:
Fix Released
Bug description:
When running the riscv64 live installer
(https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-
live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly
see rcu_sched stalls related to accessing the UEFI runtime:
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched
detected stalls on CPUs/tasks:
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3
GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0,
t=15002 jiffies, g=155853, q=1286)
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3:
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1
state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq
efi_call_rts
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace:
Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] []
__schedule+0x226/0x644
uname -a:
Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC
2022 riscv64 riscv64 riscv64 GNU/Linux
---
ProblemType: Bug
Architecture: riscv64
DistroRelease: Ubuntu 22.04
Package: linux-image-generic 5.15.0.1004.4
PackageArchitecture: riscv64
ProcEnviron:
TERM=vt220
PATH=(custom, no user)
LANG=C.UTF-8
Uname: Linux 5.15.0-1004-generic riscv64
UserGroups: N/A
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+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 1975592] Re: Enable Nezha board
** Description changed: - Enable Nezha board + [Impact] + Enable the Allwinner D1 based Nezha, Lichee RV and MangoPi MQ Pro boards. + Patches yet to make it upstream are available from Samuel Hollands tree at + https://github.com/smaeul/linux - Apply relevant patches to linux-riscv-5.17 kernel to enable nezha kernel - flavour. + [Test] + Cherry pick patches and run the kernel on the various boards and see that devices that does not yet have upstream support. - Backport patches from https://github.com/AlexGhiti/riscv- - linux/tree/int/alex/nezha_Ubuntu-unstable-5.17.0-8.8 + [Regression potential] + The out-of-tree patches may interfere with other supported boards, so make sure to test on those too. -- 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-riscv package in Ubuntu: Fix Committed Bug description: [Impact] Enable the Allwinner D1 based Nezha, Lichee RV and MangoPi MQ Pro boards. Patches yet to make it upstream are available from Samuel Hollands tree at https://github.com/smaeul/linux [Test] Cherry pick patches and run the kernel on the various boards and see that devices that does not yet have upstream support. [Regression potential] The out-of-tree patches may interfere with other supported boards, so make sure to test on those too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+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 2013232] [NEW] Enable StarFive VisionFive 2 board
Public bug reported: Apply relevant patches to the linux-riscv kernel to support the StarFive JH7110 SoC and their StarFive VisionFive 2 board. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- 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/2013232 Title: Enable StarFive VisionFive 2 board Status in linux-riscv package in Ubuntu: New Bug description: Apply relevant patches to the linux-riscv kernel to support the StarFive JH7110 SoC and their StarFive VisionFive 2 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2013232/+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 1986833] Re: PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree
** Changed in: linux-riscv (Ubuntu) Status: New => Fix Released -- 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/1986833 Title: PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree Status in linux-riscv package in Ubuntu: Fix Released Bug description: [Impact] The 5.19 kernel contains support for the PolarFire Icicle board. But booting with linux-image-5.19.0-1002-generic_5.19.0-1002.2_riscv64.deb fails. The cause is that the device-tree incorrectly specifies the PLIC interrupts used for the drivers/soc/sifive/sifive_l2_cache.c. A patch is available as https://lore.kernel.org/all/20220817132521.3159388-1-heinrich.schucha...@canonical.com/ [PATCH 1/1] riscv: dts: microchip: correct L2 cache interrupts This patch only changes the device-tree of the PolarFire Icicle Kit. Please, add the patch to the 5.19 and future kernels. [Test Plan] Use the SiFive Unmatched preinstalled image and install the 5.19 kernel. Try to boot on the Polarfire Icicle board. [Where problems could occur] The fix only concerns a board which has been unsupported by Ubuntu yet. In case of an incorrect fix the board might not boot or otherwise malfunction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1986833/+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 1983019] Re: Pinctrl driver has a race condition bug
** Changed in: linux-starfive-5.17 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1983019 Title: Pinctrl driver has a race condition bug Status in linux-starfive-5.17 package in Ubuntu: Fix Released Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: [Impact] * The pinctrl-starfive driver has a race when initializing groups and functions that may result in other drivers not being able to initialize. * If this happens to the mmc driver the board will fail to boot. * This is an example of this happening: Loading device tree blob... [ 13.933777] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.941940] pinctrl-starfive 1191.pinctrl: invalid group sdio0-0.sdio-pins in map table [ 13.957656] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.965801] pinctrl-starfive 1191.pinctrl: could not map group config for "sdio0-0.sdio-pins" [ 13.974746] Unable to handle kernel NULL pointer dereference at virtual address [ 13.983581] Oops [#1] [ 13.985853] Modules linked in: phylink dw_mmc_pltfm clk_starfive_jh7100_audio reset_starfive_jh7100_audio(+) dw_mc [ 13.986227] starfive-drm soc:display-subsystem: bound 1200.crtc (ops starfive_crtc_component_ops) [ 13.996286] CPU: 1 PID: 8 Comm: kworker/u4:0 Not tainted 5.17.0-1004-starfive #5-Ubuntu [ 13.996297] Hardware name: StarFive VisionFive V1 (DT) [ 13.996305] Workqueue: events_unbound async_run_entry_fn [ 14.023868] epc : strcmp+0x12/0x36 [ 14.027274] ra : pinmux_func_name_to_selector+0x5a/0x76 [ 14.032583] epc : 80521224 ra : 805307d8 sp : ffd88006bb00 [ 14.039781] gp : 81e32e30 tp : ffd87ffd t0 : 0040 [ 14.046988] t1 : t2 : 81004ed4 s0 : ffd88006bb10 [ 14.054190] s1 : 0006 a0 : ffd9ff1d3cb8 a1 : [ 14.061392] a2 : a3 : a4 : ffd88c45ce00 [ 14.068594] a5 : 0073 a6 : ffd88c45cdb0 a7 : ffd88c45ce08 [ 14.075795] s2 : ffd897c53000 s3 : 0007 s4 : ffd9ff1d3cb8 [ 14.082996] s5 : 810776f0 s6 : s7 : ffd8801aa5c0 [ 14.090199] s8 : ffd890fdf780 s9 : fdfb s10: 81d80008 [ 14.097400] s11: t3 : 0002 t4 : 0402 [ 14.104600] t5 : ffd897c53040 t6 : ffd897c53048 [ 14.109896] status: 00020120 badaddr: cause: 000d [ 14.117986] ---[ end trace ]--- [Test Plan] * Unfortunately this is a race that happens rarely so rebooting the board several times is the only known way to reproduce. [Where problems could occur] * The fix could get the locking wrong and lock up the machine at boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1983019/+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 1988984] Re: earlyconsole prints question marks on 5.19.0-1002-generic
** Changed in: linux-meta-riscv (Ubuntu)
Status: New => Fix Released
--
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/1988984
Title:
earlyconsole prints question marks on 5.19.0-1002-generic
Status in linux-meta-riscv package in Ubuntu:
Fix Released
Bug description:
earlyconsole prints on 5.19.0-1002-generic
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board the serial console will print garbage
halfway through booting until entering userspace and other
other drivers are loaded.
* The problem is the UART driver doesn't claim its clocks
properly so the PWM driver will turn off the parent clock
until PWM is needed for the LEDs on the board.
* Compiling the PWM driver as a module so it will be loaded
at the same time the LED drivers are loaded is a workaround
until the following patch is backported
643792048ee8 ("serial: sifive: enable clocks for UART when probed")
* Only the SoCs on the SiFive Unleashed and Unmatched boards use
this PWM driver, but none of them need it at boot time, so should
be harmless.
[ Test Plan ]
* Add earlycon and watch the serial console while booting.
* Test that PWM leds still work after the PWM driver module is
loaded.
[ Where problems could occur ]
* There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+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 1993148] Re: Support Icicle Kit reference design v2022.10
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Emil Renner Berthing (esmil) Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993148/+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 1993148] Re: Support Icicle Kit reference design v2022.10
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- 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/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Incomplete Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993148/+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 1993148] [NEW] Support Icicle Kit reference design v2022.10
Public bug reported: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: [ Impact ] - * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V -cores. So the memory map and some peripherals depend on the FPGA design loaded. + * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 +RISC-V cores. So the memory map and some peripherals depend on the +FPGA design loaded. - * Microchip releases reference designs and are upstreaming support for running -Linux on it. Unfortunately the upcoming v2022.10 release changes the memory -layout compared to earlier versions, but v6.1-rc1 contains patches for it. + * Microchip releases reference designs and are upstreaming support for +running Linux on it. Unfortunately the upcoming v2022.10 release +changes the memor layout compared to earlier versions, but v6.1-rc1 +contains patches for it. - * We'd like to support the v2022.10 release and hopefully future versions -by backporting these changes. + * We'd like to support the v2022.10 release and hopefully future versions + by backporting these changes. [ Test Plan ] - * Update the Icicle Kit to the v2022.10 reference design and check that the -generic riscv64 kernel boots. + * Update the Icicle Kit to the v2022.10 reference design and check that +the generic riscv64 kernel boots. [ Where problems could occur ] - * Users who are running v2022.9 or older versions of the reference design may -have trouble booting, but the Icicle Kit was never officially supported by -Ubuntu. + * Users who are running v2022.9 or older versions of the reference design +may have trouble booting, but the Icicle Kit was never officially +supported by Ubuntu. ** Description changed: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 -RISC-V cores. So the memory map and some peripherals depend on the -FPGA design loaded. + RISC-V cores. So the memory map and some peripherals depend on the + FPGA design loaded. * Microchip releases reference designs and are upstreaming support for -running Linux on it. Unfortunately the upcoming v2022.10 release -changes the memor layout compared to earlier versions, but v6.1-rc1 -contains patches for it. + running Linux on it. Unfortunately the upcoming v2022.10 release + changes the memory layout compared to earlier versions, but v6.1-rc1 + contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that -the generic riscv64 kernel boots. + the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design -may have trouble booting, but the Icicle Kit was never officially -supported by Ubuntu. + may have trouble booting, but the Icicle Kit was never officially + supported by Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Incomplete Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [
[Kernel-packages] [Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks
There is more information in LP: #1992458 -- 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/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: Fix Released Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+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 1991790] Re: Disable sv57 as the userspace is not ready
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- 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/1991790 Title: Disable sv57 as the userspace is not ready Status in linux-riscv package in Ubuntu: New Bug description: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the kernel to downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and other Go programs work correctly and that you can compile a simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. * Qemu will no longer work with > 256 TB of memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1991790/+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 1991790] Re: Disable sv57 as the userspace is not ready
** Description changed: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software - using too many bits for this "pointer tagging" technique. + using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the kernel to downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and - other Go programs works correctly and that you can compile a + other Go programs work correctly and that you can compile a simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. * Qemu will no longer work with > 256 TB of memory. -- 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/1991790 Title: Disable sv57 as the userspace is not ready Status in linux-riscv package in Ubuntu: New Bug description: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the kernel to downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and other Go programs work correctly and that you can compile a simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. * Qemu will no longer work with > 256 TB of memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1991790/+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 1991790] Re: Disable sv57 as the userspace is not ready
** Description changed: [ Impact ] - sv57 breaks Go since Go uses the upper bits of a pointer to store data, - and it is not ready for sv57 yet. It probably breaks other type of - software using this "pointer tagging" technic. The following patch fixes - this: at the moment, there is no way to indicate to the kernel to - downgrade to sv48, so we must patch the kernel. + * Linux 5.18 merged support for 5-level page tables (sv57), and it + does it such that 5-level page tables are used whenever the + system supports it. + + * So far only Qemu support sv57, but it breaks Go since Go uses + too many of the upper bits of pointers to store data, and is not + yet ready for sv57. It probably breaks other types of software + using too many bits for this "pointer tagging" technique. + At the moment, there is no way to indicate to the kernel to + downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) - disable_pgtable_l4(); - } - + disable_pgtable_l4(); + } + + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + - memset(early_pg_dir, 0, PAGE_SIZE); - memset(early_p4d, 0, PAGE_SIZE); - memset(early_pud, 0, PAGE_SIZE); + memset(early_pg_dir, 0, PAGE_SIZE); + memset(early_p4d, 0, PAGE_SIZE); + memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] - Build an image with the new kernel and make sure snapd started - correctly, or that you can compile a simple helloworld written in Go. + * Build an image with the patched kernel and make sure snapd and + other Go programs works correctly and that you can compile a + simple helloworld written in Go. [ Where problems could occur ] - The patch could be wrong, but I already built a kernel with it and it - worked fine. + * The patch could be buggy. + + * Qemu will no longer work with > 128 PB of memory. ** Description changed: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it - does it such that 5-level page tables are used whenever the - system supports it. + does it such that 5-level page tables are used whenever the + system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses - too many of the upper bits of pointers to store data, and is not - yet ready for sv57. It probably breaks other types of software - using too many bits for this "pointer tagging" technique. - At the moment, there is no way to indicate to the kernel to - downgrade to sv48, so we must patch the kernel: + too many of the upper bits of pointers to store data, and is not + yet ready for sv57. It probably breaks other types of software + using too many bits for this "pointer tagging" technique. + At the moment, there is no way to indicate to the kernel to + downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and - other Go programs works correctly and that you can compile a - simple helloworld written in Go. + other Go programs works correctly and that you can compile a + simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. - * Qemu will no longer work with > 128 PB of memory. + * Qemu will no longer work with > 256 TB of memory. -- 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/1991790 Title: Disable sv57 as the userspace is not ready Status in linux-riscv package in Ubuntu: New Bug description: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the
[Kernel-packages] [Bug 1988984] Re: earlyconsole prints ������������������������ on 5.19.0-1002-generic
** Description changed:
[ Impact ]
- * When adding earlycon to the kernel command line on the
-SiFive Unmatched board the serial console will print garbage
-halfway through booting until entering userspace and other
-other drivers are loaded.
+ * When adding earlycon to the kernel command line on the
+ SiFive Unmatched board the serial console will print garbage
+ halfway through booting until entering userspace and other
+ other drivers are loaded.
- * The problem is the UART driver doesn't claim its clocks
-properly so the PWM driver will turn off the parent clock
-until PWM is needed for the LEDs on the board.
+ * The problem is the UART driver doesn't claim its clocks
+ properly so the PWM driver will turn off the parent clock
+ until PWM is needed for the LEDs on the board.
- * Compiling the PWM driver as a module so it will be loaded
-at the same time the LED drivers are loaded is a temporary
-workaround until the following patch is backported
-643792048ee8 ("serial: sifive: enable clocks for UART when probed")
+ * Compiling the PWM driver as a module so it will be loaded
+ at the same time the LED drivers are loaded is a workaround
+until the following patch is backported
+ 643792048ee8 ("serial: sifive: enable clocks for UART when probed")
- * Only the SoCs on the SiFive Unleashed and Unmatched boards use
-this PWM driver, but none of them need it at boot time, so should
-be harmless.
+ * Only the SoCs on the SiFive Unleashed and Unmatched boards use
+ this PWM driver, but none of them need it at boot time, so should
+ be harmless.
[ Test Plan ]
- * Add earlycon and watch the serial console while booting.
+ * Add earlycon and watch the serial console while booting.
- * Test that PWM leds still work after the PWM driver module is loaded.
+ * Test that PWM leds still work after the PWM driver module is loaded.
[ Where problems could occur ]
- * There might be a hidden dependency on loading the PWM driver early.
+ * There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
--
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/1988984
Title:
earlyconsole prints on 5.19.0-1002-generic
Status in linux-meta-riscv package in Ubuntu:
New
Bug description:
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board the serial console will print garbage
halfway through booting until entering userspace and other
other drivers are loaded.
* The problem is the UART driver doesn't claim its clocks
properly so the PWM driver will turn off the parent clock
until PWM is needed for the LEDs on the board.
* Compiling the PWM driver as a module so it will be loaded
at the same time the LED drivers are loaded is a workaround
until the following patch is backported
643792048ee8 ("serial: sifive: enable clocks for UART when probed")
* Only the SoCs on the SiFive Unleashed and Unmatched boards use
this PWM driver, but none of them need it at boot time, so should
be harmless.
[ Test Plan ]
* Add earlycon and watch the serial console while booting.
* Test that PWM leds still work after the PWM driver module is
loaded.
[ Where problems could occur ]
* There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+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 1988984] Re: earlyconsole prints ������������������������ on 5.19.0-1002-generic
** Description changed:
+ [ Impact ]
+
+ * When adding earlycon to the kernel command line on the
+SiFive Unmatched board the serial console will print garbage
+halfway through booting until entering userspace and other
+other drivers are loaded.
+
+ * The problem is the UART driver doesn't claim its clocks
+properly so the PWM driver will turn off the parent clock
+until PWM is needed for the LEDs on the board.
+
+ * Compiling the PWM driver as a module so it will be loaded
+at the same time the LED drivers are loaded is a temporary
+workaround until the following patch is backported
+643792048ee8 ("serial: sifive: enable clocks for UART when probed")
+
+ * Only the SoCs on the SiFive Unleashed and Unmatched boards use
+this PWM driver, but none of them need it at boot time, so should
+be harmless.
+
+ [ Test Plan ]
+
+ * Add earlycon and watch the serial console while booting.
+
+ * Test that PWM leds still work after the PWM driver module is loaded.
+
+ [ Where problems could occur ]
+
+ * There might be a hidden dependency on loading the PWM driver early.
+
+ [ Other Info ]
+
+ Original bug description:
+
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
--
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/1988984
Title:
earlyconsole prints on 5.19.0-1002-generic
Status in linux-meta-riscv package in Ubuntu:
New
Bug description:
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board the serial console will print garbage
halfway through booting until entering userspace and other
other drivers are loaded.
* The problem is the UART driver doesn't claim its clocks
properly so the PWM driver will turn off the parent clock
until PWM is needed for the LEDs on the board.
* Compiling the PWM driver as a module so it will be loaded
at the same time the LED drivers are loaded is a temporary
workaround until the following patch is backported
643792048ee8 ("serial: sifive: enable clocks for UART when probed")
* Only the SoCs on the SiFive Unleashed and Unmatched boards use
this PWM driver, but none of them need it at boot time, so should
be harmless.
[ Test Plan ]
* Add earlycon and watch the serial console while booting.
* Test that PWM leds still work after the PWM driver module is
loaded.
[ Where problems could occur ]
* There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+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 1967889] Re: Raise CONFIG_NR_CPUS
** Description changed: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. - * The QEMU 7.0 virt machine supports up to 512 harts (CPU threads). + * The QEMU 7.0 virt machine supports up to 512 harts +(CPU hardware threads). - * Raising CONFIG_NR_CPUS to 32 allows us to use a reasonable number of them. This matches the allowed maximum in upstream Linux. Patches for - raising the limit are pending. + * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use +more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. - * After raising CONFIG_NR_CPUS to 32 all of them should be used. + * After raising CONFIG_NR_CPUS to 32 up to 32 of them should +be used. [Where problems could occur] - * This will use slightly more RAM which might hurt very small + * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich ** Description changed: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. * The QEMU 7.0 virt machine supports up to 512 harts -(CPU hardware threads). + (CPU hardware threads). * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use -more of them. + more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. - * After raising CONFIG_NR_CPUS to 32 up to 32 of them should -be used. + * After raising CONFIG_NR_CPUS up to 32 of them should be used. [Where problems could occur] * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich ** Description changed: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. - * The QEMU 7.0 virt machine supports up to 512 harts - (CPU hardware threads). + * The QEMU 7.0 virt machine supports up to 512 virtual CPUs. * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. * After raising CONFIG_NR_CPUS up to 32 of them should be used. [Where problems could occur] * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. 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/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. * The QEMU 7.0 virt machine supports up to 512 virtual CPUs. * Raising CONFIG_NR_CPUS to the maximum of 32 allows us to use more of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. * After raising CONFIG_NR_CPUS up to 32 of them should be used. [Where problems could occur] * This will allocate slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1967889] Re: Raise CONFIG_NR_CPUS
** Description changed: + [Impact] + + * Currently our riscv64 kernels don't support more than 8 CPUs. + + * The QEMU 7.0 virt machine supports up to 32 harts (CPU threads). + + * Raising CONFIG_NR_CPUS to 32 allows us to use all of them. + + [Test Plan] + + * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 +virtual CPUs and see that only 8 of them are used. + + * After raising CONFIG_NR_CPUS to 32 all of them should be used. + + [Where problems could occur] + + * This will use slightly more RAM which might hurt very small +machines. + + [Other Info] + + * Original bug description: + The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. 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/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * Currently our riscv64 kernels don't support more than 8 CPUs. * The QEMU 7.0 virt machine supports up to 32 harts (CPU threads). * Raising CONFIG_NR_CPUS to 32 allows us to use all of them. [Test Plan] * Run riscv64 Ubuntu in a QEMU virt instance with more than 8 virtual CPUs and see that only 8 of them are used. * After raising CONFIG_NR_CPUS to 32 all of them should be used. [Where problems could occur] * This will use slightly more RAM which might hurt very small machines. [Other Info] * Original bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1967889] Re: Raise CONFIG_NR_CPUS
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- 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/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1986833] Re: PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- 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/1986833 Title: PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree Status in linux-riscv package in Ubuntu: New Bug description: [Impact] The 5.19 kernel contains support for the PolarFire Icicle board. But booting with linux-image-5.19.0-1002-generic_5.19.0-1002.2_riscv64.deb fails. The cause is that the device-tree incorrectly specifies the PLIC interrupts used for the drivers/soc/sifive/sifive_l2_cache.c. A patch is available as https://lore.kernel.org/all/20220817132521.3159388-1-heinrich.schucha...@canonical.com/ [PATCH 1/1] riscv: dts: microchip: correct L2 cache interrupts This patch only changes the device-tree of the PolarFire Icicle Kit. Please, add the patch to the 5.19 and future kernels. [Test Plan] Use the SiFive Unmatched preinstalled image and install the 5.19 kernel. Try to boot on the Polarfire Icicle board. [Where problems could occur] The fix only concerns a board which has been unsupported by Ubuntu yet. In case of an incorrect fix the board might not boot or otherwise malfunction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1986833/+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 1986970] Re: PolarFire Icicle Kit: missing USB support
** Changed in: linux-riscv (Ubuntu)
Assignee: (unassigned) => Emil Renner Berthing (esmil)
--
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/1986970
Title:
PolarFire Icicle Kit: missing USB support
Status in linux-riscv package in Ubuntu:
New
Bug description:
[Impact]
The 5.19 kernel contains support for the PolarFire Icicle board but
the USB driver is missing.
The following patches are available in Linux v6.0-rc1 and are
sufficient to make USB usable on the PolarFire Icicle board. Please,
apply them to the 5.19 kernel and set CONFIG_USB_MUSB_POLARFIRE_SOC=m.
7a96b6ea90a4 ("usb: musb: Add support for PolarFire SoC's musb controller")
https://lore.kernel.org/r/20220613114642.1615292-2-conor.doo...@microchip.com
21cdd6a0e844 ("usb: musb: mpfs: Fix error codes in probe()")
https://lore.kernel.org/r/YrVmLEc/FOEzNdzj@kili
98ceba755928 ("usb: musb: mpfs: add missing clk_disable_unprepare() in
mpfs_remove()"
https://lore.kernel.org/all/YrVmLEc%2FFOEzNdzj@kili/
With this change internal USB devices are fully usable. External
devices are supported with the following Jumper settings:
* J17 closed
* J15 open
[Test Plan]
Ensure the correct jumper settings:
* J17 closed
* J15 open
Use the SiFive Unmatched preinstalled image and install the 5.19
kernel. Try to boot on the Polarfire Icicle board.
* Run lsusb.
* Attach a USB device to J16 (USB port beside SD-card slot)
* Run lsusb again. The new device appears.
[Where problems could occur]
The fix only concerns a board which has been unsupported by Ubuntu
yet.
In case of an incorrect fix the board might not boot or otherwise
malfunction.
Best regards
Heinrich
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1986970/+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 1987513] Re: Use upstream LED description on Unmatched
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987513 Title: Use upstream LED description on Unmatched Status in linux package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987513/+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 1987513] [NEW] Use upstream LED description on Unmatched
Public bug reported: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - * The Ubuntu RISC-V kernel carries out-of-tree patches to enable -the two LEDs on the SiFive Unmatched board. + * The Ubuntu RISC-V kernel carries out-of-tree patches to enable + the two LEDs on the SiFive Unmatched board. - * There are now an upstream solution to enable the LEDs that appears -a little different from userspace. With the out-of-tree patches the -three colours in the RGB LED appears as 3 different LEDs, but upstream -models them as 1 RGB LED. + * There is now an upstream solution to enable the LEDs that appears + a little different from userspace. With the out-of-tree patches the + three colours in the RGB LED appears as 3 different LEDs, but upstream + models them as 1 RGB LED. - * Replacing the out-of-tree patches with the upstream solution will -make Ubuntu kernels behave like the upstream kernel going forward. - + * Replacing the out-of-tree patches with the upstream solution will + make Ubuntu kernels behave like the upstream kernel going forward. + [Test Plan] - * Boot Ubuntu on the Unmatched board and look at how the LEDs show up -in /sys/class/leds + * Boot Ubuntu on the Unmatched board and look at how the LEDs show up + in /sys/class/leds - * Check that both the green D12 and all three colours of D2 can still -be controlled from userspace. + * Check that both the green D12 and all three colours of D2 can still + be controlled from userspace. [Where problems could occur] - * Users may have scripts setting up LEDs that will no longer work when -updating to Kinetic with this change. + * Users may have scripts setting up LEDs that will no longer work when + updating to Kinetic with this change. -- 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/1987513 Title: Use upstream LED description on Unmatched Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987513/+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 1983019] [NEW] Pinctrl driver has a race condition bug
Public bug reported: [Impact] * The pinctrl-starfive driver has a race when initializing groups and functions that may result in other drivers not being able to initialize. * If this happens to the mmc driver the board will fail to boot. * This is an example of this happening: Loading device tree blob... [ 13.933777] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.941940] pinctrl-starfive 1191.pinctrl: invalid group sdio0-0.sdio-pins in map table [ 13.957656] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.965801] pinctrl-starfive 1191.pinctrl: could not map group config for "sdio0-0.sdio-pins" [ 13.974746] Unable to handle kernel NULL pointer dereference at virtual address [ 13.983581] Oops [#1] [ 13.985853] Modules linked in: phylink dw_mmc_pltfm clk_starfive_jh7100_audio reset_starfive_jh7100_audio(+) dw_mc [ 13.986227] starfive-drm soc:display-subsystem: bound 1200.crtc (ops starfive_crtc_component_ops) [ 13.996286] CPU: 1 PID: 8 Comm: kworker/u4:0 Not tainted 5.17.0-1004-starfive #5-Ubuntu [ 13.996297] Hardware name: StarFive VisionFive V1 (DT) [ 13.996305] Workqueue: events_unbound async_run_entry_fn [ 14.023868] epc : strcmp+0x12/0x36 [ 14.027274] ra : pinmux_func_name_to_selector+0x5a/0x76 [ 14.032583] epc : 80521224 ra : 805307d8 sp : ffd88006bb00 [ 14.039781] gp : 81e32e30 tp : ffd87ffd t0 : 0040 [ 14.046988] t1 : t2 : 81004ed4 s0 : ffd88006bb10 [ 14.054190] s1 : 0006 a0 : ffd9ff1d3cb8 a1 : [ 14.061392] a2 : a3 : a4 : ffd88c45ce00 [ 14.068594] a5 : 0073 a6 : ffd88c45cdb0 a7 : ffd88c45ce08 [ 14.075795] s2 : ffd897c53000 s3 : 0007 s4 : ffd9ff1d3cb8 [ 14.082996] s5 : 810776f0 s6 : s7 : ffd8801aa5c0 [ 14.090199] s8 : ffd890fdf780 s9 : fdfb s10: 81d80008 [ 14.097400] s11: t3 : 0002 t4 : 0402 [ 14.104600] t5 : ffd897c53040 t6 : ffd897c53048 [ 14.109896] status: 00020120 badaddr: cause: 000d [ 14.117986] ---[ end trace ]--- [Test Plan] * Unfortunately this is a race that happens rarely so rebooting the board several times is the only known way to reproduce. [Where problems could occur] * The fix could get the locking wrong and lock up the machine at boot. ** Affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Assignee: Emil Renner Berthing (esmil) Status: In Progress ** Changed in: linux-starfive-5.17 (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux-starfive-5.17 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1983019 Title: Pinctrl driver has a race condition bug Status in linux-starfive-5.17 package in Ubuntu: In Progress Bug description: [Impact] * The pinctrl-starfive driver has a race when initializing groups and functions that may result in other drivers not being able to initialize. * If this happens to the mmc driver the board will fail to boot. * This is an example of this happening: Loading device tree blob... [ 13.933777] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.941940] pinctrl-starfive 1191.pinctrl: invalid group sdio0-0.sdio-pins in map table [ 13.957656] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.965801] pinctrl-starfive 1191.pinctrl: could not map group config for "sdio0-0.sdio-pins" [ 13.974746] Unable to handle kernel NULL pointer dereference at virtual address [ 13.983581] Oops [#1] [ 13.985853] Modules linked in: phylink dw_mmc_pltfm clk_starfive_jh7100_audio reset_starfive_jh7100_audio(+) dw_mc [ 13.986227] starfive-drm soc:display-subsystem: bound 1200.crtc (ops starfive_crtc_component_ops) [ 13.996286] CPU: 1 PID: 8 Comm: kworker/u4:0 Not tainted 5.17.0-1004-starfive #5-Ubuntu [ 13.996297] Hardware name: StarFive VisionFive V1 (DT) [ 13.996305] Workqueue: events_unbound async_run_entry_fn [ 14.023868] epc : strcmp+0x12/0x36 [ 14.027274] ra : pinmux_func_name_to_selector+0x5a/0x76 [ 14.032583] epc : 80521224 ra : 805307d8 sp : ffd88006bb00 [ 14.039781] gp : 81e32e30 tp : ffd87ffd t0 : 0040 [ 14.046988] t1 : t2 : 81004ed4 s0 : ffd88006bb10 [ 14.054190] s1 : 0006 a0 : ffd9ff1d3
[Kernel-packages] [Bug 1980061] Re: RISC-V enables CONFIG_COMPAT in the unstable branch
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- 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/1980061 Title: RISC-V enables CONFIG_COMPAT in the unstable branch Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] * The 5.19 kernel adds RISC-V support for running 32bit binaries on 64bit systems, but only with hardware support. So far no chips have been released that support it and it's not even implemented in upstream Qemu. Also neither Ubuntu nor any other mainstream Linux distro ships 32bit binaries, so this enables a bunch of code that will most likely never be used. [Test Plan] * Setting CONFIG_COMPAT=n just disables a feature that was added in 5.19, so should have no impact on userspace compared to earlier kernels. [Where problems could occur] * This was implemented by T-Head (Alibaba) so will most likely be supported by one of their future designs. If it turns out to be useful on these cores we can always enable it later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980061/+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 1979647] Re: No RISC-V configuration in the unstable tree
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979647 Title: No RISC-V configuration in the unstable tree Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] * We would like to eventually build and test the unstable and generic kernels on the riscv64 architecture. Fixing this is a step towards that. * Having the riscv64 configuration alongside the other architectures should ensure it doesn't drift away from the generic configuration over time. * This allows us to do backports more easily. [Test Plan] * After merging riscv64 the generated configuration for other architectures should not change. * The generated riscv64 configuration should be as close as possible to the current linux-riscv configuration. Right now unstable is based on 5.19 while the riscv kernel is based on 5.18, so it can't be identical. [Where problems could occur] * Adding the riscv64 annotations may subtly change annotations from other architectures. * Adding the riscv64 configuration and annotations might confuse tooling scripts that are not prepared to handle the new architecture. [Other Info] * In the near future we'd also like to base the StarFive and Allwinner (Nezha) kernels on the same series that will become the generic kinetic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979647/+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 1981437] Re: RISC-V kernel config is out of sync with other archs
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- 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/1981437 Title: RISC-V kernel config is out of sync with other archs Status in linux package in Ubuntu: In Progress Bug description: [Impact] * Some drivers are available on other architectures but not on RISC-V. * Some things might work or look differently in RISC-V. Eg. RISC-V has an additional terminal font enabled. * The RISC-V kernel benefits less from testing done on other architectures. [Test Plan] * Install the kernel on RISC-V and see what modules and features are enabled. * After aligning the RISC-V kernel config there should be fewer differences to other architectures. [Where problems could occur] * Some options that are disabled on other architectures may be needed on RISC-V. * Some modules or features may be broken on RISC-V. [Other Info] * When RISC-V config and annotations were added to the generic kernel the config was copied from the linux-riscv tree without modifications. This revealed a lot of differences to the other architectures and many of them were not annotated, so presumably the configs had just drifted apart over time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981437/+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 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
** Also affects: linux-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-allwinner-5.17 (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux-allwinner-5.17 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: In Progress Status in linux-allwinner-5.17 package in Ubuntu: In Progress Status in linux-riscv package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: In Progress Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+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 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux-starfive-5.17 (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux-starfive-5.17 (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux-riscv (Ubuntu) Status: New => Invalid ** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: In Progress Status in linux-riscv package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: In Progress Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+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 1953613] Re: GPIO character device v1 API not enabled in kernel
** Summary changed: - GPIO character device API not enabled in kernel + GPIO character device v1 API not enabled in kernel -- 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/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1953613] Re: GPIO character device API not enabled in kernel
** Description changed: + [Impact] + + * The libgpiod2 library and gpiod tools shipped in Jammy don't work. + + * These tools are meant to replace the old sysfs interface and be +a better and more efficient way to manipulate GPIOs from userspace. +Unfortunately the latest release is still using v1 of the character +device kernel API which is not enabled in Ubuntu kernels. + + * This is Kent Gibsons reply on the linux-gpio mailing list: + + On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: + > Hi, + > + > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the + > libgpiod package that we ship is still based on the latest version + > 1.6.3 which does not implement the API v2. So I'd like to update + > libgpiod, do you have any recommendations about what branch/sha1 I + > should use? Do you plan to make a release that implements the API v2? + > + + Firstly, libgpiod is Bart's library so he is the authority, but this + is my understanding... + + TLDR: You should keep GPIO_CDEV_V1 enabled. + + v1 is deprecated from a development perspective, so all new feature + development will occur on v2, and new applications should target v2. + Existing apps targetting v1, be that directly or via libgpiod v1.6.3, + will require GPIO_CDEV_V1 until they migrate to v2. + The mainline kernel will continue to support v1 while userspace + transitions. + + libgpiod v2 is in active development, and should reach its first release + shortly. + Note that it is NOT a plugin replacement for v1. It has a different API, + for similar reasons to why we had to switch in the kernel, so apps will + need to be actively migrated. + + I wouldn't suggest making any effort to package libgpiod v2 until Bart + makes an official release. + + Cheers, + Kent. + + [Test Plan] + + * Run gpioinfo on a machine with exposed GPIOs and check that it lists +the GPIOs and doesn't error with + +gpioinfo: error creating line iterator: Invalid argument + + [Where problems could occur] + + * There may be code and scripts that hasn't been tested with a working +libgpiod2/gpiod tools and uncover latent bugs. + + [Other Info] + + Original bug text: + The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio
[Kernel-packages] [Bug 1981074] Re: Drivers with unsatisfied dependencies on the Allwinner D1
Tested with linux-image-5.17.0-1003-allwinner version 5.17.0-1003.3, and no more deferred devices: # uname -a Linux nezha 5.17.0-1003-allwinner #3-Ubuntu SMP Fri Jul 15 15:28:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux # cat /sys/kernel/debug/devices_deferred # ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981074 Title: Drivers with unsatisfied dependencies on the Allwinner D1 Status in linux-allwinner-5.17 package in Ubuntu: Fix Committed Status in linux-allwinner-5.17 source package in Jammy: Fix Committed Status in linux-allwinner-5.17 source package in Kinetic: Fix Committed Bug description: [Impact] * The drivers for the display engine, crypto acceleration and USB don't probe because of missing dependencies. [Test Plan] * Boot the kernel in linux-image-5.17.0-1002-allwinner and see /sys/kerne/debug/devices_deferred [Where problems could occur] * Fixing this may introduce now bugs if the now probing drivers turn out to be buggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981074/+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 1981437] [NEW] RISC-V kernel config is out of sync with other archs
Public bug reported: [Impact] * Some drivers are available on other architectures but not on RISC-V. * Some things might work or look differently in RISC-V. Eg. RISC-V has an additional terminal font enabled. * The RISC-V kernel benefits less from testing done on other architectures. [Test Plan] * Install the kernel on RISC-V and see what modules and features are enabled. * After aligning the RISC-V kernel config there should be fewer differences to other architectures. [Where problems could occur] * Some options that are disabled on other architectures may be needed on RISC-V. * Some modules or features may be broken on RISC-V. [Other Info] * When RISC-V config and annotations were added to the generic kernel the config was copied from the linux-riscv tree without modifications. This revealed a lot of differences to the other architectures and many of them were not annotated, so presumably the configs had just drifted apart over time. ** Affects: linux (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/1981437 Title: RISC-V kernel config is out of sync with other archs Status in linux package in Ubuntu: New Bug description: [Impact] * Some drivers are available on other architectures but not on RISC-V. * Some things might work or look differently in RISC-V. Eg. RISC-V has an additional terminal font enabled. * The RISC-V kernel benefits less from testing done on other architectures. [Test Plan] * Install the kernel on RISC-V and see what modules and features are enabled. * After aligning the RISC-V kernel config there should be fewer differences to other architectures. [Where problems could occur] * Some options that are disabled on other architectures may be needed on RISC-V. * Some modules or features may be broken on RISC-V. [Other Info] * When RISC-V config and annotations were added to the generic kernel the config was copied from the linux-riscv tree without modifications. This revealed a lot of differences to the other architectures and many of them were not annotated, so presumably the configs had just drifted apart over time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981437/+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 1981074] [NEW] Drivers with unsatisfied dependencies on the Allwinner D1
Public bug reported: [Impact] * The drivers for the display engine, crypto acceleration and USB don't probe because of missing dependencies. [Test Plan] * Boot the kernel in linux-image-5.17.0-1002-allwinner and see /sys/kerne/debug/devices_deferred [Where problems could occur] * Fixing this may introduce now bugs if the now probing drivers turn out to be buggy. ** Affects: linux (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/1981074 Title: Drivers with unsatisfied dependencies on the Allwinner D1 Status in linux package in Ubuntu: New Bug description: [Impact] * The drivers for the display engine, crypto acceleration and USB don't probe because of missing dependencies. [Test Plan] * Boot the kernel in linux-image-5.17.0-1002-allwinner and see /sys/kerne/debug/devices_deferred [Where problems could occur] * Fixing this may introduce now bugs if the now probing drivers turn out to be buggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981074/+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 1946231] Re: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)
Found it - https://github.com/Koenkk/zigbee2mqtt/issues/8663 ** Bug watch added: github.com/Koenkk/zigbee2mqtt/issues #8663 https://github.com/Koenkk/zigbee2mqtt/issues/8663 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946231 Title: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: the esp8266 development boards like wemos D1 mini have an integrated usb-uart converter which allows to flash/monitor/debug the esp8266 by usb cable and a tool called esptool on linux, which is either standalone (esptool package) or integrated into some IDE (platformio + visio) dmesg output: [ 46.614510] usbcore: registered new interface driver usbserial_generic [ 46.614523] usbserial: USB Serial support registered for generic [ 46.615912] usbcore: registered new interface driver ch341 [ 46.615925] usbserial: USB Serial support registered for ch341-uart [ 46.615938] ch341 1-9:1.0: ch341-uart converter detected [ 46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0 This convenient flashing method worked without issues up to kernel 5.11.0-36-generic and stopped working with 5.11.0-37-generic. The issue remains the same whether I use the esptool package or the version bundled with platformio, >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x firmware.bin esptool.py v2.8 Serial port /dev/ttyUSB0 Connecting_._._._._._._ A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header The communication to the esp8266 still seems to work, but the flash process includes some additional DTR/RTS magic in the beginning to switch the esp into flash mode before transmitting the data. My impression is that this DTR/RTS process might be broken. I can flash an esp with an external UART (some dongle) and manually triggering the flash mode. I tried with several cables, esps, ... Booting the older kernel (5.11.0-36-generic) solves the issue ... There seems to be an update to the ch341 from kernel -36 to -37, but it is beyond my knowledge whether there is any connection. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 14:59:58 2021 InstallationDate: Installed on 2020-08-29 (403 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946231/+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 1946231] Re: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)
Same issue under 5.4.0-89 kernel. Tested about 10 different boards, those ones based on ch340G does not work. Ones using ch340C or ch340K DOES work (mostly esp32 boards). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946231 Title: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: the esp8266 development boards like wemos D1 mini have an integrated usb-uart converter which allows to flash/monitor/debug the esp8266 by usb cable and a tool called esptool on linux, which is either standalone (esptool package) or integrated into some IDE (platformio + visio) dmesg output: [ 46.614510] usbcore: registered new interface driver usbserial_generic [ 46.614523] usbserial: USB Serial support registered for generic [ 46.615912] usbcore: registered new interface driver ch341 [ 46.615925] usbserial: USB Serial support registered for ch341-uart [ 46.615938] ch341 1-9:1.0: ch341-uart converter detected [ 46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0 This convenient flashing method worked without issues up to kernel 5.11.0-36-generic and stopped working with 5.11.0-37-generic. The issue remains the same whether I use the esptool package or the version bundled with platformio, >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x firmware.bin esptool.py v2.8 Serial port /dev/ttyUSB0 Connecting_._._._._._._ A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header The communication to the esp8266 still seems to work, but the flash process includes some additional DTR/RTS magic in the beginning to switch the esp into flash mode before transmitting the data. My impression is that this DTR/RTS process might be broken. I can flash an esp with an external UART (some dongle) and manually triggering the flash mode. I tried with several cables, esps, ... Booting the older kernel (5.11.0-36-generic) solves the issue ... There seems to be an update to the ch341 from kernel -36 to -37, but it is beyond my knowledge whether there is any connection. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 14:59:58 2021 InstallationDate: Installed on 2020-08-29 (403 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946231/+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 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system
We just installed a fresh X260 for a new coworker. Can confirm that kernel 4.8.0-040800rc5 works even without https://github.com/linuxenko/ubuntu-skylake-i915-video-fix We do still have problems with the Lenovo Pro and Ultra docks. We cannot get 4K@60Hz working using any videooutput on the dock. the *only* way is to plug the monitor into the mini DP on the X260. Though I think that this a failure of the dock rather than Ubuntu or the kernel. -- 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/1597267 Title: ThinkPad X260 connecting external DisplayPort hangs system Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD Graphics 520, connecting an external monitor to the DisplayPort connector causes the system to quickly hang. The system stops responding to network pings, cannot switch consoles, and needs a hard reboot. The external monitor does work when using a text console, and does not always hang in the LightDM login screen, but starting up a desktop session will always hang. This originally happened using a ThinkPad dock, and I tested it further using an external DP monitor. This happens on 4.4.0-28-generic as well as mainline 4.6.3-040603-generic and 4.7.0-040700rc5-generic; they all hang in a similar fashion. I have attached a journalctl log from running 4.7.0-040700rc5-generic and connecting the DP monitor while in a text console, before switching to the graphical console and logging in. The system hangs after a series of: kernel: WARNING: CPU: 3 PID: 2319 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3647 skl_update_other_pipe_wm+0x15d/0x170 [i915] kernel: WARNING: CPU: 3 PID: 4418 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:13957 skl_max_scale.part.108+0x69/0x70 [i915] kernel: [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun The first warnings come immediately when connecting, and others when switching consoles and logging in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: terom 1903 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 29 13:03:18 2016 InstallationDate: Installed on 2016-06-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20F6007RGE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=UUID=6636a3bb-262e-4ab2-ae81-d9388e3f7684 ro rootflags=subvol=@ quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET48W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6007RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6007RGE:pvrThinkPadX260:rvnLENOVO:rn20F6007RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20F6007RGE dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597267/+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 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system
Now I tried with the newest kernel 4.7.0-994-generic together with an Xorg.conf.d fix from https://github.com/linuxenko/ubuntu-skylake-i915-video-fix It now works almost flawlessly over DP 4K 60hz. -- 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/1597267 Title: ThinkPad X260 connecting external DisplayPort hangs system Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD Graphics 520, connecting an external monitor to the DisplayPort connector causes the system to quickly hang. The system stops responding to network pings, cannot switch consoles, and needs a hard reboot. The external monitor does work when using a text console, and does not always hang in the LightDM login screen, but starting up a desktop session will always hang. This originally happened using a ThinkPad dock, and I tested it further using an external DP monitor. This happens on 4.4.0-28-generic as well as mainline 4.6.3-040603-generic and 4.7.0-040700rc5-generic; they all hang in a similar fashion. I have attached a journalctl log from running 4.7.0-040700rc5-generic and connecting the DP monitor while in a text console, before switching to the graphical console and logging in. The system hangs after a series of: kernel: WARNING: CPU: 3 PID: 2319 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3647 skl_update_other_pipe_wm+0x15d/0x170 [i915] kernel: WARNING: CPU: 3 PID: 4418 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:13957 skl_max_scale.part.108+0x69/0x70 [i915] kernel: [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun The first warnings come immediately when connecting, and others when switching consoles and logging in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: terom 1903 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 29 13:03:18 2016 InstallationDate: Installed on 2016-06-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20F6007RGE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=UUID=6636a3bb-262e-4ab2-ae81-d9388e3f7684 ro rootflags=subvol=@ quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET48W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6007RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6007RGE:pvrThinkPadX260:rvnLENOVO:rn20F6007RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20F6007RGE dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597267/+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 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system
Hi first post here... Just wanted to chime in and confirm same bug on same machine: Thinkpad x260 Processor: Intel® Core™ i7-6500U CPU @ 2.50GHz × 4 Graphics: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) In order to try and fix the bug I have added the repo: http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu Before this change, the system reported Graphics: Intel Skylake HD Graphics 520 I'm running a 1 day old Ubuntu 16.04. I have experienced this crash on the stock kernel, 4.6.9 and 4.6.3 My steps to reproduce: * plug in HDMI to a 4K external display and set display to full resolution (this will only have a frame rate of 30Hz due to a limitation in HDMI standard) * turn off laptop monitor * plug in DP to *the same* external display * Set new configuration where HDMI if off and DP is on. (this will be at 60Hz) * screen goes blank on both HDMI and DP source. reverts to last configuration because of crash. I believe it is the combination of 4K display in full resolution *and* 60hz. This would be why the crash is only seen with DP at full resolution. last crash report with kernel 4.6.3: Jul 06 19:32:14 emil-workpad kernel: [ cut here ] Jul 06 19:32:14 emil-workpad kernel: WARNING: CPU: 0 PID: 986 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:13938 skl_max_scale.part.99+0x6d/0x80 [i915] Jul 06 19:32:14 emil-workpad kernel: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Jul 06 19:32:14 emil-workpad kernel: Modules linked in: Jul 06 19:32:14 emil-workpad kernel: rfcomm bnep arc4 snd_soc_skl snd_soc_skl_ipc snd_hda_codec_hdmi snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_hda_codec_realtek snd_hda_codec_generic snd_soc_sst_match intel_rapl snd_soc_core x86_pkg_temp_thermal snd_compress inte Jul 06 19:32:14 emil-workpad kernel: hid_lenovo usbhid hid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect e1000e sysimgblt psmouse f Jul 06 19:32:14 emil-workpad kernel: CPU: 0 PID: 986 Comm: Xorg Tainted: G W 4.6.3-040603-generic #201606241434 Jul 06 19:32:14 emil-workpad kernel: Hardware name: LENOVO 20F6006XMD/20F6006XMD, BIOS R02ET44W (1.17 ) 01/25/2016 Jul 06 19:32:14 emil-workpad kernel: 0286 eeed4400 8802148b7a50 813f3373 Jul 06 19:32:14 emil-workpad kernel: 8802148b7aa0 8802148b7a90 8108293b Jul 06 19:32:14 emil-workpad kernel: 3672c02dada0 8802183dba80 880035c4e800 8800b29cb000 Jul 06 19:32:14 emil-workpad kernel: Call Trace: Jul 06 19:32:14 emil-workpad kernel: [] dump_stack+0x63/0x90 Jul 06 19:32:14 emil-workpad kernel: [] __warn+0xcb/0xf0 Jul 06 19:32:14 emil-workpad kernel: [] warn_slowpath_fmt+0x5f/0x80 Jul 06 19:32:14 emil-workpad kernel: [] skl_max_scale.part.99+0x6d/0x80 [i915] Jul 06 19:32:14 emil-workpad kernel: [] intel_check_primary_plane+0xc0/0xe0 [i915] Jul 06 19:32:14 emil-workpad kernel: [] ? intel_ddi_compute_config+0x5a/0xc0 [i915] Jul 06 19:32:14 emil-workpad kernel: [] intel_plane_atomic_check+0x12e/0x1f0 [i915] Jul 06 19:32:14 emil-workpad kernel: [] drm_atomic_helper_check_planes+0x48/0x1d0 [drm_kms_helper] Jul 06 19:32:14 emil-workpad kernel: [] intel_atomic_check+0x172/0x830 [i915] Jul 06 19:32:14 emil-workpad kernel: [] drm_atomic_check_only+0x181/0x600 [drm] Jul 06 19:32:14 emil-workpad kernel: [] ? drm_atomic_set_crtc_for_connector+0x57/0xe0 [drm] Jul 06 19:32:14 emil-workpad kernel: [] drm_atomic_commit+0x17/0x60 [drm] Jul 06 19:32:14 emil-workpad kernel: [] drm_atomic_helper_set_config+0x7a/0xb0 [drm_kms_helper] Jul 06 19:32:14 emil-workpad kernel: [] drm_mode_set_config_internal+0x62/0x100 [drm] Jul 06 19:32:14 emil-workpad kernel: [] drm_mode_setcrtc+0x3e0/0x500 [drm] Jul 06 19:32:14 emil-workpad kernel: [] drm_ioctl+0x152/0x540 [drm] Jul 06 19:32:14 emil-workpad kernel: [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Jul 06 19:32:14 emil-workpad kernel: [] do_vfs_ioctl+0xa1/0x5b0 Jul 06 19:32:14 emil-workpad kernel: [] ? __set_task_blocked+0x41/0xa0 Jul 06 19:32:14 emil-workpad kernel: [] ? __set_current_blocked+0x36/0x60 Jul 06 19:32:14 emil-workpad kernel: [] SyS_ioctl+0x79/0x90 Jul 06 19:32:14 emil-workpad kernel: [] entry_SYSCALL_64_fastpath+0x1e/0xa8 Jul 06 19:32:14 emil-workpad kernel: ---[ end trace dce1bcd4b56b9a53 ]--- Jul 06 19:32:14 emil-workpad kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -- 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/1597267 Title: ThinkPad X260 connecting external DisplayPort hangs system Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD Graphics 520, connect
[Kernel-packages] [Bug 1331322] Re: Fan runs either too slow or too fast
After an upgrade through terminal, 1 month ago, this problem disappeared and now everything works great. Sorry for not marking this bug as solved earlier. Thank you ! Best regards, Emil Preda ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331322 Title: Fan runs either too slow or too fast Status in “linux” package in Ubuntu: Fix Released Bug description: I am using a laptop, HP Compaq 6910P and is running Ubuntu 14.04, 32 bit edition. When I start my laptop the fan is running optimally, my processor temperature remains at 60 C at idle. If I start using any intensive program, the temperature raises up to 90 C but the fan is running at the same speed. If I immediately restart the laptop, the fan starts spinning very fast and it doesn't slow down even at idle, when cpu temperature is just 45 C . This happens with the charger connected. If I shut down the laptop and let it cool down for an hour and start it again whithout the charger connected, the fan doesn't spin at all, and it doesn't starts spinning even if the cpu temp reaches 90 C and laptop shuts itself down. The radiator is clean and the thermal paste is new. Please any help ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331322/+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 1376120] Re: Touch-pad dosen't work after installing Ubuntu 14.04 [Dual boot with Windows 8]
I have the same problem but with my ASUS X550LN... -- 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/1376120 Title: Touch-pad dosen't work after installing Ubuntu 14.04 [Dual boot with Windows 8] Status in “linux” package in Ubuntu: Incomplete Bug description: Hi I just bought a new Acer Aspire V 15 Nitro computer with a pre-installed Windows 8. I installed Ubuntu so I can run dual-boot. Everything works fine now except my touch-pad that isn't working in Ubuntu but works fine when i boot into Windows. And when i'm in Ubuntu my USB mouse works fine aswell. cat /proc/bus/input/devices cat /proc/bus/input/devices This command does not show any SynPS/2 or anything. When i run xinput --list Under the Virtual core pointer there is only one Virtual core XTEST pointer Logitec USB-PS/2 Optical Mouse and then there is a empty slot where I think my touch-pad should be. In my system settings I can see the touch-pad and turn it on/off but nothing happens. I also installed Touch-pad indicator but nothing happens aswell. When I run cat /var/log/Xorg.0.log | grep -i synaptics [ 4.362] (**): Applying InputClass enable synaptics SHMConfig [ 4.362] (II) LoadModule: synaptics [ 4.362] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so [ 4.362] (II) Module synaptics: vendor=X.Org Foundation [ 4.362] (II) Using input driver 'synaptics' for ' ' [ 4.388] (--) synaptics:: x-axis range 0 - 1236 (res 12) [ 4.388] (--) synaptics:: y-axis range 0 - 898 (res 12) [ 4.388] (II) synaptics:: device does not report pressure, will use touch data. [ 4.388] (II) synaptics:: device does not report finger width. [ 4.388] (--) synaptics:: buttons: left double triple [ 4.388] (--) synaptics:: Vendor 0x6cb Product 0x2970 [ 4.388] (--) synaptics:: invalid pressure range. defaulting to 0 - 255 [ 4.388] (--) synaptics:: invalid finger width range. defaulting to 0 - 15 [ 4.388] (--) synaptics:: touchpad found [ 4.404] (**) synaptics:: (accel) MinSpeed is now constant deceleration 2.5 [ 4.404] (**) synaptics:: (accel) MaxSpeed is now 1.75 [ 4.404] (**) synaptics:: (accel) AccelFactor is now 0.131 [ 4.404] (--) synaptics:: touchpad found After running grep -i touchpad /var/log/Xorg.0.log the output is [ 4.362] (**): Applying InputClass evdev touchpad catchall [ 4.362] (**): Applying InputClass touchpad catchall [ 4.388] (--) synaptics:: touchpad found [ 4.404] (II) XINPUT: Adding extended input device (type: TOUCHPAD, id 12) [ 4.404] (--) synaptics:: touchpad found [ 4.404] (**): Ignoring device from InputClass touchpad ignore duplicates but when i run xinput -list there is nothing with id 12 ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB-PS/2 Optical Mouse id=11 [slave pointer (2)] ⎜ ↳ id=12 [slave pointer (2)] I'm running Ubuntu 14.04.1 LTS, Release: 14.04 From cat /proc/version_signature version.log: Ubuntu 3.13.0-36.63-generic 3.13.11.6 --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eric 2183 F pulseaudio /dev/snd/controlC0: eric 2183 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire VN7-591G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=b973e8ad-55d3-4d12-a642-9cbec54417db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-591G
[Kernel-packages] [Bug 1304035] [NEW] [ASUSTeK COMPUTER INC. T300LA] suspend/resume failure
Public bug reported: it happends when I start the computer after update ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hakon 2791 F pulseaudio /dev/snd/controlC1: hakon 2791 F pulseaudio Date: Mon Apr 7 03:09:17 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2f3129f8-1cf2-4b0b-a5c4-66a59d8966cf InstallationDate: Installed on 2014-04-06 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK COMPUTER INC. T300LA ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic.efi.signed root=UUID=5c15ce47-1698-4c9e-9773-0d9865fdf3ac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux StagingDrivers: keucr Title: [ASUSTeK COMPUTER INC. T300LA] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300LA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300LA.205:bd10/08/2013:svnASUSTeKCOMPUTERINC.:pnT300LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume staging suspend trusty -- 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/1304035 Title: [ASUSTeK COMPUTER INC. T300LA] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: it happends when I start the computer after update ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hakon 2791 F pulseaudio /dev/snd/controlC1: hakon 2791 F pulseaudio Date: Mon Apr 7 03:09:17 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2f3129f8-1cf2-4b0b-a5c4-66a59d8966cf InstallationDate: Installed on 2014-04-06 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK COMPUTER INC. T300LA ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic.efi.signed root=UUID=5c15ce47-1698-4c9e-9773-0d9865fdf3ac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux StagingDrivers: keucr Title: [ASUSTeK COMPUTER INC. T300LA] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300LA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER
[Kernel-packages] [Bug 1268365] Re: [Lenovo Thinkpad t440s] Touchpad periodically stops working
Are you sure it's not a hardware issue? This discussion seems to indicate it's a hardware problem http://www.spinics.net/lists/linux-input/msg28623.html . Only Windows 8 is for some strange reason not affected. I do have the same problem with Arch Linux and Windows 7. -- 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/1268365 Title: [Lenovo Thinkpad t440s] Touchpad periodically stops working Status in “linux” package in Ubuntu: Triaged Bug description: Every 15 minutes or so, the cursor stops reacting to input from the touchpad or trackpoint. Unfortunately this machine has a clickpad instead of separate buttons and so it is impossible to use the machine without the touchpad, which means that Ubuntu is virtually unusable. In Windows on the same machine there is no problem. In syslog you see: Jan 12 19:08:43 mv8 kernel: [ 8460.304134] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Jan 12 19:08:43 mv8 kernel: [ 8460.305321] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Jan 12 19:08:43 mv8 kernel: [ 8460.306606] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Jan 12 19:08:43 mv8 kernel: [ 8460.307792] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Jan 12 19:08:43 mv8 kernel: [ 8460.309002] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 WORKAROUND: sudo rmmod psmouse sudo modprobe psmouse ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jon2119 F pulseaudio /dev/snd/controlC0: jon2119 F pulseaudio Date: Sun Jan 12 19:42:27 2014 HibernationDevice: RESUME=UUID=b5d52deb-2d98-4e2e-bdd1-c34a0bd2d9f6 InstallationDate: Installed on 2013-12-04 (38 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20AQCTO1WW MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=c0877b82-2224-438f-be5b-11b343943067 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET64WW (2.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET64WW(2.14):bd11/12/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268365/+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 1210331] [NEW] package linux-image-3.11.0-0-generic 3.11.0-0.2 failed to install/upgrade: trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', w
Public bug reported: it happends when i rebooted after system update. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-0-generic 3.11.0-0.2 ProcVersionSignature: Ubuntu 3.11.0-0.2-generic 3.11.0-rc4 Uname: Linux 3.11.0-0-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hakon 2743 F pulseaudio /dev/snd/controlC0: hakon 2743 F pulseaudio Date: Fri Aug 9 01:24:19 2013 DuplicateSignature: package:linux-image-3.11.0-0-generic:3.11.0-0.2:trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', which is also in package linux-image-extra-3.11.0-0-generic 3.11.0-0.2 ErrorMessage: trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', which is also in package linux-image-extra-3.11.0-0-generic 3.11.0-0.2 HibernationDevice: RESUME=UUID=f8fa6196-3c45-4a77-bad2-ab26487aa440 InstallationDate: Installed on 2013-08-06 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130805) MachineType: Hewlett-Packard 520-1210eo MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-0-generic root=UUID=bd344e1c-10fc-4fc1-921b-e1e8e6fa6a3c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: grub-pc 2.00-15ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.11.0-0-generic 3.11.0-0.2 failed to install/upgrade: trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', which is also in package linux-image-extra-3.11.0-0-generic 3.11.0-0.2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2012 dmi.bios.vendor: AMI dmi.bios.version: 7.12 dmi.board.asset.tag: CZC225912Q dmi.board.name: 2AC3 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.04 dmi.chassis.asset.tag: CZC225912Q dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.12:bd03/29/2012:svnHewlett-Packard:pn520-1210eo:pvr1.04:rvnPEGATRONCORPORATION:rn2AC3:rvr1.04:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 520-1210eo dmi.product.version: 1.04 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package package-conflict saucy -- 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/1210331 Title: package linux-image-3.11.0-0-generic 3.11.0-0.2 failed to install/upgrade: trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', which is also in package linux-image-extra-3.11.0-0-generic 3.11.0-0.2 Status in “linux” package in Ubuntu: Confirmed Bug description: it happends when i rebooted after system update. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-0-generic 3.11.0-0.2 ProcVersionSignature: Ubuntu 3.11.0-0.2-generic 3.11.0-rc4 Uname: Linux 3.11.0-0-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hakon 2743 F pulseaudio /dev/snd/controlC0: hakon 2743 F pulseaudio Date: Fri Aug 9 01:24:19 2013 DuplicateSignature: package:linux-image-3.11.0-0-generic:3.11.0-0.2:trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', which is also in package linux-image-extra-3.11.0-0-generic 3.11.0-0.2 ErrorMessage: trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', which is also in package linux-image-extra-3.11.0-0-generic 3.11.0-0.2 HibernationDevice: RESUME=UUID=f8fa6196-3c45-4a77-bad2-ab26487aa440 InstallationDate: Installed on 2013-08-06 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130805) MachineType: Hewlett-Packard 520-1210eo MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-0-generic root=UUID=bd344e1c-10fc-4fc1-921b-e1e8e6fa6a3c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: grub-pc 2.00-15ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.11.0-0-generic 3.11.0-0.2 failed to install/upgrade: trying to overwrite '/lib/modules/3.11.0-0-generic/kernel/arch/x86/kvm/kvm-intel.ko', which is also in package linux-image-extra-3.11.0-0-generic 3.11.0-0.2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2012 dmi.bios.vendor: AMI dmi.bios.version: 7.12
