This may be the missing patch. Willing the try a build with it at least.
commit b49feacbeffc7635cc6692cbcc6a1eae2c17da6f
Author: Sasha Neftin
Date: Sun May 8 10:09:05 2022 +0300
e1000e: Enable GPT clock before sending message to CSME
On corporate (CSME) ADL systems, the Ethernet C
Public bug reported:
This is a Dell Precision 3460 workstation (Alder Lake CPU) with latest
BIOS and Intel AMT turned off in the BIOS.
When enabling the Power -> 'Automatic Suspend' setting the e1000e wired
ethernet is always broken on wake up. rmmoding and modprobing the e1000e
driver will event
This still happens on a fresh Focal install using linux-
image-5.4.0-26-generic version 5.4.0-26.30
** Also affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: bionic
** Tags added: focal
--
You received this bug notification because you are a member of K
Were you still wanting to test this new kernel?
On Mon, Jul 25, 2016 at 2:33 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> This does appear to be an Ubuntu specific kernel. I'll build an Ubuntu
> kernel based on 4.0 and post a link to it for testing.
>
> --
> You received this b
Wasn't testing with 3.16 and 3.19 ubuntu patched kernels enough to disprove
the grub theory?
Jason
On Mon, Jul 25, 2016 at 1:44 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Can you see if the bug still happens when booting a Trusty kernel on the
> Xenial system? This can be d
As a clarification, the mainline boot behaviour is identical to the Ubuntu
kernel with $vt_handoff removed. I double checked that the option is
present in grub for all the tests. I guess this isn't surprising since that
option isn't part of mainline.
Jason
On Wed, Jul 20, 2016 at 8:30
4.1.0-040100-generic works
4.4.14-040414-generic works
Didn't test others.
The boot sequence is different with the main line kernels. There is a black
screen period with a couple of messages (1-2s), then the console font load,
then it briefly switches to the splash, black screen flash back to th
On Mon, Jul 18, 2016 at 2:48 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Does booting back into the Trusty kernel on the Xenial installed system
> make the bug go away?
>
Yes. I've done multiple reboot experiments now and have learned the bug
only happens about 80% of the time
Public bug reported:
This is a regression, at least trusty (and prior) worked fine on this
hardware.
Booting the Xenial installer image off USB also worked fine.
The system boots fine, however the monitor is in DPMS power-off and does
not ever turn back on. Switching VTs doesn't help, I have fou
Well, if I understand https://wiki.ubuntu.com/KernelTeam/KernelUpdates
properly, oops fixes for raring will not be accepted since it is not a
LTS and it is past 4 months after release.
So I guess that is the end of it.
--
You received this bug notification because you are a member of Kernel
Pack
I'm not familiar with Ubuntu's process. This is clearly a bug in Raring,
fixed in upstream and I would certainly like a backport to the Raring
kernel package as we have no plans here to use Saucy, which isn't even
in beta yet :)
--
You received this bug notification because you are a member of Ke
ore information when we already know
that 3.11 solves the issue.
Jason
On Tue, Aug 27, 2013 at 4:07 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Jason Gunthorpe, testing the live environment would be just fine.
>
> --
> You received this bug notificat
they actually seem to fix
oops's with a similar back trace.
On Mon, Aug 26, 2013 at 6:11 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Jason Gunthorpe, could you please confirm this issue exists with the
> latest development release of Ubuntu? ISO ima
So, it has been 11 days and 3.11.0-031100rc5-generic hasn't crashed, I
think that is enough to confirm it is fixed in this version.
Per Joseph's instructions I've added the 'kernel-fixed-upstream' and
marked the bug complete.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
*
Joseph:
I have successfully booted:
Linux jggl 3.11.0-031100rc5-generic #201308112135 SMP Mon Aug 12
01:35:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Since I don't know how to reproduce the crash, I will update this bug
either when 3.11 crashes or in about a weeks time.
** Changed in: linux (Ub
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774136/+files/UdevDb.txt
--
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/1212818
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774138/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774133/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774135/+files/PulseList.txt
--
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/
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774137/+files/UdevLog.txt
--
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/1212
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774134/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774132/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774127/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774129/+files/Lspci.txt
--
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/1212818
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774130/+files/Lsusb.txt
--
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/1212818
apport information
** Attachment added: "HookError_cloud_archive.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774128/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774126/+files/BootDmesg.txt
--
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/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1212818/+attachment/3774131/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Tags added: apport-collected
** Description changed:
It is hard to get an oops because the entire FS system seems to hang and
/var/log/kern.log won't capture it. I have managed to get a kdump
capture. I think I told apport to submit the crash dump, but I'm not
real
Public bug reported:
It is hard to get an oops because the entire FS system seems to hang and
/var/log/kern.log won't capture it. I have managed to get a kdump
capture. I think I told apport to submit the crash dump, but I'm not
really sure if it worked, and I don't know where to look to see if i
30 matches
Mail list logo
