This delay appears to be occurring because grub passes "console=ttyS0"
on the commandline.
--
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/1879290
Title:
pc: no message on the screen for
And, "console=ttyS0" on it's own is particularly bad because it seems to
default to a baud rate of 9600 (at least, setting it to 115200 on my NUC
improved things considerably, but the boot is still slower than without
the serial console option). Add that to the fact that the kernel is
quite noisy o
I briefly tested the kernels and I'm seeing that the log is consistent
with the PCR values in the TPM. May I ask what tool it is you're using
in those screenshots so that I can try it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
I think the reason for your issue is that the final 2 events extended to
PCR7 are recorded twice in the log, most likely because the test kernel
from comment 12 doesn't contain
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=166a2809d65b282272c474835ec22c882a39ca1b
I
Hi,
In response to your queries:
1) With kernel version 5.0.0-37, I can confirm that the event log
provided by the kernel is inconsistent with the TPM for PCR7 in a VM
that's running OVMF. This is because of the opposite problem - in this
case, the last event is missing from the log exported by t
I just noticed I didn't respond to the question in comment 16. The tool
I'm using is https://github.com/chrisccoulson/tcglog-parser
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1838
Ok, I think that the truncated log issue with kernel version 5.0.0-37 is
a bug in tpm1_bios_measurements_next() which is fixed by
https://lore.kernel.org/patchwork/patch/1031236/, although I've not
verified that this is the case.
--
You received this bug notification because you are a member of K
Public bug reported:
My machine locks up for several seconds at a time quite regularly.
During this time, nothing on the screen responds to input. Eventually it
unfreezes, and I see this in dmesg:
[87414.775168] [drm] stuck on render ring
[87414.775176] [drm] GPU crash dump saved to /sys/class/dr
** Attachment added: "Contents of /sys/class/drm/card0/error"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328048/+attachment/4128083/+files/error
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Public bug reported:
I've just tried both -39 and -40 in xenial-proposed, and both fail to
boot on my laptop (dropping to busybox - see the attached screenshot).
This is a regression over -38, which works fine.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.
The kernel in xenial-proposed doesn't boot on my laptop (see bug
1627670)
--
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/1627074
Title:
linux: 4.4.0-40.60 -proposed tracker
Status in Ke
I was just going to say - I tested the 3 kernels in comment 3 and they
all worked. I'll test
http://kernel.ubuntu.com/~jsalisbury/lp1626894/30d6592-reverted/ now
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
And the kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1626894/30d6592-reverted/ also
works.
--
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/1627670
Title:
4.4.0-40.60 fails to boot
That test kernel works fine too.
--
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/1627670
Title:
4.4.0-40.60 fails to boot
Status in linux package in Ubuntu:
Triaged
Status in linux sou
I keep experiencing a crash when trying to run kvm with this kernel on
the host. This doesn't happen with the current kernel in raring-updates
Jul 24 10:32:41 farnsworth kernel: [ 91.512726] general protection fault:
[#1] SMP
Jul 24 10:32:41 farnsworth kernel: [ 91.512757] Modules linke
I have the same bluetooth device and just purchased a bluetooth headset,
expecting HSP/HFP to work. I saw bug 1065400, but I've got no idea where
to find the firmware for my device :/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez i
Public bug reported:
I've just had my machine lock up for the second time in 2 days, although
the first time left no trace in /var/log/kern.log. This is what I've
just seen:
Aug 11 15:22:05 farnsworth kernel: [53211.181003] BUG: unable to handle kernel
paging request at 000101500034
Aug 11 1
> I didn't quite get as far as understanding why the BOGUS NID matters
and what that breaks, or what is fixed by the change, fully.
The issue is that the unique identifiers are meant to be unique between
drives, but some specific SSDs do not report unique values, which makes
them difficult to iden
18 matches
Mail list logo
