definitely. If I sudo reboot, I get black screen and no boot. If I
power off the machine and boot, it works.
Could be the RC kernel.
--
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/170065
@CoolStar You have to change the bios to AHCI for the USB thumbdrive
install image to boot. At least for me. I mean, we all have the same
Yoga 720 15" laptop, right?
I didn't want to toast my Windows 10 install, so I resized the Windows
partition to 1/2, leaving 1/2 for Ubuntu.
The instructions
@CoolStar nothing to do.
https://github.com/torvalds/linux/pull/444
@Hoeze made the PR already.
--
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/1700657
Title:
Touchpad not detected in L
I must say the 720 is zippy to use. It took me 36-38 minutes to do a
complete kernel build. apt-et update/upgrade takes just a few seconds.
At least with KDE (other desktops may vary), I was able to adjust the
font sizes, and other window decorations and the like to make the
environment look grea
@kaihengfeng
Can you please assure this gets in the queue to get merged into master?
The file in question hasn't been changed since early July, so not
merged. It would be awesome to not have to build custom kernels all the
time the kernel needs to be updated.
--
You received this bug notifica
Public bug reported:
There's just a 1 line patch required, to add an initializer to array of
structs scanned to match up the device ID with driver.
The PR is here:
https://github.com/torvalds/linux/pull/444#discussion_r131229815
I've applied the patch and created and booted from a custom kernel
I searched the WWW for any kind of solution to the trackpad not being
recognized. There are several months of similar questions, but no
resolution. Until this patch was made public/known.
Further discussion here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700657
--
You received thi
No.
The laptop is a 2017 model. The source file in question simply doesn't
have an array element that describes/identifies the trackpad. My
assumption is that the driver maintainer simply hasn't seen a device
with this ID before.
I would be happy to test the latest kernel, but I don;'t see the
Sorry, to answer the first question, the latest kernels do boot on the
machine, the trackpad isn't recognized and doesn't respond to anything
at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
I changed it to confirmed, although I am the reporter.
I found the patch is missing in the ubuntu kernel source:
https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git
/mainline-crack/tree/drivers/mfd/intel-lpss-pci.c
--
You received this bug notification because you are a memb
The bug exists upstream in 4.13-rc4
** Tags added: kernel-bug-exists-upstream
** 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.n
Please do use my email or name, etc.
B
--
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/1700657
Title:
Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
Status in Linux:
Unknow
The title of the email might be better to include the directory path to
the file, and a brief description.
Use the body of the email to mention Lenovo.
I assume you already got that feedback...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Posting because I ran into what I feel is the same problem between
4.8.0-52 and 4.8.0-53.
4x large login screen... no mouse... no touchpad. Could login. Desktop
4x large. Took me a while to find this thread (had been trying
unsuccessfully to catch GRUB-2 Menu with Shift key, also):
https://ubuntuf
After a few days of uptime I still saw issues with the ratio set to 100.
I'll give 0 a try.
--
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/183
Title:
Default VM overcommit sysctls in
We still have not received the machine back from IBM.
--
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) failes KVM guest cert test with kvm_init_vcpu
We received the hardware back and have started testing all blockers
again. The latest test of the above mentioned PPA did not yield positive
results:
"Unable to find PowerPC CPU definition"
$ apt-cache policy qemu-system-ppc
qemu-system-ppc:
Installed: 1:2.5+dfsg-5ubuntu10.10
Candidate: 1:2.5
Just to be sure I installed qemu-system-ppc version 1:2.6.1+dfsg-
0ubuntu5.3 from yakkety-updates and the tests pass.
--
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
This issue, or similar symptoms doesn't seem to be fixed. This is with
stock kernel, stock stress-ng but with the suggested changes to the
memory_stress_ng test script. The machine locks up completely maybe 1
out of 5-10 runs. See attached dmesg for errors.
Kernel: 4.4.0-64-generic-85-Ubuntu
stres
Public bug reported:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmP
** Also affects: checkbox (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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC
kernel 4.11.0-041100rc3-generic failed with the same symptoms.
--
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 detect
** Summary changed:
- Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed:
Invalid argument
+ Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed:
Invalid argument
--
You received this bug notification because you are a member of Kernel
Packages
** Changed in: qemu (Ubuntu)
Status: Fix Released => 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/1656112
Title:
Power S822LC (8335-GTB) fails KVM guest cert test wi
** Changed in: plainbox-provider-checkbox
Status: Fix Released => Confirmed
** Changed in: plainbox-provider-checkbox
Assignee: Mike Rushton (leftyfb) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Public bug reported:
After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
brought up and assigned an ip via MAAS. This is where functionality
stops on this kernel. Pinging the MAAS server which is connected
directly
linux-image-4.10.6-041006 has also failed.
--
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/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
Stat
4.8.0-45.48~16.04.1 from xenial updates 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/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
S
4.4.0-71-generic is tested as working now.
--
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/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
Stat
I tested 4.4.0-72 from above and got the same results as 4.4.0-71.
In the process of testing 4.4.0-71 more, I found all is not as well as
we assumed. At first deployment everything seems to be fine. And after
most reboots, we are still able to ping across both interfaces. But
bringing interfaces u
I have tested the qemu-system-ppc package from both PPA's and both work
without issue.
--
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) fails KVM gue
Public bug reported:
I recently replaced some Xenial servers, and started experiencing "Out
of memory" problems with the default kernel.
We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
e6b58e85, in ap-southeast-2, from https://cloud-
images.ubuntu.com/locator/ec2/). Previous
Public bug reported:
Upon running the virtualization test from the certification test suite,
the kvm guest test fails with the following error:
kvm_init_vcpu failed: Invalid argument
This same test works on multiple other IBM Power 8 and Openpower
servers. kvm-ok tells us that kvm virtualization
This test has been run dozens of times across multiple machines and
deployments and reboots. It is completely reproducible.
--
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:
As mentioned above, I have run the test multiple times with SMT both
enabled and disabled. I get the same error. This is from running the
test just now with SMT disabled:
WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
Automatically detecting the format is
Thanks jsalisbury. We have deployed using your test kernel (from
http://kernel.ubuntu.com/~jsalisbury/lp1655842/), and experienced no OOM
issues.
--
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
4.10 RC3 gives a kernel panic:
[3.863436] ahci 0009:04:00.0: AHCI 0001. 32 slots 4 ports 6 Gbps 0xf
impl SATA mode
[3.863631] ahci 0009:04:00.0: flags: 64bit ncq sntf led only pmp fbs pio
slum part sxs
[3.864221] scsi host0: ahci
[3.864404] scsi host1: ahci
[3.864562] sc
KVM was never tested successfully on this particular model. The
virtualization test works fine on all other open power servers we have
in the labs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Cascardo: we've tried your test kernel, and it looks good - we've seen
no OOM problems.
--
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/1655842
Title:
"Out of memory" errors after upgrade
In my testing, only qemu-system-ppc version 1:2.6.1+dfsg-0ubuntu5.2
available in yakkety and the template to set -cpu POWER8NVL was needed
to resolve the issue. No kernel patches were necessary.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Merge proposal linked:
https://code.launchpad.net/~leftyfb/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/315823
--
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/165
@Christian The branch is for a fix in the plainbox-provider-checkbox
package which is part of the certification suite. It is not for qemu-
system-ppc but is a necessary part of the overall fix since the script
was originally assuming POWER8.
--
You received this bug notification because you are a
For about the last month I have encountered this error. While /boot does
appear to be full it is only after the update starts generating images
that it can't find. Running "sudo apt-get autoremove" will do the same
thing:
Reading package lists... Done
Building dependency tree
Reading state
Thank you Seth, that seemed to work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1658839
Title:
package linux-firmware 1.127.23 failed to install/upgrade: subprocess
instal
@Christian
The qemu fix is still necessary in order to resolve the issue.
While I do have access to the hardware, it is currently having issues
booting. Once we resolve the issue with IBM, I plan on testing out the
qemu fix from the PPA.
--
You received this bug notification because you are a m
@paelzer the machine was sent out for repair/replacement. We expect it
to return later this week. I will test the package from the above PPA as
soon as it is back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
I'm pretty sure this bug was introduced in 4.4.0-58, even though I
reported it against 4.4.0-59. Still, +1 for a raising a separate bug
against 4.8.
Thanks to Cascardo for fixing this one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Public bug reported:
On my system, running a couple of LXD containers and VMs (16 GB RAM, 16
GB swap) seems to cause the kernel oom-killer to be frequently
triggered.
In order to try to resolve this, first I tried limiting the memory my
containers were allowed to use, such as by using:
lxc c
Changing status to "Confirmed". I don't think there are any relevant
logs for this issue. Here's some anecdotal evidence, though:
# dmesg | grep oom-killer
[1389379.248406] apt-mirror invoked oom-killer: gfp_mask=0x26000c0, order=2,
oom_score_adj=0
[1399428.772409] chrome invoked oom-killer: gfp_
Hm. Oddly enough, pulseaudio seemed to have problems for me until I set
the overcommit ratio higher (to 150).
--
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/183
Title:
Default VM ove
Public bug reported:
Ubuntu 12.04.5, ASUS model 1015E, x86_64
When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much never
get a working display manager. (I think it booted okay the first time
after installing the kernel, but that's it.) Usually I just get a black
display. I have al
I ran "apport-collect 1553626", but it appeared to hang. (After an
hour, it was still saying "Collecting problem information".)
I poked around a bit while it was running. Here's some ps output in
case it's useful:
camomile$ ps -t pts/1
PID TTY TIME CMD
1757 pts/100:00:00 bash
1
I booted the -98 kernel, enabled wireless in Network Manager, and then
booted the -99 kernel. I'm afraid apport-collect still stalls, and I
still see rfkill stuck in D+ state.
So, I can manually attach files from /var/log. Or I could try running
apport-collect with the -98 kernel running. Let m
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594525/+files/CRDA.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/1553626
Ti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594527/+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
** Tags added: apport-collected xenial
** Description changed:
Ubuntu 12.04.5, ASUS model 1015E, x86_64
When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much never
get a working display manager. (I think it booted okay the first time
after installing th
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594526/+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/1553626/+attachment/4594528/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594536/+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/1553626
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594533/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594534/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594529/+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/1553626
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594532/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594535/+files/RfKill.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/1553626
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594531/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594530/+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/1553626
apport-collect has been run as requested. And FWIW, the live image
console worked just fine (no need to ssh in to run apport-collect).
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594537/+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
I don't need a backport, so closing as requested.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1553626
Title:
blank
Public bug reported:
(Note that the attached logs are not a machine exhibiting the issue)
I've observed this issue specifically on Dell's PowerEdge R410 with its
DRAC. I manage quite a few other machines with DRACs and haven't seen
this issue so it may be limited to the R410. I've seen cases of t
Sorry, I'm not super familiar with apport (our security folks make us
disable it because they get upset for reasons I don't quite grasp).
I tried to install apport and python-apport, but no dice on actually
running apport-collect.
$ apport-collect 1557172
Traceback (most recent call last):
File
Hi Joseph
I'll see if I can nab some extra hardware to try it out. Keep in mind
that I haven't found a way to reproduce this reliably yet, with our
usual setup it can take a few weeks before it happens. Basically we have
a cron job that periodically exports the state of our machines, which
include
Public bug reported:
The latest daily Xenial image for MAAS seems to lack network
connectivity. Tested with kernel version 4.4.0-15 from the 20160328
image from the daily stream
Attached are logs from the boot sequence as well as the maas deployment
logs.
** Affects: linux (Ubuntu)
Importan
** Attachment added: "sutboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615236/+files/sutboot.txt
** Description changed:
The latest daily Xenial image for MAAS seems to lack network
connectivity. Tested with kernel version 4.4.0-15 from the 20160328
** Attachment added: "clusterd.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615237/+files/clusterd.log
--
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/1
** Attachment added: "regiond.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615238/+files/regiond.log
** Summary changed:
- IBM Power8 PPC MAAS images booting with no network
+ IBM ppc64le MAAS images booting with no network
--
You received this bug notifica
Due to the nature of no network connectivity, We cannot login (curtin
preseed didn't run to setup credentials) or submit logs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Public bug reported:
After Ubuntu updated the kernel to 3.19.0-56 the touchpad stopped working.
The mouse pointer never appears and touching/dragging/clicking has no effect.
I can make it work by using the GRUB menu to boot 3.19.0-49 instead.
On the older, working, kernel xinput outputs:
⎡ Virtua
I noticed in dmesg:
Working kernel:
[3.565137] i2c_hid i2c-SYN1B7D:01: failed to retrieve report from device.
[3.565306] input: SYN1B7D:01 06CB:2991 UNKNOWN as
/devices/platform/80860F41:00/i2c-0/i2c-SYN1B7D:01/0018:06CB:2991.0001/input/input8
[3.565618] hid-multitouch 0018:06CB:2991.
I noticed in dmesg:
Working kernel:
[3.565137] i2c_hid i2c-SYN1B7D:01: failed to retrieve report from device.
[3.565306] input: SYN1B7D:01 06CB:2991 UNKNOWN as
/devices/platform/80860F41:00/i2c-0/i2c-SYN1B7D:01/0018:06CB:2991.0001/input/input8
[3.565618] hid-multitouch 0018:06CB:2991.
** Attachment added: "dmesg log from 3.19.0-56, not working"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1564237/+attachment/4617903/+files/bad.dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1*2*3*4*5*6*7*
Core 1:8*9* 10* 11* 12* 13* 14* 15*
Core 2: 16* 17* 18* 19* 20* 21* 22* 23*
Core 3: 24* 25* 26* 27* 28* 29* 30* 31*
Core 4: 32* 33* 34*
ubuntu@alpine01:~$ sudo ppc64_cpu --smt=1
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1 2 3 4 5 6 7
Core 1:8*9101112131415
Core 2: 16* 17181920212223
Core 3: 24* 252627282
@serge-hallyn
ubuntu@alpine01:~/kvm$ cat /etc/issue; uname -a ; ppc64_cpu --smt
Ubuntu Xenial Xerus (development branch) \n \l
Linux alpine01 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
SMT is off
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256
@mdroth
I don't think PPC supports kvm the same way as x86:
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -enable-kvm -m 256 -display none
-nographic -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio
Sorry, I copied the wrong thing:
sudo qemu-system-ppc64 -enable-kvm -m 256 -display none -nographic -net nic
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=seed.iso,if=virtio
ioctl(KVM_CREA
The PowerVM machine I've been using for these tests has the following
output:
ubuntu@alpine01:~/kvm$ cat /proc/cpuinfo | grep platform
platform: pSeries
The PowerNV server has the following output:
ubuntu@binacle:~$ cat /etc/issue; uname -a ; ppc64_cpu --smt ; cat
/proc/cpuinfo |grep
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
PowerVM mode is an LPAR. It is not a kvm instance trying to run an KVM
within. This was also working in 14.04 without issue and is being asked
of us from IBM to certify
2. the xenial cloud images ha
I have also shown that this issue has the exact same results on PowerNV
above.
** Changed in: qemu
Status: Invalid => Confirmed
** Changed in: qemu (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Confirming marcin's bug report as well after it failed starting on a TPM error:
"A TPM error (6) occurred attempting to read a pcr value"
The only way for me to get access was to boot from previous base:
4.2.0-27-generic
--
You received this bug notification because you are a member of Kernel
Pa
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Wily)
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/bug
@Serge, A workaround for me is to use "hypervisor default" in virt-
manager. I'm not sure what the equivalent is in virt-install, but maybe
using --cpu=host-model-only would be a workaround?
>From the man page:
Expose the host CPUs configuration to the guest. This enables
the gue
Public bug reported:
The underlying kernel bug was originally reported and fixed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609
The bug was fixed confirmed not present in the original trusty kernel
and has been fixed in vivid and wily, but was not addressed in utopic as
it has
Here's the fragment of Oops I have demonstrating the crash. If I'm
understanding the versioning here, it looks like the issue may now have
been fully addressed by that patch alone? :(
[0.104000] CR2: 8807b000 CR3: 01c13000 CR4: 001406f0
[0.104000] Stack:
[0.10
*not have
--
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/1527748
Title:
lts-utopic kernel needs boot-up race condition fix.
Status in linux package in Ubuntu:
Incomplete
Bug descript
I'm on an MSI Dominator GT72 2QD, and have the wifi working by implementing the
following bug fix, but bluetooth isn't working.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184
I'm running Ubuntu 15.10, here's my specific version:
$ uname -a
Linux 4.2.0-22-generic #27-Ubuntu SMP Thu
Note: I ask about the qa for luks, as this is about the third time in
memory since 8.xx days luks has been suddenly broken with an update. No
one that tests the kernels seems to use disk encryption or understand it
to ensure this works consistently.
--
You received this bug notification because
Wow, I installed a 3.19 kernel today on 14.04, and suddenly found I
couldn't type my disk encryption password. Then I found it was non-
trivial to actually get into the non-hidden grub menu as holding shift
did not work apparently from my bios.
Why is this *still* an issue? Does no one at canon
The tests run manually above were NOT run as root. The test during
certification does run as root. I have run the test as root and as the
ubuntu user, both with the same results.
Also, as shown above, this test ran fine manually while running Ubuntu
14.04 without root and during proper certificati
Hi, sorry for the lack of update. In the meantime I've seen reports of a
few cases of this on actual desktops and laptops, so the workaround of
disabling the usbhid dirver via udev isn't really an option there :)
Our setup relies on a handful of out-of-tree modules that don't seem to
build on 4.5.
501 - 600 of 1119 matches
Mail list logo
