error screen picture
** Attachment added: "error screen picuture"
https://bugs.launchpad.net/ubuntu/+bug/1877083/+attachment/5367295/+files/qemu-vnc-error-in-dashboard.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
qemu error sceen shot via virt-manager
** Attachment added: "qemu error sceen shot via virt-manager"
https://bugs.launchpad.net/ubuntu/+bug/1877083/+attachment/5367297/+files/qemu-vn-error-via-virt-manager.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
>From the arm qemu wiki:
https://wiki.qemu.org/Documentation/Platforms/ARM
vns seems works and require as:
virt machine graphics
Graphics is also available, but unlike x86 there is no default display
device enabled: you should select on from the Display devices section of
"-device ?". One good op
The commend link for qemu which created by nova compute, the vcn parameter are:
-vnc 0.0.0.0:0 -k en-us -device
virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.5,addr=0x0
ubuntu@hc3:~$ ps auxww |grep -i qemu
libvirt+ 1157628 3.6 0.1 5691124 737996 ? Sl 04:34 1:21 qemu-system-aarch64
-enable-kvm -
For 18.04.2 ga-kernel of Linux hc3 4.15.0-47-generic, the CONFIG_DRM=y
and CONFIG_DRM_VIRTIO_GPU=y seems already set. Test with drm virtio-gpu
modules load, it seems same. I tested by delete instance via dashboard
and create it again on the same hc3.maas host.
For the virt-manager still display fo
Public bug reported:
Qemu vnc console can only show "no suitable video mode" and nothing else
both on opensack dashboard (vnc) or virt-manager. This was tested on
Taishan2280 server (D05).
Please see attached screen shoot.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Y
** Attachment added: "screen shot for Installer error"
https://bugs.launchpad.net/ubuntu/+bug/1815847/+attachment/5238503/+files/16.05.5-Chinese-Language-Insall-Error.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
This error was reported by Huawei when they install 16.04 with Chinese
Language. I can re-produce it via KVM virtual machine with BIOS (not UEFI)
option as:
1. Create new KVM VM with BIOS
2. Boot Ubuntu 16.04.5 server ISO to begin install
3. Select "Chinese Language" in the
This error would disappear if not Choose Chinese Language in first
screen (F2 or grub manual screen). The UEFI boot would not provide this
option choosing too.
** Attachment added: "first screen for Language choose"
https://bugs.launchpad.net/ubuntu/+bug/1815847/+attachment/5238502/+files/Lanu
** Attachment added: "screen shot for console message of the error"
https://bugs.launchpad.net/ubuntu/+bug/1815847/+attachment/5238504/+files/16.04.05-Chines-Install-Error-Message.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One of IHV parnter get this issues too during stressapp + iperf testing.
LP#1823615
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752091
Title:
gvfsd-metadata[1703]: g_udev_device_has_property: ass
The screen also get blur after ubuntu 18.04 beta2 was installed by
legacy bios on Huawei server (VGA card is SM750 which was embedded in
Hi1710 iMBC chips). The ubuntu-destktop was installed by "apt-get
install ubuntu-desktop and init 5 to switch to x.
--
You received this bug notification becau
** Attachment added: "bure screen picture for 18.04 beta2 atfter switch to
x-window on Huawei server"
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118758/+files/creen_picture_for_blur.png
--
You received this bug notification because you are a member of
** Attachment added: "sos-report for Ubuntu 18.04 after ubuntu-desktop
installed. it also become screen blur after witch to x-window (init 5)."
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118756/+files/sosreport-2288Hv5-20180417044501.tar.xz
--
You rec
For Xenial ubuntu-deskto on Huawei server testing (UEFI), all kernel 4.4
(default) and 4.13 (hwe) and 4.15 (hwe-edge) works well (no screen
blur).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
** Attachment added: "screen shoot for xenial (16.04.4) with 4.15 kernel on
Huawei server (UEFI)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5119225/+files/xenial-4.15-kernel-gui.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "Test matrix for sceen blur on 16.04.4 with 4.4 4.13 4.15
kernel and 18.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5120230/+files/test-matrix-on-1604-1804.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "sos report for 16.04.04 with 4.15 kernel tesing (no
screen blur after enable x-window)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5120260/+files/sosreport-2288Hv5uefi16.04.44.15-20180417120113.tar.xz
--
You received this bug notification b
Today, Huawei side did x-window testing 16.04.04 in legacy BIOS model,
all 4.4,4.13(hwe),4.15(hwe-edge which as as 18.04), 4.17rc1 works fine
(no screen blur).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "x-windows test matrix for 16.04.4 with kernel
4.4,4.13,4.15,4.17"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5123905/+files/blur-test0420.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Tested on 17.10 server d-i install, it would be screen blur too during
installation, the kernel is 4.13.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubuntu 18.04 d-i install scree
Tested with 18.04.1 Desktop, it wouldn't screen blur. The kernel log are
enclosed.
** Attachment added: "18.04.1 desktop install kernel log (no screen blur)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5181977/+files/kern.log-18.04.1-desktop-noblur.txt
--
You rec
In case 18.04.1 server and destop iso use same kernel of v4.15.0-29 and
the GUI works fine on destop, so the kernel should not be blamed.
In 18.04.1 server installation, if I kill bterm process of below:
/usr/bin/bterm -f /lib/unifont.bgf -l C.UTF-i /lib/debian-installer/menu
Some blur picture wo
Huawei hisilicon team thought it might be caused by hibmc_drm which are
upstream and included in v4.10 kernel for their ARM64 server. It is right.
After disable this module by:
modprobe.blacklist=hibmc_drm
In the grub whiling booting iso. The install screen blur was disappeared.
--
You receiv
Hisilicon team said this driver (hibmc_drm) are only for arm64. For X86
architecture, it need to use default driver for this SM750.
It seems we incorrectly include this model in X86.
Hisicon team have plans to fix in upstream source code which to limit
this modules configure options only to arm64
I just tested with /boot/vmlinuz-4.15.0-29-generic which from my laptop
( to replace install/vmlinuz with this file), it would be screen blur.
If I use 4.15.0-32-generic, blur would disappear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
The 16.04.5 ga-kernel wouldn't be screen blur and their syslog are
enclosed.
** Attachment added: "syslog for 16.04.5 ga-kernel which are not screen blur"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5179080/+files/syslog-16045-noblur.txt
--
You received this bug
I test 16.04.5 ga-kernel would not be screen blur but the hwe-
kernel(4.15.0-29) which is same as 18.04.1 would become screen blur.
The 16.04.5 hwe (blur) syslog are enclosed.
** Attachment added: "16.04.5 hwe-kernel (4.15.0-29) is blur"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/17
replace 18.04.1 with 4.15.0-29 kernel from my laptop (16.04) and it
would be screen blur too. The syslog are enclosed here. If I replacing
it with 4.15.0-32-generic from my laptop, it would not be screen bure on
language select screen, but the system seems hanged (died) in case I
can't switch to tt
The 18.04.1 ga-kernel (4.15.0-29) would be screen blur. The syslog are
enclosed too.
** Attachment added: "18.04.1 d-i install iso screen blur syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5179081/+files/syslog-180401-d-i-iso-blur.txt
--
You received this b
In the screen blur kernel syslog, it show below error which 16.04.5 GA kernel
don't have this error:
...
Aug 21 10:25:50 kernel: [0.589408] ACPI Exception: Could not find/resolve
named package element: LNKA (20170831/dspkginit-381)
(repeated 942 lines)
...
--
You received this bug notificat
ACPI Exception have been reported here and it seems not related to
screen blur
https://bugzilla.kernel.org/show_bug.cgi?id=198167
** Bug watch added: Linux Kernel Bug Tracker #198167
https://bugzilla.kernel.org/show_bug.cgi?id=198167
--
You received this bug notification because you are a me
This bug seems related with 4.15.0-20, the test result on UEFI model for
different combination of 16.04, 18.04 and their kernel are below:
18.04(d-i not subiquity) with 4.13 kerel: no screen blur
18.04(d-i not subiquity) with 4.15.22 kerenl: no screen blur
16.04 with 4.15.
In #18, 4.13 should replaced with 4.4.0-116 which used by 16.04.4 ISO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in
The daily build is still use 4.15.0-20 kernel. It was expecting of
update and fix this blur problem. http://cdimage.ubuntu.com/ubuntu-
server/bionic/daily/20180625/bionic-server-amd64.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have tested with 18.04.1 on Huawei FusionServer 2288 again. The screen
blure is same. The kernel of this iso have been update to
4.15.0-29-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17629
This bug seems related with the kernel or 4.15.0-20 of d-i ISO. Please
refer to #18 for test results on different kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubuntu 18.04 d-
The daily build is still use 4.15.0-20 kernel.
http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/bionic-server-amd64.iso
Anyone can confirm that the 18.04.1 d-i install iso would update the
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Hawei team just tested and verified this bug on 4.15.0-10-generic kernel
on D05 server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("
Call traces for this bug on D05 for kernel 4.15.0-10-generic which
tested on 1 March 2018 on 18.04 daily build
** Attachment added: "Call traces for this bug on D05 for kernel
4.15.0-10-generic which tested on 1 March 2018 on 18.04 daily build"
https://bugs.launchpad.net/ubuntu/+source/linux/
The below is testing after remove of "xserver-xorg-video-fbdev package"
ubuntu@ubuntu:/usr/lib/xorg/modules/drivers$ sudo /usr/lib/xorg/Xorg
X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
Current Opera
For the mainline kernel (general kernel from Ubuntu 16.04.02 AM64) was
not tested in case we are not supported for Hisilicon D05 board.
We also do some basic fbdev and modesetting testing on this kerenl by
pass Xserver, it seems works well and so we tend to think this is caused
by Xorg or driver o
,
Mao
On Wed, May 31, 2017 at 3:07 PM, Daniel Axtens
wrote:
> Hi,
>
> This is what I have figured out so far.
>
> For some reason the initial probing done by the modesetting driver
> fails. This is part of the platform device probing stage. This failure
> means the device
hi Daniel,
If tt is more easy and save time for you. I can share my ssh remote access
to you for D05 testing environment, so you can directly patching and
testing over it.
thanks,
Mao
On Wed, May 31, 2017 at 3:32 PM, Zhanglei Mao
wrote:
> hi Daniel,
>
> Thank you very much for you m
kernel.
For the new kernel install, I should be able to set it up.
thanks,
Mao
On Thu, Jun 1, 2017 at 7:56 PM, Daniel Axtens
wrote:
> Ok, so I think part of the problem is that the kernel hibmc driver needs
> to use a set_busid function from the drm core. I've simulated this
>
Ｄannie,
For new kernel building, please note that is not a our general/stand
zesty, I though Dann use a another kernel source tree or use may patches
specified for D05 board. I am not familiar with it and please contact
with Dann too.
thanks,
Mao
--
You received this bug notification because
hi Daniel,
Fantastic! I is a really good news for me.
thanks,
Mao
On Mon, Jun 5, 2017 at 12:46 PM, Daniel Axtens
wrote:
> Hi,
>
> I can get xorg working if I do these 2 things:
>
> 1) Edit memory with gdb to add "pci:" to bus id. This is what the kernel
> patc
hi Daniel,
I am not knowing it but I will check Huawei and vendor of VGA card for
it.
thanks,
Mao
On Tue, Jun 6, 2017 at 3:14 PM, Daniel Axtens
wrote:
> Hi Mao,
>
> I have looked at the PCI setup a bit more closely: the VGA card is
> behind a PCI bridge which does not a
hi Daniel,
It is nice. I thought to upstream is the responsibility of HiSilicon/HWE
team. But If you can make it upstream, it will be out of all expecting and
very nice too.
thanks,
Mao
On Wed, Jun 7, 2017 at 12:40 PM, Daniel Axtens
wrote:
> Hi Mao,
>
> I have successfully verified
hi Daniel,
Agree with you that is something they need to fix. I have sent mail to
HiSilicon and their VGA card vendors and they replied some for confirming
and understand questions or our requests. I will push them again.
thanks,
Mao
On Thu, Jun 8, 2017 at 8:41 AM, Daniel Axtens
wrote:
>
hi Danniel,
This forwarded mail are from Huawei guy which to say
"PCI_BRIDGE_CTL_VGA" are only used on X86 but not for AMR64. The English
line was my translated for Chines text.
thanks,
Mao
-- Forwarded message --
From: wanghuiqiang
Date: 2017-06-09 13:38 GMT+08:00
S
This 4.5.1 seems form "PCI-to-PCI Bridge Architecture Specification",
the full document can be download from below link:
https://cds.cern.ch/record/551427/files/cer-2308933.pdf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
hi Danniel,
This forwarded mail are from Huawei guy which to say "PCI_BRIDGE_CTL_VGA"
are only used on X86 but not for AMR64. The English line was my translated
for Chines text.
thanks,
Mao
-- Forwarded message --
From: wanghuiqiang
Date: 2017-06-09 13:38 GMT+08:00
S
s also
not suitable for ARM because ARM didn't have any IO resource in its'
initial definitions.
thanks,
Mao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691991
Title:
Xorg Segmentation fa
o you
have bug id for it? Actually, I think we can take both those 2 bugs back to
Huawei or Pearl team in case it is bugs from Kernel.
thanks,
Mao
On Fri, Jun 16, 2017 at 11:46 AM, Daniel Axtens wrote:
> Hi Mao,
>
> I have done more work on the HiSilicon board. I have talked with the
Translate from Huawei's reply mail: The sever board have only this VGA PCI
devices:
19e5 Huawei Technologies Co., Ltd.
1711 Hi1710 [iBMC Intelligent Management system chip w/VGA support]
Please check if this math to our D05 testing environment.
--
You received this bug notification
hi Danneil,
Those are translate from Huawei's reply mail:
The sever board have only this VGA PCI devices:
19e5 Huawei Technologies Co., Ltd.
1711 Hi1710 [iBMC Intelligent Management system chip w/VGA support]
Please check if this math to our D05 testing environment.
thanks,
Ma
Yes, you can close this bug now. Thank you very much for your good works
and to fix this problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691991
Title:
Xorg Segmentation fault on Hisilicon D
** Attachment added: "ubuntu-bug xorg report file"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4879485/+files/ubuntu-bug_xorg_d05_0519.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
[sudo] password for ubuntu:
X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
Current Operating System: Linux ubuntu 4.10.0-20.22-generic #2
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4879487/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691991
Title:
X
** Attachment added: "core dump of xorg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4879486/+files/_usr_lib_xorg_Xorg.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
backtrace by apport-retrace
crash buntu:/var/crash# apport-retrace --stdout
/var/crash/_usr_lib_xorg_Xorg.0.c
gpgv: Signature made Tue 01 Nov 2016 04:15:19 PM CST using RSA key ID A88984DC
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on
./xor
** Attachment added: "sosreport at 24 May 2017"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4882242/+files/sosreport-ubuntu.d05-20170524102121.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Pual Liu analyse for this bug, he provide a temporarily fix but it seems not
works (no output in monitor)
---
Hi all,
I look deep into the problem and I'm not sure if it is the kernel issue or Xorg
issue.
We might need to spend more time on this issue to t
This final goal is "Ubuntu 16.04 support x-Window by modesetting
(modesetting_drv.so) driver"
Notes: From xserver source code，it only use modeset. For the display card
hardware it is a display controller without GPU，the call paths is
xserver->modesetting_drv(userspace)->libdrm(userspace)->dr
It seems only warning. Please check if new initrd was created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693503
Title:
Remove mlx4.conf
To manage notifications about this bug go to:
https://bu
This patch have been accepted to be merged in in kernel V4.16. Please
refer to: https://lkml.org/lkml/2017/12/25/24
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738334
Title:
hisilicon hibmc regr
Public bug reported:
When test S4 on Huawei 1288H V5 server as
#echo disk>/sys/power/state
It show error of
Error taking CPU79 down: -34
Non-boot CPUs are not disabled
The echo command return with error of:
Write error: Numerical result out of range
>From the dmesg it show error of:
This S4-cpu-down-screen-show.pdf contains the testing screen shot and
dmesg of works well testing.
** Attachment added: "S4-cpu-down-failed-screen-shot.pdf"
https://bugs.launchpad.net/ubuntu/+bug/1718871/+attachment/4954913/+files/S4-cpu-down-failed-screen-shot.pdf
--
You received this bug n
For the newest upstream kernel of http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.14-rc2/linux-
image-4.14.0-041400rc2-generic_4.14.0-041400rc2.201709242031_amd64.deb.
The S4 test is same error.
tags:kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
Tested works well kernel are:
kernel 3.13.0-24-generic of 14.04
Kernel 3.13.0-031300-generic on 14.04 from
（http://kernel.ubuntu.com/~kernel-ppa/mainline/)
Tested was failed kernel are:
linux-image-4.4.0-93-generic of lasted 16.04.1
4.4.9-21-generic, 4.12.0-041200-generic,4.14.0-999-gene
Public bug reported:
The test process:
1)Put "AMD radeon pro WX7100 graphics card" on our X86 server and ARM server ;
2)Installed Ubuntu 17.10 server OS on both X86 server and ARM server with same
steps.
3)Installed x-windows packages by:
apt-get install xserver-xorg xinit xfce4 mesa-utils glm
** Attachment added: "image004.jpg backtrace output of glxgears (segment
fault)"
https://bugs.launchpad.net/ubuntu/+source/base-config/+bug/1735681/+attachment/5016900/+files/image004.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
One of affected packages should be "mesa-utils". But I don't know how to
change it for the above package field.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735681
Title:
AMD radeon pro WX7100 gra
** Package changed: base-config (Ubuntu) => mesa-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735681
Title:
AMD radeon pro WX7100 graphic card have bad performance and display
out
** Description changed:
The test process:
1)Put "AMD radeon pro WX7100 graphics card" on our X86 server and ARM server ;
- 2)Installed Ubuntu 17.10 server OS on both X86 server and ARM server with
same steps.
+ 2)Installed Ubuntu 17.10 server OS on both X86 server and ARM server with
same s
sos report
** Attachment added: "sos reports"
https://bugs.launchpad.net/ubuntu/+source/mesa-utils/+bug/1735681/+attachment/5019158/+files/sosreport-d05-amd-wx7100-xwindow-20171206162234.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
reports of "apport-cli xserver-xorg-video-amdgpu"
** Attachment added: "reports of "apport-cli xserver-xorg-video-amdgpu""
https://bugs.launchpad.net/ubuntu/+source/mesa-utils/+bug/1735681/+attachment/5019159/+files/apport.xserver-xorg-video-amdgpu._2dr9jqp.apport
--
You received this bug no
Public bug reported:
package python-pexpect 4.0.1-1 failed to install/upgrade: 子进程 已安装 pre-
removal 脚本 返回错误状态 1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-pexpect 4.0.1-1
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ebruary, the HWE kernel will work
> with Xorg.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1738334/+subscriptions
>
--
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@c
It was reported by Huawei by mail this was tested and verified. So I
change the tag to to 'verification-done-zesty'.
** Tags removed: kernel-da-key verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Comments 25
> (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/25
> )
> and 31 onwards detail this issue.
>
> [1] https://patchwork.ozlabs.org/patch/778054/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+b
Huawei have fix this bug and provide patch to our team that will be
merged in 4.12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702253
Title:
hio.ko driver from linux-
image-4.10.0-26-generic_
The attach file of ap.bug is apport-cli report on 16.04.3 with kernel of
4.10.0-28-generic. This kernel have same issue for s4.
** Attachment added: "The attach file of ap.bug is apport-cli report on 16.04.3
with kernel of 4.10.0-28-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bu
4.1.demsg is from kernel 4.1 which works fine for s4 suspend.
** Attachment added: "4.1.dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718871/+attachment/4978138/+files/4.1.dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
For different kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/
and test on Ubuntu 14.04.1. All version below 4.2 works fine for S4, the
kernel of 4.2, 4.3, 4.3 can't works for S4.
The 4.1 and 4.2 dmesg was attach.
** Attachment added: "4.2.dmesg"
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
My computer has multiple Intel NICs, but only 1 connected. I configured
this one to boot from iSCSI. I could install Ubuntu 14.04 on the iSCSI
disk successfully. But after the reboot, the process stopped after
getting IP address of all NICs.
The attachment is the screenshot.
The fix works for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launc
Forgot to say, I verified in 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs
I get the same problem. Here is the reproduce steps:
I have two network nodes in my environment. Both of them installed L3 agent and
metering agent.
Then I create some metering rules and two routers, and the routers are
scheduled on different network nodes. Then this error will happen. The error
Public bug reported:
ubuntu 10.04 with kernel 2.6.39-3 can't install proprietary drivers
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.39-3.9~lucid1-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
Date: Mon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/815923
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx
kernel module failed to build
To manage notifications about this bug g
I know this is a relatively old bug, but the problem seems to have
reappeared in the most recent update in 11.04. Xfdesktop seems to load
several times, causing the desktop to flicker in and out. Sometimes,
xfdesktop just crashes and I have to start it again manually. It is not
as severe for me as
ubuntu@infra1:~$ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:00 93.1G 0 loop
/var/lib/lxd/storage-pools/default
sda 8:00 1.1T 0 disk
├─sda1 8:10 512M 0 part /boot/efi
└─sda2
Public bug reported:
coping data get io error
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Started Availability of block devices.
[ 185.379378] kdump-tools[1695]: Starting kdump-tools: * running makedumpfile
-c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete
Copying d
Public bug reported:
To configure kernel crash dump, if memory is less than 576M, it would
get oom and to configure crashkernel=2G-:576M, it would get call trace.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
root@node1:~# dmesg |grep -i crash
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic
root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB
hugepagesz=1GB hugepages=192 transparent_hugepage=never
solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 crashke
Public bug reported:
18.04 ga-kernel to load ib_uverbs model which required by Mellanox PMD (
18.04.3 hwe can auto load via model depends)
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
in 18.04 ga-kenrel, the mellanox nic PMD would fail. after manually load
ib_uverbs, then it works fine.
2019-12-02T15:49:57.243Z|00306|netdev|WARN|dpdk-360bbd6: could not set
configuration (Invalid argument)
2019-12-02T15:49:57.262Z|00307|dpdk|INFO|EAL: PCI device :3b:00.0 on NUMA
socket 0
2
101 - 200 of 261 matches
Mail list logo
