[Kernel-packages] [Bug 1364759] Re: ELAN touchpad-pointing device not detected
Dear Mr. Penalver, After the BIOS update, touchpad enabled successfully. Thank you so much for your efforts, sorry for wasting your time, I'll be more careful next time. ** 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/1364759 Title: ELAN touchpad-pointing device not detected Status in “linux” package in Ubuntu: Confirmed Bug description: I'm a ubuntu release 14.04 user on Gigabyte U24F, my ELAN touchpad-pointing device is not detected as a device by the system, I'm using external mouse to come over that issue. Hope this problem can be solved by the help of the suggested attachment files. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: batu 14841 F pulseaudio batu 17036 F pulseaudio /dev/snd/controlC1: batu 14841 F pulseaudio batu 17036 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=80243359-72c9-4388-9b42-648169cd8862 InstallationDate: Installed on 2014-06-17 (78 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: GIGABYTE U24 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=00c62373-bae0-436c-a6f9-78bbe9a5ee30 ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-06-28 (66 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U24.305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U24 dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU24.305:bd12/26/2013:svnGIGABYTE:pnU24:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU24:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: U24 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364759/+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 1348670] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010, set_nfsv4_acl_one+0x21/0xb0 [nfsd]
* Joseph Salisbury [2014-09-03 19:46:04 +]: Also, has the patch in comment #12 been sent upstream for inclusion in the mainline/stable kernel? The affected code was refactored out of existence in kernel 3.14. As such, my patch is inapplicable to 3.14 and later. The replacement set_acl methods in the various filesystem drivers generally are coded to cope with a NULL argument; I didn't conduct an exhaustive search but I looked at a few and didn't notice anything problematic. Given the above, I see no need to actually test kernel 3.17. Will tag. -- 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/1348670 Title: BUG: unable to handle kernel NULL pointer dereference at 0010, set_nfsv4_acl_one+0x21/0xb0 [nfsd] Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: In Progress Status in “linux” package in Debian: New Bug description: I've seen this happen twice in the last 8 days on an NFS server running Ubuntu precise and kernels 3.2.0-65.98-generic (on the first occasion) and 3.2.0-67.101-generic (the second time), amd64. This never happened before in several months of operation; until 2014-07-01 this server was running an older 3.2.0 kernel. When this error appears in the logs, the system stops answering NFS RPCs (e.g., rpcinfo -u localhost nfs 3 hangs) and a reboot is necessary to restore NFS service. A more detailed stack trace follows. Looking at the source code (fs/nfsd/vfs.c:set_nfsv4_acl_one()) I see that the call posix_acl_xattr_size(pacl-a_count) is not preceded by a check that pacl != NULL. Could this be related to the following entry in the changelog for 3.2.0-65.98? * NFSD: Call -set_acl with a NULL ACL structure if no entries - LP: #1328154 Jul 24 10:12:53 server kernel: [575939.742131] IP: [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] PGD c243bb067 PUD c2400a067 PMD 0 Jul 24 10:12:53 server kernel: [575939.742131] Oops: [#1] SMP Jul 24 10:12:53 server kernel: [575939.742131] CPU 3 Jul 24 10:12:53 server kernel: [575939.742131] Modules linked in: usblp btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs reiserfs ext2 cts openafs(P) xt_tcpudp ipmi_si ipmi_devintf ipmi_msghandler iptable_filter ip_tables x_tables autofs4 bnep parport_pc rfcomm bluetooth ppdev binfmt_misc rpcsec_gss_krb5 nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc xfs dm_crypt bridge stp psmouse hpilo sp5100_tco i2c_piix4 amd64_edac_mod hpwdt edac_core k10temp edac_mce_amd joydev serio_raw acpi_power_meter mac_hid lp parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath linear radeon ttm drm_kms_helper drm osst usbhid hid st ch i2c_algo_bit pata_atiixp hpsa bnx2 Jul 24 10:12:53 server kernel: [575939.742131] Jul 24 10:12:53 server kernel: [575939.742131] Pid: 2523, comm: nfsd Tainted: P O 3.2.0-67-generic #101-Ubuntu HP ProLiant DL385 G7 Jul 24 10:12:53 server kernel: [575939.742131] RIP: 0010:[a055c451] [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] RSP: 0018:880422085ce0 EFLAGS: 00010282 Jul 24 10:12:53 server kernel: [575939.742131] RAX: 4000 RBX: 880e29b16cc0 RCX: 013cc2cc Jul 24 10:12:53 server kernel: [575939.742131] RDX: a0583374 RSI: RDI: 880e29b16cc0 Jul 24 10:12:53 server kernel: [575939.742131] RBP: 880422085d10 R08: ea002cdf3b80 R09: a055c4af Jul 24 10:12:53 server kernel: [575939.742131] R10: 880b37ceed00 R11: 4004 R12: Jul 24 10:12:53 server kernel: [575939.742131] R13: 8807f56418c0 R14: R15: 880c2268d180 Jul 24 10:12:53 server kernel: [575939.742131] FS: 7fafd700() GS:88103fc8() knlGS: Jul 24 10:12:53 server kernel: [575939.742131] CS: 0010 DS: ES: CR0: 8005003b Jul 24 10:12:53 server kernel: [575939.742131] CR2: 0010 CR3: 000c22d6c000 CR4: 06e0 Jul 24 10:12:53 server kernel: [575939.742131] DR0: DR1: DR2: Jul 24 10:12:53 server kernel: [575939.742131] DR3: DR6: 0ff0 DR7: 0400 Jul 24 10:12:53 server kernel: [575939.742131] Process nfsd (pid: 2523, threadinfo 880422084000, task 880425964500) Jul 24 10:12:53 server kernel: [575939.742131] Stack: Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d040 880e29b16cc0 8807f56418c0 Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d180 880422085d50 a055d5e3 Jul 24 10:12:53 server kernel: [575939.742131]
[Kernel-packages] [Bug 320638] Re: hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device mapper on top = data corruption (bio too big device md0 (248 240))
** Changed in: linux Status: Fix Released = 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/320638 Title: hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device mapper on top = data corruption (bio too big device md0 (248 240)) Status in The Linux Kernel: Confirmed Status in mdadm - Tool for managing linux software RAID arrays.: Confirmed Status in “debian-installer” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Won't Fix Status in “mdadm” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Invalid Bug description: Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the device mapper and filesystem layer on top of the raid can not (always?) cope with that. Observations: * bio too big device mdX (248 240) messages in the syslog * read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.) Expected: Adding and removing members to running raids (hotplugging) should not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present. Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices). Fix: Upsteam has no formal bug tracking, but a mailing list. The response was that finally this needs to be fixed [outside of mdadm] by cleaning up the bio path so that big bios are split by the device that needs the split, not be the fs sending the bio. However, in the meantime mdadm needs to saveguard against the date corruption: [The mdadm] fix is to reject the added device [if] its limits are too low. Good Idea to avoid the data corruption. MD could save the max_sectors default limit for arrays. If the array is modified and the new limit gets smaller, postpone the sync until the next assembe/restart. And of course print a message if postponing, that explains when --force would be save. What ever that would be: no block device abstraction layer (device mapper, lvm, luks,...) between an unmounted? ext, fat?, ...? filesystem and md? As upsteam does not do public bug tracking, the status and rememberence of this need remains unsure though. --- This is on a MSI Wind U100 and I've got the following stack running: HDD SD card (USB card reader) - RAID1 - LUKS - LVM - Reiser Whenever I remove the HDD from the Raid1 mdadm /dev/md0 --fail /dev/sda2 mdadm /dev/md0 --remove /dev/sda2) for powersaving reasons, I cannot run any apt related tools. sudo apt-get update [...] Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources Reading package lists... Error! E: Read error - read (5 Input/output error) E: The package lists or status file could not be parsed or opened. Taking a look at the kernel log shows (and many more above): dmesg|tail [ 9479.330550] bio too big device md0 (248 240) [ 9479.331375] bio too big device md0 (248 240) [ 9479.332182] bio too big device md0 (248 240) [ 9611.980294] bio too big device md0 (248 240) [ 9742.929761] bio too big device md0 (248 240) [ 9852.932001] bio too big device md0 (248 240) [ 9852.935395] bio too big device md0 (248 240) [ 9852.938064] bio too big device md0 (248 240) [ 9853.081046] bio too big device md0 (248 240) [ 9853.081688] bio too big device md0 (248 240) $ sudo mdadm --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Tue Jan 13 11:25:57 2009 Raid Level : raid1 Array Size : 3871552 (3.69 GiB 3.96 GB) Used Dev Size : 3871552 (3.69 GiB 3.96 GB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 0 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Fri Jan 23 21:47:35 2009 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain) Events : 0.8767 Number Major Minor RaidDevice State 0 000 removed 1 8 171 active sync writemostly /dev/sdb1 $ sudo ubuntu-bug -p linux-meta dpkg-query: failed in buffer_read(fd): copy info
[Kernel-packages] [Bug 1348670] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010, set_nfsv4_acl_one+0x21/0xb0 [nfsd]
I'm a bit confused by Tim's changes in #16. The bug affects kernels up to and including 3.13 (trusty). I'll take his word that it also affects lucid, but what does a status of Invalid mean? ** Tags removed: regression-update ** Tags added: regression-updatekernel-fixed-upstream ** Tags removed: regression-updatekernel-fixed-upstream ** Tags added: kernel-fixed-upstream regression-update -- 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/1348670 Title: BUG: unable to handle kernel NULL pointer dereference at 0010, set_nfsv4_acl_one+0x21/0xb0 [nfsd] Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: In Progress Status in “linux” package in Debian: New Bug description: I've seen this happen twice in the last 8 days on an NFS server running Ubuntu precise and kernels 3.2.0-65.98-generic (on the first occasion) and 3.2.0-67.101-generic (the second time), amd64. This never happened before in several months of operation; until 2014-07-01 this server was running an older 3.2.0 kernel. When this error appears in the logs, the system stops answering NFS RPCs (e.g., rpcinfo -u localhost nfs 3 hangs) and a reboot is necessary to restore NFS service. A more detailed stack trace follows. Looking at the source code (fs/nfsd/vfs.c:set_nfsv4_acl_one()) I see that the call posix_acl_xattr_size(pacl-a_count) is not preceded by a check that pacl != NULL. Could this be related to the following entry in the changelog for 3.2.0-65.98? * NFSD: Call -set_acl with a NULL ACL structure if no entries - LP: #1328154 Jul 24 10:12:53 server kernel: [575939.742131] IP: [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] PGD c243bb067 PUD c2400a067 PMD 0 Jul 24 10:12:53 server kernel: [575939.742131] Oops: [#1] SMP Jul 24 10:12:53 server kernel: [575939.742131] CPU 3 Jul 24 10:12:53 server kernel: [575939.742131] Modules linked in: usblp btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs reiserfs ext2 cts openafs(P) xt_tcpudp ipmi_si ipmi_devintf ipmi_msghandler iptable_filter ip_tables x_tables autofs4 bnep parport_pc rfcomm bluetooth ppdev binfmt_misc rpcsec_gss_krb5 nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc xfs dm_crypt bridge stp psmouse hpilo sp5100_tco i2c_piix4 amd64_edac_mod hpwdt edac_core k10temp edac_mce_amd joydev serio_raw acpi_power_meter mac_hid lp parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath linear radeon ttm drm_kms_helper drm osst usbhid hid st ch i2c_algo_bit pata_atiixp hpsa bnx2 Jul 24 10:12:53 server kernel: [575939.742131] Jul 24 10:12:53 server kernel: [575939.742131] Pid: 2523, comm: nfsd Tainted: P O 3.2.0-67-generic #101-Ubuntu HP ProLiant DL385 G7 Jul 24 10:12:53 server kernel: [575939.742131] RIP: 0010:[a055c451] [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] RSP: 0018:880422085ce0 EFLAGS: 00010282 Jul 24 10:12:53 server kernel: [575939.742131] RAX: 4000 RBX: 880e29b16cc0 RCX: 013cc2cc Jul 24 10:12:53 server kernel: [575939.742131] RDX: a0583374 RSI: RDI: 880e29b16cc0 Jul 24 10:12:53 server kernel: [575939.742131] RBP: 880422085d10 R08: ea002cdf3b80 R09: a055c4af Jul 24 10:12:53 server kernel: [575939.742131] R10: 880b37ceed00 R11: 4004 R12: Jul 24 10:12:53 server kernel: [575939.742131] R13: 8807f56418c0 R14: R15: 880c2268d180 Jul 24 10:12:53 server kernel: [575939.742131] FS: 7fafd700() GS:88103fc8() knlGS: Jul 24 10:12:53 server kernel: [575939.742131] CS: 0010 DS: ES: CR0: 8005003b Jul 24 10:12:53 server kernel: [575939.742131] CR2: 0010 CR3: 000c22d6c000 CR4: 06e0 Jul 24 10:12:53 server kernel: [575939.742131] DR0: DR1: DR2: Jul 24 10:12:53 server kernel: [575939.742131] DR3: DR6: 0ff0 DR7: 0400 Jul 24 10:12:53 server kernel: [575939.742131] Process nfsd (pid: 2523, threadinfo 880422084000, task 880425964500) Jul 24 10:12:53 server kernel: [575939.742131] Stack: Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d040 880e29b16cc0 8807f56418c0 Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d180 880422085d50 a055d5e3 Jul 24 10:12:53 server kernel: [575939.742131] 880b37cee840 880c22684000 880c2268d040 Jul 24 10:12:53 server kernel: [575939.742131] Call Trace: Jul 24 10:12:53 server kernel:
[Kernel-packages] [Bug 1041790]
*** Bug 83473 has been marked as a duplicate of this bug. *** -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash to: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0 run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1341256] Re: Press caps lock on bluetooth keyboard then the keyboard go death
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New = Confirmed -- 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/1341256 Title: Press caps lock on bluetooth keyboard then the keyboard go death Status in “bluez” package in Ubuntu: Confirmed Bug description: I am typing using the Apple wireless keyboard,When I press 'caps lock',the keyboard don't work any more! So I go use keyboard on the Macbook.The key case have change,but the light on the key do not light on. I have to off the bluetooth then make it on again.Then reconnect the wireless keyboard. Yes,It work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 13 17:12:23 2014 InstallationDate: Installed on 2014-03-08 (126 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Apple Inc. MacBookPro9,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B08.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-4B7AC7E43945597E dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B7AC7E43945597E dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E: dmi.product.name: MacBookPro9,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 7C:D1:C3:79:A7:25 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:119665 acl:5720 sco:0 events:2443 errors:0 TX bytes:13420 acl:640 sco:0 commands:718 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1341256/+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 1364805] Re: [Lenovo ThinkPad T440p][10de:1290] hot key video out could not work under graphic performance mode.
** Description changed: Lenovo ThinkPad T440p ( CID 201309-14169 ) on Ubuntu 14.04 3.13.0-24-generic --- Steps to reproduce this bug: 1. install proprietary dirver nvidia-331 to enable the nvidia graphic card [10de:1290] 2. reboot 3. plugin mini display port of a monitor 4. press the hot key to try to switch to different display mode. Expected result: The display mode was changed. Actual result: Nothing happened. --- More information: 1. on power-saving mode, the hot key works 2. there are two kinds of port, VGA and mini-display port. Both of them have this issue. + 3. dash-display could set up the external monitor screen on mini-display and VGA port both. (mirror, extended, built-in screen only and external screen only) --- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1716 F pulseaudio /dev/snd/controlC0: ubuntu 1716 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 3 03:34:38 2014 HibernationDevice: RESUME=UUID=b437ec5c-4a11-4108-a4b7-900f2ea9f312 InstallationDate: Installed on 2014-08-27 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20ANZ03CUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=cb520008-8859-45fa-b8dd-d66a667b1be2 ro rootdelay=60 quiet splash initcall_debug RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GLET34WW (1.09.T05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANZ03CUS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET34WW(1.09.T05):bd08/20/2013:svnLENOVO:pn20ANZ03CUS:pvrThinkPadT440p:rvnLENOVO:rn20ANZ03CUS:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANZ03CUS dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO -- 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/1364805 Title: [Lenovo ThinkPad T440p][10de:1290] hot key video out could not work under graphic performance mode. Status in “linux” package in Ubuntu: Incomplete Bug description: Lenovo ThinkPad T440p ( CID 201309-14169 ) on Ubuntu 14.04 3.13.0-24-generic --- Steps to reproduce this bug: 1. install proprietary dirver nvidia-331 to enable the nvidia graphic card [10de:1290] 2. reboot 3. plugin mini display port of a monitor 4. press the hot key to try to switch to different display mode. Expected result: The display mode was changed. Actual result: Nothing happened. --- More information: 1. on power-saving mode, the hot key works 2. there are two kinds of port, VGA and mini-display port. Both of them have this issue. 3. dash-display could set up the external monitor screen on mini-display and VGA port both. (mirror, extended, built-in screen only and external screen only) --- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1716 F pulseaudio /dev/snd/controlC0: ubuntu 1716 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 3 03:34:38 2014 HibernationDevice: RESUME=UUID=b437ec5c-4a11-4108-a4b7-900f2ea9f312 InstallationDate: Installed on 2014-08-27 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20ANZ03CUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=cb520008-8859-45fa-b8dd-d66a667b1be2 ro rootdelay=60 quiet splash initcall_debug RelatedPackageVersions:
[Kernel-packages] [Bug 1341256] Re: Press caps lock on bluetooth keyboard then the keyboard go death
This problems seems to affect other BT keyboards as well: After hitting CapsLock, I have to do a re-connect of the Bluetooth keyboard. In my case a Fujitsu LX360 keyboard at a CSR bluetooth dongle (USB ID 0a12:0001). -- 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/1341256 Title: Press caps lock on bluetooth keyboard then the keyboard go death Status in “bluez” package in Ubuntu: Confirmed Bug description: I am typing using the Apple wireless keyboard,When I press 'caps lock',the keyboard don't work any more! So I go use keyboard on the Macbook.The key case have change,but the light on the key do not light on. I have to off the bluetooth then make it on again.Then reconnect the wireless keyboard. Yes,It work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 13 17:12:23 2014 InstallationDate: Installed on 2014-03-08 (126 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Apple Inc. MacBookPro9,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B08.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-4B7AC7E43945597E dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B7AC7E43945597E dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E: dmi.product.name: MacBookPro9,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 7C:D1:C3:79:A7:25 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:119665 acl:5720 sco:0 events:2443 errors:0 TX bytes:13420 acl:640 sco:0 commands:718 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1341256/+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 1349002] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195059/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195060/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195061/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195058/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] Re: Screen brightness cannot be changed on HP EliteBook 8560w
apport information ** Description changed: - I cannot change the screen brightness on my HP Elitebook 8560w. If I use - the keys for changing the screen brightness (fn + f9 or fn + f10), the - on-screen display appears and the displayed percentage changes as - intended but the actual screen brightness does not change (i.e. it - remains at full brightness). Similarly, if I do not use my computer for - some time, the on-screen display appears and indicates the the screen - brightness is reduced (lower percentage) but the actual screen - brightness remains unchanged (at full brightness). I have this computer - since November 2011 and I had always the latest Kubuntu version - installed. Changing the screen brightness always worked until and - including Kubuntu 13.10. However, it stopped working when I upgraded to - Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version - (F.42) but this did not help. As I also experience another bug (1337579) - with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel - (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug - occurs with all three kernel versions. + I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: ubuntu 3663 F pulseaudio + /dev/snd/controlC0: ubuntu 3663 F pulseaudio + CasperVersion: 1.340 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) + MachineType: Hewlett-Packard HP EliteBook 8560w + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaufb + ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity + ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-32-generic N/A + linux-backports-modules-3.13.0-32-generic N/A + linux-firmware 1.127.5 + Tags: trusty + Uname: Linux 3.13.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/15/2013 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: 68SVD Ver. F.42 + dmi.board.name: 1631 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: KBC Version 01.3D + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: + dmi.product.name: HP EliteBook 8560w + dmi.product.version: A0001D02 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195057/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I
[Kernel-packages] [Bug 1349002] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195062/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195068/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195070/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195065/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195064/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195063/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195067/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195071/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195066/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349002] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1349002/+attachment/4195069/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1074763] Re: Hauppauge HVR-2200 saa7164_api_i2c_read() error, ret(1) = 0xc
Ubuntu 14.04 here with kernel 3.13.0-35-generic with Hauppauge HVR-2200 used on MythTV 0.27.3 Still having similar issue This is what the problem starts out with in /var/log/kern.log [157860.889756] Event timed out [157860.889772] saa7164_api_i2c_read() error, ret(1) = 0x32 [157860.889781] tda10048_readreg: readreg error (ret == -5) And then some instances of this: [158001.548484] Event timed out [158001.548501] saa7164_api_i2c_write() error, ret(1) = 0x32 [158001.548514] __tda18271_write_regs: [10-0060|M] ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5 [158001.548522] tda18271_init: [10-0060|M] error -5 on line 832 [158001.548528] tda18271_tune: [10-0060|M] error -5 on line 910 [158001.548534] tda18271_set_params: [10-0060|M] error -5 on line 985 And then ends in repetition of the following until reboot: [159111.601585] saa7164_api_i2c_write() error, ret(1) = 0x32 [159111.601593] tda10048_writereg: writereg error (ret == -5) [159111.601607] saa7164_cmd_send() No free sequences -- 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/1074763 Title: Hauppauge HVR-2200 saa7164_api_i2c_read() error, ret(1) = 0xc Status in “linux” package in Ubuntu: Expired Bug description: I have a Hauppauge HVR 2200 dual tuner TV card that uses the Steven Toth saa7164 driver. I use Mythbuntu and MythTV to record television. I just noticed that, since last Sunday, nothing has recorded. Live TV did not work. I checked dmesg/kern.log and it was full of these: [784356.796077] saa7164_api_i2c_read() error, ret(1) = 0xc [784356.796083] tda10048_readreg: readreg error (ret == -5) [784356.796091] saa7164_cmd_send() No free sequences Growing every second to the point that I have two ~4GB kern.log files and my machine filled nearly 80GB of free space with logs etc. I have restarted the machine and now it is working correctly. Looking around the internet, it seems that others have the same problem and it keeps recurring at random times after a reboot: https://github.com/OpenELEC/OpenELEC.tv/issues/1349 http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/39591 http://ubuntuforums.org/archive/index.php/t-1983887.html I am using the latest Mythbuntu (which is 12.04). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-32-generic 3.2.0-32.51 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythbuntu 2200 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 48 Simple ctrls : 22 Date: Sat Nov 3 22:09:55 2012 HibernationDevice: RESUME=UUID=b0cf6e35-1d80-4364-9309-f79e4324b37a InstallationMedia: Mythbuntu 12.04 Precise Pangolin - Release amd64 (20120425) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=ead8d6ee-fce1-4e8e-9157-17618da2b2e1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-32-generic N/A linux-backports-modules-3.2.0-32-generic N/A linux-firmware1.79.1 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: GA-MA78GM-S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd09/19/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GM-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GM-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA78GM-S2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1074763/+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 1349002] Re: Screen brightness cannot be changed on HP EliteBook 8560w
** 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/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Confirmed Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1364759] Re: ELAN touchpad-pointing device not detected
bmankir, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364759/comments/19 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364759 Title: ELAN touchpad-pointing device not detected Status in “linux” package in Ubuntu: Invalid Bug description: I'm a ubuntu release 14.04 user on Gigabyte U24F, my ELAN touchpad-pointing device is not detected as a device by the system, I'm using external mouse to come over that issue. Hope this problem can be solved by the help of the suggested attachment files. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: batu 14841 F pulseaudio batu 17036 F pulseaudio /dev/snd/controlC1: batu 14841 F pulseaudio batu 17036 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=80243359-72c9-4388-9b42-648169cd8862 InstallationDate: Installed on 2014-06-17 (78 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: GIGABYTE U24 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=00c62373-bae0-436c-a6f9-78bbe9a5ee30 ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-06-28 (66 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U24.305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U24 dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU24.305:bd12/26/2013:svnGIGABYTE:pnU24:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU24:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: U24 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364759/+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 1349002] Re: Screen brightness cannot be changed on HP EliteBook 8560w
Arne Henningsen, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc3-utopic/ and advise to the results? ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+attachment/4163536/+files/ProcEnviron.txt ** Tags added: regression-release ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349002 Title: Screen brightness cannot be changed on HP EliteBook 8560w Status in “linux” package in Ubuntu: Incomplete Bug description: I cannot change the screen brightness on my HP Elitebook 8560w. If I use the keys for changing the screen brightness (fn + f9 or fn + f10), the on-screen display appears and the displayed percentage changes as intended but the actual screen brightness does not change (i.e. it remains at full brightness). Similarly, if I do not use my computer for some time, the on-screen display appears and indicates the the screen brightness is reduced (lower percentage) but the actual screen brightness remains unchanged (at full brightness). I have this computer since November 2011 and I had always the latest Kubuntu version installed. Changing the screen brightness always worked until and including Kubuntu 13.10. However, it stopped working when I upgraded to Kubuntu 14.04. I have upgraded my computer's BIOS to the latest version (F.42) but this did not help. As I also experience another bug (1337579) with Kubuntu 14.04, I have upgraded the kernel to the upstream kernel (3.14.4-031404) and a mainline kernel (3.16.0-031600rc6) but the bug occurs with all three kernel versions. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3663 F pulseaudio /dev/snd/controlC0: ubuntu 3663 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8560w Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349002/+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 1349282] Re: The gpu-manager should allow RandR offloading without bbswitch
** Description changed: + SRU Request + + While bbswitch may fail on some hybrid systems (e.g. on the desktop or + when the bbswitch module fails to build), this is not a good reason to + prevent the system from offloading rendering to the NVIDIA GPU. + + [Impact] + * This problem makes it impossible to use the NVIDIA GPU on hybrid systems with Intel+NVIDIA GPUs when bbswitch is not available (i.e. when it fails to load). + + [Test Case] + * Make sure to be using a hybrid system with Intel+NVIDIA GPUs. + + * Check that bbswitch is not available. You can do so by posting output of the following command: +test -e /proc/acpi/bbswitch echo true || echo false + + * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). + + * Install ubuntu-drivers-common from trusty-proposed. + + * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): +sudo apt-get --purge remove nvidia-331 +sudo apt-get --purge remove nvidia-331 +sudo apt-get --purge remove fglrx +sudo apt-get --purge remove fglrx-updates + + * Restart the system. + + * Install the nvidia binary driver, reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) + - Expected: the NVIDIA discrete GPU is enabled. + - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. + + [Regression Potential] + * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. + + [Other Info] + * N/A + + --- + The gpu-manager should allow RandR offloading without bbswitch. This would allow desktop systems to make use of offloading even when bbswitch is not supported. Also, nvidia-settings should not complain in such scenarios. See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1310023/comments/70 -- 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/1349282 Title: The gpu-manager should allow RandR offloading without bbswitch Status in “nvidia-settings” package in Ubuntu: Triaged Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “nvidia-settings” source package in Trusty: Triaged Status in “ubuntu-drivers-common” source package in Trusty: In Progress Bug description: SRU Request While bbswitch may fail on some hybrid systems (e.g. on the desktop or when the bbswitch module fails to build), this is not a good reason to prevent the system from offloading rendering to the NVIDIA GPU. [Impact] * This problem makes it impossible to use the NVIDIA GPU on hybrid systems with Intel+NVIDIA GPUs when bbswitch is not available (i.e. when it fails to load). [Test Case] * Make sure to be using a hybrid system with Intel+NVIDIA GPUs. * Check that bbswitch is not available. You can do so by posting output of the following command: test -e /proc/acpi/bbswitch echo true || echo false * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Install ubuntu-drivers-common from trusty-proposed. * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Restart the system. * Install the nvidia binary driver, reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the NVIDIA discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A --- The gpu-manager should allow RandR offloading without bbswitch. This would allow desktop systems to make use of offloading even when bbswitch is not supported. Also, nvidia-settings should not complain in such scenarios. See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1310023/comments/70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1349282/+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 1365378] [NEW] [Regression] realtek pci-e card readers don't recognize mmc cards
Public bug reported: It's a regression introduced by a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) from v3.13, only trusty is affected. This commit could fix it: From 5027251eced6e34315a52bd841279df957f627bb Mon Sep 17 00:00:00 2001 From: Micky Ching micky_ch...@realsil.com.cn Date: Thu, 27 Mar 2014 13:35:04 +0800 Subject: [PATCH] mmc: rtsx: add R1-no-CRC mmc command type handle a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) produced a cmd.flags unhandled in realtek pci host driver. This will make MMC card fail to initialize, this patch is used to handle the new cmd.flags condition and MMC card can be used. Signed-off-by: Micky Ching micky_ch...@realsil.com.cn Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Signed-off-by: Chris Ball ch...@printf.net --- drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++ 1 file changed, 3 insertions(+) ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Adam Lee (adam8157) Status: In Progress ** Description changed: It's a regression introduced by a27fbf2f067b0cd (mmc: add ignorance - case for CMD13 CRC error). + case for CMD13 CRC error) from v3.13, only trusty is affected. This commit could fix it: From 5027251eced6e34315a52bd841279df957f627bb Mon Sep 17 00:00:00 2001 From: Micky Ching micky_ch...@realsil.com.cn Date: Thu, 27 Mar 2014 13:35:04 +0800 Subject: [PATCH] mmc: rtsx: add R1-no-CRC mmc command type handle a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) produced a cmd.flags unhandled in realtek pci host driver. This will make MMC card fail to initialize, this patch is used to handle the new cmd.flags condition and MMC card can be used. Signed-off-by: Micky Ching micky_ch...@realsil.com.cn Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Signed-off-by: Chris Ball ch...@printf.net --- - drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++ - 1 file changed, 3 insertions(+) + drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++ + 1 file changed, 3 insertions(+) -- 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/1365378 Title: [Regression] realtek pci-e card readers don't recognize mmc cards Status in HWE Next Project: New Status in “linux” package in Ubuntu: In Progress Bug description: It's a regression introduced by a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) from v3.13, only trusty is affected. This commit could fix it: From 5027251eced6e34315a52bd841279df957f627bb Mon Sep 17 00:00:00 2001 From: Micky Ching micky_ch...@realsil.com.cn Date: Thu, 27 Mar 2014 13:35:04 +0800 Subject: [PATCH] mmc: rtsx: add R1-no-CRC mmc command type handle a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) produced a cmd.flags unhandled in realtek pci host driver. This will make MMC card fail to initialize, this patch is used to handle the new cmd.flags condition and MMC card can be used. Signed-off-by: Micky Ching micky_ch...@realsil.com.cn Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Signed-off-by: Chris Ball ch...@printf.net --- drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++ 1 file changed, 3 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1365378/+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 1365378] Re: [Regression] realtek pci-e card readers don't recognize mmc cards
patch is submitted to kernel-team@ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365378 Title: [Regression] realtek pci-e card readers don't recognize mmc cards Status in HWE Next Project: New Status in “linux” package in Ubuntu: In Progress Bug description: It's a regression introduced by a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) from v3.13, only trusty is affected. This commit could fix it: From 5027251eced6e34315a52bd841279df957f627bb Mon Sep 17 00:00:00 2001 From: Micky Ching micky_ch...@realsil.com.cn Date: Thu, 27 Mar 2014 13:35:04 +0800 Subject: [PATCH] mmc: rtsx: add R1-no-CRC mmc command type handle a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) produced a cmd.flags unhandled in realtek pci host driver. This will make MMC card fail to initialize, this patch is used to handle the new cmd.flags condition and MMC card can be used. Signed-off-by: Micky Ching micky_ch...@realsil.com.cn Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Signed-off-by: Chris Ball ch...@printf.net --- drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++ 1 file changed, 3 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1365378/+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 1322211] Re: linux-image-3.13.0-24-generic kernel doesn't boot on Xen 3.0 from CentOS5
FYI, this bug is now fixed by http://kernel.ubuntu.com/git?p=ubuntu /ubuntu-trusty.git;a=commit;h=6ac0d80c79b062b44135cec6436d6eeeaeed1ec2. I've tested linux-image-3.13.0-35-generic version 3.13.0-35.62~precise1 and can confirm it's working OK. So this bug report can probably be closed. Tore -- 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/1322211 Title: linux-image-3.13.0-24-generic kernel doesn't boot on Xen 3.0 from CentOS5 Status in “linux” package in Ubuntu: Triaged Bug description: linux-image-3.13.0-24-generic does not boot on Xen 3.0. Tested on CentOS 5.10. Boot crashes before any output from kernel. Output from xm dmesg: (XEN) event_channel.c:181:d0 EVTCHNOP failure: domain 0, error -22, line 181 (XEN) event_channel.c:181:d0 EVTCHNOP failure: domain 0, error -22, line 181 (XEN) traps.c:1912:d2004 Domain attempted WRMSR 008b from 0015: to :. (XEN) traps.c:405:d2004 Unhandled invalid opcode fault/trap [#6] in domain 2004 on VCPU 0 [ec=] (XEN) domain_crash_sync called from entry.S (XEN) Domain 2004 (vcpu#0) crashed on cpu#14: (XEN) [ Xen-3.1.2-308.8.2.el5 x86_64 debug=n Not tainted ] (XEN) CPU:14 (XEN) RIP:e033:[81004c38] (XEN) RFLAGS: 0282 CONTEXT: guest (XEN) rax: ffea rbx: 023ff000 rcx: 0002 (XEN) rdx: 0001 rsi: 81c01e48 rdi: (XEN) rbp: 81c01e58 rsp: 81c01e08 r8: (XEN) r9: 81c01dc8 r10: 7ff0 r11: (XEN) r12: 81dd6900 r13: r14: (XEN) r15: cr0: 80050033 cr4: 26b0 (XEN) cr3: 001dde584000 cr2: (XEN) ds: es: fs: gs: ss: e02b cs: e033 (XEN) Guest stack trace from rsp=81c01e08: (XEN)0002 81004c38 0001e030 (XEN)00010082 81c01e48 e02b 81004c32 (XEN)00010004 8171e4a0 81c01e78 81d38f1d (XEN)00010001 81727ed0 81c01ef0 81d3c58b (XEN) 81c01ef0 81c01f08 (XEN)0010 81c01f00 81c01ec0 81ebc632 (XEN) 81dd6900 (XEN) 81c01f30 81d34c07 0018 (XEN)356a4e4bd08da87b 81c01f60 f3df (XEN) 81c01f40 81d345ee 81c01ff8 (XEN)81d384a7 000206c2 000133200800 0f898371 (XEN) (XEN) (XEN) (XEN) (XEN) 0f0060c0c748 (XEN)c305 (XEN) (XEN) (XEN) Appears to be a known bug that has not been patched in mainline kernel yet: http://lists.xen.org/archives/html/xen-devel/2014-05/msg01474.html Tested recompiling from kernel at git://kernel.ubuntu.com/ubuntu /ubuntu-trusty.git with patch from above thread. # lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 # apt-cache policy linux-image-3.13.0-24-generic linux-image-3.13.0-24-generic: Installed: 3.13.0-24.46 Candidate: 3.13.0-24.46 Version table: *** 3.13.0-24.46 0 100 /var/lib/dpkg/status --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 15:10 seq crw-rw 1 root audio 116, 33 May 22 15:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory 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 CurrentDmesg: [ 20.010048] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not
[Kernel-packages] [Bug 1348670] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010, set_nfsv4_acl_one+0x21/0xb0 [nfsd]
Invalid for the development release is appropriate as this code was removed in v3.14 (you indicate). This looks applicable to P and T indeed. ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Precise) Assignee: (unassigned) = Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Precise) Status: New = In Progress ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348670 Title: BUG: unable to handle kernel NULL pointer dereference at 0010, set_nfsv4_acl_one+0x21/0xb0 [nfsd] Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: In Progress Status in “linux” source package in Precise: In Progress Status in “linux” source package in Trusty: New Status in “linux” source package in Utopic: Invalid Status in “linux” package in Debian: New Bug description: I've seen this happen twice in the last 8 days on an NFS server running Ubuntu precise and kernels 3.2.0-65.98-generic (on the first occasion) and 3.2.0-67.101-generic (the second time), amd64. This never happened before in several months of operation; until 2014-07-01 this server was running an older 3.2.0 kernel. When this error appears in the logs, the system stops answering NFS RPCs (e.g., rpcinfo -u localhost nfs 3 hangs) and a reboot is necessary to restore NFS service. A more detailed stack trace follows. Looking at the source code (fs/nfsd/vfs.c:set_nfsv4_acl_one()) I see that the call posix_acl_xattr_size(pacl-a_count) is not preceded by a check that pacl != NULL. Could this be related to the following entry in the changelog for 3.2.0-65.98? * NFSD: Call -set_acl with a NULL ACL structure if no entries - LP: #1328154 Jul 24 10:12:53 server kernel: [575939.742131] IP: [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] PGD c243bb067 PUD c2400a067 PMD 0 Jul 24 10:12:53 server kernel: [575939.742131] Oops: [#1] SMP Jul 24 10:12:53 server kernel: [575939.742131] CPU 3 Jul 24 10:12:53 server kernel: [575939.742131] Modules linked in: usblp btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs reiserfs ext2 cts openafs(P) xt_tcpudp ipmi_si ipmi_devintf ipmi_msghandler iptable_filter ip_tables x_tables autofs4 bnep parport_pc rfcomm bluetooth ppdev binfmt_misc rpcsec_gss_krb5 nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc xfs dm_crypt bridge stp psmouse hpilo sp5100_tco i2c_piix4 amd64_edac_mod hpwdt edac_core k10temp edac_mce_amd joydev serio_raw acpi_power_meter mac_hid lp parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath linear radeon ttm drm_kms_helper drm osst usbhid hid st ch i2c_algo_bit pata_atiixp hpsa bnx2 Jul 24 10:12:53 server kernel: [575939.742131] Jul 24 10:12:53 server kernel: [575939.742131] Pid: 2523, comm: nfsd Tainted: P O 3.2.0-67-generic #101-Ubuntu HP ProLiant DL385 G7 Jul 24 10:12:53 server kernel: [575939.742131] RIP: 0010:[a055c451] [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] RSP: 0018:880422085ce0 EFLAGS: 00010282 Jul 24 10:12:53 server kernel: [575939.742131] RAX: 4000 RBX: 880e29b16cc0 RCX: 013cc2cc Jul 24 10:12:53 server kernel: [575939.742131] RDX: a0583374 RSI: RDI: 880e29b16cc0 Jul 24 10:12:53 server kernel: [575939.742131] RBP: 880422085d10 R08: ea002cdf3b80 R09: a055c4af Jul 24 10:12:53 server kernel: [575939.742131] R10: 880b37ceed00 R11: 4004 R12: Jul 24 10:12:53 server kernel: [575939.742131] R13: 8807f56418c0 R14: R15: 880c2268d180 Jul 24 10:12:53 server kernel: [575939.742131] FS: 7fafd700() GS:88103fc8() knlGS: Jul 24 10:12:53 server kernel: [575939.742131] CS: 0010 DS: ES: CR0: 8005003b Jul 24 10:12:53 server kernel: [575939.742131] CR2: 0010 CR3: 000c22d6c000 CR4: 06e0 Jul 24 10:12:53 server kernel: [575939.742131] DR0: DR1: DR2: Jul 24 10:12:53 server kernel: [575939.742131] DR3: DR6: 0ff0 DR7: 0400 Jul 24 10:12:53 server kernel: [575939.742131] Process nfsd (pid: 2523, threadinfo 880422084000, task 880425964500) Jul 24 10:12:53 server kernel: [575939.742131] Stack: Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d040 880e29b16cc0 8807f56418c0
[Kernel-packages] [Bug 1348670] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010, set_nfsv4_acl_one+0x21/0xb0 [nfsd]
** Changed in: linux (Ubuntu Precise) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348670 Title: BUG: unable to handle kernel NULL pointer dereference at 0010, set_nfsv4_acl_one+0x21/0xb0 [nfsd] Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: In Progress Status in “linux” source package in Precise: Fix Committed Status in “linux” source package in Trusty: New Status in “linux” source package in Utopic: Invalid Status in “linux” package in Debian: New Bug description: I've seen this happen twice in the last 8 days on an NFS server running Ubuntu precise and kernels 3.2.0-65.98-generic (on the first occasion) and 3.2.0-67.101-generic (the second time), amd64. This never happened before in several months of operation; until 2014-07-01 this server was running an older 3.2.0 kernel. When this error appears in the logs, the system stops answering NFS RPCs (e.g., rpcinfo -u localhost nfs 3 hangs) and a reboot is necessary to restore NFS service. A more detailed stack trace follows. Looking at the source code (fs/nfsd/vfs.c:set_nfsv4_acl_one()) I see that the call posix_acl_xattr_size(pacl-a_count) is not preceded by a check that pacl != NULL. Could this be related to the following entry in the changelog for 3.2.0-65.98? * NFSD: Call -set_acl with a NULL ACL structure if no entries - LP: #1328154 Jul 24 10:12:53 server kernel: [575939.742131] IP: [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] PGD c243bb067 PUD c2400a067 PMD 0 Jul 24 10:12:53 server kernel: [575939.742131] Oops: [#1] SMP Jul 24 10:12:53 server kernel: [575939.742131] CPU 3 Jul 24 10:12:53 server kernel: [575939.742131] Modules linked in: usblp btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs reiserfs ext2 cts openafs(P) xt_tcpudp ipmi_si ipmi_devintf ipmi_msghandler iptable_filter ip_tables x_tables autofs4 bnep parport_pc rfcomm bluetooth ppdev binfmt_misc rpcsec_gss_krb5 nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc xfs dm_crypt bridge stp psmouse hpilo sp5100_tco i2c_piix4 amd64_edac_mod hpwdt edac_core k10temp edac_mce_amd joydev serio_raw acpi_power_meter mac_hid lp parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath linear radeon ttm drm_kms_helper drm osst usbhid hid st ch i2c_algo_bit pata_atiixp hpsa bnx2 Jul 24 10:12:53 server kernel: [575939.742131] Jul 24 10:12:53 server kernel: [575939.742131] Pid: 2523, comm: nfsd Tainted: P O 3.2.0-67-generic #101-Ubuntu HP ProLiant DL385 G7 Jul 24 10:12:53 server kernel: [575939.742131] RIP: 0010:[a055c451] [a055c451] set_nfsv4_acl_one+0x21/0xb0 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] RSP: 0018:880422085ce0 EFLAGS: 00010282 Jul 24 10:12:53 server kernel: [575939.742131] RAX: 4000 RBX: 880e29b16cc0 RCX: 013cc2cc Jul 24 10:12:53 server kernel: [575939.742131] RDX: a0583374 RSI: RDI: 880e29b16cc0 Jul 24 10:12:53 server kernel: [575939.742131] RBP: 880422085d10 R08: ea002cdf3b80 R09: a055c4af Jul 24 10:12:53 server kernel: [575939.742131] R10: 880b37ceed00 R11: 4004 R12: Jul 24 10:12:53 server kernel: [575939.742131] R13: 8807f56418c0 R14: R15: 880c2268d180 Jul 24 10:12:53 server kernel: [575939.742131] FS: 7fafd700() GS:88103fc8() knlGS: Jul 24 10:12:53 server kernel: [575939.742131] CS: 0010 DS: ES: CR0: 8005003b Jul 24 10:12:53 server kernel: [575939.742131] CR2: 0010 CR3: 000c22d6c000 CR4: 06e0 Jul 24 10:12:53 server kernel: [575939.742131] DR0: DR1: DR2: Jul 24 10:12:53 server kernel: [575939.742131] DR3: DR6: 0ff0 DR7: 0400 Jul 24 10:12:53 server kernel: [575939.742131] Process nfsd (pid: 2523, threadinfo 880422084000, task 880425964500) Jul 24 10:12:53 server kernel: [575939.742131] Stack: Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d040 880e29b16cc0 8807f56418c0 Jul 24 10:12:53 server kernel: [575939.742131] 880c2268d180 880422085d50 a055d5e3 Jul 24 10:12:53 server kernel: [575939.742131] 880b37cee840 880c22684000 880c2268d040 Jul 24 10:12:53 server kernel: [575939.742131] Call Trace: Jul 24 10:12:53 server kernel: [575939.742131] [a055d5e3] nfsd4_set_nfs4_acl+0x143/0x150 [nfsd] Jul 24 10:12:53 server kernel: [575939.742131] [a056ab74]
[Kernel-packages] [Bug 1318218] Re: SATA problems on MacBook Pro 11, 1?
I'm getting these errors in Xubuntu 14.04 amd64 with nvidia binaries on
a Lenovo Thinkpad W510. I only noticed them because several times over
the past couple of months since installing Xubuntu 14.04, the machine
has suddenly, and quite randomly, remounted the filesystem to read only.
When that happens, I can't even shut down normally. I can't even log in
via a TTY to issue a shutdown command. When I installed Xubuntu 14.04, I
also upgraded from a hard drive to a Crucial MX100 SSD, but it seems
likelier the problem is software, not hardware. I don't have any buffer
I/O errors or anything like that in kern.log or syslog.
--
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/1318218
Title:
SATA problems on MacBook Pro 11,1?
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
I installed Ubuntu 14.04 next to MacOS following the guide at
https://help.ubuntu.com/community/MacBookPro11-1/Saucy/
Looking into dmesg, I constantlz get entries like
[ 276.380934] ata1: SError: { PHYRdyChg }
[ 276.380943] ata1: hard resetting link
[ 277.103527] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 277.103999] ata1.00: unexpected _GTF length (8)
[ 277.104504] ata1.00: unexpected _GTF length (8)
[ 277.104507] ata1.00: configured for UDMA/33
[ 277.104629] ata1: EH complete
[ 277.206319] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe
frozen
[ 277.206328] ata1: irq_stat 0x0040, PHY RDY changed
[ 277.206333] ata1: SError: { PHYRdyChg }
[ 277.206343] ata1: hard resetting link
[ 277.927757] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 277.928425] ata1.00: unexpected _GTF length (8)
[ 277.929040] ata1.00: unexpected _GTF length (8)
[ 277.929051] ata1.00: configured for UDMA/33
[ 277.929168] ata1: EH complete
[ 278.030944] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe
frozen
[ 278.030952] ata1: irq_stat 0x0040, PHY RDY changed
[ 278.030957] ata1: SError: { PHYRdyChg }
[ 278.030965] ata1: hard resetting link
[ 278.752008] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 278.752582] ata1.00: unexpected _GTF length (8)
[ 278.753140] ata1.00: unexpected _GTF length (8)
[ 278.753147] ata1.00: configured for UDMA/33
[ 278.753231] ata1: EH complete
[ 278.853417] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe
frozen
[ 278.853424] ata1: irq_stat 0x0040, PHY RDY changed
[ 278.853427] ata1: SError: { PHYRdyChg }
[ 278.853434] ata1: hard resetting link
[ 279.576258] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 279.576881] ata1.00: unexpected _GTF length (8)
[ 279.577417] ata1.00: unexpected _GTF length (8)
[ 279.577427] ata1.00: configured for UDMA/33
[ 279.577491] ata1: EH complete
[ 279.677753] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe
frozen
[ 279.677762] ata1: irq_stat 0x0040, PHY RDY changed
[ 279.677767] ata1: SError: { PHYRdyChg }
[ 279.66] ata1: hard resetting link
[ 280.400449] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 280.401147] ata1.00: unexpected _GTF length (8)
[ 280.401722] ata1.00: unexpected _GTF length (8)
[ 280.401733] ata1.00: configured for UDMA/33
[ 280.401809] ata1: EH complete
[ 280.502117] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe
frozen
[ 280.502127] ata1: irq_stat 0x0040, PHY RDY changed
[ 280.502132] ata1: SError: { PHYRdyChg }
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: markus 1663 F pulseaudio
/dev/snd/controlC1: markus 1663 F pulseaudio
CurrentDesktop: Unity
Date: Sat May 10 19:33:44 2014
HibernationDevice: RESUME=UUID=c71381d2-e2f3-4c96-94ea-57b8986afd08
InstallationDate: Installed on 2014-05-09 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Apple Inc. MacBookPro11,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
root=UUID=7584bc70-893a-4291-a1cb-4680f5e09d22 ro libata.force=noncq quiet
splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B03.1310291227
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name:
[Kernel-packages] [Bug 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-vfs-obexftp (Ubuntu) Status: New = Confirmed -- 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/1284308 Title: Bogus another operation in progress error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gnome-vfs-obexftp” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose bluetooth settings 3 - select the phone among the listed devices 4 - click on Browse files 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer = I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is another operation in progress. Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then ejected the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error This location could not be displayed. Another operation in progress, so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when ejecting the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1365457] [NEW] [Lenovo ThinkPad X220] suspend/resume failure.
*** This bug is a duplicate of bug 1363853 *** https://bugs.launchpad.net/bugs/1363853 Public bug reported: No idea what happened. This is with 3.17. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-12-generic 3.16.0-12.18 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2618 F pulseaudio Date: Thu Sep 4 13:37:09 2014 ExecutablePath: /usr/share/apport/apportcheckresume HibernationDevice: RESUME=UUID=e3968bc2-4b49-4bc2-a8f2-485b8cdd957f InstallationDate: Installed on 2013-12-22 (256 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 429149G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-12-generic N/A linux-backports-modules-3.16.0-12-generic N/A linux-firmware 1.133 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops utopic ** This bug has been marked a duplicate of bug 1363853 [Lenovo ThinkPad X220] suspend/resume failure -- 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/1365457 Title: [Lenovo ThinkPad X220] suspend/resume failure. Status in “linux” package in Ubuntu: New Bug description: No idea what happened. This is with 3.17. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-12-generic 3.16.0-12.18 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2618 F pulseaudio Date: Thu Sep 4 13:37:09 2014 ExecutablePath: /usr/share/apport/apportcheckresume HibernationDevice: RESUME=UUID=e3968bc2-4b49-4bc2-a8f2-485b8cdd957f InstallationDate: Installed on 2013-12-22 (256 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 429149G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-12-generic N/A linux-backports-modules-3.16.0-12-generic N/A linux-firmware 1.133 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1363853] Re: [Lenovo ThinkPad X220] suspend/resume failure
Bug 1365457 is a dup of this and has the information of 3.17-rc3. Same problem. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363853 Title: [Lenovo ThinkPad X220] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: No idea what happened. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2818 F pulseaudio Date: Mon Sep 1 09:13:35 2014 DuplicateSignature: suspend/resume:LENOVO 429149G:8DET46WW (1.16 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=e3968bc2-4b49-4bc2-a8f2-485b8cdd957f InstallationDate: Installed on 2013-12-22 (252 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 429149G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-11-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.133 SourcePackage: linux Title: [LENOVO 429149G] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363853/+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 1176577] Re: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8
Thanks for the info. Once I enable debug, what should I look for? I trying to look where connect process is stuck, if driver really write data to FW or not. -- 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/1176577 Title: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8 Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Arch Linux: New Status in “linux” package in Fedora: Unknown Bug description: Right after upgrading kernel from 3.5 to 3.8 (Ubuntu 13.04), the syslog got flooded by a large number of such messages: (cut) May 5 15:33:15 compaq-aldo kernel: [ 205.064042] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:21 compaq-aldo kernel: [ 211.076029] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:27 compaq-aldo kernel: [ 217.088035] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:33 compaq-aldo kernel: [ 223.100039] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:39 compaq-aldo kernel: [ 229.112045] mei :00:03.0: unexpected reset: dev_state = RESETING (cut) This was associated by non reliable ethernet functionality, i.e. transfer of large files from my Ubuntu box to a local NAS connected via ethernet got hanging with no other apparent errors or diagnostics: nautilus copy just stopped transferring data, leaving the copy window there with the progress bar stopped. I tried to reboot, but this behaviour is perfectly reproducible. This is one of the first syslog lines got from that kernel: May 5 15:30:15 compaq-aldo kernel: [0.00] Linux version 3.8.0-19-generic (buildd@roseapple) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 (Ubuntu 3.8.0-19.30-generic 3.8.8) I attach the whole syslog from boot of that kernel. On the same box, launching a previsous kernel (3.5) works flawlessly. For the time being, I removed 3.8 kernel from my box, now running 3.5. Kind regards Aldo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ldx2074 F pulseaudio /dev/snd/controlC0: ldx2074 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=32cc5d6d-43c1-4e97-a8b7-10b71aac3e29 InstallationDate: Installed on 2013-01-04 (121 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=38ce1d51-c3cf-438d-b395-f7c4744e2e37 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-26 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark dmi.bios.date: 04/13/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.10 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC7451V4Q dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.10:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+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 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity
4 September amd64 .iso boots to flashing desktop, no unity. 3.16.0-12 kernel in the .iso according to ls /boot fails to start unity. My -11 updated to -12 does work. Now the .iso is usually behind apt-get update. Past experience if the .iso isn't running correctly the install won't either. Not sure it's worth my while to install the non-unity .iso and try an update. Bummer. -- 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/1359299 Title: utopic 3.16.0-9 iso boots to desktop no unity Status in Unity: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Confirmed Bug description: Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre. Boots 3.16.0-6 amd64 fine, runs compiz 3D fine. Today's amd64 iso download, 20 August, boots to desktop cursor. No unity. Did ubuntu-bug from command line on the booted iso, saved report. Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file. Planet Ubuntu asked for results on 3.16.0-9 so this is my result. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-9-generic 3.16.0-9.14 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CasperVersion: 1.341 Date: Wed Aug 20 16:57:57 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140820) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359299/+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 1365485] [NEW] Kernel BUG with multiple NFS4 kerberos mounts on boot
Public bug reported: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs-utils: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: gssd kerberos nfs4 ** Attachment added: dmesg output https://bugs.launchpad.net/bugs/1365485/+attachment/4195365/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: New Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts
[Kernel-packages] [Bug 1365485] Re: Kernel BUG with multiple NFS4 kerberos mounts on boot
I'll just chime in (from the same site as Jani) that lacking a proper fix, it would be nice if the boot-time automounting worked around this by default by forgoing parallel mounts, or have the facilities to be instructed to do so. -- 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/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: New Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365485/+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 1365485] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1365485 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365485/+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 1365485] Re: Kernel BUG with multiple NFS4 kerberos mounts on boot
apport information ** Tags added: apport-collected ** Description changed: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs-utils: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1046762 - We will fix this by removing the NFS mounts from fstab and doing them - sequentially in startup scripts, but it would be nice if the kernel race - would be fixed too. + We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. + --- + ApportVersion: 2.14.1-0ubuntu3.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lightdm2698 F pulseaudio + /dev/snd/seq:timidity 2607 F timidity + CRDA: Error: [Errno 2] No such file or directory + CurrentDmesg: + [ 23.980615] init: gdm main process (1881) killed by TERM signal + [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning + [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 + [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning + [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC + Package: linux (not installed) + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not
[Kernel-packages] [Bug 1365485] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195381/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash vt.handoff=7
[Kernel-packages] [Bug 1365485] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195383/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash
[Kernel-packages] [Bug 1365485] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195380/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash
[Kernel-packages] [Bug 1365485] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195389/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash
[Kernel-packages] [Bug 1365485] Re: Kernel BUG with multiple NFS4 kerberos mounts on boot
I added the required information from another (identical) host with the same problem. Please ignore it, since the actual hardware used is not really relevant. We can reproduce this in other hardware too. This happens in classroom installations in University of Helsinki and has been going on for at least two years. -- 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/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not
[Kernel-packages] [Bug 1358647] Re: [Dell XPS 12-9Q33] suspend/resume failure
Not sure, because the laptop never slept by itself, just monitor in energy save. Sleep is only forced by lid down or pm-suspend. tl;dr: unsure -- 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/1358647 Title: [Dell XPS 12-9Q33] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Entering sleep mode by itself, and then resuming, the usb3 boot device wasn't located by the kernel (recurring message of directory block 0 not found). WORKAROUND: Execute at a terminal: pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-9-generic 3.16.0-9.14 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: erik 2123 F pulseaudio /dev/snd/controlC0: erik 2123 F pulseaudio Date: Tue Aug 19 09:29:38 2014 DuplicateSignature: suspend/resume:Dell Inc. XPS 12-9Q33:A06 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-02-22 (177 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-9-generic root=UUID=6c8159b5-1d49-4e08-8023-42cfb13a5ebf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-9-generic N/A linux-backports-modules-3.16.0-9-generic N/A linux-firmware1.132 SourcePackage: linux Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure UpgradeStatus: Upgraded to utopic on 2014-07-02 (47 days ago) UserGroups: dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358647/+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 1365485] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195388/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash vt.handoff=7
[Kernel-packages] [Bug 1365485] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195386/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash
[Kernel-packages] [Bug 1365485] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195387/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash vt.handoff=7
[Kernel-packages] [Bug 1365485] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195385/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash
[Kernel-packages] [Bug 1365485] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1365485/+attachment/4195384/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status 1 [ 25.402298] init: plymouth-upstart-bridge main process ended, respawning [ 27.805918] init: plymouth-stop pre-start process (2612) terminated with status 1 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c7fe0bc6-4712-4a0e-9f10-9ade6280a12e IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=268aac80-328a-4ab2-9e21-f38b9897ba79 ro adhome quiet splash
[Kernel-packages] [Bug 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels
Perfect. I'll dig into upstream changes to provide another built kernel based on -stable version. Let you all know soon. Tks -Rafael -- 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/1221995 Title: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: Bluetooth device stopped working. Device support regression. Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6 Testcase: Comment #10 Original Description: Bluetooth device stopped working after upgrading ubuntu to 13.10. ~$ lsusb: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) ~$ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:10:00:0F:46 ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:457 acl:0 sco:0 events:16 errors:0 TX bytes:68 acl:0 sco:0 commands:16 errors:0 ~$ hcitool dev Devices: device simply doesnt appear on bluetooth manager. blueman UI is broken. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jorge 1954 F pulseaudio /dev/snd/controlC0: jorge 1954 F pulseaudio Date: Fri Sep 6 22:32:45 2013 HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MEGAWARE MW-H61M-2H MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 MW dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MW-H61M-2H dmi.board.vendor: MEGAWARE dmi.board.version: v1.3 - 17/07/2012 - MWX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MW-H61M-2H dmi.product.version: v1.3 - 17/07/2012 - MWX dmi.sys.vendor: MEGAWARE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995/+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 1358153] Re: Keyboard and touchpad randomly crash after boot
apport information ** Tags added: apport-collected ** Description changed: After the OS boots, the keyboard and the touchpad crash and I cannot even type my password to log in. This bug is a quite old one, and present in multiple distributions, so I think it might be a kernel bug, but I am not sure. The OS itself doesn't freeze, I can use a mouse instead of the touchpad, and if I had an external USB keyboard, it would work also. One more thing: when this problem occurs, I cannot simply reboot or turn off the machine by selecting the appropriate option from the system menu, because this way the system hangs with a black screen. I can turn off only by pressing the power-off button. - I am using Ubuntu 14.04 with this kernel: Ubuntu 3.13.0-32.57-generic - 3.13.11.4 + I am using Ubuntu 14.04 with this kernel: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + --- + ApportVersion: 2.14.1-0ubuntu3.3 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-08-29 (5 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) + Package: linux (not installed) + Tags: trusty + Uname: Linux 3.17.0-031700rc3-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1358153/+attachment/4195414/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1358153 Title: Keyboard and touchpad randomly crash after boot Status in “linux” package in Ubuntu: Incomplete Bug description: After the OS boots, the keyboard and the touchpad crash and I cannot even type my password to log in. This bug is a quite old one, and present in multiple distributions, so I think it might be a kernel bug, but I am not sure. The OS itself doesn't freeze, I can use a mouse instead of the touchpad, and if I had an external USB keyboard, it would work also. One more thing: when this problem occurs, I cannot simply reboot or turn off the machine by selecting the appropriate option from the system menu, because this way the system hangs with a black screen. I can turn off only by pressing the power-off button. I am using Ubuntu 14.04 with this kernel: Ubuntu 3.13.0-32.57-generic 3.13.11.4 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-08-29 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: linux (not installed) Tags: trusty Uname: Linux 3.17.0-031700rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358153/+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 1365378] Re: [Regression] realtek pci-e card readers don't recognize mmc cards
** Also affects: linux (Ubuntu Utopic) Importance: High Assignee: Adam Lee (adam8157) Status: In Progress ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: In Progress = Fix Released ** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Adam Lee (adam8157) ** Changed in: linux (Ubuntu Utopic) Assignee: Adam Lee (adam8157) = (unassigned) -- 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/1365378 Title: [Regression] realtek pci-e card readers don't recognize mmc cards Status in HWE Next Project: New Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: It's a regression introduced by a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) from v3.13, only trusty is affected. This commit could fix it: From 5027251eced6e34315a52bd841279df957f627bb Mon Sep 17 00:00:00 2001 From: Micky Ching micky_ch...@realsil.com.cn Date: Thu, 27 Mar 2014 13:35:04 +0800 Subject: [PATCH] mmc: rtsx: add R1-no-CRC mmc command type handle a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) produced a cmd.flags unhandled in realtek pci host driver. This will make MMC card fail to initialize, this patch is used to handle the new cmd.flags condition and MMC card can be used. Signed-off-by: Micky Ching micky_ch...@realsil.com.cn Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Signed-off-by: Chris Ball ch...@printf.net --- drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++ 1 file changed, 3 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1365378/+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 1358153] Re: Keyboard and touchpad randomly crash after boot
Sorry for not sending this apport information earlier, but I had to wait for the bug to 'happen'. As I wrote in the title, it happens randomly. But now, I figured out that it happens always if I wait enough. If I wait for everything to load before logging in, then the keyboard and touchpad freeze. If I quickly touch the touchpad or start to type just after the login screen appears, then they won't crash. I hope that it helps something. ** 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/1358153 Title: Keyboard and touchpad randomly crash after boot Status in “linux” package in Ubuntu: Confirmed Bug description: After the OS boots, the keyboard and the touchpad crash and I cannot even type my password to log in. This bug is a quite old one, and present in multiple distributions, so I think it might be a kernel bug, but I am not sure. The OS itself doesn't freeze, I can use a mouse instead of the touchpad, and if I had an external USB keyboard, it would work also. One more thing: when this problem occurs, I cannot simply reboot or turn off the machine by selecting the appropriate option from the system menu, because this way the system hangs with a black screen. I can turn off only by pressing the power-off button. I am using Ubuntu 14.04 with this kernel: Ubuntu 3.13.0-32.57-generic 3.13.11.4 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-08-29 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: linux (not installed) Tags: trusty Uname: Linux 3.17.0-031700rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358153/+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 1354313] Re: [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13)
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Utopic) Importance: Undecided Assignee: Edward Lin (airken) Status: Fix Committed ** Changed in: linux (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: Fix Committed = Invalid ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux-lts-trusty (Ubuntu Precise) Assignee: (unassigned) = Edward Lin (airken) ** Changed in: linux-lts-trusty (Ubuntu Utopic) Assignee: Edward Lin (airken) = (unassigned) ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Edward Lin (airken) -- 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/1354313 Title: [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13) Status in HWE Next Project: Triaged Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-trusty” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: Fix Committed Status in “linux” source package in Trusty: Fix Committed Status in “linux-lts-trusty” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-lts-trusty” source package in Utopic: Invalid Bug description: This is a system installed with latest stable 12.04.5 image. The Brightness key will invoke the osd-notify indicator but the display brightness won't change. Verifying the value changing in backlight interface, system are using acpi_video0 instead: Steps to monitor the backlight interfaces: Press the brightness key until maxium indicator shows: ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; cat acpi_video0/brightness 3407 99 ubuntu@201210-11863:/sys/class/backlight$ Press the brightness key until to minimum indicator shows: ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; cat acpi_video0/brightness 3407 0 - The workaround found here could solve this issue: http://itsfoss.com/fix-brightness-ubuntu-1310/ - Verified with other kernels: linux-image-generic 3.2.0.67.79 = brightness control works linux-image-generic-lts-quantal 3.5.0.54.59 = brightness control works There is possible regression in following kernels: linux-image-generic-lts-raring 3.8.0.44.44 = brightness control not work linux-image-generic-lts-saucy 3.11.0.26.23 = brightness control not work - ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Fri Aug 8 03:51:43 2014 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05ba] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev ff) (prog-if ff) InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MachineType: Dell Inc. Inspiron 5721 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=93a24f68-72a1-4335-938a-75f624f57e68 ro quiet splash initcall_debug vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013
[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at Switched to clocksource tsc when booting up, then resumes booting to the login screen, after 1 minute
Unfortunately, none of the workarounds works on my system. On top of that, the boot stops at Switched to clocksource tsc forever. I can't even boot a Live-Cd. -- 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/1308264 Title: Ubuntu 14.04 Beta 2 stuck at Switched to clocksource tsc when booting up, then resumes booting to the login screen, after 1 minute Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at Switched to clocksource tsc for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+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 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels
Kedar: Could you test the following kernel: Ubuntu-lts-3.16.0-12.17 (lts-backport-utopic for Trusty) and see if fixes the issue ? Easier for me to cherry-pick something that was already fixed for Utopic. Thank you! -Rafael -- 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/1221995 Title: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: Bluetooth device stopped working. Device support regression. Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6 Testcase: Comment #10 Original Description: Bluetooth device stopped working after upgrading ubuntu to 13.10. ~$ lsusb: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) ~$ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:10:00:0F:46 ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:457 acl:0 sco:0 events:16 errors:0 TX bytes:68 acl:0 sco:0 commands:16 errors:0 ~$ hcitool dev Devices: device simply doesnt appear on bluetooth manager. blueman UI is broken. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jorge 1954 F pulseaudio /dev/snd/controlC0: jorge 1954 F pulseaudio Date: Fri Sep 6 22:32:45 2013 HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MEGAWARE MW-H61M-2H MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 MW dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MW-H61M-2H dmi.board.vendor: MEGAWARE dmi.board.version: v1.3 - 17/07/2012 - MWX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MW-H61M-2H dmi.product.version: v1.3 - 17/07/2012 - MWX dmi.sys.vendor: MEGAWARE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995/+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 1364333] Re: Num lock LED doesn't light up while Num lock state is on.
Sorry, tested again on Linux ubuntu 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux. System was booted with Num lock off, real is off too. In virtual terminals Num lock was off and LED was off. But, when i enabled Num lock at desktop and switched to terminal, i got enabled LED, and disabled Num lock. -- 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/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Incomplete Bug description: With my PS/2 A4 Tech keyboard, Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic and v3.17-rc3-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364333/+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 1365378] Re: [Regression] realtek pci-e card readers don't recognize mmc cards
** Changed in: linux (Ubuntu Trusty) Importance: Undecided = High ** Changed in: hwe-next Importance: Undecided = High ** Changed in: hwe-next Assignee: (unassigned) = Adam Lee (adam8157) -- 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/1365378 Title: [Regression] realtek pci-e card readers don't recognize mmc cards Status in HWE Next Project: New Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: It's a regression introduced by a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) from v3.13, only trusty is affected. This commit could fix it: From 5027251eced6e34315a52bd841279df957f627bb Mon Sep 17 00:00:00 2001 From: Micky Ching micky_ch...@realsil.com.cn Date: Thu, 27 Mar 2014 13:35:04 +0800 Subject: [PATCH] mmc: rtsx: add R1-no-CRC mmc command type handle a27fbf2f067b0cd (mmc: add ignorance case for CMD13 CRC error) produced a cmd.flags unhandled in realtek pci host driver. This will make MMC card fail to initialize, this patch is used to handle the new cmd.flags condition and MMC card can be used. Signed-off-by: Micky Ching micky_ch...@realsil.com.cn Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Signed-off-by: Chris Ball ch...@printf.net --- drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++ 1 file changed, 3 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1365378/+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 1358921] Re: [Acer AO 751h] Laptop requires a hard reset to recover from suspend state
I've updated the BIOS as indicated, but nothing changed: When I suspend the netbook, closing the lid, fom the exit menu option or typing sudo pm-suspend, the netbook become suspended (no activity, power button blinking) but there are no way to resume it again: neither pressing a key, neither pressing power button. Even holding the power button pressed down by more or 4 seconds nothing change (the netbook do not become to power-off state). the only way to use the system again is removing the battery and starting again. The output of the commands: V0.3212 02/26/2010 Thanks! ** 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/1358921 Title: [Acer AO 751h] Laptop requires a hard reset to recover from suspend state Status in “linux” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04.1 LTS Release: 14.04 Since update to Lubuntu 14.04.1 from lubuntu 13.10, the laptop is not able to resume from suspend anymore. I've checked this happens runing lubuntu 14.04.01 LiveCD too (but not with the LiveCD of previous version of Lubuntu). If I start the OS with the previous kernel 3.11.0-26 I have not the problem. But starting with kernel 3.13.0-32 or 3.13.0-34 it is there. If I suspend the laptop closing the lid, or from the menu, pressing the power button (to show the exit menu) or running sudo pm-suspend, the laptop get suspended, the screen will off, and the power button led blinks as expected. But then it is not possible to awake again neither pressing a key or pressing the power button. If in that state I try to power off keeping pressed the power button, that still does not work: the blink led still blinks and nothing happens. The only way to recover the system is removing the battery and turning on again. That I expect: After suspend the laptop, I am able to resume it again, just pressing a key, or pressing the power button. I've tried starting with acpi_osi=linux but didn't help. (anyway, that was not necessary with the previous kernel/OS version). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No existe el archivo o el directorio: 'iw' CurrentDesktop: LXDE Date: Tue Aug 19 22:26:06 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=25620b94-5943-42f1-8b93-c4922fd4ceb1 Lsusb: Bus 001 Device 002: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO751h ProcFB: 0 psbdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=0e9dd9a1-128b-47a7-bd68-575ef7fb2073 ro quiet splash acpi_osi=linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2009 dmi.bios.vendor: Acer dmi.bios.version: V0.3202 dmi.board.name: JV11-ML dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV0.3202:bd04/27/2009:svnAcer:pnAO751h:pvrNotApplicable:rvnAcer:rnJV11-ML:rvrNotApplicable:cvnAcer:ct1:cvrN/A: dmi.product.name: AO751h dmi.product.version: Not Applicable dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358921/+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 1354349] Re: trusty crash (7.0.3 based) can't support arm64
** Summary changed: - trusty crash(7.0.3 based) can't support arm64 + trusty crash (7.0.3 based) can't support arm64 ** Tags added: trusty ** Summary changed: - trusty crash (7.0.3 based) can't support arm64 + Crash utility doesn't support arm64 architecture ** Summary changed: - Crash utility doesn't support arm64 architecture + The crash reporting utility doesn't support arm64 architecture ** Tags added: utopic ** Summary changed: - The crash reporting utility doesn't support arm64 architecture + The crash reporting utility doesn't support the arm64 architecture ** Summary changed: - The crash reporting utility doesn't support the arm64 architecture + The Crash utility doesn't support the arm64 architecture -- 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/1354349 Title: The Crash utility doesn't support the arm64 architecture Status in “crash” package in Ubuntu: New Bug description: After investigation, looks VTOP() works mistakenly in current trusty crash on arm64. With the commit below, crash starts to working on arm64, and it can be applied cleanly on trusty crash, so could you guys merge it? https://github.com/crash- utility/crash/commit/0f6d989aa091a97e979ea01fb15e05cc22673de7 Updated the ARM64 implementation to support Linux 3.13 and later kernels that expand to a 42-bit address space when 64K pages are configured. This is also the first crash version that has been tested on a live ARM64 system with 4K pages, where it cleanly make it to the crash prompt. However, it should be noted that some commands (most notably bt) still do not work as of yet. (ander...@redhat.com) [Impact] crash package in trusty can't be used on arm64 [Test Case] just run crash on arm64 box [Regression Potential] the change is arm64-only related, so no potential regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1354349/+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 1365052] Re: linux: 3.13.0-36.63 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- 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/1365052 Title: linux: 3.13.0-36.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 Trusty: New Bug description: This bug is for tracking the 3.13.0-36.63 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-Prepare-package-start:Wednesday, 03. September 2014 16:10 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Thursday, 04. September 2014 05:07 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 05:07 UTC ppa-package-testing-start:Thursday, 04. September 2014 05:07 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1365052/+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 1364208] Re: linux: 3.2.0-69.103 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- 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/1364208 Title: linux: 3.2.0-69.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 Precise: New Bug description: This bug is for tracking the 3.2.0-69.103 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-Prepare-package-start:Tuesday, 02. September 2014 03:28 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 09:08 UTC ppa-package-testing-start:Tuesday, 02. September 2014 09:08 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364208/+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 1305371] Re: [Dell Inspiron 1525] suspend/resume failure
*** This bug is a duplicate of bug 1331654 *** https://bugs.launchpad.net/bugs/1331654 I will try. I do not know what you mean by the default Ubuntu kernel vs. mainline one. Also, I realized that the Ubuntu OS is having several problems at once despite clean install. Can u advise? Thanks Peter -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Christopher M. Penalver Sent: Wednesday, September 03, 2014 10:13 PM To: famil...@sbcglobal.net Subject: [Bug 1305371] Re: [Dell Inspiron 1525] suspend/resume failure *** This bug is a duplicate of bug 1331654 *** https://bugs.launchpad.net/bugs/1331654 Noobinit, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. As well, please do not announce in this report you created a new bug report. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1305371 Title: [Dell Inspiron 1525] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: suspend/resume failed. restart required to bring back system ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ashraf 1484 F pulseaudio Date: Thu Apr 10 06:30:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=f4caffe3-3165-417b-bd56-386b8e3852b8 InstallationDate: Installed on 2014-03-29 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Inspiron 1525 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=26592a1f-092c-4949-9107-771865219fcd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Dell Inc. Inspiron 1525] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305371/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305371 Title: [Dell Inspiron 1525] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: suspend/resume failed. restart required to bring back system ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ashraf 1484 F pulseaudio Date: Thu Apr 10 06:30:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=f4caffe3-3165-417b-bd56-386b8e3852b8
[Kernel-packages] [Bug 1364291] Re: linux-armadaxp: 3.2.0-1638.55 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1364291 Title: linux-armadaxp: 3.2.0-1638.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1638.55 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-Prepare-package-start:Tuesday, 02. September 2014 09:04 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 03:01 UTC kernel-stable-Security-signoff-end:Wednesday, 03. September 2014 03:01 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Wednesday, 03. September 2014 05:02 UTC kernel-stable-Prepare-package-end:Wednesday, 03. September 2014 05:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 03. September 2014 05:02 UTC ppa-package-testing-start:Wednesday, 03. September 2014 05:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364291/+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 1354349] Re: The Crash utility doesn't support the arm64 architecture
** Description changed: - After investigation, looks VTOP() works mistakenly in current trusty - crash on arm64. + + HOW TO REPRODUCE + - With the commit below, crash starts to working on arm64, and it can be - applied cleanly on trusty crash, so could you guys merge it? + On an system that uses the ARM64 architecture, run the crash utility. - https://github.com/crash- - utility/crash/commit/0f6d989aa091a97e979ea01fb15e05cc22673de7 + ** + EXPECTED BEHAVIOUR + ** - Updated the ARM64 implementation to support Linux 3.13 and later + - The crash utility to work. - kernels that expand to a 42-bit address space when 64K pages are - configured. This is also the first crash version that has been - tested on a live ARM64 system with 4K pages, where it cleanly - make it to the crash prompt. However, it should be noted that - some commands (most notably bt) still do not work as of yet. - (ander...@redhat.com) + ** + REAL BEHAVIOUR + ** + - The crash utility doesn't work. - [Impact] - crash package in trusty can't be used on arm64 + + PROPOSED FIX + - [Test Case] - just run crash on arm64 box + - To clean merge into Ubuntu the https://github.com/crash- + utility/crash/commit/0f6d989aa091a97e979ea01fb15e05cc22673de7 commit, + which updates the ARM64 implementation to support Linux 3.13 and later. - [Regression Potential] - the change is arm64-only related, so no potential regression + - Since the change only affects the ARM64 architecture, there is no + potential regression. + + + RELEVANT DETAILS + + + - The package's affected versions are the 7.0.6 based. + + - Dave Anderson at + http://people.redhat.com/anderson/crash.changelog.html said that some + commands, most notably bt, don't work yet. ** Summary changed: - The Crash utility doesn't support the arm64 architecture + The crash utility doesn't support the ARM64 architecture ** Summary changed: - The crash utility doesn't support the ARM64 architecture + The crash utility doesn't run in the ARM64 architecture ** Summary changed: - The crash utility doesn't run in the ARM64 architecture + The crash utility doesn't run in ARM64 based devices ** Description changed: HOW TO REPRODUCE On an system that uses the ARM64 architecture, run the crash utility. ** EXPECTED BEHAVIOUR ** - The crash utility to work. ** REAL BEHAVIOUR ** - The crash utility doesn't work. PROPOSED FIX - To clean merge into Ubuntu the https://github.com/crash- utility/crash/commit/0f6d989aa091a97e979ea01fb15e05cc22673de7 commit, which updates the ARM64 implementation to support Linux 3.13 and later. - Since the change only affects the ARM64 architecture, there is no potential regression. RELEVANT DETAILS - - The package's affected versions are the 7.0.6 based. + - The package's affected versions are the 7.0.3 based. - Dave Anderson at http://people.redhat.com/anderson/crash.changelog.html said that some commands, most notably bt, don't work yet. ** Changed in: crash (Ubuntu) Importance: Undecided = High ** Changed in: crash (Ubuntu) Status: New = Triaged -- 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/1354349 Title: The crash utility doesn't run in ARM64 based devices Status in “crash” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE On an system that uses the ARM64 architecture, run the crash utility. ** EXPECTED BEHAVIOUR ** - The crash utility to work. ** REAL BEHAVIOUR ** - The crash utility doesn't work. PROPOSED FIX - To clean merge into Ubuntu the https://github.com/crash- utility/crash/commit/0f6d989aa091a97e979ea01fb15e05cc22673de7 commit, which updates the ARM64 implementation to support Linux 3.13 and later. - Since the change only affects the ARM64 architecture, there is no potential regression. RELEVANT DETAILS - The package's affected versions are the 7.0.3 based. - Dave Anderson at http://people.redhat.com/anderson/crash.changelog.html said that some commands, most notably bt, don't work yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1354349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1354397] Re: Latest fixes from storvsc scsi drivers for Hyper-V/Azure
Thanks Andy, The new kernel images for Ubuntu 1404 are booting without any issues. We will report back with any issues once complete testing is done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354397 Title: Latest fixes from storvsc scsi drivers for Hyper-V/Azure Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress Bug description: A number of significant fixes have landed upstream for Hyper-V/Azure clouds. The upstream devs for this recommend we apply the below list of patches: commit 26b9fd8b3452dcf0a8862e307ee23f442f63fb51 Author: K. Y. Srinivasan k...@microsoft.com Date: Fri Jul 18 17:11:27 2014 +0200 sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O timeout commit 4cd83ecdac20d30725b4f96e5d7814a1e290bc7e Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:26 2014 -0700 Drivers: scsi: storvsc: Change the limits to reflect the values on the host commit 52f9614dd8294e95d2c0929c2d4f64b077ae486f Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:27 2014 -0700 Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported by the Host commit 8caf92d80526f3d7cc96831ec18b384ebcaccdf0 Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:28 2014 -0700 Drivers: scsi: storvsc: Filter commands based on the storage protocol version commit adb6f9e1a8c6af1037232b59edb11277471537ea Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:29 2014 -0700 Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol version commit 56b26e69c8283121febedd12b3cc193384af46b9 Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:30 2014 -0700 Drivers: scsi: storvsc: Implement a eh_timed_out handler commit f885fb73f64154690c2158e813de56363389ffec Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:31 2014 -0700 drivers: scsi: storvsc: Set srb_flags in all cases commit 3533f8603d28b77c62d75ec899449a99bc6b77a1 Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:32 2014 -0700 drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure commit f3cfabce7a2e92564d380de3aad4b43901fb7ae6 Author: K. Y. Srinivasan k...@microsoft.com Date: Mon Jul 21 16:06:01 2014 -0700 Drivers: add blist flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354397/+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 1365593] [NEW] No driver provided for X-Gene's hardware RNG
Public bug reported: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365593 Title: No driver provided for X-Gene's hardware RNG Status in “linux” package in Ubuntu: New Bug description: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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 1349282] Re: The gpu-manager should allow RandR offloading without bbswitch
Hello Alberto, or anyone else affected, Accepted ubuntu-drivers-common into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source /ubuntu-drivers-common/1:0.2.91.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ubuntu-drivers-common (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1349282 Title: The gpu-manager should allow RandR offloading without bbswitch Status in “nvidia-settings” package in Ubuntu: Triaged Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “nvidia-settings” source package in Trusty: Triaged Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: SRU Request While bbswitch may fail on some hybrid systems (e.g. on the desktop or when the bbswitch module fails to build), this is not a good reason to prevent the system from offloading rendering to the NVIDIA GPU. [Impact] * This problem makes it impossible to use the NVIDIA GPU on hybrid systems with Intel+NVIDIA GPUs when bbswitch is not available (i.e. when it fails to load). [Test Case] * Make sure to be using a hybrid system with Intel+NVIDIA GPUs. * Check that bbswitch is not available. You can do so by posting output of the following command: test -e /proc/acpi/bbswitch echo true || echo false * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Install ubuntu-drivers-common from trusty-proposed. * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Restart the system. * Install the nvidia binary driver, reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the NVIDIA discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A --- The gpu-manager should allow RandR offloading without bbswitch. This would allow desktop systems to make use of offloading even when bbswitch is not supported. Also, nvidia-settings should not complain in such scenarios. See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1310023/comments/70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1349282/+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 1362168] Re: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn
I've tried to install the first of your list, but it doesn't go. the version downloaded was the latest, linux-headers-3.17.0-031700rc2-generic_3.17.0-031700rc2.201408251935_i386.deb I've put it in a new directory, called headers317 but this is the response to command dpkg-i: massimo@SONY:~$ cd '/home/massimo/Scaricati/headers317' massimo@SONY:~/Scaricati/headers317$ sudo dpkg -i [sudo] password for massimo: dpkg: errore: --install richiede almeno un archivio di pacchetto come argomento Usare dpkg --help per un aiuto sull'installazione e la rimozione dei pacchetti [*]. Usare apt o aptitude per un'interfaccia alla gestione dei pacchetti. Usare dpkg -Dhelp per l'elenco delle opzioni di debug per dpkg. Usare dpkg --force-help per l'elenco delle opzioni di forzatura. Usare dpkg-deb --help per un aiuto sulla manipolazione dei file *.deb. Le opzioni indicate con [*] producono output prolisso - creare una pipe con less o more. massimo@SONY:~/Scaricati/headers317 I need some other help, please: maybe I am in error when I try to launch the command: A guide step by step could be helpful. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in webforum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47t=522361p=4634264hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1365485] Re: Kernel BUG with multiple NFS4 kerberos mounts on boot
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc3-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: kernel-da-key -- 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/1365485 Title: Kernel BUG with multiple NFS4 kerberos mounts on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Currently latest Ubuntu Linux kernel image has a a bug, probably a race condition, which happens when there are multiple kerberos nfs4 mounts in /etc/fstab. This does not happen on every boot, so to reproduce this you probably need a few retries. This happens using the current Ubuntu Linux kernel in 14.04: # cat /proc/version_signature Ubuntu 3.13.0-35.62-generic 3.13.11.6 Apparently you need to have _multiple_ kerberos NFS4 mounts in /etc/fstab to trigger this: xx.helsinki.fi:/root_vdm_3/fshome1/u1 /home/ad/fshome1/u1 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome2/u2 /home/ad/fshome2/u2 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome3/u3 /home/ad/fshome3/u3 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome4/u4 /home/ad/fshome4/u4 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome5/u5 /home/ad/fshome5/u5 nfs4 sec=krb5,rw,bg,hard 0 0 xx.helsinki.fi:/root_vdm_3/fshome6/u6 /home/ad/fshome6/u6 nfs4 sec=krb5,rw,bg,hard 0 0 When this happens we get a kernel stack trace (complete trace included), which starts like this: [ 19.999751] gss_pipe_downcall: bad return from gss_fill_context: -4 [ 19.999779] [ cut here ] [ 19.999791] kernel BUG at /build/buildd/linux-3.13.0/net/sunrpc/auth_gss/auth_gss.c:735! [ 19.999796] invalid opcode: [#1] SMP [ 19.999802] Modules linked in: arc4(+) des_generic cmac xcbc nfsv4 rmd160 crypto_null af_key xfrm_algo dm_crypt snd_hda_codec_realtek gpio_ich hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi coretemp dm_multipath snd_seq kvm_intel scsi_dh kvm snd_seq_device bnep serio_raw rfcomm snd_timer bluetooth lpc_ich snd soundcore tpm_infineon mei_me mei mac_hid parport_pc ppdev lp parport binfmt_misc rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_mirror dm_region_hash dm_log hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm e1000e drm_kms_helper ahci psmouse libahci drm wmi ptp pps_core When this has happened, rpc.gssd gets stuck in D state: # ps aux|grep gssd root 452 0.0 0.0 0 0 ?Ds 13:18 0:00 [rpc.gssd] Also NFS4 mounts will fail, with an error message which does not tell what is actually going on: root@do0-kukad211-07:~# mount -a -t nfs4 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome1/u1 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome2/u2 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome3/u3 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome4/u4 mount.nfs4: access denied by server while mounting ..helsinki.fi:/root_vdm_3/fshome5/u5 mount.nfs4: access denied by server while mounting .helsinki.fi:/root_vdm_3/fshome6/u6 This also happened on Ubuntu 12.04, so the bug is probably old. There is a bug report, which is (IMHO) incorrectly reported against nfs- utils: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1046762 We will fix this by removing the NFS mounts from fstab and doing them sequentially in startup scripts, but it would be nice if the kernel race would be fixed too. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm2698 F pulseaudio /dev/snd/seq:timidity 2607 F timidity CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 23.980615] init: gdm main process (1881) killed by TERM signal [ 25.395448] init: plymouth-upstart-bridge main process ended, respawning [ 25.402287] init: plymouth-upstart-bridge main process (2248) terminated with status
[Kernel-packages] [Bug 1365593] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1365593 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/1365593 Title: No driver provided for X-Gene's hardware RNG Status in “linux” package in Ubuntu: Incomplete Bug description: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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 1364290] Re: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1364290 Title: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New 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 upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled 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-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Wednesday, 03. September 2014 15:01 UTC kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 15:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364290/+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 1349282] Re: The gpu-manager should allow RandR offloading without bbswitch
** Branch linked: lp:ubuntu/trusty-proposed/ubuntu-drivers-common -- 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/1349282 Title: The gpu-manager should allow RandR offloading without bbswitch Status in “nvidia-settings” package in Ubuntu: Triaged Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “nvidia-settings” source package in Trusty: Triaged Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: SRU Request While bbswitch may fail on some hybrid systems (e.g. on the desktop or when the bbswitch module fails to build), this is not a good reason to prevent the system from offloading rendering to the NVIDIA GPU. [Impact] * This problem makes it impossible to use the NVIDIA GPU on hybrid systems with Intel+NVIDIA GPUs when bbswitch is not available (i.e. when it fails to load). [Test Case] * Make sure to be using a hybrid system with Intel+NVIDIA GPUs. * Check that bbswitch is not available. You can do so by posting output of the following command: test -e /proc/acpi/bbswitch echo true || echo false * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Install ubuntu-drivers-common from trusty-proposed. * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Restart the system. * Install the nvidia binary driver, reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the NVIDIA discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A --- The gpu-manager should allow RandR offloading without bbswitch. This would allow desktop systems to make use of offloading even when bbswitch is not supported. Also, nvidia-settings should not complain in such scenarios. See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1310023/comments/70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1349282/+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 1365593] Re: No driver provided for X-Gene's hardware RNG
Is this an issue with all Ubuntu releases including Utopic? ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: kernel-da-key -- 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/1365593 Title: No driver provided for X-Gene's hardware RNG Status in “linux” package in Ubuntu: Confirmed Bug description: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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 1354710] Re: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570
We can also perform a kernel bisect to identify the commit that introduced this regression in 3.10. Would you be able to test 7 - 10 kernel for the bisect process? ** Tags removed: needs-bisect ** Tags added: performing-bisect -- 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/1354710 Title: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570 Status in “linux” package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo B570 package version: Ubuntu 3.13.0-32.57-generic 3.13.11.4 I expected the keys for changeing the backlight brightness to work they had no effect on the backlight further details in attatched Tar ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: x321x321 1977 F pulseaudio Date: Sat Aug 9 16:11:34 2014 HibernationDevice: RESUME=UUID=61c2c6a6-4b45-4af0-941a-dadf05ad0aba InstallationDate: Installed on 2014-07-31 (8 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140723) MachineType: LENOVO 1068FJG ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN36WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN36WW:bd07/11/2011:svnLENOVO:pn1068FJG:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 1068FJG dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354710/+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 1354710] Re: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354710 Title: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570 Status in “linux” package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo B570 package version: Ubuntu 3.13.0-32.57-generic 3.13.11.4 I expected the keys for changeing the backlight brightness to work they had no effect on the backlight further details in attatched Tar ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: x321x321 1977 F pulseaudio Date: Sat Aug 9 16:11:34 2014 HibernationDevice: RESUME=UUID=61c2c6a6-4b45-4af0-941a-dadf05ad0aba InstallationDate: Installed on 2014-07-31 (8 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140723) MachineType: LENOVO 1068FJG ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN36WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN36WW:bd07/11/2011:svnLENOVO:pn1068FJG:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 1068FJG dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354710/+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 1355196] Re: compiz fails with intel_do_flush_locked failed: Invalid argument
Looks like its this https://bugzilla.kernel.org/show_bug.cgi?id=82481 ** Bug watch added: Linux Kernel Bug Tracker #82481 http://bugzilla.kernel.org/show_bug.cgi?id=82481 ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1355196 Title: compiz fails with intel_do_flush_locked failed: Invalid argument Status in “linux” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Bug description: Recent upgrade and reboot/re-login left me with a generally unusable compiz/unity. On login, the desktop icons move back and forth several times, I believe this correlates with ~/.xesssion-errors 'unity main process ended' messages like: upstart: unity7 main process (7477) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (7910) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (7939) terminated with status 1 Further investigation showed that compiz was failing to start. Attempting to start it by hand shows: intel_do_flush_locked failed: Invalid argument Those same messages appear in ~/.cache/upstart/unity7.log. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140731.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Aug 11 09:53:07 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1027 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-05-20 (448 days ago) --- .tmp.unity.support.test.0: ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smoser 4190 F pulseaudio CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2013-05-20 08:14:41,880 DEBUG openCache() DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2011-10-19 (1034 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 7417CTO Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=f9832678-e9fb-41c5-8edb-5edd5200ed0a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 Tags: utopic utopic ubuntu regression reproducible compiz-0.9 Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: Upgraded to utopic on 2013-05-20 (456 days ago) UserGroups: adm admin cdrom dialout fuse kvm libvirtd lpadmin plugdev sambashare sbuild _MarkForUpload: True dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 7417CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7417CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2:
[Kernel-packages] [Bug 1355196] Re: compiz fails with intel_do_flush_locked failed: Invalid argument
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ece4a17d237a79f63fbfaf3f724a12b6d500555c in 3.17-rc1 -- 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/1355196 Title: compiz fails with intel_do_flush_locked failed: Invalid argument Status in “linux” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Bug description: Recent upgrade and reboot/re-login left me with a generally unusable compiz/unity. On login, the desktop icons move back and forth several times, I believe this correlates with ~/.xesssion-errors 'unity main process ended' messages like: upstart: unity7 main process (7477) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (7910) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (7939) terminated with status 1 Further investigation showed that compiz was failing to start. Attempting to start it by hand shows: intel_do_flush_locked failed: Invalid argument Those same messages appear in ~/.cache/upstart/unity7.log. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140731.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Aug 11 09:53:07 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1027 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-05-20 (448 days ago) --- .tmp.unity.support.test.0: ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smoser 4190 F pulseaudio CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2013-05-20 08:14:41,880 DEBUG openCache() DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2011-10-19 (1034 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 7417CTO Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=f9832678-e9fb-41c5-8edb-5edd5200ed0a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 Tags: utopic utopic ubuntu regression reproducible compiz-0.9 Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: Upgraded to utopic on 2013-05-20 (456 days ago) UserGroups: adm admin cdrom dialout fuse kvm libvirtd lpadmin plugdev sambashare sbuild _MarkForUpload: True dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 7417CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7417CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2 version.libgl1-mesa-dri-experimental:
[Kernel-packages] [Bug 1359706] Re: EXT4 file system corruption on ubuntu server 14.04 LTS
** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359706 Title: EXT4 file system corruption on ubuntu server 14.04 LTS Status in “linux” package in Ubuntu: Incomplete Bug description: There was extensive file system corruption triggered by a user (non- root) program consuming all memory. Dmesg contained following messages: [2678426.843981] Out of memory: Kill process 31328 (python) score 983 or sacrifice child [2678426.844151] Killed process 31328 (python) total-vm:60801412kB, anon-rss:60694516kB, file-rss:0kB [2893469.391974] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7865240 (offset 0 size 0 starting block 49231) [2893469.391982] Buffer I/O error on device dm-2, logical block 49231 [2893469.392032] Buffer I/O error on device dm-2, logical block 49232 [2893469.395494] Buffer I/O error on device dm-2, logical block 49233 [2893469.569757] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7864978 (offset 0 size 0 starting block 20808467) [2893469.569762] Buffer I/O error on device dm-2, logical block 20808467 [2893469.569896] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7866610 (offset 0 size 0 starting block 79732436) [2893469.569899] Buffer I/O error on device dm-2, logical block 79732436 [2893469.570176] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7866610 (offset 8192 size 4096 starting block 109098591) [2893469.570180] Buffer I/O error on device dm-2, logical block 109098591 [2893469.707534] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7865240 (offset 0 size 0 starting block 49217) [2893469.707539] Buffer I/O error on device dm-2, logical block 49217 [2893469.707578] Buffer I/O error on device dm-2, logical block 49218 [2893469.707674] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7865240 (offset 0 size 0 starting block 49223) [2893469.707679] Buffer I/O error on device dm-2, logical block 49223 [2893469.707768] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7865240 (offset 0 size 0 starting block 49226) [2893469.707773] Buffer I/O error on device dm-2, logical block 49226 [2893469.707859] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7865240 (offset 0 size 0 starting block 49229) [2893469.707870] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7864600 (offset 0 size 0 starting block 44853) [2893469.707876] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 7864600 (offset 0 size 0 starting block 44858) [2893469.726747] Aborting journal on device dm-2-8. [2893469.768725] init: rsyslog main process (919) killed by BUS signal [2893469.768766] init: rsyslog main process ended, respawning [2893469.867576] Buffer I/O error on device dm-2, logical block 65044480 [2893469.867617] lost page write due to I/O error on dm-2 [2893469.867641] JBD2: Error -5 detected when updating journal superblock for dm-2-8. [2893470.103486] Buffer I/O error on device dm-2, logical block 0 [2893470.103524] lost page write due to I/O error on dm-2 [2893470.103568] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal [2893470.103684] EXT4-fs (dm-2): Remounting filesystem read-only [2893470.103770] EXT4-fs (dm-2): previous I/O error to superblock detected [2893470.197496] Buffer I/O error on device dm-2, logical block 0 [2893470.197584] lost page write due to I/O error on dm-2 [2893470.197720] Core dump to |/usr/share/apport/apport 439 7 0 439 pipe failed [2893470.208395] init: rsyslog pre-start process (439) killed by BUS signal [2893470.378616] Core dump to |/usr/share/apport/apport 442 7 0 442 pipe failed [2893470.380183] init: startpar-bridge (rsyslog--stopped) main process (442) killed by BUS signal [2893511.046711] Core dump to |/usr/share/apport/apport 1421 7 18446744073709551615 1421 pipe failed [2903746.904285] EXT4-fs warning (device dm-1): __ext4_read_dirblock:681: error reading directory block (ino 174523398, block 0) [2903773.782839] Aborting journal on device dm-1-8. [2903773.801696] Buffer I/O error on device dm-1, logical block 1048084480 [2903773.801799] lost page write due to I/O error on dm-1 [2903773.801817] JBD2: Error -5 detected when updating journal superblock for dm-1-8. [2903774.966747] Buffer I/O error on device dm-1, logical block 0 [2903774.968009] lost page write due to I/O error on dm-1 [2903774.968186] EXT4-fs error (device dm-1): ext4_journal_check_start:56: Detected aborted journal [2903774.969608] EXT4-fs (dm-1): Remounting filesystem read-only
[Kernel-packages] [Bug 1363853] Re: [Lenovo ThinkPad X220] suspend/resume failure
Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem. -- 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/1363853 Title: [Lenovo ThinkPad X220] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: No idea what happened. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2818 F pulseaudio Date: Mon Sep 1 09:13:35 2014 DuplicateSignature: suspend/resume:LENOVO 429149G:8DET46WW (1.16 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=e3968bc2-4b49-4bc2-a8f2-485b8cdd957f InstallationDate: Installed on 2013-12-22 (252 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 429149G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-11-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.133 SourcePackage: linux Title: [LENOVO 429149G] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363853/+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 1365593] Re: No driver provided for X-Gene's hardware RNG
On Thu, Sep 4, 2014 at 11:13 AM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Is this an issue with all Ubuntu releases including Utopic? It impacts trusty and utopic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365593 Title: No driver provided for X-Gene's hardware RNG Status in “linux” package in Ubuntu: Confirmed Bug description: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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 1354604] Re: Regression: touchscreen-as-input not recognized in recent kernels (Dell Venue 11 Pro 7130)
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed = Triaged -- 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/1354604 Title: Regression: touchscreen-as-input not recognized in recent kernels (Dell Venue 11 Pro 7130) Status in “linux” package in Ubuntu: Triaged Bug description: Due to bug #1354598, my Dell Venue 11 Pro 7130 tablet is unusable as a tablet with the current Trusty kernel, so I have been attempting to find a more recent kernel for which the screen functions both as a display and a touch input device. No luck so far. (Well, actually, oddly enough, that's not quite true: I installed the 05-Aug-2014 01:21 daily live CD of Kubuntu Active, which is i386 only, and *that* worked just fine, from a kernel/hardware perspective. But I'm hoping to get an amd64 kernel working.) When booting either of the most recent Utopic kernel (3.16.0-6) and the kernel team's latest build of upstream (3.16.0-031600), the touchscreen is unresponsive to touch input, and inspection of the logs confirms that the multitouch device is not recognized as such. Will run apport-collect. Also the udev logs attached to bug #1354598 may be interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354604/+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 1341925] Re: [Dell Inspiron 11 - 3147] System will hang on reboot / poweroff
Adding noapic to the kernel command line enabled shutdown/reboot/suspend/resume for me, but it wouldn't boot reliably. This issue seems to be caused by a buggy driver for the Synopsys Designware I2C DMA controller, which is also used in the HP x360 and various other 2-in-1s and laptops. Blacklisting the dw_dmac kernel module enables shutdown, reboot, and suspend/resume for me on both Arch Linux and Ubuntu 14.10, but my fix should work on 14.04 and presumably other distros/versions as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1341925 Title: [Dell Inspiron 11 - 3147] System will hang on reboot / poweroff Status in HWE Next Project: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201403-14888 Dell Inspiron 11 - 3147 While rebooting this system, it will stuck on the Ubuntu splash screen, caps lock LED will be not responding. This issue happens right after 14.04 installation with USB stick. If you press F1 right after the Ubuntu splash screen appears, you will see the message indicating it's now rebooting: * Deactivating swap... [OK] * Unmounting local filesystems... [OK] * Will now restart Steps: 1. Install 14.04, reboot to desktop 2. Try to reboot again Expect result: * System could be reboot normally Actual result: * It will stuck on the Ubuntu splash screen, the only way to power it off is to hold the power button Same thing could be apply to Shut Down * Unmounting local filesystems... [OK] * Will now halt ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1431 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Mon Jul 14 22:25:58 2014 HibernationDevice: RESUME=UUID=b30f45e9-6fc7-4aa0-adff-37e7c87c19cd InstallationDate: Installed on 2014-07-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 11 - 3147 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=cc246aa9-85c1-49ac-b06b-6c0f4e37dbea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 00K010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/05/2014:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn00K010:rvrD02:cvnDellInc.:ct8:cvrA01: dmi.product.name: Inspiron 11 - 3147 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1341925/+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 1346096] Re: [drm:init_ring_common] *ERROR* render ring initialization failed
*** This bug is a duplicate of bug 1355196 *** https://bugs.launchpad.net/bugs/1355196 ** This bug has been marked a duplicate of bug 1355196 compiz fails with intel_do_flush_locked failed: Invalid argument -- 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/1346096 Title: [drm:init_ring_common] *ERROR* render ring initialization failed Status in “linux” package in Ubuntu: Fix Released Bug description: After last apt-get dist-upgrade my computer can not start with a graphic environment. It start but it's freeze in login screen (cursor blink not blink, it's all screen locked). I only can login into my Ubuntu from Grub Advanced options resume. Computer: Toshiba Satellite Pro U400-182 with Intel graphic card (Intel GM45 Chipset). Ubuntu version: Ubuntu 14.10 Utopic Unicorn (development branch) Kernel: Linux 3.16.0-4-generic #9-Ubuntu SMP Mon Jul 14 11:55:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Error in syslog is: Jul 18 11:00:14 lito-Ubuntu kernel: [2.420468] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 (valid? 1) head 0304 tail start 00503000 [expected 00503000] Jul 18 11:00:14 lito-Ubuntu kernel: [2.420478] [drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged Xorg log: [11.900] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [11.901] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000 [11.901] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100 [11.901] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200 [11.901] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [11.901] (II) FBDEV: driver for framebuffer: fbdev [11.901] (II) VESA: driver for VESA chipsets: vesa [11.901] (++) using VT number 7 [11.927] (EE) open /dev/dri/card0: No such file or directory [11.927] (WW) Falling back to old probe method for modesetting [11.927] (EE) open /dev/dri/card0: No such file or directory No errors in dmesg Related intel packages: ii intel-gpu-tools1.7-1amd64tools for debugging the Intel graphics driver ii libdrm-intel1:amd642.4.54-1 amd64Userspace interface to intel-specific kernel DRM ii libdrm-intel1:i386 2.4.54-1 i386 Userspace interface to intel-specific kernel DRM un libva-intel-vaapi-driv none none (no description available) ii xserver-xorg-video-int 2:2.99.910-0ubun amd64X.Org X server -- Intel i8xx, i9xx display driver Thanks in advance. --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lito 5855 F...m pulseaudio /dev/snd/pcmC0D0p: lito 5855 F...m pulseaudio /dev/snd/controlC0: lito 5855 F pulseaudio /dev/snd/seq:timidity 3621 F timidity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=fca42103-06f9-4fcd-bbca-9e8aba068dad InstallationDate: Installed on 2012-07-10 (740 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: TOSHIBA Satellite Pro U400 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-generic root=UUID=3a477584-a099-4e62-879e-855c5aed40c3 ro recovery nomodeset ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-4-generic N/A linux-backports-modules-3.16.0-4-generic N/A linux-firmware1.132 Tags: utopic Uname: Linux 3.16.0-4-generic x86_64 UpgradeStatus: Upgraded to utopic on 2013-10-16 (277 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/26/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V5.00 dmi.board.name: Satellite Pro U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1339939] Re: [Lenovo ThinkPad T400] intel graphics fail after suspend with 3.16 kernel
*** This bug is a duplicate of bug 1355196 *** https://bugs.launchpad.net/bugs/1355196 ** This bug has been marked a duplicate of bug 1355196 compiz fails with intel_do_flush_locked failed: Invalid argument -- 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/1339939 Title: [Lenovo ThinkPad T400] intel graphics fail after suspend with 3.16 kernel Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: After resuming from suspend, I find gnome-shell has crashed. If I try to restart gnome-shell or gdm after this all I get is the following message. Everything does work fine on initial boot up until I suspend. intel_do_flush_locked failed: Invalid argument Booting on the 3.13 kernel from trusty, this problem does not occur. I also tried to test utopic dailly Ubuntu GNOME, this fails to even boot too gdm, unless I set nomodeset from the kernel line. I have never need to do this in the past though. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darkness 2770 F pulseaudio CurrentDesktop: GNOME Date: Thu Jul 10 10:04:38 2014 HibernationDevice: RESUME=UUID=80ccdbf4-2eec-47cd-aac0-5d90ab898481 MachineType: LENOVO 2764CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=70836e80-816b-424b-8aaf-6a0d2863fa50 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-01-05 (185 days ago) dmi.bios.date: 02/13/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET61WW (2.07 ) dmi.board.name: 2764CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET61WW(2.07):bd02/13/2009:svnLENOVO:pn2764CTO:pvrThinkPadT400:rvnLENOVO:rn2764CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2764CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1339939/+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 1365611] [NEW] linux: 3.16.0-13.19 -proposed tracker
Public bug reported: This bug is for tracking the 3.16.0-13.19 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-Prepare-package-start:Thursday, 04. September 2014 17:42 UTC kernel-phase-changed:Thursday, 04. September 2014 17:42 UTC kernel-phase:Prepare ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Tags: kernel-release-tracking-bug utopic ** Tags added: kernel-release-tracking-bug ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Tags added: utopic ** Also affects: kernel-development-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New = In Progress ** Changed in: kernel-development-workflow Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided = Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) = Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365611 Title: linux: 3.16.0-13.19 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-13.19 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-Prepare-package-start:Thursday, 04. September 2014 17:42 UTC kernel-phase-changed:Thursday, 04. September 2014 17:42 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1365611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
Hello, I have an Iogear GBU521 and I'm using Ubuntu 14.04 dmesg | grep -B1 Broadcom [1.439431] usb 3-1: Product: BCM20702A0 [1.439432] usb 3-1: Manufacturer: Broadcom Corp A2DP works fine but I have the same issue(HSP/HFP is not working) no mic or audio I downloaded the *.hcd from comment #120 to /lib/firmware and restarted the PC but nothing have changed. Am I missing something to make it works? -- 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/1065400 Title: Support for loading Broadcom bluetooth firmware Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Released Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetoothm=132039175324993w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)
** Changed in: bluez (Ubuntu Trusty) Status: New = In Progress ** Changed in: gnome-bluetooth (Ubuntu Precise) Status: New = In Progress ** Changed in: gnome-bluetooth (Ubuntu Trusty) Status: New = In Progress ** Changed in: gnome-bluetooth (Ubuntu Precise) Status: In Progress = Triaged ** Changed in: bluez (Ubuntu Precise) Status: New = Triaged ** Changed in: bluez (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: bluez (Ubuntu Trusty) Importance: Undecided = High ** Changed in: gnome-bluetooth (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: gnome-bluetooth (Ubuntu Trusty) Importance: Undecided = High ** Changed in: gnome-bluetooth (Ubuntu Trusty) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Changed in: bluez (Ubuntu Trusty) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- 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/1035431 Title: bluetooh-wizard failed to connect to a keyboard(logitech) Status in GNOME Bluetooth: New Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in “bluez” package in Ubuntu: Fix Released Status in “gnome-bluetooth” package in Ubuntu: Fix Released Status in “bluez” source package in Precise: Triaged Status in “gnome-bluetooth” source package in Precise: Triaged Status in “bluez” source package in Trusty: In Progress Status in “gnome-bluetooth” source package in Trusty: In Progress Bug description: When I try to connect my bluetooth keyboard using bluetooth-wizard, it ever fails: ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760' failed: Authentication Failed This keyboard works fine with another computer under ubuntu 11.04. This keyboard works fine with this computer and Windows 7 (arghhh). This computer ubuntu 12.04 works fine with my bluetooth mouse. I can attach manually this keyboard to this computer using : sudo hidd --search My computer is a Samsung 305U1A My bluetooth interface is : Bus 003 Device 002: ID 0a5c:219c Broadcom Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity
U + 1 forums for last few days a number of people on a variety of hardware booting to black screen or command line or Anything we can do to test anything? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359299 Title: utopic 3.16.0-9 iso boots to desktop no unity Status in Unity: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Confirmed Bug description: Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre. Boots 3.16.0-6 amd64 fine, runs compiz 3D fine. Today's amd64 iso download, 20 August, boots to desktop cursor. No unity. Did ubuntu-bug from command line on the booted iso, saved report. Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file. Planet Ubuntu asked for results on 3.16.0-9 so this is my result. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-9-generic 3.16.0-9.14 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CasperVersion: 1.341 Date: Wed Aug 20 16:57:57 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140820) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359299/+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 1364290] Re: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker
All builds are complete, packages in this bug can be copied to -proposed. ** Changed in: kernel-sru-workflow/prepare-package Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) = Paolo Pisati (p-pisati) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/package-testing Status: In Progress = Confirmed ** Description changed: This bug is for tracking the version to be filled 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-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 - kernel-stable-phase:ReadyToBePackaged - kernel-stable-phase-changed:Wednesday, 03. September 2014 15:01 UTC kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 15:00 UTC + kernel-stable-phase:PPA Testing + kernel-stable-phase-changed:Thursday, 04. September 2014 18:01 UTC + kernel-stable-Prepare-package-end:Thursday, 04. September 2014 18:01 UTC + kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 18:01 UTC + ppa-package-testing-start:Thursday, 04. September 2014 18:01 UTC ** Description changed: This bug is for tracking the version to be filled 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-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 15:00 UTC - kernel-stable-phase:PPA Testing - kernel-stable-phase-changed:Thursday, 04. September 2014 18:01 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 18:01 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 18:01 UTC ppa-package-testing-start:Thursday, 04. September 2014 18:01 UTC + kernel-stable-phase:ReadyToBePackaged + kernel-stable-phase-changed:Thursday, 04. September 2014 18:03 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1364290 Title: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled 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-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 15:00 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 18:01 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 18:01 UTC ppa-package-testing-start:Thursday, 04. September 2014 18:01 UTC kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Thursday, 04. September 2014 18:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364290/+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 1364290] Re: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1364290 Title: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled 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-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 15:00 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 18:01 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 18:01 UTC ppa-package-testing-start:Thursday, 04. September 2014 18:01 UTC kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Thursday, 04. September 2014 18:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364290/+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 1365052] Re: linux: 3.13.0-36.63 -proposed tracker
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone -- 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/1365052 Title: linux: 3.13.0-36.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 Trusty: New Bug description: This bug is for tracking the 3.13.0-36.63 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-Prepare-package-start:Wednesday, 03. September 2014 16:10 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Thursday, 04. September 2014 05:07 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 05:07 UTC ppa-package-testing-start:Thursday, 04. September 2014 05:07 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1365052/+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 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone -- 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/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] Some disk types will never be seen after boot, while others can disappear after a reboot. This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Only affects the the xgene ahci driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+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 1360140] Re: trusty still uses APM's out-of-tree xgene-enet patches
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone -- 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/1360140 Title: trusty still uses APM's out-of-tree xgene-enet patches Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Now all APM's xgene-enet patches are merged to linus tree already, so it is time to replace these out-of-tree patches with upstreamed xgene-enet commits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360140/+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 1362447] Re: CVE-2014-5471
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1362447 Title: CVE-2014-5471 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: [unbound recursion in ISOFS - crashes / reboots a kernel due to kernel stack overflow / corruption] Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362447/+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
