[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
Intel AX101 20230919.git3672ccab-0ubuntu1 Not working bluetooth. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2036428 Title: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1 Status in linux-firmware package in Ubuntu: Fix Released Bug description: After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my Intel AX201 Bluetooth controller is not available post-reboot. The device itself shows up here: $ lsusb | grep -i blue Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth But running e.g. `dmesg | grep -i bluetooth` returns no matches, and bluetoothctl finds no controllers. Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full functionality. n.b. Possible duplicate of LP:2036348 - I am not in a position to confirm those symptoms yet, but will update later. Running mantic pre-release on amd64: $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
I tested with Ubuntu Server 22.04 on R210II, same issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883887] Re: Focal installer destroyed my datasets
Also to note, not all the datasets I created in rpool/USERDATA were destroyed: oot@mesozoic:/# zfs list | grep USERDATA rpool/USERDATA 338G 1.41T 96K / rpool/USERDATA/atm26_tavly8 32.6G 1.41T 29.9G /home/atm26 rpool/USERDATA/root_tavly8 920K 1.41T 592K /root rpool/USERDATA/ssd250 305G 1.41T 88K /local/ssd250 rpool/USERDATA/ssd250/build 55.3G 1.41T 112K /local/ssd250/build rpool/USERDATA/ssd250/build/lineageos 53.1G 1.41T 52.9G /local/ssd250/build/lineageos rpool/USERDATA/ssd250/build/riscos 2.17G 1.41T 2.17G /local/ssd250/build/riscos rpool/USERDATA/ssd250/docker 746M 1.41T 746M /local/ssd250/docker rpool/USERDATA/ssd250/dvd 458M 1.41T 458M /local/ssd250/dvd rpool/USERDATA/ssd250/vm 249G 1.41T 88K /local/ssd250/vm rpool/USERDATA/ssd250/vm/ecadlabs 152K 1.41T 88K /local/ssd250/vm/ecadlabs rpool/USERDATA/ssd250/vm/jenkins 240G 1.41T 240G /local/ssd250/vm/jenkins rpool/USERDATA/ssd250/vm/uvtool 8.74G 1.41T 8.74G /local/ssd250new/vm/uvtool -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1883887 Title: Focal installer destroyed my datasets Status in zfs-linux package in Ubuntu: New Bug description: I installed focal about a month about, using the desktop installer with the 'experimental' ZFS root option. I've been running ZFS on FreeBSD for about 10 years and figured I could handle any sharp edges. It's installed to a single 2TB SSD - no RAID, no L2ARC/ZIL, no dedup, nothing complicated. Machine is an Intel S2600CP2, 2x E5-2670 v1, 128GiB RAM. The machine stayed up for a few weeks, until I had cause to physically move it and so shut it down. It turned out GRUB had installed onto the wrong disk which I'd removed in the intervening time. It wouldn't boot, so I booted the focal desktop installer from a USB stick to give me a shell to fix things. I didn't run the actual installer, I just booted to the installer desktop and then did Ctrl-Alt-F1, apt install openssh-server, and then logged in via SSH. Then I followed some instructions about mounting the pool in a chroot (Step 3): https://askubuntu.com/questions/826209/re-initialise-grub-for-non-bootable-uefi-zfs-16-04-installation This took a couple of goes to get right as the first time I tried to mount on top of the installer (without zpool import -R) and many filesystems couldn't replace preexisting mounts, so I exported and re-imported. Anyway, I succeeded in mounting, and then doing update-grub. However, looking at the zpool history -il log while I was in the installer I see: (full zpool history -il log attached) 2020-06-16.14:56:34 [txg:889337] open pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.14:56:34 [txg:889339] import pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.14:58:20 zpool export rpool bpool [user 0 (root) on ubuntu:linux] 2020-06-16.14:59:16 [txg:889372] open pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.14:59:16 [txg:889374] import pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.15:01:32 [txg:889402] destroy rpool/ROOT/ubuntu_rjlt3b/var/log@autozsys_1gwqtf (19222) [on ubuntu] 2020-06-16.15:01:32 ioctl destroy_snaps input: snaps: rpool/ROOT/ubuntu_rjlt3b/var/log@autozsys_1gwqtf [user 0 (root) on ubuntu:linux] ...lots of snapshots are deleted...
[Kernel-packages] [Bug 1883887] [NEW] Focal installer destroyed my datasets
Public bug reported: I installed focal about a month about, using the desktop installer with the 'experimental' ZFS root option. I've been running ZFS on FreeBSD for about 10 years and figured I could handle any sharp edges. It's installed to a single 2TB SSD - no RAID, no L2ARC/ZIL, no dedup, nothing complicated. Machine is an Intel S2600CP2, 2x E5-2670 v1, 128GiB RAM. The machine stayed up for a few weeks, until I had cause to physically move it and so shut it down. It turned out GRUB had installed onto the wrong disk which I'd removed in the intervening time. It wouldn't boot, so I booted the focal desktop installer from a USB stick to give me a shell to fix things. I didn't run the actual installer, I just booted to the installer desktop and then did Ctrl-Alt-F1, apt install openssh- server, and then logged in via SSH. Then I followed some instructions about mounting the pool in a chroot (Step 3): https://askubuntu.com/questions/826209/re-initialise-grub-for-non-bootable-uefi-zfs-16-04-installation This took a couple of goes to get right as the first time I tried to mount on top of the installer (without zpool import -R) and many filesystems couldn't replace preexisting mounts, so I exported and re-imported. Anyway, I succeeded in mounting, and then doing update-grub. However, looking at the zpool history -il log while I was in the installer I see: (full zpool history -il log attached) 2020-06-16.14:56:34 [txg:889337] open pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.14:56:34 [txg:889339] import pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.14:58:20 zpool export rpool bpool [user 0 (root) on ubuntu:linux] 2020-06-16.14:59:16 [txg:889372] open pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.14:59:16 [txg:889374] import pool version 5000; software version unknown; uts ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 [on ubuntu] 2020-06-16.15:01:32 [txg:889402] destroy rpool/ROOT/ubuntu_rjlt3b/var/log@autozsys_1gwqtf (19222) [on ubuntu] 2020-06-16.15:01:32 ioctl destroy_snaps input: snaps: rpool/ROOT/ubuntu_rjlt3b/var/log@autozsys_1gwqtf [user 0 (root) on ubuntu:linux] ...lots of snapshots are deleted... 2020-06-16.15:05:55 [txg:889577] destroy rpool/USERDATA/root_tavly8@autozsys_1gwqtf (19722) [on ubuntu] 2020-06-16.15:06:00 ioctl destroy_snaps input: snaps: rpool/USERDATA/root_tavly8@autozsys_1gwqtf 2020-06-16.15:06:45 [txg:889588] destroy rpool/USERDATA/local/vm/freebsd-12.1 (3398) [on ubuntu] 2020-06-16.15:06:45 [txg:889590] destroy rpool/USERDATA/local/vm (735) [on ubuntu] 2020-06-16.15:06:46 [txg:889592] destroy rpool/USERDATA/local/ecad/altera (551) [on ubuntu] 2020-06-16.15:06:46 [txg:889594] destroy rpool/USERDATA/local/ecad/xilinx (3476) [on ubuntu] 2020-06-16.15:06:47 [txg:889596] destroy rpool/USERDATA/local/ecad (127) [on ubuntu] 2020-06-16.15:06:48 [txg:889598] destroy rpool/USERDATA/local/scratch/atm26 (2058) [on ubuntu] 2020-06-16.15:06:48 [txg:889600] destroy rpool/USERDATA/local/scratch (2447) [on ubuntu] 2020-06-16.15:06:49 [txg:889602] destroy rpool/USERDATA/local (1671) [on ubuntu] 2020-06-16.15:07:20 [txg:889668] destroy rpool/USERDATA/opt_tavly8/riscv (1878) [on ubuntu] 2020-06-16.15:07:21 [txg:889670] destroy rpool/USERDATA/opt_tavly8/brave.com (1864) [on ubuntu] 2020-06-16.15:07:23 [txg:889672] destroy rpool/USERDATA/opt_tavly8/riscv-llvm (4788) [on ubuntu] 2020-06-16.15:07:24 [txg:889674] destroy rpool/USERDATA/opt_tavly8/riscv-freebsd (5147) [on ubuntu] 2020-06-16.15:07:25 [txg:889676] destroy rpool/USERDATA/opt_tavly8 (3313) [on ubuntu] Here something that wasn't the command line - and so I assume is zsys - deleted all the datasets I made in rpool/USERDATA. This was about 1TiB of data. Needless to say, nothing should be destroying user datasets. root@mesozoic:/# lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 root@mesozoic:/# apt-cache policy zsys zsys: Installed: 0.4.5 Candidate: 0.4.5 Version table: *** 0.4.5 500 500 http://ubuntu.mirrors.uk2.net/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@mesozoic:/# dpkg --list | grep zfs ii libzfs2linux 0.8.3-1ubuntu12 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 0.8.3-1ubuntu12 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed 0.8.3-1ubuntu12 amd64OpenZFS Event Daemon ii zfsutils-linux
[Kernel-packages] [Bug 1824642] Re: nvidia card disabled after upgrading to 5.0.0-11-generic
*** This bug is a duplicate of bug 1824677 *** https://bugs.launchpad.net/bugs/1824677 ** This bug has been marked a duplicate of bug 1824677 Display only has 640x480 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824642 Title: nvidia card disabled after upgrading to 5.0.0-11-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 5.0.0.8-generic to 5.0.0.11-generic, the nvidia card suddenly became "disabled". I own a laptop with hybrid GPU stack, intel + nvidia; nvidia is in charge of display ports. On 5.0.0.8-generic I had only nvidia GPU enabled (discrete mode) and nouveau was able to properly control nvidia and send the signal to my monitor. In hybrid mode this worked as well properly. On 5.0.0.11-generic in discrete mode, linux booted to 640x480 resolution only. When I enabled hybrid mode back, the computer boots into 1920x1200 mode properly, however the display port ports don't work at all, and the "About" screen only lists the Intel GPU, not nvidia. lspci still lists nvidia though. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mavi 2324 F pulseaudio /dev/snd/controlC1: mavi 2324 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:09:25 2019 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (950 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-11-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-11-generic N/A linux-backports-modules-5.0.0-11-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-12 (32 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
Not working also on 4.18.0-17-generic kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638780] Re: Linux 4.8.0-27-generic Eclipse fail
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638780 Title: Linux 4.8.0-27-generic Eclipse fail Status in linux package in Ubuntu: Invalid Bug description: ubuntu-16.10 After updating system, on each launching of Eclipse, system freezed and i have one way - reboot PC. Mouse, keyboord no workin, clock stoped ect. When i booting using Linux 4.8.0-26-generic it OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806223] Re: Black Screen 18.10 Kernel 4.19.1+
Similar report: bug 1803400 ** Package changed: light-locker (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806223 Title: Black Screen 18.10 Kernel 4.19.1+ Status in linux package in Ubuntu: New Bug description: Ubuntu 18.10 Running on VM Fusion 11 latest updates to it, on Imac 2015 Mojave, any kernel past 4.19 example 4.19.1, 4.19.2 it locks to a black screen after boot up and there is nothing u can do. Kernel 4.19 and lower is fine, i went all the way to 4.20 RC4 and black screen no matter what? I googles this and it seems im not the only one with this issue lately? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend
** Bug watch added: freedesktop.org Bugzilla #108703 https://bugs.freedesktop.org/show_bug.cgi?id=108703 ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=108703 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1782177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803268] Re: Ubuntu 18.10 after Blank Screen System Will NOT Unblank
Possibly a duplicate of bug 1801609. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803268 Title: Ubuntu 18.10 after Blank Screen System Will NOT Unblank Status in linux package in Ubuntu: Confirmed Bug description: Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running Xubuntu 18.10. Once the Toshiba's Screen has Blanked, it will not unblank with normal Keystrokes or Mouse Events. My "Work around": Plugging an External Monitor into the Satellite C650's VGA Port, which will then unblank the Toshiba's Screen!!! version.log Ubuntu 4.18.0-10.11-generic 4.18.12 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: houston2335 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 13 22:42:09 2018 InstallationDate: Installed on 2018-11-01 (12 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: TOSHIBA Satellite C650 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=9d27207e-4cea-4a3f-9e73-35d175aa6a19 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd11/21/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC2EC-07J001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C650 dmi.product.sku: PSC2EC-07J001 dmi.product.version: PSC2EC-07J001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802712] Re: Doesn't work a touchpad on Lenovo 330-15IGM 81d1
** Package changed: xfce4-notifyd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802712 Title: Doesn't work a touchpad on Lenovo 330-15IGM 81d1 Status in linux package in Ubuntu: Incomplete Bug description: I think the touchpad doesn't work on linux kernel 4.18 and less, because it works fine with kernel 4.19.1. I'm using Ubuntu 18.10 now. My laptop: https://psref.lenovo.com/Detail/Lenovo_Laptops/ideapad_330_15_Intel?M=81D1003SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend
** Package changed: xfce4-power-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798353] Re: When waking from suspend screen remains blank
Then this is not a bug in xfce4-power-manager which is only active after starting the Xfce session. What hardware is that exactly? ** Package changed: xfce4-power-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798353 Title: When waking from suspend screen remains blank Status in linux package in Ubuntu: New Bug description: After install of Xubuntu 18.04 When placing my laptop into suspend the screen remains blank when I try to wake it. I know that the laptop has woken because the power & cpu lights come on. I am also able to suspend the laptop by using the suspend hotkey. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 451282] Re: display is fully dimmed after resume from suspend
Please open a new report if you still encounter this issue in any of the currently supported Ubuntu releases. ** Changed in: xfce4-power-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/451282 Title: display is fully dimmed after resume from suspend Status in linux package in Ubuntu: Won't Fix Status in xfce4-power-manager package in Ubuntu: Invalid Bug description: Binary package hint: gnome-power-manager When I resume from suspend (while on AC power), the laptop display brightness is set to it's lowest level, even when I had the brightness turned all the way up before. Interestingly enough, this only seems to happen on the first suspend after a reboot. Once I have turned up the display brightness again using the function keys, the next suspend/resume cycle will work normally (until the next reboot). Finally, when I use the function keys to increase the brightness after a suspend, I see that the brightness level in the notification bar indicates that the brightness is set to the maximum. Only after repeated adjustments with the function keys, the indicator 'resets' and reflects the true display brightness level. I'm using the proprietary nvidia display driver, but I've never had this problem before in Jaunty. Also, in case it makes a difference, I've set my laptop to suspend on lid closure since that's the way I generally suspend the laptop. ProblemType: Bug Architecture: amd64 CheckboxSubmission: 464ed6184a4fbf79d6e3084c58b13de8 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Oct 14 09:46:16 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-power-manager 2.28.0-0ubuntu6 ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.46-generic SourcePackage: gnome-power-manager Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591043] Re: xubuntu 16.04 on the haswell platform random restart
Was this issue resolved? ** Package changed: xfdesktop4 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591043 Title: xubuntu 16.04 on the haswell platform random restart Status in linux package in Ubuntu: Incomplete Bug description: Recently，I am use the xubuntu 16.04 on the haswell platform.I found my haswell's device random restart,when log in the xubuntu about 10 minutes,but it doesn't happen every time. The random reboot is similar to use the watchdog(directly power off and then automatically power on ). Now,I can't find any message about this issue. Any help will be grateful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
Looks like the next step would be to test with an older NVIDIA driver version from the Ubuntu repository, and maybe with the slightly newer version 390.77 from the NVIDIA website also. ** Changed in: xfce4 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Invalid Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
I suggested to test with MATE's compositing window manager "marco" also. Any results? Another test case would be to use xfwm4 with disabled compositor plus "compton" (standalone compositing manager). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Incomplete Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
What output do you get when opening the Totem player from a terminal window? The builtin compositor can be disabled via xfwm4-tweaks-settings, and that will most likely prevent the issue from occurring. Other than that, I suggest to test with a different window manager (e.g. "marco --replace", afterwards "xfwm4 --replace"). ** Changed in: xfce4 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Incomplete Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543418] Re: Closing lid causes system hang
Which hardware is that exactly? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1543418 Title: Closing lid causes system hang Status in linux package in Ubuntu: Incomplete Bug description: I have been having this problem for a past few weeks. I have been using this system for almost 1 year. I use with the power setting to suspend my system when I close the lid. In the past few weeks sometimes when I close the lid, the system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid screen will be back and nothing can bring the system back. I have to restart the system by pressing the power key. No key is working during this state. I tried pressing num lock and no response. It happened rarely before. But for past few days, my system has been getting stuck like this more. Before this, I used to have system crash suddenly and lose all data without any reasons. I am fairly new to ubuntu I don't know how to diagnose these things. Please help me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543418] Re: Closing lid causes system hang
Is this problem still present in current Ubuntu releases? ** Package changed: xubuntu-default-settings (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1543418 Title: Closing lid causes system hang Status in linux package in Ubuntu: Incomplete Bug description: I have been having this problem for a past few weeks. I have been using this system for almost 1 year. I use with the power setting to suspend my system when I close the lid. In the past few weeks sometimes when I close the lid, the system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid screen will be back and nothing can bring the system back. I have to restart the system by pressing the power key. No key is working during this state. I tried pressing num lock and no response. It happened rarely before. But for past few days, my system has been getting stuck like this more. Before this, I used to have system crash suddenly and lose all data without any reasons. I am fairly new to ubuntu I don't know how to diagnose these things. Please help me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687274] Re: Boot fails waiting for /dev/disk/by-uuid
Did a kernel update or the upgrade to a newer Ubuntu release resolve this problem? ** Package changed: xubuntu-meta (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687274 Title: Boot fails waiting for /dev/disk/by-uuid Status in linux package in Ubuntu: Incomplete Bug description: The system is stuck waiting 90 seconds for the /dev/disk/by-uuid/* devices to show up. When dropping me to a shell, they do exist. Forcing the system to fsck (by removing power) makes no difference. After rebooting 1-5 times it suddenly completes booting. So it seems it might be a race condition. = Workaround = If I boot once in recovery mode, then the next boot will mostly complete just fine. OK as a workaround, but a horrible solution. I can even just run `systemctl reboot` from recovery mode - no need to boot fully. Running `reboot`, however, does not work. Attached: working$ cat ls-dev-disk-by-uuid working$ cat journalctl-xb failing$ cat ls-dev-disk-by-uuid failing$ cat journalctl-xb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638780] Re: Linux 4.8.0-27-generic Eclipse fail
Was this issue resolved? ** Package changed: xubuntu-meta (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638780 Title: Linux 4.8.0-27-generic Eclipse fail Status in linux package in Ubuntu: Incomplete Bug description: ubuntu-16.10 After updating system, on each launching of Eclipse, system freezed and i have one way - reboot PC. Mouse, keyboord no workin, clock stoped ect. When i booting using Linux 4.8.0-26-generic it OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730321] Re: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730321 Title: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode Status in linux package in Ubuntu: Incomplete Status in xubuntu-meta package in Ubuntu: Invalid Bug description: Below is my setup details: C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs. Installed ESXi 6.0U1b in the boot SSD in AHCI mode. Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00) Created a VM and Installed Ubuntu 14.04.04. AVB card has one RAID1 VD, one JBOD and all other UG drives. Assigned the AVB controller as a Pass thorugh to ESXi host. Added AVB controller as a Pass through device to the Ubuntu VM. Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of AVB card. Updated the Ubuntu VM with the latest MR driver 06.810 I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. But I am unable to see the disks from the VM. I am seeing so many call traces in the console related to megaraid_sas and see the attached screenshots of the same. Avago is able to reproduce the issue in their lab and see the attached email thread on this discussion. Note : The same scenario is working fine with Ubuntu 12.x series VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series guest operating systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1252266] Re: Corrupted low memory after resume from suspend after updating to saucy
Utopic here. [13998.659944] Corrupted low memory at 8800afa8 (afa8 phys) = ff575351ff221f1e [13998.659945] Corrupted low memory at 8800afb0 (afb0 phys) = ffc0bbb8ffbfbab7 [13998.659946] Corrupted low memory at 8800afb8 (afb8 phys) = ff221f1eff948f8c [13998.659947] Corrupted low memory at 8800afc0 (afc0 phys) = ff7e7a77ff736e6c [13998.659948] Corrupted low memory at 8800afc8 (afc8 phys) = ffb3aeabffbeb8b5 [13998.659949] Corrupted low memory at 8800afd0 (afd0 phys) = ff312e2cff474342 [13998.659950] Corrupted low memory at 8800afd8 (afd8 phys) = ff2d2b2aff252221 [13998.659951] Corrupted low memory at 8800afe0 (afe0 phys) = ffb0a9a7ff575352 etc Lots of this (3k). Linux widly 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ** Changed in: linux (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1252266 Title: Corrupted low memory after resume from suspend after updating to saucy Status in “linux” package in Ubuntu: Confirmed Bug description: After upgrading to saucy and Linux 3.11 my Gigabyte 965P-DS3 board no longer properly resumes from suspend. The desktop still works fine after resume, but the ethernet interface won't come up again. dmesg after resume warns about corrupted low memory: [40560.864036] [ cut here ] [40560.864044] WARNING: CPU: 0 PID: 24687 at /build/buildd/linux-3.11.0/arch/x86/kernel/check.c:140 check_for_bios_corruption+0x10f/0x120() [40560.864046] Memory corruption detected in low memory [40560.864048] Modules linked in: pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) cuse ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_conntrack(F) nf_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) bridge(F) stp(F) llc(F) ip6table_filter(F) ip6_tables(F) iptable_filter(F) ip_tables(F) ebtable_nat(F) ebtables(F) x_tables(F) joydev(F) xpad ff_memless hid_generic usbhid hid rfcomm bnep bluetooth binfmt_misc(F) kvm_intel(F) kvm(F) gpio_ich ppdev(F) ir_lirc_codec lirc_dev ir_sanyo_decoder ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder e4000 rtl2832 usb_storage(F) snd_usb_audio snd_usbmidi_lib uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dvb_usb_rtl28xxu rtl2830 dvb_usb_v2 dvb_core rc_core snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) microcode(F) pcspkr serio_raw(F) snd_rawmidi(F) snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) lpc_ich soundcore(F) nvidia(POF) parport_pc(F) drm mac_hid it87 hwmon_vid coretemp lp(F) parport(F) pata_acpi sky2 pata_jmicron ahci(F) libahci(F) [40560.864148] CPU: 0 PID: 24687 Comm: kworker/0:1 Tainted: PF W O 3.11.0-13-generic #20-Ubuntu [40560.864151] Hardware name: Gigabyte Technology Co., Ltd. 965P-DS3/965P-DS3, BIOS F14d 12/18/2008 [40560.864155] Workqueue: events check_corruption [40560.864158] 0009 880064be9d30 816e54ba 880064be9d78 [40560.864162] 880064be9d68 81061dbd 8801 [40560.864166] 81ea73b0 0001 8800 880064be9dc8 [40560.864171] Call Trace: [40560.864178] [816e54ba] dump_stack+0x45/0x56 [40560.864183] [81061dbd] warn_slowpath_common+0x7d/0xa0 [40560.864187] [81061e2c] warn_slowpath_fmt+0x4c/0x50 [40560.864191] [8104e5bf] check_for_bios_corruption+0x10f/0x120 [40560.864195] [8104e5de] check_corruption+0xe/0x40 [40560.864200] [8107d05c] process_one_work+0x17c/0x430 [40560.864204] [8107dcac] worker_thread+0x11c/0x3c0 [40560.864208] [8107db90] ? manage_workers.isra.24+0x2a0/0x2a0 [40560.864212] [810847b0] kthread+0xc0/0xd0 [40560.864217] [810846f0] ? kthread_create_on_node+0x120/0x120 [40560.864221] [816f51ec] ret_from_fork+0x7c/0xb0 [40560.864225] [810846f0] ? kthread_create_on_node+0x120/0x120 [40560.864228] ---[ end trace a5d0e3f4744a1e9d ]--- This did not happen with raring/Linux 3.8 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: benpicco 3071 F pulseaudio /dev/snd/controlC0: benpicco 3071 F pulseaudio Date: Mon Nov 18 14:12:08 2013 HibernationDevice:
