any ETA for adding the fix to linux-hwe-22.04 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2036184
Title:
Infinite systemd loop when power off the machine with multiple MD
Having this issue on razer blade 17 pro (2021) on Ubuntu 22.10. Don't
see anything relevant in logs. It works fine most of the time but every
so often has heavy flickering for a few seconds or minutes.
--
You received this bug notification because you are a member of Kernel
Packages, which is
*** This bug is a duplicate of bug 1941044 ***
https://bugs.launchpad.net/bugs/1941044
I had the same issue at https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1948685 and fixed it by putting the PNVM file back, now
the firmware is working fine on version 63
--
You received
Oh I needed to put the PNVM file back to get it to work on the latest
firmware, that was my mistake. Will close this.
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Renaming the 63 and 62 files so the module can't find them and is forced
to load the 59 firmware works.
dmesg:
[ 216.772000] iwlwifi :5a:00.0: Direct firmware load for
iwlwifi-ty-a0-gf-a0-63.ucode failed with error -2
[ 216.772018] iwlwifi :5a:00.0: Direct firmware load for
Public bug reported:
It works fine on 5.11 kernel, firmware version 59. I did need to rename
the pnvm file as mentioned in other bugs but once I did that it loads.
After upgrading to 21.10 I needed to rename that file again and then it
still works on 5.11 kernel. However, on the 5.13 kernel it
FYI, I fixed this by enabling the Intel VMD thing in bios. Still a
regression though and should be fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948611
Title:
Second NVME drive
https://www.reddit.com/r/linuxhardware/comments/pyey6m/newer_kernels_do_not_detect_any_hard_drives_on/
someone else with the same issue on different hardware
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535715/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535714/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535709/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535716/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535718/+files/WifiSyslog.txt
** Description changed:
On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
the 2nd one. It works fine on 5.11 kernel, but when I
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535719/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535712/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535717/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535701/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535710/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535711/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535713/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535703/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535704/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535705/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948611
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535708/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535702/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948611
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535706/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1948611/+attachment/5535707/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948611
Public bug reported:
On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
the 2nd one. It works fine on 5.11 kernel, but when I upgraded to 21.10
it doesn't boot on 5.13 kernel. If I manually select 5.11 in grub it
boots fine.
Running blkid in initramfs only finds the first
Yes, had the same issue on 418.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1828131
Title:
Qemu causes system hang
Status in nvidia-graphics-drivers-418
Having same issue, freeze without any changes on screen, on Ubuntu
18.10, Dell Precision 5530.
It only started recently after I encrypted my home directory and swap
but I don't know if that's related.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Package changed: linux-lts-vivid (Ubuntu) => linux-lts-trusty
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1500954
Title:
xfs DIO data corruption
Status in
Any progress on this issue? This is DATA CORRUPTION!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1500954
Title:
xfs DIO data corruption
Status in linux-lts-vivid package
Public bug reported:
An appending DIO write will corrupt files on XFS.
The following patch needs to be backported:
commit b9d59846f73713d77f0f3fb784c7f84249fc2b93
Author: Dave Chinner
Date: Thu Apr 16 22:03:07 2015 +1000
xfs: DIO write completion size updates race
It also hung for me.
The supplied realtek driver wouldn't build, either.
https://github.com/pvaret/rtl8192cu-fixes is a ported fix of the
realtek's supplied driver.
https://code.google.com/p/realtek-8188cus-wireless-
drivers-3444749-ubuntu-1304/ seems to be a deb of that.
--
You received this
.
WORKAROUND: Use 12.04.2 with nvidia drivers.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0
Yes -- on a clean 12.04 with minimal additions, suspend worked just
fine:
It's running the nvidia screen driver, not neuvoeu.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.2 LTS
Release:12.04
Codename: precise
avi@avi-i7
resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate
didn't seem to be configurable.
I am using nouveu but setting the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi
resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F pulseaudio
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
I can do the resume-trace here if needed:
https://wiki.ubuntu.com/DebuggingKernelSuspend
I couldn't find exactly my bug elsewhere... maybe you could just point me to
bug report if it's duplicate.
Version: Ubuntu 3.13.0-24.46-generic 3.13.9
Wakeup:
Device S-state Status Sysfs node
UAR1
Public bug reported:
I have a fresh install of 14.04:
Description:Ubuntu 14.04 LTS
Release:14.04
When I try a suspend, when it comes back it looks fine. But rather soon X
crashes.
Sometimes ctrl-ALT F1 doesn't even work. Other times it does, I try killing X
or lightdm but I'm not
Also: I was using this hardware with Linux Mint 13 and the nvidia driver
and resume/suspend was fine. So this is a new configuration issue or
bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm sorry --- wakeup is from: cat /proc/acpi/wakeup (I couldn't find
an edit button)
And I also uploaded the wrong xlog -- that's the working one, now
attached is the .old
** Attachment added: Xorg.0.log.old
the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi
screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F
but setting the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0
the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi
but setting the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi
the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi
screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F
screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F
the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi
the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi
screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550 F
the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi
: avi2550 F pulseaudio
+ /dev/snd/controlC1: avi2550 F pulseaudio
+ /dev/snd/controlC0: avi2550 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2014-04-25 (10 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS
drivers didn't seem to be configurable.
I am using nouveu but setting the 2nd screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1
screen's resolution manually.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: avi2550 F pulseaudio
/dev/snd/controlC1: avi2550 F pulseaudio
/dev/snd/controlC0: avi2550
60 matches
Mail list logo