[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
** 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+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 1750441] Re: Boston-LC:bos1u1: Stress test on Qlogic Fibre Channel on Ubuntu KVM guest that caused KVM host crashed in qlt_free_session_done call
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- 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/1750441 Title: Boston-LC:bos1u1: Stress test on Qlogic Fibre Channel on Ubuntu KVM guest that caused KVM host crashed in qlt_free_session_done call Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Problem Description: = - PCI passthru Qlogic Fibre Channel adapter from Ubuntu 18.04 KVM host to Ubuntu 18.04 KVM guest. - Stress test on Qlogic Fibre Channel on Ubuntu KVM guest caused KVM host crashed in qlt_free_session_done call. - Below stack traces from KVM host: 91:mon> t [c000200e4e81fb60] c0081162f044 qlt_free_session_done+0x4ec/0x680 [qla2xxx] (unreliable) [c000200e4e81fc90] c012fbb8 process_one_work+0x298/0x5a0 [c000200e4e81fd20] c012ff58 worker_thread+0x98/0x630 [c000200e4e81fdc0] c0138ae8 kthread+0x1a8/0x1b0 [c000200e4e81fe30] c000b528 ret_from_kernel_thread+0x5c/0xb4 91:mon> e cpu 0x91: Vector: 300 (Data Access) at [c000200e4e81f8e0] pc: c0081162ed58: qlt_free_session_done+0x200/0x680 [qla2xxx] lr: c0081162eca8: qlt_free_session_done+0x150/0x680 [qla2xxx] sp: c000200e4e81fb60 msr: 9280b033 dar: 20 dsisr: 4000 current = 0xc000200e4e7b0e00 paca= 0xcfae3b00 softe: 0irq_happened: 0x01 pid = 1119, comm = kworker/145:1 Linux version 4.15.0-041500rc9-generic (kernel@tangerine) (gcc version 7.2.0 (Ubuntu 7.2.0-6ubuntu1)) #201801212130 SMP Mon Jan 22 03:36:42 UTC 2018 91:mon> r R00 = c0081162eca8 R16 = R01 = c000200e4e81fb60 R17 = R02 = c0081166ad60 R18 = R03 = 0001 R19 = R04 = c000200e44f8c7f8 R20 = c000200e618e7d80 R05 = f087 R21 = R06 = c0081165e6c8 R22 = 0001 R07 = c0081164adb0 R23 = c000200e44f99d24 R08 = R24 = 0402 R09 = R25 = R10 = R26 = c00fe1270c20 R11 = c0081163e170 R27 = c000200e44f99000 R12 = c0cfccf0 R28 = c0081164adb0 R13 = cfae3b00 R29 = c00fe1270c00 R14 = c0138948 R30 = c000200e44f8c7f8 R15 = c000200e4f019440 R31 = c00fe1270cc0 pc = c0081162ed58 qlt_free_session_done+0x200/0x680 [qla2xxx] cfar= c0081162ed1c qlt_free_session_done+0x1c4/0x680 [qla2xxx] lr = c0081162eca8 qlt_free_session_done+0x150/0x680 [qla2xxx] msr = 9280b033 cr = 28002284 ctr = c0cfccf0 xer = trap = 300 dar = 0020 dsisr = 4000 91:mon> The crash location seems close to this one fixed about two weeks ago: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/drivers/scsi/qla2xxx/qla_os.c?h=next-20180212&id=2ce87cc5b269510de9ca1185ca8a6e10ec78c069 scsi: qla2xxx: Fix memory corruption during hba reset test This patch fixes memory corrpution while performing HBA Reset test. Following stack trace is seen: [ 466.397219] BUG: unable to handle kernel NULL pointer dereference at 0020 [ 466.433669] IP: [] qlt_free_session_done+0x260/0x5f0 [qla2xxx] [ 466.467731] PGD 0 [ 466.476718] Oops: [#1] SMP - Luciano built and provided the patch with new Qlogic change on Friday last week. root@bos1u1p1:~/chavez# ls linux-image* linux-image-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_ppc64el.deb linux-image-extra-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_ppc64el.deb - I configured and ran same test over weekend and test ran good. KVM host did not crash in qlt_free_session_done call like before. - So the patch fixed the problem. Hi Canonical, Please review and consider this a request to pull in commit 2ce87cc5b269510de9ca1185ca8a6e10ec78c069 please. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1750441/+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 1749420] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: Confirmed Bug description: - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420/+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 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds
Miguel: Please log a separate bug. This bug is being closed due to no response from the original reporter. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1442896 Title: Bluetooth mouse disconnects and reconnects every few seconds Status in Bluez Utilities: New Status in bluez package in Ubuntu: Invalid Bug description: I have a bluetooth mouse (Genius Traveller 9005BT) that I have been using without problems with Ubuntu for over a year. Since a few weeks ago, however, it started disconnecting and reconnected from the computer. The symptoms are like this: 1. The mouse works, and the bluetooth icon on the computer is visible (in gnome-shell's top bar) 2. The mouse stops working, but the bluetooth icon is still visible. This state lasts between 1 and 10 seconds. 3. The bluetooth icon vanishes. This can last for half a second if I keep trying to use the mouse, to forever I I leave the mouse alone 4. The bluetooth icon reappears and the mouse starts working again. This state last from 2-3 seconds if I don't move the mouse, to seemingly forever if I continuously move the mouse This seems to occur only after a suspend/resume cycle, and rebooting the computer fixes the issue. The only thing I see in syslog is this when the mouse reconnects: Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 0005:0458:0139.002F: unknown main item tag 0x0 Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as /devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59 Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] on e8:2a:ea:8b:a5:5f ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 11 09:49:37 2015 InstallationDate: Installed on 2015-01-23 (77 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: E8:2A:EA:8B:A5:5F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0 TX bytes:29044 acl:238 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1442896/+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 1689433] Re: bluetoothd crashed with SIGSEGV in memcpy from bacpy from bt_cancel_discovery from browse_request_cancel from device_remove
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689433 Title: bluetoothd crashed with SIGSEGV in memcpy from bacpy from bt_cancel_discovery from browse_request_cancel from device_remove Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/28b7383d0b74f23dd092e097248686dd0be7300e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689433/+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 1689460] Re: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689460 Title: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b07fc39aa06a535581fad194d445c76f189364c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689460/+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 1556324] Re: bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate from g_main_loop_run
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1556324 Title: bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate from g_main_loop_run Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 5.36-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/20c758a42f23b514e8bc98469a414de3ed9b727f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1556324/+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 1689443] Re: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689443 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689443/+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 1689462] Re: bluetoothd crashing with SIGSEGV in release_stream from g_slist_foreach from connection_lost from disconnect_timeout from g_timeout_dispatch
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689462 Title: bluetoothd crashing with SIGSEGV in release_stream from g_slist_foreach from connection_lost from disconnect_timeout from g_timeout_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/d9aec0cc9617e42fcd64fe69270d8f758e39c453 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689462/+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 1514166] Re: bluetoothd crashed with SIGSEGV in rawmemchr() from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device [plugins/sixaxis.c]
This crash has stopped happening after 17.04. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1514166 Title: bluetoothd crashed with SIGSEGV in rawmemchr() from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device [plugins/sixaxis.c] Status in bluez package in Ubuntu: Fix Released Bug description: bluetoothd crashed with SIGSEGV in rawmemchr() https://errors.ubuntu.com/problem/f0eca11dfcb228bd89caa34e5f9b5529151c0c88 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 Date: Sat Nov 7 17:15:18 2015 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-06-02 (158 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20349 ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic.efi.signed root=/dev/mapper/btree-ubuntu ro rootflags=subvol=@ noprompt quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fef0124a51f : movdqu (%rdi),%xmm0 PC (0x7fef0124a51f) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: bluez StacktraceTop: rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37 _IO_str_init_static_internal (sf=sf@entry=0x7fffafd6df50, ptr=ptr@entry=0x0, size=size@entry=0, pstart=pstart@entry=0x0) at strops.c:44 _IO_vsscanf (string=0x0, format=0x7fef0062eacc "%hx:%hx:%hx", args=args@entry=0x7fffafd6e078) at iovsscanf.c:43 __sscanf (s=, format=) at sscanf.c:32 ?? () from /usr/lib/x86_64-linux-gnu/bluetooth/plugins/sixaxis.so Title: bluetoothd crashed with SIGSEGV in rawmemchr() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to xenial on 2015-10-28 (11 days ago) UserGroups: dmi.bios.date: 07/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN40WW(V3.00) dmi.board.asset.tag: 31900058Std dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: 31900058Std dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN40WW(V3.00):bd07/22/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 28:B2:BD:0B:11:97 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:691 acl:0 sco:0 events:47 errors:0 TX bytes:2182 acl:0 sco:0 commands:47 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1514166/+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 1689436] Re: bluetoothd crashed with SIGABRT due to heap corruption "double free or corruption (fasttop)"
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689436 Title: bluetoothd crashed with SIGABRT due to heap corruption "double free or corruption (fasttop)" Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2522ea5604a622769e532f07ec9ecab43310bf23 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689436/+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 1390063] Re: Bug Bluetooth on ubuntu 14.10
Closed due to no response. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1390063 Title: Bug Bluetooth on ubuntu 14.10 Status in bluez package in Ubuntu: Invalid Bug description: My Laptop is Acer Aspire E1-432, Now It is running Ubuntu 14.10 Utopic. Kernnel 3.16 When I turned on laptop, on status bar didnt have bluetooth icon (setting>bluetooth>cant turn on/off). After that, I restarted laptop, The bluetooth icon was had on bar and i could use it. That is repeat every i use my laptop. How to fĩx it ? Please help me. p/s: I am very bad at English :( ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 6 19:33:07 2014 InstallationDate: Installed on 2014-11-04 (2 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E1-432 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=e5789554-5e39-4b05-8e74-b37ef2a66046 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2014 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.11 dmi.board.name: EA40_HW dmi.board.vendor: Acer dmi.board.version: V2.11 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.11:bd02/20/2014:svnAcer:pnAspireE1-432:pvrV2.11:rvnAcer:rnEA40_HW:rvrV2.11:cvnAcer:ct9:cvrV2.11: dmi.product.name: Aspire E1-432 dmi.product.version: V2.11 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:DB:30:CA:D8:50 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:654 acl:0 sco:0 events:44 errors:0 TX bytes:1936 acl:0 sco:0 commands:44 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1390063/+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 1411487] Re: [GNOME gnome-control-center] Not work AD2P in device HV-800 (problem random)
Closed due to no response. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1411487 Title: [GNOME gnome-control-center] Not work AD2P in device HV-800 (problem random) Status in GNOME Bluetooth: Expired Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Invalid Bug description: Attach video. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu22 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 15 23:27:34 2015 InstallationDate: Installed on 2014-09-25 (113 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 init=/lib/systemd/systemd SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:3923189 acl:28369 sco:67913 events:523 errors:0 TX bytes:3351604 acl:260 sco:65569 commands:111 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1411487/+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 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
Thank you for reporting this bug to Ubuntu. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: Incomplete Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+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 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted
Thank you for reporting this bug to Ubuntu. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1629632 Title: Sap driver initialization failed, sap-server: Operation not permitted Status in bluez package in Ubuntu: Incomplete Status in bluez package in Debian: New Bug description: Hi, here are are messages from the bluetooth daemon: $ journalctl -b | grep bluetoothd Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41 Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 initialized Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for "Service Changed" characteristic Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed. Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted (1) There are at least 2 errors concerning: - handles - Sap driver/server ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 09:59:43 2016 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:85:DE:57:27:6F ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:1974 acl:0 sco:0 events:132 errors:0 TX bytes:6033 acl:0 sco:0 commands:132 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+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 1689464] Re: bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from avctp_channel_destroy from avctp_disconnected from avctp_set_state from session_cb
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689464 Title: bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from avctp_channel_destroy from avctp_disconnected from avctp_set_state from session_cb Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a562dd1c2698bbeadb296ebb39c238522aeb3600 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689464/+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 1025971] Re: bluetooth is ON after standby although I've switched it off in the settings
Closed due to no response. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1025971 Title: bluetooth is ON after standby although I've switched it off in the settings Status in AC100_enablement: New Status in GNOME Bluetooth: New Status in bluez package in Ubuntu: Invalid Bug description: To save battery on my Toshiba AC100 with Ubuntu 12.04 installed on it, I've switched off bluetooth in the settings GUI. But I notice that sometimes bluetooth is again ON. It seems that it becomes ON after I go back from a standby mode. I'll make an experiment and I will attach an hci.log (as asked) if the bug reoccurs. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bluetooth (not installed) Uname: Linux 3.0.27-1-ac100 armv7l ApportVersion: 2.0.1-0ubuntu8 Architecture: armhf Date: Wed Jul 18 14:04:53 2012 InterestingModules: bnep rfcomm btusb bluetooth ProcKernelCmdLine: mem=448M@0M tegrapart=recovery:300:a00:800,boot:d00:1000:800,mbr:1d00:200:800 root=UUID=d42b885d-2e92-4236-b17e-d1efc2edb7ca quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 6C:62:6D:17:96:FD ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:1106 acl:0 sco:0 events:37 errors:0 TX bytes:645 acl:0 sco:0 commands:36 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1025971/+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 1689440] Re: bluetoothd crashed with SIGSEGV in btd_device_get_service from policy_connect_sink from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689440 Title: bluetoothd crashed with SIGSEGV in btd_device_get_service from policy_connect_sink from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/685c44346c1666e27b097b86cba784459205e32d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689440/+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 1674501] Re: bluetoothd crashed with SIGSEGV in g_slist_find() from avdtp_open() from endpoint_open_cb() from endpoint_reply() from complete_pending_call_and_unlock()
Fix Released (no crashes since 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1674501 Title: bluetoothd crashed with SIGSEGV in g_slist_find() from avdtp_open() from endpoint_open_cb() from endpoint_reply() from complete_pending_call_and_unlock() Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/73af5b8f19bde06f5dbbfaf55c4448c1b48d637f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674501/+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 1689432] Re: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list"
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689432 Title: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list" Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a0e2acef0b29137ce41d624db0f08893d7ee9636 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689432/+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 1689438] Re: bluetoothd crashed with SIGABRT in free(): invalid pointer
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689438 Title: bluetoothd crashed with SIGABRT in free(): invalid pointer Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9690f8797e673b0fa8359647ae193ab8d0a62d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689438/+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 1689459] Re: bluetoothd crashing with SIGSEGV in ext_confirm from server_cb from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689459 Title: bluetoothd crashing with SIGSEGV in ext_confirm from server_cb from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/79fb1a2bdca7699121c71f94778d0ac7688ef891 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689459/+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 1689457] Re: bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from adapter_remove
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689457 Title: bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from adapter_remove Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e2c5f3e07125e7ba40af3a44a3b07adb73420030 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689457/+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 1689463] Re: bluetoothd crashing with SIGSEGV in ba2str from update_bredr_services from browse_cb from search_completed_cb from sdp_process
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689463 Title: bluetoothd crashing with SIGSEGV in ba2str from update_bredr_services from browse_cb from search_completed_cb from sdp_process Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/34f2d57d9e4087da25c8712bf1ea880ced7a88b6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689463/+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 1689458] Re: bluetoothd crashing with SIGSEGV in device_svc_resolved from search_cb from browse_cb from connect_watch from g_main_dispatch
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689458 Title: bluetoothd crashing with SIGSEGV in device_svc_resolved from search_cb from browse_cb from connect_watch from g_main_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/3d579b15e5040bb946caffbf22f9ee8124529197 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689458/+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 1689448] Re: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689448 Title: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74228037aee5c1e95c18d26533f63d5396d48e3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689448/+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 1689465] Re: bluetoothd crashing with SIGABRT due to heap corruption - malloc(): smallbin double linked list corrupted
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689465 Title: bluetoothd crashing with SIGABRT due to heap corruption - malloc(): smallbin double linked list corrupted Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2cd62ac3fc6977ec03346b6dedcb8edee13c8014 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689465/+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 1689442] Re: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689442 Title: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fffbe12b82b8b2181e3dc736bea0a598f3b61042 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689442/+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 1689450] Re: bluetoothd crashed with SIGSEGV in strlen from _dbus_string_init_const from _dbus_check_is_valid_path from dbus_message_iter_append_basic from dev_property_get_adap
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689450 Title: bluetoothd crashed with SIGSEGV in strlen from _dbus_string_init_const from _dbus_check_is_valid_path from dbus_message_iter_append_basic from dev_property_get_adapter Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e95b08689734fed39c54cb1173dccd71279f1c1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689450/+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 1689445] Re: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch
** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689445 Title: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b959171c4183443c43f641033bf8efcdee964438 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689445/+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 1689451] Re: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689451 Title: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/686eb99935548ae15300b85caf382f510d0c074f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689451/+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 403779] Re: Error Msg: Device added successfuly, but failed to connect
Closed due to no response. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/403779 Title: Error Msg: Device added successfuly, but failed to connect Status in Blueman: Confirmed Status in bluez package in Ubuntu: Invalid Bug description: Fedora 11, Rocketfish dongle, Blackberry Storm as Verizon Broad-Band Modem. Setup, Connect to Dialup Networking DUN Error Message: Device added successfuly, but failed to connect. Any ideas? Cheers! Karl To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/403779/+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 453885] Re: bluetooth is nonfunctional
Closed due to no response. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/453885 Title: bluetooth is nonfunctional Status in Bluez Utilities: New Status in bluez package in Ubuntu: Invalid Bug description: Binary package hint: bluez Since my upgrade to kubuntu karmic my USB dongle stopped working, but it still works in my other jaunty machine and in Windows XP. Adapter model is Broadcom BCM2035 lsusb says: Bus 003 Device 005: ID 0c10: Symptoms: 1) If i open bluetooth adapter settings in either kbluetooth, bluez-gnome or gnome-bluetooth, it says adapter is in hidden mode. If i change it to discovered, save settings, then open configuration dialog again, it still says that adapter is in hidden mode. 2) When i scan for bluetooth devices in kbluetooth, bluez-gnome, gnome-bluetooth or using command hcitool scan it cannot find any device. When i try to connect to already known device connection also fails 3)Same when i try to discover karmic machine or connect to it from my mobile or PDA. 3) Also in adapter config dialog adapter name is set to "Broadcom BCM2035", whereas in jaunty it was $hostname-1 hciconfig says: hci0: Type: USB BD Address: 00:1A:7D:0A:C8:8A ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING RX bytes:664 acl:0 sco:0 events:18 errors:0 TX bytes:76 acl:0 sco:0 commands:20 errors:0 $ hcitool scan Scanning ... Inquiry failed: Connection timed out $ uname -a Linux gendalf 2.6.31-14-generic #47-Ubuntu SMP Thu Oct 15 02:08:08 UTC 2009 i686 GNU/Linux $ apt-cache policy bluez bluez: Installed: 4.51-0ubuntu2 Candidate: 4.51-0ubuntu2 Version table: *** 4.51-0ubuntu2 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status Let me know if you need additional info from me. ProblemType: Bug Architecture: i386 Date: Sat Oct 17 13:53:20 2009 DistroRelease: Ubuntu 9.10 Package: bluez 4.51-0ubuntu2 ProcEnviron: LANGUAGE=uk_UA:uk:en_GB:en LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.47-generic SourcePackage: bluez Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (polkit-gnome-authentication-agent-1:2131): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/453885/+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 1694827] Re: [VIZIO SB3820, playback] Bluetooth speaker not listed in Sound and can't be used without workarounds.
** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1694827 Title: [VIZIO SB3820, playback] Bluetooth speaker not listed in Sound and can't be used without workarounds. Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: When I try to connect to my Bluetooth speaker using Ubuntu GNOME (a Vizio SB3820 sound bar) it is not listed in the sound devices until I use a workaround from this site: https://askubuntu.com/questions/824404/bluetooth-speaker-connected- but-not-listed-in-sound-output Specifically, "Install blueman sudo apt install blueman Delete the paired device in the bluetooth settings. Run these commands in terminal: bash sudo pkill pulseaudio sudo /etc/init.d/bluetooth restart Turn off headphones. Turn on headphones, and press green/go until headphones notification voice says "Ready to pair." Launch blueman, and from the upper right menu, right-click the icon to bring up the blueman menu. Select Setup new device. Pair the device, and when you are given an option, not headphones, not handsfree. Use the Audio sink option. Then when you look into the audio settings panel, the device should be displayed." In my case, the situation is more like killing pulseaudio, restarting the bluetooth service, and reconnecting to the device using Blueman as an audio sink, NOT using the GNOME Bluetooth applet. If I do this, the device appears as a sound device and worksuntil I reboot the computer. I was told to file a bug on this by the #ubuntu-gnome IRC channel using ubuntu-bug audio. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ryan 3043 F...m pulseaudio /dev/snd/controlC0: ryan 3043 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 15:47:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: VIZIO SB3820 Symptom_Type: None of the above Title: [VIZIO SB3820, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK2 dmi.modalias: dmi:bvnLENOVO:bvr2UCN10T:bd10/14/2016:svnLENOVO:pn80UE:pvrLenovoYOGA900-13ISK2:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK2: dmi.product.name: 80UE dmi.product.version: Lenovo YOGA 900-13ISK2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694827/+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 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: New Bug description: - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420/+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 1665589] Re: Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS Mobile Mouse 3600
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1665589 Title: Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS Mobile Mouse 3600 Status in bluez package in Ubuntu: Incomplete Bug description: I saw number of posts here about Mobile Mouse 3600 but sadly none of them helped me to debug the issue. I have Killer 1535 card on my Dell XPS 13. According to specs it's Bluetooth 4.1 device. Mobile Mouse 3600 is Bluetooth Low Energy device of version 4.0. In theory these two devices should be able to communicate. Unfortunately they don't :( I'm on Ubuntu MATE 16.10 but I also tested it on Linux Mint 18 and Element OS. I have bluez 5.41 installed. Here is what info I have abut my devices usb-devices | awk '/e301/' RS= T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0cf3 ProdID=e301 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb hciconfig -a | grep HCI HCI Version: 4.1 (0x7) Revision: 0x0 lsusb | grep Ath Bus 001 Device 004: ID 0cf3:e301 Atheros Communications, Inc. `sudo hcitool lescan` finds nothing. After clean installation `dmesg | grep ath10` gives [ 14.979939] ath10k_pci :3a:00.0: enabling device ( -> 0002) [ 14.981966] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 15.263691] ath10k_pci :3a:00.0: Direct firmware load for ath10k/pre-cal-pci-:3a:00.0.bin failed with error -2 [ 15.263709] ath10k_pci :3a:00.0: Direct firmware load for ath10k/cal-pci-:3a:00.0.bin failed with error -2 [ 15.263734] ath10k_pci :3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 15.263736] ath10k_pci :3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 15.440154] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [ 15.440156] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 15.440582] ath10k_pci :3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 15.532098] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 17.658135] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 17.770412] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0 My WiFi works. I can also pair Bluetooth keyboard. Since I don't really know how device drivers work in Linux I noticed line with error about `firmware-5.bin` in output of dmesg. So I took missing file from https://github.com/kvalo/ath10k- firmware/tree/master/QCA6174/hw3.0/4.4. It turned out to be bad idea because it botched wifi/bluetooth completely. Here is what I had in log [3.519354] ath10k_pci :3a:00.0: enabling device ( -> 0002) [3.521259] ath10k_pci :3a:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [3.765880] ath10k_pci :3a:00.0: Direct firmware load for ath10k/cal-pci-:3a:00.0.bin failed with error -2 [3.831220] ath10k_pci :3a:00.0: failed to fetch board data for ath10k/QCA6174/hw3.0 from bus=pci,bmi-chip-id=0,bmi-board-id=0/board-2.bin [5.887772] ath10k_pci :3a:00.0: Unknown eventid: 90118 [5.887786] ath10k_pci :3a:00.0: qca6174 hw3.2 (0x0503, 0x00340aff bmi 0:0) fw WLAN.RM.4.4-00022-QCARMSWPZ-2 fwapi 5 bdapi 1 htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features wowlan,ignore-otp [5.887789] ath10k_pci :3a:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.884160] ath10k_pci :3a:00.0: could not suspend target (-11) [8.966789] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0 [ 11.178547] ath10k_pci :3a:00.0: Unknown eventid: 90118 [
[Kernel-packages] [Bug 1694455] Re: Bluetooth: Cannot receive files
Thank you for reporting this bug to Ubuntu. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-bluetooth (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1694455 Title: Bluetooth: Cannot receive files Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: # Use case Ubuntu 17.04, quite fresh installation, updated. Bluetooth file transmission I want to send files to my smartphone, and receive files sent by my smartphone via bluetooth. I pair both devices, initiate file transfer from one of the devices, and the other device asks me what to do. # Problems This is a mix from usability and technical issues. 1. OBEX disabled (bug 1645631) The bluetooth file transmission service OBEX was not started. I started and enabled OBEX: `systemctl --user start obex` `systemctl --user enable obex` ``` Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service... Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 ``` 2. OBEX silently fails (this bug) After having OBEX enabled, I was able to transmit files from laptop to smartphone, yet I could not receive files on the laptop. In the system log, you could see that OBEX fails (please note `FORBIDDEN`): ``` Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected ``` I did not receive a popup notification asking me to receive the file or not. In the file sharing preferences `gnome-file-share-properties`, there is a setting to automatically receive files via bluetooth. With this box checked, you're finally able to receive files from your smartphone. Successful log for comparison: ``` Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected ``` # Expected behaviour OBEX is started by default to handle bluetooth file transfers. If no automatic file receipt is configured, a popup notification asks me if I want to receive the file or not. If this is not possible, there should be a notification pointing the user to the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694455/+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 1727914] Re: bluetoothd crashed with SIGEMT in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk
Fix Released (no crash reports after 17.04) ** Changed in: bluez (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1727914 Title: bluetoothd crashed with SIGEMT in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/98da419ed3c25ad6b4e2fe408d176d1abed4d08c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727914/+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 1738907] Re: Bluetooth audio latency / delay increasing on video streamig
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1738907 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1738907 Title: Bluetooth audio latency / delay increasing on video streamig Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: With my bluetooth headset (A2DP audio protocole) when I watch videos streaming with Google Chrome for example. there is a delay increasing between audio and video. I tried to change and set up the audio latency, but the delay increase, as much as I play bigger video ubuntu 17.04 or 17.10 64bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738907/+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 1264311] Re: BCM43142 bluetooth adapter not finding any bluetooth devices
Closed due to no response. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1264311 Title: BCM43142 bluetooth adapter not finding any bluetooth devices Status in bluez package in Ubuntu: Invalid Bug description: On my officially Ubuntu-certified Lenovo B590 laptop the BCM43142 bluetooth adapter is not working. I have two further bluetooth devices placed closely to the laptop, non-paired and each being able to discover the other respectively. None of them is able to discover the laptop, nor does 'hcitool scan' on the laptop find any devices. It does not give any errors though. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Dec 26 15:34:08 2013 InstallationDate: Installed on 2013-12-25 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 37613EG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=UUID=c379c17a-9869-47a8-b9b3-83be4e302040 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET74WW(1.11) dmi.board.asset.tag: Not Available dmi.board.name: 37613EG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn37613EG:pvrLenovoB590:rvnLENOVO:rn37613EG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37613EG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 1C:3E:84:E8:81:98 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1244 acl:0 sco:0 events:81 errors:0 TX bytes:2820 acl:0 sco:0 commands:77 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311/+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 418617] Re: Allow laptop users to use select mic
Closed due to no response. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/418617 Title: Allow laptop users to use select mic Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Won't Fix Status in linux-backports-modules-2.6.31 package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Sound Preferences is currently only allowing the use of the internal microphone of a laptop. But it will not allow you to switch to a microphone attached to the Mic jack of the laptop. This is a common use case for users as the internal microphone of the laptop records all ambient noise around the laptop. This relates to LP #322909 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/418617/+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 77010] Re: Overuse of system beep without volume control
Closed due to no response. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/77010 Title: Overuse of system beep without volume control Status in Ayatana: Invalid Status in One Hundred Papercuts: Fix Released Status in libgnome package in Ubuntu: Fix Released Status in linux package in Ubuntu: Won't Fix Status in module-init-tools package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in libgnome source package in Karmic: Fix Released Status in linux source package in Karmic: Won't Fix Status in module-init-tools source package in Karmic: Fix Released Status in pulseaudio source package in Karmic: Won't Fix Bug description: System 'beeps' have become omnipresent in gnome. When I unplug my power cord, the notification system emits a system beep. When I try to do quick find in Firefox and I type a word that doesn't exist in the document, it beeps. When I tab-autocomplete in a gnome-terminal, it beeps if there are no completions. There are numerous other software packages that behave similarly. This is a problem for multiple reasons. First of all, there are some cases where the beep is used inappropriately -- I really *don't care* that my power cord is unplugged - in fact I unplugged it! I appreciate the technology advances that gnome-power-management has made in recent history, but I feel like I just want it to `go away' most of the time - I don't care about most of the things it informs me (besides low battery). Firefox has color feedback in the "Find" bar, why do I need auditory feedback too? Second of all, I can't control the volume of the beep, or disable it in all cases. In the case of the gnome-terminal I can disable the console "bell", but that only solves a single instance of the problem. In most other cases, there is nothing I can do to prevent the beeps. This can be very obtrusive in quite environments, and simply annoying in other cases. On my laptop (recent Dell Latitude D620) the beep is incredibly loud - it is very noticeable. It would be great to have a toggle button in the system "sound" preferences, or better yet, a volume slider for the system bell. This is a large problem, affecting multiple packages and systems - I don't know the best way to fix it, but I do know that it is definitely an overall gnome UI issue. I've read that some programs literally just have the ASCII "BEL" coded into the source, so in some cases the problem may be unavoidable - I don't know enough of the technical details to recognize an appropriate solution. Any help dividing this into specific fixes for multiple projects or identifying the best place for an overall fix would be appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/dead-ayatana/+bug/77010/+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 1288055] Re: Nvidia and Pulseaudio
Closed due to no response. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1288055 Title: Nvidia and Pulseaudio Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Invalid Bug description: Nvidia está causando incompatibilidade no Ubuntu 13.10. Minha placa de vídeo e uma nVidia GeoForce 550 ti. A um bug também no pulseaudio, eu tenho que instalar um painel de controle pulseaudio para poder abilitar o microfone frontal para poder falar no Skype. Obrigado pela paciência. ASS : THAUAN7020 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-17-generic 3.11.0-17.31 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soneca 1417 F pulseaudio /dev/snd/controlC0: soneca 1417 F pulseaudio CurrentDmesg: [ 17.861452] atl1c :03:00.0: atl1c: eth0 NIC Link is Up<1000 Mbps Full Duplex> [ 41.596084] systemd-hostnamed[1896]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [ 86.328044] usb 1-8: reset high-speed USB device number 3 using ehci-pci [ 299.136040] atl1c :03:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. Date: Wed Mar 5 01:58:20 2014 HibernationDevice: RESUME=UUID=caa5d39c-44e4-4f1d-b2cc-529628b1c907 InstallationDate: Installed on 2014-03-03 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G41MT-S2P MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=544fb0e8-c375-4dca-9e2d-c1d058564b2e ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: G41MT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288055/+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 1750491] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1750491 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: artful -- 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/1750491 Title: Ubuntu 17.10.1 UEFI Bios Corruption - WinBook TW802 Tablet Status in linux package in Ubuntu: Incomplete Bug description: Winbook TW802 - Intel Atom Tablet with UEFI Bios 64bit cpu / 32bit bootloader Related models: TW700, TW800, TW801 & TW100 Recommend do not install V17.10.1 on those machines until issue resolved Previous Single boot Ubuntu 16.04.1 installation NO Bios issues: installed via isorespin from USB New Single boot Ubuntu 17.10.1 installation caused Corrupted Bios: installed via isorespin from USB uname -r = 4.13.0-32-generic Corruption prevents Bios access to USB, so cannot boot ClonZilla to restore prior image Ubuntu 17 boots to desktop but not fully functional: (issues are unrelated to this bug report) WinBook Bios Phoenix SecureCore Bios Version 1.00 IA32 Build 11/24/2014 Can access BIOS with F2 during boot But Bios hangs accessing "BOOT" tab that controls boot devices Will not display & cannot select any boot device Restoring Bios defaults does not fix issue Attempted Fix: Tried 17.10 "SPI" fix - bug #1734147 Neither method shown resolves the issue after fix applied uname -r = 4.15.0-041500rc6-generic Fix #1734147 creates other issues: Bug #1734147 fix prevents access to grub during boot prior to #1734147 fix,"shift" during boot opened grub menu after fix, cannot open grub with "shift" or "c" uninstalled the fix via method shown in #1734147 uname -r = 4.13.0-32-generic after #1734148 uninstalled & reboot Gathering Info for this bug report ubuntu-bug linux = gathers the information but; V17 touchpad issues prevent sending the data version.log & lspci-vnvn.log are attached. Once USB is accessed, I can restore prior image Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750491/+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 1750491] [NEW] Ubuntu 17.10.1 UEFI Bios Corruption - WinBook TW802 Tablet
Public bug reported: Winbook TW802 - Intel Atom Tablet with UEFI Bios 64bit cpu / 32bit bootloader Related models: TW700, TW800, TW801 & TW100 Recommend do not install V17.10.1 on those machines until issue resolved Previous Single boot Ubuntu 16.04.1 installation NO Bios issues: installed via isorespin from USB New Single boot Ubuntu 17.10.1 installation caused Corrupted Bios: installed via isorespin from USB uname -r = 4.13.0-32-generic Corruption prevents Bios access to USB, so cannot boot ClonZilla to restore prior image Ubuntu 17 boots to desktop but not fully functional: (issues are unrelated to this bug report) WinBook Bios Phoenix SecureCore Bios Version 1.00 IA32 Build 11/24/2014 Can access BIOS with F2 during boot But Bios hangs accessing "BOOT" tab that controls boot devices Will not display & cannot select any boot device Restoring Bios defaults does not fix issue Attempted Fix: Tried 17.10 "SPI" fix - bug #1734147 Neither method shown resolves the issue after fix applied uname -r = 4.15.0-041500rc6-generic Fix #1734147 creates other issues: Bug #1734147 fix prevents access to grub during boot prior to #1734147 fix,"shift" during boot opened grub menu after fix, cannot open grub with "shift" or "c" uninstalled the fix via method shown in #1734147 uname -r = 4.13.0-32-generic after #1734148 uninstalled & reboot Gathering Info for this bug report ubuntu-bug linux = gathers the information but; V17 touchpad issues prevent sending the data version.log & lspci-vnvn.log are attached. Once USB is accessed, I can restore prior image Regards. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: artful ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1750491/+attachment/5058643/+files/lspci-vnvn.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/1750491 Title: Ubuntu 17.10.1 UEFI Bios Corruption - WinBook TW802 Tablet Status in linux package in Ubuntu: Incomplete Bug description: Winbook TW802 - Intel Atom Tablet with UEFI Bios 64bit cpu / 32bit bootloader Related models: TW700, TW800, TW801 & TW100 Recommend do not install V17.10.1 on those machines until issue resolved Previous Single boot Ubuntu 16.04.1 installation NO Bios issues: installed via isorespin from USB New Single boot Ubuntu 17.10.1 installation caused Corrupted Bios: installed via isorespin from USB uname -r = 4.13.0-32-generic Corruption prevents Bios access to USB, so cannot boot ClonZilla to restore prior image Ubuntu 17 boots to desktop but not fully functional: (issues are unrelated to this bug report) WinBook Bios Phoenix SecureCore Bios Version 1.00 IA32 Build 11/24/2014 Can access BIOS with F2 during boot But Bios hangs accessing "BOOT" tab that controls boot devices Will not display & cannot select any boot device Restoring Bios defaults does not fix issue Attempted Fix: Tried 17.10 "SPI" fix - bug #1734147 Neither method shown resolves the issue after fix applied uname -r = 4.15.0-041500rc6-generic Fix #1734147 creates other issues: Bug #1734147 fix prevents access to grub during boot prior to #1734147 fix,"shift" during boot opened grub menu after fix, cannot open grub with "shift" or "c" uninstalled the fix via method shown in #1734147 uname -r = 4.13.0-32-generic after #1734148 uninstalled & reboot Gathering Info for this bug report ubuntu-bug linux = gathers the information but; V17 touchpad issues prevent sending the data version.log & lspci-vnvn.log are attached. Once USB is accessed, I can restore prior image Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750491/+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 1731060] Re: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di err
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1731060 Title: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Expired Bug description: The uninstall process run forever with this last line as output: run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-17-generic /boot/vmlinuz-4.13.0-17-generic ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1521 F pulseaudio casa 2790 F pulseaudio /dev/snd/controlC0: gdm1521 F pulseaudio casa 2790 F pulseaudio Date: Wed Nov 8 23:03:53 2017 ErrorMessage: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 HibernationDevice: RESUME=UUID=b1a7755c-92df-48fe-92d2-66de15fbb008 InstallationDate: Installed on 2015-10-23 (747 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20ANCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=942dc08f-9465-4002-8ffb-c1fbe03f7a04 ro 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: linux Title: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (18 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GLET80WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET80WW(2.34):bd07/23/2015:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731060/+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 1738921] Re: PGD 0
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1738921 Title: PGD 0 Status in linux package in Ubuntu: Expired Bug description: Running the latest 18.04 daily (desktop), selected try out, opened a terminal window and a few seconds after I got the error. I was going to select install ... ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4264 F pulseaudio /dev/snd/controlC2: ubuntu 4264 F pulseaudio /dev/snd/controlC0: ubuntu 4264 F pulseaudio CasperVersion: 1.387 Date: Tue Dec 19 03:33:40 2017 Failure: oops IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171218) MachineType: Dell Inc. Precision T5600 ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: PGD 0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0Y56T3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T5600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738921/+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 1737761] Re: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2
The fix for Bionic is not required as Bionic will be using version 0.7.x of ZFS (userspace + kernel) once the 4.15 kernel is released. I am working on a different 'reverse' compat fix for Bionic that will allow 0.7.x userspace of ZFS to support the older 0.6.x ZFS kernel driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1737761 Title: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2 Status in zfs-linux package in Ubuntu: Fix Committed Bug description: == SRU Justification, Xenial, Artful == Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks ZFS send/receive because of changes in the ioctl command structure. == Testcase == ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests will show a failure in ZFS SEND, with userspace zfs tools segfaulting. == Fix == Fix is to detect if ZFS kernel driver is version 0.7.x and copy the 0.6.5.x zfs ioctl command structure to a ZFS 0.7.x version, call the ioctl() and then copy the result back. == Regression Potential == This will only affect the ZFS ioctl interface and this can be fully tested using the ZFS autotests with 0.7.0 and 0.6.5.x ZFS enabled kernels to check for the compatibility change regressions. -- Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1737761/+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 1750479] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1750479 Title: 'perf record' does not work Status in linux package in Ubuntu: Confirmed Bug description: $ perf archive perf: 'archive' is not a perf-command. See 'perf --help'. $ perf --help usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file <- bench General framework for benchmark suites buildid-cache Manage build-id cache. buildid-listList the buildids in a perf.data file c2c Shared Data C2C/HITM Analyzer. config Get and set variables in a configuration file. dataData file related processing diffRead perf.data files and display the differential profile evlist List the event names in a perf.data file ftrace simple wrapper for kernel's ftrace functionality inject Filter to augment the events stream with additional information kallsymsSearches running kernel for symbols kmemTool to trace/measure kernel memory properties kvm Tool to trace/measure kvm guest os listList all symbolic event types lockAnalyze lock events mem Profile memory accesses record Run a command and record its profile into perf.data report Read perf.data (created by perf record) and display the profile sched Tool to trace/measure scheduler properties (latencies) script Read perf.data (created by perf record) and display trace output statRun a command and gather performance counter statistics testRuns sanity tests. timechart Tool to visualize total system behavior during a workload top System profiling tool. probe Define new dynamic tracepoints trace strace inspired tool See 'perf help COMMAND' for more information on a specific command. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-tools-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sbarcomb 2227 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 20:53:27 2018 HibernationDevice: RESUME=UUID=ac3f108f-4494-4f48-ae8c-fbab8a509ffc InstallationDate: Installed on 2017-10-19 (123 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp5s0no wireless extensions. tun0 no wireless extensions. MachineType: Alienware Aurora-R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: Alienware dmi.bios.version: A11 dmi.board.name: 07JNH0 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Aurora-R4 dmi.product.version: 00 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750479/+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 1746340] Re: Samsung SSD corruption (fsck needed)
Here's what I did: git clone bionic_git_url... cd ubuntu-bionic git checkout patch -p1 < nvme_reset.diff #(from your diff file) #gave an error about last line but I checked manually and it was ok (I guess was because of the number in the end: https://pastebin.com/j4Tz1fDa sudo apt-get build-dep linux-image-$(uname -r) fakeroot debian/rules clean fakeroot debian/rules binary-headers binary-generic binary-perarch after a long time, I copied linux-headers-4.15.0-9_4.15.0-9.10_all.deb linux-headers-4.15.0-9-generic_4.15.0-9.10_amd64.deb linux-image-4.15.0-9-generic_4.15.0-9.10_amd64.deb linux-image-extra-4.15.0-9-generic_4.15.0-9.10_amd64.deb and installed on my fresh ubuntu 17.10.1 install on the razer blade stealth by doing sudo dpkg -i *.deb then I added nvme_..._us=0 to grub and did sudo update-grub rebooted and used for a while (confirmed using uname-r that the new kernel was running). In the first time I did all this, the problem ocurred while installing updates. In the second time I tried, the error ocurred when tried to install virt-manager. Since the kernel worked perfectly except for that, I can only assume that your diff didn't go through. But if I do git checkout and then apply a diff to that tag, then I can simply cd to this folder and compile and I'll be using the diff, right? Thank you for your help! -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it bro
[Kernel-packages] [Bug 1750479] [NEW] 'perf record' does not work
Public bug reported: $ perf archive perf: 'archive' is not a perf-command. See 'perf --help'. $ perf --help usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file <- bench General framework for benchmark suites buildid-cache Manage build-id cache. buildid-listList the buildids in a perf.data file c2c Shared Data C2C/HITM Analyzer. config Get and set variables in a configuration file. dataData file related processing diffRead perf.data files and display the differential profile evlist List the event names in a perf.data file ftrace simple wrapper for kernel's ftrace functionality inject Filter to augment the events stream with additional information kallsymsSearches running kernel for symbols kmemTool to trace/measure kernel memory properties kvm Tool to trace/measure kvm guest os listList all symbolic event types lockAnalyze lock events mem Profile memory accesses record Run a command and record its profile into perf.data report Read perf.data (created by perf record) and display the profile sched Tool to trace/measure scheduler properties (latencies) script Read perf.data (created by perf record) and display trace output statRun a command and gather performance counter statistics testRuns sanity tests. timechart Tool to visualize total system behavior during a workload top System profiling tool. probe Define new dynamic tracepoints trace strace inspired tool See 'perf help COMMAND' for more information on a specific command. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-tools-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sbarcomb 2227 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 20:53:27 2018 HibernationDevice: RESUME=UUID=ac3f108f-4494-4f48-ae8c-fbab8a509ffc InstallationDate: Installed on 2017-10-19 (123 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp5s0no wireless extensions. tun0 no wireless extensions. MachineType: Alienware Aurora-R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: Alienware dmi.bios.version: A11 dmi.board.name: 07JNH0 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Aurora-R4 dmi.product.version: 00 dmi.sys.vendor: Alienware ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful -- 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/1750479 Title: 'perf record' does not work Status in linux package in Ubuntu: Confirmed Bug description: $ perf archive perf: 'archive' is not a perf-command. See 'perf --help'. $ perf --help usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file <- bench General framework for benchmark suites buildid-cache Manage build-id cache. buildid-listList the buildids in a perf.data file c2c Shared Data C2C/HITM Analyzer. config Get and set variables in a configuration file. dataData
[Kernel-packages] [Bug 1750379] Re: Distortion Realtek ALC887
This may be related to bug 1576420 with the same audio chip, but let's keep it separate for now... Please tell us: * Does the bug exist in Ubuntu 17.10.1 if you live boot that? * Does the bug persist if you try installing older or newer kernels? http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D * If there is a kernel version that doesn't have the bug, are you able to narrow it down to find the kernel version that introduced it? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750379 Title: Distortion Realtek ALC887 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sounds can distort even when not amplified. Amplification worked well for years before recent PulseAudio update. The audio is Realtek ALC887 under an IntelG41 Chipset with GA-G41M-Combo main board; Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 I am seeking to engage upstream for April LTS release. Windows have abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user going! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fleamour 1049 F pulseaudio /dev/snd/controlC2: fleamour 1049 F pulseaudio /dev/snd/controlC0: fleamour 1049 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 13:54:33 2018 InstallationDate: Installed on 2018-02-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750379/+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 1746340] Re: Samsung SSD corruption (fsck needed)
I installed ubuntu again, installed my compiled kernel, disabled updates. When installing a package (virt-manager), the error ocurred again. This package messes with kernel (kvm things) but I used before on your kernels and everything was fine (I didn't try to install while in your kernel though) -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "
[Kernel-packages] [Bug 1676884] Comment bridged from LTC Bugzilla
--- Comment From thiag...@br.ibm.com 2018-02-19 20:11 EDT--- Confirmed fixed in 17.10. Since 17.04 isn't supported anymore, closing bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1676884 Title: kdump-tools uses the wrong crashkernel command line parameter in ppc64le Status in The Ubuntu-power-systems project: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile package in Debian: Fix Released Bug description: == Comment: #0 - Thiago Jung Bauermann - 2017-03-24 11:44:39 == ---Problem Description--- kdump-tools uses the wrong crashkernel command line parameter in ppc64le: u1704le?? grep crashkernel /boot/grub/grub.cfg linux /boot/vmlinux-4.10.0-13-generic root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro crashkernel=384M-:128M 128M of reserved memory is too small for ppc64le. That happens because /etc/default/grub.d/kdump-tools.cfg links to the wrong file: u1704le?? ls -l /etc/default/grub.d/ total 8.0K lrwxrwxrwx 1 root root 39 Mar 24 13:34 kdump-tools.cfg -> /etc/default/grub.d/kdump-tools.default -rw-r--r-- 1 root root 80 Jan 5 08:07 kdump-tools.default -rw-r--r-- 1 root root 137 Jan 5 08:07 kdump-tools..ppc64el u1704le?? As can be seen, it should be pointing to kdump-tools..ppc64el but isn't. Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right. Possibly just a cosmetic issue, but it would be nice if that was fixed. Contact Information = thiag...@br.ibm.com ---uname output--- Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 8286-42A. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- sudo apt intall kdump-tools Select 'Yes' when asked whether kdump should be enabled. Userspace tool common name: kdump The userspace tool has the following bit modes: 64 bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for thiag...@br.ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1676884/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
I can't test the touchpad on 4.16, since it wont get up from suspend state. Tried it on 4.16-rc1 and 4.16-rc2 and it was the same. Resume from suspend worked on 4.15 but not on 4.16 and also on 4.15-rc9 i was able to get a half-working (cursor movement/tap, but no left/right buttons) touchpad after resuming the notebook from suspend. My device is a Chuwi Lapbook Air. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
FYI this is also happening for me, LTS 16.04.3 + HWE (kernel and xorg pkgs), Thinkpad x270 w/ Integrated Graphics Chipset: Intel(R) HD Graphics 620. -- 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/1742602 Title: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen and disk encryption passphrase prompt showed correctly, but when X started, the screen went blank. Logs showed everything running as normal despite the blank screen. Rebooting with the "nomodeset" kernel parameter fixed the issue but is not suitable as a permanent workaround since it disables my external monitor. Rebooting back into 4.10 also fixed the issue. I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried both intel and fbdev X drivers, both gave a blank screen. lsb_release: Ubuntu 16.04.3 LTS dpkg-query -W: linux-signed-image-generic-hwe-16.04 4.13.0.26.46 xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1 xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1 xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1 In Xorg.0.log with fbdev, I saw: [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument repeated 239 times. Typical kernel messages attached (from kern.log, reformatted to look like dmesg). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+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 1737761] Re: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2
The SRU of this to Artful is waiting on the release of the fix for Bionic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1737761 Title: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2 Status in zfs-linux package in Ubuntu: Fix Committed Bug description: == SRU Justification, Xenial, Artful == Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks ZFS send/receive because of changes in the ioctl command structure. == Testcase == ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests will show a failure in ZFS SEND, with userspace zfs tools segfaulting. == Fix == Fix is to detect if ZFS kernel driver is version 0.7.x and copy the 0.6.5.x zfs ioctl command structure to a ZFS 0.7.x version, call the ioctl() and then copy the result back. == Regression Potential == This will only affect the ZFS ioctl interface and this can be fully tested using the ZFS autotests with 0.7.0 and 0.6.5.x ZFS enabled kernels to check for the compatibility change regressions. -- Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1737761/+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 1746340] Re: Samsung SSD corruption (fsck needed)
I download a fresh 4.15.0-9 kernel, applied the diff and compiled just as in the page you sent. I then formatted, installed ubuntu 17.10.1, booted and enabled nvme_..._us=0, rebooted. Then I started installing updates. The error ocurred in the middle of it. I've never tried to install updates on the kernels you made me test. Could it be that it's breaking something? :( -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationD
[Kernel-packages] [Bug 1750457] Re: /usr/bin/cheese:11:g_value_object_collect_value:g_object_set_valist:g_object_set:cheese_camera_setup:cheese_application_setup_camera
** Package changed: linux (Ubuntu) => cheese (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750457 Title: /usr/bin/cheese:11:g_value_object_collect_value:g_object_set_valist:g_object_set:cheese_camera_setup:cheese_application_setup_camera Status in cheese package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding linux. This problem was most recently seen with package version 3.24.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6a59d211acff6c6b8f62994174d67fcb1a42926e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1750457/+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 1750457] [NEW] /usr/bin/cheese:11:g_value_object_collect_value:g_object_set_valist:g_object_set:cheese_camera_setup:cheese_application_setup_camera
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding linux. This problem was most recently seen with package version 3.24.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6a59d211acff6c6b8f62994174d67fcb1a42926e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety 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/1750457 Title: /usr/bin/cheese:11:g_value_object_collect_value:g_object_set_valist:g_object_set:cheese_camera_setup:cheese_application_setup_camera Status in cheese package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding linux. This problem was most recently seen with package version 3.24.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6a59d211acff6c6b8f62994174d67fcb1a42926e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1750457/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Hibernation works again with 4.15.0.10.11 from bionic-proposed as well ! -- 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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1661475] Re: i915 driver fails to resume display from suspend
I can confirm this bug with kernel 4.14.0-3-amd64 (debian- ker...@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-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/1661475 Title: i915 driver fails to resume display from suspend Status in linux package in Ubuntu: Expired Bug description: Symptom is that the LCD on the laptop (Dell Latitude E7450) stays off after boot. The laptop is running fine and can be reached via SSH, and rebooted. I can also kill the Xorg server at which point my display manager starts a new session and restores the driver. I believe the display driver is failing to resume as indicated by this kernel log line: Feb 2 19:08:33 LON-IX-L-763 kernel: [32839.947460] [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22 This looks like a regression in a recent kernel; this worked fine for ~1 year on Ubuntu 15.10 but I didn't test it on 16.04 so I can't confirm if it exists there. I suspend the machine by running pm-suspend, and it is resumed by the lid open event. I've attached the relevant time from /var/log/syslog which shows the kernel messages; this suspend was entered at 18:16:30 and woken up at 19:08:33. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: pv 4009 F...m pulseaudio /dev/snd/controlC1: pv 4009 F pulseaudio /dev/snd/controlC0: pv 4009 F pulseaudio /dev/snd/seq:pv 4126 F chrome Date: Fri Feb 3 03:23:55 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=adb71bac-b2c6-4c48-9f39-8b07f2b1d7b7 InstallationDate: Installed on 2015-07-24 (559 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=3cd0b0b6-f38d-45bf-85aa-e6578b5e37c4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-12-19 (45 days ago) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0R1VJD dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/18/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661475/+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 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Oh and I have also experienced random, unexplained OOM crashing of squid process recently on two separate machines (one i386 and one amd64) which seem to coincide in time with the upgrade from kernel 4.10 to 4.13 -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+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 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Hi guys. I'm experiencing problems with 4.13.0-36 on a cloud server (x64) with dynamic ram management. The server is provisioned to use up to 12GB of RAM, but it got so bad that only 1GB was visible, causing everything to a halt while swap usage went through the roof. Could it be related? And here is another instance of kernel 4.13 showing memory problems similar to what is being described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722778 I have reverted to 4.11.0-041100-generic #201705041534, for now -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+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 1750232] Re: Linux Mint/Ubuntu is taking modem off-hook during logon
I also have no idea what the following email, received in response to my message, means: ---begin - Original Message - From: To: Sent: Monday, February 19, 2018 14:36 Subject: Submit Request Failure An error occurred while processing a mail you sent to Launchpad's email interface. Failing command: status new => incomplete Error message: The 'status' argument expects 1 argument(s). It got 3. --end With such an overly-complicated and counter-productive "bug reporting" system, it's no wonder nothing gets fixed for years, if ever. -- 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/1750232 Title: Linux Mint/Ubuntu is taking modem off-hook during logon Status in linux package in Ubuntu: Incomplete Bug description: As of 15 February 2018 (and possibly earlier) the following bug has been reintroduced: When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the login screen), the Smartlink internal modem is taken off hook, and remains off hook (disabling the telephone line) until such time as the system is shut down or rebooted (in which case it goes off hook again after login). This annoying bug was introduced with Linux Mint 17.0 Trusty, and also occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial (which is based on Ubuntu 16.04). Now it is back, possibly as a result of the latest updates, possibly earlier. Yes, since Linux no longer supports the Smartlink modem, even with the modifications to the kernel that previously worked, I could simply disconnect the internal modem. But I dual-boot to Windoze, and DO use it without problem in Windoze, so it is more than an annoyance. I can understand Linux not supporting hardware, but it is unacceptable that Linux is sending commands to unsupported hardware whihc cause it to malfunction. As a Linux USER, I have no way of isolating the component causing the bug. It will require a trace of what is written to the COM port(s) during login. But, since it was fixed before, there should be some record of the cause and solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750232/+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
Re: [Kernel-packages] [Bug 1750232] Missing required logs.
I have no idea what "While running an Ubuntu kernel (not a mainline or third-party kernel)" means - Original Message - From: "Ubuntu Kernel Bot" To: Sent: Monday, February 19, 2018 13:00 Subject: [Bug 1750232] Missing required logs. This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1750232 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1750232 Title: Linux Mint/Ubuntu is taking modem off-hook during logon Status in linux package in Ubuntu: Incomplete Bug description: As of 15 February 2018 (and possibly earlier) the following bug has been reintroduced: When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the login screen), the Smartlink internal modem is taken off hook, and remains off hook (disabling the telephone line) until such time as the system is shut down or rebooted (in which case it goes off hook again after login). This annoying bug was introduced with Linux Mint 17.0 Trusty, and also occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial (which is based on Ubuntu 16.04). Now it is back, possibly as a result of the latest updates, possibly earlier. Yes, since Linux no longer supports the Smartlink modem, even with the modifications to the kernel that previously worked, I could simply disconnect the internal modem. But I dual-boot to Windoze, and DO use it without problem in Windoze, so it is more than an annoyance. I can understand Linux not supporting hardware, but it is unacceptable that Linux is sending commands to unsupported hardware whihc cause it to malfunction. As a Linux USER, I have no way of isolating the component causing the bug. It will require a trace of what is written to the COM port(s) during login. But, since it was fixed before, there should be some record of the cause and solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750232/+subscriptions -- 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/1750232 Title: Linux Mint/Ubuntu is taking modem off-hook during logon Status in linux package in Ubuntu: Incomplete Bug description: As of 15 February 2018 (and possibly earlier) the following bug has been reintroduced: When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the login screen), the Smartlink internal modem is taken off hook, and remains off hook (disabling the telephone line) until such time as the system is shut down or rebooted (in which case it goes off hook again after login). This annoying bug was introduced with Linux Mint 17.0 Trusty, and also occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial (which is based on Ubuntu 16.04). Now it is back, possibly as a result of the latest updates, possibly earlier. Yes, since Linux no longer supports the Smartlink modem, even with the modifications to the kernel that previously worked, I could simply disconnect the internal modem. But I dual-boot to Windoze, and DO use it without problem in Windoze, so it is more than an annoyance. I can understand Linux not supporting hardware, but it is unacceptable that Linux is sending commands to unsupported hardware whihc cause it to malfunction. As a Linux USER, I have no way of isolating the component causing the bug. It will require a trace of what is written to the COM port(s) during login. But, since it was fixed before, there should be some record of the cause and solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750232/+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 1750440] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1750440 Title: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: This package failed when I ran an `apt autoremove`. In particular, it appeared to fail as part of some sort of DKMS process. The first time I ran `apt autoremove` the DKMS process hung and apt stalled at 50% progress. I had to kill the process for apt to continue. The second time I ran `apt autoremove` the apt process stalled at 33% progress and eventually the crash detector ran and prompted me to report this bug. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-35.39-generic 4.13.13 Uname: Linux 4.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm4604 F pulseaudio drbarret 5314 F pulseaudio /dev/snd/controlC0: gdm4604 F pulseaudio drbarret 5314 F pulseaudio Date: Mon Feb 19 15:12:14 2018 ErrorMessage: subprocess installed post-removal script returned error exit status 1 HibernationDevice: RESUME=UUID=a63bd4bc-211b-488c-8af4-71983fced9d2 InstallationDate: Installed on 2017-04-01 (324 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-35-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2018-01-22 (28 days ago) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd12/22/2016:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750440/+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 1750440] [NEW] package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Public bug reported: This package failed when I ran an `apt autoremove`. In particular, it appeared to fail as part of some sort of DKMS process. The first time I ran `apt autoremove` the DKMS process hung and apt stalled at 50% progress. I had to kill the process for apt to continue. The second time I ran `apt autoremove` the apt process stalled at 33% progress and eventually the crash detector ran and prompted me to report this bug. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-35.39-generic 4.13.13 Uname: Linux 4.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm4604 F pulseaudio drbarret 5314 F pulseaudio /dev/snd/controlC0: gdm4604 F pulseaudio drbarret 5314 F pulseaudio Date: Mon Feb 19 15:12:14 2018 ErrorMessage: subprocess installed post-removal script returned error exit status 1 HibernationDevice: RESUME=UUID=a63bd4bc-211b-488c-8af4-71983fced9d2 InstallationDate: Installed on 2017-04-01 (324 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-35-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2018-01-22 (28 days ago) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd12/22/2016:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1750440 Title: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in linux package in Ubuntu: New Bug description: This package failed when I ran an `apt autoremove`. In particular, it appeared to fail as part of some sort of DKMS process. The first time I ran `apt autoremove` the DKMS process hung and apt stalled at 50% progress. I had to kill the process for apt to continue. The second time I ran `apt autoremove` the apt process stalled at 33% progress and eventually the crash detector ran and prompted me to report this bug. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-35.39-generic 4.13.13 Uname: Linux 4.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm4604 F pulseaudio drbarret 5314 F pulseaudio /dev/snd/controlC0: gdm4604 F pulseaudio drbarret 5314 F pulseaudio Date: Mon Feb 19 15:12:14 2018 ErrorMessage: subprocess installed post-removal script returned error exit status 1 HibernationDevice: RESUME=UUID=a63bd4bc-211b-488c-8af4-71983fced9d2 InstallationDate: Installed on 2017-04-01 (324 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-35-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7
[Kernel-packages] [Bug 1750441] [NEW] Boston-LC:bos1u1: Stress test on Qlogic Fibre Channel on Ubuntu KVM guest that caused KVM host crashed in qlt_free_session_done call
Public bug reported: Problem Description: = - PCI passthru Qlogic Fibre Channel adapter from Ubuntu 18.04 KVM host to Ubuntu 18.04 KVM guest. - Stress test on Qlogic Fibre Channel on Ubuntu KVM guest caused KVM host crashed in qlt_free_session_done call. - Below stack traces from KVM host: 91:mon> t [c000200e4e81fb60] c0081162f044 qlt_free_session_done+0x4ec/0x680 [qla2xxx] (unreliable) [c000200e4e81fc90] c012fbb8 process_one_work+0x298/0x5a0 [c000200e4e81fd20] c012ff58 worker_thread+0x98/0x630 [c000200e4e81fdc0] c0138ae8 kthread+0x1a8/0x1b0 [c000200e4e81fe30] c000b528 ret_from_kernel_thread+0x5c/0xb4 91:mon> e cpu 0x91: Vector: 300 (Data Access) at [c000200e4e81f8e0] pc: c0081162ed58: qlt_free_session_done+0x200/0x680 [qla2xxx] lr: c0081162eca8: qlt_free_session_done+0x150/0x680 [qla2xxx] sp: c000200e4e81fb60 msr: 9280b033 dar: 20 dsisr: 4000 current = 0xc000200e4e7b0e00 paca= 0xcfae3b00 softe: 0irq_happened: 0x01 pid = 1119, comm = kworker/145:1 Linux version 4.15.0-041500rc9-generic (kernel@tangerine) (gcc version 7.2.0 (Ubuntu 7.2.0-6ubuntu1)) #201801212130 SMP Mon Jan 22 03:36:42 UTC 2018 91:mon> r R00 = c0081162eca8 R16 = R01 = c000200e4e81fb60 R17 = R02 = c0081166ad60 R18 = R03 = 0001 R19 = R04 = c000200e44f8c7f8 R20 = c000200e618e7d80 R05 = f087 R21 = R06 = c0081165e6c8 R22 = 0001 R07 = c0081164adb0 R23 = c000200e44f99d24 R08 = R24 = 0402 R09 = R25 = R10 = R26 = c00fe1270c20 R11 = c0081163e170 R27 = c000200e44f99000 R12 = c0cfccf0 R28 = c0081164adb0 R13 = cfae3b00 R29 = c00fe1270c00 R14 = c0138948 R30 = c000200e44f8c7f8 R15 = c000200e4f019440 R31 = c00fe1270cc0 pc = c0081162ed58 qlt_free_session_done+0x200/0x680 [qla2xxx] cfar= c0081162ed1c qlt_free_session_done+0x1c4/0x680 [qla2xxx] lr = c0081162eca8 qlt_free_session_done+0x150/0x680 [qla2xxx] msr = 9280b033 cr = 28002284 ctr = c0cfccf0 xer = trap = 300 dar = 0020 dsisr = 4000 91:mon> The crash location seems close to this one fixed about two weeks ago: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/drivers/scsi/qla2xxx/qla_os.c?h=next-20180212&id=2ce87cc5b269510de9ca1185ca8a6e10ec78c069 scsi: qla2xxx: Fix memory corruption during hba reset test This patch fixes memory corrpution while performing HBA Reset test. Following stack trace is seen: [ 466.397219] BUG: unable to handle kernel NULL pointer dereference at 0020 [ 466.433669] IP: [] qlt_free_session_done+0x260/0x5f0 [qla2xxx] [ 466.467731] PGD 0 [ 466.476718] Oops: [#1] SMP - Luciano built and provided the patch with new Qlogic change on Friday last week. root@bos1u1p1:~/chavez# ls linux-image* linux-image-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_ppc64el.deb linux-image-extra-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_ppc64el.deb - I configured and ran same test over weekend and test ran good. KVM host did not crash in qlt_free_session_done call like before. - So the patch fixed the problem. Hi Canonical, Please review and consider this a request to pull in commit 2ce87cc5b269510de9ca1185ca8a6e10ec78c069 please. Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-164551 severity-high targetmilestone-inin1804 ** Tags added: architecture-ppc64le bugnameltc-164551 severity-high targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750441 Title: Boston-LC:bos1u1: Stress test on Qlogic Fibre Channel on Ubuntu KVM guest that caused KVM host crashed in qlt_free_session_done call Status in linux package in Ubuntu: New Bug description: Problem Description: = - PCI passthru Qlogic Fibre Channel adapter from Ubuntu 18.04 KVM host to Ubuntu 18.04 KVM guest. - Stress test on Qlogic Fibre Channel on Ubuntu KVM guest caused KVM host crashed in qlt_free_session_done call. - Below stack traces from KVM host: 91:mon> t [c000200e4e81fb60] c0081162f044 qlt_free_session_done+0x4ec/0x680 [qla2xxx] (unreliable) [c000200e4e81fc90] c012fbb8 process_one_work+0x298/0x5a0 [c000200e4e81fd20] c012ff58 worker_thread+0x98/0x630 [c000200e4e81fdc0
[Kernel-packages] [Bug 1750441] [NEW] Boston-LC:bos1u1: Stress test on Qlogic Fibre Channel on Ubuntu KVM guest that caused KVM host crashed in qlt_free_session_done call
You have been subscribed to a public bug: Problem Description: = - PCI passthru Qlogic Fibre Channel adapter from Ubuntu 18.04 KVM host to Ubuntu 18.04 KVM guest. - Stress test on Qlogic Fibre Channel on Ubuntu KVM guest caused KVM host crashed in qlt_free_session_done call. - Below stack traces from KVM host: 91:mon> t [c000200e4e81fb60] c0081162f044 qlt_free_session_done+0x4ec/0x680 [qla2xxx] (unreliable) [c000200e4e81fc90] c012fbb8 process_one_work+0x298/0x5a0 [c000200e4e81fd20] c012ff58 worker_thread+0x98/0x630 [c000200e4e81fdc0] c0138ae8 kthread+0x1a8/0x1b0 [c000200e4e81fe30] c000b528 ret_from_kernel_thread+0x5c/0xb4 91:mon> e cpu 0x91: Vector: 300 (Data Access) at [c000200e4e81f8e0] pc: c0081162ed58: qlt_free_session_done+0x200/0x680 [qla2xxx] lr: c0081162eca8: qlt_free_session_done+0x150/0x680 [qla2xxx] sp: c000200e4e81fb60 msr: 9280b033 dar: 20 dsisr: 4000 current = 0xc000200e4e7b0e00 paca= 0xcfae3b00 softe: 0irq_happened: 0x01 pid = 1119, comm = kworker/145:1 Linux version 4.15.0-041500rc9-generic (kernel@tangerine) (gcc version 7.2.0 (Ubuntu 7.2.0-6ubuntu1)) #201801212130 SMP Mon Jan 22 03:36:42 UTC 2018 91:mon> r R00 = c0081162eca8 R16 = R01 = c000200e4e81fb60 R17 = R02 = c0081166ad60 R18 = R03 = 0001 R19 = R04 = c000200e44f8c7f8 R20 = c000200e618e7d80 R05 = f087 R21 = R06 = c0081165e6c8 R22 = 0001 R07 = c0081164adb0 R23 = c000200e44f99d24 R08 = R24 = 0402 R09 = R25 = R10 = R26 = c00fe1270c20 R11 = c0081163e170 R27 = c000200e44f99000 R12 = c0cfccf0 R28 = c0081164adb0 R13 = cfae3b00 R29 = c00fe1270c00 R14 = c0138948 R30 = c000200e44f8c7f8 R15 = c000200e4f019440 R31 = c00fe1270cc0 pc = c0081162ed58 qlt_free_session_done+0x200/0x680 [qla2xxx] cfar= c0081162ed1c qlt_free_session_done+0x1c4/0x680 [qla2xxx] lr = c0081162eca8 qlt_free_session_done+0x150/0x680 [qla2xxx] msr = 9280b033 cr = 28002284 ctr = c0cfccf0 xer = trap = 300 dar = 0020 dsisr = 4000 91:mon> The crash location seems close to this one fixed about two weeks ago: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/drivers/scsi/qla2xxx/qla_os.c?h=next-20180212&id=2ce87cc5b269510de9ca1185ca8a6e10ec78c069 scsi: qla2xxx: Fix memory corruption during hba reset test This patch fixes memory corrpution while performing HBA Reset test. Following stack trace is seen: [ 466.397219] BUG: unable to handle kernel NULL pointer dereference at 0020 [ 466.433669] IP: [] qlt_free_session_done+0x260/0x5f0 [qla2xxx] [ 466.467731] PGD 0 [ 466.476718] Oops: [#1] SMP - Luciano built and provided the patch with new Qlogic change on Friday last week. root@bos1u1p1:~/chavez# ls linux-image* linux-image-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_ppc64el.deb linux-image-extra-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_ppc64el.deb - I configured and ran same test over weekend and test ran good. KVM host did not crash in qlt_free_session_done call like before. - So the patch fixed the problem. Hi Canonical, Please review and consider this a request to pull in commit 2ce87cc5b269510de9ca1185ca8a6e10ec78c069 please. Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-164551 severity-high targetmilestone-inin1804 -- Boston-LC:bos1u1: Stress test on Qlogic Fibre Channel on Ubuntu KVM guest that caused KVM host crashed in qlt_free_session_done call https://bugs.launchpad.net/bugs/1750441 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1747336] Re: need linux-firmware for rtl bt ( 0bda:b023)
On elementary OS Loki, adding xenial-proposed and upgrading resulted in a functional bluetooth device. The upgrade did, however, upgrade a lot of packages so I just have to assume the fix is was added from this bug. All that said, it's nice to have bluetooth working. Thank you for all that you do! For reference, the files added/updated were: The following NEW packages will be installed: linux-headers-4.13.0-36 linux-headers-4.13.0-36-generic linux-image-4.13.0-36-generic linux-image-extra-4.13.0-36-generic The following packages will be upgraded: bamfdaemon bluez bluez-cups bluez-obexd bsdutils console-setup console-setup-linux cpp-5 g++-5 gcc-5 gcc-5-base gnome-accessibility-themes initramfs-tools initramfs-tools-bin initramfs-tools-core keyboard-configuration libasan2 libatomic1 libaudit-common libaudit1 libbamf3-2 libblkid1 libbluetooth3 libcc1-0 libcilkrts5 libfdisk1 libgcc-5-dev libgomp1 libitm1 liblsan0 libmount1 libmpx0 libpulse-mainloop-glib0 libpulse0 libpulsedsp libpython-stdlib libquadmath0 libsane libsane-common libsmartcols1 libstdc++-5-dev libstdc++6 libtsan0 libubsan0 libuuid1 linux-firmware linux-generic-hwe-16.04 linux-headers-generic-hwe-16.04 linux-image-generic-hwe-16.04 linux-libc-dev mount pulseaudio pulseaudio-module-bluetooth pulseaudio-module-x11 pulseaudio-utils python python-minimal sane-utils ubuntu-drivers-common util-linux uuid-runtime -- 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/1747336 Title: need linux-firmware for rtl bt ( 0bda:b023) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Xenial: Fix Committed Bug description: == SRU Justification == [Test Case] boot the system and connnect the bt devices, all works well [Fix] Backport the uptream patch [Regression Potential] This only adds new firmware files, so no potential for regressions with already working hardware. --- rtl8822b_config.bin rtl8822b_fw.bin in the /lib/firmware/rtl_bt/ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1747336/+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 1750232] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1750232 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750232 Title: Linux Mint/Ubuntu is taking modem off-hook during logon Status in linux package in Ubuntu: Incomplete Bug description: As of 15 February 2018 (and possibly earlier) the following bug has been reintroduced: When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the login screen), the Smartlink internal modem is taken off hook, and remains off hook (disabling the telephone line) until such time as the system is shut down or rebooted (in which case it goes off hook again after login). This annoying bug was introduced with Linux Mint 17.0 Trusty, and also occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial (which is based on Ubuntu 16.04). Now it is back, possibly as a result of the latest updates, possibly earlier. Yes, since Linux no longer supports the Smartlink modem, even with the modifications to the kernel that previously worked, I could simply disconnect the internal modem. But I dual-boot to Windoze, and DO use it without problem in Windoze, so it is more than an annoyance. I can understand Linux not supporting hardware, but it is unacceptable that Linux is sending commands to unsupported hardware whihc cause it to malfunction. As a Linux USER, I have no way of isolating the component causing the bug. It will require a trace of what is written to the COM port(s) during login. But, since it was fixed before, there should be some record of the cause and solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750232/+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 1750232] Re: Linux Mint/Ubuntu is taking modem off-hook during logon
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750232 Title: Linux Mint/Ubuntu is taking modem off-hook during logon Status in linux package in Ubuntu: New Bug description: As of 15 February 2018 (and possibly earlier) the following bug has been reintroduced: When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the login screen), the Smartlink internal modem is taken off hook, and remains off hook (disabling the telephone line) until such time as the system is shut down or rebooted (in which case it goes off hook again after login). This annoying bug was introduced with Linux Mint 17.0 Trusty, and also occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial (which is based on Ubuntu 16.04). Now it is back, possibly as a result of the latest updates, possibly earlier. Yes, since Linux no longer supports the Smartlink modem, even with the modifications to the kernel that previously worked, I could simply disconnect the internal modem. But I dual-boot to Windoze, and DO use it without problem in Windoze, so it is more than an annoyance. I can understand Linux not supporting hardware, but it is unacceptable that Linux is sending commands to unsupported hardware whihc cause it to malfunction. As a Linux USER, I have no way of isolating the component causing the bug. It will require a trace of what is written to the COM port(s) during login. But, since it was fixed before, there should be some record of the cause and solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750232/+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 1750232] [NEW] Linux Mint/Ubuntu is taking modem off-hook during logon
You have been subscribed to a public bug: As of 15 February 2018 (and possibly earlier) the following bug has been reintroduced: When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the login screen), the Smartlink internal modem is taken off hook, and remains off hook (disabling the telephone line) until such time as the system is shut down or rebooted (in which case it goes off hook again after login). This annoying bug was introduced with Linux Mint 17.0 Trusty, and also occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial (which is based on Ubuntu 16.04). Now it is back, possibly as a result of the latest updates, possibly earlier. Yes, since Linux no longer supports the Smartlink modem, even with the modifications to the kernel that previously worked, I could simply disconnect the internal modem. But I dual-boot to Windoze, and DO use it without problem in Windoze, so it is more than an annoyance. I can understand Linux not supporting hardware, but it is unacceptable that Linux is sending commands to unsupported hardware whihc cause it to malfunction. As a Linux USER, I have no way of isolating the component causing the bug. It will require a trace of what is written to the COM port(s) during login. But, since it was fixed before, there should be some record of the cause and solution. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Linux Mint/Ubuntu is taking modem off-hook during logon https://bugs.launchpad.net/bugs/1750232 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1750385] Re: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel
Added requested (log)-files ** Attachment added: "output of apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750385/+attachment/5058313/+files/apport.linux.vnIMhd.apport ** 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/1750385 Title: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel Status in linux package in Ubuntu: Confirmed Bug description: When using Linux Mint 18.3 alongside with the 4.13.0-32 kernel the wifi signal is really really poor (while almost sitting on the respective router) whereas with the 4.10.0-38 it works like charm. I had to use a configuration file for getting the wifi to work properly (/etc/modprobe.d/rtl8723be.conf: options rtl8723be fwlps=0 ips=0 ant_sel=1) but chaning the antenna from 1 to 0 did not change anything with the 4.13 kernel. I am also running Manjaro Linux with the 4.14 kernel on my machine where the wifi is also working just fine (with antenna 0 though). cat /proc/version_signature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 (I tried using ubuntu-bug linux but it didn't work [The report belongs to a package that is not installed.]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750385/+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 1750046] Re: linux: 4.13.0-36.40 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1750046 Title: linux: 4.13.0-36.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1750047 (linux-azure), bug 1750048 (linux-azure-edge), bug 1750049 (linux-gcp), bug 1750052 (linux-hwe), bug 1750053 (linux-hwe-edge), bug 1750055 (linux-oem) derivatives: bug 1750057 (linux-raspi2) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1750046/+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 1710976] Re: Livepatch motd enhancement to show people how livepatch can help protect systems.
This bug was fixed in the package ubuntu-advantage-tools - 14 --- ubuntu-advantage-tools (14) bionic; urgency=medium * New upstream release: - repositories are only added after credentials are verified (LP: #1730361) - Livepatch MOTD script (LP: #1710976) - better "status" command output formatting (LP: #1719034) - sources.list.d files no longer contain credentials. The "auth.conf" facility is used instead. (LP: #1700611) - enabled Livepatch support for Bionic 18.04 LTS -- Andreas Hasenack Tue, 06 Feb 2018 09:58:03 -0200 ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: In Progress => 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/1710976 Title: Livepatch motd enhancement to show people how livepatch can help protect systems. Status in linux package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Invalid Bug description: This is a request to add an enhancement in our motd.d to inform users of the following: 1) that livepatch is available for their platform/kernel if they don't have it set up and installed right now. 2) When a system is protected by livepatch, and the system is currently patched (i.e., canonical-livepatch has active patches applied). 3) when a system is protected by livepatch and no livepatches exist yet for the kernel version, a single line message of 'This system is protected by canonical-livepatch." or similar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710976/+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 1744117] Re: ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel
Verified by our QA. Changing tag to "verification-done-xenial". Thanks, Jamie, below steps were helpful. This bug did not repro with [Ubuntu 16.04] + kernel 4.4.0-116-generic : 384.111 (R384_00) I've verified output through all channels (7.1) using Test Sound option in Sound Setting + by running different 4,6 channel clips using aplay. Connections were made using DP-HDMI dongle + DENON-AVR ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1744117 Title: ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Add support for 4/6/8 channel sound in 16.04 LTS kernel for future GPUs. This commit[1] first introduced in "Thu Jul 13 19:27:39 2017"[2] has what is needed base on discussion we had with nvidia: [1] - Commit https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table Add codec IDs for several recently released, pending, and historical NVIDIA GPU audio controllers to the patch table, to allow the correct patch functions to be selected for them. [2] - git describe --contains 74ec118152ea494a25ebb677cbc83a75c982ac5f v4.13-rc3~21^2~5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744117/+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 1750101] Re: package firmware-b43-installer 1:019-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1750101 Title: package firmware-b43-installer 1:019-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in b43-fwcutter package in Ubuntu: New Bug description: firmware-b43-installer not installed and not wifi installed ProblemType: Package DistroRelease: Ubuntu 17.10 Package: firmware-b43-installer 1:019-3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: b43-fwcutter:i386: Install firmware-b43-installer:i386: Install NULL: ConfigurePending Architecture: i386 Date: Sat Feb 17 12:26:06 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-02-17 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20180105) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1750101/+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 1736593] Re: ThunderX: TX failure unless checksum offload disabled
Thanks Dann. Scott is testing this and has found an additional issue, but we're not sure yet whether it's directly related or independent. He'll file a more detailed report or open another Launchpad as appropriate. -- 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/1736593 Title: ThunderX: TX failure unless checksum offload disabled Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: [Impact] Most attempts to use IPv6 on the ThunderX NIC will fail. [Test Case] Attempt an IPv6 TCP connection: $ wget -6 'http://www.kernel.org/' The connection will time out. [Regression Risk] The fix is upstream, and is limited to the ThunderX nicvf driver. [Workaround] Disable TX checksum offload: $ ethtool -K eth0 tx off [More Details] The issue first appears in Linux 4.12. A fix from Cavium has been merged upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736593/+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 1750101] Re: package firmware-b43-installer 1:019-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1750101 Title: package firmware-b43-installer 1:019-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in b43-fwcutter package in Ubuntu: New Bug description: firmware-b43-installer not installed and not wifi installed ProblemType: Package DistroRelease: Ubuntu 17.10 Package: firmware-b43-installer 1:019-3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: b43-fwcutter:i386: Install firmware-b43-installer:i386: Install NULL: ConfigurePending Architecture: i386 Date: Sat Feb 17 12:26:06 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-02-17 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20180105) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1750101/+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 1745959] Re: linux: 3.2.0-133.179 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Released + kernel-stable-phase-changed:Monday, 19. February 2018 18:03 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Released - kernel-stable-phase-changed:Monday, 19. February 2018 18:03 UTC ** Tags removed: kernel-release-tracking-bug-live -- 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/1745959 Title: linux: 3.2.0-133.179 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1745959/+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 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
According to [1], the :u quirk mentioned in this bug is equivalent to US_FL_IGNORE_UAS, which completely disables uas. The US_FL_NO_ATA_1X quirk can be specified in modprobe.conf as :t. I'm not sure what that quirk does. [1] https://en.opensuse.org/SDB:USB_3.0_Hard_Drive_troubleshooting Unfortunately I can't test this against my STEA1000400 as it is currently in off-site storage, but I'll try this when I get it 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/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+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 1745959] Re: linux: 3.2.0-133.179 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress -- 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/1745959 Title: linux: 3.2.0-133.179 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: In Progress Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1745959/+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 1749090] Re: linux-aws: 4.4.0-1014.14 -proposed tracker
Regression test results look good. ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1749090 Title: linux-aws: 4.4.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1749089 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749090/+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 1749093] Re: linux-aws: 4.4.0-1052.61 -proposed tracker
Regression test results look good. ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1749093 Title: linux-aws: 4.4.0-1052.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1749089 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749093/+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 1744870] Re: Xenial update to 4.4.102 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- 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/1744870 Title: Xenial update to 4.4.102 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.102 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.102 stable release shall be applied: * mm, hwpoison: fixup "mm: check the return value of lookup_page_ext for all call sites" * Linux 4.4.102 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744870/+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 1737761] Re: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2
** Description changed: + == SRU Justification == + + Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks + ZFS send/receive because of changes in the ioctl command structure. + + == Testcase == + + ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests will + show a failure in ZFS SEND, with userspace zfs tools segfaulting. + + == Fix == + + Fix is to detect if ZFS kernel driver is version 0.7.x and copy the + 0.6.5.x zfs ioctl command structure to a ZFS 0.7.x version, call the + ioctl() and then copy the result back. + + == Regression Potential == + + This will only affect the ZFS ioctl interface and this can be fully + tested using the ZFS autotests with 0.7.0 and 0.6.5.x ZFS enabled + kernels to check for the compatibility change regressions. + + -- + + Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz ** Description changed: - == SRU Justification == + == SRU Justification, Xenial, Artful == Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks ZFS send/receive because of changes in the ioctl command structure. == Testcase == ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests will show a failure in ZFS SEND, with userspace zfs tools segfaulting. == Fix == Fix is to detect if ZFS kernel driver is version 0.7.x and copy the 0.6.5.x zfs ioctl command structure to a ZFS 0.7.x version, call the ioctl() and then copy the result back. == Regression Potential == This will only affect the ZFS ioctl interface and this can be fully tested using the ZFS autotests with 0.7.0 and 0.6.5.x ZFS enabled kernels to check for the compatibility change regressions. -- - Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz ** Changed in: zfs-linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1737761 Title: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2 Status in zfs-linux package in Ubuntu: Fix Committed Bug description: == SRU Justification, Xenial, Artful == Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks ZFS send/receive because of changes in the ioctl command structure. == Testcase == ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests will show a failure in ZFS SEND, with userspace zfs tools segfa
[Kernel-packages] [Bug 1750046] Re: linux: 4.13.0-36.40 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750046 Title: linux: 4.13.0-36.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1750047 (linux-azure), bug 1750048 (linux-azure-edge), bug 1750049 (linux-gcp), bug 1750052 (linux-hwe), bug 1750053 (linux-hwe-edge), bug 1750055 (linux-oem) derivatives: bug 1750057 (linux-raspi2) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1750046/+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 1744794] Re: Xenial update to 4.4.101 stable release
On comment #1: The patch that was skipped mentions that db3cbfff5bcc0 "NVMe: IO queue deletion re-write" fixes the issue in a different manner but would not qualify as a stable candidate due to its size. But as you found we did a rather large backport for bug #1531539 which does include the mentioned patch (already applied pre-release of Xenial in Ubuntu-4.4.0-9.24). So it is indeed not needed in Xenial. ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- 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/1744794 Title: Xenial update to 4.4.101 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.101 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.101 stable release shall be applied: * tcp: do not mangle skb->cb[] in tcp_make_synack() * netfilter/ipvs: clear ipvs_property flag when SKB net namespace changed * bonding: discard lowest hash bit for 802.3ad layer3+4 * vlan: fix a use-after-free in vlan_device_event() * af_netlink: ensure that NLMSG_DONE never fails in dumps * sctp: do not peel off an assoc from one netns to another one * fealnx: Fix building error on MIPS * net/sctp: Always set scope_id in sctp_inet6_skb_msgname * ima: do not update security.ima if appraisal status is not INTEGRITY_PASS * serial: omap: Fix EFR write on RTS deassertion * arm64: fix dump_instr when PAN and UAO are in use * nvme: Fix memory order on async queue deletion * ocfs2: should wait dio before inode lock in ocfs2_setattr() * ipmi: fix unsigned long underflow * mm/page_alloc.c: broken deferred calculation * coda: fix 'kernel memory exposure attempt' in fsync * mm: check the return value of lookup_page_ext for all call sites * mm/page_ext.c: check if page_ext is not prepared * mm/pagewalk.c: report holes in hugetlb ranges * Linux 4.4.101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744794/+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 1749090] Re: linux-aws: 4.4.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1749090 Title: linux-aws: 4.4.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1749089 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749090/+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 1750366] Re: Strange versioning in 18.04 Bionic Beaver
According to the World of Google: https://www.google.co.uk/search?q=%22apport-collect%22+headless This has been an issue since 2010 and as best I can tell, still remains unfixed. Would be pleased to stand corrected on this matter. -- 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/1750366 Title: Strange versioning in 18.04 Bionic Beaver Status in linux package in Ubuntu: Incomplete Bug description: System: Ubuntu Server 18.04 LTS Alpha 2 installed within Citrix XenServer 7.0. Installed Citrix' 'guest-tools', confirmed on status page as having v7.0 tools working. Ran 'apt update', 'apt dist-upgrade' and was offered 'xe-guest- utilities' as one of the many packages being installed. Cancelled the upgrade to 'apt show' that package and found it to be v7.4. Happy that it was a newer version, started the upgrade && rebooted. Upon booting, the status page revealed v6.6 was installed, surely a backwards step and in spite of v7.4 having just been installed! I then checked with Citrix and they're only up to XenServer 7.3! All being said and done, the client tools allow interaction (ie, XenCenter initiated clean shutdown and reboot* requests, virtual drivers for Net and Blk front devices detected). However, the versioning seems awry. Is having v6.6 on v7.0 going to have an impact on performance, say for example, by using outdated APIs? Looking forward to clarification on the subject. Modiford, Ubuntu and XenServer fanboi :-) * except for the 'Soft Lock CPU' bug documented here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750366/+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 1744794] Re: Xenial update to 4.4.101 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1744794 Title: Xenial update to 4.4.101 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.101 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.101 stable release shall be applied: * tcp: do not mangle skb->cb[] in tcp_make_synack() * netfilter/ipvs: clear ipvs_property flag when SKB net namespace changed * bonding: discard lowest hash bit for 802.3ad layer3+4 * vlan: fix a use-after-free in vlan_device_event() * af_netlink: ensure that NLMSG_DONE never fails in dumps * sctp: do not peel off an assoc from one netns to another one * fealnx: Fix building error on MIPS * net/sctp: Always set scope_id in sctp_inet6_skb_msgname * ima: do not update security.ima if appraisal status is not INTEGRITY_PASS * serial: omap: Fix EFR write on RTS deassertion * arm64: fix dump_instr when PAN and UAO are in use * nvme: Fix memory order on async queue deletion * ocfs2: should wait dio before inode lock in ocfs2_setattr() * ipmi: fix unsigned long underflow * mm/page_alloc.c: broken deferred calculation * coda: fix 'kernel memory exposure attempt' in fsync * mm: check the return value of lookup_page_ext for all call sites * mm/page_ext.c: check if page_ext is not prepared * mm/pagewalk.c: report holes in hugetlb ranges * Linux 4.4.101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744794/+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 1744639] Re: Xenial update to 4.4.100 stable release
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- 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/1744639 Title: Xenial update to 4.4.100 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.100 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.100 stable release shall be applied: * media: imon: Fix null-ptr-deref in imon_probe * media: dib0700: fix invalid dvb_detach argument * ext4: fix data exposure after a crash * KVM: x86: fix singlestepping over syscall * bpf: don't let ldimm64 leak map addresses on unprivileged * xen-blkback: don't leak stack data via response ring * sctp: do not peel off an assoc from one netns to another one * net: cdc_ether: fix divide by 0 on bad descriptors * net: qmi_wwan: fix divide by 0 on bad descriptors * arm: crypto: reduce priority of bit-sliced AES cipher * Bluetooth: btusb: fix QCA Rome suspend/resume * dmaengine: dmatest: warn user when dma test times out * extcon: palmas: Check the parent instance to prevent the NULL * fm10k: request reset when mbx->state changes * ARM: dts: Fix compatible for ti81xx uarts for 8250 * ARM: dts: Fix am335x and dm814x scm syscon to probe children * ARM: OMAP2+: Fix init for multiple quirks for the same SoC * ARM: dts: Fix omap3 off mode pull defines * ata: ATA_BMDMA should depend on HAS_DMA * ata: SATA_HIGHBANK should depend on HAS_DMA * ata: SATA_MV should depend on HAS_DMA * drm/sti: sti_vtg: Handle return NULL error from devm_ioremap_nocache * igb: reset the PHY before reading the PHY ID * igb: close/suspend race in netif_device_detach * igb: Fix hw_dbg logging in igb_update_flash_i210 * scsi: ufs-qcom: Fix module autoload * scsi: ufs: add capability to keep auto bkops always enabled * staging: rtl8188eu: fix incorrect ERROR tags from logs * scsi: lpfc: Add missing memory barrier * scsi: lpfc: FCoE VPort enable-disable does not bring up the VPort * scsi: lpfc: Correct host name in symbolic_name field * scsi: lpfc: Correct issue leading to oops during link reset * scsi: lpfc: Clear the VendorVersion in the PLOGI/PLOGI ACC payload * ALSA: vx: Don't try to update capture stream before running * ALSA: vx: Fix possible transfer overflow * backlight: lcd: Fix race condition during register * backlight: adp5520: Fix error handling in adp5520_bl_probe() * gpu: drm: mgag200: mgag200_main:- Handle error from pci_iomap * ALSA: hda/realtek - Add new codec ID ALC299 * arm64: dts: NS2: reserve memory for Nitro firmware * ixgbe: fix AER error handling * ixgbe: handle close/suspend race with netif_device_detach/present * ixgbe: Reduce I2C retry count on X550 devices * ixgbe: add mask for 64 RSS queues * ixgbe: do not disable FEC from the driver * staging: rtl8712: fixed little endian problem * MIPS: End asm function prologue macros with .insn * mm: add PHYS_PFN, use it in __phys_to_pfn() * MIPS: init: Ensure bootmem does not corrupt reserved memory * MIPS: init: Ensure reserved memory regions are not added to bootmem * MIPS: Netlogic: Exclude netlogic,xlp-pic code from XLR builds * Revert "crypto: xts - Add ECB dependency" * Revert "uapi: fix linux/rds.h userspace compilation errors" * uapi: fix linux/rds.h userspace compilation error * uapi: fix linux/rds.h userspace compilation errors * USB: usbfs: compute urb->actual_length for isochronous * USB: Add delay-init quirk for Corsair K70 LUX keyboards * USB: serial: qcserial: add pid/vid for Sierra Wireless EM7355 fw update * USB: serial: garmin_gps: fix I/O after failed probe and remove * USB: serial: garmin_gps: fix memory leak on probe errors * Linux 4.4.100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744639/+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 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
successfully tested with bug 1743746 ** Tags removed: verification-needed-artful verification-queens-needed ** Tags added: verification-done-artful verification-queens-done -- 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/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+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 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC
This bug was fixed in the package debian-installer - 20101020ubuntu530 --- debian-installer (20101020ubuntu530) bionic; urgency=medium [ dann frazier ] * netboot/arm64: Include nic-firmware. LP: #1743638. [ Dimitri John Ledkov ] * Drop the hunk that detects potentially redundant libraries in /lib and removes them. This currently, only removes libcrypto.so.1.0 (due to libcrypto.so.1.1 presence in /usr/lib) and thus breaks network-console/openssh-server. LP: #1749442 -- Dimitri John Ledkov Thu, 15 Feb 2018 11:49:25 + ** Changed in: debian-installer (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1743638 Title: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe-edge package in Ubuntu: Invalid Status in debian-installer source package in Xenial: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-firmware source package in Xenial: Fix Committed Status in linux-hwe source package in Xenial: Fix Committed Status in linux-hwe-edge source package in Xenial: Fix Committed Status in debian-installer source package in Artful: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-firmware source package in Artful: Fix Committed Status in linux-hwe source package in Artful: Invalid Status in linux-hwe-edge source package in Artful: Invalid Status in debian-installer source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-firmware source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Invalid Bug description: [Impact] Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work. [Test Case] Attempt to use the netinst installer to install a system over this NIC. [Regression Risk] The fix is just add to add additional kernel modules and firmware to the installer to support this NIC. The biggest risk I see there is that it increases the size of the installer, which could potentially grow to bit for some smaller systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+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 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC
This bug was fixed in the package linux-firmware - 1.171 --- linux-firmware (1.171) bionic; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 2aa2ac2e9c09f09b0cfb6fc320c1e2d281530fa0 - linux-firmware: update Marvell PCIe-USB8897-A2 firmware image - linux-firmware: update Marvell PCIe-USB8997 firmware image - linux-firmware/i915: Add Geminilake DMC version 1.04 - linux-firmware/i915: Add Cannonlake DMC version 1.06 - linux-firmware: GuC firmware for Skylake v9.33 - linux-firmware: GuC firmware for Broxton v9.29 - linux-firmware: GuC firmware for kabylake v9.39 - linux-firmware: update Marvell PCIe-USB8997 firmware image - linux-firmware: DMC firmware for kabylake v1.04 - iwlwifi: update firmwares for 3160, 3168, 7265D, 8000C and 8265 - iwlwifi: update firmwares for 3160, 3168, 7260, 7265 and 7265D - iwlwifi: add new firmware version 34 for 8000C and 8265 - iwlwifi: add firmware version 33 for new 9000 series - linux-firmware: intel: Update Geminilake audio firmware - linux-firmware: liquidio: update firmware to v1.7.0 - iwlwifi: add firmware version 34 for new 9000 series - qcom: add firmware files for Adreno a530 - qcom: add venus firmware files for v4.2 - qed: Add firmware 8.33.1.0 - amdgpu: add new CP firmware for polaris chips - s2255drv: f2255usb: firmware version 1.2.8 - WHENCE: Fix typo in entry for iwlwifi-8265-34.ucode - WHENCE: Add missing entry for mlxsw_spectrum firmware - Mellanox: Add new mlxsw_spectrum firmware 13.1530.152 - brcm: update firmware for bcm4339 - brcm: introduce firmware for bcm43430 revision 0 - brcm: update firmware for bcm4354 - brcm: update firmware for bcm4356 - brcm: update firmware for bcm4358 - linux-firmware: DMC firmware for skylake v1.27 - amdgpu: update vega10 vce firmware - amdgpu: add firmware for Raven - linux-firmware: Add firmware file for Intel Bluetooth 9560 - linux-firmware: Add firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Update firmware patch for Intel Bluetooth 8260 - nfp: update firmware for Agilio CX SmartNICs - nfp: change firmware directory layout - nfp: add firmware for tc-flower - Revert commits a42f895, c113d33, 041aff8, 73d13b5 - linux-firmware: Add firmware file for Intel Bluetooth 9560 - linux-firmware: Add firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Update firmware patch for Intel Bluetooth 8260 - brcm: add CYW4373 firmwares and Cypress license file - linux-firmware: liquidio: add v1.7.0 vswitch firmware - nvidia: add GP108 signed firmware - linux-firmware: DMC firmware for cannonlake v1.07 - rtlwifi: rtl8723de: Add firmware for new driver/device - wl127x/wl128x: update firmwares - wl18xx: update firmware file 8.9.0.0.76 - linux-firmware: intel: Update Geminilake audio firmware - linux-firmware: update Marvell PCIe-USB8897/8997 firmware image to add WPA2 vulnerability fix - cxgb4: update firmware to revision 1.17.14.0 - mediatek: update MT8173 VPU firmware to 1.0.8 [decoder h264] Fix h264 decoder output delay for some low latency bitstreams - amdgpu: update vce and uvd firmware for Vega10 - amdgpu: update vcn firmware for raven - amdgpu: update vce firmware for Fiji - amdgpu: update uvd firmware for polaris asics - linux-firmware: intel: Update Kabylake audio firmware - wl127x/wl128x: update PLT firmwares - linux-firmware: Update firmware file for Intel Bluetooth,8265 - linux-firmware: Add firmware file for Intel Bluetooth,9260 - linux-firmware: Add firmware file for Intel Bluetooth,9560 * UBUNTU: Update nic-firmware.lst for 4.14 * UBUNTU: Update nic-firmware.lst for 4.15 [ dann frazier ] * nic-firmware: Add QLogic QED firmware (LP: #1743638) -- Seth Forshee Fri, 09 Feb 2018 15:32:29 -0600 -- 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/1743638 Title: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe-edge package in Ubuntu: Invalid Status in debian-installer source package in Xenial: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-firmware source package in Xenial: Fix Committed Status in linux-hwe source package in Xenial: Fix Committed Status in linux-hwe-edge source package in Xenial: Fix Committed Status in debian-installer so
[Kernel-packages] [Bug 1750388] Re: 17.10 - BPF test tool build with errors
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1750388 Title: 17.10 - BPF test tool build with errors Status in Ubuntu on IBM z Systems: Invalid Status in linux package in Ubuntu: Invalid Bug description: Rebuild problem of BPFC test tool with Ubuntu 17.10 uname -a Linux s8360046 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:33:05 UTC 2017 s390x s390x s390x GNU/Linux cat ./etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10" root@s8360046:/# When I compile file test_pkt_access.c in directory linux/tools/testing/selftest/bpf I get a compile error. root@s8360046:~/linux/tools/testing/selftests/bpf# clang -I. -I./include/uapi -I../../../include/uapi -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:8: /usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not found #include ^~ 1 error generated. # File bits/libc-header-start.h is located in directory /usr/include/s390x-linux-gnu which is not part of the include directory list: # find /usr/ -name libc-header-start.h /usr/include/s390x-linux-gnu/bits/libc-header-start.h # When I add this directory to the include pathes of the compile, I get another error: # clang -I. -I./include/uapi -I../../../include/uapi -I/usr/include/s390x-linux-gnu -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:12: In file included from /usr/include/linux/ip.h:20: In file included from /usr/include/s390x-linux-gnu/asm/byteorder.h:4: In file included from /usr/include/linux/byteorder/big_endian.h:12: In file included from /usr/include/linux/swab.h:6: /usr/include/s390x-linux-gnu/asm/swab.h:52:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ /usr/include/s390x-linux-gnu/asm/swab.h:80:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ 2 errors generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750388/+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 1750388] Re: 17.10 - BPF test tool build with errors
I believe this is third party source that you are trying to build, not using Ubuntu package build procedures, with a non-default compiler. This is out of scope to provide support for. Why are you using clang, instead of gcc, btw? I believe you will have more success if you use the default Ubuntu gcc compiler. ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-z-systems Status: New => 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/1750388 Title: 17.10 - BPF test tool build with errors Status in Ubuntu on IBM z Systems: Invalid Status in linux package in Ubuntu: Invalid Bug description: Rebuild problem of BPFC test tool with Ubuntu 17.10 uname -a Linux s8360046 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:33:05 UTC 2017 s390x s390x s390x GNU/Linux cat ./etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10" root@s8360046:/# When I compile file test_pkt_access.c in directory linux/tools/testing/selftest/bpf I get a compile error. root@s8360046:~/linux/tools/testing/selftests/bpf# clang -I. -I./include/uapi -I../../../include/uapi -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:8: /usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not found #include ^~ 1 error generated. # File bits/libc-header-start.h is located in directory /usr/include/s390x-linux-gnu which is not part of the include directory list: # find /usr/ -name libc-header-start.h /usr/include/s390x-linux-gnu/bits/libc-header-start.h # When I add this directory to the include pathes of the compile, I get another error: # clang -I. -I./include/uapi -I../../../include/uapi -I/usr/include/s390x-linux-gnu -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:12: In file included from /usr/include/linux/ip.h:20: In file included from /usr/include/s390x-linux-gnu/asm/byteorder.h:4: In file included from /usr/include/linux/byteorder/big_endian.h:12: In file included from /usr/include/linux/swab.h:6: /usr/include/s390x-linux-gnu/asm/swab.h:52:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ /usr/include/s390x-linux-gnu/asm/swab.h:80:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ 2 errors generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750388/+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 1744639] Re: Xenial update to 4.4.100 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1744639 Title: Xenial update to 4.4.100 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.100 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.100 stable release shall be applied: * media: imon: Fix null-ptr-deref in imon_probe * media: dib0700: fix invalid dvb_detach argument * ext4: fix data exposure after a crash * KVM: x86: fix singlestepping over syscall * bpf: don't let ldimm64 leak map addresses on unprivileged * xen-blkback: don't leak stack data via response ring * sctp: do not peel off an assoc from one netns to another one * net: cdc_ether: fix divide by 0 on bad descriptors * net: qmi_wwan: fix divide by 0 on bad descriptors * arm: crypto: reduce priority of bit-sliced AES cipher * Bluetooth: btusb: fix QCA Rome suspend/resume * dmaengine: dmatest: warn user when dma test times out * extcon: palmas: Check the parent instance to prevent the NULL * fm10k: request reset when mbx->state changes * ARM: dts: Fix compatible for ti81xx uarts for 8250 * ARM: dts: Fix am335x and dm814x scm syscon to probe children * ARM: OMAP2+: Fix init for multiple quirks for the same SoC * ARM: dts: Fix omap3 off mode pull defines * ata: ATA_BMDMA should depend on HAS_DMA * ata: SATA_HIGHBANK should depend on HAS_DMA * ata: SATA_MV should depend on HAS_DMA * drm/sti: sti_vtg: Handle return NULL error from devm_ioremap_nocache * igb: reset the PHY before reading the PHY ID * igb: close/suspend race in netif_device_detach * igb: Fix hw_dbg logging in igb_update_flash_i210 * scsi: ufs-qcom: Fix module autoload * scsi: ufs: add capability to keep auto bkops always enabled * staging: rtl8188eu: fix incorrect ERROR tags from logs * scsi: lpfc: Add missing memory barrier * scsi: lpfc: FCoE VPort enable-disable does not bring up the VPort * scsi: lpfc: Correct host name in symbolic_name field * scsi: lpfc: Correct issue leading to oops during link reset * scsi: lpfc: Clear the VendorVersion in the PLOGI/PLOGI ACC payload * ALSA: vx: Don't try to update capture stream before running * ALSA: vx: Fix possible transfer overflow * backlight: lcd: Fix race condition during register * backlight: adp5520: Fix error handling in adp5520_bl_probe() * gpu: drm: mgag200: mgag200_main:- Handle error from pci_iomap * ALSA: hda/realtek - Add new codec ID ALC299 * arm64: dts: NS2: reserve memory for Nitro firmware * ixgbe: fix AER error handling * ixgbe: handle close/suspend race with netif_device_detach/present * ixgbe: Reduce I2C retry count on X550 devices * ixgbe: add mask for 64 RSS queues * ixgbe: do not disable FEC from the driver * staging: rtl8712: fixed little endian problem * MIPS: End asm function prologue macros with .insn * mm: add PHYS_PFN, use it in __phys_to_pfn() * MIPS: init: Ensure bootmem does not corrupt reserved memory * MIPS: init: Ensure reserved memory regions are not added to bootmem * MIPS: Netlogic: Exclude netlogic,xlp-pic code from XLR builds * Revert "crypto: xts - Add ECB dependency" * Revert "uapi: fix linux/rds.h userspace compilation errors" * uapi: fix linux/rds.h userspace compilation error * uapi: fix linux/rds.h userspace compilation errors * USB: usbfs: compute urb->actual_length for isochronous * USB: Add delay-init quirk for Corsair K70 LUX keyboards * USB: serial: qcserial: add pid/vid for Sierra Wireless EM7355 fw update * USB: serial: garmin_gps: fix I/O after failed probe and remove * USB: serial: garmin_gps: fix memory leak on probe errors * Linux 4.4.100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744639/+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
