I took lm-sensors out of the bug title because lm-sensors 1:3.4.0-4
works fine with an updated it87 driver.
$ sensors
it8686-isa-0a40
Adapter: ISA adapter
CPU Vcore:+0.77 V (min = +0.00 V, max = +3.06 V)
+3.3V:+3.39 V (min = +0.00 V, max = +5.05 V)
+12V:+12.38 V (min =
** Description changed:
+ Summary: Thermal sensors are not accessible due to being unsupported by
+ the it87.ko module in linux-image-extra which does not include the
+ it8686 model line among others..
+
+ Expected behavior:
+
+ $ journalctl | grep it87:
+ Apr 20 21:36:00 lakshmi kernel: it87: i
** Package changed: ubuntu => linux (Ubuntu)
--
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/1740736
Title:
Driver it87 and lm_sensors are too old and don't support newer
chipsets (such
I'm using the default that comes with 18.04
uname -svr
Linux 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018
The same IOMMU=pt
$ grep iommu /etc/default/grub
GRUB_CMDLINE_LINUX="iommu=pt"
Fixed 4.14.* on 17.10 (I didn't try the default 4.13.* kernel)
Last tested on 4.14.33-041433-g
Please see comment #4
--
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/1758305
Title:
Panic during SyS_reboot
Status in linux package in Ubuntu:
Incomplete
Status in linux source packag
I no longer am using the motherboard, CPU and RAM that this happened on.
I am using 4.15.0-13-generic on 18.04 now.
--
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/1730374
Title:
NULL po
The system in question here used to panic in numerous ways until I started
using iommu=pt
Now it appears to be stable.
The BIOS setting for IOMMU is "auto".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
dmidecode output from BIOS F22
https://gist.github.com/mettacrawler/ed333ea4349f71c481892fe53eea6039
--
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/1759828
Title:
BUG: Bad page map in p
@malachid can you please try booting with:
iommu=pt
and see if that works?
--
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/1759947
Title:
BUG: unable to handle kernel paging request at
I'm on the new BIOS. It requires iommu=pt
Even with older kernels like 4.14.31 this computer requires iommu=pt
--
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/1759828
Title:
BUG: Bad pa
** Description changed:
Note that this is from an AMD Ryzen 5 2600G
Also the BIOS firmware is a beta, but the previous version, which is the
last so-called stable version is in much worse shape. For instance it
misidentifies the RAM as having CAS 19 when it's really CAS 16. The beta
Public bug reported:
Note that this is from an AMD Ryzen 5 2600G
Also the BIOS firmware is a beta, but the previous version, which is the
last so-called stable version is in much worse shape. For instance it
misidentifies the RAM as having CAS 19 when it's really CAS 16. The beta
BIOS firmware d
Public bug reported:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: device_shutdown+0xbb/0x200
PGD 0 P4D 0
Oops: 0002 [#1] SMP NOPTI
See the screenshot for more.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSigna
** Tags added: kernel-bug
--
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/1730374
Title:
NULL pointer dereference during writeback
Status in linux package in Ubuntu:
Confirmed
Bug des
** Description changed:
+ This could be part of CVE-2016-3070
+
Happened during dd of 40GB LV:
$ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo
I also used SIGUSR1 on the dd to monitor it occasionally. There was
other activity at the time as well.
It appears that an attempt was
It happened again.
$ uname -r
4.14.9-041409-generic
Dec 29 14:32:14 lakshmi kernel: BUG: unable to handle kernel NULL pointer
dereference at (null)
Dec 29 14:32:14 lakshmi kernel: IP: locked_inode_to_wb_and_lock_list+0x20/0x110
Dec 29 14:32:14 lakshmi kernel: PGD 0 P4D 0
Dec 29 14:32:
It's likely that this was either fixed upstream or the root cause is
from a patch that was put on the 4.13 kernels that the 4.14 kernels
don't have.
Nov 05 22:15:30 lakshmi kernel: Linux version 4.13.0-16-generic
(buildd@lcy01-02) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP
Wed Oc
Installation of 4.14.2
https://gist.github.com/mettacrawler/7d60c8f51a19b506ea1cb575c2ed4032
--
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/1730374
Title:
NULL pointer dereference during
I was unable to reproduce this on 4.13 until Nov 23 when it happened
again.
This time the logs show that I was handling PDF files via Nautilus which
doesn't imply as much disk I/O as the previous 40G dd did.
A quote from:
https://patchwork.kernel.org/patch/9614361/
{{ I am able to reproduce the p
Eventually I'll have time to test the upstream kernel.
--
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/1730374
Title:
NULL pointer dereference during writeback
Status in linux package in
I'd love to have time to work on this kernel bug but I have fires all
over the place with 17.10.
I have a dual-boot setup between 16.04 and 17.10. The 17.10 took over
nine minutes to boot originally. After finding out about
Debian_bug_867368 I got it to boot in over three minutes. It still gets
Public bug reported:
Happened during dd of 40GB LV:
$ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo
I also used SIGUSR1 on the dd to monitor it occasionally. There was
other activity at the time as well.
It appears that an attempt was made to fix this in 4.10
https://patchwork.kernel.org/patch
22 matches
Mail list logo
