just happened for me running 4.10.10-041010-generic running google-
chrome-beta, went to this page : http://www.abc.net.au/news/2017-10-16
/north-korea-missile-range-map/8880894 . If you're running vanilla
kernels you need 4.11.6 I think?
https://bugs.freedesktop.org/show_bug.cgi?id=99295
--
You
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux-hwe (Ubuntu Zesty)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 4.10.0-33.37
---
linux (4.10.0-33.37) zesty; urgency=low
* linux: 4.10.0-33.37 -proposed tracker (LP: #1709303)
* CVE-2017-1000112
- Revert "udp: consistently apply ufo or fragmentation"
- udp: consistently apply ufo or
This bug was fixed in the package linux-hwe - 4.10.0-33.37~16.04.1
---
linux-hwe (4.10.0-33.37~16.04.1) xenial; urgency=low
* linux-hwe: 4.10.0-33.37~16.04.1 -proposed tracker (LP: #1709304)
* linux: 4.10.0-33.37 -proposed tracker (LP: #1709303)
* CVE-2017-1000112
-
Enable proposed updates from the "Software updater" application, install
whatever updates you get, then disable proposed updates again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
This bug affects me too.
@Sam Stenvall: How can I install the Xenial kernel from -proposed?
Aug 23 12:31:46 U571T kernel: [40284.307406] BUG: unable to handle kernel NULL
pointer dereference at 0018
Aug 23 12:31:46 U571T kernel: [40284.307480] IP:
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To
FWIW the Xenial kernel from -proposed seems to work just fine too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage
** Changed in: linux
Status: Unknown => Fix Released
** Changed in: linux
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to
Can't reproduce the crash as described before (consistently failed on a
heavy export job in virtualbox W10 guest).
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
** Description changed:
Upgraded to zesty about a week ago. Ran into this on latest kernel.
@kleber-souza It seems like the issue affects both Zesty and Xenial
(when using the HWE stack). Does that mean that we need an additional
tag "verification-done-xenial" or is it sufficient the way you write it
above? Thanks for clarifying!
--
You received this bug notification because you are a
Just installed the kernel from proposed, if I don't report back that
means it works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
@negge The fix for Ubuntu 16.04 (linux-generic-hwe-16.04) has been
merged and will be part of the next update (4.10.0-33.37).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty
Can someone comment here once a fix for the HWE kernel in Ubuntu 16.04
is available? I'm currently using one of the custom builds from earlier
in this thread but I haven't yet been able to confirm whether it fixes
the issue or not.
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
@philipp-classen
4.10.0-30.34~16.04.1 is a release for CVE-2017-7533 only, it does not contain
the patch.
The patch is not been applied in master-next of ubuntu-zesty kernel tree.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7533
--
You received this bug notification
After enabling proposed updates, I see 4.10.0-30-generic is available.
Does it already contain the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel
@brad-figg Thanks, that's good to hear!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about this bug
The fix for this issue will get committed to the appropriate Ubuntu
kernel repositories this week and will be included in the next kernel
SRU cycle. Kernels with this fix should be landing in -proposed next
week.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=99295
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty
If anyone else is having the issue with running @chichun's kernels, it
could be due to the efi.signed image taking precedence. On my Dell XPS
13 the default kernel that boots was
`vmlinuz-4.10.0-28-generic.efi.signed`. I forced it to use
`vmlinuz-4.10.0-28-generic` and am now running the patched
@chihchun Many thanks for your work on this issue!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about
@s-illes79-gmail developers asked the end user to verify the upstream
kernel, it's to identify if it's a regression or fixes have been landed.
It helps when we don't know the patch or the root cause of the issue at
the early stage.
We know the root cause and patch of this issue, and we also know
@Rex Normally we are asked to test the upstream kernel and I also gave
up on ubuntu to fix 4.10.
Right now testing 4.11.12-041112-generic so far this seems to be ok
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@s-illes79-gmail New kernel may introduce regression or new issue, I don't
think testing 4.12 is in the scope of this bug.
@mstucki You don't need linx*tools* packages.
@samvde Please follow the instruction on wiki[1]. You may have other ppa,
apt-cache policy linux-image-4.10.0-28-generic can
@matthias-opennomad
I use sudo apt install /directory-with-the-debs/*.deb. Use absolute
paths for this.
It warns about downgrading, after which the install runs fine.
@mstucki
Are you running on HWE ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@chihchun Actually I could not install your kernel on 16.04 without
breaking dependencies. It requires binutils >= 2.29 (or 2.28, not sure
if I remember correctly) but Ubuntu 16.04 only includes version 2.26. So
I manually edited the config file in your archive to remove that
restriction. I guess
@chichun I've tried installing you debs, but my uname keeps reflecting
the Jun 30 date. I pull all the debs and install them with `sudo dpkg -i
--force-overwrite *.deb`.
Is there some other magik incantation to force this?
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe (Ubuntu Zesty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
@chihchun
Out of interest: could you give the procedure how you build this (I've
seen various recipes online)?
On my system, your debs are considered a lower version to the
repositories that have 4.10.0-28 as well and will offer to "upgrade" it
to the official ones every apt upgrade cycle.
So I
I've been experimenting with 4.12.3-041203-generic, not crashes but
sometimes the screen goes blank for 3 seconds, from syslog
Jul 27 14:50:45 XPS13 org.gnome.Shell.desktop[1986]:
intel_do_flush_locked failed: Cannot allocate memory
it recovers nicely, no apps gets killed and nothing gets
@Nazar Gerasymchuk (troyan3)
No, you are not using my version. mime is built at Sat Jul 22 12:39:20 UTC 2017.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
@Rex Tsai (chihchun)
It will be ridiculous...
$ uname -a
Linux tro-T460p 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Nazar Gerasymchuk (troyan3)
Could you provide the output of "uname -a" on your testing kernel? you might
have installed the version from Ubuntu archive without the fix, but not the deb
version I built.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
2 Rex Tsai (chihchun)
I've been using your patched kernel since 2017-07-23, but today I've got
crash, and it seems quite similar (see attachment).
** Attachment added: "Few lines from kern.log"
@flipvb
The main issue is not that this bug exists and that it is not the fault
of Canonical. The issue is that the 16.04 stable HWE LTS stack rolled to
4.10 despite this bug being known and being critical, with 16.04.3 not
even released yet.
--
You received this bug notification because you
Believe me I already complied there, but nothing happened.
Just had this crash again ( after installing
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe )
[19537.273820] BUG: unable to handle kernel NULL pointer dereference at
0018
[19537.273892] IP:
I understand that people are *** off by this bug, but keep in mind this
bug is not the fault of Canonical or any of the ubuntu developers, this
bug actually is the result of the developers at freedesktop/intel
pushing their broken code into the mainline kernel release and only
(partially) fixing
I'm using debs from http://people.canonical.com/~chihchun/lp1680904/
since 2017-07-23 -- lots of heavy work, with VM running almost all time.
No crashes happened yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this is ridicules, this bug was reported long time ago (2017-04-07), the
patch was created long time ago and here we go.
I might need to abandon the Ubuntu ship and install openSuse or
something else where bugs get fixed.
--
You received this bug notification because you are a member of Ubuntu
I can consistently reproduce this issue doing a heavy mail export job in
a VirtualBox guest I use for work.
Just having done first run after applying the deb files provided per
comment 52, I was not able to reproduce the issue. Thank you @chihchun !
Canonical needs to apply these asap if they
I can also confirm this bug with Ubuntu 16.04 and kernel
4.10.0-27-generic on a Dell XPS 13 from 2015.
I had a system freeze yesterday and today. In the months before I never
experienced any problems despite heavy swapping.
--
You received this bug notification because you are a member of
I can now confirm this bug landed on the LTS HWE kernel.
Honestly, I get Ubuntu for free (well I support them but by no means
this is comparable to certain other license schemes out there) but I
have never been so disappointed. All my systems are now at risk. I don't
know who does QA at Canonical
Ok, I'll give it a go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about this bug go to:
@samvde yes, the build include zfs. The deb is built with Ubuntu zesty
kernel tree with the cherry-picked patch.
@mstucki you can cherry pick 1933a35[1] or Chris Wilson's patch[2].
[1] https://patchwork.kernel.org/patch/9789601/
[2]
@chihchun Thanks, but I'd like to build this on my own. Which patches
did you add?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer
@mstucki If you have time, please kindly verify the deb[1] solved your
issue.
[1] http://people.canonical.com/~chihchun/lp1680904/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
@chihchun does your build contain zfs modules?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about
I'm a user of the linux-image-generic-hwe-16.04 package on Ubuntu 16.04.
Until last weekend, I've never had this issue (using kernel 4.8.x) but
today on 4.10.0-27-generic this happened twice to me!
If there's a fix for this issue then it should be merged into this
release pretty quick...
--
You
@ Rex Tsai Thanks for prebuilt kernel. I've installed packages you
provided via http://people.canonical.com/~chihchun/lp1680904/
Will try to test it for a while and write if I got any news/conclusions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was not expecting the 4.10 kernel to land in the HWE stack for LTS
without seeing a fix here, so I am genuinely worried about the LTS+HWE
stability now.
Can we get confirmation on the state of the HWE 4.10 kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about this bug go
There are two patches to address the issue, one for v4.11[1] which can
be backported for 4.10 for zesty and current 4.11/master-next branch for
artful. The other one has been landed in v4.12[2].
I assume the first patch[1] should be landed for zesty. I can not
reproduce the issue on Lenovo
I noticed the HWE kernel rolled from 4.8 to 4.10.0-27-generic, and I
wondered if someone knows whether this bug was addressed in that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
Agreed. I also saw it with firefox when I tried just swapping out the
browser. I'm back to chrome and disabling hardware accelaration has been
working for me so far. In the end I'd just really like to see this
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
2Matthias As I mentioned, I've tried Firefox too. But got that bug few
times.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To
For me it's always been chrome. After unchecking "use hardware
acceleration when available" I've not had it hang again. This is going
on 3 weeks now for me. Side effect is that some fancier websites
generate some ugly artifacts temporarily at times.
--
You received this bug notification because
I'm on 4.10.0-28 right now, and tried almost all kernels downto
4.10.0-19.
Most used case to face this bug is when I'm running VirtualBox and
Chrome with lots of opened pages. Few times it happened to me when I
open new tab in Chrome. I thought that its all about Chrome and
absolutely switched to
just had a crash with 4.12 ... nothing in the log after reboot so cannot
neither confirm nor deny this was the same crash :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty
I'm already on vanilla 4.12, no issues so far :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about
FYI, 4.12 was released as stable yesterday, so I'm hoping the
maintainers of Ubuntu/Fedora/etc have the patches ready for update in
the next week or so and this problem will be a thing of the past!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
just had this:
Jul 3 15:06:22 XPS13 kernel: [36225.817104] BUG: unable to handle kernel NULL
pointer dereference at 0018
J
i was ok for a week, than opened chrome and boom.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I got the same error - it happens twice:
Kernel: 4.11.5-1-ARCH (upgrading now to 4.11.7, but i will try 4.12 RC)
[881346.853394] BUG: unable to handle kernel NULL pointer dereference at
0018
[881346.853465] IP: gen8_ppgtt_alloc_page_directories.isra.16+0xd9/0x280 [i915]
But it's
Well, the patch I mentioned in comment #28 is not perfect, crashes still
happen, just way less often (I achieved several days uptime while
without the patch the crashed usually happened twice a day).
Today's crash with the patch on top of Ubuntu-4.10.0-23.25 tag:
Jun 16 12:21:15 patrickxps
I have this bug on Dell XPS 13 9360 with Ubuntu 16.04 and
4.10.0-22-generic (installed as depend of linux-generic-hwe-16.04-edge).
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671314] BUG: unable to handle
kernel NULL pointer dereference at 0018
Jun 16 00:55:13 adept-XPS-13-9360
I think I had the same problem on zesty. It started occurring AFTER I
used nvidia-settings to switch to integrated intel graphics on a Dell
XPS-15 9560 (GTX1050) and completely uninstalled nvidia drivers to get
back to a working laptop.
Indeed it seems to happen while using chromium. My machine
I am having this issue on Xubuntu Xenial with the linux-generic-
hwe-16.04-edge kernel. It happened once a long time ago, but now it is
happening again. This bug happens when the system is under load and more
graphical load is demanded. On my specific case, when my system is
already under some
This is relatively hard to reproduce. It happens sometimes directly
after boot and login, sometimes after more than a week uptime.
I've simply selected an older kernel at boot (4.8.0-46-generic; the
newest one I had installed from Yakkety) and I didn't experience a
crash, yet.
--
You received
just install 4.8-X from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.8.17/
but yeah I agree this should have been fix long time ago. there is even
a backport for 4.10 this has to go into the ubuntu kernel
what takes so much time i donno
--
You received this bug notification because you
I'm running 4.10.0-22-generic and it is still crashing (at least 2 to 5
times a day) (not only when running chrome, a couple of other
applications also cause this kernel panic to happen which completely
makes ubuntu (and any other linux distro on 4.10/4.11) unusable for work
@the moment...
I hope
has this been backported to 4.10 yet?
so far so go 4.10.0-22-generic is. maybe because I stopped using chrome
and use firefox instead?
2 days uptime and no crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm experiencing the same issue for a while now. I think it occurred
after I upgraded form Yakkety to Zesty.
I'm currently on 4.10.0-21-generic.
I think the issue is more likely to happen when I run CPU and / or RAM
intensive applications.
If this happens, all my screens are stuck.
**
Dell XPS 13 9343 running fine with
https://patchwork.freedesktop.org/patch/158340/ applied on top of
Ubuntu-4.10.0-22.24.
Got the hint from https://bugs.freedesktop.org/show_bug.cgi?id=99295#c53
** Attachment added: "patch-freedesktop-99295.txt"
Having this issue with Asus UX303UB, kernel 4.11.3 64 bits, Ubuntu 16.04.
Might be related to [this systemd kbus
bug](https://github.com/systemd/systemd/issues/378).
** Bug watch added: github.com/systemd/systemd/issues #378
https://github.com/systemd/systemd/issues/378
--
You received this
For those like me that fail booting 4.12rc3 but had no issue with
previous builds, this looks like a interesting trail:
https://bugs.launchpad.net/linux/+bug/1694561
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> I just tried and my Dell XPS 13 9343 does not boot (hangs with a blank screen
> right after kernel selection in grub) with generic variants from:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3
I can replicate this. Dell Latitude E7250.
--
You received this bug notification
v4.12-rc3 works for me, had it in the last 3 days, no crash. Dell XPS 13
9350 ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
Same issue with generic variant from http://kernel.ubuntu.com/~kernel-
ppa/mainline/drm-intel-nightly/2017-06-01/ this morning.
Also tried to select recovery mode in grub, no better: I only get a
black console screen with a blinking cursor in the upper left.
No error message, nothing in the
@Joseph,
I just tried and my Dell XPS 13 9343 does not boot (hangs with a blank
screen right after kernel selection in grub) with generic variants from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-05-31/
I need zfs and it fails on the proprietary nvidia driver too. I'll see
if I can get it running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL
I'm running on a custom kernel since this bug occurred to me a few weeks
ago. This was actually before the first rc (next branch) I'm therfore
not 100% sure if it got merged or not. I will build a new kernel 12 RC
tomorrow and report back (I can't use the upstream ppa versions as it
lacks aufs).
Can folks affected by this bug please test the v4.12-rc3 kernel? It can
be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have a similar problem, plug the mobil to the usb and the PC frozen:
Kernel: 4.10.0-21-generic
May 29 12:15:37 roal kernel: [13126.330476] usb 2-1: new high-speed USB device
number 3 using ehci-pci
May 29 12:15:37 roal kernel: [13126.479378] usb 2-1: New USB device found,
idVendor=22b8,
Every time it has locked up I've been scrolling in chrome.
[28680.993697] CPU: 2 PID: 4930 Comm: chrome Tainted: G OE 4.10.0-20-generic
#22-Ubuntu
[28680.993718] Hardware name: Dell Inc. Latitude E7450, BIOS A07 09/01/2015
As an experiment I've disabled hardware acceleration in chrome since all
With Linux XPS13 4.8.0-46-generic:
09:24:36 up 25 days, 10:33, 10 users, load average: 3.49, 2.40, 1.91
4.8.X is super stable, this is on a work laptop with high load.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've experienced apparently random freezes on 17.04 (kernel 4.10.0-21).
It appears to happen when Chrome is active, although Chrome is probably
active all the time. There's nothing out of the ordinary in kern.log,
but syslog has:
May 23 12:44:34 thornback unity-panel-ser[2612]: menus_destroyed:
Just experienced this on kernal 4.10.0-21 while running Chrome (not
chromium).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
It looks like the patch from Chris Wilson has not landed in mainline
yet. However, I'd like to see if this issue still occurs in v4.12-rc1,
which is current mainline. If it does, I'll submit the patch upstream
for Chris and SRU it to Ubuntu.
The 4.12-rc1 kernel can be downloaded from:
So experiencing several crashes a day (hard lock) I decided to install
the HWE 4.8 kernel using the Xenial deb files. No more lock ups have
occured since.
This seems to me an extremely critical issue at the heart of the OS. I
would have expected more visibility on this TBH.
--
You received this
After a few days of using the patched kernel: the patch is not a 100%
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: New => Triaged
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Medium
--
You
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** 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/1680904
Title:
zesty unable to handle kernel NULL
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about this bug go to:
I have implemented the workaround from #7
(https://bugs.freedesktop.org/show_bug.cgi?id=99295#c22) using the
attached patchfile on kernel 4.10.0-20.
My system crashed consistently when doing a resource heavy export job on
a VirtualBox Windows 10 guest. First try after patching this no longer
is
I have this issue and can provide logs if needed. Kernel
4.10.0-20-generic on Zesty. Very, very nasty bug causing very frequent
hard crashes. I think the importance ought to be raised on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Good find cxreg!
Indeed does look the same, happens when I am running chromium, cxreg
found bug happens in Chrome. So some path with the i915 there does
appear to be flaky.
Workaround seems to not be super effective given post
https://bugs.freedesktop.org/show_bug.cgi?id=99295#c27 unfortunately.
This looks like Redhat's bug for this same issue
https://bugzilla.redhat.com/show_bug.cgi?id=1441906
and it refers to an upstream fix
https://bugs.freedesktop.org/show_bug.cgi?id=100516
and also a workaround
https://bugs.freedesktop.org/show_bug.cgi?id=99295#c22
** Bug watch added: Red Hat
1 - 100 of 104 matches
Mail list logo
