lier.
> https://bugzilla.redhat.com/show_bug.cgi?id=1565131;
>
> What is most helpful is if one confirms with their hardware via adding
> and reverting the potential fix commit that it does indeed address their
> issue.
>
--
fREW Schmidt
https://blog.afoolishmanifesto.com
--
You received t
Good news! the 4.17.0-rc3 kernel *fixed this issue*! You can get it
here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3/ I only
tried undocking once so far but hey, I was able to undock and redock and
there was no oops in dmesg. I will likely try again later throughout
the day for
Same.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1767452
Title:
kernel oops when I undocked
Status in linux-signed package in Ubuntu:
Confirmed
Bug description:
Here's
I just realized why I thought this was not predictable. The system
continues to function just fine after the Oops *until* I close my
laptop. Once I close my laptop the whole thing freezes and does not
recover. Attaching one last kernel log and then will leave it alone
till someone asks for more
I reproduced this this afternoon with the latest stable kernel (4.16.6.)
See attached subset of the kernel log. I'll try with 4.17 tomorrow.
** Attachment added: "kern2.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767452/+attachment/5131193/+files/kern2.log
--
You
> https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767452/+attachment/5130886/+files/thunderbolt_crash
>
--
fREW Schmidt
https://blog.afoolishmanifesto.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in
Public bug reported:
Here's a snippet from the kernel log which I think will make the actual
issue clear:
Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused
to change power state, currently in D3
Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0:
Here's the above in an (unmunged) attachment
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767452/+attachment/5128741/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Ok, confirmed. Just happened after switching to one of the TTYs:
Jun 16 09:03:35 zfp kernel: [205770.823411] nouveau :02:00.0: DRM: resuming
kernel object tree...
Jun 16 09:03:35 zfp kernel: [205770.823583] nouveau :02:00.0: priv: HUB0:
10ecc0 (1b70822c)
Jun 16 09:03:36 zfp
Ok so Seth Forshee asserted that all of the mainline builds have been
fixed, and I have installed 4.7-rc2 again and it is not missing a vdso.
Will update here if the crash happens again. If it hasn't happened in
60 days it didn't happen or I died.
--
You received this bug notification because
So I installed 4.7-rc2, but it is a broken build. I will reboot out of
it shortly. Details are here:
http://www.openwall.com/lists/musl/2016/06/08/4
For some reason, either related to the kernel or the build tools, the
vdso in that kernel is broken. If another one gets built I'll happily
test
Sure, is there a commit that you think will fix it? (Will try tomorrow
morning.)
--
sent from a rotary phone, pardon my brevity
On Jun 7, 2016 5:05 PM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
frew, could you please test the latest mainline
DMIDecode output:
GLET83WW (2.37 )
03/31/2016
It is not improved.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok. I'll update the BIOS on monday; I don't have a CD-R handy to flash
the BIOS with. This is a rare enough issue (every couple of weeks I
guess?) that I guess I'll update the BIOS and check back here in maybe
60 days if it hasn't happened again.
Thanks for the direction, I hope it resolves it!
Did anyone report this upstream or anything? Would love to follow
along.
--
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/1576764
Title:
Kernel bug caused by XRandR / Video Drivers
Look it happened again with the upstream kernel!
May 5 13:37:44 zfp kernel: [ 61.795795] general protection fault: [#1]
SMP
May 5 13:37:44 zfp kernel: [ 61.795822] Modules linked in:
snd_hda_codec_hdmi(+) joydev input_leds serio_raw snd_hda_codec_realtek iwlwifi
Kernel installed. This happens frequently enough (almost daily) that
I'll just wait a week and if it hasn't happened by next Thu I'll mark it
as fixed upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Here are two stack traces showing the issue:
Apr 29 08:33:05 zfp kernel: [34730.860474] general protection fault: [#1]
SMP
Apr 29 08:33:05 zfp kernel: [34730.860507] Modules linked in: ctr ccm xt_nat
xt_tcpudp ipt_REJECT nf_reject_ipv4 pci_stub vboxpci(OE)
This issue started when I upgraded from 15.04 to 15.11. Thus it did not
happen with 3.19.
I tried to reproduce with 4.3 but I cannot, because AUFS is applied by
canonical and is thus not in the upstream kernel.
Please advise on how to continue from here.
--
You received this bug notification
This issue started when I upgraded from 15.04 to 15.11. Thus it did not
happen with 3.19.
I tried to reproduce with 4.3 but I cannot, because AUFS is applied by
canonical and is thus not in the upstream kernel.
Please advise on how to continue from here.
--
You received this bug notification
Public bug reported:
Basically, when I write "a lot" of data while in a docker container I
can consistently crash my machine. Here are some logs that I gathered
when trying to figure this out:
Nov 04 08:58:54 zfp kernel: BUG: unable to handle kernel NULL pointer
dereference at 0098
21 matches
Mail list logo
