Guys, this is not a panic, it's history-daemon process that dereferences
a rouge pointer, it has nothing to do with the kernel - the kernel just
print out that your application dereferenced a rouge pointer.
** Summary changed:
- arm64 kernel panic for l2 mmu with unity8 session snap (& deb as wel
Paolo, you marked this invalid. Is there a workaround or does the
kernel no longer panic in this case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu wit
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well)
** Summary changed:
- arm64 kernel panic for l2 mmu with unity8 session snap
+ arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625
Kevin, the oops above is just the history-daemon process that
dereferences a stray pointer: i can reproduce it on every arm64
installation where i tried running the history-daemon (classic or
snappy), or a test.c prg like the one below.
(here is my raspberrypi3 in arm64 mode dereferencing a fooba
is there any update to this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session snap
To manage notifications about this bug go to:
ht
I can reproduce it on a ubuntu-classic installation on the Dragonboard,
just trying to execute the history-daemon as an unprivileged user:
$ sudo apt-get instal history-service
$ sudo reboot
login again:
$ history-daemon
Using database at "/home/ubuntu/.local/share/history-service/history.sqlit
@ppisati - didi you need anything else?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 m
@ppisati - if you have a classic deb based filesystem that is Xenial based, add
the ppa:ci-train-ppa-service/stable-phone-overlay (update/upgrade), then you
can simply apt-get install unity8-desktop-session-mir. Once that is installed,
you can toggle between unity8 & unity7 by clicking the ubunt
Ok, i was able to reproduce this on a classic image by installing the
snap core / unity-session 8 snaps and running it under snap-confine -
now, how can i recreate the unity-session8 binary locally? I want a
vanilla linux elf executable that i can run on a vanilla ubuntu classic
image to start digg
I tried running the unity8-session on DB as per the steps mentioned in above
doc but process terminated as soon as it launched followed by several respawing
messages. Please find attached the relevant syslog as well as terminal output
after launching unity8-session is here
https://paste.ubuntu.
My dragonboard environment info is
~$ snap list
NameVersion Rev Developer Notes
dragonboard 16.04-0.1723 canonical -
dragonboard-kernel 4.4.0-1024-3 9canonical -
snapweb 0.21 17 canonical -
ubuntu-core 16.04.1 759
@ppisati sorry about that, must've had too many tabs open. Corrected the
link and shared the doc with you as well.
** Description changed:
we are running the unity8 session snap on amd64 without any problems.
- to setup and reproduce the problem follow the "on Dragonboard" section of
https://d
There's no "on Dragonboard" section in the document linked above, is
there a way to reproduce it on a classic image?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic f
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session sn
oh, do you ship mesa in the mir server snap ? i didnt think that would
be possible
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session snap
@ogra actually we do! we all lucked out, recently (like within the last
month) someone somewhere turned on gallium/freedreno drivers for our
mesa builds. So i've got the full stack, i've already run the mir-
server/client snap on it with no problems (really need to blog that)
--
You received this
so to be clear, this on ubuntu-core dragonboard image from the beta
images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session snap
To man
i assume this is running a snap on a classic image, not on an ubuntu core one ?
(since we have no EGL support in teh core image yet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm
** Also affects: linux (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/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session snap
To ma
20 matches
Mail list logo
