[Kernel-packages] [Bug 2007306] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools
Public bug reported: Ran into this on Ubuntu 20.04 while running "sudo apt install linux- tools-generic". ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.4.0-139:amd64: Install linux-tools-5.4.0-139-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evan 2001 F pulseaudio /dev/snd/controlC2: evan 2001 F pulseaudio /dev/snd/pcmC0D0p: evan 2001 F...m pulseaudio /dev/snd/controlC1: evan 2001 F pulseaudio CasperMD5CheckResult: skip Date: Tue Feb 14 13:45:48 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-139.156_all.deb ... Unpacking linux-tools-common (5.4.0-139.156) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-139.156_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 InstallationDate: Installed on 2022-12-08 (68 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: LENOVO 30B4S28S0F ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=4244e522-14d4-4ec0-aa65-59cc1f57ff19 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2017 dmi.bios.release: 0.38 dmi.bios.vendor: LENOVO dmi.bios.version: S00KT38A dmi.board.name: 102F dmi.board.vendor: LENOVO dmi.board.version: SBB0J05441 WIN 3305049314784 dmi.chassis.asset.tag: MJ05C51F dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 16.19 dmi.modalias: dmi:bvnLENOVO:bvrS00KT38A:bd03/02/2017:br0.38:efr16.19:svnLENOVO:pn30B4S28S0F:pvrThinkStationP510:rvnLENOVO:rn102F:rvrSBB0J05441WIN3305049314784:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30B4_BU_LENOVO_FM_ThinkStationP510: dmi.product.family: ThinkStation P510 dmi.product.name: 30B4S28S0F dmi.product.sku: LENOVO_MT_30B4_BU_LENOVO_FM_ThinkStation P510 dmi.product.version: ThinkStation P510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/2007306 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 Status in linux package in Ubuntu: New Bug description: Ran into this on Ubuntu 20.04 while running "sudo apt install linux- tools-generic". ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.4.0-139:amd64: Install linux-tools-5.4.0-139-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evan 2001 F pulseaudio /dev/snd/controlC2: evan 2001 F pulseaudio /dev/snd/pcmC0D0p: evan 2001 F...m pulseaudio /dev/snd/controlC1: evan 2001 F pulseaudio CasperMD5CheckResult: skip Date: Tue Feb 14 13:45:48 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-139.156_all.deb ... Unpacking linux-tools-common (5.4.0-139.156) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-139.156_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-5.15-tools-common 5.15.0-1023.28~20.04.1 ErrorMessage:
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Following up on #57. IMO, filesystem corruption is one of the worst types of bugs a Linux distro can introduce. That this was bug was known, released anyways, and only mentioned 2000+ words into the patch notes is particularly egregious. I doubt a bug in EXT4 would be treated with the same carelessness. If you're shipping ZFS as a root filesystem in Ubuntu then you need to treat it as such. Has Canonical made any statement regarding how they will prevent this from happening in the future? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Looking for advice if anyone has it as to how I can recover my filesystem after being affected by this bug. I installed zfs 2.0.6 via dkms and have moved affected files like my chrome cache to a quarantine location as suggested by Trent. However, I seem to continue stumbling on affected files, and even with /sys/module/zfs/parameters/zfs_recover=1 set I see panics in dmesg and hung processes that cant be killed. >From what I've gathered: Running 2.0.6 via dkms means that I'm not running the affected code anymore. However, it seems like there is permanent FS corruption (which is very unfortunate since this is the sort of thing ZFS is supposed to be good at preventing). Is there a best course of action to prevent future kernel panics? Would reverting to a snapshot from before I noticed this issue work, or is there shared metadata that's been corrupted? Should I just copy the files I can access onto another disk and re-create my ZFS pool / dataset? Any advice is appreciated :/ Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Thanks Matt. I have it installed on one machine so far and looks good (in the past 10 minutes). fstrim of a ~30 TB RAID 10 took 73 seconds instead of multiple hours. # uname -a Linux xxx 5.4.0-75-generic #84-Ubuntu SMP Fri May 28 16:28:37 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # df -h /dev/md0 Filesystem Size Used Avail Use% Mounted on /dev/md0 30T 212G 29T 1% /opt/raid # cat /proc/mdstat Personalities : [raid10] [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] md0 : active raid10 nvme7n1[7] nvme2n1[2] nvme6n1[6] nvme4n1[4] nvme1n1[1] nvme3n1[3] nvme0n1[0] nvme5n1[5] 31255576576 blocks super 1.2 512K chunks 2 near-copies [8/8] [] bitmap: 11/233 pages [44KB], 65536KB chunk unused devices: # time fstrim /opt/raid real1m13.162s user0m0.004s sys 0m0.351s -- 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
I have it running on two machines now that needed big RAID 10s: # uname -rv 5.4.0-72-generic #80+TEST1896578v20210504b1-Ubuntu SMP Tue May 4 00:30:36 UTC 202 # df -h /opt/raid Filesystem Size Used Avail Use% Mounted on /dev/md0 30T 208G 29T 1% /opt/raid # cat /proc/mdstat Personalities : [raid10] md0 : active raid10 nvme7n1[7] nvme6n1[6] nvme5n1[5] nvme4n1[4] nvme3n1[3] nvme2n1[2] nvme1n1[1] nvme0n1[0] 31255576576 blocks super 1.2 512K chunks 2 near-copies [8/8] [] [>] resync = 0.1% (48777600/31255576576) finish=2514.8min speed=206813K/sec bitmap: 233/233 pages [932KB], 65536KB chunk FWIW the mkfs.xfs took ~1 minute across 8x8TB NVMe disks with this patched 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commit enables
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Is there any ETA on a supported kernel with this patch? -- 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commit enables Radid10 to use large discards, instead of splitting into many bios, since the technical hurdles have now been removed. commit ca4a4e9a55beeb138bb06e3867f5e486da896d44 Author: Mike Snitzer Date: Fri Apr 30 14:38:37 2021 -0400 Subject: dm raid: remove unnecessary discard limits for raid0 and raid10 Link: https://github.com/torvalds/linux/commit/ca4a4e9a55beeb138bb06e3867f5e486da896d44 The commits more or less cherry pick to the 5.11, 5.8, 5.4 and 4.15 kernels, with the following minor backports: 1) submit_bio_noacct() needed to be renamed to generic_make_request() since it was recently changed in: commit ed00aabd5eb9fb44d6aff1173234a2e911b9fead
[Kernel-packages] [Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260
Complete newbie here. But also wanted to report this affects 17.10 on a HP Spectre 13" Intel® Core™ i7-7500U CPU @ 2.70GHz × 4 -- 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/1682744 Title: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260 Status in Ubuntu: Unknown Status in linux package in Ubuntu: Triaged Bug description: Only happens when connecting to 5GHz network, 2.5 GHz work fine. Network controller: Intel Corporation Wireless 7260 (rev 6b) iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode iwlmvm апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4289] device (wlan0): Activation: starting connection 'NewHibernia5' (104460fe-9e5b-4a8c-8735-cfe48dec488e) апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4290] audit: op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" name="NewHibernia5" pid=7054 uid=1000 result="success" апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4291] device (wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4293] manager: NetworkManager state is now CONNECTING апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4339] device (wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent) апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4381] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4383] device (wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but secrets are required. апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4384] device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4433] device (wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4438] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4450] device (wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets exist. No new secrets needed. апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4451] Config: added 'ssid' value 'NewHibernia5' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4451] Config: added 'scan_ssid' value '1' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'key_mgmt' value 'WPA-PSK' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'auth_alg' value 'OPEN' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'psk' value '' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4654] sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1 апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz) апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values: апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_HW_IF_CONFIG_REG: 0X40489204 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT_COALESCING: 0X8000ff40 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT_MASK: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_FH_INT_STATUS: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GPIO_IN: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_RESET: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GP_CNTRL: 0X080403cd апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_HW_REV: 0X0144 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_EEPROM_REG: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_EEPROM_GP: 0X8000 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_OTP_GP_REG: 0X803a апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GIO_REG: 0X001f0042 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
[Kernel-packages] [Bug 1704512] Re: MTX load commands fail on kernel 4.12
I don't have relevant log files and can't currently replicate the issue since I'm on 4.11.10, so I will mark this as complete. ** 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/1704512 Title: MTX load commands fail on kernel 4.12 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 4.12rc0 (also tested on all RC's 4.12, and 4.13 git), the following mtx commands fail on an ML6000 with LTO5 FC drive attached to a qlogic 2462 HBA. Running Ubuntu Server 16.04 mtx -f /dev/sg19 load 16 0 Loading media from Storage Element 16 into drive 0...mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=0 (Unknown?!) mtx: Request Sense: Sense Key=No Sense mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 00 mtx: Request Sense: Additional Sense Qualifier = 00 mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no MOVE MEDIUM from Element Address 4111 to 256 Failed Downgrading to 4.11.10 resolves the issue. The issue (and fix) has been replicated on a server running Fedora with an NEOs T48 with an LTO6 SAS drive attached to LSI 3008. Commit hash from latest version that works is - v4.11-4395-g89c9fea Sorry if anything here is formatted wrong, first bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704512/+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 219057] Re: Bluetooth does not coexist with WiFi
This workaround fixed this issue for me: echo "options iwlwifi bt_coex_active=0" | sudo tee -a /etc/modprobe.d/iwlwifi.conf The above instructions set a bunch of unrelated options, and also blank out any pre-existing content. -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels >= 3.12
Does this result in anyone not being able to suspend?
--
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/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfermode (err_mask=0x40) on upstream kernels >= 3.12
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux source package in Wily:
Fix Released
Bug description:
[Impact]
* Users with Samsung 8** SSD drives see miscellaneous errors and
warning messages in the logs depending on the firmware level of the
drive while booting or after running trim.
[Test Case]
* Run this script, and then check logs for errors.
#!/bin/bash
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
for i in {0..10} ; do
cp -r linux linux$i
done
rm -rf linux*
echo "sudo fstrim requires your password"
sudo fstrim ./
[Regression Potential]
* There is very little regression potential as this change simply
prevents NCQ trim from being used on Samsung 8** drives.
[Other Info]
* Commit is upstream.
* Greatly increasing the timeout for the drives seems to relieve the timeout
errors. This may be due to trimming large numbers of sectors with single
commands. It may be prudent for future upstream to break up large trims into
multiple requests on smaller regions.
===Original Bug description ==
Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-30-generic 3.13.0-30.55
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 2131 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jul 7 20:01:28 2014
HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
InstallationDate: Installed on 2014-06-22 (14 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-30-generic N/A
linux-backports-modules-3.13.0-30-generic N/A
linux-firmware 1.127.4
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-EM
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.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM: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/1338706/+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 1547231] Re: /proc/$pid/maps performance regression
What makes this unsuitable for an SRU? Is the concern that this would be considered an interface change? -- 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/1547231 Title: /proc/$pid/maps performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: /proc/$pid/maps experienced a significant performance regression for processes with large numbers of threads between Precise and Trusty due to an upstream bug. This behavior is currently blocking my ability to upgrade to Trusty, as we depend on applications with with 10s of thousands of threads. The issue has been fixed in the 4.5 release. Upstream report: http://comments.gmane.org/gmane.linux.kernel.mm/144712 Upstream patches: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=65376df582174ffcec9e6471bf5b0dd79ba05e4a ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 18 12:13 seq crw-rw 1 root audio 116, 33 Feb 18 12:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Feb 18 13:44:23 2016 MachineType: Supermicro A1SAi PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=/dev/md1 ro console=tty0 console=ttyS0,57600 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-18 (579 days ago) WifiSyslog: dmi.bios.date: 02/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A1SAi dmi.board.vendor: Supermicro dmi.board.version: 123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 18 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd02/27/2014:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SAi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.: dmi.product.name: A1SAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547231/+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 1547231] Re: /proc/$pid/maps performance regression
** Description changed: /proc/$pid/maps experienced a significant performance regression for processes with large numbers of threads between Precise and Trusty due to an upstream bug. This behavior is currently blocking my ability to upgrade to Trusty, as we depend on applications with with 10s of thousands of threads. - The issue has been fixed in the usptream -mm tree. + The issue has been fixed in the 4.5 release. Upstream report: http://comments.gmane.org/gmane.linux.kernel.mm/144712 - Upstream patches: - https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4=2d2a106c79f4b5b2b10e72957f7448e276dbf0a9 - https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4=eb1899e03405faf7c79396ae9593303d53e2710d + Upstream patches: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=65376df582174ffcec9e6471bf5b0dd79ba05e4a ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Feb 18 12:13 seq - crw-rw 1 root audio 116, 33 Feb 18 12:13 timer + total 0 + crw-rw 1 root audio 116, 1 Feb 18 12:13 seq + crw-rw 1 root audio 116, 33 Feb 18 12:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Feb 18 13:44:23 2016 MachineType: Supermicro A1SAi PciMultimedia: - + ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=/dev/md1 ro console=tty0 console=ttyS0,57600 RelatedPackageVersions: - linux-restricted-modules-3.13.0-36-generic N/A - linux-backports-modules-3.13.0-36-generic N/A - linux-firmware 1.127.20 + linux-restricted-modules-3.13.0-36-generic N/A + linux-backports-modules-3.13.0-36-generic N/A + linux-firmware 1.127.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-18 (579 days ago) WifiSyslog: - + dmi.bios.date: 02/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A1SAi dmi.board.vendor: Supermicro dmi.board.version: 123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 18 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd02/27/2014:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SAi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.: dmi.product.name: A1SAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro -- 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/1547231 Title: /proc/$pid/maps performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: /proc/$pid/maps experienced a significant performance regression for processes with large numbers of threads between Precise and Trusty due to an upstream bug. This behavior is currently blocking my ability to upgrade to Trusty, as we depend on applications with with 10s of thousands of threads. The issue has been fixed in the 4.5 release. Upstream report: http://comments.gmane.org/gmane.linux.kernel.mm/144712 Upstream patches: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=65376df582174ffcec9e6471bf5b0dd79ba05e4a ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 18 12:13 seq crw-rw 1 root audio 116, 33 Feb 18 12:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Feb 18 13:44:23
[Kernel-packages] [Bug 1547231] Re: /proc/$pid/maps performance regression
Hey folks - Anything I can do to get this into the next trusty kernel release? This has now caused multiple production incidents for us. -- 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/1547231 Title: /proc/$pid/maps performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: /proc/$pid/maps experienced a significant performance regression for processes with large numbers of threads between Precise and Trusty due to an upstream bug. This behavior is currently blocking my ability to upgrade to Trusty, as we depend on applications with with 10s of thousands of threads. The issue has been fixed in the usptream -mm tree. Upstream report: http://comments.gmane.org/gmane.linux.kernel.mm/144712 Upstream patches: https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4=2d2a106c79f4b5b2b10e72957f7448e276dbf0a9 https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4=eb1899e03405faf7c79396ae9593303d53e2710d ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 18 12:13 seq crw-rw 1 root audio 116, 33 Feb 18 12:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Feb 18 13:44:23 2016 MachineType: Supermicro A1SAi PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=/dev/md1 ro console=tty0 console=ttyS0,57600 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-18 (579 days ago) WifiSyslog: dmi.bios.date: 02/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A1SAi dmi.board.vendor: Supermicro dmi.board.version: 123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 18 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd02/27/2014:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SAi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.: dmi.product.name: A1SAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547231/+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 1584597] Re: Hyper-V Memory Ballooning re-broken in 16.04
Sorry, second screen shot didn't get attached. Here it is. See post #38 for details. ** Attachment added: "Ubuntu Mate Desktop 16.04.1 /proc/meminfo" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+attachment/4738365/+files/ubuntu_mate_16..04.1_proc_mem_info_hyperv.png -- 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/1584597 Title: Hyper-V Memory Ballooning re-broken in 16.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but the bug has returned in 16.04. Steps to reproduce: 1. Create Gen2 Hyper-V VM 2. Install Ubuntu 16.04 3. modprobe hv_balloon Memory usage according to Hyper-V Manager will not change This has been reproduced on 2 fresh Ubuntu Server 16.04 instances. I installed linux-generic-xenial on a 14.04 instance, rebooted, modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to the correct level. Environment: Host: Windows NanoServer 2016 Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6` Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+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 1584597] Re: Hyper-V Memory Ballooning re-broken in 16.04
OP seems to be MIA, but I'm also seeing higher than expected memory usage. This is actually showing up in both Ubuntu 15.10 and 16.04. I've attached screenshots of `cat proc/meminfo` from both an Ubuntu 15.10 Desktop and Ubuntu Mate 16.04.1 Desktop install. The 15.10 VM has dynamic memory set to 512 MiB - 4096 MiB. Assigned memory is maxed out at 4096 MiB, memory demand is reported as 3604 MiB. The 16.04.1 VM has dynamic memory set to 512 MiB - 2048 MiB. Assigned memory is maxed out at 2048 MiB, memory demand is reported as 2088 MiB. Both of these are with the VM idling for days and nothing going on. The host computer has 16 GiB of memory, with 4.4 GiB available. Memory usage by host applications (other than VMs) is relatively light. ** Attachment added: "Ubuntu 15.10 Desktop /proc/meminfo" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+attachment/4738364/+files/ubuntu_15.10_proc_mem_info_hyperv.png -- 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/1584597 Title: Hyper-V Memory Ballooning re-broken in 16.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but the bug has returned in 16.04. Steps to reproduce: 1. Create Gen2 Hyper-V VM 2. Install Ubuntu 16.04 3. modprobe hv_balloon Memory usage according to Hyper-V Manager will not change This has been reproduced on 2 fresh Ubuntu Server 16.04 instances. I installed linux-generic-xenial on a 14.04 instance, rebooted, modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to the correct level. Environment: Host: Windows NanoServer 2016 Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6` Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+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 1584597] Re: Hyper-V Memory Ballooning re-broken in 16.04
OP seems to be MIA, but I'm also seeing higher than expected memory usage. This is actually showing up in both Ubuntu 15.10 and 16.04. I've attached screenshots of `cat proc/meminfo` from both an Ubuntu 15.10 Desktop and Ubuntu Mate 16.04.1 Desktop install. The 15.10 VM has dynamic memory set to 512 MiB - 4096 MiB. Assigned memory is maxed out at 4096 MiB, memory demand is reported as 3604 MiB. The 16.04.1 VM has dynamic memory set to 512 MiB - 2048 MiB. Assigned memory is maxed out at 2048 MiB, memory demand is reported as 2088 MiB. Both of these are with the VM idling for days and nothing going on. The host computer has 16 GiB of memory, with 4.4 GiB available. Memory usage by host applications (other than VMs) is relatively light. ** Attachment added: "Ubuntu 15.10 Desktop /proc/meminfo" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+attachment/4738363/+files/ubuntu_15.10_proc_mem_info_hyperv.png -- 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/1584597 Title: Hyper-V Memory Ballooning re-broken in 16.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but the bug has returned in 16.04. Steps to reproduce: 1. Create Gen2 Hyper-V VM 2. Install Ubuntu 16.04 3. modprobe hv_balloon Memory usage according to Hyper-V Manager will not change This has been reproduced on 2 fresh Ubuntu Server 16.04 instances. I installed linux-generic-xenial on a 14.04 instance, rebooted, modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to the correct level. Environment: Host: Windows NanoServer 2016 Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6` Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+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 1285434] Re: hyper-v: Keyboard dysfunctional while booting 14.04 Generation 2 virtual machines on Hyper-V
Can also confirm bug is present. Trying to install Ubuntu 16.04 LTS server in a Gen 2 Hyper-V VM with secure boot enabled. Keyboard does not work. -- 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/1285434 Title: hyper-v: Keyboard dysfunctional while booting 14.04 Generation 2 virtual machines on Hyper-V Status in linux package in Ubuntu: Fix Released Bug description: Hi folks, While booting in to Generation 2 virtual machine mode, I noticed that the keyboard stops functioning. It appears that the keyboard is operational during the Grub 2 menu (see attached picture) but when we get to the screen to select a language, the keyboard stops responding. Is it feasible for you to check if the Hyper-V keyboard driver has been included from here: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/tree/drivers/input/serio/hyperv-keyboard.c?id=HEAD Please let me know. Thanks, Abhishek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1285434/+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 1533541] [NEW] BT device will connect automatically even though the option "connect automatically when detected" is not checked
Public bug reported: $ system-image-cli -i current build number: 228 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-13 07:17:55 version version: 228 version ubuntu: 20160113 version device: 20160108-efc96d8 version custom: 2015--36-46-vivid Steps to reproduce: 1. Open Bluetooth settings page and turn Bluetooth on 2. Press 'connect' button on bt devices (mouse), make sure it can be detected by phone 3. Enter the entry of target bt device (mouse) then tap 'connect', make sure the option "Connect automatically when detected" is not checked 4. Once the mouse is connected, enter the device entry check the option again, found the option has been checked automatically 5. Uncheck the option and disconnect the bt device, Actual results: It's still going to connect automatically and will be connected successfully when it's scanned again ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1533541 Title: BT device will connect automatically even though the option "connect automatically when detected" is not checked Status in bluez package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 228 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-13 07:17:55 version version: 228 version ubuntu: 20160113 version device: 20160108-efc96d8 version custom: 2015--36-46-vivid Steps to reproduce: 1. Open Bluetooth settings page and turn Bluetooth on 2. Press 'connect' button on bt devices (mouse), make sure it can be detected by phone 3. Enter the entry of target bt device (mouse) then tap 'connect', make sure the option "Connect automatically when detected" is not checked 4. Once the mouse is connected, enter the device entry check the option again, found the option has been checked automatically 5. Uncheck the option and disconnect the bt device, Actual results: It's still going to connect automatically and will be connected successfully when it's scanned again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1533541/+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 1495136] Re: System hard froze, kernel bug reported in syslog
I have had the same issue - went away when I reverted to 3.19.0-28-generic #30. Hardware is a DELL Lattitude 6540 with Intel Graphics -- 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/1495136 Title: System hard froze, kernel bug reported in syslog Status in linux package in Ubuntu: Confirmed Bug description: When I rebooted and looked in syslog, I saw this: Sep 12 15:05:41 avignon thermald[681]: Dropped below poll threshold Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 0:Processor Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 8:intel_powerclamp Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 11:intel_pstate Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 10:rapl_controller Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 0:Processor Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 8:intel_powerclamp Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 11:intel_pstate Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset index 10:rapl_controller Sep 12 15:05:41 avignon thermald[681]: Read set point 0 Sep 12 15:05:57 avignon thermald[681]: Dropped below poll threshold Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 0:Processor Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 8:intel_powerclamp Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 11:intel_pstate Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 10:rapl_controller Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 0:Processor Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 8:intel_powerclamp Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 11:intel_pstate Sep 12 15:05:57 avignon thermald[681]: thd_trip_cdev_state_reset index 10:rapl_controller Sep 12 15:05:58 avignon thermald[681]: Read set point 0 Sep 12 15:17:01 avignon CRON[4827]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Sep 12 13:56:05 avignon org.freedesktop.Notifications[1391]: ** (notify-osd:1777): WARNING **: stack_close_notification_handler(): notification id == 0, likely wrong Sep 12 15:29:25 avignon org.freedesktop.Telepathy.AccountManager[1391]: (process:1830): GLib-GIO-WARNING **: netlink message was truncated; shouldn't happen... Followed immediately by this Sep 12 15:29:29 avignon kernel: [16233.486261] BUG: unable to handle kernel paging request at ffe0 Sep 12 15:29:29 avignon kernel: [16233.486330] IP: [] i915_gem_object_move_to_inactive+0x7d/0x170 [i915] Sep 12 15:29:29 avignon kernel: [16233.486414] PGD 1c16067 PUD 1c18067 PMD 0 Sep 12 15:29:29 avignon kernel: [16233.486453] Oops: [#1] SMP Sep 12 15:29:29 avignon kernel: [16233.486484] Modules linked in: hid_generic snd_usb_audio usbhid snd_usbmidi_lib hid snd_hda_codec_hdmi arc4 snd_hda_codec_via uvcvideo snd_hda_codec_generic iwldvm snd_hda_intel snd_hda_controller mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_core snd_hda_codec snd_hwdep v4l2_common i915 videodev snd_pcm intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp media coretemp snd_seq_midi snd_seq_midi_event snd_rawmidi iwlwifi kvm_intel kvm snd_seq crct10dif_pclmul crc32_pclmul snd_seq_device ghash_clmulni_intel mei_me snd_timer cfg80211 drm_kms_helper drm aesni_intel snd mei rtsx_pci_ms memstick i2c_algo_bit aes_x86_64 lrw soundcore gf128mul glue_helper ablk_helper shpchp cryptd lpc_ich video joydev serio_raw tpm_infineon mac_hid wmi parport_pc ppdev lp parport autofs4 rtsx_pci_sdmmc psmouse ahci r8169 rtsx_pci libahci mii Sep 12 15:29:29 avignon kernel: [16233.487171] CPU: 1 PID: 1058 Comm: Xorg Not tainted 3.19.0-29-generic #31-Ubuntu Sep 12 15:29:29 avignon kernel: [16233.487223] Hardware name: System76, Inc. Gazelle Professional/Gazelle Professional, BIOS 4.6.5 09/27/2012 Sep 12 15:29:29 avignon kernel: [16233.487284] task: 880214b989d0 ti: 88020485c000 task.ti: 88020485c000 Sep 12 15:29:29 avignon kernel: [16233.487331] RIP: 0010:[] [] i915_gem_object_move_to_inactive+0x7d/0x170 [i915] Sep 12 15:29:29 avignon kernel: [16233.487424] RSP: 0018:88020485fb88 EFLAGS: 00010286 Sep 12 15:29:29 avignon kernel: [16233.487459] RAX: RBX:
[Kernel-packages] [Bug 1491284] [NEW] Two spinners showing and the status will become "Not discoverable" after BT enabled for a while
Public bug reported: $ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 06:52:45 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid Steps to reproduce: 1.Enable Bluetooth from System Settings -->Bluetooth-->Enabled 2.The status will show as "Discoverable -->Aquaris E4.5 Ubuntu Edition" and the spinner appears in 10 seconds 3.Waiting for a while then check the status again Expected results: The status should be kept as "Discoverable" with device name shown, and only one spinner shows in every 10 seconds Actual results: The status will become "Not discoverable" and two spinners showing after for a while, attached the screenshot and the dmesg output bellow: [ 1050.241914] BT ON <>sec=1441177892, usec=884713 [ 1050.241939] [WMT-STP-EXP][I]mtk_wcn_wmt_func_on: mtk_wcn_wmt_func_on_f type(0) [ 1050.241959] [HCI-STP][I]hci_stp_open:WMT turn on BT OK! [ 1050.241978] Flush type = 0 Rx Queue [ 1050.242119] [HCI-STP][I]hci_stp_dev_init_work:Load custom BT config success [ 1050.275283] [HCI-STP][I]hci_stp_open:hci_stp_dev_init ok [ 1050.275315] Flush type = 0 Rx Queue [ 1078.037588] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1591.020633] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1761.020828] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1813.890670] [mtk_net][sched]dev_deactivate dev = wlan0 [ 1813.904681] cfg80211: Calling CRDA for country: US [ 1825.479625] [mtk_net][sched]dev_activate dev = wlan0 [ 1825.500057] --> mtk_cfg80211_set_default_key() [ 1921.031722] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2161.026379] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2511.029227] [STP-BTIF][I]mtk_wcn_consys_stp_btif_tx:special case for STP-CORE,pbuf(c1001e98) [ 2511.036971] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 3424.024060] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bt-not-discoverable-1.png" https://bugs.launchpad.net/bugs/1491284/+attachment/4456033/+files/bt-not-discoverable-1.png -- 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/1491284 Title: Two spinners showing and the status will become "Not discoverable" after BT enabled for a while Status in bluez package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 06:52:45 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid Steps to reproduce: 1.Enable Bluetooth from System Settings -->Bluetooth-->Enabled 2.The status will show as "Discoverable -->Aquaris E4.5 Ubuntu Edition" and the spinner appears in 10 seconds 3.Waiting for a while then check the status again Expected results: The status should be kept as "Discoverable" with device name shown, and only one spinner shows in every 10 seconds Actual results: The status will become "Not discoverable" and two spinners showing after for a while, attached the screenshot and the dmesg output bellow: [ 1050.241914] BT ON <>sec=1441177892, usec=884713 [ 1050.241939] [WMT-STP-EXP][I]mtk_wcn_wmt_func_on: mtk_wcn_wmt_func_on_f type(0) [ 1050.241959] [HCI-STP][I]hci_stp_open:WMT turn on BT OK! [ 1050.241978] Flush type = 0 Rx Queue [ 1050.242119] [HCI-STP][I]hci_stp_dev_init_work:Load custom BT config success [ 1050.275283] [HCI-STP][I]hci_stp_open:hci_stp_dev_init ok [ 1050.275315] Flush type = 0 Rx Queue [ 1078.037588] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1591.020633] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1761.020828] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1813.890670] [mtk_net][sched]dev_deactivate dev = wlan0 [ 1813.904681] cfg80211: Calling CRDA for country: US [ 1825.479625] [mtk_net][sched]dev_activate dev = wlan0 [ 1825.500057] --> mtk_cfg80211_set_default_key() [ 1921.031722] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2161.026379] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2511.029227] [STP-BTIF][I]mtk_wcn_consys_stp_btif_tx:special case for STP-CORE,pbuf(c1001e98) [ 2511.036971] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 3424.024060] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) To manage notifications about this bug
[Kernel-packages] [Bug 1481991] Re: 900 second pause on boot
Does needs-bisect tag mean there's some action you need from me? -- 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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Triaged Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443119/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] Re: 900 second pause on boot
apport information ** Tags added: apport-collected ** Description changed: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. + --- + ApportVersion: 2.14.1-0ubuntu3.11 + Architecture: i386 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME= + MachineType: Hewlett-Packard HP Compaq dc5800 Microtower + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide + ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 + 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-61-generic N/A + linux-backports-modules-3.13.0-61-generic N/A + linux-firmware 1.127.14 + RfKill: + 3: phy3: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: trusty + Uname: Linux 3.13.0-61-generic i686 + UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) + UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video + WpaSupplicantLog: + + _MarkForUpload: True + dmi.bios.date: 08/01/2008 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: 786F2 v01.51 + dmi.board.asset.tag: 2UA9340HZZ + dmi.board.name: 2820h + dmi.board.vendor: Hewlett-Packard + dmi.chassis.asset.tag: 2UA9340HZZ + dmi.chassis.type: 6 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: + dmi.product.name: HP Compaq dc5800 Microtower + dmi.sys.vendor: Hewlett-Packard ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443117/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname:
[Kernel-packages] [Bug 1481991] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443126/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443124/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443123/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443122/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443127/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443129/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443125/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443120/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443121/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1481991/+attachment/4443118/+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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Incomplete Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1481991] Re: 900 second pause on boot
Yes, I'm only seeing this on 3.13.0.x kernels, I don't see it with the older 3.2 kernels. The messages on screen during the pause are the same as in the dmesg output in comment #1 before the 900s timestamp. ** 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/1481991 Title: 900 second pause on boot Status in linux package in Ubuntu: Confirmed Bug description: When I boot from a 3.13.0.x kernel I get a very odd 900 second (15 minute!) pause on boot (see attached dmesg log). Once past the pause the system works normally and with no issues. If I boot from a 3.2.0.x kernel there is no pause. $ cat /etc/issue.net Ubuntu 14.04.3 LTS $ uname -a Linux ubuntu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:22:15 UTC 2015 i686 i686 i686 GNU/Linux I'm happy to provide any other information that would be useful. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME= MachineType: Hewlett-Packard HP Compaq dc5800 Microtower NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/md0 ro all_generic_ide ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 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-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-61-generic i686 UpgradeStatus: Upgraded to trusty on 2015-06-27 (45 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare tty video WpaSupplicantLog: _MarkForUpload: True dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.51 dmi.board.asset.tag: 2UA9340HZZ dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9340HZZ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.51:bd08/01/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481991/+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 1357632] Re: HVR-950Q Display Glitches
Its too late. I've switched distros and all sorts of stuff since then. Somewhere along the line, an update of some sort has fixed it. I don't know if its was a video driver or kernel update or what, but its was working last I used it. I ended up giving it to my dad who runs it on his laptop (also Linux) so he can watch his news while he works on his car. Thanks anyway! -- 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/1357632 Title: HVR-950Q Display Glitches Status in “linux” package in Ubuntu: Incomplete Bug description: I have a USB TV Tuner - Hauppage HVR-950Q with USB ID 2040:7217 It has an odd display glitch which is hard to describe. I can post screen-grabs but its intermittant, yet constant. What I mean is that it occurs every couple of seconds, but not every frame. It's less noticeable with tvtime, but is noticeable in all video applications trying to display from this tuner. I have tried different USB ports and changing kernels and changing other USB devices. I can make the problem go away by transcoding a video with Handbrake - this eats up a lot of CPU time and this seems to resolve the problem (race condition?) This is VERY annoying. My poor laptop is being thrashed by having to transcode a video everytime I want to watch TV. If anyone can help, it would be greatly appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357632/+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 1381805] [NEW] 'man perf-stat' has bad notation for specifying multiple events of interest
Public bug reported: The SYNOPSIS in the manpage of perf-stat(1) says: perf stat [-e EVENT | --event=EVENT] [-a] command where -e specifies events of interest: -e, --event= Select the PMU event. Selection can be a symbolic event name (use perf list to list all events) or a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a hexadecimal event descriptor. Nowhere in the manpage does it say how to specify multiple events, or even whether that is possible. A strict reading of the syntax would suggest that it actually *isn't* possible. Now, it's not hard to guess: either 'perf -e event1 -e event2 ...' or 'perf -e event1,event2' seems to work, but this should be specified explicitly. Perhaps something like -e, --event= Select the PMU event. Selection can be a symbolic event name (use perf list to list all events) or a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a hexadecimal event descriptor. Multiple events can be specified either as a comma-separated list or as multiple -e EVENT options. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-tools-generic 3.13.0.37.44 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: edriscoll 2480 F pulseaudio /dev/snd/pcmC1D0p: edriscoll 2480 F...m pulseaudio /dev/snd/controlC0: edriscoll 2480 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 15 17:40:03 2014 HibernationDevice: RESUME=/dev/mapper/md126p4_crypt IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: Hewlett-Packard HP Z220 CMT Workstation ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=4977c0ff-3e3b-46ec-8514-7b53d26fe4df ro splash quiet nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K51 v01.61 dmi.board.asset.tag: 2UA3310KB0 dmi.board.name: 1790 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA3310KB0 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK51v01.61:bd05/16/2013:svnHewlett-Packard:pnHPZ220CMTWorkstation:pvr:rvnHewlett-Packard:rn1790:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z220 CMT Workstation dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug trusty ** Attachment removed: AlsaInfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237695/+files/AlsaInfo.txt ** Attachment removed: BootDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237696/+files/BootDmesg.txt ** Attachment removed: CRDA.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237697/+files/CRDA.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237698/+files/CurrentDmesg.txt ** Attachment removed: PulseList.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237705/+files/PulseList.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237704/+files/ProcModules.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237706/+files/UdevDb.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237703/+files/ProcInterrupts.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237700/+files/Lspci.txt ** Attachment removed: UdevLog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237707/+files/UdevLog.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237702/+files/ProcCpuinfo.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237701/+files/Lsusb.txt ** Attachment removed: WifiSyslog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+attachment/4237708/+files/WifiSyslog.txt ** Attachment removed: Dependencies.txt
[Kernel-packages] [Bug 1381805] Re: 'man perf-stat' has bad notation for specifying multiple events of interest
I removed the log files because they contained what I considered private information, like what programs I'm running. Anyway, this is a simple documentation bug so there shouldn't be any diagnosis your logs would help with anyway, aside from knowing the package information 'linux-tools-generic 3.13.0.37.44' which is included in the main text. Setting to confirmed. ** 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/1381805 Title: 'man perf-stat' has bad notation for specifying multiple events of interest Status in “linux” package in Ubuntu: Confirmed Bug description: The SYNOPSIS in the manpage of perf-stat(1) says: perf stat [-e EVENT | --event=EVENT] [-a] command where -e specifies events of interest: -e, --event= Select the PMU event. Selection can be a symbolic event name (use perf list to list all events) or a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a hexadecimal event descriptor. Nowhere in the manpage does it say how to specify multiple events, or even whether that is possible. A strict reading of the syntax would suggest that it actually *isn't* possible. Now, it's not hard to guess: either 'perf -e event1 -e event2 ...' or 'perf -e event1,event2' seems to work, but this should be specified explicitly. Perhaps something like -e, --event= Select the PMU event. Selection can be a symbolic event name (use perf list to list all events) or a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a hexadecimal event descriptor. Multiple events can be specified either as a comma-separated list or as multiple -e EVENT options. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-tools-generic 3.13.0.37.44 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: edriscoll 2480 F pulseaudio /dev/snd/pcmC1D0p: edriscoll 2480 F...m pulseaudio /dev/snd/controlC0: edriscoll 2480 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 15 17:40:03 2014 HibernationDevice: RESUME=/dev/mapper/md126p4_crypt IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: Hewlett-Packard HP Z220 CMT Workstation ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=4977c0ff-3e3b-46ec-8514-7b53d26fe4df ro splash quiet nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K51 v01.61 dmi.board.asset.tag: 2UA3310KB0 dmi.board.name: 1790 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA3310KB0 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK51v01.61:bd05/16/2013:svnHewlett-Packard:pnHPZ220CMTWorkstation:pvr:rvnHewlett-Packard:rn1790:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z220 CMT Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381805/+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 1379087] Re: rtl8188ee constantly dropping connections
Wow, installing 3.17 was a mess. X is black because fglrx wouldn't
install an updated module and Xorg is won't fall-back to the open-source
driver. So, I tried to reinstall fglrx, which didn't fix it, but broke
it for my 3.13 kernel! Luckily I have an alternative install (Sabayon
with kernel 3.16, and it seems to have the same issue).
I don't have time to fix fglrx right now, so I'm going to boot it to
3.17 and let it stay black. I'm leaving for a few hours. I'll check
the logs when I get back and see what its like. *sigh* Thats how it
always goes - try to fix one thing and break 20 others.
--
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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
[Kernel-packages] [Bug 1379087] Re: rtl8188ee constantly dropping connections
OK, after leaving the system running for a few hours running 3.17, I'm
showing 5 spurious disconnects in the same number of hours with the same
information in the logs as above. And I don't know if it helps, but I
found someone else is having the same problem with a very similar
notebook, so it may be something particular to this model? I can't
understand the details or if there was a solution since it's in German.
But if it helps, it's http://forum.ubuntuusers.de/topic/rtl8188ee-wlan-
unkonstant-unverlaesslich/
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to
[Kernel-packages] [Bug 1379087] [NEW] rtl8188ee constantly dropping connections
Public bug reported:
Not sure how long this has been happening since I recently switched out
routers to a dd-wrt and it likes to restart the connection whenever you
make a change. It could have been happening before that since I
switched out the other router because it was acting weird (not related I
don't think, but wasn't dropping connection ... but it had 4 amplified
aerials). New router has internal, but my phone is right next to me and
its connection is worse (SNR wise) but stable. Laptop is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the dd-
wrt, the cisco, cron jobs, and all kinds of stuff going to my syslog,
and I checked .. the mrtg run doesn't always preceed the lost message,
but it was fairly common that it does. The same messages repeat
forever (weekly log rotations show from 69 to over 250 occurances per
log file). Let me know what other info I can give. This was stable
some weeks ago, but I can't tell you what I changed or when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant interface
state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq - end_freq
@ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz - 2472000
KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz - 2482000
KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz - 2494000
KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz - 525
KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz - 5835000
KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant interface
state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant interface
state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant interface
state: authenticating - associated
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant interface
state: associated - 4-way handshake
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: WPA: Key negotiation
completed with 96:44:52:76:56:a2 [PTK=CCMP GTK=CCMP]
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-CONNECTED -
Connection to 96:44:52:76:56:a2 completed [id=0 id_str=]
Oct 8
[Kernel-packages] [Bug 1379087] UdevDb.txt
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229152/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] IwConfig.txt
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229144/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] BootDmesg.txt
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229141/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] ProcEnviron.txt
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229148/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] Re: rtl8188ee constantly dropping connections
apport information
** Tags added: apport-collected freya
** Description changed:
Not sure how long this has been happening since I recently switched out
routers to a dd-wrt and it likes to restart the connection whenever you
make a change. It could have been happening before that since I
switched out the other router because it was acting weird (not related I
don't think, but wasn't dropping connection ... but it had 4 amplified
aerials). New router has internal, but my phone is right next to me and
its connection is worse (SNR wise) but stable. Laptop is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the dd-
wrt, the cisco, cron jobs, and all kinds of stuff going to my syslog,
and I checked .. the mrtg run doesn't always preceed the lost message,
but it was fairly common that it does. The same messages repeat
forever (weekly log rotations show from 69 to over 250 occurances per
log file). Let me know what other info I can give. This was stable
some weeks ago, but I can't tell you what I changed or when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: authenticating - associated
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: associated - 4-way handshake
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: WPA: Key negotiation
completed
[Kernel-packages] [Bug 1379087] CRDA.txt
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229142/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] PulseList.txt
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229151/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] ProcModules.txt
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229150/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] ProcInterrupts.txt
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229149/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated
[Kernel-packages] [Bug 1379087] Lsusb.txt
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229146/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] Lspci.txt
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229145/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] CurrentDmesg.txt
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229143/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated
[Kernel-packages] [Bug 1379087] UdevLog.txt
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229153/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] ProcCpuinfo.txt
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229147/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] WifiSyslog.txt
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1379087/+attachment/4229154/+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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
[Kernel-packages] [Bug 1379087] Re: rtl8188ee constantly dropping connections
** 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/1379087
Title:
rtl8188ee constantly dropping connections
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Not sure how long this has been happening since I recently switched
out routers to a dd-wrt and it likes to restart the connection
whenever you make a change. It could have been happening before that
since I switched out the other router because it was acting weird (not
related I don't think, but wasn't dropping connection ... but it had 4
amplified aerials). New router has internal, but my phone is right
next to me and its connection is worse (SNR wise) but stable. Laptop
is NOT stable.
Seems to be similar to Bug #1349108, but that one was a different
driver. And I don't want to post the entire log since I've got the
dd-wrt, the cisco, cron jobs, and all kinds of stuff going to my
syslog, and I checked .. the mrtg run doesn't always preceed the
lost message, but it was fairly common that it does. The same
messages repeat forever (weekly log rotations show from 69 to over 250
occurances per log file). Let me know what other info I can give.
This was stable some weeks ago, but I can't tell you what I changed or
when.
$ uname -a
Linux Taro 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 21:56:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg-query -W linux-firmware
linux-firmware 1.127.7
$ lsmod | grep rtl
rtl8188ee 89677 0
rtl_pci26690 1 rtl8188ee
rtlwifi63475 2 rtl_pci,rtl8188ee
mac80211 638933 3 rtl_pci,rtlwifi,rtl8188ee
cfg80211 496328 2 mac80211,rtlwifi
*** Snippet of /var/log/messages showing problem ... ***
Oct 8 01:25:01 Taro CRON[21545]: (root) CMD (if [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ] [ -d $(grep '^[[:space:]]*[^#]*[[:spac
e:]]*WorkDir' /etc/mrtg.cfg | awk '{ print $NF }') ]; then mkdir -p
/var/log/mrtg ; env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 | tee -
a /var/log/mrtg/mrtg.log ; fi | /usr/bin/logger -t mrtg)
Oct 8 01:25:25 Taro kernel: [ 1811.437893] wlan0: Connection to AP
96:44:52:76:56:a2 lost
Oct 8 01:23:59 Taro wpa_supplicant[1256]: message repeated 2 times: [ wlan0:
CTRL-EVENT-SCAN-STARTED ]
Oct 8 01:25:25 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=96:44:52:76:56:a2 reason=4 locally_generated=1
Oct 8 01:25:25 Taro NetworkManager[1094]: warn Connection disconnected
(reason -4)
Oct 8 01:25:25 Taro kernel: [ 1811.495191] cfg80211: Calling CRDA to update
world regulatory domain
Oct 8 01:25:25 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: completed - disconnected
Oct 8 01:25:25 Taro kernel: [ 1811.502751] cfg80211: World regulatory domain
updated:
Oct 8 01:25:25 Taro kernel: [ 1811.502759] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 8 01:25:25 Taro kernel: [ 1811.502765] cfg80211: (2402000 KHz -
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502770] cfg80211: (2457000 KHz -
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502775] cfg80211: (2474000 KHz -
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502779] cfg80211: (517 KHz -
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:25 Taro kernel: [ 1811.502784] cfg80211: (5735000 KHz -
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
Oct 8 01:25:26 Taro wpa_supplicant[1256]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 8 01:25:26 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: disconnected - scanning
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: SME: Trying to authenticate
with 96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.883224] wlan0: authenticate with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro kernel: [ 1812.902737] wlan0: send auth to
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro NetworkManager[1094]: info (wlan0): supplicant
interface state: scanning - authenticating
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Trying to associate with
96:44:52:76:56:a2 (SSID='Stray Scamp's Back Door' freq=2437 MHz)
Oct 8 01:25:27 Taro kernel: [ 1812.904311] wlan0: authenticated
Oct 8 01:25:27 Taro kernel: [ 1812.905136] wlan0: associate with
96:44:52:76:56:a2 (try 1/3)
Oct 8 01:25:27 Taro kernel: [ 1812.908472] wlan0: RX AssocResp from
96:44:52:76:56:a2 (capab=0x411 status=0 aid=3)
Oct 8 01:25:27 Taro kernel: [ 1812.908619] wlan0: associated
Oct 8 01:25:27 Taro wpa_supplicant[1256]: wlan0: Associated with
96:44:52:76:56:a2
Oct 8 01:25:27 Taro NetworkManager[1094]: info
[Kernel-packages] [Bug 1347737] Re: Kernel nested kvm support
+-+-+
| Property| Value
|
+-+-+
| status | ACTIVE
|
| updated | 2014-07-23T12:12:07Z
|
| OS-EXT-STS:task_state | None
|
| key_name| None
|
| image |
ubuntu-released/ubuntu-trusty-14.04-i386-server-20140607.1-disk1.img
(09c2032a-92cf-47a1-8e94-8c91f3675ab8) |
| hostId |
b06b04e83970a8abe48d9976ba3e5bd6372718da506955357f2bb416
|
| OS-EXT-STS:vm_state | active
|
| flavor | m1.small (2)
|
| id | 5270c9f6-c07b-46da-af1f-97a53bce9de2
|
| security_groups | [{u'name': u'juju-lcy'}, {u'name':
u'juju-lcy-0'}] |
| user_id | 7a636f4ea1914246a08fc84e60960134
|
| name| juju-lcy-machine-0
|
| created | 2014-07-23T12:11:52Z
|
| tenant_id | c0136db8dc454f2d8523d9326bca2d78
|
| OS-DCF:diskConfig | MANUAL
|
| metadata| {}
|
| accessIPv4 |
|
| accessIPv6 |
|
| canonistack network | 10.55.61.111
|
| progress| 0
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-AZ:availability_zone | nova
|
| config_drive|
|
+-+-+
--
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/1347737
Title:
Kernel nested kvm support
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Before we go barking up the tree of the Ubuntu Touch emulator on bare
metal using MAAS and Juju, I wanted to make sure we tried nested kvm.
I heard rumors that this was known not to work well, and sure enough
if I run the touch emulator inside an i386 2G RAM trusty instance on
Canonistack, I get the occasional kernel panic or OOPS.
If it's not something we care to support, that's fine, but getting a
statement from the kernel team to this effect would be helpful.
Begin: Running /scripts/init-bottom ... done.
[9.97] init: ureadahead-touch main process (263) terminated with
status 5
[ 46.67] init: /dev/hw_random not found
[ 46.67] init: cannot open '/initlogo.rle'
[ 47.00] init: /dev/hw_random not found
[ 47.85] healthd: wakealarm_init: timerfd_create failed
[ 48.22] init: cannot find
[Kernel-packages] [Bug 1347737] Re: Kernel nested kvm support
ubuntu@juju-lcy-machine-0:~$ sudo lshw juju-lcy-machine-0 description: Computer product: OpenStack Nova () vendor: OpenStack Foundation version: 2013.1.5 serial: 33313934-3432-5a43-4339-353037544c37 width: 32 bits capabilities: smbios-2.4 dmi-2.4 smp-1.4 smp configuration: boot=normal cpus=1 uuid=5270C9F6-C07B-46DA-AF1F-97A53BCE9DE2 *-core description: Motherboard physical id: 0 *-firmware description: BIOS vendor: Bochs physical id: 0 version: Bochs date: 01/01/2007 size: 96KiB *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz vendor: Intel Corp. physical id: 401 bus info: cpu@0 version: 6.15.11 serial: -06FB---- slot: CPU 1 size: 2GHz capacity: 2GHz width: 64 bits capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx rdtscp x86-64 constant_tsc pni vmx ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm *-memory description: System Memory physical id: 1000 size: 2GiB capacity: 2GiB *-bank description: DIMM RAM physical id: 0 slot: DIMM 0 size: 2GiB width: 64 bits *-pci description: Host bridge product: 440FX - 82441FX PMC [Natoma] vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 02 width: 32 bits clock: 33MHz *-isa description: ISA bridge product: 82371SB PIIX3 ISA [Natoma/Triton II] vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 00 width: 32 bits clock: 33MHz capabilities: isa configuration: latency=0 *-ide description: IDE interface product: 82371SB PIIX3 IDE [Natoma/Triton II] vendor: Intel Corporation physical id: 1.1 bus info: pci@:00:01.1 version: 00 width: 32 bits clock: 33MHz capabilities: ide bus_master configuration: driver=ata_piix latency=0 resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:c0e0(size=16) *-usb description: USB controller product: 82371SB PIIX3 USB [Natoma/Triton II] vendor: Intel Corporation physical id: 1.2 bus info: pci@:00:01.2 version: 01 width: 32 bits clock: 33MHz capabilities: uhci bus_master configuration: driver=uhci_hcd latency=0 resources: irq:11 ioport:c080(size=32) *-bridge UNCLAIMED description: Bridge product: 82371AB/EB/MB PIIX4 ACPI vendor: Intel Corporation physical id: 1.3 bus info: pci@:00:01.3 version: 03 width: 32 bits clock: 33MHz capabilities: bridge configuration: latency=0 *-display UNCLAIMED description: VGA compatible controller product: GD 5446 vendor: Cirrus Logic physical id: 2 bus info: pci@:00:02.0 version: 00 width: 32 bits clock: 33MHz capabilities: vga_controller configuration: latency=0 resources: memory:fc00-fdff memory:febf-febf0fff memory:febe-febe *-network description: Ethernet interface product: Virtio network device vendor: Red Hat, Inc physical id: 3 bus info: pci@:00:03.0 logical name: eth0 version: 00 serial: fa:16:3e:9d:ac:93 width: 32 bits clock: 33MHz capabilities: msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=virtio_net driverversion=1.0.0 ip=10.55.61.111 latency=0 link=yes multicast=yes resources: irq:10 ioport:c0a0(size=32) memory:febf1000-febf1fff *-scsi:0 description: SCSI storage controller product: Virtio block device vendor: Red Hat, Inc physical id: 4 bus info: pci@:00:04.0 version: 00 width: 32 bits clock: 33MHz capabilities: scsi msix bus_master cap_list configuration: driver=virtio-pci latency=0 resources: irq:11 ioport:c000(size=64)
[Kernel-packages] [Bug 1347737] Re: Kernel nested kvm support
Chris points out that we're doing armhf on i386. -- 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/1347737 Title: Kernel nested kvm support Status in “linux” package in Ubuntu: Incomplete Bug description: Before we go barking up the tree of the Ubuntu Touch emulator on bare metal using MAAS and Juju, I wanted to make sure we tried nested kvm. I heard rumors that this was known not to work well, and sure enough if I run the touch emulator inside an i386 2G RAM trusty instance on Canonistack, I get the occasional kernel panic or OOPS. If it's not something we care to support, that's fine, but getting a statement from the kernel team to this effect would be helpful. Begin: Running /scripts/init-bottom ... done. [9.97] init: ureadahead-touch main process (263) terminated with status 5 [ 46.67] init: /dev/hw_random not found [ 46.67] init: cannot open '/initlogo.rle' [ 47.00] init: /dev/hw_random not found [ 47.85] healthd: wakealarm_init: timerfd_create failed [ 48.22] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' [ 48.22] init: cannot find '/system/bin/ubuntuappmanager.disabled', disabling 'ubuntuappmanager' [ 49.37] Unable to handle kernel paging request at virtual address 8030c164 [ 49.37] pgd = bf9dc000 [ 49.37] [8030c164] *pgd=3fffe801, *pte=0030c0cf, *ppte=0030c21e [ 49.37] Internal error: Oops: 81f [#1] PREEMPT ARM [ 49.37] Modules linked in: [ 49.37] CPU: 0Not tainted (3.4.0-3-goldfish #17-Ubuntu) [ 49.37] PC is at __patch_text+0xc/0x24 [ 49.37] LR is at __jump_label_update+0x3c/0x58 [ 49.37] pc : [80413d0c]lr : [8009c6c4]psr: 80030013 [ 49.37] sp : be97df08 ip : 0900 fp : 001d [ 49.37] r10: 0004 r9 : 0001 r8 : bb875380 [ 49.37] r7 : 0001 r6 : 806217ac r5 : 805e8b7c r4 : 806204c8 [ 49.37] r3 : 8030c164 r2 : 805e8064 r1 : ea5b r0 : 8030c164 [ 49.37] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 49.37] Control: 10c5387d Table: 3f9dc059 DAC: 0015 [ 49.37] [ 49.37] PC: 0x80413c8c: [ 49.37] 3c8c e1a0200d ebf014ca e1a096ad e1a09689 e3a08000 eaefe8b6 e281c01c e5923060 [ 49.37] 3cac e8ac6ff0 ee0d3f70 e3a04000 ee0d4f50 e592700c e59f8020 e59771ec e1a05000 [ 49.37] 3ccc e282401c e59f0014 e3a01002 eb000553 e5887000 e1a5 e894aff0 805e8048 [ 49.37] 3cec 806270ac e320f000 e320f000 e320f000 e320f000 e59f2018 e92d4008 e1a03000 [ 49.37] 3d0c e4831004 e1a01003 e5922010 e12fff32 e8bd8008 805e8064 eaf5 e92d0fff [ 49.37] 3d2c e1ad ebf7 e1a0e000 e8bd0fff e1a0f00e e92d4037 e1a04000 e5903014 [ 49.37] 3d4c e59f20b4 e1530002 3a27 e59f20ac e1530002 3a22 ea23 e593 [ 49.37] 3d6c e1a01004 e28d3000 e5840030 e5a13034 eb0003e6 e351 0a03 3a18 [ 49.37] LR: 0x8009c644: [ 49.37] c644 3a02 93a0 83a1 e12fff1e e3e0 e12fff1e e5903000 e5902004 [ 49.37] c664 e353 e2020001 d3a03000 c3a03001 e1d32002 02233001 0003 13a1 [ 49.37] c684 e12fff1e e92d40f8 e1a05000 e1a04001 e1a06002 e1a07003 ea09 e594 [ 49.37] c6a4 e350 0a05 ebfe745a e350 0a02 e1a4 e1a01007 ebfdd73c [ 49.37] c6c4 e284400c e1540006 28bd80f8 e5943008 e1550003 0af0 e8bd80f8 e92d47f0 [ 49.37] c6e4 e1a05000 e5908004 e1a07001 ebff005a e3a0a00c e3c88001 e5954008 e1a06000 [ 49.37] c704 ea08 e5943008 e1a5 e5941004 e5932138 e5933134 e022329a e1a03007 [ 49.37] c724 ebd7 e5944000 e354 1af4 e356 15962138 13a0100c 15963134 [ 49.37] [ 49.37] SP: 0xbe97de88: [ 49.37] de88 0003 be97df08 76e4b000 800e94e8 800d95e0 bf90b5e8 be97df08 [ 49.37] dea8 80413d0c 80030013 be97def4 80413898 8030c164 ea5b [ 49.37] dec8 805e8064 8030c164 806204c8 805e8b7c 806217ac 0001 bb875380 0001 [ 49.37] dee8 0004 001d 0900 be97df08 8009c6c4 80413d0c 80030013 [ 49.37] df08 806204c8 8009c6c4 0001 805e8b7c 0001 7e973898 8009cb24 [ 49.37] df28 bfb00040 0001 802ffe90 be97df90 800cebc0 0041 c1b6 [ 49.37] df48 805e8a18 802fb078 0002 a1ec60e1 fff7 bb875380 0001 0004 [ 49.37] df68 001d 7e973898 be97c000 76e4b000 802fc4f8 0004 0001 [ 49.37] [ 49.37] R0: 0x8030c0e4: [ 49.37] c0e4 e59c200a e0202002 e1811002 e1d320b0 e1dc30b0 e0223003 e1811003 ea08 [ 49.37] c104 e351 1a06 e5941018 e1a02007 e5950094 e351 05941094 ebfcd253 [
[Kernel-packages] [Bug 1269917] Re: Kernel GPF
** 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/1269917 Title: Kernel GPF Status in “linux” package in Ubuntu: Confirmed Bug description: The system was installed with saucy within the last week before this crash. It had been running raring for the prior 3 months or so with no prior kernel crashes. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-15-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Jan 16 19:42:57 2014 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation W2600CR MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=441f20e7-a2de-4bf1-876f-88a6ae0bc41f ro quiet RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2014-01-09 (7 days ago) WifiSyslog: dmi.bios.date: 11/01/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: SE5C600.86B.01.06.0002.110120121539 dmi.board.asset.tag: dmi.board.name: W2600CR dmi.board.vendor: Intel Corporation dmi.board.version: G59236-301 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrSE5C600.86B.01.06.0002.110120121539:bd11/01/2012:svnIntelCorporation:pnW2600CR:pvr:rvnIntelCorporation:rnW2600CR:rvrG59236-301:cvn..:ct17:cvr..: dmi.product.name: W2600CR dmi.product.version: dmi.sys.vendor: Intel Corporation --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-15-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=1400f1e7-aa38-45c7-89f9-656fddf7c3bd IwConfig: Error: [Errno 2] No such file or directory MachineType: Intel Corporation W2600CR MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=441f20e7-a2de-4bf1-876f-88a6ae0bc41f ro quiet ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: Error: [Errno 2] No such file or directory Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-01-09 (7 days ago) UserGroups: dmi.bios.date: 11/01/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: SE5C600.86B.01.06.0002.110120121539 dmi.board.asset.tag: dmi.board.name: W2600CR dmi.board.vendor: Intel Corporation dmi.board.version: G59236-301 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias:
[Kernel-packages] [Bug 1261308] Re: Intel ivy bridge crash on a CI machine executing autopilot tests
** Tags added: ci-engineering -- 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/1261308 Title: Intel ivy bridge crash on a CI machine executing autopilot tests Status in “linux” package in Ubuntu: Confirmed Bug description: A following crash was gotten in CI when running autopilot tests: /var/local/autopilot/autopilot.log: 06:25:06.559 DEBUG globals:155 - Starting: ['/usr/bin/recordmydesktop', '--fps=6', '--no-wm-check', '--no-sound', '--no-frame', '-o', '/var/local/autopilot//videos/autopilot.tests.functional.test_input_stack.TouchGesturesTests.test_pinch_gesture.ogv'] /var/local/autopilot/autopilot.log: 06:25:06.569 INFO __init__:162 - Launching process: ['/usr/bin/qmlscene', '-qt=qt5', '-testability', '/tmp/tmpyErdkz.qml'] /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.717922] kernel BUG at /build/buildd/linux-3.12.0/drivers/gpu/drm/i915/i915_gem.c:4839! /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.736780] Modules linked in: bluetooth veth squashfs aufs nls_utf8 isofs xt_CHECKSUM xt_tcpudp iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc iptable_filter ip_tables x_tables x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crc32_pclmul aesni_intel aes_i586 xts lrw snd_hda_codec_hdmi gf128mul snd_hda_codec_realtek ablk_helper cryptd i915 drm_kms_helper snd_hda_intel snd_hda_codec drm snd_hwdep snd_pcm snd_page_alloc i2c_algo_bit mxm_wmi mei_me snd_timer snd mei soundcore psmouse serio_raw joydev lpc_ich microcode wmi mac_hid video lp parport hid_generic usbhid hid e1000e ahci ptp libahci pps_core /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.822345] Hardware name: /DZ77BH-55K, BIOS BHZ7710H.86A.0097.2012.1228.1346 12/28/2012 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.851440] EIP: 0060:[f901d776] EFLAGS: 00210246 CPU: 2 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.880754] EAX: e6b90270 EBX: e6b90270 ECX: ed4b4000 EDX: ed4b55e0 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.910940] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.941836] Stack: /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.973256] e8921c00 00b4 00c0 e6b90294 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.005758] Call Trace: /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.037812] [c130a8ec] ? _copy_from_user+0x2c/0x40 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.070637] [f9024990] ? i915_gem_execbuffer+0x560/0x560 [i915] /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.104147] [f9024990] ? i915_gem_execbuffer+0x560/0x560 [i915] /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.137652] [f8e2c430] ? drm_copy_field+0x70/0x70 [drm] /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.171153] [c16561af] ? __do_page_fault+0x24f/0x530 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.204938] [c11826c0] SyS_ioctl+0x60/0x80 /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.238719] Code: 39 50 f4 8d 48 cc 75 0a eb 1b 8d 76 00 39 50 f4 74 13 8b 41 34 39 c3 8d 48 cc 75 f1 b8 ff ff ff ff 5b 5d c3 90 8b 41 18 5b 5d c3 0f 0b 90 8d b4 26 00 00 00 00 55 89 e5 56 53 3e 8d 74 26 00 8b /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.367196] ---[ end trace d36900663c323dfa ]--- /var/local/autopilot/autopilot.log: 06:25:33.001 ERROR proxies:410 - Introspect error on :1.180:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. /var/local/autopilot/autopilot.log: 06:25:33.001 DEBUG proxies:413 - Executing introspect queue due to error /home/ubuntu/.cache/upstart/gnome-session.log: WARN 2013-12-16 06:25:32 unity unknown:0 Failed to fetch xid: Timeout was reached /home/ubuntu/.cache/upstart/gnome-session.log: WARN 2013-12-16 06:25:33 unity unknown:0 Failed to fetch type: Timeout was reached /home/ubuntu/.cache/upstart/gnome-session.log: WARN 2013-12-16 06:25:33 unity unknown:0 Failed to fetch monitor: Timeout was reached /home/ubuntu/.cache/upstart/gnome-session.log: WARN 2013-12-16 06:25:34 unity unknown:0 Failed to fetch maximized state: Timeout was reached
Re: [Kernel-packages] [Bug 883029] Re: boot hangs with PANIC: early exception 0d
It seems that this is not a software bug, but was caused by ram that failed intermittently. I removed two ram dimms and the system is now able to boot reliably. Thanks for the follow up. Evan On Nov 11, 2013 7:31 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Evan, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux replace-with-bug-number Also, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.12 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: kernel-bug-exists-upstream kernel-needs-upstream-bug-report ** Tags added: bios-outdated-a58 kernel-bug-exists-upstream-v3.1-rc10 needs-upstream-testing ** Description changed: - After grub the boot stalls on a blank purple splash screen. - I then tried booting with earlyprintk=vga,keep and copied down a stack trace, which I have attached as printk. There were many hex numbers in the printk output which I didn't copy down, but I could if they would be helpful. From the trace it seems that this affects the paging initialization. - This problem occurs *almost* every morning when I boot up my computer. I then power cycle it and usually by the third power cycle it will boot up fine. Also, I have not seen this issue from a reboot after a successful boot; I have only seen it when booting up cold, or after it stalled on the previous boot. - The non-vanilla part of my setup is that it boots from a RAID array controlled by a pci card. - Thanks, - Evan + After grub the boot stalls on a blank purple splash screen. I then tried + booting with earlyprintk=vga,keep and copied down a stack trace, which I + have attached as printk. There were many hex numbers in the printk + output which I didn't copy down, but I could if they would be helpful. + From the trace it seems that this affects the paging initialization. + This problem occurs *almost* every morning when I boot up my computer. I + then power cycle it and usually by the third power cycle it will boot up + fine. Also, I have not seen this issue from a reboot after a successful + boot; I have only seen it when booting up cold, or after it stalled on + the previous boot. The non-vanilla part of my setup is that it boots + from a RAID array controlled by a pci card. + + http://www.evga.com/support/download/default.aspx + Intel 5520/ICH10R ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ward 1966 F pulseaudio /dev/snd/controlC0: ward 1966 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf7bf8000 irq 82' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,,0014' Controls : 39 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfbcfc000 irq 34' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Fri Oct 28 06:57:42 2011
[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 needs bluetooth driver
Is someone actively working on a kernel module to replace the MediaTek driver? Would a polite email campaign, directed at the manufacturer or other parties and requesting that the full source to the driver be released, help with such development at all? -- 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/1189721 Title: Ralink RT3290 needs bluetooth driver Status in “linux” package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189721/+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 1245819] Re: RT3290 driver keeps disconnecting.
Graeme, how long will your connection last before you get a disconnect? I may have the same bug; I'm getting anywhere from 30~90 minutes before losing connection. I will try the 3.12 kernel 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/1245819 Title: RT3290 driver keeps disconnecting. Status in “linux” package in Ubuntu: Confirmed Bug description: Since I upgraded to Saucy my RT3290 wifi disconnects after a while and, cannot reconnect. Networks are visible but connecting fails. Rebooting fixes it for a few minutes, then it disconnects again. dmseg output: [ 2712.692030] wlan0: direct probe to 1c:af:f7:6a:1f:5b (try 1/3) [ 2712.895945] wlan0: direct probe to 1c:af:f7:6a:1f:5b (try 2/3) [ 2713.100176] wlan0: direct probe to 1c:af:f7:6a:1f:5b (try 3/3) [ 2713.304416] wlan0: authentication with 1c:af:f7:6a:1f:5b timed out [ 2713.312581] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2713.312581] Please file bug report to http://rt2x00.serialmonkey.com [ 2713.448643] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2713.448643] Please file bug report to http://rt2x00.serialmonkey.com [ 2714.473932] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2714.473932] Please file bug report to http://rt2x00.serialmonkey.com [ 2719.187137] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2719.187137] Please file bug report to http://rt2x00.serialmonkey.com [ 2720.212474] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2720.212474] Please file bug report to http://rt2x00.serialmonkey.com [ 2722.214667] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2722.214667] Please file bug report to http://rt2x00.serialmonkey.com [ 2723.236836] wlan0: authenticate with 1c:af:f7:6a:1f:5b [ 2723.243918] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2723.243918] Please file bug report to http://rt2x00.serialmonkey.com [ 2723.244032] wlan0: direct probe to 1c:af:f7:6a:1f:5b (try 1/3) [ 2723.448094] wlan0: direct probe to 1c:af:f7:6a:1f:5b (try 2/3) [ 2723.652289] wlan0: direct probe to 1c:af:f7:6a:1f:5b (try 3/3) [ 2723.856508] wlan0: authentication with 1c:af:f7:6a:1f:5b timed out [ 2723.872653] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2723.872653] Please file bug report to http://rt2x00.serialmonkey.com [ 2724.008668] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2724.008668] Please file bug report to http://rt2x00.serialmonkey.com [ 2725.033954] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2725.033954] Please file bug report to http://rt2x00.serialmonkey.com [ 2730.067660] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2730.067660] Please file bug report to http://rt2x00.serialmonkey.com [ 2731.092941] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0 [ 2731.092941] Please file bug report to http://rt2x00.serialmonkey.com --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2157 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (166 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 9: phy9: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-26 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6
[Kernel-packages] [Bug 1238494] Re: Kernel panic on 3.8.0-29 when using ipvs
I can confirm that this kernel fixes the problem for me as well, including with the new keepalived build from precise-proposed which fixes this bug https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876 -- 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/1238494 Title: Kernel panic on 3.8.0-29 when using ipvs Status in “linux” package in Ubuntu: Confirmed Bug description: In kernel 3.8.0-29 and higher (I've tested 3.8.0-30 and 3.8.0-31), the kernel panics when adding IPVS service. Specifically, when I execute the following command: sudo ipvsadm -A -u 10.0.50.4:53 The kernel immediately panics. I've reverted the kernel to 3.8.0-27, and IPVS executes without a problem. The panic is completely reproducable, using a clean install, no extra packages installed, all packages upgraded. I've attached the apport report of the system running 3.8.0-29. Best, Luc van Donkersgoed --- AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Oct 11 10:04 seq crw-rw---T 1 root audio 116, 33 Oct 11 10:04 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.9.2-0ubuntu8.3 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 DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=566497ef-0abf-42f0-85ee-988bf9ba2034 InstallationDate: Installed on 2012-12-03 (311 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-31-generic root=/dev/mapper/dnslb01-root ro ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: Error: [Errno 2] No such file or directory Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-10-10 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/22/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd06/22/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1238494/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Well, between the new bios, new firmware, and 3.11.3 kernel (whose changelog includes a whole mess of radeon-related fixes) something seems to have fixed this. I haven't had any lock-ups at all in a few days now (and the only suspend-related bug I see now is #1184262 which is entirely unrelated). ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Fix Released Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
I actually haven't seen the suspend hang since updating the bios, though that could still just be dumb luck. I *am* still seeing the lock-ups as per comment #8, though they don't trigger apport for some reason. I am currently installing the updated firmware package (bug #1218691 or my comment #7 on this bug) so we'll see if that makes a difference. -- 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/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
I have just updated to the latest bios, as indicated by the dmidecode output: 1.0.18 02/24/2009 I will post back if/when I reproduce the issue again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1219238] [NEW] suspend/resume failure
*** This bug is a duplicate of bug 1212041 *** https://bugs.launchpad.net/bugs/1212041 Public bug reported: Duplicate of #1212041 with later kernel (rc7) in case the updated trace is useful. ProblemType: KernelOops 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 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Fri Aug 30 22:03:32 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (706 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (84 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume saucy suspend ** This bug has been marked a duplicate of bug 1212041 suspend/resume failure, Dell Inspiron 530 -- 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/1219238 Title: suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: Duplicate of #1212041 with later kernel (rc7) in case the updated trace is useful. ProblemType: KernelOops 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 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Fri Aug 30 22:03:32 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (706 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (84 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219238/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Still occurs with rc7 (I filed a dupe and marked it as such, in case the updated apport trace is useful). Moving back to Confirmed since I have provided all the information I can think to provide at this point. Joseph, Christopher, please advise on next steps. ** Changed in: linux (Ubuntu) Status: Incomplete = New ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Confirmed Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Currently installing the first of the bisect kernels. Just a note that during the install I get: W: Possible missing firmware /lib/firmware/radeon/KAVERI_sdma.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_rlc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_mec.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_ce.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_me.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_pfp.bin for module radeon from the update-initramfs run. -- 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/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Given that, and the fact that 3.11 includes major radeon changes (in the form of DPM) and the fact that I have a radeon graphics card, I would put money on a radeon driver regression. Tangentially: every time I try and shut-down I get a hard hang as well (with the current kernel, not yet the bisect kernel). Possibly a different symptom of the same bug. It doesn't seem to be triggering an apport hook though... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Skimming the linux git changes since rc6 (on which the current saucy kernel is based) show a couple of radeon-related fixes, but nothing that claims to be relevant to my r6xx card. I don't currently have much hope that rc7 will fix anything when it lands. -- 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/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Both -rc4 and -rc2 are substantially worse: -rc4 freezes hard immediately on boot-up, it never gets past loading initial ramdisk. Modesetting never kicks in. Sysrq+reisub does nothing, I have to kill the power. -rc2 boots, but freezes hard immediately on suspend (going in, whereas the current kernel freezes coming out). Screen goes black, but backlight stays on. One of two fans stops but other stays on. Power light stays solid (should start blinking). Sysrq+reisub does nothing, I have to kill the power. Continuing tangent: with the current kernel, if I sudo restart lightdm and then shutdown from the log-in screen it works. Definitely seems like an X-related thing... -- 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/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Unfortunately I have not experienced this bug since originally filing it here (so I have not yet started a bisect). It does not appear to be reliably reproducable even on the same kernel version. If I can get it to happen with any regularity I will try bisecting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] [NEW] suspend/resume failure
Public bug reported: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops regression-release resume saucy suspend -- 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/1212041 Title: suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure
** Tags added: regression-release -- 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/1212041 Title: suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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 1212041] Re: suspend/resume failure, Dell Inspiron 530
Looking at the changelog for the BIOS, there do not appear to be any related fixes between 1.0.15 and 1.0.18 so I highly doubt the upgrade will fix the issue (which does not seem consistently reproducable anyways). I will do it to be sure, but it may take me a while to get around to it. -- 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/1212041 Title: suspend/resume failure, Dell Inspiron 530 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend appeard to work fine. Resume came back, monitor backlight turned on and disk spun a bit, but no visible graphics or reaction to input. Had to alt+sysrq+reisub to force a reboot. This is a regression since the update to kernel 3.11.0 a few days ago. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 20:15:07 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2011-09-24 (689 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=60269649-642d-4672-83bb-7bfadaae6e31 ro quiet splash vt.handoff=7 SourcePackage: linux Title: suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-06-08 (66 days ago) UserGroups: dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212041/+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
