teresaejunior, could you try that:
"Can you try 4.20-rc2 and boot with kernel parameter `pcie_aspm=off`?"
I suggest first trying 4.20-rcX and seeing if it freezes at least once.
If it does, try booting for a few days with pcie_aspm=off in the kernel
parameters. Post back results.
I can't do
** Attachment added: "output of journalctl -b -1 -k"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+attachment/5212302/+files/journal2.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It happened again.
See the attachment of the output of journalctl -b -1 -k
This time I was just editing the position of widgets on the xfce4-panel.
I think it was around 11:45 on the clock.
And I do not have a .cache/thumbnails/fail folder.
** Also affects: linux (Arch Linux)
Importance:
I have updated to A16 and so far no freezes, although it's still not
uncommon for these to stop happening for a while and then return.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The problem is, it could take days before the system freezes. I don't
know how to reproduce, it simply happens. I don't even know where to
start. Maybe 4.17-rc1 and so on. But that's a huge task and one needs a
lot of patience to do it. I'm not sure I'll be able to.
--
You received this bug
** Description changed:
First thing I notice is that the mouse cursor freezes as I'm using it,
then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then
I try the "REISUB" command, but it doesn't do anything either. Only a
hard reset works, pressing down the power button
Affects the latest mainline build 4.19-rc8 as well.
Still cannot identify one way to reproduce it intentionally, although
most of the time it happens when I have a video playing and/or multiple
images being displayed with the image viewer.
** Changed in: linux (Ubuntu)
Status: Incomplete
I am failing to boot from this new kernel. Downloaded the amd64 build
files, 'sudo dpkg -i ' on each of them, but upon trying to boot
from the new entries, it stops with "you need to load the kernel first".
I really need some help figuring out my mistake here. I did my homework
but no solutions
This is the bug report opened for Arch Linux [TASK FS#59483]:
https://bugs.archlinux.org/task/59483?string=freeze=1%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=open%5B0%5D
The OP reports 4.17.10-1 being the problematic kernel version. What I
can say for sure is that this
Public bug reported:
First thing I notice is that the mouse cursor freezes as I'm using it,
then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then
I try the "REISUB" command, but it doesn't do anything either. Only a
hard reset works, pressing down the power button for a few
Tested kernel 4.13.4-200.fc26.x86_64, and is still reproducible. Arch is
free from this bug, but Fedora and Debian are not.
** Tags removed: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tested kernel 4.13 in Arch Linux. Cannot reproduce the bug with it.
Fedora is in 4.12.14-300.fc26 and is still reproducible there.
** 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.
Sorry, can you tell me how to install the 4.13 kernel in Debian? It's
useless to do it in Ubuntu. As I said, Ubuntu is not affected. I might
have reported in the wrong place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Fedora's kernel version: 4.12.13-300.fc26.x86_64
Debian's kernel version: 4.9.0-3-amd64
Both are affected. Ubuntu LTS is not, though. I don't remember 17.04.
I can install the mainline 4.13 kernel for Fedora. If Ubuntu is really
needed, I don't mind installing it here.
--
You received this bug
Public bug reported:
Symptoms:
The computer begins its boot process, then the root decryption password
prompt appears (via Plymouth) and I start typing. The first letters are
caught, but some letters are not captured. It's as if the keyboard shut
down during a few seconds and then returned, and
I fixed it with `sudo systemctl enable bluetooth` followed by a reboot.
It will print something to the terminal when you enable. Something else
must have disabled bluetooth.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
16 matches
Mail list logo
