I've also seen this issue with a Dell R740 server, Xeon Gold 6132 CPU @
2.60GHz, kernel 4.13.0-37-generic. Switching to hpet clocksource
mitigated it successfully.
Unfortunately I still haven't had the opportunity to test this on 4.15.
** Summary changed:
- Very inaccurate TSC clocksource on HP
Using an HP ProLiant DL380 Gen10 (Intel Xeon Gold 5118 CPU @ 2.30GHz) I
tested the following kernels (on xenial):
4.13.0-37-generic - FAIL https://pastebin.canonical.com/p/RbTzC3jgjm/
4.13.0-39-generic - PASS
4.13.0-45-generic - PASS
4.15.0-29-generic - PASS
So it seems this was fixed in 4.13.0-3
Public bug reported:
On kernel 4.13.0-37-generic, HP ProLiant DL380 Gen10 systems have been
observed with very large clock offsets, as measured by NTP. Over the
past few days on one of our production systems, we've used 3 different
kernels: https://pastebin.ubuntu.com/p/nDkkgRqdtv/
All of these
** Tags removed: artful
** Tags added: canonical-is
--
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/1759787
Title:
Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel
** Description changed:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
- 2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
- Ubun
I'm no longer experiencing this on 4.13.0 series kernels.
--
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/1649727
Title:
No sound card detected with device: Intel Corporation Device 9d71
Azure timesync is preventing a number of our production services from
getting accurate timesync; when is the xenial SRU likely to be
available?
--
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
I'm experiencing this intermittently on a Lenovo ThinkPad T470; I'm
currently running 4.12.0-041200-generic, and it has been patchy
throughout the 4.12.0-rcX series. Anything I can do to gather info?
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
For posterity: If
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/comments/143
is the cause of this issue for you, dmesg -D (which turns off console
logging of kernel messages) might be a viable workaround until you can
reboot.
--
You received this bug notification because you are a
This seems to be the same oops as http://oops.kernel.org/oops/warning-
at-drivers-gpu-
drm-i915-intel_display-c3313-intel_crtc_wait_for_pending_flips0x160-0x170-i915/
It might be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384342, which
seems to be the same oops as http://oops
I've experienced this also on the latest standard kernels on utopic.
The kernel that jondee mentioned above is no longer available, and there
seems little activity on the upstream bug. Is there a preferred kernel
which utopic users should be testing?
The oops I experienced seems to be similar to
Thanks Christopher. It looks like only 3.18-rc2 is available for utopic
at this stage: http://kernel.ubuntu.com/~kernel-ppa/mainline/ Is that
worth trying, or should I wait for a newer one to become available?
With respect to regression, this is definitely worse on utopic than it
was on trusty:
I'm on 3.19.0-031900rc3.201501060135 also for the past several days and
haven't experienced any lockups. So far, so good.
Is there a way to add the mainline kernel as a true PPA so that we get
updates automatically?
--
You received this bug notification because you are a member of Kernel
Packag
We've also been running into this issue on ScalingStack instances
recently; I got this traceback which seems to strongly implicate nohz as
the problem area: https://pastebin.canonical.com/158640/ Presently
testing @pitti's workaround on a number of different sized instances to
confirm.
--
You re
Public bug reported:
Reproducible by trying to do any non-trivial amount of I/O to one of the
installed SSDs, e.g.: dd if=/dev/sdb of=/dev/null bs=1024k
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.13.0-68-generic 3.13.0-68.111~precise1
ProcVersionSignature: Ubuntu 3.13.0-6
Console log available at https://pastebin.canonical.com/144076/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console logs kernel BUG at /build/
Reoccurred; console log at https://pastebin.canonical.com/144181/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console logs kernel BUG at /buil
It has happened every time I have run the dd example so far (and other
I/O such as rsyncing the Ubuntu archive into it). It happened on prior
kernels as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
htt
Those kernels don't appear to be precise-compatible, which is what this
machine is using.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console
Hi Joseph,
Here's what happens when I try to install http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.3-wily/linux-
image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb:
https://pastebin.canonical.com/144314/
Is there a specific repo which needs to be enabled in order to provide
kmod f
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521106/+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/1515828
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521104/+files/IwConfig.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/15
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521103/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521109/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521108/+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: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/452/+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/1515
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521110/+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/1515828
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521107/+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
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521105/+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/1515828
apport information
** Tags added: apport-collected
** Description changed:
Reproducible by trying to do any non-trivial amount of I/O to one of the
installed SSDs, e.g.: dd if=/dev/sdb of=/dev/null bs=1024k
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.13.0-68-
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521112/+files/WifiSyslog.txt
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Information type changed from Private to Public
--
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/1515828
Title:
system lockup, console logs kernel BUG at /build/linux-lts-trusty-
HlNG
That doesn't fix the missing kmod package on precise:
https://pastebin.canonical.com/144357/
--
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/1515828
Title:
system lockup, console logs ker
I've just updated to the latest BIOS, and it now is reporting 3 memory
modules are inaccessible, so this is looking more like it's hardware-
related. I'll report back as soon as we've resolved the hardware
issues.
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank
shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100%
sure), the last message before the screen
I ended up on 5.17 because I installed linux-oem-22.04 myself. (Ubuntu
isn't available on this hardware model in my region; it's a self-
install.) There was a bug introduced in 5.19 (I'll find the reference
when I get a moment) which meant that it wasn't stable on my system, but
I can give the la
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in li
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in li
lspci -vvnn output
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641118/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
h
Log from booting 5.17.0-1026-oem - this is the kernel that blanks the
screen and is thus unusable. Note the amdgpu errors beginning at line
961 which do not appear in the 5.17.0-1025-oem log.
** Attachment added: "kern.log-5.17.0-1026-oem"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5
Log from booting 5.17.0-1025-oem - this is the kernel that works
correctly.
** Attachment added: "kern.log-5.17.0-1025-oem"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641119/+files/kern.log-5.17.0-1025-oem
--
You received this bug notification because
Log from booting 6.0.0-1010-oem - non-viable due to what appears to be
an instance of
https://bugs.launchpad.net/ubuntu/kinetic/+source/linux/+bug/1995956 or
a related bug. Errors start at line 1202. The 80 minutes which it took
for this bug to surface while using Slack is the longest this machin
@tjaalton: Added logs for 1 working and 2 non-working versions. It
seems like there has been quite a lot of churn in the amdgpu driver
between 5.17 and 6.0. Hope this helps narrow down the problem commits.
--
You received this bug notification because you are a member of Kernel
Packages, which
I've confirmed that 6.1.0-1004-oem (the current version of linux-image-
oem-22.04c) does not have the screen disabling bug. I'll test for
stability in the face of amdgpu protection faults today and see what
happens.
--
You received this bug notification because you are a member of Kernel
Package
6.1.0-1004-oem worked fine in terms of stability over yesterday's work
day, with no amdgpu protection faults, but when I tried to suspend by
closing the lid at the end of the work day, I got some very strange
behaviour that I've never seen before - see video here:
https://photos.app.goo.gl/hkyy9a9U
lspci -nnvv output on ThinkPad E14 AMD Gen3.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641903/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Public bug reported:
Please update the ena driver in the default AWS images to 2.10.x or
later. This is to enable use of the PTP hardware clock (PHC) for high
resolution timekeeping. https://github.com/amzn/amzn-
drivers/tree/master/kernel/linux/ena#ptp-hardware-clock-phc
Ideally it would be ac
Unfortunately, the 5.17.0-2026.27 kernel removing commit
d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a did not resolve the problem -
it exhibits the same display blanking characteristics on the ThinkPad
L14 Gen3 AMD as the signed release 5.17.0-1026-oem does. Boot log for
this kernel attached.
** Atta
@acelankao: Thanks very much! Confirmed that your test kernel fixes the
screen blanking problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen
49 matches
Mail list logo
