[Kernel-packages] [Bug 1715552] Re: VMWare does not start
It works with VMware 14. -- 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/1715552 Title: VMWare does not start Status in linux package in Ubuntu: Confirmed Bug description: Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started: /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux- gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC symbol `clock_gettime' Works under Ubuntu 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-13-generic 4.12.0-13.14 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 9336 F pulseaudio /dev/snd/controlC0: wolf 9336 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 07:53:43 2017 HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.12.0-13-generic N/A linux-backports-modules-4.12.0-13-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+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 759725] Re: The kernel is no longer readable by non-root users
A consequence of the design decision to prevent read-access for users is that a bug has emerged in libguestfs: https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1813662 -- 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/759725 Title: The kernel is no longer readable by non-root users Status in linux package in Ubuntu: Won't Fix Bug description: The mode of the latest kernel has changed so it is no longer readable by non-root users: -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 /boot/vmlinuz-2.6.35-22-generic -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 /boot/vmlinuz-2.6.35-23-generic -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic This prevents people from using this kernel to boot qemu virtual machines as non-root. Please change the mode back to make the kernel readable. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:240: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:240: no soundcards found... CRDA: Error: [Errno 2] No such file or directory Date: Wed Apr 13 13:05:01 2011 HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM PciMultimedia: ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash RelatedPackageVersions: linux-restricted-modules-2.6.35-22-generic N/A linux-backports-modules-2.6.35-22-generic N/A linux-firmware 1.50 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr: dmi.product.name: KVM dmi.product.version: RHEL 6.0.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+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 1700621] Re: System freezes and crashes when enabling USB network
Many years later: I have now tried with a newer kernel and a newer VMware. the problem does not exist anymore. Cleaning up and closing ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1700621 Title: System freezes and crashes when enabling USB network Status in linux package in Ubuntu: Fix Released Bug description: I have my Android (Google pixel) attached via USB cable. Now I want to use the network from the android using USB. So (on the android device) I turn on "Network sharing via USB" and boom my ubuntu crashes and I find "BUG: stack guard page was hit at b691c54981c0 (stack is b691c5494000..b691c5497fff)" in /var/log/kern.log It is 100% reproducible every time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 2901 F pulseaudio /dev/snd/controlC0: jarl 2901 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 26 19:39:37 2017 HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88 InstallationDate: Installed on 2016-01-08 (534 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System76, Inc. Oryx Pro ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-19 (67 days ago) dmi.bios.date: 02/02/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: orxp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: orxp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700621/+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 1736023] Re: Graphics is corrupt on VT1-VT7 even during boot
After upgrading ubuntu to 18.04 I can no longer reproduce this problem using unmodified package-installed grub files. So if nobody else can reproduce this problem I suggest it is closed as fixed in 18.04. -- 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/1736023 Title: Graphics is corrupt on VT1-VT7 even during boot Status in grub2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: This is on an Acer Aspire One (https://en.wikipedia.org/wiki/Acer_Aspire_One) after upgrading from ubuntu 17.04 to 17.10 When booting. At the time where the load screen flashing "Kubuntu" is normally displayed, the graphics is corrupted. Both on text terminals VT1-VT6 and graphics terminal VT7 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CurrentDesktop: KDE Date: Sun Dec 3 20:44:14 2017 InstallationDate: Installed on 2014-12-15 (1084 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) SourcePackage: grub2 UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1736023/+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 1736023] Re: Graphics is corrupt on VT1-VT7 even during boot
I change status to fixed released as per comment#11 ** Changed in: grub2 (Ubuntu) Status: Expired => Fix Released ** Changed in: linux (Ubuntu) Status: Expired => Fix Released -- 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/1736023 Title: Graphics is corrupt on VT1-VT7 even during boot Status in grub2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This is on an Acer Aspire One (https://en.wikipedia.org/wiki/Acer_Aspire_One) after upgrading from ubuntu 17.04 to 17.10 When booting. At the time where the load screen flashing "Kubuntu" is normally displayed, the graphics is corrupted. Both on text terminals VT1-VT6 and graphics terminal VT7 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CurrentDesktop: KDE Date: Sun Dec 3 20:44:14 2017 InstallationDate: Installed on 2014-12-15 (1084 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) SourcePackage: grub2 UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1736023/+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 1700621] [NEW] System freezes and crashes when enabling USB network
Public bug reported: I have my Android (Google pixel) attached via USB cable. Now I want to use the network from the android using USB. So (on the android device) I turn on "Network sharing via USB" and boom my ubuntu crashes and I find "BUG: stack guard page was hit at b691c54981c0 (stack is b691c5494000..b691c5497fff)" in /var/log/kern.log It is 100% reproducible every time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 2901 F pulseaudio /dev/snd/controlC0: jarl 2901 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 26 19:39:37 2017 HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88 InstallationDate: Installed on 2016-01-08 (534 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System76, Inc. Oryx Pro ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-19 (67 days ago) dmi.bios.date: 02/02/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: orxp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: orxp1 dmi.sys.vendor: System76, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Description changed: I have my Android (Google pixel) attached via USB cable. Now I want to use the network from the android using USB. So (on the android device) I - turn on "Network sharing via USB" and boom my ubuntu crashes. + turn on "Network sharing via USB" and boom my ubuntu crashes and I find + "BUG: stack guard page was hit at b691c54981c0 (stack is + b691c5494000..b691c5497fff)" in /var/log/kern.log It is 100% reproducible every time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jarl 2901 F pulseaudio - /dev/snd/controlC0: jarl 2901 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: jarl 2901 F pulseaudio + /dev/snd/controlC0: jarl 2901 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 26 19:39:37 2017 HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88 InstallationDate: Installed on 2016-01-08 (534 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System76, Inc. Oryx Pro ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.10.0-24-generic N/A - linux-backports-modules-4.10.0-24-generic N/A - linux-firmware 1.164.1 + linux-restricted-modules-4.10.0-24-generic N/A + linux-backports-modules-4.10.0-24-generic N/A + linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-19 (67 days ago) dmi.bios.date: 02/02/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: orxp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: orxp1 dmi.sys.vendor: System76, Inc. -- You rece
[Kernel-packages] [Bug 1700621] Re: System freezes and crashes when enabling USB network
Attached is snippet from /var/log/kern.log ** Attachment added: "snippet from /var/log/kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700621/+attachment/4903730/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700621 Title: System freezes and crashes when enabling USB network Status in linux package in Ubuntu: New Bug description: I have my Android (Google pixel) attached via USB cable. Now I want to use the network from the android using USB. So (on the android device) I turn on "Network sharing via USB" and boom my ubuntu crashes and I find "BUG: stack guard page was hit at b691c54981c0 (stack is b691c5494000..b691c5497fff)" in /var/log/kern.log It is 100% reproducible every time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 2901 F pulseaudio /dev/snd/controlC0: jarl 2901 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 26 19:39:37 2017 HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88 InstallationDate: Installed on 2016-01-08 (534 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System76, Inc. Oryx Pro ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-19 (67 days ago) dmi.bios.date: 02/02/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: orxp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: orxp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700621/+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 1700621] Re: System freezes and crashes when enabling USB network
@kaihengfeng: It has worked with previous versions of ubuntu, but it is quite some time ago I used this feature (> 1 year), but that was with a micros USB 2.0, this time it is with a USB-C cable. I don't know if that changes anything. I have tried again with the new kernel 4.10.0-26-generic with same deterministic result. Could you give precise instructions on how try the kernels you have linked? And just to emphasize The kernels seems to be for xenial, I am running Zesty. -- 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/1700621 Title: System freezes and crashes when enabling USB network Status in linux package in Ubuntu: Confirmed Bug description: I have my Android (Google pixel) attached via USB cable. Now I want to use the network from the android using USB. So (on the android device) I turn on "Network sharing via USB" and boom my ubuntu crashes and I find "BUG: stack guard page was hit at b691c54981c0 (stack is b691c5494000..b691c5497fff)" in /var/log/kern.log It is 100% reproducible every time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 2901 F pulseaudio /dev/snd/controlC0: jarl 2901 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 26 19:39:37 2017 HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88 InstallationDate: Installed on 2016-01-08 (534 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System76, Inc. Oryx Pro ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-19 (67 days ago) dmi.bios.date: 02/02/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: orxp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: orxp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700621/+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 1700621] Re: System freezes and crashes when enabling USB network
@kaihengfeng: Or try without VMware installed (remove vmnet completely), correct? -- 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/1700621 Title: System freezes and crashes when enabling USB network Status in linux package in Ubuntu: Confirmed Bug description: I have my Android (Google pixel) attached via USB cable. Now I want to use the network from the android using USB. So (on the android device) I turn on "Network sharing via USB" and boom my ubuntu crashes and I find "BUG: stack guard page was hit at b691c54981c0 (stack is b691c5494000..b691c5497fff)" in /var/log/kern.log It is 100% reproducible every time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 2901 F pulseaudio /dev/snd/controlC0: jarl 2901 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 26 19:39:37 2017 HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88 InstallationDate: Installed on 2016-01-08 (534 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System76, Inc. Oryx Pro ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-19 (67 days ago) dmi.bios.date: 02/02/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: orxp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: orxp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700621/+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 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
I have now tried with the latest rc5 kernel `Linux hermes 4.4.0-040400rc5-generic #201512140221 SMP Mon Dec 14 02:23:36 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux` The problem/symptoms are still the same. Jarl ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Confirmed Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 1333416] [NEW] [rt2561/rt61] cannot connect with wifi
Public bug reported: Now when I have installed Kubuntu 14.04 from DVD the wifi will not connect. The access points are shown in the list of available access points, but it will not connect. The odd thing is that during installation, the wifi was detected and connected without any problems to the access point. I wonder if the installation process was using another kernel. Jarl ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 1950 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 23 22:43:44 2014 HibernationDevice: RESUME=/dev/sda2 InstallationDate: Installed on 2014-06-14 (9 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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 MachineType: NOTEBOOK SAM2000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=ba94e7d4-274a-40b8-b1c7-9cc9d5479186 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1013AM7 V6.40 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1013AM7V6.40:bd11/01/2005:svnNOTEBOOK:pnSAM2000:pvr0131:cvnMICRO-STARINT'LCO.,LTD:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2000 dmi.product.version: 0131 dmi.sys.vendor: NOTEBOOK ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1333416 Title: [rt2561/rt61] cannot connect with wifi Status in “linux” package in Ubuntu: New Bug description: Now when I have installed Kubuntu 14.04 from DVD the wifi will not connect. The access points are shown in the list of available access points, but it will not connect. The odd thing is that during installation, the wifi was detected and connected without any problems to the access point. I wonder if the installation process was using another kernel. Jarl ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 1950 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 23 22:43:44 2014 HibernationDevice: RESUME=/dev/sda2 InstallationDate: Installed on 2014-06-14 (9 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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 MachineType: NOTEBOOK SAM2000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=ba94e7d4-274a-40b8-b1c7-9cc9d5479186 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1013AM7 V6.40 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1013AM7V6.40:bd11/01/2005:svnNOTEBOOK:pnSAM2000:pvr0131:cvnMICRO-STARINT'LCO.,LTD:ct10:cvrToBeFil
[Kernel-packages] [Bug 1333416] Re: [rt2561/rt61] cannot connect with wifi
This is really weird... The SSID I am trying to connect to is "FreeNet" it is an open wifi without security; there it fails. When I try to connect to another SSID with WPA2 wireless security it works fine. However, I must repeat again that during installation I connected to "FreeNet" without problems, and I have other 14.04 installations (on different wifi hardware) that connects fine to "FreeNet". -- 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/1333416 Title: [rt2561/rt61] cannot connect with wifi Status in “linux” package in Ubuntu: Confirmed Bug description: Now when I have installed Kubuntu 14.04 from DVD the wifi will not connect. The access points are shown in the list of available access points, but it will not connect. The odd thing is that during installation, the wifi was detected and connected without any problems to the access point. I wonder if the installation process was using another kernel. Jarl ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 1950 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 23 22:43:44 2014 HibernationDevice: RESUME=/dev/sda2 InstallationDate: Installed on 2014-06-14 (9 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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 MachineType: NOTEBOOK SAM2000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=ba94e7d4-274a-40b8-b1c7-9cc9d5479186 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1013AM7 V6.40 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1013AM7V6.40:bd11/01/2005:svnNOTEBOOK:pnSAM2000:pvr0131:cvnMICRO-STARINT'LCO.,LTD:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2000 dmi.product.version: 0131 dmi.sys.vendor: NOTEBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333416/+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 1333416] Re: [rt2561/rt61] cannot connect with wifi
I am sorry if I have wasted anyones time. It tutned out that the router providing the "FreeNet" SSID hung soon after the installation, that is what caused the strange experiences (the other laptops could not connect either) , rebooting the router solved the problem Sorry, I will closing this issue. ** Changed in: linux (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/1333416 Title: [rt2561/rt61] cannot connect with wifi Status in “linux” package in Ubuntu: Invalid Bug description: Now when I have installed Kubuntu 14.04 from DVD the wifi will not connect. The access points are shown in the list of available access points, but it will not connect. The odd thing is that during installation, the wifi was detected and connected without any problems to the access point. I wonder if the installation process was using another kernel. Jarl ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 1950 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 23 22:43:44 2014 HibernationDevice: RESUME=/dev/sda2 InstallationDate: Installed on 2014-06-14 (9 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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 MachineType: NOTEBOOK SAM2000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=ba94e7d4-274a-40b8-b1c7-9cc9d5479186 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1013AM7 V6.40 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1013AM7V6.40:bd11/01/2005:svnNOTEBOOK:pnSAM2000:pvr0131:cvnMICRO-STARINT'LCO.,LTD:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2000 dmi.product.version: 0131 dmi.sys.vendor: NOTEBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333416/+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 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
It's no so easy to update the BIOS when Ubuntu is installed, working on it, hang on, I'll be there. -- 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/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Incomplete Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 1424261] [NEW] usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
Public bug reported: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: "output of `lsusb -v -d 090c:6200`" https://bugs.launchpad.net/bugs/1424261/+attachment/4324181/+files/sdcardreader.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: New Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x
[Kernel-packages] [Bug 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
First time I tried to use thsi SD card reader was about a year ago (13.10) where I also had this problem (same hardware), and the situation has not changed (i.e. all kernels through Ubuntu 14.04 and now 14.10. The reason I have not repported this before is lack of time of root- cause investigation. For quite some time I was mislead/confused by the 32GB limitation of the FAT file system and not-so-mature linux implementation of the exFAT file system. So this problem did not just start happening, it has never worked correct for me. > Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0]. Yes, I have try to use the v4.0-rc1 kernel downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/ with no effect the behaviour is identical. Therefore I add the tag 'kernel-bug- exists-upstream'. ** Tags added: kernel-bug-exists-upstream -- 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/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Confirmed Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Confirmed Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 1265151] [NEW] rt2800pci doesn't work after upgrading to 13.10
Public bug reported: After upgrading to 13.10 wifi no longer works for rt2800pci (RT3290) To me it looks like this problem: http://www.spinics.net/lists/linux-wireless/msg113047.html $ lsb_releasee -rd Description:Ubuntu 13.10 Release:13.10 $ apt-cache policy linux linux: Installeret: (ingen) Kandidat:3.11.0.14.15 Versionstabel: 3.11.0.14.15 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 3.11.0.12.13 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages I expected wifi to work as in 13.04, but it is unstable and in is deactivated after some time. I can reproduce the problem with $ sudo rmmod rt2800pci $ sudo modprobe rt2800pci after that WIFI works for some seconds or minutes, then it is disconnected. the dmesg output is like this but it varies a bit... [ 360.455741] rt2800pci :04:00.0: irq 56 for MSI/MSI-X [ 360.455823] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 360.459348] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 3290 detected [ 360.459674] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 360.471808] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 360.471870] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 360.517677] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 360.518267] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 362.601583] wlan0: authenticate with 00:18:e7:8a:55:2b [ 362.616562] wlan0: send auth to 00:18:e7:8a:55:2b (try 1/3) [ 362.617959] wlan0: authenticated [ 362.620409] wlan0: associate with 00:18:e7:8a:55:2b (try 1/3) [ 362.624016] wlan0: RX AssocResp from 00:18:e7:8a:55:2b (capab=0x431 status=0 aid=2) [ 362.624103] wlan0: associated [ 362.624156] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.156373] r8169 :02:00.0 eth0: link down [ 476.091171] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.251186] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.639219] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.799146] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.807303] cfg80211: Calling CRDA to update world regulatory domain [ 476.813452] cfg80211: World regulatory domain updated: [ 476.813459] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 476.813464] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813468] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813472] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 476.813475] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813478] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 477.059262] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.219205] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 477.379126] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.539122] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 478.759324] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 478.919410] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 483.755832] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 483.915844] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 484.235771] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 1860 F pulseaudio /dev/snd/controlC0: jarl 1860 F pulseaudio Date: Tue Dec 31 09:11:38 2013 HibernationDevice: RESUME=UUID=92f3c741-1bd3-4762-a2c1-59d27eef756c InstallationDate: Installed on 2013-12-28 (2 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ProBook 455 G1 MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=3f5bd5b6-65b8-4ea5-bf33-4a8a7bf79b52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A
[Kernel-packages] [Bug 1265151] Re: rt2800pci doesn't work after upgrading to 13.10
_queue: Warning - Queue 2 failed to flush [ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 484.235771] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 1860 F pulseaudio /dev/snd/controlC0: jarl 1860 F pulseaudio Date: Tue Dec 31 09:11:38 2013 HibernationDevice: RESUME=UUID=92f3c741-1bd3-4762-a2c1-59d27eef756c InstallationDate: Installed on 2013-12-28 (2 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ProBook 455 G1 MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=3f5bd5b6-65b8-4ea5-bf33-4a8a7bf79b52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 RfKill: 4: phy4: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.02:bd04/26/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2019DD203:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2019DD203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265151/+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 1049466] Re: Need support of Ralink RT3290 wifi support
Since this bug is about support for RT3290 and I have seen RT3290 to be working fine in 13.04 I consider the support for RT3290 to be in place. However In Ubuntu 13.10 there seems to be a bug introduced with kernel 3.11, so I have created a separate bug for that at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265151 I don't know whether that is the correct way to do it, please feel free to mark it as duplicate if that is the correct thing to do. At lease I find it usefull that others have identified what I believe it the offending commit in the kernel: http://www.spinics.net/lists/linux-wireless/msg113047.html -- 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/1049466 Title: Need support of Ralink RT3290 wifi support Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Confirmed Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Invalid Status in “linux-firmware” source package in Precise: Fix Released Status in “linux” source package in Quantal: Invalid Status in “linux-firmware” source package in Quantal: Won't Fix Status in “linux” source package in Raring: Fix Released Status in “linux-firmware” source package in Raring: Fix Released Status in “linux” package in Baltix: Opinion Status in “linux” package in Gentoo Linux: New Bug description: RT3290 wifi chip is becoming common on consumer notebooks. Its support starts from 3.6 so support on 12.10 may need lbm-cw. commit a89534edaaa7008992b878680490e9b02a665563 Author: Woody Hung Date: Wed Jun 13 15:01:16 2012 +0800 rt2x00 : RT3290 chip support v4 This patch support the new chipset rt3290 wifi implementation in rt2x00. It initailize the related mac, bbp and rf register in startup phase. And this patch modify the efuse read/write method for the different efuse data offset of rt3290. Signed-off-by: Woody Hung Signed-off-by: John W. Linville To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1049466/+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 1265151] Re: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10
Thanks a lot for the verify specific links, especially https://help.ubuntu.com/community/BiosUpdate, I didn't know. I will update the BIOS later today and get back. -- 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/1265151 Title: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to 13.10 wifi no longer works for rt2800pci (RT3290) To me it looks like this problem: http://www.spinics.net/lists/linux-wireless/msg113047.html $ lsb_releasee -rd Description:Ubuntu 13.10 Release:13.10 $ apt-cache policy linux linux: Installeret: (ingen) Kandidat:3.11.0.14.15 Versionstabel: 3.11.0.14.15 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 3.11.0.12.13 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages I expected wifi to work as in 13.04, but it is unstable and in is deactivated after some time. I can reproduce the problem with $ sudo rmmod rt2800pci $ sudo modprobe rt2800pci after that WIFI works for some seconds or minutes, then it is disconnected. the dmesg output is like this but it varies a bit... [ 360.455741] rt2800pci :04:00.0: irq 56 for MSI/MSI-X [ 360.455823] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 360.459348] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 3290 detected [ 360.459674] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 360.471808] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 360.471870] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 360.517677] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 360.518267] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 362.601583] wlan0: authenticate with 00:18:e7:8a:55:2b [ 362.616562] wlan0: send auth to 00:18:e7:8a:55:2b (try 1/3) [ 362.617959] wlan0: authenticated [ 362.620409] wlan0: associate with 00:18:e7:8a:55:2b (try 1/3) [ 362.624016] wlan0: RX AssocResp from 00:18:e7:8a:55:2b (capab=0x431 status=0 aid=2) [ 362.624103] wlan0: associated [ 362.624156] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.156373] r8169 :02:00.0 eth0: link down [ 476.091171] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.251186] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.639219] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.799146] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.807303] cfg80211: Calling CRDA to update world regulatory domain [ 476.813452] cfg80211: World regulatory domain updated: [ 476.813459] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 476.813464] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813468] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813472] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 476.813475] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813478] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 477.059262] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.219205] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 477.379126] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.539122] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 478.759324] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 478.919410] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 483.755832] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 483.915844] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 484.235771] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd
[Kernel-packages] [Bug 1265151] Re: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10
I updated the BIOS, it doesn't help... After BIOS update: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 68CPE Ver. F.24 10/18/2013 The problem seems to be introduced in kernel 3.11 and solved in 3.12. Are there any plans on updating ubuntu official kernel to 3.12? Jarl -- 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/1265151 Title: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to 13.10 wifi no longer works for rt2800pci (RT3290) To me it looks like this problem: http://www.spinics.net/lists/linux-wireless/msg113047.html $ lsb_releasee -rd Description:Ubuntu 13.10 Release:13.10 $ apt-cache policy linux linux: Installeret: (ingen) Kandidat:3.11.0.14.15 Versionstabel: 3.11.0.14.15 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 3.11.0.12.13 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages I expected wifi to work as in 13.04, but it is unstable and in is deactivated after some time. I can reproduce the problem with $ sudo rmmod rt2800pci $ sudo modprobe rt2800pci after that WIFI works for some seconds or minutes, then it is disconnected. the dmesg output is like this but it varies a bit... [ 360.455741] rt2800pci :04:00.0: irq 56 for MSI/MSI-X [ 360.455823] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 360.459348] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 3290 detected [ 360.459674] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 360.471808] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 360.471870] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 360.517677] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 360.518267] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 362.601583] wlan0: authenticate with 00:18:e7:8a:55:2b [ 362.616562] wlan0: send auth to 00:18:e7:8a:55:2b (try 1/3) [ 362.617959] wlan0: authenticated [ 362.620409] wlan0: associate with 00:18:e7:8a:55:2b (try 1/3) [ 362.624016] wlan0: RX AssocResp from 00:18:e7:8a:55:2b (capab=0x431 status=0 aid=2) [ 362.624103] wlan0: associated [ 362.624156] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.156373] r8169 :02:00.0 eth0: link down [ 476.091171] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.251186] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.639219] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.799146] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.807303] cfg80211: Calling CRDA to update world regulatory domain [ 476.813452] cfg80211: World regulatory domain updated: [ 476.813459] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 476.813464] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813468] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813472] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 476.813475] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813478] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 477.059262] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.219205] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 477.379126] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.539122] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 478.759324] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 478.919410] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 483.755832] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 483.915844] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 484.235771] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernel
[Kernel-packages] [Bug 1265151] Re: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10
Should I change status to "New" now that I have provided the requested info? -- 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/1265151 Title: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to 13.10 wifi no longer works for rt2800pci (RT3290) To me it looks like this problem: http://www.spinics.net/lists/linux-wireless/msg113047.html $ lsb_releasee -rd Description:Ubuntu 13.10 Release:13.10 $ apt-cache policy linux linux: Installeret: (ingen) Kandidat:3.11.0.14.15 Versionstabel: 3.11.0.14.15 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 3.11.0.12.13 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages I expected wifi to work as in 13.04, but it is unstable and in is deactivated after some time. I can reproduce the problem with $ sudo rmmod rt2800pci $ sudo modprobe rt2800pci after that WIFI works for some seconds or minutes, then it is disconnected. the dmesg output is like this but it varies a bit... [ 360.455741] rt2800pci :04:00.0: irq 56 for MSI/MSI-X [ 360.455823] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 360.459348] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 3290 detected [ 360.459674] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 360.471808] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 360.471870] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 360.517677] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 360.518267] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 362.601583] wlan0: authenticate with 00:18:e7:8a:55:2b [ 362.616562] wlan0: send auth to 00:18:e7:8a:55:2b (try 1/3) [ 362.617959] wlan0: authenticated [ 362.620409] wlan0: associate with 00:18:e7:8a:55:2b (try 1/3) [ 362.624016] wlan0: RX AssocResp from 00:18:e7:8a:55:2b (capab=0x431 status=0 aid=2) [ 362.624103] wlan0: associated [ 362.624156] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.156373] r8169 :02:00.0 eth0: link down [ 476.091171] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.251186] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.639219] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.799146] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.807303] cfg80211: Calling CRDA to update world regulatory domain [ 476.813452] cfg80211: World regulatory domain updated: [ 476.813459] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 476.813464] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813468] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813472] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 476.813475] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813478] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 477.059262] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.219205] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 477.379126] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.539122] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 478.759324] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 478.919410] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 483.755832] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 483.915844] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 484.235771] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarl 1860 F pulseaudio /dev/snd/controlC0: jarl 1860 F
[Kernel-packages] [Bug 1265151] Re: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10
I have update to the latest kernel using the steps in http://ubuntuhandbook.org/index.php/2013/11/linux-kernel-3-12-released- install-ubuntu-or-linux-mint/ (Thanks Ivo) That solved my problem. Christopher, Are you serious? you are asking me to completely wipe my ubuntu installation and reinstall from scratch the daily CD image to see if that solves the problem. It has been confirmed now by three sources that kernel 3.12 solves the problem, isn't that sufficient information? I trust that if daily CD has kernel 3.11 the problem is there, if it has kernel 3.12 the problem is not there. Jarl -- 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/1265151 Title: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to 13.10 wifi no longer works for rt2800pci (RT3290) To me it looks like this problem: http://www.spinics.net/lists/linux-wireless/msg113047.html $ lsb_releasee -rd Description:Ubuntu 13.10 Release:13.10 $ apt-cache policy linux linux: Installeret: (ingen) Kandidat:3.11.0.14.15 Versionstabel: 3.11.0.14.15 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 3.11.0.12.13 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages I expected wifi to work as in 13.04, but it is unstable and in is deactivated after some time. I can reproduce the problem with $ sudo rmmod rt2800pci $ sudo modprobe rt2800pci after that WIFI works for some seconds or minutes, then it is disconnected. the dmesg output is like this but it varies a bit... [ 360.455741] rt2800pci :04:00.0: irq 56 for MSI/MSI-X [ 360.455823] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 360.459348] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 3290 detected [ 360.459674] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 360.471808] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 360.471870] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 360.517677] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 360.518267] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 362.601583] wlan0: authenticate with 00:18:e7:8a:55:2b [ 362.616562] wlan0: send auth to 00:18:e7:8a:55:2b (try 1/3) [ 362.617959] wlan0: authenticated [ 362.620409] wlan0: associate with 00:18:e7:8a:55:2b (try 1/3) [ 362.624016] wlan0: RX AssocResp from 00:18:e7:8a:55:2b (capab=0x431 status=0 aid=2) [ 362.624103] wlan0: associated [ 362.624156] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.156373] r8169 :02:00.0 eth0: link down [ 476.091171] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.251186] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.639219] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.799146] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.807303] cfg80211: Calling CRDA to update world regulatory domain [ 476.813452] cfg80211: World regulatory domain updated: [ 476.813459] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 476.813464] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813468] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813472] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 476.813475] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813478] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 477.059262] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.219205] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 477.379126] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.539122] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 478.759324] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 478.919410] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 483.755832] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 483.915844] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[Kernel-packages] [Bug 1265151] Re: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10
I tend to agree with Ivo, this bug report is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245819 (though it is a slightly different computer model) -- 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/1265151 Title: 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to 13.10 wifi no longer works for rt2800pci (RT3290) To me it looks like this problem: http://www.spinics.net/lists/linux-wireless/msg113047.html $ lsb_releasee -rd Description:Ubuntu 13.10 Release:13.10 $ apt-cache policy linux linux: Installeret: (ingen) Kandidat:3.11.0.14.15 Versionstabel: 3.11.0.14.15 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 3.11.0.12.13 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages I expected wifi to work as in 13.04, but it is unstable and in is deactivated after some time. I can reproduce the problem with $ sudo rmmod rt2800pci $ sudo modprobe rt2800pci after that WIFI works for some seconds or minutes, then it is disconnected. the dmesg output is like this but it varies a bit... [ 360.455741] rt2800pci :04:00.0: irq 56 for MSI/MSI-X [ 360.455823] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 360.459348] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 3290 detected [ 360.459674] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 360.471808] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 360.471870] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 360.517677] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 360.518267] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 362.601583] wlan0: authenticate with 00:18:e7:8a:55:2b [ 362.616562] wlan0: send auth to 00:18:e7:8a:55:2b (try 1/3) [ 362.617959] wlan0: authenticated [ 362.620409] wlan0: associate with 00:18:e7:8a:55:2b (try 1/3) [ 362.624016] wlan0: RX AssocResp from 00:18:e7:8a:55:2b (capab=0x431 status=0 aid=2) [ 362.624103] wlan0: associated [ 362.624156] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.156373] r8169 :02:00.0 eth0: link down [ 476.091171] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.251186] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.639219] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 476.799146] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 476.807303] cfg80211: Calling CRDA to update world regulatory domain [ 476.813452] cfg80211: World regulatory domain updated: [ 476.813459] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 476.813464] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813468] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813472] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 476.813475] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 476.813478] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 477.059262] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.219205] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 477.379126] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 477.539122] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 478.759324] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 478.919410] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 483.755832] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 483.915844] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush [ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 484.235771] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/cont
[Kernel-packages] [Bug 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
I have now (finally) updated the BIOS to the latest F.20 (mentioned in comment #5). I have further upgraded to the latest ubuntu 15.10 with kernel Linux hermes 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The hardware, the symptoms and the problem is still the same. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Confirmed Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
The output from `sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date` is 68PAD Ver. F.20 12/07/2011 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Confirmed Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 2042996] [NEW] After upgrading to 23.10 the system does not suspend when lid is taken down
Public bug reported:
Normally I use the nvidia-driver but to take proprietary binary drivers
out of the equation. I have now uninstalled that and is reporting this
bug without the proprietary binary driver.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 7560 F wireplumber
/dev/snd/controlC1: jarl 7560 F wireplumber
/dev/snd/seq:jarl 7557 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 07:58:08 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
nvidia.NVreg_EnableBacklightHandler=1 quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
dmi.bios.date: 02/02/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: orxp1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:br5.11:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: orxp1
dmi.sys.vendor: System76, Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2042996
Title:
After upgrading to 23.10 the system does not suspend when lid is taken
down
Status in linux package in Ubuntu:
New
Bug description:
Normally I use the nvidia-driver but to take proprietary binary
drivers out of the equation. I have now uninstalled that and is
reporting this bug without the proprietary binary driver.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jarl 7560 F wireplumber
/dev/snd/controlC1: jarl 7560 F wireplumber
/dev/snd/seq:jarl 7557 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 07:58:08 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
nvidia.NVreg_EnableBacklightHandler=1 quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
[Kernel-packages] [Bug 2042998] [NEW] After upgrading to 23.10 the system does not resume after suspend
Public bug reported:
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 5102 F wireplumber
/dev/snd/controlC1: jarl 5102 F wireplumber
/dev/snd/seq:jarl 5099 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 08:19:03 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
dmi.bios.date: 02/02/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: orxp1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:br5.11:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: orxp1
dmi.sys.vendor: System76, Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2042998
Title:
After upgrading to 23.10 the system does not resume after suspend
Status in linux package in Ubuntu:
New
Bug description:
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jarl 5102 F wireplumber
/dev/snd/controlC1: jarl 5102 F wireplumber
/dev/snd/seq:jarl 5099 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 08:19:03 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
[Kernel-packages] [Bug 2042998] Re: After upgrading to 23.10 the system does not resume after suspend
** Description changed:
+ It seems to suspend fine (when closing lid), but when opening lid it
+ tries to startup... LEDs are blinking (as the HDD is activated), after
+ some time it is working hard because the fan starts running faster and
+ faster. No reaction on any keys. Tried the power button, CTRL+ALT+F1-F8,
+ but no reaction. Only option is to restart by holding power button down
+ for 4 seconds.
+
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: jarl 5102 F wireplumber
- /dev/snd/controlC1: jarl 5102 F wireplumber
- /dev/snd/seq:jarl 5099 F pipewire
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: jarl 5102 F wireplumber
+ /dev/snd/controlC1: jarl 5102 F wireplumber
+ /dev/snd/seq:jarl 5099 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 08:19:03 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
- Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
- Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
+ Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
+ Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
- linux-restricted-modules-6.5.0-10-generic N/A
- linux-backports-modules-6.5.0-10-generic N/A
- linux-firmware20230919.git3672ccab-0ubuntu2.1
+ linux-restricted-modules-6.5.0-10-generic N/A
+ linux-backports-modules-6.5.0-10-generic N/A
+ linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
dmi.bios.date: 02/02/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: orxp1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:br5.11:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: orxp1
dmi.sys.vendor: System76, Inc.
--
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/2042998
Title:
After upgrading to 23.10 the system does not resume after suspend
Status in linux package in Ubuntu:
New
Bug description:
It seems to suspend fine (when closing lid), but when opening lid it
tries to startup... LEDs are blinking (as the HDD is activated), after
some time it is working hard because the fan starts running faster and
faster. No reaction on any keys. Tried the power button,
CTRL+ALT+F1-F8, but no reaction. Only option is to restart by holding
power button down for 4 seconds.
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-ge
[Kernel-packages] [Bug 2017980] [NEW] Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Public bug reported: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) ** Affects: linux-meta-nvidia-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: New Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I get "permission denied" on the chrome bug link https://bugs.chromium.org/p/chromium/issues/detail?id=1459821. Is there a public link for that bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
** Summary changed: - Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) + FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2069130] Re: Bluetooth fail to load firmware for 8087:0a2b Intel Corp. Bluetooth wireless interface
Why do you mark it incomplete? I have asked if there is anything I can do to investigate the issue? and you have been silence... ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Confirmed -- 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/2069130 Title: Bluetooth fail to load firmware for 8087:0a2b Intel Corp. Bluetooth wireless interface Status in linux-firmware package in Ubuntu: Confirmed Bug description: It seems like the firmware is missing for 8087:0a2b Intel Corp. Bluetooth wireless interface `$ sudo dmesg | grep -i bluetooth` gives ``` [5.609015] Bluetooth: Core ver 2.22 [5.609045] NET: Registered PF_BLUETOOTH protocol family [5.609048] Bluetooth: HCI device and connection manager initialized [5.609052] Bluetooth: HCI socket layer initialized [5.609056] Bluetooth: L2CAP socket layer initialized [5.609063] Bluetooth: SCO socket layer initialized [5.624996] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [5.631455] Bluetooth: hci0: Device revision is 5 [5.631460] Bluetooth: hci0: Secure boot is enabled [5.631462] Bluetooth: hci0: OTP lock is enabled [5.631464] Bluetooth: hci0: API lock is enabled [5.631466] Bluetooth: hci0: Debug lock is disabled [5.631468] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.636984] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [5.647330] Bluetooth: hci0: Failed to send firmware data (-38) [5.647357] Bluetooth: hci0: Intel reset sent to retry FW download [6.845544] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.845550] Bluetooth: BNEP filters: protocol multicast [6.84] Bluetooth: BNEP socket layer initialized [7.838527] Bluetooth: hci0: command 0xfca6 tx timeout [7.838598] Bluetooth: hci0: Reading supported features failed (-110) [7.838602] Bluetooth: hci0: Error reading debug features [7.838605] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. ``` It seems like it's looking for file `/lib/firmware/intel/ibt-11-5.sfi`, but it's not there: ``` $ ls -l /lib/firmware/intel/ibt-11-5.* -rw-r--r-- 1 root root 31 apr 10 00:14 /lib/firmware/intel/ibt-11-5.ddc.zst -rw-r--r-- 1 root root 379353 apr 10 00:14 /lib/firmware/intel/ibt-11-5.sfi.zst ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-firmware 20240318.git3b128b60-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:jarl 3697 F pipewire /dev/snd/controlC1: jarl 3701 F wireplumber /dev/snd/controlC2: jarl 3701 F wireplumber /dev/snd/controlC0: jarl 3701 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 12 11:46:23 2024 Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1 HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88 InstallationDate: Installed on 2016-01-08 (3078 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System76, Inc. Oryx Pro ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-35-generic root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro quiet splash nvidia.NVreg_EnableBacklightHandler=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-35-generic N/A linux-backports-modules-6.8.0-35-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux-firmware UpgradeStatus: Upgraded to noble on 2024-05-29 (13 days ago) dmi.bios.date: 02/02/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: orxp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:br5.11:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: orxp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source
