[Kernel-packages] [Bug 1959121] [NEW] nvidia graphics driver stopped working, screen resolution has been degraded
Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
N: Unable to locate package pkgname
I expected my computer to recognize my graphics card. It has been working fine
until this morning. When I turned on my computer it took longer than normal to
load and now it does not identify my graphics card and the resolution is
degraded.
apt.log
log time: 2021-06-17 15:56:46.835636
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) linux-modules-nvidia-460-5.8.0-53-generic:amd64 < 5.8.0-53.60>
Broken linux-modules-nvidia-460-5.8.0-53-generic:amd64 Depends on nvidia-kernel>
Considering nvidia-kernel-common-460:amd64 13 as a solution to linux-modules->
Removing linux-modules-nvidia-460-5.8.0-53-generic:amd64 rather than change n>
Done
Log time: 2021-06-17 16:16:26.065339
MarkPurge libsratom-0-0:amd64 < 0.6.4-1 @ii gK > FU=1
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii gK Ib >
Broken liblilv-0-0:amd64 Depends on libsratom-0-0:amd64 < 0.6.4-1 @ii pgP > (>=>
Considering libsratom-0-0:amd64 1 as a solution to liblilv-0-0:amd64 2
Removing liblilv-0-0:amd64 rather than change libsratom-0-0:amd64
MarkDelete liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii gK Ib > FU=0
Investigating (0) libavfilter7:amd64 < 7:4.2.4-1ubuntu0.1 @ii gK Ib >
Broken libavfilter7:amd64 Depends on liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii >
Considering liblilv-0-0:amd64 2 as a solution to libavfilter7:amd64 1
[ File 'apt.log' is unwritable ]
Start-Date: 2021-06-17 16:14:39
Requested-By: office (1000)
Install: linux-signatures-nvidia-5.8.0-55-generic:amd64 (5.8.0-55.62~20.04.1, a>
Upgrade: gnome-control-center-data:amd64 (1:3.36.5-0ubuntu1, 1:3.36.5-0ubuntu2)>
Remove: linux-modules-nvidia-460-5.8.0-53-generic:amd64 (5.8.0-53.60~20.04.1)
End-Date: 2021-06-17 16:16:24
Start-Date: 2021-06-17 16:16:39
Requested-By: office (1000)
Purge: libavfilter7:amd64 (7:4.2.4-1ubuntu0.1), libopencore-amrnb0:amd64 (0.1.5>
End-Date: 2021-06-17 16:16:41
Log started: 2021-06-17 16:14:39
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(R>
Preparing to unpack .../0-nvidia-driver-460_460.80-0ubuntu0.20.04.2_amd64.deb .>
Unpacking nvidia-driver-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubuntu0.>
Preparing to unpack .../1-libnvidia-gl-460_460.80-0ubuntu0.20.04.2_amd64.deb ...
De-configuring libnvidia-gl-460:i386 (460.73.01-0ubuntu0.20.04.1) ...
Unpacking libnvidia-gl-460:amd64 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubu>
Preparing to unpack .../2-libnvidia-gl-460_460.80-0ubuntu0.20.04.2_i386.deb ...
Unpacking libnvidia-gl-460:i386 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubun>
Preparing to unpack .../3-nvidia-dkms-460_460.80-0ubuntu0.20.04.2_amd64.deb ...
Removing all DKMS Modules
Done.
Unpacking nvidia-dkms-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubuntu0.20>
Preparing to unpack .../4-nvidia-kernel-source-460_460.80-0ubuntu0.20.04.2_amd6>
Unpacking nvidia-kernel-source-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0u>
Preparing to unpack .../5-linux-modules-nvidia-460-generic-hwe-20.04_5.8.0-55.6>
Unpacking linux-modules-nvidia-460-generic-hwe-20.04 (5.8.0-55.62~20.04.1) over>
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(R>
Removing linux-modules-nvidia-460-5.8.0-53-generic (5.8.0-53.60~20.04.1) ...
[ File 'apt-term.log' is unwritable ]
7zXZ^@^@^D�ִF^B^@!^A^V^@^@^@t/���]^@)^YJ'�H�^Uh�TZۄUّ���|y�^R^Q��ya��^S��^Y�>
ʆ��G�$^LE�^H��C;}�l^9Ꭱ^V^@���f^S)^Y^H
e17ӕ�ozұ^R�
�^P^N�}^W^^���§��Ԙ#�^W�1�UvĬ^WӺY�e�"^B��fS��"^R^F�^[�(,(^C�H��Վ8J5^Zhi�E+^O>
j!#�b�"?�ˉ��:���F�v�SN^]��V|*S7�^AC^Y^]f��^\})�wɼ���^Fh^h^[Ɓ�>-^ZSj2#^^^Qif>
Yҙ~<�LΎ9oĥ�~K,iyӼ��6mս�ω��$�\k`���^_
½�%�j��ԅ+
�^HA�$G�^B�B��H�zuG�h^D{Ձ!ű�-�^R)5��Qi�O^_Jk�^?˳��T�T�b8^^w��[�^N�X^DX�>
�^K:jw�n^Aئ� ^PWܖ�4��/@^P^C�n� �#�Ҵ��_��^L;i�Ku�~��^F���ʽ��^[�^]��bq�z�>
�^F^P���B�Ԯ^D^Y�^U" �^T�^E;�F���Z�`�^C��^\䒁+�,=�F^^�W���K�mNx-`藬A�,�Y�1��A�?ՠ>
GJ���H�]A<�^R]�c�o�^]Ţ#�^^�^Y���N帹��/^S�^_-��{:^^B�Y7^SCJT���9|c��@==�>
Ӡ1o�j}�r��^X^W!F^@�^E$㲐#ja(^Z��\��^]�5�D^Z��6Xx��}eL��^PۗC�^S�#^Z�q�ٝR�{�^K�>
r��^Zڤ�^Smf��^[w^Wl[^E�>�H���v^F�^(��gSz)�̥���;�^@,TQ�8��ސ��r�^D@/��2��'��[fK�U�>
�^^v�J[���^W�:�9���^KX�9��_^Zq�ZPu}Efi�DoZ���^[�G&^Y'^XU�^_~^B�*}y4V�^S^E >
baY�q^@�@^N�^Y���j��fB���U�^E^H�'qx��S)��+c՟��V��l��*�
WsVA�I7^C�^���AZ�5^S_���^Wj�,B�Į�(�^S^Cd4��InVB>^^ר�'^U^W^^�M�$�a�^L��O>
�E���9^PE��Q�^W���^Yn�e��g^V�oc��?U^D�L��M��7�kx�-^\^X/���^\J�k^O��>
^O�2D�ln���ڇV'��G���_�+��`�u��s�dAn�U�^[���4^]�E~L^D�a��^E�ء^�B^Z^F�JO�U�,�>
��r�/z�Ybn��⺌I^B^N��� w�M^R^B�:��/�D���C�c�^]W�1�7��T^\��^Z���ȥ.��qp�H= ��^B^>
^Z._dH��^xu�/��:-��-*5`0p�ȧ%^P���^Hh��;�.��^V47^K�3wQ�^Vً�9�v��^O^T^U�I�>
[ File
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
@hui your kernel works for me on my Dell XPS9710. Sound in and out. Thanks!! In other words, in response to the kernel bot: This patch solves the problem. If I knew how, I would change this to 'verification-done-hirsute' Thanks again! -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+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 1054458] Re: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'
Same problem on new Dell G5 and MSI GE75 after initial install of Ubuntu 20.04 Mate Nvidia GTX 1650 & RTX 2080 Super were using 440.100 driver and now using 450.66 but still getting the error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-common in Ubuntu. https://bugs.launchpad.net/bugs/1054458 Title: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304' Status in nvidia-common package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-common source package in Precise: Fix Released Status in ubuntu-drivers-common source package in Precise: Invalid Status in nvidia-common source package in Quantal: Invalid Status in ubuntu-drivers-common source package in Quantal: Fix Released Status in nvidia-common source package in Bionic: Invalid Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: If other people report this at the current level with xorg/nvidia it might be a bug. It is also possible the error stems from a bad combination of free and proprietary material. Further details will be provided as necessary/available. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: ubuntu-drivers-common 1:0.2.69 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 Date: Fri Sep 21 22:48:18 2012 ExecutablePath: /usr/bin/nvidia-detector InterpreterPath: /usr/bin/python3.2mu ProcCmdline: /usr/bin/python3.2 /usr/bin/nvidia-detector ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=de_CH.UTF-8 LANGUAGE=de_CH:de PythonArgs: ['/usr/bin/nvidia-detector'] SourcePackage: ubuntu-drivers-common Title: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304' UpgradeStatus: Upgraded to quantal on 2012-07-31 (52 days ago) UserGroups: audio pulse pulse-access video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1054458/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Happy confirmed as well! sudo apt install haveged fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Triaged Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Interesting thing happening... I tried booting 0-23 success, then did shutdown -r now, and tried booting 0-24, as noted above just hangs. Briefly hit power button tried to boot 0-23 again and now it doesn't boot... Tried turning off power and then booting 0-23, still hangs, got "Started GNOME display manager. Dispatcher service..before the ppp link was shut down Initially when I had the issue this morning I just turned the power off and let the laptop sit for about three hours before trying to boot (successfully) the 0-23 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Triaged Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Agreed, I see the same thing. Glad 0-23 boots, but 0-24 still hangs at the Ubuntu logo, five white dots, not animated. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Triaged Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Me either. The booting to prior kernel does not fix the issue. Glad to help test but need some instructions. Only have non-bootable system at this point. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Triaged Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1568969] Re: FDB table grows out of control
The defect has been fixed in kernel3.13.0-89-generic with the test approach in https://github.com/dlevy-ibm/fdb_bug. -- Adding FDB entry for IP: 123.123.123.1 ... Adding FDB entry for IP: 123.123.123.74 79 Linux vmtotest 3.13.0-89-generic #136-Ubuntu SMP Fri Jun 10 19:19:24 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ** Summary changed: - FDB table grows out of control + FDB table grows out of control ** Tags added: verification-done-trusty ** Tags removed: verification-needed-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/1568969 Title: FDB table grows out of control Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: The forwarding database (FDB) grows out of control after too many broadcast entries are entered under the same interface. I've written a test script to reproduce the bug here using virtual box: https://github.com/dlevy-ibm/fdb_bug Also filed here: https://bugzilla.kernel.org/show_bug.cgi?id=116141 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-83-generic 3.13.0-83.127 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 16:36 seq crw-rw 1 root audio 116, 33 Apr 11 16:36 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Apr 11 16:45:55 2016 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=a742ba82-8430-4d30-b747-99c9c9af3168 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568969/+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 1568969] Re: FDB table grows out of control
I see that the patch has gotten two ACKs. Looks the coming cycle is from 03-Jun through 25-Jun, and it is 03-Jun as last day for kernel commits. Please let me know if you need my support. Thanks. -- 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/1568969 Title: FDB table grows out of control Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: The forwarding database (FDB) grows out of control after too many broadcast entries are entered under the same interface. I've written a test script to reproduce the bug here using virtual box: https://github.com/dlevy-ibm/fdb_bug Also filed here: https://bugzilla.kernel.org/show_bug.cgi?id=116141 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-83-generic 3.13.0-83.127 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 16:36 seq crw-rw 1 root audio 116, 33 Apr 11 16:36 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Apr 11 16:45:55 2016 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=a742ba82-8430-4d30-b747-99c9c9af3168 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568969/+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 1568969] Re: FDB table grows out of control
Hi Tim, Can we add the patch into new v3.13 maintenance patch? It affects many people and we really needs this. Please suggest. Otherwise we have to build custom kernel and we don't prefer custom kernel. Thanks. btw, I checked out Ubuntu-3.13.0-87.133 which has the problem. And after cherry-picking 9063e21fb026c4966fc93261c18322214f9835eb, the problem is gone. Perry -- 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/1568969 Title: FDB table grows out of control Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: The forwarding database (FDB) grows out of control after too many broadcast entries are entered under the same interface. I've written a test script to reproduce the bug here using virtual box: https://github.com/dlevy-ibm/fdb_bug Also filed here: https://bugzilla.kernel.org/show_bug.cgi?id=116141 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-83-generic 3.13.0-83.127 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 16:36 seq crw-rw 1 root audio 116, 33 Apr 11 16:36 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Apr 11 16:45:55 2016 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=a742ba82-8430-4d30-b747-99c9c9af3168 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568969/+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 1568969] Re: FDB table grows out of control
This problem affects us. I have identified that the change 9063e21fb026c4966fc93261c18322214f9835eb is able to resolve it after merging it to v3.13 kernel. Can we add the patch to new ubuntu v3.13 patch? Any suggestion? Thanks. -- 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/1568969 Title: FDB table grows out of control Status in linux package in Ubuntu: Confirmed Bug description: The forwarding database (FDB) grows out of control after too many broadcast entries are entered under the same interface. I've written a test script to reproduce the bug here using virtual box: https://github.com/dlevy-ibm/fdb_bug Also filed here: https://bugzilla.kernel.org/show_bug.cgi?id=116141 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-83-generic 3.13.0-83.127 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 16:36 seq crw-rw 1 root audio 116, 33 Apr 11 16:36 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Apr 11 16:45:55 2016 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=a742ba82-8430-4d30-b747-99c9c9af3168 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568969/+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 1407760] Re: Kernel crash when setting vxlan tunnel over the mlx4_en when acting as PF
** Tags removed: verification-needed-trusty
** Tags added: verification-done-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/1407760
Title:
Kernel crash when setting vxlan tunnel over the mlx4_en when acting as
PF
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Utopic:
Fix Released
Bug description:
Eyal Perry (~eyalpe) writes:
[Impact]
When enabling SR-IOV on Mellanox devices and setting vxlan tunnel over the PF
device (adding vxlan port to an OVS bridge),
the kernel is crashing as result of the unimplemented ndos:
.ndo_{add,del}_vxlan_port
[Fix]
This issue was fixed in upstream kernel:
9737c6a net/mlx4_en: Add VXLAN ndo calls to the PF net device ops too
~/linux$ git describe --contains 9737c6ab7afbc950e997ef80cba2c40dbbd16ea4
v3.18-rc6~9^2~12
I've backported it to 3.16 (by removing the yet to be introduced
ndo_gso_check) and attached the backported version here.
The patch was built and tested on top of ubuntu-trusty: abb1293
(UBUNTU: Ubuntu-lts-3.16.0-29.39~14.04.1)
[Test Case]
Use the affected Mellanox device w/ an Ubuntu 3.16 kernel. Setup vxlan tunnel
over PF device. This should succeed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407760/+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 1400127] Re: Mellanox updates for Trusty
** Tags removed: verification-needed-trusty verification-needed-utopic
** Tags added: verification-done-trusty verification-done-utopic
--
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/1400127
Title:
Mellanox updates for Trusty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Utopic:
Fix Committed
Bug description:
SRU Justification:
[Impact]
Users of Mellanox mlx4_{core,en} drivers may be missing hardware enablement
features.
[Test Case]
Test Mellanox hardware and ensure functionality with mlx4_{core,en} drivers.
[Fix]
As described below, and summarized in Comment #5.
--
The following changes since commit
b87885d70c29324b66ee7d4f979a9f95cc46564b:
UBUNTU: Ubuntu-3.13.0-42.71 (2014-12-05 14:35:11 +)
are attached to this tracker as patch files.
The main goal for this is patch-set is to add functionality to:
1. reduce cache misses by aligning CQE/EQE writes to the actual cache line
size
2. set/get link speed using ethtool [-s].
3. set rx/tx vlan offload
4. bug fixes
all of the patches are upsream (net-next), except for the last one which is
a bug fix waiting for review:
https://patchwork.ozlabs.org/patch/418451/
Ido Shamay (3):
net/mlx4_core: Enable CQE/EQE stride support
net/mlx4_core: Cache line EQE size support
net/mlx4_en: Add mlx4_en_get_cqe helper
Saeed Mahameed (12):
net/mlx4_core: Introduce mlx4_get_module_info for cable module info
reading
ethtool, net/mlx4_en: Cable info, get_module_info/eeprom ethtool support
net/mlx4_core: Introduce ACCESS_REG CMD and eth_prot_ctrl dev cap
net/mlx4_core: Add ethernet backplane autoneg device capability
ethtool, net/mlx4_en: Add 100M, 20G, 56G speeds ethtool reporting
support
net/mlx4_en: Use PTYS register to query ethtool settings
net/mlx4_en: Use PTYS register to set ethtool settings (Speed)
net/mlx4_en: Add support for setting rxvlan offload OFF/ON
net/mlx4_en: Add ethtool support for [rx|tx]vlan offload set to OFF/ON
net/mlx4_core: Prevent VF from changing port configuration
net/mlx4_en: mlx4_en_set_settings() always fails when autoneg is set
net/mlx4_en: ethtool force speed when asking for autoneg=off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400127/+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 1407760] Re: [SRU][PATCH] [Utopic] Kernel crash when setting vxlan tunnel over the mlx4_en when acting as PF
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
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/1407760
Title:
[SRU][PATCH] [Utopic] Kernel crash when setting vxlan tunnel over the
mlx4_en when acting as PF
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Utopic:
Fix Committed
Bug description:
Eyal Perry (~eyalpe) writes:
[Impact]
When enabling SR-IOV on Mellanox devices and setting vxlan tunnel over the PF
device (adding vxlan port to an OVS bridge),
the kernel is crashing as result of the unimplemented ndos:
.ndo_{add,del}_vxlan_port
[Fix]
This issue was fixed in upstream kernel:
9737c6a net/mlx4_en: Add VXLAN ndo calls to the PF net device ops too
~/linux$ git describe --contains 9737c6ab7afbc950e997ef80cba2c40dbbd16ea4
v3.18-rc6~9^2~12
I've backported it to 3.16 (by removing the yet to be introduced
ndo_gso_check) and attached the backported version here.
The patch was built and tested on top of ubuntu-trusty: abb1293
(UBUNTU: Ubuntu-lts-3.16.0-29.39~14.04.1)
This only affect 3.16 since it has the VLAN features.
[Test Case]
Use the affected Mellanox device w/ an Ubuntu 3.16 kernel. Setup vxlan tunnel
over PF device. This should succeed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407760/+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 1400127] [NEW] Mellanox updates for trsuty
Public bug reported: The following changes since commit b87885d70c29324b66ee7d4f979a9f95cc46564b: UBUNTU: Ubuntu-3.13.0-42.71 (2014-12-05 14:35:11 +) are attached to this tracker as patch files. The main goal for this is patch-set is to add functionality to: 1. reduce cache misses by aligning CQE/EQE writes to the actual cache line size 2. set/get link speed using ethtool [-s]. 3. set rx/tx vlan offload 4. bug fixes all of the patches are upsream (net-next), except for the last one which is a bug fix waiting for review: https://patchwork.ozlabs.org/patch/418451/ Ido Shamay (3): net/mlx4_core: Enable CQE/EQE stride support net/mlx4_core: Cache line EQE size support net/mlx4_en: Add mlx4_en_get_cqe helper Saeed Mahameed (12): net/mlx4_core: Introduce mlx4_get_module_info for cable module info reading ethtool, net/mlx4_en: Cable info, get_module_info/eeprom ethtool support net/mlx4_core: Introduce ACCESS_REG CMD and eth_prot_ctrl dev cap net/mlx4_core: Add ethernet backplane autoneg device capability ethtool, net/mlx4_en: Add 100M, 20G, 56G speeds ethtool reporting support net/mlx4_en: Use PTYS register to query ethtool settings net/mlx4_en: Use PTYS register to set ethtool settings (Speed) net/mlx4_en: Add support for setting rxvlan offload OFF/ON net/mlx4_en: Add ethtool support for [rx|tx]vlan offload set to OFF/ON net/mlx4_core: Prevent VF from changing port configuration net/mlx4_en: mlx4_en_set_settings() always fails when autoneg is set net/mlx4_en: ethtool force speed when asking for autoneg=off ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: tar-gz-ed patchset https://bugs.launchpad.net/bugs/1400127/+attachment/4275726/+files/ethtool-set-link-etc.tar.gz -- 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/1400127 Title: Mellanox updates for trsuty Status in linux package in Ubuntu: Incomplete Bug description: The following changes since commit b87885d70c29324b66ee7d4f979a9f95cc46564b: UBUNTU: Ubuntu-3.13.0-42.71 (2014-12-05 14:35:11 +) are attached to this tracker as patch files. The main goal for this is patch-set is to add functionality to: 1. reduce cache misses by aligning CQE/EQE writes to the actual cache line size 2. set/get link speed using ethtool [-s]. 3. set rx/tx vlan offload 4. bug fixes all of the patches are upsream (net-next), except for the last one which is a bug fix waiting for review: https://patchwork.ozlabs.org/patch/418451/ Ido Shamay (3): net/mlx4_core: Enable CQE/EQE stride support net/mlx4_core: Cache line EQE size support net/mlx4_en: Add mlx4_en_get_cqe helper Saeed Mahameed (12): net/mlx4_core: Introduce mlx4_get_module_info for cable module info reading ethtool, net/mlx4_en: Cable info, get_module_info/eeprom ethtool support net/mlx4_core: Introduce ACCESS_REG CMD and eth_prot_ctrl dev cap net/mlx4_core: Add ethernet backplane autoneg device capability ethtool, net/mlx4_en: Add 100M, 20G, 56G speeds ethtool reporting support net/mlx4_en: Use PTYS register to query ethtool settings net/mlx4_en: Use PTYS register to set ethtool settings (Speed) net/mlx4_en: Add support for setting rxvlan offload OFF/ON net/mlx4_en: Add ethtool support for [rx|tx]vlan offload set to OFF/ON net/mlx4_core: Prevent VF from changing port configuration net/mlx4_en: mlx4_en_set_settings() always fails when autoneg is set net/mlx4_en: ethtool force speed when asking for autoneg=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400127/+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 1400127] Re: Mellanox updates for trsuty
This item is opened for tracking purposes, and more resembles a feature request than a bug in its nature. Therefore I'm skipping the apport-collect script. -- 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/1400127 Title: Mellanox updates for trsuty Status in linux package in Ubuntu: Incomplete Bug description: The following changes since commit b87885d70c29324b66ee7d4f979a9f95cc46564b: UBUNTU: Ubuntu-3.13.0-42.71 (2014-12-05 14:35:11 +) are attached to this tracker as patch files. The main goal for this is patch-set is to add functionality to: 1. reduce cache misses by aligning CQE/EQE writes to the actual cache line size 2. set/get link speed using ethtool [-s]. 3. set rx/tx vlan offload 4. bug fixes all of the patches are upsream (net-next), except for the last one which is a bug fix waiting for review: https://patchwork.ozlabs.org/patch/418451/ Ido Shamay (3): net/mlx4_core: Enable CQE/EQE stride support net/mlx4_core: Cache line EQE size support net/mlx4_en: Add mlx4_en_get_cqe helper Saeed Mahameed (12): net/mlx4_core: Introduce mlx4_get_module_info for cable module info reading ethtool, net/mlx4_en: Cable info, get_module_info/eeprom ethtool support net/mlx4_core: Introduce ACCESS_REG CMD and eth_prot_ctrl dev cap net/mlx4_core: Add ethernet backplane autoneg device capability ethtool, net/mlx4_en: Add 100M, 20G, 56G speeds ethtool reporting support net/mlx4_en: Use PTYS register to query ethtool settings net/mlx4_en: Use PTYS register to set ethtool settings (Speed) net/mlx4_en: Add support for setting rxvlan offload OFF/ON net/mlx4_en: Add ethtool support for [rx|tx]vlan offload set to OFF/ON net/mlx4_core: Prevent VF from changing port configuration net/mlx4_en: mlx4_en_set_settings() always fails when autoneg is set net/mlx4_en: ethtool force speed when asking for autoneg=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400127/+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 1353947] Re: Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04
Can't run apport-collect after the kernel hang
** 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/1353947
Title:
Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with
CirrOS or Ubuntu 12.04
Status in QEMU:
New
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The issue observed when running an hypervisor with QEMU 2.0/libvirtd 1.2.2
The VM network interface is attached to a PCI virtual function (SR-IOV).
When we ran VM with guest OS CirrOS or Ubuntu 12.04 we observed an hipervisor
hang shortly after the VM is loaded
We observed the same issue with Mellanox NIC and with Intel NIC
We’ve tried few combinations of {GuestOS}X{Hypervisor} and we got the
following findings:
When a hypervisor is running QEMU 1.5/libvirtd 1.1.1 - no issue observed
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CirrOS and Ubuntu
12.04 guest OSes caused hypervisor hang
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CentOS 6.4 and Ubuntu
13.10 - no issue observed
The problematic guest OSes are with kernel versions ~3.2.y
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1353947/+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 1353947] Re: Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04
Indeed, with qemu 1.5 we did not observed this issue at all.
Sorry, but I don't have the resources at the moment to do the bisecting.
--
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/1353947
Title:
Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with
CirrOS or Ubuntu 12.04
Status in QEMU:
New
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The issue observed when running an hypervisor with QEMU 2.0/libvirtd 1.2.2
The VM network interface is attached to a PCI virtual function (SR-IOV).
When we ran VM with guest OS CirrOS or Ubuntu 12.04 we observed an hipervisor
hang shortly after the VM is loaded
We observed the same issue with Mellanox NIC and with Intel NIC
We’ve tried few combinations of {GuestOS}X{Hypervisor} and we got the
following findings:
When a hypervisor is running QEMU 1.5/libvirtd 1.1.1 - no issue observed
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CirrOS and Ubuntu
12.04 guest OSes caused hypervisor hang
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CentOS 6.4 and Ubuntu
13.10 - no issue observed
The problematic guest OSes are with kernel versions ~3.2.y
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1353947/+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 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
Hi all, I can confirm that with kernel 3.16.0-031600-generic the connection is more or less stable. However, the download speed is extremely slow (maxes out at around 1 Mbps). Does anyone have a workaround to increase the throughput? Regards PY -- 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/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+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 1207812] Re: Iphone with iOS 7 does not work on Ubuntu
I commented on the dup by accident, but I also have this problem on the following setup: iPhone 5 7.0.4 Ubuntu 12.04.3 I've tried reinstalling Fuse and iFuse, as well was libimobiledevice etc. Nothing helps. I get a perpetual loop of Trust this computer and errors: Unable to mount - DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus). Would love to see this fixed, as I name numerous iOS devices. It's problematic for me just to plug them in, let alone mount them! -- 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/1207812 Title: Iphone with iOS 7 does not work on Ubuntu Status in “linux” package in Ubuntu: Confirmed Bug description: When plugging in an iPhone with iOS 7 - Currently BETA 4. You receive the following message on Ubuntu 13.04 : The Device Nick's iPhone is locked. Enter the passcode on the device and click Try again. The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens inacontinous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207812/+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
