[Bug 889706] Re: Gnome-shell randomly crashes
I switched to Firefox for about a week and noticed I never experienced this bug under it as I did with Chrome. However, Firefox isn't my preferred browser so I switched back to Chrome after installing Flash Aid (https://addons.mozilla.org/en-US/firefox/addon/flash-aid/) in Firefox and letting it run through the Terminal and ta-dah, the bug is gone for me! Hopefully this fix might help others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
Nanovarium's fix didn't work for me, used ppa purge to roll back. Still having the same issues, worse when interacting with text boxes and copy+paste in Chrome. Very annoying bug, a fix would be appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
I ended up switching to Cinnamon. GNOME still randomly crashes as I'm working on Chrome, losing data and hours of work...I couldn't take it anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
@Alexander Ast You're absolutely right, I just experienced this bug under Cinnamon as well. I'm still under Mint 12 because, for some strange reason, I can't install Mint 13 from a Live CD (it just hangs after the 'Linux Mint 13' loading screen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
Well, looks like there was an update for my Intel graphics card, and so far, so good. Let's hope it sticks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
@Alexander Ast I switched to Mint 13 today. It's odd having a computer that doesn't crash every other hour, guess I was starting to see this bug as a feature...but so far, so good! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
Same problem here, tends to pop up when using Google Chrome. Lenovo G570 Intel HD Graphics 3000 Mint 12, Gnome 3, 64 Bit Would love a fix because this is my main computer and I nuked Windows 7 for Mint 12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
I installed the Gnome3 PPA as suggested above and I haven't had a single crash in Chrome for at least two hours now. Hopefully that's the end of that. Will report if any changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889706] Re: Gnome-shell randomly crashes
Nope, spoke too soon, came back. However, I'm able to duplicate the error. It always happens when I highlight text in Chrome, which freezes GNOME. I can only interact with the top menus, such as right-click, but I can't minimize/maximize/close any windows. Tabs with music playing in the background (Pandora, YouTube) continue playing. It's very annoying but not turning my computer into a brick. Still, would love a fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889706 Title: Gnome-shell randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/889706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76513] Re: crash when editing a input field
Brian, my current version of openoffice.org come with Gutsy as an upgrade obtained by update-manager . With synaptic i see: package: openoffice.org installed version: 1:2.3.0-1ubuntu5.1 last version: 1.2.3.0-1ubuntu5.1 in openoffice --> Help -> About OpenOffice.org, i see: OpenOffice.org 2.3.0 Copyright 2000-2007 Sun Microsystems Inc. This product has been created by Debian and Ubuntu based in OpenOffice.org. OpenOffice.org acknowledges all community members, especially those mentioned in http://www.openoffice.org/welcome/credits.html openoffice.org-core 1:2.3.0-1ubuntu5.1, Sat Oct 20 15:09:53 GMT 2007 You need any other info about this? -- crash when editing a input field https://bugs.launchpad.net/bugs/76513 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76513] Re: crash when editing a input field
i have tried OO 2.3.0 (openoffice.org-core 1:2.3.0-1ubuntu5.1) and is affected by de same bug what i can do? -- crash when editing a input field https://bugs.launchpad.net/bugs/76513 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76513] crash when editing a input field
Public bug reported: Binary package hint: openoffice.org try to insert a variable field and then a input field of previous defined variable. Save, close and re-open. Click on input field and edit variable value. Oo crash when you insert second char openoffice.org 2.0.4-2ubuntu0.4 on ubuntu 6.10 here. ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: Unconfirmed -- crash when editing a input field https://launchpad.net/bugs/76513 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76513] Re: crash when editing a input field
here a test file that exploit bug ** Attachment added: "open the attached file and try to edit input field" http://librarian.launchpad.net/5478119/test_edit_field.odt -- crash when editing a input field https://launchpad.net/bugs/76513 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76513] Re: crash when editing a input field
Ryan, Attached you can find backtrace of soffice.bin crash event, Mao ** Attachment added: "gdb backtrace of soffice.bin" http://librarian.launchpad.net/5482688/gdb-soffice.bin.txt -- crash when editing a input field https://launchpad.net/bugs/76513 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68597] Re: bittornado crashed "after quiting".
** Attachment added: "same problem" http://librarian.launchpad.net/5483023/_usr_bin_btdownloadgui.bittornado.1000.crash -- bittornado crashed "after quiting". https://launchpad.net/bugs/68597 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526710] [NEW] WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210()
Public bug reported: not sure what happen. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. AplayDevices: List of PLAYBACK Hardware Devices card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mao1285 F pulseaudio CRDA: Error: [Errno 2] 沒有此一檔案或目錄 Card0.Amixer.info: Card hw:0 'SI7012'/'SiS SI7012 with AD1980 at irq 18' Mixer name : 'Analog Devices AD1980' Components : 'AC97a:41445370' Controls : 46 Simple ctrls : 32 CurrentDmesg: [ 15.309224] eth0: Media Link On 10mbps half-duplex [ 22.752036] eth0: no IPv6 routers present Date: Wed Feb 24 05:30:30 2010 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=3f4ec5a4-45fa-4fd1-a8e8-aaac2db821d2 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 003 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System Manufacturer System Name Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-generic root=UUID=77b0db70-c7ea-4c2e-872a-c969d7ea6b05 ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-19.56-generic RelatedPackageVersions: linux-backports-modules-2.6.31-19-generic N/A linux-firmware 1.26 RfKill: SourcePackage: linux Tags: kernel-oops Title: WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210() Uname: Linux 2.6.31-19-generic i686 dmi.bios.date: 06/11/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4S533-MX ACPI BIOS Revision 1006 dmi.board.name: P4S533MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4S533-MXACPIBIOSRevision1006:bd06/11/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4S533MX:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops -- WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210() https://bugs.launchpad.net/bugs/526710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526710] Re: WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210()
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/39669076/AlsaDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/39669077/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/39669078/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/39669079/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/39669080/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/39669081/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39669082/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/39669083/Lspci.txt ** Attachment added: "OopsText.txt" http://launchpadlibrarian.net/39669084/OopsText.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/39669086/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/39669087/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/39669088/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/39669089/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/39669090/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/39669092/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/39669093/WifiSyslog.txt -- WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210() https://bugs.launchpad.net/bugs/526710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310393] [NEW] MenuLibre refuses to launch
Public bug reported: 1) Ubuntu Trusty Tahr (14.04) 2) MenuLibre 2.0.3-1 3) MenuLibre would launch 4) MenuLibre refuses to launch. Cursor changes to 'busy' for a couple of minutes, then stops. Cannot send any information to Canonical through Apport, as MenuLibre simply doesn't start. Launch from Terminal yields same results. MenuLibre still present in Unity Search and Launcher. Purge and reinstall yields same results. ** Affects: menulibre (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310393 Title: MenuLibre refuses to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1310393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310393] Re: MenuLibre refuses to launch
Purged and reinstalled. Now getting this output: mao@CatLap:~$ menulibre ** ERROR:/build/buildd/gnome-menus-3.10.1/./libmenu/gmenu-tree.c:4022:preprocess_layout_info: assertion failed: (!directory->preprocessed) Aborted (core dumped) mao@CatLap:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310393 Title: MenuLibre refuses to launch To manage notifications about this bug go to: https://bugs.launchpad.net/menulibre/+bug/1310393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228352] Re: [regression] Alt-Tab for all viewports will not switch viewports when selecting a window on another viewport
Hi, the bug also occours on my installation (compiz 0.9.10.2 + ubuntu 13.10), after I played with Ubuntu Tweak, Unity Tweak, or after I run this command 'dconf reset -f /org/compiz/', I don't know. Now I could not restore the correct behavior. Maybe this could help you ro resolve this very annoying issue, thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228352 Title: [regression] Alt-Tab for all viewports will not switch viewports when selecting a window on another viewport To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1228352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386390] [NEW] Bootloader was not able to install, works in default ubuntu
Public bug reported: During installation booltloader failed to install. It wanted to install on raid /dev/cciss/c0d0, that failed. Attempted to change to sdb, where it should install. Also failed. Aborted installation and got a crash report. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity 2.20.0 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CasperVersion: 1.345 Date: Mon Oct 27 20:32:30 2014 InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=se LiveMediaBuild: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.20.0 ubuntu-gnome utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386390 Title: Bootloader was not able to install, works in default ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1386390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792110] Re: New VPN connection does not appear available to choose for connection after creation
When creating a new VPN connection it doesn't get shown in the VPN under "Connect to VPN". If one reconnects to an connected network, lets say the WiFi it appears straight away as it should. When setting the VPN as "Available to all users" it's not possible to set a password for the VPN connection. The password never gets saved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792110 Title: New VPN connection does not appear available to choose for connection after creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/792110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080065] [NEW] package ukui-wallpapers (not installed) failed to install/upgrade: trying to overwrite '/usr/share/backgrounds/calla.png', which is also in package ubuntukylin-wallpapers-focal 24.
Public bug reported: ran apt install ukui-wallpapers ProblemType: Package DistroRelease: Ubuntu 24.04 Package: ukui-wallpapers (not installed) ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 9 21:57:46 2024 ErrorMessage: trying to overwrite '/usr/share/backgrounds/calla.png', which is also in package ubuntukylin-wallpapers-focal 24.04 InstallationDate: Installed on 2024-09-09 (0 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: ukui-wallpapers Title: package ukui-wallpapers (not installed) failed to install/upgrade: trying to overwrite '/usr/share/backgrounds/calla.png', which is also in package ubuntukylin-wallpapers-focal 24.04 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ukui-wallpapers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080065 Title: package ukui-wallpapers (not installed) failed to install/upgrade: trying to overwrite '/usr/share/backgrounds/calla.png', which is also in package ubuntukylin-wallpapers-focal 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ukui-wallpapers/+bug/2080065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454725] Re: I get an error message after boot-up telling me that there is an kernel error and that the system might be ubstable
I get the same problem as CTW above, and I'm on an Intel processor too. In addition, I am using the Gnome environment. -- I get an error message after boot-up telling me that there is an kernel error and that the system might be ubstable https://bugs.launchpad.net/bugs/454725 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934112] [NEW] Intel 100G nic get call trace for sosreport on focal ga-kenel
Public bug reported: On Asus Server, when it run "sosreport -a" to the network step, the console would print below call trace and the 100G Nic port became unreachable. call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/ ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934112] Re: Intel 100G nic get call trace for sosreport on focal ga-kenel
The call trace seems correlating to ethtools like below: Jun 18 01:19:08 frank-viper kernel: [69418.453457] BUG: unable to handle page fault for address: b2660b04 Jun 18 01:19:08 frank-viper kernel: [69418.465204] #PF: supervisor read access in kernel mode Jun 18 01:19:08 frank-viper kernel: [69418.473243] #PF: error_code(0x) - not-present page Jun 18 01:19:08 frank-viper kernel: [69418.473245] PGD 3f72d5a067 P4D 3f72d5a067 PUD 3f72d5b067 PMD 3f515a4067 PTE 0 Jun 18 01:19:08 frank-viper kernel: [69418.473251] Oops: [#1] SMP NOPTI Jun 18 01:19:08 frank-viper kernel: [69418.473255] CPU: 42 PID: 4113544 Comm: ethtool Tainted: P O 5.4.0-74-generic #83-Ubuntu Jun 18 01:19:08 frank-viper kernel: [69418.473256] Hardware name: ASUSTeK COMPUTER INC. AE-SER1UW-A --/AE-SER1UW-A/AF1829.01, BIOS 3.03.00 05/25/2021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
For #37 screen shot and #39. We found this wayland issues for 18.04 and Huawei x86 server, but it seems no for 18.04.1. In my test, apt-get install ubuntu-desktop and reboot works fine. For #37 "Why would hibmc_drm be arm64-specific?", I guess it might because vendors (sm750 vga) have already provided driver x86. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
For #37-#39 This screen blur issues during install are only happened on Huawei X86 server for 18.04 and 18.04.1 d-i iso. As I know, 18.04 and even 18.04.1 ARM64 iso works fine with this new hibmc-drm module for installation on Hisilicon D05 board. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Dann, For the wanland issues, I understood it as comments in #15, that is: Blur screen for GDM login was caused by wayland, it can be fix by force to use Xorg in /etc/gdm3/customer.conf to uncoment WaylandEnable=false Is this right for your wanland issues on D05? In 18.04, we found 2 issues on Huawei X86 server. One is screen blur during d-i install on UEFI model in Language selection screen, but it works for legacy bios model. The other is after start GUI (x-window or Ubuntu desktop). After we sucessfully installed 18.04 in legacy bios model on X86 Huawei server, I tried to start X-windows via apt-get install ubuntu-dekstop and reboot, we would get this blur screen again. This seems caused by this wanyland and can be fixed by this "WaylandEnable=false". As I know, this wayland issues have been happened for D05 but I don't think D05 have above issues during install. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
A good feedback from partner is "I just update Ubuntu kernel to v4.19 and Memory Stress can got pass result this time." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
** Attachment added: "sos report when issued showed on console" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+attachment/5197396/+files/sosreport-right-goblin-20181003095301.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796217] [NEW] Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
Public bug reported: We are facing a problem during the certification test. System always stop at below screen while memory stress. In the following re-producing, kernel seems un-normal and it can’t capture above info into the syslog or kernel log, but the console will show same warning as screen shot attachment file. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
** Attachment added: "sos report when issued showed on console" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+attachment/5197397/+files/sosreport-right-goblin-20181003095301.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802832] [NEW] ethtools report i40e as 10G instead the real 1G
Public bug reported: ethtools report i40e as 10G instead the real 1G on Ubuntu 16.04.5 ga- kernel ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802832 Title: ethtools report i40e as 10G instead the real 1G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802832] Re: ethtools report i40e as 10G instead the real 1G
sos-reports ** Attachment added: "sos reports" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+attachment/5211663/+files/sosreport-R4900G3-20180930070440.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802832 Title: ethtools report i40e as 10G instead the real 1G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04
It is also found on 16.04.5 hwe kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04
** Attachment added: "dmesg before" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5188979/+files/dmesg_before -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04
** Attachment added: "dmegs after" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5188978/+files/dmesg_after -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04
It was found on v4.15.0 kernel and not for v4.4 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] [NEW] nvme name floated after boot in Ubuntu 18.04
Public bug reported: nvme device name such as /dev/nvme?n?p? would be floated that is symbol link to different real ssd device after reboot in 4.15.0 kernel. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
** Summary changed: - nvme name floated after boot in Ubuntu 18.04 + nvme name floated after boot with 4.15.0 kernel ** Description changed: nvme device name such as /dev/nvme?n?p? would be floated that is symbol - link to different real ssd device after reboot in 4.15.0 kernel. + link to different real ssd device after reboot in 4.15.0 kernel for + 16.04.5 HWE and 18.04 GA-kernel. ** Description changed: nvme device name such as /dev/nvme?n?p? would be floated that is symbol link to different real ssd device after reboot in 4.15.0 kernel for - 16.04.5 HWE and 18.04 GA-kernel. + 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA-kernel + ( 4.4.0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
In the 4.15.0 kernel, a mismatch was found under /sys/class/nvme/, for example for the /sys/class/nvme/nvme1/, there is a of nvme3n1 directory which might be wrong. In 4.4 kernel, it is a matched directory of nvme1n1. Please refer to attach screen shot for more details. ** Attachment added: "mismatch directory of /sys/class/nvme" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189359/+files/image003.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
** Attachment added: "match name in 4.4.0 kernel for /sys/class/nvme" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189361/+files/image004.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
** Attachment added: "match name in 4.4.0 kernel for /sys/class/nvme" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189362/+files/image004.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
In the 4.15.0 kernel, a mismatch was found under /sys/class/nvme/, for example for the /sys/class/nvme/nvme1/, there is a of nvme3n1 directory which might be wrong. In 4.4 kernel, it is a matched directory of nvme1n1. Please refer to attach screen shot for more details. ** Attachment added: "mismatch directory of /sys/class/nvme" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189360/+files/image003.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
** Package changed: ubuntu => kernel-package (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
@AaronMa Do you have docs for how to compile a new kernel. I can found below doc link https://help.ubuntu.com/community/Kernel/Compile But it seems a bit old. The other difficult is how to get compile config from d-i iso kernel. I found if I use a kernel from running/installed system to replace d-i iso kernel, it would hang (died) after booting in the first language selection screen. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
The log which collect via apport-cli --save=/tmp/apport-log linux ** Attachment added: "apport-cli log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+attachment/5191267/+files/apport-log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
@Guiherme Firstly, thank you much to provide those inforamtion. I asked customer to check on 4.15.0-34 with kernel parameter of "nvme_core.multipath=0", it was reported the same ( nvme device name would be changed every reboot). ** Attachment added: "nvme name mismatch screen shoot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+attachment/5192975/+files/image003.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
hi Guilherme, The partner have tested both for 4.16.0 and 4.15.1 ( I guess it is newer than 4.15.0-34), it was reported that the issues is same. The 4.15.1 testing results are as below: zlmao@zlmao-T460s:~/tmp$ cat test_result.txt uname -r 4.15.1-041501-generic cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.1-041501-generic root=UUID=3e875566-3c1b-4bda-a869-6eb59ff1624a ro nvme_core.multipath=0 ls -l /sys/block/* lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme0n1 -> ../devices/pci:80/:80:03.2/:83:00.0/nvme/nvme2/nvme0n1 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme1n1 -> ../devices/pci:80/:80:03.3/:84:00.0/nvme/nvme3/nvme1n1 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/nvme1n2 -> ../devices/pci:80/:80:03.3/:84:00.0/nvme/nvme3/nvme1n2 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme2n1 -> ../devices/pci:80/:80:03.0/:81:00.0/nvme/nvme0/nvme2n1 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme3n1 -> ../devices/pci:80/:80:03.1/:82:00.0/nvme/nvme1/nvme3n1 zlmao@zlmao-T460s:~/tmp$ 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/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
summary for workaround via kernel parameter to blocker loading: modprobe.blacklist=hibmc_drm **prevent load during install To add "modprobe.blacklist=hibmc_drm" kernel parameter in grub when boot from d-i iso (press ‘e’ key and then press F10 or ctrl+x ( those key was noticed on the screen). It would prevent this module to load and let you install as usual. **prevent load for installed system Although, we didn't find any issues for X-window during our testing. If you want to prevent loading on a finished installed system. You can add similar setting to /etc/default/grub for line as: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=hibmc_drm" You need to update grub by "sudo grub-update" and reboot to make it be efectly. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864612] [NEW] requests ipmi-tool to include lasted patch for supporting quanta server
Public bug reported: The existing ipmitool can't works for Quanta server as it didn't include lasted patches, even in 20.04. >From Quanta feedback that pmitools in 20.04 can work for quanta server if >apply this patch set: https://github.com/ipmitool/ipmitool/commit/5c033c06abb45bc183f42cd758c61807ce953726. Hopes to consideration this patch in 20.04 releasing. ** Affects: ipmitool (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864612 Title: requests ipmi-tool to include lasted patch for supporting quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1864612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864612] Re: requests ipmi-tool to include lasted patch for supporting quanta server
Got feedback about what was fixed by the patch as below: New IPMITOOL QCT support OEM DIMM description as below, so customer can know which CPU/DIMM/slot Logged "Correctable ECC / SBE Warning Threshold (DIMM A0) - Asserted": ipmitool -U admin -P admin -H 10.10.12.21 raw 0xa 0x44 0x0 0x0 0x2 0x0 0x0 0x00 0x0 0x1 0x0 0x4 0xc 0x87 0x6f 0xa0 0x00 0x00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864612 Title: requests ipmi-tool to include lasted patch for supporting quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1864612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864612] Re: requests ipmi-tool to include lasted patch for supporting quanta server
It was also tested that freeipmi tools of ipmiconsole and ipmipower cmd works fine with Quanta server as it is standard for ipmi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864612 Title: requests ipmi-tool to include lasted patch for supporting quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1864612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS
It seems not works on my side ( 18.04 ARM64). I have to add the
listening IP explicitly.
ubuntu@infra1:/etc/bind$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
ubuntu@infra1:/etc/bind$ uname -a
Linux infra1 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:32:18 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@infra1:/etc/bind$ cat /etc/bind/named.conf.options
..
options { directory "/var/cache/bind";
auth-nxdomain no;
listen-on-v6 { none; };
listen-on { 185.168.3.1; };
//listen-on { !10.54.224.0/24; };
//listen-on { any; };
include "/etc/bind/maas/named.conf.options.inside.maas"; };
ubuntu@infra1:/etc/bind$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1594317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS
to add floating ip too as:
listen-on { 185.168.3.1; 185.168.3.5; };
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1594317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860403] [NEW] fio call trace on xenial during ceph rbd testing
Public bug reported: During fio testing as below on 16.04 (xenial) hwe-kernel ( 4.15.0-55-generic), the below fio woluld get call trace or segment falut: /tmp/juju-exec53975/script.sh: line 1: 1104000 Segmentation fault (core dumped) fio --name=randread --ioengine=rbd --clientname=admin --pool=scbench --rbdname=image01 --iodepth=16 --bs=4k --direct=0 --size=512M --numjobs=8 --runtime=240 --group_reporting --rw=randread ** Affects: fio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860403 Title: fio call trace on xenial during ceph rbd testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fio/+bug/1860403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] [NEW] The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
Public bug reported: In Quanta server testing for 18.04.3 hwe-kernel 18.04.4 hwe-kernel and 20.04 daily build, it seems usb keyboard would: 1.Same OS would lost keybord and record usb usbx-portx: couldn't allocate usb_device log. 2.It is easy to reproduce the issue if add "open initcall debug" in grub.cfg. ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
Also, it was said that this issues didn't found on rhel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
kernel log from testing ** Attachment added: "kernel.log" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+attachment/5341769/+files/log.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
>From the kernel log, beside below errors, there are no errors for usb or keryboard, it also show correctly dectected keyboard for every reboot. $ grep -i error kern.log | tail -n5 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [4.321273] ERST: Error Record Serialization Table (ERST) support is initialized. Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 21.017745] RAS: Correctable Errors collector initialized. Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 28.579403] calling init_error_injection+0x0/0x6f @ 1 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 28.639458] initcall init_error_injection+0x0/0x6f returned 0 after 160 usecs Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 61.697880] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro $ grep -i keybaord kernel.log|tail -n15 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 14.154902] usb 1-2: Product: USB Multimedia Keyboard Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.585889] input: Lite-On Technology Corp. USB Multimedia Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04CA:0027.0001/input/input1 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.642395] hid-generic 0003:04CA:0027.0001: input,hidraw0: USB HID v1.10 Keyboard [Lite-On Technology Corp. USB Multimedia Keyboard] on usb-:00:14.0-2/input0 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.642705] input: Lite-On Technology Corp. USB Multimedia Keyboard System Control as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:04CA:0027.0002/input/input2 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.702392] input: Lite-On Technology Corp. USB Multimedia Keyboard Consumer Control as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:04CA:0027.0002/input/input3 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.702495] input: Lite-On Technology Corp. USB Multimedia Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:04CA:0027.0002/input/input4 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.702653] hid-generic 0003:04CA:0027.0002: input,hiddev0,hidraw1: USB HID v1.10 Device [Lite-On Technology Corp. USB Multimedia Keyboard] on usb-:00:14.0-2/input1 Feb 26 10:05:08 user-QuantaGrid-D52PL-4U kernel: [ 88.768902] usb 1-1: Product: Logitech USB Keyboard Feb 26 10:05:08 user-QuantaGrid-D52PL-4U kernel: [ 88.773167] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C315.0003/input/input5 Feb 26 10:05:08 user-QuantaGrid-D52PL-4U kernel: [ 88.830768] hid-generic 0003:046D:C315.0003: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:14.0-1/input0 Feb 26 10:06:26 user-QuantaGrid-D52PL-4U kernel: [ 167.205004] usb 1-2: Product: Logitech USB Keyboard Feb 26 10:06:26 user-QuantaGrid-D52PL-4U kernel: [ 167.209006] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C315.0005/input/input7 Feb 26 10:06:26 user-QuantaGrid-D52PL-4U kernel: [ 167.266672] hid-generic 0003:046D:C315.0005: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:14.0-2/input0 Feb 26 10:08:09 user-QuantaGrid-D52PL-4U kernel: [ 270.085139] usb 1-2: Product: Logitech USB Keyboard Feb 26 10:08:09 user-QuantaGrid-D52PL-4U kernel: [ 270.089237] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C315.0007/input/input9 Feb 26 10:08:09 user-QuantaGrid-D52PL-4U kernel: [ 270.146678] hid-generic 0003:046D:C315.0007: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:14.0-2/input0 zlmao@zlmao-T460s:~/tmp/quanta$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
The boot which failed to detected keyboard are below: Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.688666] xhci_hcd :00:14.0: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.739684] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.796396] xhci_hcd :00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x9810 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.860304] xhci_hcd :00:14.0: cache line size of 64 is not supported Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.924653] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.989809] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.055002] usb usb1: Product: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.119662] usb usb1: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.184980] usb usb1: SerialNumber: :00:14.0 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.249663] hub 1-0:1.0: USB hub found Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.313880] hub 1-0:1.0: 16 ports detected Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.379787] probe of 1-0:1.0 returned 1 after 130128 usecs Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.444761] probe of usb1 returned 1 after 195129 usecs Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.509606] xhci_hcd :00:14.0: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.574399] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.609979] usb usb1-port1: couldn't allocate usb_device Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.639502] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.703568] usb usb1-port2: couldn't allocate usb_device Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.769363] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.900828] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.968612] usb usb2: Product: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.027356] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.079505] usb usb2: SerialNumber: :00:14.0 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.133178] hub 2-0:1.0: USB hub found Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.184423] hub 2-0:1.0: 10 ports detected Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.235270] usb: port power management may be unreliable Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.287421] probe of 2-0:1.0 returned 1 after 154246 usecs Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.338363] probe of usb2 returned 1 after 205203 usecs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
The Quanta give me hits about error and it seems that in 68 reboot cycles there are 11 times which can't detected out the usb keyboard. $ grep 'Command line' kern.log |wc 68 952 12988 $ grep "usb1-port2: couldn't allocate usb_device" kern.log |wc 11 1321199 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
The boot with keyboard detected logs as below: Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.242592] hub 1-0:1.0: 16 ports detected Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.308359] probe of 1-0:1.0 returned 1 after 129930 usecs Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.372798] probe of usb1 returned 1 after 194395 usecs Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.437456] xhci_hcd :00:14.0: xHCI Host Controller Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.502175] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.541288] usb usb1-port1: couldn't allocate usb_device Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.567309] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.567341] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.757241] usb 1-2: new low-speed USB device number 2 using xhci_hcd Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764290] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764291] usb usb2: Product: xHCI Host Controller Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764292] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764295] usb usb2: SerialNumber: :00:14.0 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.986189] usb 1-2: New USB device found, idVendor=04ca, idProduct=0027, bcdDevice= 1.18 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.004749] hub 2-0:1.0: USB hub found Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.056592] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.109726] hub 2-0:1.0: 10 ports detected Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.161986] usb 1-2: Product: USB Multimedia Keyboard Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.161988] usb 1-2: Manufacturer: Lite-On Technology Corp. Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.215697] usb: port power management may be unreliable Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.269095] probe of 1-2 returned 1 after 1173 usecs Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.320539] probe of 2-0:1.0 returned 1 after 315796 usecs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
Compare the kernel related usb logs between keyboard detected and not, all previous logs are no difference, it began difference only from. I personally thought it might not issues from kernel as it likes external device (keyboad) didn't report devices information back and from testing log it sees just 16% reboot were failed to detect keyboard. no-keyboard: Feb 25 20:56:06 13.639502] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed *Feb 25 20:56:06 13.703568] usb usb1-port2: couldn't allocate usb_device *Feb 25 20:56:06 13.769363] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 20:56:06 13.900828] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:56:06 13.968612] usb usb2: Product: xHCI Host Controller Feb 25 20:56:06 14.027356] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:56:06 14.079505] usb usb2: SerialNumber: :00:14.0 with-keyboard: Feb 25 14:58:11 17.021871] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed *Feb 25 14:58:11 17.021903] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 14:58:11 17.212935] usb 1-2: new low-speed USB device number 2 using xhci_hcd Feb 25 14:58:11 17.220801] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 14:58:11 17.220803] usb usb2: Product: xHCI Host Controller Feb 25 14:58:11 17.220803] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 14:58:11 17.220804] usb usb2: SerialNumber: :00:14.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
The kernel of Linux version 3.10.0-862.el7.x86_64 which didn't find issues. From the below log of "usb 1-1: Product: Keyboard Hub", it seems ubuntu new hwe kernel can't detected and support this usb hub of the keybaord. The full log about usb 1-1 are below: usb 1-1: new high-speed USB device number 2 using xhci_hcd usb 1-1: New USB device found, idVendor=05ac, idProduct=1006 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1: Product: Keyboard Hub usb 1-1: Manufacturer: Apple, Inc. usb 1-1: SerialNumber: kernel: hub 1-1:1.0: USB hub found - full log for a reboot crycle via grep usb messages Feb 17 19:54:41 192-168-129-24 kernel: ACPI: bus type USB registered Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbfs Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver hub Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new device driver usb Feb 17 19:54:41 192-168-129-24 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Feb 17 19:54:41 192-168-129-24 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Feb 17 19:54:41 192-168-129-24 kernel: uhci_hcd: USB Universal Host Controller Interface driver Feb 17 19:54:41 192-168-129-24 kernel: xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: Product: xHCI Host Controller Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: Manufacturer: Linux 3.10.0-862.el7.x86_64 xhci-hcd Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: SerialNumber: :00:14.0 Feb 17 19:54:41 192-168-129-24 kernel: hub 1-0:1.0: USB hub found Feb 17 19:54:41 192-168-129-24 kernel: xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: Product: xHCI Host Controller Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: Manufacturer: Linux 3.10.0-862.el7.x86_64 xhci-hcd Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: SerialNumber: :00:14.0 Feb 17 19:54:41 192-168-129-24 kernel: hub 2-0:1.0: USB hub found Feb 17 19:54:41 192-168-129-24 kernel: usb: port power management may be unreliable Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbserial Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbserial_generic Feb 17 19:54:41 192-168-129-24 kernel: usbserial: USB Serial support registered for generic Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbhid Feb 17 19:54:41 192-168-129-24 kernel: usbhid: USB HID core driver Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: New USB device found, idVendor=05ac, idProduct=1006 Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: Product: Keyboard Hub Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: Manufacturer: Apple, Inc. Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: SerialNumber: Feb 17 19:54:41 192-168-129-24 kernel: hub 1-1:1.0: USB hub found Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: new low-speed USB device number 3 using xhci_hcd Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: New USB device found, idVendor=046d, idProduct=c31c Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: Product: USB Keyboard Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: Manufacturer: Logitech Feb 17 19:54:42 192-168-129-24 kernel: input: Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input1 Feb 17 19:54:42 192-168-129-24 kernel: usb 1-1.2: new low-speed USB device number 4 using xhci_hcd Feb 17 19:54:42 192-168-129-24 kernel: hid-generic 0003:046D:C31C.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-:00:14.0-2/input0 Feb 17 19:54:42 192-168-129-24 kernel: input: Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/input/input2 Feb 17 19:54:42 192-168-129-24 kernel: hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-:00:14.0-2/input1 Feb 17 19:54:42 192-168-129-24 kernel: usb 1-1.2: New USB device found, idVendor=05ac, idProduct=0220 Feb 17 19:54:42 192-168-129-24 kernel: usb 1-
[Bug 1702253] [NEW] hio.ko driver from linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb will corrupt data on SSD disk
Public bug reported:
The user upgrade Ubuntu server to linux-
image-4.10.0-26-generic_4.10.0-26.30_amd64.deb and it use a SSD of
ES3000 V2 SSD which the correspond module driver of hio.ko is include in
this kernel. The data write to disk seems was incorrect.
To format this sdd disk with xfs get error of "meta data corruption" and
to use dd write data to this ssd disk and read out again, the sha256
chuksum is also mismatched.
It was tested for 4.8.0-34-generic, 4.10.0-26-generic and 4.12， this
problem was not found on 4.8.0-34-generic, but both 4.10.0-26-generic
and 4.12 have same issues.
This hio source can be download from
http://support.huawei.com/enterprise/zh/server/es3000-v2-pid-21242728/software/22305278?idAbsPath=fixnode01%7C7919749%7C9856522%7C9856629%7C21462722%7C21242728.
It is also include in Ubuntu kernel tree of linux-source-4.10.0.
Huawei reports that they get similar problem when upgrading from linux4.4 to
linux4.8 and they fix it at the hio driver in 2.1.0.28 version as:
为适配4.8内核修改代码如下：
if (!test_bit(SSD_ONLINE, &dev->state)) {
ssd_bio_endio(bio, -ENODEV);
goto out;
}
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
blk_queue_split(q, &bio, q->bio_split);
#endif
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: zesty
--
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_4.10.0-26.30_amd64.deb will corrupt data on
SSD disk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1702253/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702253] Re: hio.ko driver from linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb will corrupt data on SSD disk
** Description changed:
The user upgrade Ubuntu server to linux-
image-4.10.0-26-generic_4.10.0-26.30_amd64.deb and it use a SSD of
ES3000 V2 SSD which the correspond module driver of hio.ko is include in
this kernel. The data write to disk seems was incorrect.
To format this sdd disk with xfs get error of "meta data corruption" and
to use dd write data to this ssd disk and read out again, the sha256
chuksum is also mismatched.
It was tested for 4.8.0-34-generic, 4.10.0-26-generic and 4.12， this
problem was not found on 4.8.0-34-generic, but both 4.10.0-26-generic
and 4.12 have same issues.
This hio source can be download from
http://support.huawei.com/enterprise/zh/server/es3000-v2-pid-21242728/software/22305278?idAbsPath=fixnode01%7C7919749%7C9856522%7C9856629%7C21462722%7C21242728.
It is also include in Ubuntu kernel tree of linux-source-4.10.0.
+ Huawei reports that they get similar problem when upgrading from linux4.4 to
linux4.8 and they fix it at the hio driver in 2.1.0.28 version as:
+ The modification for 4.8 is as below:
+ if (!test_bit(SSD_ONLINE, &dev->state)) {
+ ssd_bio_endio(bio, -ENODEV);
+ goto out;
+ }
- Huawei reports that they get similar problem when upgrading from linux4.4 to
linux4.8 and they fix it at the hio driver in 2.1.0.28 version as:
- 为适配4.8内核修改代码如下：
- if (!test_bit(SSD_ONLINE, &dev->state)) {
- ssd_bio_endio(bio, -ENODEV);
- goto out;
- }
-
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
- blk_queue_split(q, &bio, q->bio_split);
+ blk_queue_split(q, &bio, q->bio_split);
#endif
--
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_4.10.0-26.30_amd64.deb will corrupt data on
SSD disk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702253/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702253] Re: hio.ko driver from linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb will corrupt data on SSD disk
It is Ubuntu server without Desktop environment and I can't provide my launchpad access to customer too. I will ask them to collect bug reports by: apport-bug linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb I am not family for apport. Can apport-bug provide what you want? -- 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_4.10.0-26.30_amd64.deb will corrupt data on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702253] Re: hio.ko driver from linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb will corrupt data on SSD disk
We found same problem on Ubuntu17.04 the kernel version is linux-image-4.10.0-19-generic上. The apport report is in the attachment file. We compared and testing on kernel 4.9 an 4.10， this HIO driver works fine on 4.9 but does not work on kernel 4.10-rc5 and aboe. ** Attachment added: "This is apport on linux-image-4.10.0-19-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702253/+attachment/4909670/+files/apport.linux-image-4.10.0-19-generic.kk0x7vwq.apport ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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_4.10.0-26.30_amd64.deb will corrupt data on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
This patch need to merged and fixed for the release 16.04.04. The final
SRU4 windows is 8 Dec. to 6 Jan 2018.
--
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 ("drm/ttm: add
io_mem_pfn callback")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738334/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
Notes and some more detail for this bug/patch:
The bug is from/caused by 4.12 DRM architecture, the main line commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc3&id=ea642c3216cb2a60d1c0e760ae47ee85c9c16447
It will cause x-window start hanged, the detail bug are
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700
The fix path link are here: https://lists.freedesktop.org/archives/dri-
devel/2017-November/159002.html
This patch only change Huawei driver, it will not affect any other
vendors.
--
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 ("drm/ttm: add
io_mem_pfn callback")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738334/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738990] Re: rdma-core conflicted with kmod
** Attachment added: "screen shot for apt-get conflicts" https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1738990/+attachment/5024549/+files/fjedfhha.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738990 Title: rdma-core conflicted with kmod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1738990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738990] [NEW] rdma-core conflicted with kmod
Public bug reported: sudo apt-get install rdma-core reports for "tring to overwrite /etc/modprobe.d/mlx4.conf which is also in package kmod 24-1ubuntu2". This test on 16.04.3 ARM64 with 18.04 repository. The mlx4.conf contains are: cat /etc/modprobe.d/mlx4.conf # mlx4_core gets automatically loaded, load mlx4_en also (LP: #1115710) softdep mlx4_core post: mlx4_en ** Affects: rdma-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738990 Title: rdma-core conflicted with kmod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1738990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 1804 install screen becomes blur on Huawei server
** Attachment added: "full demsg and syslog for 18.04 uefi install, 18.04 legacy bios install, 16.04.4 uefi install" https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5110296/+files/dmesg_syslog_1804_1604.tar.gz -- 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 1804 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] [NEW] Ubuntu 1804 install screen becomes blur on Huawei server
Public bug reported: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... ** Affects: install-package (Ubuntu) Importance: Undecided Status: New -- 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 1804 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 1804 install screen becomes blur on Huawei server
-- 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 1804 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** Summary changed: - Ubuntu 1804 install screen becomes blur on Huawei server + Ubuntu 18.04 install screen becomes blur on Huawei server -- 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 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection
** Attachment added: "debug log for KVM UEFI model without internet access" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+attachment/5137592/+files/subiquity-debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770585 Title: 18.04 installer would become failed in UEFI without Internet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770585 Title: 18.04 installer would become failed in UEFI without Internet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770585] [NEW] 18.04 installer would become failed in UEFI without Internet connection
Public bug reported: Below iso use new Subiquity (not d-i) and it would be fail without correct internet connection in UEFI mode. After reboot it would show error of "No boot device, please reboot system with manual operaton" in Huawei server. This issue can be produce by KVM with UEFI too. It would report error for install log and after reboot it would give UEFI interactive shell. Both of them works fine if there are internet access to install/upgrade packages during installation. The used ISO was download from below link: http://releases.ubuntu.com/18.04/ubuntu-18.04-live-server-amd64.iso. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770585 Title: 18.04 installer would become failed in UEFI without Internet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection
** Attachment added: "Sos report on KVM UEFI testing" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+attachment/5137665/+files/sosreport-ubuntu-server-20180511073713.tar.xz.md5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770585 Title: 18.04 installer would become failed in UEFI without Internet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection
*** This bug is a duplicate of bug 1750819 *** https://bugs.launchpad.net/bugs/1750819 If I change UEIF to BIOS for my local VM (kvm) then it can be installed successfully after I configure an IP without actually internet access. But if I use UEFI, the install would failed and can't boot into the system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770585 Title: 18.04 installer would become failed in UEFI without Internet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1770585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
For ISO of classic Debian installer (d-i), it would become screen blur after kernel load and in the first screen of "select a langue" -- 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 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** Attachment added: "This screen bure on UEFI model for 18.04 classic d-i installer in the first installer screen of language select" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5141063/+files/uefi-di-screen-blur.png -- 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 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
Below image uses the Subiquity and it can be installed successfully. But after install ubuntu-desktop, the login screen would become screen blur after reboot or init 5, but it can be start by startx after init 3 in the terminal. http://releases.ubuntu.com/18.04/ubuntu-18.04-live-server-amd64.iso. For ISO of classic Debian installer (d-i) which was download from below, the setup (install) would still become bur and can't continue to finish install by manual which was tested by iMBC(KVM) and virtual CD-ROM. http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04-server-amd64.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 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
Blur screen for GDM login was caused by wayland, it can be fix by force to use Xorg in /etc/gdm3/customer.conf to uncoment WaylandEnable=false -- 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 install screen becomes blur on Huawei server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
@Aaron Ma I want to test your patch. But seems it would patch with error. I guess, the new 18.04 source code have been change to: list_add_tail(&vgadev->list, &vga_list); instead of: - list_add(&vgadev->list, &vga_list); + list_add_tail(&vgadev->list, &vga_list); Does it mean this patch have been already merged in our new source. In last month, I testing with 18.04.2 iso (d-i) and this screen blur is still existing. Does it mean this patch did not solve our cases. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
For #44 Aaron's suggested patch, it seems patch have been included after 4.15.0-46. The testing 18.04.2 iso with 4.15.0-48 kernel seems the system would be hang on language selection after select install server of grub screen. So it seems this hibmc_drm would caused another this hang issues too. This hibmc_drm driver can only work for ARM64, as I know, chip vendors don't have any intend/interesting to make this drm/kernel driver to work for x86. For x86, it must use the existing driver which was based Xorg. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
For #44, in the following testing, if disable hibmc_drm loading, then it works fine and would not be hang. -- 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 EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] [NEW] bcache register_bdev() error cannot allocate memory
Public bug reported: On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would fail as below if the back devices are large than 1024G ( 1025 would fail, but not 1024 ). [ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory [ 727.756456] bcache: register_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.9.16/ The similar bug report can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1783075. It might related to back device type. it was tested on "Lenov SR665 Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X 375GB U.2 NVMe SSD". ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic focal ga-kernel hwe-kernel ** Tags added: bionic focal ga-kernel hwe-kernel ** Description changed: On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would - fail as below if the back devices are large than 1024G ( 102% fail, but - 1024 did not). + fail as below if the back devices are large than 1024G ( 1025 would + fail, but not 1024 ). [ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory [ 727.756456] bcache: register_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped - - There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.16/ + There are fix in 5.9 kernel and it can work after install 5.9 kernel on + 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com + /~kernel-ppa/mainline/v5.9.16/ The similar bug reports are https://bugzilla.redhat.com/show_bug.cgi?id=1783075. It might related to back device type. We tested on "Lenov SR665 Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X 375GB U.2 NVMe SSD". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
Also, 18.04 ga-kernel worked fine too. ** Description changed: On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would fail as below if the back devices are large than 1024G ( 1025 would fail, but not 1024 ). [ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory [ 727.756456] bcache: register_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.9.16/ - The similar bug reports are + The similar bug report can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1783075. - It might related to back device type. We tested on "Lenov SR665 Server" - and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X - 375GB U.2 NVMe SSD". + It might related to back device type. it was tested on "Lenov SR665 + Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are + "Intel P4800X 375GB U.2 NVMe SSD". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
This max 1024G size applies to the 512byte sector, most NVME ssd can change ( LBA format ) to 4K and the max limits will be 16T than. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
The command example to change 512 sector to 4K for “Intel P4510 4.0TB U.2 NVMe SSD” ubuntu@prdhci01a:~$ sudo nvme id-ns /dev/nvme1 -n 1 -H |grep "LBA Format" [3:0] : 0 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0x2 Good (in use) LBA Format 1 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best ubuntu@prdhci01a:~$ sudo nvme format /dev/nvme1 -n 1 -l 1 Success formatting namespace:1 ubuntu@prdhci01a:~$ sudo nvme id-ns /dev/nvme1 -n 1 -H |grep "LBA Format" [3:0] : 0x1 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0x2 Good LBA Format 1 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) ubuntu@prdhci01a:~$ ' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
For the 4K sectors, the max limits should be 8T then. (1024G*4096/512) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911828] [NEW] Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module
Public bug reported: Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module,Please add the driver on next kernel version release. More details please refer to https://bugs.launchpad.net/quantatw/+bug/1905673 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911828 Title: Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900776] [NEW] can't log back in after sleep/lock
Public bug reported: After upgrading to 20.04.1 LTS, when the display goes to sleep and the session locks, I can't log back in. An incorrect password is notified as such, but the correct password blanks the screen. When I move the mouse, the login prompt re-appears. If I lock the session manually, login works fine. Also, I can log in remotely to reboot the machine. This was not a problem before the upgrade from 18.?? Not sure if this bug resides ubuntu or xfce or what. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.28 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Tue Oct 20 15:31:57 2020 InstallationDate: Installed on 2018-07-23 (820 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-10-19 (1 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900776 Title: can't log back in after sleep/lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1900776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900768] Re: Upgrade from 18.04 failed
Problem appears when the Xfce Power Manager locks the session (under the security tab). When the screensaver locks the screen, I am still able to log back in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900768 Title: Upgrade from 18.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1900768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
After add this to /etc/default/grub, ubuntu@test-2:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=0ba22f57-08ab-4b84-9592-936a48bd5692 ro console=tty0 quiet splash vt.handoff=1 ubuntu@test-2:~$ The issues is same which still show as "error: no suitalbe video mode found" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
the out put of "virsh dumpxml" ... ... This should be OpenStack configured for VNC and qemu devices. If I manual remove them, and the virt-manager can become normally which show grub menu, boot message and login etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
