Thanks, that worked:
https://errors.ubuntu.com/oops/93823806-9ff7-11ea-9bb3-fa163e102db1
but I can't see any interesting functions blocking in any of the
threads.
Let's skip that and just make this about the nouveau kernel crash.
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
Daniel thank you so much for being so supportive, I really appreciate it
:)
I have ran the command `ubuntu-bug /var/crash/_usr_bin_gnome-
shell.1000.crash` which then opens a dialog; however when I press "Send"
there's no follow-up - no browser tab opens. The contents of
If we're unable to solve this quickly then consider opening the
'Additional Drivers' app and installing the proprietary Nvidia driver...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166
Title:
Thanks. Yes if the nouveau kernel driver is crashing then it's quite
possible the gnome-shell process will be frozen. Still, it would be
interesting to know where in gnome-shell this happens. And to confirm
they're the same issue or two coincidental ones.
--
You received this bug notification
Thank you kindly. I was able to ssh into the machine and prepare a crash
report from the gnome-shell process, I will upload that shortly, perhaps
as a separate bug report. However, the real culprit might be located in
the dmesg:
```
[12870.773176] nouveau :01:00.0: fifo: SCHED_ERROR 0a
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+attachment/5377303/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166
Title:
If you can ssh in when the freeze happens then please look for the
gnome-shell processes. Find the one running as yourself and then:
kill -ABRT
That should generate a crash file in /var/crash which you can then
report for formal analysis using the 'ubuntu-bug' command.
--
You received this
It was a different time, so maybe they're unrelated as you say.
Because the sound continues to play, I suspect that it's just the
graphics stack that freezes. To verify this assumption I've installed
openssh-server on the laptop; if the freeze occurs again, I'll ssh into
the machine and I may be
If those kernel messages happen at the same time as this bug then we
would move this to a kernel bug. If they happen at different times then
they're not related to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you so much. I was not yet able to investigate the crash (it
usually happens during a video call and then I quickly need to reboot,
to continue chatting with the customer - no time to diagnose :-D )
However, today I found out something in the log that might be connected
(even though in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
I can't see any kind of kernel crash that I was expecting.
But it does appear one of your USB controllers is overwhelmed, which may
cause the mouse and keyboard to fail:
touko 12 07:47:46 mavi-vaadin kernel: usb 1-4.2.4: Not enough bandwidth for new
device state.
touko 12 07:47:46 mavi-vaadin
Thank you, I was exactly hoping for a guidance on how to debug this
issue further.
The crash happened today 10:55:00; please find the output of journalctl
-b-1 attached.
** Attachment added: "prevboot.txt"
After a freeze and rebooting, please run:
journalctl -b-1 > prevboot.txt
then attach the resulting text file here.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
14 matches
Mail list logo
