Closing invalid as a bios update resolved the issues.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720263
Title:
BUG: unable to
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720263
Title:
BUG: unable to handle kernel paging request at ffe1
To manage notifications about this bug go t
Turns out I did not have the latest bios despite what Asus's wonderful
Windows autoupdate utility claimed. I manually downloaded and installed
the latest bios, which contains an Intel microcode update, and I haven't
had a single crash since.
I even had the intel-microcode package installed, but it
I tried Fedora Rawhide (26's nouveau doesn't work with my graphics
card), with kernel 4.14.0-0.rc2.git4.1.fc28.x86_64, repeatedly starting
atom and chrome is the easiest way to trigger it.
I also tried security=none and disabling hyperthreading (even though I
should have the microcode fix for the
And more:
[ 1177.958926] chrome[8687]: segfault at 373506627019 ip 373506627019 sp
7fff94d12950 error 15
[ 1772.670263] BUG: Bad page state in process atom pfn:6e57e6
[ 1772.670267] page:f4f35b95f980 count:0 mapcount:-4096 mapping:
(null) index:0x1
[ 1772.670269] flags: 0x1
I tried security=none, it didn't help. I also tried the ubuntu-gnome
17.04 live-usb, and it panicked on boot.
I ran memtest and found that one of my memory sticks was defective.
However, I still have some problems with only two sticks that did pass
memtest.
This is with the 4.13 ubuntu kernel:
[
Just a comment from a security module developer.
What happens if you pass security=none to kernel command line options
(i.e. disable AppArmor security module), for I think it might help
isolating the problem because you are hitting oops at
security_vm_enough_memory_mm() and security_file_free().
Got an oops with 4.14 that hung firefox (like the ubuntu 4.13 kernel),
had to hard-reset because the restart process couldn't kill my session.
The 4.14-rc2 mainline kernel has some other bugs: network-manager can't
get an ip via dhcp, I have to manually run sudo dhclient (sometimes
multiple times)
(My previous comment was too long, so I moved the logs to the end.)
The 4.13.0 mainline kernel is unusable, it panicked once immediately after
boot, the second time it hung on the boot splash, the third time when I tried
to open this page in firefox.
There was also an oops before the third hang,
The 4.13.0 mainline kernel is unusable, it panicked once immediately after
boot, the second time it hung on the boot splash, the third time when I tried
to open this page in firefox.
There was also an oops before the third hang, and that's the only thing present
in kern.log:
Sep 30 10:24:47 Hyp
It's a clean install. I barely managed to install it though. There are
no other versions of the kernel in the repository.
I'm going to try the mainline kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720263
Title:
BUG: unable to handle kernel paging request at ffe1
To manage notifications about this
13 matches
Mail list logo
