[Kernel-packages] [Bug 1260431] Re: update-grub hangs under 3.11.0-3-generic
Thanks for the help. After a while modprobe btrfs hangs again, specifically on "insmod /lib/modules/3.13.0-88-generic/kernel/lib/raid6/raid6_pq.ko" and "insmod /lib/modules/3.13.0-88-generic/kernel/fs/btrfs/btrfs.ko". Even after installing btrfs-tools. -- 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/1260431 Title: update-grub hangs under 3.11.0-3-generic Status in linux package in Ubuntu: Triaged Bug description: I have a saucy/amd64 instance that was booted using the 20130822 image (checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on 2013-08-29, which I finally updated today. During the upgrade, modprobe btrfs hung in init_module(). If I kill modprobe, the upgrade finishes. The apport gathering is on the new kernel, since apport declined to file a bug with the 3.11.0-3-generic kernel running. filing here for historical purposes, I expect. The problem does not reproduce on a current machine running 3.11.0-14-generic. lamont ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 12 17:45 seq crw-rw 1 root audio 116, 33 Dec 12 17:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 10.105412] init: plymouth-stop pre-start process (1008) terminated with status 1 Date: Thu Dec 12 17:45:40 2013 Ec2AMI: ami-0005 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=25707b7a-3d31-4823-831f-ed5306116706 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.4 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260431/+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 1607355] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1607355 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/1607355 Title: Task (usually mongod) blocked more 120 seconds (lock-ups) in juju on lxc/lxd + zfs Status in linux package in Ubuntu: Incomplete Bug description: I was able to reproduce this 2 or 3 times last 2 days. I have the following setup: Containers for Trusty/kilo service machines: inaddy@workstation:~$ lxc-ls | grep tk tkcephmon01 RUNNING 0 - 192.168.65.52 - tkcephmon02 RUNNING 0 - 192.168.65.51 - tkcephmon03 RUNNING 0 - 192.168.65.48 - tkcinder RUNNING 0 - 192.168.65.49 - tkdash RUNNING 0 - 192.168.65.50 - tkglance RUNNING 0 - 192.168.65.53 - tkjuju RUNNING 0 - 192.168.65.15 - tkkeystone RUNNING 0 - 192.168.65.54 - tkmysql RUNNING 0 - 192.168.65.55 - tknova RUNNING 0 - 192.168.65.56 - tkrabbit RUNNING 0 - 192.168.65.57 - tkswiftproxy RUNNING 0 - 192.168.65.58 - And compute nodes + neutrongw as kvm guests: inaddy@workstation:~$ virsh list --all | grep tk 21tkcompute01running 22tkcompute02running 23tkcompute03running 24tkneutrongwrunning All my LXC containers are on top of ZFS: Linux workstation 4.4.0-32-generic #51-Ubuntu SMP Tue Jul 19 18:09:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux And my KVM guests are on top of ext4 + 1.2 raid0 stripped volume. I'm getting the lockups bellow (usually for mongod, from tkjuju container, the juju controller). After the first lockup appears (schedule timeout coming from zfs sync logic most likely), JuJu controller starts giving me errors on "update-status". From "juju status": glance/0error idle1.25.6 10 9292/tcp tkglance hook failed: "update-status" keystone/0 error idle1.25.6 11 tkkeystone hook failed: "update-status" mysql/0 error idle1.25.6 12 tkmysqlhook failed: "config-changed" neutron-api/0 error idle1.25.6 4 9696/tcp tkneutrongwhook failed: "update-status" nova-compute/0 error idle1.25.6 1 tkcompute01hook failed: "update-status" nova-compute/1 error idle1.25.6 2 tkcompute02hook failed: "update-status" nova-compute/2 error idle1.25.6 3 tkcompute03hook failed: "update-status" Lockups: [105601.816578] INFO: task mongod:14480 blocked for more than 120 seconds. [105601.816583] Tainted: P O4.4.0-32-generic #51-Ubuntu [105601.816584] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [105601.816586] mongod D 88010ec47ba8 0 14480 16855 0x0100 [105601.816590] 88010ec47ba8 57992eeb 880108e5ee00 880108e58dc0 [105601.816592] 88010ec48000 88081ecd6d00 7fff 8182a600 [105601.816594] 88010ec47d08 88010ec47bc0 81829e05 [105601.816596] Call Trace: [105601.816603] [] ? bit_wait+0x60/0x60 [105601.816606] [] schedule+0x35/0x80 [105601.816608] [] schedule_timeout+0x1b5/0x270 [105601.816612] [] ? find_get_pages_tag+0x109/0x190 [105601.816614] [] ? bit_wait+0x60/0x60 [105601.816616] [] io_schedule_timeout+0xa4/0x110 [105601.816618] [] bit_wait_io+0x1b/0x70 [105601.816620] [] __wait_on_bit+0x5d/0x90 [105601.816622] [] wait_on_page_bit+0xcb/0xf0 [105601.816625] [] ? autoremove_wake_function+0x40/0x40 [105601.816628] [] __filemap_fdatawait_range+0xf3/0x160 [105601.816630] [] filemap_fdatawait_range+0x14/0x30 [105601.816632] [] filemap_write_and_wait_range+0x3f/0x70 [105601.816682] [] zpl_fsync+0x38/0x90 [zfs] [105601.816685] [] vfs_fsync_range+0x4b/0xb0 [105601.816687] [] SyS_msync+0x17e/0x1f0 [105601.816689] [] entry_SYSCAL
[Kernel-packages] [Bug 1607356] Re: package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1607356 Title: package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 Status in dkms package in Ubuntu: New Bug description: ... someone replaced my init-functions with an HTML file :-o Waht an a..hole ! ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.14 Architecture: amd64 Date: Thu Jul 28 13:39:52 2016 DuplicateSignature: package:linux-image-3.5.0-54-generic:3.5.0-54.81~precise1:run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2) MarkForUpload: True SourcePackage: dkms Title: package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1607356/+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 1584528] Re: Inspiron 3543 TouchPad cursor jumps to left edge unexpectedly
Using my simpler testing I found that the problem first started occurring in 15.10 I also noticed this is also when the "Disable while typing" option was removed. I hope this helps, I will be able to test any new upstream releases pretty quickly (Now that I have done it once :) ) ** Tags removed: vivid -- 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/1584528 Title: Inspiron 3543 TouchPad cursor jumps to left edge unexpectedly Status in linux package in Ubuntu: Incomplete Bug description: At times (mostly undetermined) when touching the glide pad to take an action the cursor will jump to the left edge of the screen. I do not recall the system ever taking ACTION based on the click at the new location. ex: side bar opening, etc It may not ever take the action at the ORIGINAL location, I can't be sure since I am only alerted when things don't happen as I expect. If I am using the keyboard to type or scroll (arrows) I have not noticed anything strange. I am not sure if it only happens when attempting a Left click or a Right Click. As a developer I think it is seeing my Click and reading the position incorrectly or hitting some other error condition. I do believe it is a result of my click. Tom ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tom2103 F pulseaudio /dev/snd/controlC0: tom2103 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 16:30:13 2016 HibernationDevice: RESUME=UUID=ebc3eae4-8f8a-49c6-9d22-a59e4bdf0ec5 InstallationDate: Installed on 2015-07-17 (310 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3543 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=5b06297b-c923-468b-bc52-d2dfa945174c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-03 (19 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 01Y5DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn01Y5DY:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584528/+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 1607355] [NEW] Task (usually mongod) blocked more 120 seconds (lock-ups) in juju on lxc/lxd + zfs
Public bug reported: I was able to reproduce this 2 or 3 times last 2 days. I have the following setup: Containers for Trusty/kilo service machines: inaddy@workstation:~$ lxc-ls | grep tk tkcephmon01 RUNNING 0 - 192.168.65.52 - tkcephmon02 RUNNING 0 - 192.168.65.51 - tkcephmon03 RUNNING 0 - 192.168.65.48 - tkcinder RUNNING 0 - 192.168.65.49 - tkdash RUNNING 0 - 192.168.65.50 - tkglance RUNNING 0 - 192.168.65.53 - tkjuju RUNNING 0 - 192.168.65.15 - tkkeystone RUNNING 0 - 192.168.65.54 - tkmysql RUNNING 0 - 192.168.65.55 - tknova RUNNING 0 - 192.168.65.56 - tkrabbit RUNNING 0 - 192.168.65.57 - tkswiftproxy RUNNING 0 - 192.168.65.58 - And compute nodes + neutrongw as kvm guests: inaddy@workstation:~$ virsh list --all | grep tk 21tkcompute01running 22tkcompute02running 23tkcompute03running 24tkneutrongwrunning All my LXC containers are on top of ZFS: Linux workstation 4.4.0-32-generic #51-Ubuntu SMP Tue Jul 19 18:09:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux And my KVM guests are on top of ext4 + 1.2 raid0 stripped volume. I'm getting the lockups bellow (usually for mongod, from tkjuju container, the juju controller). After the first lockup appears (schedule timeout coming from zfs sync logic most likely), JuJu controller starts giving me errors on "update-status". From "juju status": glance/0error idle1.25.6 10 9292/tcp tkglance hook failed: "update-status" keystone/0 error idle1.25.6 11 tkkeystone hook failed: "update-status" mysql/0 error idle1.25.6 12 tkmysqlhook failed: "config-changed" neutron-api/0 error idle1.25.6 4 9696/tcp tkneutrongwhook failed: "update-status" nova-compute/0 error idle1.25.6 1 tkcompute01hook failed: "update-status" nova-compute/1 error idle1.25.6 2 tkcompute02hook failed: "update-status" nova-compute/2 error idle1.25.6 3 tkcompute03hook failed: "update-status" Lockups: [105601.816578] INFO: task mongod:14480 blocked for more than 120 seconds. [105601.816583] Tainted: P O4.4.0-32-generic #51-Ubuntu [105601.816584] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [105601.816586] mongod D 88010ec47ba8 0 14480 16855 0x0100 [105601.816590] 88010ec47ba8 57992eeb 880108e5ee00 880108e58dc0 [105601.816592] 88010ec48000 88081ecd6d00 7fff 8182a600 [105601.816594] 88010ec47d08 88010ec47bc0 81829e05 [105601.816596] Call Trace: [105601.816603] [] ? bit_wait+0x60/0x60 [105601.816606] [] schedule+0x35/0x80 [105601.816608] [] schedule_timeout+0x1b5/0x270 [105601.816612] [] ? find_get_pages_tag+0x109/0x190 [105601.816614] [] ? bit_wait+0x60/0x60 [105601.816616] [] io_schedule_timeout+0xa4/0x110 [105601.816618] [] bit_wait_io+0x1b/0x70 [105601.816620] [] __wait_on_bit+0x5d/0x90 [105601.816622] [] wait_on_page_bit+0xcb/0xf0 [105601.816625] [] ? autoremove_wake_function+0x40/0x40 [105601.816628] [] __filemap_fdatawait_range+0xf3/0x160 [105601.816630] [] filemap_fdatawait_range+0x14/0x30 [105601.816632] [] filemap_write_and_wait_range+0x3f/0x70 [105601.816682] [] zpl_fsync+0x38/0x90 [zfs] [105601.816685] [] vfs_fsync_range+0x4b/0xb0 [105601.816687] [] SyS_msync+0x17e/0x1f0 [105601.816689] [] entry_SYSCALL_64_fastpath+0x16/0x71 [117121.961545] INFO: task txg_sync:4589 blocked for more than 120 seconds. [117121.961549] Tainted: P O4.4.0-32-generic #51-Ubuntu [117121.961550] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [117121.961551] txg_syncD 8807e1fbbaa8 0 4589 2 0x [117121.961558] 8807e1fbbaa8 88081ed96d00 8807faf03700 8807e2dbb700 [117121.961560] 8807e1fbc000 88081ed16d00 7fff 88017a8f2208 [117121.961561] 0001 8807e1fbbac0 81829e05 [117121.961563] Call Trace: [117121.961569] [] schedule+0x35/0x80 [117121.961571] [] schedule_timeout+0x1b5/0x270 [117121.961574] [] ? default_wake_function+0x12/0x20 [117121.961576] [] ? __wake_up_common+0x52/0x90 [117121.961578] [] io_schedule_timeout+0xa4/0x110 [117121.961586] [] cv_wait_common+0xbc/0x140 [spl] [117121.961589] []
[Kernel-packages] [Bug 1607356] [NEW] package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2
Public bug reported: ... someone replaced my init-functions with an HTML file :-o Waht an a..hole ! ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.14 Architecture: amd64 Date: Thu Jul 28 13:39:52 2016 DuplicateSignature: package:linux-image-3.5.0-54-generic:3.5.0-54.81~precise1:run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2) MarkForUpload: True SourcePackage: dkms Title: package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1607356 Title: package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 Status in dkms package in Ubuntu: New Bug description: ... someone replaced my init-functions with an HTML file :-o Waht an a..hole ! ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.14 Architecture: amd64 Date: Thu Jul 28 13:39:52 2016 DuplicateSignature: package:linux-image-3.5.0-54-generic:3.5.0-54.81~precise1:run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2) MarkForUpload: True SourcePackage: dkms Title: package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1607356/+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 1260431] Re: update-grub hangs under 3.11.0-3-generic
blkid gives me /dev/vda1: LABEL="cloudimg-rootfs" UUID="1ff353c2-3fed- 48fb-acc0-6d18086d030b" TYPE="ext4" After blacklisting btrfs and restarting it gives me the message "[1] 1360 segmentation fault modprobe btrfs" after running "modprobe btrfs". But it does not hang anymore. -- 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/1260431 Title: update-grub hangs under 3.11.0-3-generic Status in linux package in Ubuntu: Triaged Bug description: I have a saucy/amd64 instance that was booted using the 20130822 image (checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on 2013-08-29, which I finally updated today. During the upgrade, modprobe btrfs hung in init_module(). If I kill modprobe, the upgrade finishes. The apport gathering is on the new kernel, since apport declined to file a bug with the 3.11.0-3-generic kernel running. filing here for historical purposes, I expect. The problem does not reproduce on a current machine running 3.11.0-14-generic. lamont ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 12 17:45 seq crw-rw 1 root audio 116, 33 Dec 12 17:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 10.105412] init: plymouth-stop pre-start process (1008) terminated with status 1 Date: Thu Dec 12 17:45:40 2013 Ec2AMI: ami-0005 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=25707b7a-3d31-4823-831f-ed5306116706 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.4 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260431/+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 1607349] [NEW] package linux-firmware 1.157 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/liquidio/lio_410nv_nic.bin« können nicht nach »/lib/firmware/liquidi
Public bug reported: got this error by making a "sudo apt-get update && sudo apt-get dist- upgrade" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jul 28 14:14:04 2016 Dependencies: ErrorMessage: Extrahierte Daten für »./lib/firmware/liquidio/lio_410nv_nic.bin« können nicht nach »/lib/firmware/liquidio/lio_410nv_nic.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms InstallationDate: Installed on 2016-05-20 (68 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: linux-firmware Title: package linux-firmware 1.157 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/liquidio/lio_410nv_nic.bin« können nicht nach »/lib/firmware/liquidio/lio_410nv_nic.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1607349 Title: package linux-firmware 1.157 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/liquidio/lio_410nv_nic.bin« können nicht nach »/lib/firmware/liquidio/lio_410nv_nic.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms Status in linux-firmware package in Ubuntu: New Bug description: got this error by making a "sudo apt-get update && sudo apt-get dist- upgrade" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jul 28 14:14:04 2016 Dependencies: ErrorMessage: Extrahierte Daten für »./lib/firmware/liquidio/lio_410nv_nic.bin« können nicht nach »/lib/firmware/liquidio/lio_410nv_nic.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms InstallationDate: Installed on 2016-05-20 (68 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: linux-firmware Title: package linux-firmware 1.157 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/liquidio/lio_410nv_nic.bin« können nicht nach »/lib/firmware/liquidio/lio_410nv_nic.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1607349/+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 1607325] Re: Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin16041 -- 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/1607325 Title: Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge Status in linux package in Ubuntu: New Bug description: Problem Description === system Z Ubuntu 16.04 LTS can not correctly configured DS8870 2107 LUNs. ---uname output--- Linux ilabg3 4.4.0-33-generic #52-Ubuntu SMP Fri Jul 22 19:17:00 UTC 2016 s390x s390x s390x GNU/Linux ---Additional Hardware Info--- Z13 system using 16G FCP adapters to attach to FC fabric and IBM Blue ridge Machine Type = Z13 S390 Steps to Reproduce The initial kernel is 4.4.0-24-generic and all blue ridge devices can be configured normally. After we upgrade kernel to 4.4.0-33 and reload BR code all BR devices can not be detect. System log show: [ 2645.893763] scsi 0:0:7:0: RAID IBM 2810XIV-LUN-0 PQ: 0 ANSI: 5 [ 2645.895269] sysfs: cannot create duplicate filename '/bus/scsi/devices/0:0:7:0' [ 2645.895310] [ cut here ] [ 2645.895311] WARNING: at /build/linux-o03cxz/linux-4.4.0/fs/sysfs/dir.c:31 [ 2645.895312] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth ccwgroup vmur ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core sunrpc ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi btrfs zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common zfcp dasd_eckd_mod qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 2645.895338] CPU: 1 PID: 4008 Comm: sh Tainted: GW 4.4.0-33-generic #52-Ubuntu [ 2645.895339] task: dfe436b0 ti: 7b97c000 task.ti: 7b97c000 [ 2645.895340] Krnl PSW : 0704d0018000 003a361c (sysfs_warn_dup+0x7c/0x98) [ 2645.895350]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 EA:3 Krnl GPRS: 00cf7039 00cd9f3c 0043 ef4d18a0 [ 2645.895351]003a3618 7a49a000 707b9178 [ 2645.895352]00c1d0e0 ee71a780 0001 ee71a780 [ 2645.895353]e9554b60 7ebdf000 003a3618 7b97f9b8 [ 2645.895361] Krnl Code: 003a360c: c020002f33e7 larl %r2,989dda 003a3612: c0e5fff6befb brasl %r14,27b408 #003a3618: a7f40001 brc 15,3a361a >003a361c: b904002d lgr %r2,%r13 003a3620: ebbff0a4 lmg %r11,%r15,160(%r15) 003a3626: c0f4fffa5995 brcl 15,2ee950 003a362c: a739 lghi%r3,0 003a3630: a7f4ffec brc 15,3a3608 [ 2645.895370] Call Trace: [ 2645.895372] ([<003a3618>] sysfs_warn_dup+0x78/0x98) [ 2645.895374] [<003a3b30>] sysfs_do_create_link_sd.isra.0+0xf8/0x108 [ 2645.895378] [<005c4044>] bus_add_device+0x13c/0x230 [ 2645.895379] [<005c1758>] device_add+0x398/0x680 [ 2645.895385] [<005f7a34>] scsi_sysfs_add_sdev+0xcc/0x2a8 [ 2645.895386] [<005f4210>] scsi_probe_and_add_lun+0xcc0/0xe18 [ 2645.895387] [<005f4c5a>] __scsi_scan_target+0xba/0x268 [ 2645.895389] [<005f4f0a>] scsi_scan_target+0x102/0x120 [ 2645.895401] [<03ff801095f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp] [ 2645.895404] [<03ff80109948>] zfcp_unit_add+0x168/0x1f0 [zfcp] [ 2645.895407] [<03ff80108564>] zfcp_sysfs_unit_add_store+0x54/0x70 [zfcp] [ 2645.895408] [<003a1d9a>] kernfs_fop_write+0x13a/0x190 [ 2645.895413] [<0030fcac>] vfs_write+0x94/0x1a0 [ 2645.895414] [<003109be>] SyS_write+0x66/0xd8 [ 2645.895417] [<007b86c6>] system_call+0xd6/0x264 [ 2645.895418] [<03ffb10df6e8>] 0x3ffb10df6e8 [ 2645.895419] Last Breaking-Event-Address: [ 2645.895420] [<003a3618>] sysfs_warn_dup+0x78/0x98 [ 2645.895421] ---[ end trace a9b757385c995a64 ]--- [ 2645.895535] scsi 0:0:7:0: failed to add device: -17 == Comment: #1 - XIANG ZHANG - 2016-07-26 02:34:39 == I know the Bug 139096, not sure the same symptom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607325/+subscriptions -- Mailing list: https://launchpad.net/~ke
[Kernel-packages] [Bug 1260431] Re: update-grub hangs under 3.11.0-3-generic
Thanks Foppe. A few questions: Does blacklisting the btrfs module work around the problem? What does the output of `blkid` return for this machine? -- 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/1260431 Title: update-grub hangs under 3.11.0-3-generic Status in linux package in Ubuntu: Triaged Bug description: I have a saucy/amd64 instance that was booted using the 20130822 image (checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on 2013-08-29, which I finally updated today. During the upgrade, modprobe btrfs hung in init_module(). If I kill modprobe, the upgrade finishes. The apport gathering is on the new kernel, since apport declined to file a bug with the 3.11.0-3-generic kernel running. filing here for historical purposes, I expect. The problem does not reproduce on a current machine running 3.11.0-14-generic. lamont ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 12 17:45 seq crw-rw 1 root audio 116, 33 Dec 12 17:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 10.105412] init: plymouth-stop pre-start process (1008) terminated with status 1 Date: Thu Dec 12 17:45:40 2013 Ec2AMI: ami-0005 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=25707b7a-3d31-4823-831f-ed5306116706 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.4 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260431/+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 1607325] dmesg output
Default Comment by Bridge ** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/1607325/+attachment/4708674/+files/system_log.txt ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** 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/1607325 Title: Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge Status in linux package in Ubuntu: New Bug description: Problem Description === system Z Ubuntu 16.04 LTS can not correctly configured DS8870 2107 LUNs. ---uname output--- Linux ilabg3 4.4.0-33-generic #52-Ubuntu SMP Fri Jul 22 19:17:00 UTC 2016 s390x s390x s390x GNU/Linux ---Additional Hardware Info--- Z13 system using 16G FCP adapters to attach to FC fabric and IBM Blue ridge Machine Type = Z13 S390 Steps to Reproduce The initial kernel is 4.4.0-24-generic and all blue ridge devices can be configured normally. After we upgrade kernel to 4.4.0-33 and reload BR code all BR devices can not be detect. System log show: [ 2645.893763] scsi 0:0:7:0: RAID IBM 2810XIV-LUN-0 PQ: 0 ANSI: 5 [ 2645.895269] sysfs: cannot create duplicate filename '/bus/scsi/devices/0:0:7:0' [ 2645.895310] [ cut here ] [ 2645.895311] WARNING: at /build/linux-o03cxz/linux-4.4.0/fs/sysfs/dir.c:31 [ 2645.895312] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth ccwgroup vmur ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core sunrpc ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi btrfs zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common zfcp dasd_eckd_mod qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 2645.895338] CPU: 1 PID: 4008 Comm: sh Tainted: GW 4.4.0-33-generic #52-Ubuntu [ 2645.895339] task: dfe436b0 ti: 7b97c000 task.ti: 7b97c000 [ 2645.895340] Krnl PSW : 0704d0018000 003a361c (sysfs_warn_dup+0x7c/0x98) [ 2645.895350]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 EA:3 Krnl GPRS: 00cf7039 00cd9f3c 0043 ef4d18a0 [ 2645.895351]003a3618 7a49a000 707b9178 [ 2645.895352]00c1d0e0 ee71a780 0001 ee71a780 [ 2645.895353]e9554b60 7ebdf000 003a3618 7b97f9b8 [ 2645.895361] Krnl Code: 003a360c: c020002f33e7 larl %r2,989dda 003a3612: c0e5fff6befb brasl %r14,27b408 #003a3618: a7f40001 brc 15,3a361a >003a361c: b904002d lgr %r2,%r13 003a3620: ebbff0a4 lmg %r11,%r15,160(%r15) 003a3626: c0f4fffa5995 brcl 15,2ee950 003a362c: a739 lghi%r3,0 003a3630: a7f4ffec brc 15,3a3608 [ 2645.895370] Call Trace: [ 2645.895372] ([<003a3618>] sysfs_warn_dup+0x78/0x98) [ 2645.895374] [<003a3b30>] sysfs_do_create_link_sd.isra.0+0xf8/0x108 [ 2645.895378] [<005c4044>] bus_add_device+0x13c/0x230 [ 2645.895379] [<005c1758>] device_add+0x398/0x680 [ 2645.895385] [<005f7a34>] scsi_sysfs_add_sdev+0xcc/0x2a8 [ 2645.895386] [<005f4210>] scsi_probe_and_add_lun+0xcc0/0xe18 [ 2645.895387] [<005f4c5a>] __scsi_scan_target+0xba/0x268 [ 2645.895389] [<005f4f0a>] scsi_scan_target+0x102/0x120 [ 2645.895401] [<03ff801095f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp] [ 2645.895404] [<03ff80109948>] zfcp_unit_add+0x168/0x1f0 [zfcp] [ 2645.895407] [<03ff80108564>] zfcp_sysfs_unit_add_store+0x54/0x70 [zfcp] [ 2645.895408] [<003a1d9a>] kernfs_fop_write+0x13a/0x190 [ 2645.895413] [<0030fcac>] vfs_write+0x94/0x1a0 [ 2645.895414] [<003109be>] SyS_write+0x66/0xd8 [ 2645.895417] [<007b86c6>] system_call+0xd6/0x264 [ 2645.895418] [<03ffb10df6e8>] 0x3ffb10df6e8 [ 2645.895419] Last Breaking-Event-Address: [ 2645.895420] [<003a3618>] sysfs_warn_dup+0x78/0x98 [ 2645.895421] ---[ end trace a9b757385c995a64 ]--- [ 2645.895535] scsi 0:0:7:0: failed to add device: -17 == Comment: #1 - XIANG ZHANG - 2016-07-26 02:34:39 == I kno
[Kernel-packages] [Bug 1510570] Re: BLE pairing fail
Hi guys. I am happy about finding this page. I had the same issue with my new Dell Bluetooth Mouse WM615 but after using your suggestions, it's working well now. What I did are - editing /etc/bluetooth/main.conf as it is said in #25 - editing /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules as it is said in #27. Thanks Robert, I can assure you, it works. At least for me. I'm on Ubuntu 16.04 LTS and Dell Inspiron 15 7000. Cheers guys! -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1607325] [NEW] Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge
You have been subscribed to a public bug: Problem Description === system Z Ubuntu 16.04 LTS can not correctly configured DS8870 2107 LUNs. ---uname output--- Linux ilabg3 4.4.0-33-generic #52-Ubuntu SMP Fri Jul 22 19:17:00 UTC 2016 s390x s390x s390x GNU/Linux ---Additional Hardware Info--- Z13 system using 16G FCP adapters to attach to FC fabric and IBM Blue ridge Machine Type = Z13 S390 Steps to Reproduce The initial kernel is 4.4.0-24-generic and all blue ridge devices can be configured normally. After we upgrade kernel to 4.4.0-33 and reload BR code all BR devices can not be detect. System log show: [ 2645.893763] scsi 0:0:7:0: RAID IBM 2810XIV-LUN-0 PQ: 0 ANSI: 5 [ 2645.895269] sysfs: cannot create duplicate filename '/bus/scsi/devices/0:0:7:0' [ 2645.895310] [ cut here ] [ 2645.895311] WARNING: at /build/linux-o03cxz/linux-4.4.0/fs/sysfs/dir.c:31 [ 2645.895312] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth ccwgroup vmur ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core sunrpc ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi btrfs zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common zfcp dasd_eckd_mod qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 2645.895338] CPU: 1 PID: 4008 Comm: sh Tainted: GW 4.4.0-33-generic #52-Ubuntu [ 2645.895339] task: dfe436b0 ti: 7b97c000 task.ti: 7b97c000 [ 2645.895340] Krnl PSW : 0704d0018000 003a361c (sysfs_warn_dup+0x7c/0x98) [ 2645.895350]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 EA:3 Krnl GPRS: 00cf7039 00cd9f3c 0043 ef4d18a0 [ 2645.895351]003a3618 7a49a000 707b9178 [ 2645.895352]00c1d0e0 ee71a780 0001 ee71a780 [ 2645.895353]e9554b60 7ebdf000 003a3618 7b97f9b8 [ 2645.895361] Krnl Code: 003a360c: c020002f33e7larl %r2,989dda 003a3612: c0e5fff6befbbrasl %r14,27b408 #003a3618: a7f40001brc 15,3a361a >003a361c: b904002dlgr %r2,%r13 003a3620: ebbff0a4lmg %r11,%r15,160(%r15) 003a3626: c0f4fffa5995brcl 15,2ee950 003a362c: a739lghi%r3,0 003a3630: a7f4ffecbrc 15,3a3608 [ 2645.895370] Call Trace: [ 2645.895372] ([<003a3618>] sysfs_warn_dup+0x78/0x98) [ 2645.895374] [<003a3b30>] sysfs_do_create_link_sd.isra.0+0xf8/0x108 [ 2645.895378] [<005c4044>] bus_add_device+0x13c/0x230 [ 2645.895379] [<005c1758>] device_add+0x398/0x680 [ 2645.895385] [<005f7a34>] scsi_sysfs_add_sdev+0xcc/0x2a8 [ 2645.895386] [<005f4210>] scsi_probe_and_add_lun+0xcc0/0xe18 [ 2645.895387] [<005f4c5a>] __scsi_scan_target+0xba/0x268 [ 2645.895389] [<005f4f0a>] scsi_scan_target+0x102/0x120 [ 2645.895401] [<03ff801095f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp] [ 2645.895404] [<03ff80109948>] zfcp_unit_add+0x168/0x1f0 [zfcp] [ 2645.895407] [<03ff80108564>] zfcp_sysfs_unit_add_store+0x54/0x70 [zfcp] [ 2645.895408] [<003a1d9a>] kernfs_fop_write+0x13a/0x190 [ 2645.895413] [<0030fcac>] vfs_write+0x94/0x1a0 [ 2645.895414] [<003109be>] SyS_write+0x66/0xd8 [ 2645.895417] [<007b86c6>] system_call+0xd6/0x264 [ 2645.895418] [<03ffb10df6e8>] 0x3ffb10df6e8 [ 2645.895419] Last Breaking-Event-Address: [ 2645.895420] [<003a3618>] sysfs_warn_dup+0x78/0x98 [ 2645.895421] ---[ end trace a9b757385c995a64 ]--- [ 2645.895535] scsi 0:0:7:0: failed to add device: -17 == Comment: #1 - XIANG ZHANG - 2016-07-26 02:34:39 == I know the Bug 139096, not sure the same symptom ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-144139 severity-medium targetmilestone-inin--- -- Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge https://bugs.launchpad.net/bugs/1607325 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-pa
Re: [Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hey, the procedure is not very difficult and once all the tools are installed it is straightforward however if you do not feel confident, given that it is not certain that it will help for issues with cars, I would recommend waiting till OTA-13. Best, Konrad On Thu, Jul 28, 2016 at 1:05 PM, Marco Graziotti wrote: > Hi Konrad, > > thank you for your answer, I will try to apply the procedure that you have > described during this weekend. > I never installed a silos, so maybe it's better to wait the OTA-13 that > incude bluez 5.41. > > Thank you, > Marco > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > >> Hey, >> >> I'll try to help a bit here. >> >> First as for the unknown or unwanted entries on the paired devices lists >> [and such] you can try to remove them from the bluetoothctl level. >> >> ) enable developers mode & connect it via usb cable >> ) login with adb shell to the deivce >> ) type $ bluetoothctl >> ) then type: devices - to list the known devices >> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of >> the device [not it's name] >> >> Second we are in the of releasing the newest bluez 5.41 which is now in >> silo 37. If you are familiar with installing silos on your device you >> can try it out and check if it improves anything. It includes fixes for >> link management and pairing therefore there is a chance [although not >> certain] that there might be joy. >> >> If unsure please ask. >> >> Best, >> Konrad >> >> > -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, thank you for your answer, I will try to apply the procedure that you have described during this weekend. I never installed a silos, so maybe it's better to wait the OTA-13 that incude bluez 5.41. Thank you, Marco Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1548009] Re: ZFS pools should be automatically scrubbed
** Also affects: zfs-linux (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1548009 Title: ZFS pools should be automatically scrubbed Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: New Bug description: [Impact] Xenial shipped with a cron job to automatically scrub ZFS pools, as desired by many users and as implemented by mdadm for traditional Linux software RAID. Unfortunately, this cron job does not work, because it needs a PATH line for /sbin, where the zpool utility lives. Given the existence of the cron job and various discussions on IRC, etc., users expect that scrubs are happening, when they are not. This means ZFS is not pre-emptively checking for (and correcting) corruption. The odds of disk corruption are admittedly very low, but violating users' expectations of data safety, especially when they've gone out of their way to use a filesystem which touts data safety, is bad. [Test Case] $ truncate -s 1G test.img $ sudo zpool create test `pwd`/test.img $ sudo zpool status test $ sudo vi /etc/cron.d/zfsutils-linux Modify /etc/cron.d/zfsutils-linux to run the cron job in a few minutes (modifying the date range if it's not currently the 8th through the 14th and the "-eq 0" check if it's not currently a Sunday). $ grep zfs /var/log/cron.log Verify in /var/log/cron.log that the job ran. $ sudo zpool status test Expected results: scan: scrub repaired 0 in ... on Actual results: scan: none requested Then, add the PATH line, update the time rules in the cron job, and repeat the test. Now it will work. - OR - The best test case is to leave the cron job file untouched, install the patched package, wait for the second Sunday of the month, and verify with zpool status that a scrub ran. I did this, on Xenial, with the package I built. The debdiff is in comment #11 and was accepted to Yakkety. If someone can get this in -proposed before the 14th, I'll gladly install the actual package from -proposed and make sure it runs correctly on the 14th. [Regression Potential] The patch only touches the cron.d file, which has only one cron job in it. This cron job is completely broken (inoperative) at the moment, so the regression potential is very low. ORIGINAL, PRE-SRU, DESCRIPTION: mdadm automatically checks MD arrays. ZFS should automatically scrub pools too. Scrubbing a pool allows ZFS to detect on-disk corruption and (when the pool has redundancy) correct it. Note that ZFS does not blindly assume the other copy is correct; it will only overwrite bad data with data that is known to be good (i.e. it passes the checksum). I've attached a debdiff which accomplishes this. It builds and installs cleanly. The meat of it is the scrub script I've been using on production systems, both servers and laptops, and recommending in my Ubuntu root- on-ZFS HOWTO, for years, which scrubs all *healthy* pools. If a pool is not healthy, scrubbing it is bad for two reasons: 1) It adds a lot of disk load which could theoretically lead to another failure. We should save that disk load for resilvering. 2) Performance is already less on a degraded pool and scrubbing can make that worse, even though scrubs are throttled. Arguably, I might be being too conservative here, but the marginal benefit of scrubbing a *degraded* pool is pretty minimal as pools should not be left degraded for very long. The cron.d in this patch scrubs on the second Sunday of the month. mdadm scrubs on the first Sunday of the month. This way, if a system has both MD and ZFS pools, the load doesn't all happen at the same time. If the system doesn't have both types, it shouldn't really matter which week. If you'd rather make it the same week as MD, I see no problem with that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1548009/+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 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
Hi, I have installed these packages, but I still observer this issue: kamil@host:~$ sudo lspci | grep Volatile [sudo] password for kamil: 03:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 04:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 05:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 06:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 07:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 08:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) kamil@host:~$ ls /dev/ | grep nvme nvme0 nvme0n1 nvme1 nvme1n1 nvme2 nvme2n1 nvme3 nvme3n1 nvme4 nvme5 nvme5n1 kamil@host:~$ [ 69.542046] nvme :07:00.0: Identify Controller failed (-4) kamil@host:~$ sudo lspci | grep Volatile 03:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 04:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 05:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 06:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) 08:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) kamil@host:~$ ls /dev/ | grep nvme nvme0 nvme0n1 nvme1 nvme1n1 nvme2 nvme2n1 nvme3 nvme3n1 nvme5 nvme5n1 kamil@host:~$ uname -a Linux host 4.4.0-28-generic #47~lp1597908 SMP Thu Jun 30 22:46:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Dmesg output: [2.648607] pci :07:00.0: [8086:0953] type 00 class 0x010802 [2.649074] pci :07:00.0: reg 0x10: [mem 0xc6a1-0xc6a13fff 64bit] [2.649668] pci :07:00.0: reg 0x30: [mem 0xc6a0-0xc6a0 pref] [5.211815] pci_bus :07: resource 1 [mem 0xc6a0-0xc6af] [6.365162] pci :07:00.0: Signaling PME through PCIe PME interrupt ... [ 69.437927] nvme :07:00.0: I/O 0 QID 0 timeout, disable controller [ 69.542017] nvme :07:00.0: Cancelling I/O 0 QID 0 [ 69.542046] nvme :07:00.0: Identify Controller failed (-4) [ 69.553756] nvme :07:00.0: Removing after probe failure Kamil, -- 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/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
Hi again, Still same problem, wakeup from hibernation freezes at some time, with latest kernel (4.4.0-31), that is to say the system becomes totally unresponsive, the screen may go black or not. It seems that the system is not always able to write something in logs when this occurs : in /var/log/kern.log there is sometimes nothing, sometimes a general protection fault, sometimes one line with only @ symbols (??). In the meantime, suspend to ram is absolutely stable. Nevertheless, I noticed that if I switch ON the nvidia card (*) just before hibernating, freezes seem to occur less often. Again, if anyone has some hints about how to debug. Regards (*) The T440s has got two graphic cards, integrated intel and nvidia G730M, the nvidia card is switched OFF by default at boot with bbswitch module, I can switch it ON with "echo ON > /proc/acpi/bbswitch" -- 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/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Won't Fix Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+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 1260431] Re: update-grub hangs under 3.11.0-3-generic
This also affects our environment running on Ubuntu 14.04 / 3.13.0-65-generic. During an unattended upgrade os-prober scans all filesystems. After this the upgrade hangs on modprobe btrfs, resulting in a stalled upgrade. Because of this automatic security updates/upgrades will not take place. -- 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/1260431 Title: update-grub hangs under 3.11.0-3-generic Status in linux package in Ubuntu: Triaged Bug description: I have a saucy/amd64 instance that was booted using the 20130822 image (checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on 2013-08-29, which I finally updated today. During the upgrade, modprobe btrfs hung in init_module(). If I kill modprobe, the upgrade finishes. The apport gathering is on the new kernel, since apport declined to file a bug with the 3.11.0-3-generic kernel running. filing here for historical purposes, I expect. The problem does not reproduce on a current machine running 3.11.0-14-generic. lamont ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 12 17:45 seq crw-rw 1 root audio 116, 33 Dec 12 17:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 10.105412] init: plymouth-stop pre-start process (1008) terminated with status 1 Date: Thu Dec 12 17:45:40 2013 Ec2AMI: ami-0005 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=25707b7a-3d31-4823-831f-ed5306116706 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.4 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260431/+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 1606960] Re: linux: 4.4.0-34.53 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed 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/1606960 Title: linux: 4.4.0-34.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-34.53 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 -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1606960/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hey, I'll try to help a bit here. First as for the unknown or unwanted entries on the paired devices lists [and such] you can try to remove them from the bluetoothctl level. ) enable developers mode & connect it via usb cable ) login with adb shell to the deivce ) type $ bluetoothctl ) then type: devices - to list the known devices ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the device [not it's name] Second we are in the of releasing the newest bluez 5.41 which is now in silo 37. If you are familiar with installing silos on your device you can try it out and check if it improves anything. It includes fixes for link management and pairing therefore there is a chance [although not certain] that there might be joy. If unsure please ask. Best, Konrad -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1605974] Re: usbduxsigma_firmware.bin: old version causes driver crash
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/log/usbduxsigma_firmware.bin -- 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/1605974 Title: usbduxsigma_firmware.bin: old version causes driver crash Status in linux-firmware package in Ubuntu: New Bug description: The firmware of the usbduxsigma (alongside with the usbduxsigma.c) was updated in 2015 during a major rewrite but its binary was still the old one which causes the kernel driver to fail. I've submitted a patch to the kernel people (see below). However, as a quick fix could you also apply the patch to the package directly to have this fixed now and then we can wait until it trickles down from the kernel. I'm the maintainer of both the firmware and the drivers. This affects both 32 and 64 bit distros. Best, /Bernd Porr (www.linux-usb-daq.co.uk) Description: Ubuntu 16.04.1 LTS Release: 16.04 linux-firmware: Installed: 1.157.2 Candidate: 1.157.2 Version table: *** 1.157.2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 1.157 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages Expect to happen: plug in a duxduxsigma device, start comedirecord and see the signals plotted Happens instead: plug in a duxduxsigma device, start comedirecord and GARBLED DATA shows up / crash Fix: install this patch (new version of the firmware binary) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.2 [modified: lib/firmware/usbduxsigma_firmware.bin] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 24 10:04:19 2016 Dependencies: InstallationDate: Installed on 2013-12-09 (957 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131209) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to xenial on 2016-07-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1605974/+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 1500246] Re: modemmanager fails to configure during upgrade from 15.04 to 15.10
As a non-LTS release, 15.10 has a 9-month month support cycle and, as such, the support period is now nearing its end and Ubuntu 15.10 will reach end of life on Thursday, July 28th. At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 15.10. ** Changed in: crash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1500246 Title: modemmanager fails to configure during upgrade from 15.04 to 15.10 Status in crash package in Ubuntu: Invalid Bug description: It appears that the upgrade will refuse to continue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: crash (not installed) ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 27 14:17:16 2015 InstallationDate: Installed on 2015-07-25 (64 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: crash UpgradeStatus: Upgraded to wily on 2015-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1500246/+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 1606873] Re: Logitech Precision Gamepad shows axis activity upon connection
Hi, I can't tell you whether the issue started after an update/upgrade sorry - I've only noticed it recently. I've installed the 4.7 upstream kernel and the bug is still exhibited: eddie@codey:~$ uname -a Linux codey 4.7.0-040700-generic #201607241632 SMP Sun Jul 24 20:34:30 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux eddie@codey:~$ jstest /dev/input/js0 Driver version is 2.1.0. Joystick (Logitech Logitech(R) Precision(TM) Gamepad) has 2 axes (X, Y) and 10 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4). Testing ... (interrupt to exit) Axes: 0:-32767 1:-32767 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off I've therefore tagged the issue "bug-exists-upstream" and marked it as confirmed. ** Tags added: bug-exists-upstream ** 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/1606873 Title: Logitech Precision Gamepad shows axis activity upon connection Status in linux package in Ubuntu: Confirmed Bug description: When I connect my Logitech Precision Gamepad (or the machine starts up with it connected) it exhibits activity on both axes until I press a button/press the d-pad. UPON PLUGGING USB CONNECTOR IN: === Driver version is 2.1.0. Joystick (Logitech Logitech(R) Precision(TM) Gamepad) has 2 axes (X, Y) and 10 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4). Testing ... (interrupt to exit) Axes: 0:-32767 1:-32767 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off AFTER PRESSING ANY BUTTON OR THE D-PAD: === Driver version is 2.1.0. Joystick (Logitech Logitech(R) Precision(TM) Gamepad) has 2 axes (X, Y) and 10 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off EXPECTED BEHAVIOUR: === Both axes (0 & 1) should be "at rest" (i.e. 0, not +/- 32767) when the gamepad is initially plugged in. Note - I'm not sure whether the d-pad should be classified as a pair of axes or a pair of hats - it is a digital d-pad though, *not* analog. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 27 22:15:30 2016 HibernationDevice: RESUME=UUID=da040d4b-c54b-4bd1-9ed8-8668315fe116 InstallationDate: Installed on 2015-12-27 (212 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=379bc7ae-9d87-48f4-8485-eb287feb4a3e ro quiet splash video=vesafb vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-04 (84 days ago) dmi.bios.date: 05/03/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0054.2016.0503.1546 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0054.2016.0503.1546:bd05/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606873/+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 1499701] Re: package bluez 5.34-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
As a non-LTS release, 15.10 has a 9-month month support cycle and, as such, the support period is now nearing its end and Ubuntu 15.10 will reach end of life on Thursday, July 28th. At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 15.10. ** Changed in: bluez (Ubuntu) Status: New => 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/1499701 Title: package bluez 5.34-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: Invalid Bug description: Error is reported spontaneously. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.34-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Fri Sep 25 11:13:43 2015 DuplicateSignature: package:bluez:5.34-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-30 (329 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard Compaq 615 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=5c188f95-bbdb-49b7-bb3a-be84c71897a9 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.9.10ubuntu7 SourcePackage: bluez Title: package bluez 5.34-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GVV Ver. F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 308C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 27.07 dmi.chassis.asset.tag: CNU93824ND dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GVVVer.F.06:bd08/03/2009:svnHewlett-Packard:pnCompaq615:pvrF.06:rvnHewlett-Packard:rn308C:rvrKBCVersion27.07:cvnHewlett-Packard:ct10:cvr: dmi.product.name: Compaq 615 dmi.product.version: F.06 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499701/+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 1496969] Re: package bluez (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
As a non-LTS release, 15.10 has a 9-month month support cycle and, as such, the support period is now nearing its end and Ubuntu 15.10 will reach end of life on Thursday, July 28th. At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 15.10. ** Changed in: bluez (Ubuntu) Status: New => 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/1496969 Title: package bluez (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 Status in bluez package in Ubuntu: Invalid Bug description: Bug ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez (not installed) Uname: Linux 4.2.0-040200-generic i686 ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 Date: Thu Sep 17 16:58:32 2015 DuplicateSignature: package:bluez:(not installed):il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2013-06-25 (814 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130617) RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.9.10ubuntu6 SourcePackage: bluez Title: package bluez (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1496969/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I have an E4.5 and with OTA-12 I can't pair to C4 Citroen. Time ago I did some tests. When the phone detect a car tried to match it. Now their names still appear. This is very strange. -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1491160] Re: nvidia drivers not active with my GT330M, only nouveau
As a non-LTS release, 15.10 has a 9-month month support cycle and, as such, the support period is now nearing its end and Ubuntu 15.10 will reach end of life on Thursday, July 28th. At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 15.10. ** Changed in: nvidia-settings (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1491160 Title: nvidia drivers not active with my GT330M, only nouveau Status in nvidia-settings package in Ubuntu: Invalid Bug description: Hello, whatever the nvidia version drivers I installed from the Ubuntu official depot, my Nvidia Geforce GT 330M dos not use Nvidia drivers but Nouveau. If I launch nvidia-settings the apps is empty, no information, the card is not recognized. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nvidia-settings 352.21-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 1 23:34:31 2015 InstallationDate: Installed on 2015-08-12 (19 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to wily on 2015-08-23 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1491160/+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 1607239] 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/1607239 Title: mdadm raid gets frozen Status in linux package in Ubuntu: Confirmed Bug description: Servers periodically became unresponsive, and report the following problem: Jul 28 01:26:36 osd1-05 kernel: [1644406.270794] kworker/12:2D 88085fcd3180 0 25000 2 0x Jul 28 01:26:36 osd1-05 kernel: [1644406.270813] Workqueue: dio/bdev dio_aio_complete_work Jul 28 01:26:36 osd1-05 kernel: [1644406.270821] 88003694dc10 0046 8805621b4800 00013180 Jul 28 01:26:36 osd1-05 kernel: [1644406.270830] 88003694dfd8 00013180 8805621b4800 88003694dd38 Jul 28 01:26:36 osd1-05 kernel: [1644406.270836] 88003694dd40 7fff 8805621b4800 a6fd7000 Jul 28 01:26:36 osd1-05 kernel: [1644406.270842] Call Trace: Jul 28 01:26:36 osd1-05 kernel: [1644406.270857] [] schedule+0x29/0x70 Jul 28 01:26:36 osd1-05 kernel: [1644406.270870] [] schedule_timeout+0x279/0x310 Jul 28 01:26:36 osd1-05 kernel: [1644406.270880] [] ? md_make_request+0xd5/0x220 Jul 28 01:26:36 osd1-05 kernel: [1644406.270889] [] wait_for_completion+0xa6/0x150 Jul 28 01:26:36 osd1-05 kernel: [1644406.270900] [] ? wake_up_state+0x20/0x20 Jul 28 01:26:36 osd1-05 kernel: [1644406.270906] [] submit_bio_wait+0x5e/0x70 Jul 28 01:26:36 osd1-05 kernel: [1644406.270914] [] blkdev_issue_flush+0x5a/0x90 Jul 28 01:26:36 osd1-05 kernel: [1644406.270919] [] blkdev_fsync+0x35/0x50 Jul 28 01:26:36 osd1-05 kernel: [1644406.270928] [] generic_write_sync+0x48/0x60 Jul 28 01:26:36 osd1-05 kernel: [1644406.270934] [] dio_complete+0x103/0x120 Jul 28 01:26:36 osd1-05 kernel: [1644406.270939] [] dio_aio_complete_work+0x21/0x30 Jul 28 01:26:36 osd1-05 kernel: [1644406.270948] [] process_one_work+0x178/0x470 Jul 28 01:26:36 osd1-05 kernel: [1644406.270953] [] ? manage_workers.isra.25+0x1f7/0x2e0 Jul 28 01:26:36 osd1-05 kernel: [1644406.270959] [] worker_thread+0x121/0x410 Jul 28 01:26:36 osd1-05 kernel: [1644406.270964] [] ? rescuer_thread+0x430/0x430 Jul 28 01:26:36 osd1-05 kernel: [1644406.270971] [] kthread+0xc9/0xe0 Jul 28 01:26:36 osd1-05 kernel: [1644406.270976] [] ? kthread_create_on_node+0x1c0/0x1c0 Jul 28 01:26:36 osd1-05 kernel: [1644406.270984] [] ret_from_fork+0x58/0x90 Jul 28 01:26:36 osd1-05 kernel: [1644406.270988] [] ? kthread_create_on_node+0x1c0/0x1c0 Jul 28 01:28:36 osd1-05 kernel: [1644526.317504] INFO: task kworker/12:2:25000 blocked for more than 120 seconds. Jul 28 01:28:36 osd1-05 kernel: [1644526.326399] Not tainted 3.13.0-87-generic #133-Ubuntu The actual raid configurations is: Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sdb1[1] sda1[0] 937123648 blocks super 1.2 [2/2] [UU] md1 : active raid1 sdb2[1] sda2[0] 39473024 blocks super 1.2 [2/2] [UU] md60 : active raid6 sdw[0] sdz[3] sdaa[4] sdx[1] sdy[2] 585689088 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/5] [U] unused devices: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-87-generic 3.13.0-87.133 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 28 06:17 seq crw-rw 1 root audio 116, 33 Jul 28 06:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 29.441344] init: plymouth-upstart-bridge main process ended, respawning Date: Thu Jul 28 07:33:28 2016 HibernationDevice: RESUME=UUID=a049dacc-3f5b-4282-b507-24d3a7382389 Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6047R-E1R36L PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic root=UUID=7052bcbe-dccf-47e4-a7f7-a95a09176541 ro quiet nomdmonddf nomdmonisw crashkernel=384M-:512M Rel
[Kernel-packages] [Bug 1607239] [NEW] mdadm raid gets frozen
Public bug reported: Servers periodically became unresponsive, and report the following problem: Jul 28 01:26:36 osd1-05 kernel: [1644406.270794] kworker/12:2D 88085fcd3180 0 25000 2 0x Jul 28 01:26:36 osd1-05 kernel: [1644406.270813] Workqueue: dio/bdev dio_aio_complete_work Jul 28 01:26:36 osd1-05 kernel: [1644406.270821] 88003694dc10 0046 8805621b4800 00013180 Jul 28 01:26:36 osd1-05 kernel: [1644406.270830] 88003694dfd8 00013180 8805621b4800 88003694dd38 Jul 28 01:26:36 osd1-05 kernel: [1644406.270836] 88003694dd40 7fff 8805621b4800 a6fd7000 Jul 28 01:26:36 osd1-05 kernel: [1644406.270842] Call Trace: Jul 28 01:26:36 osd1-05 kernel: [1644406.270857] [] schedule+0x29/0x70 Jul 28 01:26:36 osd1-05 kernel: [1644406.270870] [] schedule_timeout+0x279/0x310 Jul 28 01:26:36 osd1-05 kernel: [1644406.270880] [] ? md_make_request+0xd5/0x220 Jul 28 01:26:36 osd1-05 kernel: [1644406.270889] [] wait_for_completion+0xa6/0x150 Jul 28 01:26:36 osd1-05 kernel: [1644406.270900] [] ? wake_up_state+0x20/0x20 Jul 28 01:26:36 osd1-05 kernel: [1644406.270906] [] submit_bio_wait+0x5e/0x70 Jul 28 01:26:36 osd1-05 kernel: [1644406.270914] [] blkdev_issue_flush+0x5a/0x90 Jul 28 01:26:36 osd1-05 kernel: [1644406.270919] [] blkdev_fsync+0x35/0x50 Jul 28 01:26:36 osd1-05 kernel: [1644406.270928] [] generic_write_sync+0x48/0x60 Jul 28 01:26:36 osd1-05 kernel: [1644406.270934] [] dio_complete+0x103/0x120 Jul 28 01:26:36 osd1-05 kernel: [1644406.270939] [] dio_aio_complete_work+0x21/0x30 Jul 28 01:26:36 osd1-05 kernel: [1644406.270948] [] process_one_work+0x178/0x470 Jul 28 01:26:36 osd1-05 kernel: [1644406.270953] [] ? manage_workers.isra.25+0x1f7/0x2e0 Jul 28 01:26:36 osd1-05 kernel: [1644406.270959] [] worker_thread+0x121/0x410 Jul 28 01:26:36 osd1-05 kernel: [1644406.270964] [] ? rescuer_thread+0x430/0x430 Jul 28 01:26:36 osd1-05 kernel: [1644406.270971] [] kthread+0xc9/0xe0 Jul 28 01:26:36 osd1-05 kernel: [1644406.270976] [] ? kthread_create_on_node+0x1c0/0x1c0 Jul 28 01:26:36 osd1-05 kernel: [1644406.270984] [] ret_from_fork+0x58/0x90 Jul 28 01:26:36 osd1-05 kernel: [1644406.270988] [] ? kthread_create_on_node+0x1c0/0x1c0 Jul 28 01:28:36 osd1-05 kernel: [1644526.317504] INFO: task kworker/12:2:25000 blocked for more than 120 seconds. Jul 28 01:28:36 osd1-05 kernel: [1644526.326399] Not tainted 3.13.0-87-generic #133-Ubuntu The actual raid configurations is: Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sdb1[1] sda1[0] 937123648 blocks super 1.2 [2/2] [UU] md1 : active raid1 sdb2[1] sda2[0] 39473024 blocks super 1.2 [2/2] [UU] md60 : active raid6 sdw[0] sdz[3] sdaa[4] sdx[1] sdy[2] 585689088 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/5] [U] unused devices: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-87-generic 3.13.0-87.133 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 28 06:17 seq crw-rw 1 root audio 116, 33 Jul 28 06:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 29.441344] init: plymouth-upstart-bridge main process ended, respawning Date: Thu Jul 28 07:33:28 2016 HibernationDevice: RESUME=UUID=a049dacc-3f5b-4282-b507-24d3a7382389 Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6047R-E1R36L PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic root=UUID=7052bcbe-dccf-47e4-a7f7-a95a09176541 ro quiet nomdmonddf nomdmonisw crashkernel=384M-:512M RelatedPackageVersions: linux-restricted-modules-3.13.0-87-generic N/A linux-backports-modules-3.13.0-87-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRD
[Kernel-packages] [Bug 1605974] Re: usbduxsigma_firmware.bin: old version causes driver crash
The patch has just been applied to the kernel.org git. -- 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/1605974 Title: usbduxsigma_firmware.bin: old version causes driver crash Status in linux-firmware package in Ubuntu: New Bug description: The firmware of the usbduxsigma (alongside with the usbduxsigma.c) was updated in 2015 during a major rewrite but its binary was still the old one which causes the kernel driver to fail. I've submitted a patch to the kernel people (see below). However, as a quick fix could you also apply the patch to the package directly to have this fixed now and then we can wait until it trickles down from the kernel. I'm the maintainer of both the firmware and the drivers. This affects both 32 and 64 bit distros. Best, /Bernd Porr (www.linux-usb-daq.co.uk) Description: Ubuntu 16.04.1 LTS Release: 16.04 linux-firmware: Installed: 1.157.2 Candidate: 1.157.2 Version table: *** 1.157.2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 1.157 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages Expect to happen: plug in a duxduxsigma device, start comedirecord and see the signals plotted Happens instead: plug in a duxduxsigma device, start comedirecord and GARBLED DATA shows up / crash Fix: install this patch (new version of the firmware binary) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.2 [modified: lib/firmware/usbduxsigma_firmware.bin] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 24 10:04:19 2016 Dependencies: InstallationDate: Installed on 2013-12-09 (957 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131209) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to xenial on 2016-07-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1605974/+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 1606960] Re: linux: 4.4.0-34.53 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-34.53 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 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Wednesday, 27. July 2016 15:03 UTC - -- swm properties -- derivative-trackers-created: true phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 28. July 2016 07:05 UTC ** Description changed: This bug is for tracking the 4.4.0-34.53 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 -- derivative-trackers-created: true - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 28. July 2016 07:05 UTC + phase: Uploaded -- 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/1606960 Title: linux: 4.4.0-34.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-34.53 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 -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1606960/+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
