The issue appears to be fixed in Mainline Kernel 5.6.6.
So far, I have not done further research, when this fix was implemented
excatly. If needed, I can do further mainline or -rc tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I also tried 5.3.0-29 by downloading the eoan packages:
5.3.0-29-generic #31-Ubuntu SMP Fri Jan 17 17:27:26 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux
** Attachment added: "full output of journal for 5.3.0-29-generic #31-Ubuntu"
latest kernel in proposed for bionic I could find: 5.3.0-28-generic
#30~18.04.1-Ubuntu
bug still present.
** Attachment added: "full output of journal for 5.3.0-28-generic
#30~18.04.1-Ubuntu"
Sorry I was out of office until today. Please find the logs attached.
bug still present in 5.5.0-050500-generic #202001262030
** Attachment added: "full output of journal for 5.5.0-050500-generic
#202001262030"
bug not present in 18.04 original kernel tree 4.15.0-74
** Attachment added: "full output of journal for 4.15.0-74"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+attachment/5321671/+files/megasas_4.15.0-74.txt
--
You received this bug notification because you are
bug also present in 5.5.0-050500rc7-generic #202001192030
** Attachment added: "megasas_rc.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+attachment/5321668/+files/megasas_rc.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
It appears that in recent Kernel versions the megaraid_sas cannot
properly handle suspend to RAM (rtcwake -m mem -s 30).
After the system wakes up, the megaraid_sas driver reports multiple
errors and I/O to disks fails completely. A reset is required to make
the machine work
Hi
even though I'm late to the party, I could offer to test the modified
kernel with H330, H710 and H730.
If you send me all the necessary things and provide a list of what
things to look out for, then I could test these.
--
You received this bug notification because you are a member of Ubuntu
http://marc.info/?l=linux-fbdev=150157026614752=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707641
Title:
Sunix 2D VGA controller causes kernel panic and crash on boot
To manage notifications
I have sent a message to the mailing list.
You are correct. When blacklisting the module everything is working fine
again.
Can you maybe also tell me how do I properly link this bug report to the
mailing list?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
I have attached the dmesg log from the booted Fedora and the Kernel
config as requested:
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4925000/+files/dmesg.txt
--
You received this bug notification because you are a member of
** Attachment added: "config-4.11.11-300.fc26.x86_64"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4925001/+files/config-4.11.11-300.fc26.x86_64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, exactly. There is no issue with Kernel 4.10 (16.04 HWE or 17.04).
Current 17.10 Kernel does not boot properly. Unfortunately there are no
logs, even on persistent journald. The OS freezes after switching from
initramfs to real rootfs.
Any hints what logs I could try to gather to pinpoint
** Attachment added: "policy.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924570/+files/policy.log
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "release.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924569/+files/release.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707641
Title:
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924552/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707641
Title:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924550/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707641
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924551/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707641
Title:
Public bug reported:
When using Sunix latest low power VGA or DVI controller (see link below)
on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the
system to crash on boot (the system will not become reachable via
network too, so I cannot extract any logs).
By using a second
I installed Kernel 4.13-rc1 on 3 workstations so far and tonight one of
them froze once again, this time leaving the attached Kernel panics in
the journal.
** Attachment added: "panic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4918653/+files/panic.txt
**
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915932/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704718
Title:
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915930/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704718
Title:
** Attachment added: "release.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915929/+files/release.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704718
Title:
** Attachment added: "policy.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915928/+files/policy.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704718
Title:
Public bug reported:
I'm currently looking into stability issues of several AMD Ryzen based
PCs in our company using Ubuntu 16.04 HWE and 17.04.
So far I was only able to find a single journal or log entry, which may be
related to the problem:
->%-
Jul 17
Thanks everyone for your quick response and fix of the problem!
I can also confirm that Kamal's Kernel works.
$ cat /proc/version
Linux version 4.4.0-41-generic (root@gomeisa) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #61~lp1626894KamalPatched SMP Mon Sep 26
19:28:58 UTC
Sorry for the late respond, I didn't have access to the hardware during
the weekend.
I've just tested both kernels and can confirm, that the second one works
correctly:
->%-
root@Ubuntu-1604-xenial-64-minimal ~ # uname -a
Linux Ubuntu-1604-xenial-64-minimal
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746845/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626894
** Attachment added: "release.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746843/+files/release.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626894
** Attachment added: "policy.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746842/+files/policy.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626894
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746841/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746844/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626894
Public bug reported:
After upgrading from linux-image-4.4.0-38-generic to proposed update
linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
shows a probe failure.
On the previous kernel version everything is working as expected.
->%-
[
Public bug reported:
Greetings,
pcsd does only bind to IPv6 instead of IPv4 and IPv6, if it is started
on a machine, which has active IPv6 support.
->%-
lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
-%<-
apt-cache
Public bug reported:
Greetings,
after the first installation of pcs on a freshly installed Ubuntu 16.04
minimal the pcsd cannot start because of a missing gem.
->%-
lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
35 matches
Mail list logo
