Marked all tasks invalid. It's been over 2 years and no further update
from the tester who reported this initially. One can only presume it's
been resolved by some update to the kernel, or was not kernel related
and resolved itself by other means. If this appears again, we'll open a
fresh bug.
Note for investigation: Is it possible that the kenrel and initrd boot
media are not updated and thus you're seeing the Carlsville NIC problem
with old initrd? This could mean we need to rebuild initrd and push that
to the stream?
--
You received this bug notification because you are a member of
Thanks, yes, MAAS will sync using a nightly cron job, I just wasn't
quite sure how often that happens so I had to ask.
** Summary changed:
- [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
+ [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after
images u
Jonas, Billy, Alec: Can you provide me the output of the following:
$ ls -l /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily
$ sha256sum
/var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/*
I suspect I know what the answers will be, but I want to verify
Thanks Lee... I think there are two different issues that need to be
resolved.
First, is that we recently introduced patches to the 5.4 kernel for
Intel x710 NICs because 5.4 only saw some of the NIC ports. So to solve
that problem, we would need new maas images spun that include the latest
5.4 k
Sreekanth, what's the target upstream kernel version for this feature?
Just want to get a feel for the timing. As you've already submitted
these upstream, getting them into 21.04 should be no problem at all.
Also, do you expect (or desire) us to pull these back into 5.4 at some
point, or are you
Patch exists upstream in 5.9. So Hirsute should be good, will need backport for
Groovy and Focal.
** Project changed: kernel-sru-workflow => linux (Ubuntu)
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance:
At this point, this is not a problem I can fix. It's very much tied to
their hardware, and to the kernel on that hardware. This is the only
instance of this I have ever seen, anywhere, over literally thousands of
test runs, and it is very easily reproduced manually by simply catting
the efi varia
** Summary changed:
- secure boot test locks machine up
+ Catting the SecureBoot efivar in /sys hangs
--
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/1896119
Title:
Catting the SecureBoo
ider-checkbox
Status: Incomplete => Fix Committed
** Changed in: plainbox-provider-checkbox
Status: Fix Committed => In Progress
** Changed in: plainbox-provider-checkbox
Importance: Undecided => Medium
** Changed in: plainbox-provider-checkbox
Assignee: (unassigned)
For context, the update from the customer was that
cat /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-
00e098032b8c
actually works fine UNTIL he runs the cert suite, after which point it
hangs.
So I wonder if not properly closing the file leaves this in a bad state
somehow once the
** Changed in: plainbox-provider-checkbox
Status: In Progress => Fix Committed
--
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/1896119
Title:
Catting the SecureBoot efivar in /sys
** Tags added: ubuntu-certified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1878147
Title:
Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects
unsolicitedly when B
** Tags added: ubuntu-certified
--
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/1872351
Title:
Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-
AC [1a56:143a]: Disa
** Tags added: ubuntu-certified
--
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/1872034
Title:
[Focal] No HDMI output through thunderbolt docking station
Status in OEM Priority Project:
** Tags added: ubuntu-certified
--
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/1864527
Title:
CPU0 is busy after S3 in Dell Precision 3530
Status in linux package in Ubuntu:
Fix Relea
** Tags added: ubuntu-certified
--
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/1864392
Title:
Intel WiFi [8086:02f0] subsystem [8086:0030] not working
Status in linux package in Ubuntu:
** Tags added: ubuntu-certified
--
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/1868551
Title:
Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
i915_active_acquire
** Tags added: ubuntu-certified
--
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/1851749
Title:
Frequently getting thermal warnings and cpu throttling messages in
syslog
Status in linux
** Tags added: ubuntu-certified
--
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/1766076
Title:
USB over thunderbolt turns off every once in a while
Status in Dell Sputnik:
New
Status i
** Tags added: ubuntu-certified
--
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/1861359
Title:
swap storms kills interactive use
Status in linux package in Ubuntu:
Fix Released
Status
** Tags added: ubuntu-certified
--
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/1872001
Title:
5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Status in linux package in Ubun
*** This bug is a duplicate of bug 1826125 ***
https://bugs.launchpad.net/bugs/1826125
** Tags added: ubuntu-certified
--
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/1855608
Title:
** Tags added: ubuntu-certified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1872383
Title:
blk_update_request error when mount nvme partition
Status in HWE Next:
New
Status
** Tags added: ubuntu-certified
--
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/1845677
Title:
volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1
Carbon 7th gen
Statu
** Changed in: plainbox-provider-checkbox (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1757143
Title:
/proc/modules has Null refer
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Opinion
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification beca
** 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.
https://bugs.launchpad.net/bugs/1904848
Title:
Ubuntu 18.04- call trace in kernel buffer when unloadin
So I did this on 4.4 on ppc64le with 32GB RAM and 96GB Swap:
ubuntu@entei:~$ free -lm
totalusedfree shared buff/cache available
Mem: 32565 656 30603 21304 30503
Low: 325651961 30603
High:
Also retried on amd64 and the effect was the same:
ubuntu@xwing:~$ free -lm
totalusedfree shared buff/cache available
Mem: 3838 1203601 0 1153510
Low: 3838 2363601
High:
Given that, I'm marking the kernel tasks as invalid as this appears to
be stress-ng being over aggressive.
MAAS deployments (and I presume server installs in general) only provide
about 4 - 8GB swap max in a swap file created in the root filesystem (no
swap partition anymore).
It is not reasonabl
Because of the above, I've re-opened the kernel tasks :(
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack stressors on a
I'm not able to recreate this on a smaller generic amd64 machine:
ubuntu@xwing:~$ free
totalusedfree shared buff/cache available
Mem:3930172 133912 33192006124 477060 3500044
Swap: 100040060 0 100040060
ubuntu
I'm still able to trigger problems with the "stack" stressor on the Xeon
Phi...
ubuntu@lalande:~$ sudo ./memory_stress_ng
Total memory is 63 GiB
Constant run time is 300 seconds per stressor
Variable run time is 930 seconds per stressor
Estimated total run time is 20 minutes
Running stress-ng st
** Tags added: hwcert-server
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack stressors on all
arches.
Status in Stre
** Package changed: checkbox (Ubuntu) => checkbox-support (Ubuntu)
--
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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being de
** Package changed: ubuntu => linux (Ubuntu)
--
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/1757191
Title:
Intel NICs not properly reporting link speed in SysFS in Xenial
Status in linu
nbox-provider-resource-generic/bin/module_resource",
line 49, in get_module
"offset": int(offset, 16)}
ValueError: invalid literal for int() with base 16: '0x'
result file is attached to the ticket, as well as the console log ...
** Changed in: plainbox-pr
After chatting with xnox on IRC, he discovered that the output of
catting /proc/modules in 4.15 now depends on who is doing the catting.
So `cat /proc/modules` as a normal user will return null references
while `sudo cat /proc/modules` will return the actual memory offsets,
accurately.
For exampl
I'm going to go ahead and mark the kernel task as invalid as the
workaround is to read /proc/modules as root.
** Merge proposal linked:
https://code.launchpad.net/~bladernr/plainbox-provider-resource/+git/plainbox-provider-resource/+merge/341752
** Changed in: plainbox-provider-checkbox (Ubu
Public bug reported:
This was discovered while investigating tracebacks in the cert suite.
We have a script that parses /proc/modules and returns the information
in a more human-readable format as part of the info gathering we do
during cert testing.
On 4.13 and older kernels, this script was run
I tried 4.16 and the behaviour there seems to follow the old
experiences:
ubuntu@xwing:~$ uname -a
Linux xwing 4.16.0-041600rc6-generic #201803182230 SMP Mon Mar 19 02:32:18 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@xwing:~$ cat /proc/modules |grep megaraid
megaraid_sas 139264 2 - Live 0x000
Hi Joeseph,
I tried 4.15.12 mainline and it also does not have the null reference
problem:
ubuntu@xwing:~$ uname -r
4.15.12-041512-generic
ubuntu@xwing:~$ cat /proc/modules |grep multipath
multipath 16384 0 - Live 0x
ubuntu@xwing:~$ sudo cat /proc/modules |grep multipath
multipath
Hi Joeseph, I got the tester to try 4.16 and the tests still fail for
the same reason. This is the test output indicating that
/sys/class/net/DEVICENAME/speed still reports a -1 for the second port.
ERROR:root:Detected link speed (-1) is lower than detected max speed (1)
ERROR:root:Check your
Public bug reported:
I'm trying to deploy Bionic on a MAAS node today and this is failing
with the following dependency errors in the logs. The node in question
is booting in EFI mode with Secure Boot enabled.
curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1)
third party drivers
Marking this as Invalid. I've tried a few more times and have been
unable to reproduce this myself, so I'm going to chalk it up to
"incompatible bit-registration operators" (Per the BOFH excuses
generator).
If this happens again, I'll revisit it at that time, but for now, the issues
seem resolve
Moved this to a kernel bug as these are driver patches that go into the
kernel, not the open-iscsi package.
** Package changed: open-iscsi (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
This is a feature request, logs for debugging are not necessary.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes
+ [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA sup
Public bug reported:
During regression testing on a z/VM instance, I noticed call traces
being dumped to dmesg that seem to be related to stress-ng.
The stress-ng invocation we're using is:
stress-ng --aggressive --verify --timeout $runtime \
--metrics-brief --tz
I'm also not sure why we're hitting the OOM killer either, the memory
config is light, but not light enough that we'd trigger this sort of
thing on other systems, perhaps its s390x specific:
ubuntu@hwe0008:~$ free -m
totalusedfree shared buff/cache available
M
It's possible these are just OOMkiller related, but the first few call
traces seem centered around snapd and I don't notice any OOMKiller
messages until towards the end of the dmesg log.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003081/+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:
During regression testing on a z/VM instance, I noticed call traces
being dumped to dmesg that seem to be related to stress-ng.
The stress-ng invocation we're using is:
stress-ng --aggressive --verify --timeout
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003079/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003082/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003083/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003085/+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/1729878
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003080/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003084/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1729878/+attachment/5003086/+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
Fix your bot, guys... it tells me logs are missing and to run apport-
collect which just collects the exact same logs ubuntu-bug collected the
first time.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
On Fri, Nov 3, 2017 at 1:13 PM, Joseph Salisbury
wrote:
> Do you know which prior kernels did not exhibit this bug? Was it 4.12
> or earlier?
I "think" it happened with 4.10 as well, but I'm not positive, I ran
some tests before realizing I was still on 17.04 and upgrading the VM
to 17.10.
> Co
So over the weekend, I retried with 4.14.0-041400rc6-generic (since
rc7 was not successfully built when I tried this).
This too ended with call traces in the kernel log after runs of stress-
ng.
I only ran our memory stress and system-wide CPU stress tests, both
tests indicated that they passed (
Ok, so a little bit further. This seems to be that stress-ng is
triggering OOMkiller which I'm not sure it should be, unless it's just
really writing a LOT of data to memory.
My setup has been the same on all architectures and I've seen the same
behaviour on Artful deployments on amd64 (Xeon Phi)
The call that invokes stress-ng looks like this:
timeout -s 14 $end_time stress-ng -k --aggressive --verify --timeout
$runtime --$1 0
Where $end_time is the max time before killing stress-ng IF stress-ng
runs longer than the --timeout value. $1, is the stressor invoked, and
as I said above, we r
** Summary changed:
- stress-ng triggering call-traces on s390x z/VM instances
+ stress-ng triggering oomkiller running brk and stack stressors on all arches.
** Also affects: stress-ng
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Ok, I've narrowed it down to the brk and stack stressors in stress-ng.
I've recreated this on amd64, ppc64el and s390x across 4.4, 4.10 and
4.13 kernels.
Stress-NG reports the tests as successful so I guess now the only thing
remaining is to confirm that hitting OOM killer is expected behaviour
wh
resetting all the tasks to confirmed, rather than Incomplete as I've
tested and am still waiting for a resolution or whatever.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (U
** Changed in: plainbox-provider-checkbox
Status: Confirmed => Fix Committed
--
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/1573062
Title:
memory_stress_ng failing for Power archi
** Also affects: stress-ng
Importance: Undecided
Status: New
--
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/1652132
Title:
Call trace when testing fstat stressor on ppc64el wit
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
FYI, Added stress-ng task as a specific test case in that tool is
exposing this issue. Just want to be sure this is not a test tool issue
instead of a legit kernel issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
OK... so I tried three runs of the stress-ng memory test (that has been
used successfully on every other system we certify for 16.04) and so
far, two of three runs have resulted in the system locking up and a
bunch of stack trace data dumped to console.
In both cases, I had to power cycle the syst
in: plainbox-provider-checkbox
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: ubuntu-z-systems
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Ok, so we're now using stress-ng 0.07.21 which resolved a lot of issues
and have also adopted Colin's suggestions into our wrapper script to
modify how stress-ng is being called and culled.
This seems to resolve the problems that led to this.
** Also affects: plainbox-provider-checkbox
Importa
** Changed in: plainbox-provider-checkbox
Milestone: 0.36.0 => 0.35.0
--
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/1573062
Title:
memory_stress_ng failing for Power architecture fo
The important bits of udev seem to be these:
P: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
E: DEVPATH=/devices/pci0008:00/0008:00:00.0/0008:01:00.0
E: DRIVER=mlx4_core
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_
** Changed in: checkbox (Ubuntu)
Status: Incomplete => In Progress
--
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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not b
Also verified that the SRU resolves the issue on the previously failing
hardware (POWER8NVL).
This was tested on Xenial w/ 4.4 kernel
Can we set the Ubuntu and Xenial tasks to Fix Released now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
I have a Skylake Core i7 system running up-to-date 16.04.1 (4.4 kernel).
Whenever I issue a halt (either shutdown -h now, or halt) the shutdown
process gets as far as showing the "Target shutdown reached" on the
console, but instead of actually powering the system down, it ju
On Fri, Jul 14, 2017 at 9:25 AM, Joseph Salisbury
wrote:
> Did this issue start happening after an update/upgrade?
No, it's done this as long as I've had the machine (It's home-built,
not an OEM designed system). 16.04 GA was the first OS on it and the
soft-power-off stuff has never worked on it
So tested it, it works in 4.12, and 4.10 and 4.8. something else is
going on though, I think I was just not patient enough, but IMO the
power off shouldn't take 5 minutes to accomplish.
So where I thought the power off just wasn't happening, I was incorrect,
it does happen, it just took several m
Going to mark this as invalid for now, as the bug doesn't capture the
root cause. I'll try to dig into this at a later date and raise a more
appropriate bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Abalan, Please view the bug page and at the top on the Right Hand side,
you should see a box that says the following, or something similar:
You have subscriptions that may cause you to receive notifications, but you are
not directly subscribed to this bug's notifications.
Mute bug mailMute h
Abalan, you have also subscribed to the package "Linux in Ubuntu" as
shown here:
https://bugs.launchpad.net/~fyma/+packagebugs
Because of this, you will receive bug notifications for EVERY bug filed
against "Linux". YOu will need to unsubscribe from this package if you
do not wish to receive th
FWIW, I have run this on a Xeon Phi system and not reproduced the
failure using stress-ng 0.07.16 (built in our PPA for Xenial).
This appears to have an AMI fake keyboard and mouse as the Power system that
fails does.
Bus 003 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and
Note, the above comment was validated on a Fujitsu CX1640 Xeon Phi system with
Xenial and the stock ubuntu kernel:
Linux cx1640-1 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
P
Also note, both the Intel and AMD boxes were tested with the same kernel
and the TSC clocksource in use. I tried HPET on the AMD box as well but
it didn't make any difference.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Public bug reported:
Discovered this while doing pre-release certification testing for 16.04
on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core CPU.
I have some code that essentially does this: And note, I am NOT a C
programmer, I know enough C to read it and do some minor things, and
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619532/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619529/+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/1564949
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619534/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619528/+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/1564949
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619530/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619531/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619526/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1564949/+attachment/4619527/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
** Tags added: hwcert-server
--
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/1564949
Title:
Severe latency/skew on AMD Opetron processor
Status in linux package in Ubuntu:
Confirmed
B
apport information
** Tags added: apport-collected uec-images xenial
** Description changed:
Discovered this while doing pre-release certification testing for 16.04
on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core CPU.
I have some code that essentially does this: And note,
201 - 300 of 692 matches
Mail list logo
