There is still corruption when coming out of suspend. It doesn't affect
anything other than the desktop background though.
--
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/1711936
Title:
This bug appears to be fixed in the released version of Ubuntu 17.10.
Haven't seen any corruption yet, although I've only had Ubuntu installed
for a few minutes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Well, now that I say that, I tried again after a reboot and sddm loaded
a corrupt session, same as gdm3. I'll remove gdm3 as affected.
** No longer affects: gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've added gdm3 as affected. The fact that sddm launches a working
Wayland gnome-shell is a good sign that this is a GDM bug.
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is
Additionally, if gnome-shell on Wayland is started from sddm instead of
gdm, it loads correctly.
--
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/1711936
Title:
Severe graphical
This seems to be specific to gnome-shell, not to Wayland in general.
This bug does not occur in Weston, the reference Wayland compositor.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Proprietary driver (as well as simply disabling Wayland and using X with
Nouveau) fixes this issue. Perhaps for now Wayland should be blacklisted
for this card (and other cards that have this same issue).
--
You received this bug notification because you are a member of Kernel
Packages, which is
On Fedora 26, this same issue occurs when the screen is locked (although
it doesn't prevent unlocking the screen), but it doesn't affect the
desktop on Fedora.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I just tested on two more machines, one of which has a GTX 970 and the
other of which has a GTX 1050 TI. The machine with the GTX 970 boots and
displays the desktop correctly, and I confirmed it's running under
Wayland. The machine with the 1050 TI fails to boot at all.
--
You received this bug
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1711936/+attachment/4935941/+files/JournalErrors.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/1711936/+attachment/4935942/+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
** Tags added: apport-collected artful wayland-session
** Description changed:
- When running gnome-shell on Ubuntu 17.10, text is visible only as white
- blocks (or sometimes not visible at all), and some graphics, such as the
- icons on the launcher menu, are corrupt. Only
I've replaced Ubuntu with Fedora on this machine for now. I'll reinstall
Ubuntu to an external drive and run the command when it finishes
installing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is on a Dell XPS M1330 laptop with Nvidia GeForce 8400M GS, 8 GB
RAM, and 2.6 GHz Core 2 Duo T9500. I'm adding the kernel package to this
bug report as it could be a kernel issue. This happens only on Wayland.
This issue, however, is not present under Fedora 25 or 26 when running
Wayland.
**
If the motherboard allows it, disabling the OpCache will completely
prevent (or at least greatly reduce the probability of) the ASLR-related
crash, even if ASLR is enabled in the kernel. As far as I'm aware it has
no effect on the other type of crash.
--
You received this bug notification
I've also determined that changing the CPU, memory, or SOC voltages or
timings has little or no effect on either type of crash.
--
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/1690085
This is the DragonFlyBSD commit.
https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/b48dd28447fc8ef62fbc963accd301557fd9ac20
It appears that there are two different ways that the system can crash,
which is why it is necessary to both disable ASLR and to compile the
kernel with
If any of your RAM timings are odd (eg. 17), setting them to the next
even number (eg. 18) helps a lot. Recompiling the kernel with
CONFIG_RCU_NOCB_CPU and CONFIG_RCU_NOCB_CPU_ALL, and disabling ASLR is
still necessary though. It may also be a good idea to give the SOC
slightly more voltage, but
I just tested 1.0.0.6a AGESA, and it does not solve this issue. In some
cases just one program will crash, and in other cases the entire system
will crash. I will test the workaround above later.
--
You received this bug notification because you are a member of Kernel
Packages, which is
AMD has not publicly commented on this issue that I'm aware of. This
issue has been seen on many different operating systems. DragonFlyBSD
includes a workaround for this issue. The workaround on Linux is to
compile the kernel with CONFIG_RCU_NOCB_CPU, CONFIG_RCU_NOCB_CPU_ALL,
and disable ASLR
Reopening because even though this is a known issue with the CPU we
could still implement a workaround. One workaround is to disable address
space layout randomization:
echo 0 >/proc/sys/kernel/randomize_va_space
However, that would be disabling a security feature.
** Changed in: linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
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/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on
This is a hardware bug in the CPU. This ticket should be closed as
invalid.
--
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/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls
I'm seeing this crash even with the Nvidia official driver.
--
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/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
24 matches
Mail list logo
