Getting this with 5.13 on 21.10 with a Radeon RX 6800 XT with a AMD
Ryzen 5 3600.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1919508
Title:
AMDGPU lockup on every
Is that kernel in main now? After adding proposed just now it doesn't
seem to have any kernel packages.
I just installed linux-image-4.15.0-13-generic from main (4.15.0-13.14)
however and rebooted with that and it seems to be working fine now.
Cheers!
--
You received this bug notification
Running 4.16.0-041600rc4-generic right now, works fine.
** Tags added: kernel-fixed-upstream
--
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/1755378
Title:
Plymouth, Wayland not working
Public bug reported:
I just upgraded to bionic from artful and the kernel's graphics stack
seems to be hosed. I can get text consoles, but neither plymouth nor
Wayland GDM sessions work.
X11 sessions do work however, e.g. by disabling Wayland for GDM3 in
custom.conf or running startx from the
Similarly to Bug #1389077, I can disable Intel Powerclamp by `rmmod
intel_powerclamp` to prevent kidle_inject from being used, and in this
case applesmc (presumably) will start the fan kicking in as the system
gets hotter.
However unlike Bug #1389077, when intel_powerclamp is loaded here the
fan
Public bug reported:
At least since upgrading to Yakkey, my MacBookPro12,1 (13", 2015) seems
to respond to increased system heat using only kidle_inject, and not the
built-in fan. kidle_inject with kick in rather quickly, especially with
the Australian summer starting to be felt, and will render
No change with it regardless:
> $ uname -a
> Linux payens 4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC
> 2016 x86_64 x86_64 x86_64 GNU/Linux
Full dmesg is attached. Note this ~4s pause:
> [2.809149] clocksource: Switched to clocksource tsc
> [6.505235] xhci_hcd
Still happens with: 4.4.0-040400rc8-generic from the mainline PPA (there
is a non RC 4.4 there, but it's older than RC8 so I used that instead).
These errors are reported now:
> [ 11.924171] usb 2-3: device not accepting address 2, error -62
> [ 16.832609] usb 1-3: device descriptor read/64,
It hasn't worked on the MBP 12,1 on any of the 4.x kernels, and I'm
pretty sure it didn't work on 3.x either.
The same adaptor was working with an older (pre-Thunderbolt) MBP, but
not this model.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
The Apple VGA thunderbolt/displayport adaptor seems to be non-functional
on my MacbookPro 12,1. After plugging it in with a projector attached,
the projector does not show up in the display control panel and xrandr
reports DP1, DP2, HDMI1, HDMI2 and VIRTUAL1 displays all
Also, the adaptor remains non-functional if booted with it plugged in,
in addition to attempting to hot-plug it.
--
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/1520069
Title:
MacbookPro
Hmm, no it hasn't. I think there is either a controller or device
initialisation problem, and it might be a race. On power-on, one of two
different things will happen after the Mac startup chime:
1. Usually, there will be along pause (30sec? 1min?), some random display
corruption, then boot
Quick update, after installing 4.4-rc2 from the mainline kernel PPA, the
problem has gone away again. Will report back after some use if that
seems to be persisting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
I'm not sure what you mean - it's the firmware hasn't changed, it's the
same version that appeared to have fixed the problem in the first place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
I'm re-opening this because I am intermittently seeing the same
behaviour per the description again. Likewise, disabling the XHCI in
/proc/acpi/wakeup remains a usable workaround.
This is using linux-generic 4.2.0.16.18 and linux-firmware 1.149.
** Also affects: linux (Ubuntu)
Importance:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502726/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502720/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502729/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: mjg1409 F pulseaudio
/dev/snd/controlC0: mjg1409 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 15.10
HibernationDevice:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502731/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502730/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502727/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502732/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502724/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502723/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502728/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502722/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502725/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1448566
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1448566/+attachment/4502721/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1448566
Patch fixing this was just applied to the bluetooth-next kernel repo:
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-
next.git/commit/?id=2af82d55442672e1429e36439a89e17896c2fb66
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
On my MacbookPro12,1 with Wily and Linux 4.2, by default the kernel
successfully suspends but then immediately resumes again. The problem
seems to be the XHCI controller causing spurious ACPI wakeups. After
disabling it using the following command:
> # echo XHC1 >
@penalvch: As requested, I just reported bug #1507472 then.
--
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/1487919
Title:
macbookrpro12,1 fails to suspend
Status in linux package in
I just tried reproducing this with the most recent from the link above
(v4.3-rc6-unstable) and couldn't, then went back to the current wily
kernel (4.2.0-16-generic) and still can't reproduce it.
So now I am wondering if the updated firmware for the BCM43602 wifi card
in linux-firmware 1.149
Just to confirm, using kernel 4.2.0-16-generic, downgrading linux-
firmware to 1.148 caused the problem to reappear then upgrading it back
to 1.149 caused the problem to go away again.
So it seems this issue was caused by the Broadcom's firmware, rather
than the kernel.
--
You received this bug
On my MacbookPro12,1 with Wily and Linux 4.2, by default the kernel
successfully suspends but then immediately resumes again. The problem
seems to be the XHCI controller causing spurious ACPI wakeups. After
disabling it using the following command:
> # echo XHC1 > /proc/acpi/wakeup
The kernel
35 matches
Mail list logo
