Public bug reported:
I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
for conference calls, hangouts, etc.
Yesterday (and ever since I bought the device) I was able to use this
device for audio output and input on Xenial.
Today, after upgrading to Bionic, I am no longer abl
Hey Mao, Is this visible after install?
In other words can you install 16.04 on the failing system, then add the
4.15 kernel and boot into it?
Once you do that, does the issue appear?
Just to summarize where we are:
16.04, 4.13: No problem
18.04, 4.15: Problem with frame buffer
16.04, 4.15: ???
** Also affects: linux (Ubuntu)
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/1762940
Title:
Ubuntu 18.04 install screen becomes blur on Huaw
It looks like this happened perhaps sometime between 4.10 and 4.13:
4.4.0-112:
https://certification.canonical.com/hardware/201802-26096/submission/127640/
Driver: ixgbe (ver: 4.2.1-k)
Shows proper speed for both ports
4.10.0-42:
https://certification.canonical.com/hardware/201712-26025/submiss
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
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
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
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'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
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
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
** 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
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
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:/
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
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
** 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
** 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
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
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
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
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:
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:
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
** 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, 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
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 (
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
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
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: "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: "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
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: "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
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
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
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
** 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
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
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
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
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
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
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
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 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
OK, I have a Firestone available, so I'm re-trying this with a cycle of
10 runs to see what happens. Currently using 16.04 w/ HWE-Edge (4.10)
** Changed in: plainbox-provider-checkbox
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: plainbox-provider-checkbox
M
Call it pebkac. It's possible I missed the package when I manually
updated the qemu-* packages.
--
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/1656112
Title:
Power S822LC (8335-GTB) fai
OK, THAT worked. Sorry for the worry. I have no idea why qemu-system-
ppc was skipped over when I upgraded everything, but I did retry and
indeed it does now pass the virt test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
So I thought that was a bit weird, so look below:
First, I wanted to see what was installed:
ubuntu@fesenkov:~$ apt-cache policy qemu-system-ppc*
qemu-system-ppcemb:
Installed: (none)
Candidate: (none)
Version table:
qemu-system-ppc: ###this is what I had installed, and I'm not entirely sure
I've tested the updated qemu in proposed and it fails.
ubuntu@fesenkov:~$ sudo qemu-system-ppc64 -m 1024 -display none -nographic -net
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm
-machine pseries,usb=off -cpu host -drive
file=/home/ubuntu/xenial-server-cloudimg-
ubuntu@fesenkov:~$ dpkg -l |grep qemu | awk '{print $2"\t\t"$3}'
ipxe-qemu 1.0.0+git-20150424.a25a16d-1ubuntu1
qemu-block-extra:ppc64el 1:2.5+dfsg-5ubuntu10.13
qemu-slof 20151103+dfsg-1ubuntu1
qemu-system 1:2.5+dfsg-5ubuntu10.13
qemu-system-arm
Additionally, as noted above, qemu-block-extra modules fail to load:
Failed to initialize module: /usr/lib/powerpc64le-linux-gnu/qemu/block-iscsi.so
Note: only modules from the same build can be loaded.
Failed to initialize module: /usr/lib/powerpc64le-linux-gnu/qemu/block-curl.so
Note: only modul
Due to security cert work, we won't be able to get to this until next
week. I've got this on my list to test out on Monday.
--
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/1656112
Title:
** 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
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: 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
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
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
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
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
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
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
** 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
** 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
OK, this isn't a problem with the test tools... I'm not positive if this
is a kernel issue, or a lshw issue, but thanks to PKs attachments, I've
been able to manually and programmatically parse the outputs for 'lshw
-json' and 'lshw -C system' and both parse correctly and both scripts
work when mod
** Changed in: plainbox-provider-checkbox
Status: Incomplete => Invalid
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lshw (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
u/+source/linux/+bug/1610320/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main;
> status=Confirmed; importance=High; assignee=None;
> Launchpad-Bug-Tags: apport-bug arm64 blocks-hwcert-server kernel-da-key
Just an additional data point, I ran this test (using Mike's script in a
loop) on other architectures:
amd64 bare metal: 30 times 4.4.0, no failures
amd64 virtual machine: 30 times, 4.4.0, no failures
s390 4GB RAM: 40 times on both 4.4.0-31 and 4.7.0, no failures
s390 20GB RAM: 40 times on both 4
ux
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1610320/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; source
So running the upstream 4.7.0 kernel and had 0 failures out of 31 runs
so it's pretty safe to assume that this isn't an affect upstream.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
This appears to reliably happen with the bigheap test on ARM64. I've
tried two systems and both lock up shortly after the bigheap test
begins.
This may need some input from @cking as stress-ng is his test.
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Running the certification memory test using stress-ng on an ARM64 system
with 64GB roughly of RAM (MAAS shows 63GB).
The test runs several stress-ng memory related tests. It appears that
the system locks up when the bigheap test runs, every time so far (two
of two runs have
I've removed you. I'm not positive this is a kernel bug so much as an
issue with this specific issue. I'm hoping HP can test this same model
and CPU and let us know if the issue is reproducible on a similar
system.
** Changed in: linux (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unas
Pretty sure this was resolved by GA... should this be marked invalid or
some other status to reflect this?
** Tags removed: blocks-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/b
** Tags removed: blocks-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/1550481
Title:
hpsa driver causing kernel panics on HP ProLiant DL385p Gen8
Status in linux package
-tomt bladernr colin-king janitor
> jefleung samantha-jian
> Launchpad-Bug-Reporter: Samantha Jian-Pielak (samantha-jian)
> Launchpad-Bug-Modifier: Colin Ian King (colin-king)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: bladernr
--
"Entropy isn'
*** This bug is a duplicate of bug 1578022 ***
https://bugs.launchpad.net/bugs/1578022
** This bug has been marked a duplicate of bug 1578022
dmidecode fails to output smibios 3.0 info
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
*** This bug is a duplicate of bug 1578022 ***
https://bugs.launchpad.net/bugs/1578022
** This bug is no longer a duplicate of bug 1577183
dmidecode error on MacBook Pro: map beyond end of file
** This bug has been marked a duplicate of bug 1578022
dmidecode fails to output smibios 3.0 i
Can this also be SRUd to Trusty?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1578022
Title:
dmidecode fails to output smibios 3.0 info
Status in dmidecode package in Ubuntu:
Fi
*** This bug is a duplicate of bug 1577183 ***
https://bugs.launchpad.net/bugs/1577183
** This bug has been marked a duplicate of bug 1577183
dmidecode error on MacBook Pro: map beyond end of file
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: dmidecode (Ubuntu)
Importance: Undecided => High
** Changed in: dmidecode (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1577
We found this during certification testing of a couple models from one
OEM that apparently use SMIBIOS 3.0.
The failed test shows this in the output:
mmap: Can't map beyond end of file /sys/firmware/dmi/tables/DMI
Table is unreachable, sorry.
*** Incorrect or unknown server chassis type!
Failed
Per Narinder:
Also on DL385p Gen8 is reported the kernel hang and storage controller in soft
lock up mode with 14.4.4 and 16.04 images. And i believe it is hpsa driver
error which is soft locking. I told HP team to look into it as HP owns the hpsa
driver.
So there's more than just the CPU time
Public bug reported:
This seems to be a regression from Wily. I previously had Wily
installed on this Macbook Air and noticed no issues with network
connectivity.
Yesterday I upgraded to Xenial and networking has been unreliable ever
since. It seems to be OK after booting, but after a while of
It's not really a kernel issue, it's an issue in whatever bits in
Unity?? that set the system/calendar time (e.g. the Date/Time settings).
I filed generically against Ubuntu because I coudn't find a name for the
appropriate piece of UserSpace that does this (I failed at name
searching).
--
You r
Public bug reported:
See attached screenshot of the configs. Despite the fact that it is
configured to update the time based on location, this simply does not
work. I always have to manually re-configure the system time to the
correct current timezone.
This is rather annoying. Even Google Cale
The current firmware on this box is A28 02/06/2014 (not sure exactly
what that corresponds to just yet, the HP website is less than
forthcoming on firmware updates so far).
You'd mentioned getting one of our firmware devs to take a look would
you prefer I hold off on updating this system until the
ports-modules-4.4.0-18-generic N/A
>linux-firmware1.157
> RfKill: Error: [Errno 2] No such file or directory
> Tags: xenial
> Uname: Linux 4.4.0-18-generic s390x
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: ad
Whoops, set it to New, not Confirmed, that triggered your bot again.
** 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/157
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1572347/+attachment/4640316/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1572347/+attachment/4640312/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1572347/+attachment/4640314/+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
Looks to me like apport-collect just submitted the exact same logs as
ubuntu-bug did. Your bot may be broken...
--
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/1572347
Title:
problems wi
501 - 600 of 682 matches
Mail list logo
