[Kernel-packages] [Bug 1351353] Re: Kernel oops
@Chris - I'm not an expert at reading kernel stack traces, but I don't think the oops stacktrace looks related to kvm. I just mentioned that I was using kvm when the oops occurred (*). I've edited the title accordingly. (*) - I know this since I have a script which warns me as soon as an oops is generated. ** Summary changed: - Kernel oops related to running kvm (?) + Kernel oops -- 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/1351353 Title: Kernel oops Status in “linux” package in Ubuntu: Confirmed Bug description: My system suddently became unresponsive so I tried to SysRq s/u/b and I think that's what caused another problem. Either way, my system hard-locked. Aug 1 16:15:59 faire kernel: [31778.831601] [ cut here ] Aug 1 16:15:59 faire kernel: [31778.831644] WARNING: CPU: 2 PID: 1834 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3313 intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]() Aug 1 16:15:59 faire kernel: [31778.831646] Modules linked in: cdc_acm ums_cypress btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi joydev binfmt_misc serio_raw iwlmvm mac80211 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep lpc_ich rtsx_pci_ms iwlwifi memstick snd_pcm cfg80211 uvcvideo videobuf2_vmalloc videobuf2_memops shpchp videobuf2_core v4l2_common mei_me videodev mei media thinkpad_acpi nvram btusb snd_seq_midi snd_seq_midi_event bluetooth snd_rawmidi 6lowpan_iphc snd_seq snd_seq_device snd_timer snd intel_smartconnect soundcore cuse parport_pc mac_hid ppdev lp parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core i2c_algo_bit drm_kms_helper wmi drm video Aug 1 16:15:59 faire kernel: [31778.831718] CPU: 2 PID: 1834 Comm: Xorg Not tainted 3.16.0-6-generic #11-Ubuntu Aug 1 16:15:59 faire kernel: [31778.831720] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 Aug 1 16:15:59 faire kernel: [31778.831721] 0009 8800d6233c10 82755538 Aug 1 16:15:59 faire kernel: [31778.831724] 8800d6233c48 8206bb0d 880308eed000 Aug 1 16:15:59 faire kernel: [31778.831726] 880304108240 8800da1e1000 8800da1e1000 8800d6233c58 Aug 1 16:15:59 faire kernel: [31778.831729] Call Trace: Aug 1 16:15:59 faire kernel: [31778.831735] [] dump_stack+0x45/0x56 Aug 1 16:15:59 faire kernel: [31778.831739] [] warn_slowpath_common+0x7d/0xa0 Aug 1 16:15:59 faire kernel: [31778.831742] [] warn_slowpath_null+0x1a/0x20 Aug 1 16:15:59 faire kernel: [31778.831765] [] intel_crtc_wait_for_pending_flips+0x171/0x180 [i915] Aug 1 16:15:59 faire kernel: [31778.831769] [] ? prepare_to_wait_event+0x100/0x100 Aug 1 16:15:59 faire kernel: [31778.831787] [] intel_crtc_disable_planes+0x33/0x1c0 [i915] Aug 1 16:15:59 faire kernel: [31778.831790] [] ? __ww_mutex_lock+0x1b/0x97 Aug 1 16:15:59 faire kernel: [31778.831807] [] haswell_crtc_disable+0x55/0x2f0 [i915] Aug 1 16:15:59 faire kernel: [31778.831809] [] ? mutex_lock+0x12/0x2f Aug 1 16:15:59 faire kernel: [31778.831823] [] intel_crtc_update_dpms+0x67/0xa0 [i915] Aug 1 16:15:59 faire kernel: [31778.831835] [] intel_connector_dpms+0x59/0x70 [i915] Aug 1 16:15:59 faire kernel: [31778.831848] [] drm_mode_obj_set_property_ioctl+0x39f/0x3b0 [drm] Aug 1 16:15:59 faire kernel: [31778.831858] [] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] Aug 1 16:15:59 faire kernel: [31778.831860] [] ? ipv4_conntrack_defrag+0xb0/0x163 [nf_defrag_ipv4] Aug 1 16:15:59 faire kernel: [31778.831868] [] drm_ioctl+0x1ec/0x660 [drm] Aug 1 16:15:59 faire kernel: [31778.831873] [] do_vfs_ioctl+0x2e0/0x4c0 Aug 1 16:15:59 faire kernel: [31778.831876] [] ? vtime_account_user+0x54/0x60 Aug 1 16:15:59 faire kernel: [31778.831878] [] SyS_ioctl+0x81
[Kernel-packages] [Bug 1322824] Re: [Gigabyte GA-H55M-USB3] Kernel panic
We have updated BIOS, another kernel-panic appeared today. Trace screenshot (with KVM) and apport report attached. ** Changed in: linux (Ubuntu) Status: Expired => New ** Attachment added: "bs2_panic.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322824/+attachment/4170103/+files/bs2_panic.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/1322824 Title: [Gigabyte GA-H55M-USB3] Kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: A Ubuntu 14.04 server died with a kernel panic with this stacktrace: [245407.543823] Call Trace: [249407.544937] [] dunp_stack+0x45/0x56 [249407.546067] [] uarn_sloupath_common+0x7d/0xa0 [249407.547173] [] uarn_sloupath_null+0x1a/0x20 [249407.548257] [] natiue_smp_send_reschedule+0x5d/0x60 [249407.549341] [] trigger_load_balance+0x16a/0x1e0 [249407.550416] [] scheduler_tick+0xa4/0xf0 [249407.551484] [] update_process_times+0x60/0x70 [249407.552550] [] tick_sched_handle.isra.17+0x2S/0x60 [249407.553608] [] tick_sched_timer+0x41/0x60 [249407.554671] [] __run_hrtimer+0x77/0x1d0 [249407.555728] [] ? tick_sched_handle.isra.17+0x60/0x60 [249407.556785] [] hrtimer_interrupt+0xef/0x230 [249407.557842] [] local_apic_tiner_interrupt+0x37/0x60 [249407.558900] [] smp_apic_tiner_interrupt+0x3f/0x60 [249407.559955] [] apic_tiner_interrupt+0x6d/0x80 [249407.561023] [] ? intel_crtc_set_config+0x668/0x9a0 [i915] [249407.562092] [] ? panic+0x193/0x1d7 [249407.563156] [] oops_end+0x139/0x150 [249407.564214] [] no_context+0x27e/0x28b [249407.565270] [] __bad_area_nosemaphore+0x73/0x1ca [249407.566327] [] bad_area_nosemaphore+0x13/0x15 [249407.567377] [] __do_page_fault+0xa7/0x560 [249407.568429] [] ? tcp_u4_rcu+0x664/0x7a0 [249407.569479] [] ? ip_1ocal_deliuer_finish+0xa8/0x210 [249407.570531] [] ? ip_local_deliuer+0x48/0x80 [249407.571575] [] ? ip_rcu_finish+0x7d/0x350 [249407.572613] [] do_page_fault+0x1a/0x70 [249407.573606] [] page_fault+0x28/0x30 [249407.574528] [] ? rtl8169_poll+0x22a/0x680 [r8169] [249407.575437] [] ? natiue_sched_c1ock+0x13/0x80 [249407.576339] [] net_rx_nction+0x152/0x250 [249407.577246] [] __do_softirq+0xec/0x2c0 [249407.578149] [] irq_cxit+0x105/0x110 [249407.579049] [] do_IRQ+0x56/0xc0 [249407.579943] [] common_interrupt+0x6d/0x6d [249407.580835] (EOI) [] ? cpuidle_cnter_state+0x4f/0xc0 [249407.581731] [] cpuidle_idle_call+0xb9/0x1f0 [249407.582593] [] arch_cpu_idle+0xe/0x30 [249407.583421] [] cpu_startup_entry+0xc5/0x290 [249407.584226] [] rest_init+0x77/0x80 [249407.585010] [] start_kernel+0x438/0x443 [249407.585772] [] ? repair_cnu_string+0x5c/0x5c [249407.586521] [] ? early_idt_handlers+0x120/0x120 [249407.587257] [] x86_64_start_reseruations+0x2a/0x2c [249407.587979] [] x86_64_start_kernel+0x143/0x152 [249407.588687] ---[ and trace 05db40b9a357e3e2 ]--- uname -a Linux bayanbox2 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The stackstrace is OCRed from screenshot of server (via KVM) and may be contains some spelling errors (original screenshot is attached). Also this stacktrace did not appeared in any log files. The apport server information is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322824/+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 1322824] Re: [Gigabyte GA-H55M-USB3] Kernel panic
** Attachment added: "apport.linux-image-3.13.0-24-generic.l5ww69wl.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322824/+attachment/4170105/+files/apport.linux-image-3.13.0-24-generic.l5ww69wl.apport -- 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/1322824 Title: [Gigabyte GA-H55M-USB3] Kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: A Ubuntu 14.04 server died with a kernel panic with this stacktrace: [245407.543823] Call Trace: [249407.544937] [] dunp_stack+0x45/0x56 [249407.546067] [] uarn_sloupath_common+0x7d/0xa0 [249407.547173] [] uarn_sloupath_null+0x1a/0x20 [249407.548257] [] natiue_smp_send_reschedule+0x5d/0x60 [249407.549341] [] trigger_load_balance+0x16a/0x1e0 [249407.550416] [] scheduler_tick+0xa4/0xf0 [249407.551484] [] update_process_times+0x60/0x70 [249407.552550] [] tick_sched_handle.isra.17+0x2S/0x60 [249407.553608] [] tick_sched_timer+0x41/0x60 [249407.554671] [] __run_hrtimer+0x77/0x1d0 [249407.555728] [] ? tick_sched_handle.isra.17+0x60/0x60 [249407.556785] [] hrtimer_interrupt+0xef/0x230 [249407.557842] [] local_apic_tiner_interrupt+0x37/0x60 [249407.558900] [] smp_apic_tiner_interrupt+0x3f/0x60 [249407.559955] [] apic_tiner_interrupt+0x6d/0x80 [249407.561023] [] ? intel_crtc_set_config+0x668/0x9a0 [i915] [249407.562092] [] ? panic+0x193/0x1d7 [249407.563156] [] oops_end+0x139/0x150 [249407.564214] [] no_context+0x27e/0x28b [249407.565270] [] __bad_area_nosemaphore+0x73/0x1ca [249407.566327] [] bad_area_nosemaphore+0x13/0x15 [249407.567377] [] __do_page_fault+0xa7/0x560 [249407.568429] [] ? tcp_u4_rcu+0x664/0x7a0 [249407.569479] [] ? ip_1ocal_deliuer_finish+0xa8/0x210 [249407.570531] [] ? ip_local_deliuer+0x48/0x80 [249407.571575] [] ? ip_rcu_finish+0x7d/0x350 [249407.572613] [] do_page_fault+0x1a/0x70 [249407.573606] [] page_fault+0x28/0x30 [249407.574528] [] ? rtl8169_poll+0x22a/0x680 [r8169] [249407.575437] [] ? natiue_sched_c1ock+0x13/0x80 [249407.576339] [] net_rx_nction+0x152/0x250 [249407.577246] [] __do_softirq+0xec/0x2c0 [249407.578149] [] irq_cxit+0x105/0x110 [249407.579049] [] do_IRQ+0x56/0xc0 [249407.579943] [] common_interrupt+0x6d/0x6d [249407.580835] (EOI) [] ? cpuidle_cnter_state+0x4f/0xc0 [249407.581731] [] cpuidle_idle_call+0xb9/0x1f0 [249407.582593] [] arch_cpu_idle+0xe/0x30 [249407.583421] [] cpu_startup_entry+0xc5/0x290 [249407.584226] [] rest_init+0x77/0x80 [249407.585010] [] start_kernel+0x438/0x443 [249407.585772] [] ? repair_cnu_string+0x5c/0x5c [249407.586521] [] ? early_idt_handlers+0x120/0x120 [249407.587257] [] x86_64_start_reseruations+0x2a/0x2c [249407.587979] [] x86_64_start_kernel+0x143/0x152 [249407.588687] ---[ and trace 05db40b9a357e3e2 ]--- uname -a Linux bayanbox2 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The stackstrace is OCRed from screenshot of server (via KVM) and may be contains some spelling errors (original screenshot is attached). Also this stacktrace did not appeared in any log files. The apport server information is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322824/+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 1322824] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1322824 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322824 Title: [Gigabyte GA-H55M-USB3] Kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: A Ubuntu 14.04 server died with a kernel panic with this stacktrace: [245407.543823] Call Trace: [249407.544937] [] dunp_stack+0x45/0x56 [249407.546067] [] uarn_sloupath_common+0x7d/0xa0 [249407.547173] [] uarn_sloupath_null+0x1a/0x20 [249407.548257] [] natiue_smp_send_reschedule+0x5d/0x60 [249407.549341] [] trigger_load_balance+0x16a/0x1e0 [249407.550416] [] scheduler_tick+0xa4/0xf0 [249407.551484] [] update_process_times+0x60/0x70 [249407.552550] [] tick_sched_handle.isra.17+0x2S/0x60 [249407.553608] [] tick_sched_timer+0x41/0x60 [249407.554671] [] __run_hrtimer+0x77/0x1d0 [249407.555728] [] ? tick_sched_handle.isra.17+0x60/0x60 [249407.556785] [] hrtimer_interrupt+0xef/0x230 [249407.557842] [] local_apic_tiner_interrupt+0x37/0x60 [249407.558900] [] smp_apic_tiner_interrupt+0x3f/0x60 [249407.559955] [] apic_tiner_interrupt+0x6d/0x80 [249407.561023] [] ? intel_crtc_set_config+0x668/0x9a0 [i915] [249407.562092] [] ? panic+0x193/0x1d7 [249407.563156] [] oops_end+0x139/0x150 [249407.564214] [] no_context+0x27e/0x28b [249407.565270] [] __bad_area_nosemaphore+0x73/0x1ca [249407.566327] [] bad_area_nosemaphore+0x13/0x15 [249407.567377] [] __do_page_fault+0xa7/0x560 [249407.568429] [] ? tcp_u4_rcu+0x664/0x7a0 [249407.569479] [] ? ip_1ocal_deliuer_finish+0xa8/0x210 [249407.570531] [] ? ip_local_deliuer+0x48/0x80 [249407.571575] [] ? ip_rcu_finish+0x7d/0x350 [249407.572613] [] do_page_fault+0x1a/0x70 [249407.573606] [] page_fault+0x28/0x30 [249407.574528] [] ? rtl8169_poll+0x22a/0x680 [r8169] [249407.575437] [] ? natiue_sched_c1ock+0x13/0x80 [249407.576339] [] net_rx_nction+0x152/0x250 [249407.577246] [] __do_softirq+0xec/0x2c0 [249407.578149] [] irq_cxit+0x105/0x110 [249407.579049] [] do_IRQ+0x56/0xc0 [249407.579943] [] common_interrupt+0x6d/0x6d [249407.580835] (EOI) [] ? cpuidle_cnter_state+0x4f/0xc0 [249407.581731] [] cpuidle_idle_call+0xb9/0x1f0 [249407.582593] [] arch_cpu_idle+0xe/0x30 [249407.583421] [] cpu_startup_entry+0xc5/0x290 [249407.584226] [] rest_init+0x77/0x80 [249407.585010] [] start_kernel+0x438/0x443 [249407.585772] [] ? repair_cnu_string+0x5c/0x5c [249407.586521] [] ? early_idt_handlers+0x120/0x120 [249407.587257] [] x86_64_start_reseruations+0x2a/0x2c [249407.587979] [] x86_64_start_kernel+0x143/0x152 [249407.588687] ---[ and trace 05db40b9a357e3e2 ]--- uname -a Linux bayanbox2 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The stackstrace is OCRed from screenshot of server (via KVM) and may be contains some spelling errors (original screenshot is attached). Also this stacktrace did not appeared in any log files. The apport server information is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322824/+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 1322824] Re: [Gigabyte GA-H55M-USB3] Kernel panic
** 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/1322824 Title: [Gigabyte GA-H55M-USB3] Kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: A Ubuntu 14.04 server died with a kernel panic with this stacktrace: [245407.543823] Call Trace: [249407.544937] [] dunp_stack+0x45/0x56 [249407.546067] [] uarn_sloupath_common+0x7d/0xa0 [249407.547173] [] uarn_sloupath_null+0x1a/0x20 [249407.548257] [] natiue_smp_send_reschedule+0x5d/0x60 [249407.549341] [] trigger_load_balance+0x16a/0x1e0 [249407.550416] [] scheduler_tick+0xa4/0xf0 [249407.551484] [] update_process_times+0x60/0x70 [249407.552550] [] tick_sched_handle.isra.17+0x2S/0x60 [249407.553608] [] tick_sched_timer+0x41/0x60 [249407.554671] [] __run_hrtimer+0x77/0x1d0 [249407.555728] [] ? tick_sched_handle.isra.17+0x60/0x60 [249407.556785] [] hrtimer_interrupt+0xef/0x230 [249407.557842] [] local_apic_tiner_interrupt+0x37/0x60 [249407.558900] [] smp_apic_tiner_interrupt+0x3f/0x60 [249407.559955] [] apic_tiner_interrupt+0x6d/0x80 [249407.561023] [] ? intel_crtc_set_config+0x668/0x9a0 [i915] [249407.562092] [] ? panic+0x193/0x1d7 [249407.563156] [] oops_end+0x139/0x150 [249407.564214] [] no_context+0x27e/0x28b [249407.565270] [] __bad_area_nosemaphore+0x73/0x1ca [249407.566327] [] bad_area_nosemaphore+0x13/0x15 [249407.567377] [] __do_page_fault+0xa7/0x560 [249407.568429] [] ? tcp_u4_rcu+0x664/0x7a0 [249407.569479] [] ? ip_1ocal_deliuer_finish+0xa8/0x210 [249407.570531] [] ? ip_local_deliuer+0x48/0x80 [249407.571575] [] ? ip_rcu_finish+0x7d/0x350 [249407.572613] [] do_page_fault+0x1a/0x70 [249407.573606] [] page_fault+0x28/0x30 [249407.574528] [] ? rtl8169_poll+0x22a/0x680 [r8169] [249407.575437] [] ? natiue_sched_c1ock+0x13/0x80 [249407.576339] [] net_rx_nction+0x152/0x250 [249407.577246] [] __do_softirq+0xec/0x2c0 [249407.578149] [] irq_cxit+0x105/0x110 [249407.579049] [] do_IRQ+0x56/0xc0 [249407.579943] [] common_interrupt+0x6d/0x6d [249407.580835] (EOI) [] ? cpuidle_cnter_state+0x4f/0xc0 [249407.581731] [] cpuidle_idle_call+0xb9/0x1f0 [249407.582593] [] arch_cpu_idle+0xe/0x30 [249407.583421] [] cpu_startup_entry+0xc5/0x290 [249407.584226] [] rest_init+0x77/0x80 [249407.585010] [] start_kernel+0x438/0x443 [249407.585772] [] ? repair_cnu_string+0x5c/0x5c [249407.586521] [] ? early_idt_handlers+0x120/0x120 [249407.587257] [] x86_64_start_reseruations+0x2a/0x2c [249407.587979] [] x86_64_start_kernel+0x143/0x152 [249407.588687] ---[ and trace 05db40b9a357e3e2 ]--- uname -a Linux bayanbox2 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The stackstrace is OCRed from screenshot of server (via KVM) and may be contains some spelling errors (original screenshot is attached). Also this stacktrace did not appeared in any log files. The apport server information is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322824/+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 41301]
I've been able to reproduce this by opening a terminal, then opening mouse settings. By removing my G930 headset USB dongle however, the problem doesn't happen. Each time I open mouse settings with the dongle, the problem happens, and each time I open the settings without the dongle everything is fine. -- 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/41301 Title: PS/2 Logitech MX310 clicks stop working sporadically Status in X.Org X server: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in Debian GNU/Linux: Confirmed Bug description: This bug is a long standing one for me in Dapper but it becomes more and more frequent in recent Dapper beta. Unfortunatly, there's no way I can reproduce it. Symptoms : the mouse buttons (all of them) stop working without any reason. Seems to happen mainly when surfing with Epiphany but not only. In fact, it's just like my mouse was in another dimension. I use "focus follow pointer" and it doesn't work anymore. I can see my cursor and moving it : the system just ignore it. No more click, no more focus following pointer. Also, the keyboard keeps working perfectly. By using shortcut keys, I can continue working normally. The workaround to have the mouse again is hopefully very simple : use the change desktop shortcut. The alt-tab shortcut is also working. Yes, it's strange, but they are the only two shortcuts I've found that bypass this bug ! Strange isn't it ? My mouse is a PS/2 Logitech MX310. The workaround seems to be the proof that it's not an hardware failure. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/41301/+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 1261851] Re: [Gigabyte EP45-UD3L] CPU frequency reported incorrectly after overclocking
Hello, this bug seems to still be present in 14.10 development. CPU: Intel Pentium G3258 MB: Gigabyte Z97N-Gaming 5 I'm not sure whether this is purely a cosmetic issue, or if Ubuntu is actually overriding the CPU frequency -- 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/1261851 Title: [Gigabyte EP45-UD3L] CPU frequency reported incorrectly after overclocking Status in “linux” package in Ubuntu: Confirmed Bug description: The stock speed of Intel E3300 is 2.5 GHz (200*12.5). I had pushed the FSB from 200 MHz to 300 MHz in the BIOS, giving 3.75 GHz (300*12.5). However, "cat /proc/cpuinfo" and "cpufreq-info" incorrectly shows 3.33, 2.67, 2.13, 1.6 GHz, which are probably based on 266 MHz FSB (266*12.5=3.33, 266*10=2.67, 266*8=2.13, 266*6=1.6). "dmidecode --type processor" shows it at 3.75 GHz all the time, no matter which frequency or governor was selected in CPU Frequency Scaling Monitor. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-35-generic 3.8.0-35.50 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: jkuang 2308 F pulseaudio /dev/snd/controlC3: jkuang 2308 F pulseaudio /dev/snd/controlC2: jkuang 2308 F pulseaudio /dev/snd/controlC0: jkuang 2308 F pulseaudio Date: Tue Dec 17 11:16:02 2013 InstallationDate: Installed on 2012-02-02 (684 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic root=UUID=9809d504-4a1e-433d-8cdb-269df2cdb3e2 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-35-generic N/A linux-backports-modules-3.8.0-35-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-07 (254 days ago) dmi.bios.date: 01/27/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: EP45-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP45-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261851/+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 1352778] [NEW] bluetooth does not stay off (aka setting does not persist across reboot)
You have been subscribed to a public bug: If I disable bluetooth, and reboot the phone, bluetooth is enabled again. Outcome: - a surprised user. - increased and unnecessary battery drain. - increased phone attack surface. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- bluetooth does not stay off (aka setting does not persist across reboot) https://bugs.launchpad.net/bugs/1352778 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352778] Re: bluetooth does not stay off (aka setting does not persist across reboot)
thanks but settings is an UI, not a service running on boot, it can't be what restore the status on start, reassigning to bluez but not sure if that's the right component ** Package changed: ubuntu-system-settings (Ubuntu) => bluez (Ubuntu) -- 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/1352778 Title: bluetooth does not stay off (aka setting does not persist across reboot) Status in “bluez” package in Ubuntu: New Bug description: If I disable bluetooth, and reboot the phone, bluetooth is enabled again. Outcome: - a surprised user. - increased and unnecessary battery drain. - increased phone attack surface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1352778/+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 1335795] Re: [Asus K55VM] It does not suspend after upgrading to 14.04
Christian Gonzalez, please do not mark this bug a duplicate of any other or vice versa. ** This bug is no longer a duplicate of bug 1324697 Suspend fails with kernel 3.13.0-27 and nouveau drivers -- 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/1335795 Title: [Asus K55VM] It does not suspend after upgrading to 14.04 Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Ubuntu 14.04 from 13.10 After that my laptop does not suspend. The laptop has NVIDIA GEFORCE GT 630M Graphic card, with nouveau. It seems to fails when suspending. nisarg@nisarg:~$ cat /proc/version_signature Ubuntu 3.13.0-30.54-generic 3.13.11.2 Here is the syslog. Jun 30 14:52:22 nisarg kernel: [10157.974142] PM: Syncing filesystems ... done. Jun 30 14:52:22 nisarg kernel: [10158.308806] PM: Preparing system for mem sleep Jun 30 14:52:27 nisarg kernel: [10158.558616] Freezing user space processes ... (elapsed 0.001 seconds) done. Jun 30 14:52:27 nisarg kernel: [10158.560394] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jun 30 14:52:27 nisarg kernel: [10158.561577] PM: Entering mem sleep Jun 30 14:52:27 nisarg kernel: [10158.561870] Suspending console(s) (use no_console_suspend to debug) Jun 30 14:52:27 nisarg kernel: [10158.562061] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jun 30 14:52:27 nisarg kernel: [10158.562117] sd 0:0:0:0: [sda] Stopping disk Jun 30 14:52:27 nisarg kernel: [10158.580826] nouveau [ DRM] suspending display... Jun 30 14:52:27 nisarg kernel: [10158.580828] nouveau [ DRM] unpinning framebuffer(s)... Jun 30 14:52:27 nisarg kernel: [10158.580831] nouveau [ DRM] evicting buffers... Jun 30 14:52:27 nisarg kernel: [10158.580832] nouveau [ DRM] waiting for kernel channels to go idle... Jun 30 14:52:27 nisarg kernel: [10158.580876] nouveau [ DRM] suspending client object trees... Jun 30 14:52:27 nisarg kernel: [10158.581164] nouveau [ DRM] suspending kernel object tree... Jun 30 14:52:27 nisarg kernel: [10160.580652] nouveau E[ PDISP][:01:00.0][0xc000857c][8802225fd700] fini timeout, 0xc2071008 Jun 30 14:52:27 nisarg kernel: [10160.580654] nouveau E[ PDISP][:01:00.0][0xc000857c][8802225fd700] failed suspend, -16 Jun 30 14:52:27 nisarg kernel: [10160.580655] nouveau E[ DRM] 0xd150:0xd15c7c00 suspend failed with -16 Jun 30 14:52:27 nisarg kernel: [10160.580696] nouveau E[ DRM] 0x:0xd150 suspend failed with -16 Jun 30 14:52:27 nisarg kernel: [10160.580797] nouveau E[ DRM] 0x:0x suspend failed with -16 Jun 30 14:52:27 nisarg kernel: [10160.581459] nouveau E[ DRM] 0x:0x suspend failed with -16 Jun 30 14:52:27 nisarg kernel: [10160.581559] nouveau [ DRM] resuming display... Jun 30 14:52:27 nisarg kernel: [10160.581578] nouveau E[ DRM] bo 8801f711e800 pinned elsewhere: 0x0002 vs 0x0004 Jun 30 14:52:27 nisarg kernel: [10160.581579] [drm:drm_helper_resume_force_mode] *ERROR* failed to set mode on crtc 8800befd1000 Jun 30 14:52:27 nisarg kernel: [10160.595633] pci_pm_suspend(): nouveau_pmops_suspend+0x0/0xb0 [nouveau] returns -16 Jun 30 14:52:27 nisarg kernel: [10160.595638] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 Jun 30 14:52:27 nisarg kernel: [10160.595642] PM: Device :01:00.0 failed to suspend async: error -16 Jun 30 14:52:27 nisarg kernel: [10160.595703] PM: Some devices failed to suspend, or early wake event detected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-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: nisarg 3437 F pulseaudio nisarg19771 F pulseaudio CRDA: country IN: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 20) CurrentDesktop: Unity Date: Mon Jun 30 15:05:58 2014 HibernationDevice: RESUME=UUID=8d9c6f2d-29cc-443a-8864-b5bdc278d3f5 InstallationDate: Installed on 2014-01-08 (172 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. K55VM ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=33430ee0-8da8-4984-9369-153bf9f4aa34 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 SourcePackage: linu
[Kernel-packages] [Bug 1324697] Re: Suspend fails with kernel 3.13.0-27 and nouveau drivers
Christian Gonzalez, please do not toggle the bug title, or the Status, as this report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Summary changed: - Suspend fails with kernel 3.13.0-27 and nouveau drivers + [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails with - kernel 3.13.0-27 -- 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/1324697 Title: [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails with - kernel 3.13.0-27 Status in “linux” package in Ubuntu: Incomplete Bug description: See: http://askubuntu.com/questions/473214/laptop-suspend-broken-after- latest-kernel-update where it was suggested i file a kernel bug report. short version: after kernel upgrade to 3.13.0-27 my laptop will no longer suspend. Note that the apport bug report was generated while running 3.13.0-24 (had to switch back, this is my ever-day-use computer). I noted which log files changed before and after a suspend attempt, and those changes are attached (suspend.out). I compared these to a suspend with the -24 kernel and noted the changes in the referenced askubuntu post. Please let me know if i can provide any more details! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: conrad 2293 F pulseaudio Date: Thu May 29 17:20:15 2014 HibernationDevice: RESUME=UUID=eb2b25c8-5489-484c-b3d1-b0db8834 InstallationDate: Installed on 2013-02-14 (469 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b2f1b8ee-6793-4070-8eb3-a07e52b30d03 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-18 (41 days ago) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181D dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packard:rn181D:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 078F1020572620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324697/+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 1337641] Re: Oculus Rift "drifts" on recent kernels
** Tags added: needs-bisect needs-upstream-testing -- 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/1337641 Title: Oculus Rift "drifts" on recent kernels Status in “linux” package in Ubuntu: Confirmed Bug description: When running Oculus Rift compatible software, the HMD rotation seen by software drifts by a few degrees per second, even when the HMD is not moving at all (ie, it's sitting perfectly still on the desk). This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24 prevents the bug from happening. The bug happens after using the OR in hidraw mode (which is what the OVR SDK uses), and will even persist if you reboot into Windows without power cycling the device. OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD in libusb mode the problem does not happen, unless you have previously used some software which opens the OR in hidraw mode. OpenHMD can also be compiled to use hidraw, and if you do that it just shows a black screen with the example. If you then run it in libusb mode, the drift happens. This bug has been reported on the Oculus forums: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689 To me this looks like a HID bug. Something is messing up the state of the hardware so badly that it will continue to report bad data even when using software that works correctly after a power cycle. Looking at the commits between -24 and -27 kernels I see a bunch of commits to HID which look like they might be responsible for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al 1999 F pulseaudio /dev/snd/controlC1: al 1999 F pulseaudio /dev/snd/controlC0: al 1999 F pulseaudio CurrentDesktop: XFCE Date: Fri Jul 4 01:07:13 2014 HibernationDevice: RESUME=UUID=cd4b4f29-2984-430a-8556-26b5fd58d903 InstallationDate: Installed on 2014-06-29 (4 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=06500b4e-b446-411c-9a19-cfff649a7be4 ro quiet splash 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: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO 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.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO: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/1337641/+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 1322824] Re: [Gigabyte GA-H55M-USB3] Kernel panic
Mohammad Taha Jahangir, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) 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-3.16 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. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER 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 added: latest-bios-f11 ** Changed in: linux (Ubuntu) Importance: Low => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322824 Title: [Gigabyte GA-H55M-USB3] Kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: A Ubuntu 14.04 server died with a kernel panic with this stacktrace: [245407.543823] Call Trace: [249407.544937] [] dunp_stack+0x45/0x56 [249407.546067] [] uarn_sloupath_common+0x7d/0xa0 [249407.547173] [] uarn_sloupath_null+0x1a/0x20 [249407.548257] [] natiue_smp_send_reschedule+0x5d/0x60 [249407.549341] [] trigger_load_balance+0x16a/0x1e0 [249407.550416] [] scheduler_tick+0xa4/0xf0 [249407.551484] [] update_process_times+0x60/0x70 [249407.552550] [] tick_sched_handle.isra.17+0x2S/0x60 [249407.553608] [] tick_sched_timer+0x41/0x60 [249407.554671] [] __run_hrtimer+0x77/0x1d0 [249407.555728] [] ? tick_sched_handle.isra.17+0x60/0x60 [249407.556785] [] hrtimer_interrupt+0xef/0x230 [249407.557842] [] local_apic_tiner_interrupt+0x37/0x60 [249407.558900] [] smp_apic_tiner_interrupt+0x3f/0x60 [249407.559955] [] apic_tiner_interrupt+0x6d/0x80 [249407.561023] [] ? intel_crtc_set_config+0x668/0x9a0 [i915] [249407.562092] [] ? panic+0x193/0x1d7 [249407.563156] [] oops_end+0x139/0x150 [249407.564214] [] no_context+0x27e/0x28b [249407.565270] [] __bad_area_nosemaphore+0x73/0x1ca [249407.566327] [] bad_area_nosemaphore+0x13/0x15 [249407.567377] [] __do_page_fault+0xa7/0x560 [249407.568429] [] ? tcp_u4_rcu+0x664/0x7a0 [249407.569479] [] ? ip_1ocal_deliuer_finish+0xa8/0x210 [249407.570531] [] ? ip_local_deliuer+0x48/0x80 [249407.571575] [] ? ip_rcu_finish+0x7d/0x350 [249407.572613] [] do_page_fault+0x1a/0x70 [249407.573606] [] page_fault+0x28/0x30 [249407.574528] [] ? rtl8169_poll+0x22a/0x680 [r8169] [249407.575437] [] ? natiue_sched_c1ock+0x13/0x80 [249407.576339] [] net_rx_nction+0x152/0x250 [249407.577246] [] __do_softirq+0xec/0x2c0 [249407.578149] [] irq_cxit+0x105/0x110 [249407.579049] [] do_IRQ+0x56/0xc0 [249407.579943] [] common_interrupt+0x6d/0x6d [249407.580835] (EOI) [] ? cpuidle_cnter_state+0x4f/0xc0 [249407.581731] [] cpuidle_idle_call+0xb9/0x1f0 [249407.582593] [] arch_cpu_idle+0xe/0x30 [249407.583421] [] cpu_startup_entry+0xc5/0x290 [249407.584226] [] rest_init+0x77/0x80 [249407.585010] [] start_kernel+0x438/0x443 [249407.585772] [] ? repair_cnu_string+0x5c/0x5c [249407.586521] [] ? early_idt_handlers+0x120/0x120 [249407.587257] [] x86_64_start_reseruations+0x2a/0x2c [249407.587979] [] x86_64_start_kernel+0x143/0x152 [249407.588687] ---[ and trace 05db40b9a357e3e2 ]--- uname -a Linux bayanbox2 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The stackstrace is OCRed from screenshot of server (via KVM) and may be contains some spelling errors (original screenshot is attached). Also this stacktrace did not appeared in any log files. The apport server information is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1324697] Re: Suspend fails with kernel 3.13.0-27 and nouveau drivers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry - maybe I was a bit too fast here. Thanks for clarifying. Christian Am 2014-08-05 um 12:10 schrieb Christopher M. Penalver: > Christian Gonzalez, please do not toggle the bug title, or the > Status, as this report is not scoped to you, or your problem. So > your hardware and problem may be tracked, could you please file a > new report with Ubuntu by executing the following in a terminal > while booted into the default Ubuntu kernel (not a mainline one) > via: ubuntu-bug linux > > For more on this, please read the official Ubuntu documentation: > Ubuntu Bug Control and Ubuntu Bug Squad: > https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue > > Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports > Ubuntu Community: > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > > When opening up the new report, please feel free to subscribe me > to it. > > Thank you for your understanding. > > Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs > > ** Summary changed: > > - Suspend fails with kernel 3.13.0-27 and nouveau drivers + [HP > Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails > with - kernel 3.13.0-27 > -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJT4K+lAAoJEE7aBdMtqS/53vsP+wbz5wvYWl79yCPqWmK7hMNr +iHWvUqOKKA2wiDe4x2Huwxy5jcFY88SLZ0mN73KjtU+39kL0V66NdmhxZE8z3lg 6jjBLlDd2NjY888sgHCT1qH0BpQTNaFx3W9zULYBbCHeuQamgPihvAtWUaYcmDMm amAbD1ih5NLSUT98oIIrFg2Nix/tUe1ZpytE+01FR6Hq2jOhnugjzUuWGH7m3gVG txhmGF4pQJfUp9ujUA1GOret1wf/t8hblvTiGJz20DOLl4x/JmotUdSA8T6gvMh0 BJq+SRZHqpvbP8F0IEcv41ZMvwGQQTiwj8YqY4IZxsM3ylEvka9AatU39lGmHUIk i975BeS3eDE2SuCql7sQOLPU2Oat+8hycd1AZ7xAsXXlxPaQvQM+F4HR0ZC4PjZW u2Trln4i8WdbHdVJO8ASBfuxEqUpUaL98Msl7WzJbZjF/OC6EVfbt83YFmWYk2Qp 0Y9MNJxi8gxgVpaTcxysPf51oBamaju9eoCnGocjSX+hNEh/kWpAWTfLO4Pk4vNu SrJNtMpILyHZF/7xo3c5lE+guaOTGOQ5h3bgx8uHc3mFrBTexW+7CKrkDeWEtKYj 4JHGNw0Q/j5Q8NI5mat8RJ5EWLm4m7DrH/F45dUm1WebO4dg0gTYrjqt19/Tj/YE v6J0+eLHZWVY0EKBGyeL =KFOn -END PGP SIGNATURE- -- 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/1324697 Title: [HP Pavilion dv7t-7000 CTO Entertainment Notebook PC] Suspend fails with - kernel 3.13.0-27 Status in “linux” package in Ubuntu: Incomplete Bug description: See: http://askubuntu.com/questions/473214/laptop-suspend-broken-after- latest-kernel-update where it was suggested i file a kernel bug report. short version: after kernel upgrade to 3.13.0-27 my laptop will no longer suspend. Note that the apport bug report was generated while running 3.13.0-24 (had to switch back, this is my ever-day-use computer). I noted which log files changed before and after a suspend attempt, and those changes are attached (suspend.out). I compared these to a suspend with the -24 kernel and noted the changes in the referenced askubuntu post. Please let me know if i can provide any more details! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: conrad 2293 F pulseaudio Date: Thu May 29 17:20:15 2014 HibernationDevice: RESUME=UUID=eb2b25c8-5489-484c-b3d1-b0db8834 InstallationDate: Installed on 2013-02-14 (469 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b2f1b8ee-6793-4070-8eb3-a07e52b30d03 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-18 (41 days ago) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181D dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packar
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
Repost of what I sent to the mailing list just now: My current interpretation of this problem is that it is some pathological condition caused by not rebalancing and being nearly out of space for allocating more metadata and hence it is rarely being seen by anyone else (because most users are regularly doing rebalances). See this thread for details about rebalancing and out of space: "ENOSPC with mkdir and rename" on 2014-08-02: http://thread.gmane.org/gmane.comp.file-systems.btrfs/37415 I haven't had the lockups in production since July and I'm now trialling a nightly rebalance: $ btrfs filesystem balance start -dusage=50 -musage=10 "$mount" I'll report back if I encounter further problems. -- 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/1349711 Title: Machine lockup in btrfs-transaction Status in “linux” package in Ubuntu: Confirmed Bug description: This has happened twice now. I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami- 776d9700. # cat /proc/version_signature Ubuntu 3.13.0-32.57-generic 3.13.11.4 After running for many days, the machine locked up with the below messages appearing on the console. The machine would respond to ping but not SSH or HTTP requests. The machine has one BTRFS volume which is 87% full and lives on an Logical Volume Manager (LVM) block device on top of one Amazon Elastic Block Store (EBS) device. Error messages after first reboot: [ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong amount of free space [ 77.613678] BTRFS error (device dm-0): failed to load free space cache for block group 10766778368 [ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong amount of free space [ 77.648952] BTRFS error (device dm-0): failed to load free space cache for block group 19356712960 [ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong amount of free space [ 77.931078] BTRFS error (device dm-0): failed to load free space cache for block group 20430454784 [ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong amount of free space [ 78.116165] BTRFS error (device dm-0): failed to load free space cache for block group 21504196608 Error messages after second reboot: [ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did not match free space cache generation (70012) [ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did not match free space cache generation (70012) [ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong amount of free space [ 467.429251] BTRFS error (device dm-0): failed to load free space cache for block group 518646661120 Error messages on the console after second lock-up follow: [246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246 jiffies g=35399662 c=35399661 q=0) [246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0) [246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828] [246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492] [246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828] [246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492] [246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828] [246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492] [246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828] [246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492] [246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828] [246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492] [246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828] [246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492] [246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058] INFO: rcu_sched detected stalls on CPUs/tasks: [246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828] [246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492] [246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828] [246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492] [247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828] [247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492] [247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828] [247028.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492] [247056.192053] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828] [247056.212061] B
[Kernel-packages] [Bug 1261851] Re: [Gigabyte EP45-UD3L] CPU frequency reported incorrectly after overclocking
John Kuang, would you be able to boot into a Utopic live environment via http://cdimage.ubuntu.com/daily-live/current/ ? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1261851 Title: [Gigabyte EP45-UD3L] CPU frequency reported incorrectly after overclocking Status in “linux” package in Ubuntu: Incomplete Bug description: The stock speed of Intel E3300 is 2.5 GHz (200*12.5). I had pushed the FSB from 200 MHz to 300 MHz in the BIOS, giving 3.75 GHz (300*12.5). However, "cat /proc/cpuinfo" and "cpufreq-info" incorrectly shows 3.33, 2.67, 2.13, 1.6 GHz, which are probably based on 266 MHz FSB (266*12.5=3.33, 266*10=2.67, 266*8=2.13, 266*6=1.6). "dmidecode --type processor" shows it at 3.75 GHz all the time, no matter which frequency or governor was selected in CPU Frequency Scaling Monitor. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-35-generic 3.8.0-35.50 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: jkuang 2308 F pulseaudio /dev/snd/controlC3: jkuang 2308 F pulseaudio /dev/snd/controlC2: jkuang 2308 F pulseaudio /dev/snd/controlC0: jkuang 2308 F pulseaudio Date: Tue Dec 17 11:16:02 2013 InstallationDate: Installed on 2012-02-02 (684 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic root=UUID=9809d504-4a1e-433d-8cdb-269df2cdb3e2 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-35-generic N/A linux-backports-modules-3.8.0-35-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-07 (254 days ago) dmi.bios.date: 01/27/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: EP45-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP45-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261851/+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 1261851] Re: [Gigabyte EP45-UD3L] CPU frequency reported incorrectly after overclocking
Xvani, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- 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/1261851 Title: [Gigabyte EP45-UD3L] CPU frequency reported incorrectly after overclocking Status in “linux” package in Ubuntu: Incomplete Bug description: The stock speed of Intel E3300 is 2.5 GHz (200*12.5). I had pushed the FSB from 200 MHz to 300 MHz in the BIOS, giving 3.75 GHz (300*12.5). However, "cat /proc/cpuinfo" and "cpufreq-info" incorrectly shows 3.33, 2.67, 2.13, 1.6 GHz, which are probably based on 266 MHz FSB (266*12.5=3.33, 266*10=2.67, 266*8=2.13, 266*6=1.6). "dmidecode --type processor" shows it at 3.75 GHz all the time, no matter which frequency or governor was selected in CPU Frequency Scaling Monitor. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-35-generic 3.8.0-35.50 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: jkuang 2308 F pulseaudio /dev/snd/controlC3: jkuang 2308 F pulseaudio /dev/snd/controlC2: jkuang 2308 F pulseaudio /dev/snd/controlC0: jkuang 2308 F pulseaudio Date: Tue Dec 17 11:16:02 2013 InstallationDate: Installed on 2012-02-02 (684 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic root=UUID=9809d504-4a1e-433d-8cdb-269df2cdb3e2 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-35-generic N/A linux-backports-modules-3.8.0-35-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-07 (254 days ago) dmi.bios.date: 01/27/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: EP45-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP45-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261851/+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 1092693] Re: cannot use A2DP profile on LG tone+ HBS-730 headset
Still present -- 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/1092693 Title: cannot use A2DP profile on LG tone+ HBS-730 headset Status in “linux” package in Ubuntu: Expired Bug description: When attempting to connect to a bluetooth headset from a laptop equipped with a CSR BS8510 bluetooth adapter (found in a RTL8188CEB8 mini-pci-express device), I get the following in syslog. KDE / bluedevil reports I have successfully connected to the device, but pulseaudio / kmix does not show that the device is connected. Ubuntu 12.10, bluez 4.101-0ubuntu6 Dec 20 14:24:39 ben-HP-Pavilion-dm4-Notebook-PC bluetoothd[14436]: Badly formated or unrecognized command: AT+BIA=0,0,0,1,1,1,0 Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC bluetoothd[14436]: Operation not supported (95) Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC pulseaudio[14301]: [pulseaudio] bluetooth-util.c: Failed to acquire transport fd: Input/output error Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC pulseaudio[14301]: [pulseaudio] module.c: Failed to load module "module-bluetooth-device" (argument: "address="00:18:6B:15:AC:DC" path="/org/bluez/14436/hci0/dev_00_18_6B_15_AC_DC""): initialization failed. Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC kernel: [25660.054153] input: 00:18:6B:15:AC:DC as /devices/virtual/input/input14 Initially, this seemed similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400 or to https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=827692, but ultimately I beleive this is a different issue, since the chipset and unrecognized command are diffrent respectively. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben 14301 F pulseaudio DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=cfaa0aef-50a0-42c5-aa85-a1f6e060bcd4 InstallationDate: Installed on 2012-11-01 (49 days ago) InstallationMedia: This MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=4d3bbeef-14d0-4ef1-a45a-663fa6ea1fb1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 RelatedPackageVersions: linux-restricted-modules-3.5.0-19-generic N/A linux-backports-modules-3.5.0-19-generic N/A linux-firmware1.95 Tags: quantal Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/14/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 146A dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.28 dmi.chassis.asset.tag: CNU0440X2W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd02/14/2011:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr0587110002242B1022100:rvnHewlett-Packard:rn146A:rvr58.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm4 Notebook PC dmi.product.version: 0587110002242B1022100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092693/+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 1097680] Re: CVE-2013-0160
** Also affects: linux (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: Invalid ** Also affects: linux-lts-backport-oneiric (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-armadaxp (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Utopic) Importance: Low Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Utopic) Importance: Low Status: Invalid ** No longer affects: linux-armadaxp (Ubuntu Quantal) ** No longer affects: linux-armadaxp (Ubuntu Saucy) ** No longer affects: linux-ec2 (Ubuntu Quantal) ** No longer affects: linux-ec2 (Ubuntu Saucy) ** No longer affects: linux-lts-saucy (Ubuntu Quantal) ** No longer affects: linux-lts-saucy (Ubuntu Saucy) ** No longer affects: linux-lts-quantal (Ubuntu Quantal) ** No longer affects: linux-lts-quantal (Ubuntu Saucy) ** No longer affects: linux-mvl-dove (Ubuntu Quantal) ** No longer affects: linux-mvl-dove (Ubuntu Saucy) ** No longer affects: linux (Ubuntu Quantal) ** No longer affects: linux (Ubuntu Saucy) ** No longer affects: linux-fsl-imx51 (Ubuntu Quantal) ** No longer affects: linux-fsl-imx51 (Ubuntu Saucy) ** No longer affects: linux-ti-omap4 (Ubuntu Quantal) ** No longer affects: linux-ti-omap4 (Ubuntu Saucy) ** No longer affects: linux-lts-raring (Ubuntu Quantal) ** No longer affects: linux-lts-raring (Ubuntu Saucy) ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1097680 Title: CVE-2013-0160 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-l
[Kernel-packages] [Bug 1352358] Re: Kernel 3.13 freezes sometimes at startup
Hempt IT-Support, could you please execute the following at a terminal (not manually attach an apport file): apport-collect 1352358 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352358 Title: Kernel 3.13 freezes sometimes at startup Status in “linux” package in Ubuntu: Incomplete Bug description: We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at startup. There is no kernelpanic. I can not use Systemrequest-Keys for restart. The only key that gives Feedback is the Numlock-Key (LED toggles). When i powercyle the Computer Grub has no countdown for booting the first Kernel. When I press Enter the Kernel starts normaly. I cannot find something in Syslog or somewhere else. I deactivated the bootparameter quiet und added the Parameter "console=tty0 console=ttyS0,115200n8". I connected the Computer via a Nullmodemcable with another computer and logged the bootprocess with minicom. The Logs are attached. I can not reproduce this Bug in Kernel linux-image-3.11.0-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352358/+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 1352174] Re: [Hewlett-Packard HP EliteBook 8560w] suspend/resume failure [non-free: nvidia]
Priyantha Bleeker, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) 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-3.16 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. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER 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 added: latest-bios-f.42 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352174 Title: [Hewlett-Packard HP EliteBook 8560w] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Incomplete Bug description: priyantha@priyantha-HP-EliteBook-8560w:~$ lsb_release -rd Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 priyantha@priyantha-HP-EliteBook-8560w:~$ apt-cache policy linux-image-3.16.0-6-generic linux-image-3.16.0-6-generic: Geïnstalleerd: 3.16.0-6.11 Kandidaat: 3.16.0-6.11 Versietabel: *** 3.16.0-6.11 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status priyantha@priyantha-HP-EliteBook-8560w:~$ apt-cache policy nvidia-304-updates nvidia-304-updates: Geïnstalleerd: 304.123-0ubuntu2 Kandidaat: 304.123-0ubuntu2 Versietabel: *** 304.123-0ubuntu2 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status After suspending the system, I can't power the laptop on any more. I have to remove the battery from the laptop and insert it again. Otherwise the laptop will not power up. The power button just blinks. if there is any further testing or debugging needed I am perfectly willing to do so. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-6-generic 3.16.0-6.11 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: priyantha 2637 F pulseaudio /dev/snd/controlC0: priyantha 2637 F pulseaudio Date: Wed Jan 2 09:14:32 1980 DuplicateSignature: suspend/resume:Hewlett-Packard HP EliteBook 8560w:68SVD Ver. F.42 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=e7fc9221-3c64-4925-ba5e-db1ccbb8585d InstallationDate: Installed on 2014-07-31 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterpreterPath: /usr/bin/python3.4 MachineType: Hewlett-Packard HP EliteBook 8560w ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=803ad3f3-9b89-4ef6-8f2a-b6157f07e0d5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 SourcePackage: linux Title: [Hewlett-Packard HP EliteBook 8560w] suspend/resume failure [non-free: nvidia] UpgradeStatus: Upgraded to utopic on 2014-07-31 (3 days ago) UserGroups: dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion
[Kernel-packages] [Bug 1352379] Re: Network broken after resume
Jeroen van der Ham, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/04/product-support/product/optiplex-7010/drivers an update to your BIOS is available (A18). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. As well, you don't have to create a new bug report. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Attachment removed: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352379/+attachment/4169575/+files/lspci-vnvn.log ** Attachment removed: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352379/+attachment/4169576/+files/version.log ** Tags added: bios-outdated-a18 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352379 Title: Network broken after resume Status in “linux” package in Ubuntu: Incomplete Bug description: We use Dell Optiplex 7010 machines in our student lab. These machines are capable of suspending and resuming, so that we don't waste power during the night. In our lab we also use LDAP authentication for the students. The problem is that networking is disabled once the machine is resumed after a suspend. Because of the LDAP authentication, networking is required for authentication, thus we cannot login to the machine after a suspend. A "work-around" to restart network-manager is therefor not an option. I have tried numerous things, * creating a file /etc/pm/config.d/network-resume with the content "SUSPEND_MODULE="e1000e" Outcome: This seems to break the suspend functionality. When manually entering "suspend" it goes directly to the lock screen. The networking is still disabled, so I cannot log in. * creating a file /etc/pm/sleep.d/network-resume with #!/bin/sh case ${1} in resume|thaw) nmcli nm sleep false ;; esac Outcome: Manually suspending works, resume only works when pressing the power button. Once resumed the networking is still disabled, and thus I cannot log in. * creating a file in /etc/pm/sleep.d with #!/bin/sh case "${1}" in resume|thaw) restart network-manager ;; esac Outcome: Manually suspending works, resume only works when pressing the power button. Once resumed the networking is still disabled, and thus I cannot log in. After about a full minute networking is restored and I can log in. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1285 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=5f5a9253-499b-4d0a-a0ea-903335a5222f InstallationDate: Installed on 2014-07-08 (27 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 7010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 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-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0MN1TX dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0MN1TX:rvrA01:cvnDellInc.:ct16:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage
[Kernel-packages] [Bug 1151527] Re: CVE-2013-1819
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-oneiric (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-quantal (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-raring (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Medium Status: Fix Committed ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Medium Status: Fix Released ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: Invalid ** Also affects: linux-lts-backport-oneiric (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Utopic) Importance: Medium Status: Invalid ** No longer affects: linux-armadaxp (Ubuntu Quantal) ** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-armadaxp (Ubuntu Saucy) ** No longer affects: linux-ec2 (Ubuntu Quantal) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Saucy) ** No longer affects: linux-lts-saucy (Ubuntu Quantal) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Saucy) ** No longer affects: linux-lts-quantal (Ubuntu Quantal) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Saucy) ** No longer affects: linux-mvl-dove (Ubuntu Quantal) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Saucy) ** No longer affects: linux (Ubuntu Quantal) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux (Ubuntu Saucy) ** No longer affects: linux-fsl-imx51 (Ubuntu Quantal) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Saucy) ** No longer affects: linux-ti-omap4 (Ubuntu Quantal) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Saucy) ** No longer affects: linux-lts-raring (Ubuntu Quantal) ** No longer affects: linux-lts-raring (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Saucy) ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: Fix Released => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is su
[Kernel-packages] [Bug 1352821] [NEW] 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working
You have been subscribed to a public bug: Hi, Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi working fine. pls help to provide the solution Vendor ID : 0489:e078 Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 Regds, Bala S ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working https://bugs.launchpad.net/bugs/1352821 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352461] Re: IRQ conflict disables wired network on cold (first) boot
Stig-Arne Grönroos, thank you for reporting this and helping make Ubuntu better. As per https://downloadcenter.intel.com/SearchResult.aspx?lang=&ProductID=3284&ProdId=3284 an update to your BIOS is available (0160). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. As well, you don't have to create a new bug report. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-0160 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352461 Title: IRQ conflict disables wired network on cold (first) boot Status in “linux” package in Ubuntu: Incomplete Bug description: On every cold boot the ethernet controller fails to load, leaving the wired network completely disabled. No interface /dev/eth0 is created. IRQ 49 is taken by snd_hda_intel. 49: 29219 0 0 0 PCI-MSI-edge snd_hda_intel eth0 is not listed in /proc/interrupts The following log message is printed: e1000e: probe of :00:19.0 failed with error -3 When rebooting the machine (without powering down), the ethernet controller loads normally and functions without problems. IRQ:s are now allocated differently: 49: 155107 0 0 0 PCI-MSI-edge eth0 50: 1414 965740 0 0 PCI-MSI-edge snd_hda_intel The expected behaviour is that the ethernet controller will be assigned an IRQ on the first boot, and load normally. The network controller worked fine in Precise, until some upgrade in June. I did not diagnose the problem immeditaly, and don't know which upgrade caused the regression. Upgrading to Trusty (Ubuntu 14.04.1 LTS) did not solve the problem. The problem is not random: it occurs at every cold boot and the workaround of rebooting immediately after each cold boot works persistently. I tried, as a workaround, setting the following kernel parameters (one at a time): pci=noacpi , pci=routeirq , noapic, acpi=off, pcie_pme=force and irqpoll None of the listed kernel parameters affected the problem. rmmod e1000e followed modprobe e1000e didn't help. The ethernet controller is a 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05) Kernel driver in use: e1000e The sound chip is a 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Kernel driver in use: snd_hda_intel Both of the devices are on-board chips on the motherboard, so changing slots is not possible as a workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gronsti5896 F pulseaudio gronsti7728 F pulseaudio Date: Mon Aug 4 19:46:31 2014 HibernationDevice: RESUME=UUID=a4491702-2d6a-4187-8756-1d7c48b9bbef InstallationDate: Installed on 2012-05-29 (797 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IwConfig: eth0 no wireless extensions. lono wireless extensions. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=UUID=a7af81dd-393a-4948-a371-6f54d5de589b ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-30 (4 days ago) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-210 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrB
[Kernel-packages] [Bug 1336541] [NEW] No TRIM via USB
You have been subscribed to a public bug: Hi, As USB attached SSDs are becoming quite big and affordable, along comes the idea of installing systems on these. But with current USB drivers, some functionality seems to be missing from USB subsystem. The system does not recognize it is an SSD, but it is corrected manually: # cat /etc/udev/rules.d/10-forcessd.rules SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", KERNEL=="sd?", ATTR{queue/rotational}="0" # cat /sys/block/sdb/queue/rotational 0 Checked hdparm, it is saying I have TRIM on the device: # hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SanDisk pSSD (...) Commands/features: EnabledSupported: (...) * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM (...) Here is appropriate dmesg: [3.815604] usb 2-8: Manufacturer: SunplusIT INC. [4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580 [4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4.138405] usb 3-3: Product: Extreme [4.138406] usb 3-3: Manufacturer: SanDisk [4.138407] usb 3-3: SerialNumber: AA011109131654094942 [4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected [4.141431] scsi0 : usb-storage 3-3:1.0 [4.141703] usbcore: registered new interface driver usb-storage And: [5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB) [5.331608] sd 0:0:0:0: [sdb] Write Protect is off [5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08 [5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [5.339849] sdb: sdb1 sdb2 sdb3 < sdb5 > [5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk >From here I'll be using /boot formatted to ext4 to eliminate luks,lvm and btrfs from the equasion: # mount |grep sdb2 /dev/sdb2 on /boot type ext4 (rw,noexec,discard) # fstrim -v /boot/ fstrim: /boot/: FITRIM ioctl failed: Operation not supported # strace fstrim -v /boot/ (...) open("/boot/", O_RDONLY)= 3 ioctl(3, FITRIM, 0x7fffdded85c0)= -1 EOPNOTSUPP (Operation not supported) (...) During debugging, I've tried compiling a kernel with UAS module to check, it booted, system was g changed with the trim - as it wouldn't been used at all. Any ideas why TRIM is not working on USB? Any timeframes for possible fix? Any workarounds maybe? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment fitrim fstrim trim uas usb -- No TRIM via USB https://bugs.launchpad.net/bugs/1336541 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352567] Re: OOPS in cpufreq driver with AMD Kaveri CPU
post-factum, please execute the following in the default Ubuntu kernel (not mainline): apport-collect 1352567 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Incomplete Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352567/+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 1336541] Re: No TRIM via USB
** Package changed: udev (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1336541 Title: No TRIM via USB Status in “linux” package in Ubuntu: New Bug description: Hi, As USB attached SSDs are becoming quite big and affordable, along comes the idea of installing systems on these. But with current USB drivers, some functionality seems to be missing from USB subsystem. The system does not recognize it is an SSD, but it is corrected manually: # cat /etc/udev/rules.d/10-forcessd.rules SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", KERNEL=="sd?", ATTR{queue/rotational}="0" # cat /sys/block/sdb/queue/rotational 0 Checked hdparm, it is saying I have TRIM on the device: # hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SanDisk pSSD (...) Commands/features: Enabled Supported: (...) * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM (...) Here is appropriate dmesg: [3.815604] usb 2-8: Manufacturer: SunplusIT INC. [4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580 [4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4.138405] usb 3-3: Product: Extreme [4.138406] usb 3-3: Manufacturer: SanDisk [4.138407] usb 3-3: SerialNumber: AA011109131654094942 [4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected [4.141431] scsi0 : usb-storage 3-3:1.0 [4.141703] usbcore: registered new interface driver usb-storage And: [5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB) [5.331608] sd 0:0:0:0: [sdb] Write Protect is off [5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08 [5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [5.339849] sdb: sdb1 sdb2 sdb3 < sdb5 > [5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk From here I'll be using /boot formatted to ext4 to eliminate luks,lvm and btrfs from the equasion: # mount |grep sdb2 /dev/sdb2 on /boot type ext4 (rw,noexec,discard) # fstrim -v /boot/ fstrim: /boot/: FITRIM ioctl failed: Operation not supported # strace fstrim -v /boot/ (...) open("/boot/", O_RDONLY)= 3 ioctl(3, FITRIM, 0x7fffdded85c0)= -1 EOPNOTSUPP (Operation not supported) (...) During debugging, I've tried compiling a kernel with UAS module to check, it booted, system was g changed with the trim - as it wouldn't been used at all. Any ideas why TRIM is not working on USB? Any timeframes for possible fix? Any workarounds maybe? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336541/+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 1352821] Re: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working
** Package changed: udisks2 (Ubuntu) => bluez (Ubuntu) -- 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/1352821 Title: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working Status in “bluez” package in Ubuntu: New Bug description: Hi, Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi working fine. pls help to provide the solution Vendor ID : 0489:e078 Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 Regds, Bala S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1352821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels
@Rafael, I manually installed the `linux-image-3.13.0-33-generic` package, but it doesn't seem to solve the problem. Booting to this kernel says "No bluetooth adapters found" (as against "Bluetooth is diabled" in v3.13.0-32) although I have the adapter connected. Moreover, the kernel creates additional problems. It doesn't recognize my mouse and the display is stretched on the monitor with lower resolution. In short, the package doesn't work. Let me know if you need any assistance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1221995 Title: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: Bluetooth device stopped working. Device support regression. Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6 Testcase: Comment #10 Original Description: Bluetooth device stopped working after upgrading ubuntu to 13.10. ~$ lsusb: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) ~$ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:10:00:0F:46 ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:457 acl:0 sco:0 events:16 errors:0 TX bytes:68 acl:0 sco:0 commands:16 errors:0 ~$ hcitool dev Devices: device simply doesnt appear on bluetooth manager. blueman UI is broken. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jorge 1954 F pulseaudio /dev/snd/controlC0: jorge 1954 F pulseaudio Date: Fri Sep 6 22:32:45 2013 HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MEGAWARE MW-H61M-2H MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 MW dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MW-H61M-2H dmi.board.vendor: MEGAWARE dmi.board.version: v1.3 - 17/07/2012 - MWX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MW-H61M-2H dmi.product.version: v1.3 - 17/07/2012 - MWX dmi.sys.vendor: MEGAWARE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1161962] Re: XPS 13 wakes up from suspend spontaneously
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1161962 Title: XPS 13 wakes up from suspend spontaneously Status in Dell Sputnik: In Progress Status in “linux” package in Ubuntu: New Bug description: My XPS 13 wakes up from suspend by itself. This is very annoying and potentially dangerous since it happens while the computer is its sleeve/bag. Can't tell from the pm-suspend and dmesg what causes the behavior so please let me know what logs you need to investigate it and I will provide them. Further note: It seems like the spontaneous wake up is happening around 40 minutes after suspend every time it occurs. However, the spontaneous wake up does not occur every time. Running Xubuntu 12.10 with the following Sputnik Kernel: 3.5.0-26-generic #42+kamal15~DellXPS-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1161962/+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 1336541] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1336541 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1336541 Title: No TRIM via USB Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, As USB attached SSDs are becoming quite big and affordable, along comes the idea of installing systems on these. But with current USB drivers, some functionality seems to be missing from USB subsystem. The system does not recognize it is an SSD, but it is corrected manually: # cat /etc/udev/rules.d/10-forcessd.rules SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", KERNEL=="sd?", ATTR{queue/rotational}="0" # cat /sys/block/sdb/queue/rotational 0 Checked hdparm, it is saying I have TRIM on the device: # hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SanDisk pSSD (...) Commands/features: Enabled Supported: (...) * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM (...) Here is appropriate dmesg: [3.815604] usb 2-8: Manufacturer: SunplusIT INC. [4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580 [4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4.138405] usb 3-3: Product: Extreme [4.138406] usb 3-3: Manufacturer: SanDisk [4.138407] usb 3-3: SerialNumber: AA011109131654094942 [4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected [4.141431] scsi0 : usb-storage 3-3:1.0 [4.141703] usbcore: registered new interface driver usb-storage And: [5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB) [5.331608] sd 0:0:0:0: [sdb] Write Protect is off [5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08 [5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [5.339849] sdb: sdb1 sdb2 sdb3 < sdb5 > [5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk From here I'll be using /boot formatted to ext4 to eliminate luks,lvm and btrfs from the equasion: # mount |grep sdb2 /dev/sdb2 on /boot type ext4 (rw,noexec,discard) # fstrim -v /boot/ fstrim: /boot/: FITRIM ioctl failed: Operation not supported # strace fstrim -v /boot/ (...) open("/boot/", O_RDONLY)= 3 ioctl(3, FITRIM, 0x7fffdded85c0)= -1 EOPNOTSUPP (Operation not supported) (...) During debugging, I've tried compiling a kernel with UAS module to check, it booted, system was g changed with the trim - as it wouldn't been used at all. Any ideas why TRIM is not working on USB? Any timeframes for possible fix? Any workarounds maybe? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336541/+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 1161962] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1161962 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: quantal -- 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/1161962 Title: XPS 13 wakes up from suspend spontaneously Status in Dell Sputnik: In Progress Status in “linux” package in Ubuntu: Incomplete Bug description: My XPS 13 wakes up from suspend by itself. This is very annoying and potentially dangerous since it happens while the computer is its sleeve/bag. Can't tell from the pm-suspend and dmesg what causes the behavior so please let me know what logs you need to investigate it and I will provide them. Further note: It seems like the spontaneous wake up is happening around 40 minutes after suspend every time it occurs. However, the spontaneous wake up does not occur every time. Running Xubuntu 12.10 with the following Sputnik Kernel: 3.5.0-26-generic #42+kamal15~DellXPS-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1161962/+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 1248700] Re: CVE-2013-4348
** Also affects: linux (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: Won't Fix ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: Won't Fix ** Also affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Utopic) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Utopic) Importance: Medium Status: Invalid ** No longer affects: linux-armadaxp (Ubuntu Quantal) ** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-armadaxp (Ubuntu Saucy) ** No longer affects: linux-ec2 (Ubuntu Quantal) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Saucy) ** No longer affects: linux-lts-saucy (Ubuntu Quantal) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Saucy) ** No longer affects: linux-lts-quantal (Ubuntu Quantal) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Saucy) ** No longer affects: linux-mvl-dove (Ubuntu Quantal) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Saucy) ** No longer affects: linux (Ubuntu Quantal) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux (Ubuntu Saucy) ** No longer affects: linux-fsl-imx51 (Ubuntu Quantal) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Saucy) ** No longer affects: linux-ti-omap4 (Ubuntu Quantal) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Saucy) ** No longer affects: linux-lts-raring (Ubuntu Quantal) ** No longer affects: linux-lts-raring (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Saucy) ** Changed in: linux-armadaxp (Ubuntu Precise) Status: Invalid => Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Invalid => Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Precise) Status: Invalid => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Invalid => Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1248700 Title: CVE-2013-4348 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal
[Kernel-packages] [Bug 1349799] Re: CVE-2014-5045
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Description changed: [vfs: refcount issues during unmount on symlink] - Break-Fix: - 295dc39d941dc2ae53d5c170365af4c9d5c16212 + Break-Fix: 8033426e6bdb2690d302872ac1e1fadaec1a5581 + 295dc39d941dc2ae53d5c170365af4c9d5c16212 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1349799 Title: CVE-2014-5045 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: [vfs: refcount issues during unmount on symlink] Break-Fix: 8033426e6bdb2690d302872ac1e1fadaec1a5581 295dc39d941dc2ae53d5c170365af4c9d5c16212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://
[Kernel-packages] [Bug 362704] Re: nvidia-settings does not keep resolution that it is set too and xorg.conf is useless
Is anyone still suffering from this with Ubuntu 12.04 or 14.04? ** Changed in: nvidia-settings (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/362704 Title: nvidia-settings does not keep resolution that it is set too and xorg.conf is useless Status in “nvidia-settings” package in Ubuntu: Incomplete Bug description: Binary package hint: nvidia-settings Hi there all. I am on the fabulously new jaunty. But I have a video problem. After a fresh install, I enabled the restricted nvidia drivers. Then via nvidia-settings i set my resolution to 1280x1024. This works well until I reboot, then ubuntu boots into some other low resolution that I do not know where it is getting this resolution from. I then tried to copy my old xorg.con from intrepid to jaunty but it bombs. I try to set the resolution via system -> preference -> display but no dice .. it forces me back to nvidia-settings. Exactly how is resolution setting handled in jaunty RC? ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: nvidia-settings 180.25-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/362704/+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 1352821] Re: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working
The attachment "lcpsi.jpg" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1352821 Title: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working Status in “bluez” package in Ubuntu: New Bug description: Hi, Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi working fine. pls help to provide the solution Vendor ID : 0489:e078 Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 Regds, Bala S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1352821/+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 1326757] Re: [Dell Dimension E521] System goes to sleep at GDM window and never wakes up
I have tried installing a number of older kernels in order to attempt to find the last known good or first known bad kernel, following the examples on https://wiki.ubuntu.com/Kernel/KernelBisection in the "Bisecting Ubuntu kernel versions" section. Not one of the kernels I have installed has booted correctly. I have guessed that the bogus kernel was built between the last good saucy 13.10 kernel I used and the first trusty 14.04 kernel I installed. First I installed trusty 3.12.0-8.16. It would not boot. I got a full crash. Then I installed saucy 3.11.0-26.45. It would not boot because MDADM could not find my RAIDs. So then I tried trusty 3.13.0-4.19. It would not boot, again because MDADM: Incrementally starting RAID arrays... mdadm: CREATE group disk not found Incrementally started RAID arrays. Is there something I'm doing wrong? I have been installing all three images as per the wiki page, for example: linux-headers-3.13.0-4_3.13.0-4.19_all.deb linux-image-3.13.0-4-generic_3.13.0-4.19_amd64.deb linux-headers-3.13.0-4-generic_3.13.0-4.19_amd64.deb -- 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/1326757 Title: [Dell Dimension E521] System goes to sleep at GDM window and never wakes up Status in “linux” package in Ubuntu: Incomplete Bug description: On my Dell Dimension E521, a desktop system, if I leave the system at the login prompt it will very quickly go to sleep. When I press the power button to wake it, the system seems to restart, but the screen and the keyboard never wake up. I have to poke it in the eye and reboot. This behavior effectively renders the machine unusable if I am away. If the power goes out and the system reboots, it will very quickly sleep and never wake up. Thus, I cannot use it remotely. And if I forget to immediately (IMMEDIATELY) log in, the system will go to sleep and I have to hard power off and reboot. Very annoying. This only happened once I upgraded to 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: relph 3132 F pulseaudio CurrentDesktop: KDE Date: Thu Jun 5 07:25:56 2014 HibernationDevice: RESUME=UUID=4910abff-aedb-49ea-a640-881c159d9639 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc Dimension E521 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=449c36fa-de2d-44cf-ad97-450c0903f337 ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-20 (45 days ago) WifiSyslog: WpaSupplicantLog: dmi.bios.date: 08/02/2007 dmi.bios.vendor: Dell Inc dmi.bios.version: 1.1.11 dmi.board.name: 0UW457 dmi.board.vendor: Dell Inc dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc dmi.modalias: dmi:bvnDellInc:bvr1.1.11:bd08/02/2007:svnDellInc:pnDimensionE521:pvr:rvnDellInc:rn0UW457:rvrA03:cvnDellInc:ct3:cvr: dmi.product.name: Dimension E521 dmi.sys.vendor: Dell Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326757/+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 1348466] Re: [hsw DP] Ubuntu 12.04 unable to use external monitor through edock
The patch was reverted upstream unfortunately in https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c6930992948adf0f8fc1f6ff1da51c5002a2cf95 so it's not really appropriate to backport to trusty Revert "drm/i915: reverse dp link param selection, prefer fast over wide again" This reverts commit 38aecea0ccbb909d635619cba22f1891e589b434. This breaks Haswell Thinkpad + Lenovo dock in SST mode with a HDMI monitor attached. Before this we can 1920x1200 mode, after this we only ever get 1024x768, and a lot of deferring. This didn't revert clean, but this should be fine. bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1117008 Cc: sta...@vger.kernel.org # v3.15 Signed-off-by: Dave Airlie Signed-off-by: Daniel Vetter ** Bug watch added: Red Hat Bugzilla #1117008 https://bugzilla.redhat.com/show_bug.cgi?id=1117008 ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/1348466 Title: [hsw DP] Ubuntu 12.04 unable to use external monitor through edock Status in “linux” package in Ubuntu: Won't Fix Bug description: this bug is filed to track an upstream bug http://www.libreoffice.org/bugzilla/show_bug.cgi?id=73694 It will be good if we can pull the patch from the upstream bug for Ubuntu kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348466/+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 1349804] Re: CVE-2014-5077
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Lucid) Status: New => Fix Committed ** Description changed: net: SCTP: NULL pointer dereference + + Break-Fix: - 1be9a950c646c9092fb3618197f7b6bfb50e82aa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1349804 Title: CVE-2014-5077 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: New Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: net: SCTP: NULL pointer dereference Break-Fix: - 1be9a950c646c9092fb3618197f7b6bfb50e82aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349804/+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 1352640] [NEW] Huge PCI BAR support needed for Ubuntu 14.10
You have been subscribed to a public bug: == Comment: #0 - Brian Hart - 2014-08-04 17:26:34 == ---Problem Description--- Our project requires Huge BAR Support (i.e. support for PCI BAR spaces > 1G) in Ubuntu 14.10. Guo and Gavin are working on the kernel changes (and Sapphire/OPAL changes?) and have already submitted patches. The patches did not make the 3.16 cut-off, so will need to be back-ported to the 14.10 kernel. I believe the patches are the set described by: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119170.html Contact Information = Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com) ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Problem is seen with PCI adapters that request > 1G of BAR space. We've seen it with GPUs that request a BAR1 of size 16G. Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Add a PCI adapter which requests huge BAR space in the system. The huge BARs will not be assigned and the adapter will likely not initialize. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com): -Attach sysctl -a output output to the bug. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bot-comment bugnameltc-114190 severity-critical targetmilestone-inin1410 -- Huge PCI BAR support needed for Ubuntu 14.10 https://bugs.launchpad.net/bugs/1352640 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352640] Re: Huge PCI BAR support needed for Ubuntu 14.10
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352640 Title: Huge PCI BAR support needed for Ubuntu 14.10 Status in “linux” package in Ubuntu: Incomplete Bug description: == Comment: #0 - Brian Hart - 2014-08-04 17:26:34 == ---Problem Description--- Our project requires Huge BAR Support (i.e. support for PCI BAR spaces > 1G) in Ubuntu 14.10. Guo and Gavin are working on the kernel changes (and Sapphire/OPAL changes?) and have already submitted patches. The patches did not make the 3.16 cut-off, so will need to be back-ported to the 14.10 kernel. I believe the patches are the set described by: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119170.html Contact Information = Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com) ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Problem is seen with PCI adapters that request > 1G of BAR space. We've seen it with GPUs that request a BAR1 of size 16G. Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Add a PCI adapter which requests huge BAR space in the system. The huge BARs will not be assigned and the adapter will likely not initialize. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com): -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352640/+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 1352640] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1352640 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352640 Title: Huge PCI BAR support needed for Ubuntu 14.10 Status in “linux” package in Ubuntu: Incomplete Bug description: == Comment: #0 - Brian Hart - 2014-08-04 17:26:34 == ---Problem Description--- Our project requires Huge BAR Support (i.e. support for PCI BAR spaces > 1G) in Ubuntu 14.10. Guo and Gavin are working on the kernel changes (and Sapphire/OPAL changes?) and have already submitted patches. The patches did not make the 3.16 cut-off, so will need to be back-ported to the 14.10 kernel. I believe the patches are the set described by: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119170.html Contact Information = Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com) ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Problem is seen with PCI adapters that request > 1G of BAR space. We've seen it with GPUs that request a BAR1 of size 16G. Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Add a PCI adapter which requests huge BAR space in the system. The huge BARs will not be assigned and the adapter will likely not initialize. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com): -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352640/+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 1350889] Re: kernel crash kvm guest on power8
Upgraded kernel to apw's provided binaries: http://people.canonical.com/~apw/lp1350889-trusty/ Kicked off the testing script, it'll take a few hours for it to 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/1350889 Title: kernel crash kvm guest on power8 Status in “linux” package in Ubuntu: Confirmed Bug description: subject is extremely vague, I'll give all the information I have here. We've got a number of kvm guests running on a power8 host: $ head -n 5 /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) $ rpm -qf `which qemu-system-ppc64` qemu-system-ppc-1.6.0-2.pkvm2_1.9.2.ppc64 $ uname -r 3.10.23-900.pkvm2_1.1.ppc64 $ ps axw | grep [s]tilson-01 83440 pts/1S+ 0:00 /bin/bash /home/shared/bin/guest-start stilson-01 83459 pts/1Sl+ 4882:24 qemu-system-ppc64 -enable-kvm -M pseries -cpu host -smp cores=2,threads=1 -m 8G -net nic,macaddr=52:54:00:00:43:81 -net tap,script=no,downscript=no,ifname=tap4381 -device spapr-vscsi -drive file=/var/lib/libvirt/images/shared/stilson-01/disk1.img -drive file=/var/lib/libvirt/images/shared/stilson-01/eph0.img -nographic -vga none The ppc64el Ubuntu 14.04 guest was found dead, and showed on console: [708665.375169] Unable to handle kernel paging request for data at address 0x00bf [708665.375321] Faulting instruction address: 0xc04b790c [708665.375388] Oops: Kernel access of bad area, sig: 11 [#1] [708665.375440] SMP NR_CPUS=2048 NUMA pSeries [708665.375513] Modules linked in: 8021q garp mrp ebtable_broute ebtable_filter sunrpc nfnetlink_queue nfnetlink_log nfnetlink btrfs raid6_pq xor ufs msdos xfs libcrc32c veth xt_conntrack ipt_REJECT ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [708665.376496] CPU: 0 PID: 270 Comm: cgmanager Not tainted 3.13.0-32-generic #57-Ubuntu [708665.376644] task: c001fa55be10 ti: c001f8d68000 task.ti: c001f8d68000 [708665.376786] NIP: c04b790c LR: c04b78d8 CTR: c04b7860 [708665.376931] REGS: c001f8d6b680 TRAP: 0300 Not tainted (3.13.0-32-generic) [708665.377084] MSR: 80009033 CR: 42008484 XER: 2000 [708665.377411] CFAR: c000a86c DAR: 00bf DSISR: 4000 SOFTE: 0 GPR00: c04b4710 c001f8d6b900 c164edb8 GPR04: 0800 GPR08: 0003 00bf 00bf c00172a0 GPR12: 22002482 cfe4 fe80 fe90 GPR16: fea0 feb0 fec0 GPR20: 010003df8420 c000b1bfbe00 0400 GPR24: 0001 c15f2ed8 c000b1bfbdc0 GPR28: c16e4c80 c16e4fc4 c78e6600 c001f8d6b9d0 [708665.379401] NIP [c04b790c] .tg_prfill_cpu_rwstat+0xac/0x180 [708665.379517] LR [c04b78d8] .tg_prfill_cpu_rwstat+0x78/0x180 [708665.379643] Call Trace: [708665.379694] [c001f8d6b900] [c00130138e18] 0xc00130138e18 (unreliable) [708665.379854] [c001f8d6ba20] [c04b4710] .blkcg_print_blkgs+0xf0/0x1b0 [708665.380026] [c001f8d6bae0] [c04b7730] .tg_print_cpu_rwstat+0x50/0x80 [708665.380204] [c001f8d6bb70] [c01381ec] .cgroup_seqfile_show+0x9c/0xc0 [708665.380384] [c001f8d6bc00] [c0287e98] .seq_read+0x158/0x570 [708665.380526] [c001f8d6bcf0] [c02560d4] .vfs_read+0xc4/0x1f0 [708665.380679] [c001f8d6bd90] [c0256ef4] .SyS_read+0x64/0xe0 [708665.380811] [c001f8d6be30] [c000a158] syscall_exit+0x0/0x98 [708665.380956] Instruction dump: [708665.381040] 813d 3be100d0 7c6307b4 7f891800 409d00b0 3d420009 392a1ca8 786a1f24 [708665.381268] 7d49502a e93e01c8 7d495214 7d2ad214 <7cead02a> e9090008 e9490010 e9290018 [708665.381505] ---[ end trace 512b8ac8f55926fd ]--- [708665.387710] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: User Name 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or direct
[Kernel-packages] [Bug 1342000] Re: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw
I notice that in the netg3 command, one drive is specified as scsi-hd, while the other is virtio-blk-pci. Was that intended? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw Status in “linux” package in Ubuntu: New Status in “qemu” package in Ubuntu: New Bug description: Problem Description --- ISST-KVM-UBUNTU1410-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image raw. Ubuntu installation to virtio-scsi disk type of raw, not able to find the driver by default and not listing virtio-scsi drivers to choose ---uname output--- [root@lizkvm home]# uname -a Linux lizkvm.isst.aus.stglabs.ibm.com 3.10.42-2001.pkvm2_1_1.3.ppc64 #1 SMP Tue Jun 17 13:13:10 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux [root@lizkvm home]# Steps to reproduce --- 1) [root@magkvm images]# virsh define lizg3.xml Domain lizg3 defined from lizg3.xml 2) [root@lizkvm home]# virsh dumpxml lizg3 lizg3 da4ce0fd-2268-45b8-b5ca-611ac7926e50 6606848 6606029 4 /machine hvm destroy restart restart /usr/bin/qemu-system-ppc64 system_u:system_r:svirt_t:s0:c79,c721 system_u:object_r:svirt_image_t:s0:c79,c721 3) [root@magkvm images]# virsh start --console lizg3 Domain lizg3 started Connected to domain lizg3 Escape character is ^] SLOF ** -->Configured network properly and then moved to Detect disks screen 4) Proceeded with the installation and when the disk partition screen comes up. Installer is not able to indentify the disk and asks to choose from the list of drivers as below [!] Detect disks ? ? ? ? No disk drive was detected. If you know the name of the driver needed ? ? by your disk drive, you can select it from the list.? ? ? ? Driver needed for your disk drive: ? ? ? ? continue with no disk drive ? ? login to iSCSI targets ? ? 3w-9xxx ? ? ? 3w-sas ? ? ? 3w- ? ? ? DAC960 ? ? ? a100u2w ? ? ? aacraid ? ? ? aic79xx ? ? ? aic7xxx ? ? ? ?? ? ? ??? moves; selects; activates buttons 4) verified for the drivers from the list and none of them belongs to virtio-scsi optional driver listed are: continue with no disk drive ? ? login to iSCSI targets ? ? 3w-9xxx ? ? ? 3w-sas ? ? ? 3w- ? ? ? DAC960 ? ? ? a100u2w ? ? ? aacraid ? ? ? aic79xx ? ? ? aic7xxx aic94xx ? ? aoe ? ? ? arcmsr ? ? aten ? ? ? atp870u ? ? ? bpck ? ? ? cciss ? ? ? comm ? ? ? cryptoloop ? ? ? dc395x dmx3191d ? ? dstr ? ?
[Kernel-packages] [Bug 1352794] [NEW] Null pointer dereference in mmu_set_spte.isra
You have been subscribed to a public bug: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of our hypervisors (running several KVM VMs). This led us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Null pointer dereference in mmu_set_spte.isra https://bugs.launchpad.net/bugs/1352794 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352794] Re: Null pointer dereference in mmu_set_spte.isra
** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Summary changed: - Null pointer dereference in mmu_set_spte.isra + Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic -- 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/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic Status in “linux” package in Ubuntu: Incomplete Bug description: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of our hypervisors (running several KVM VMs). This led us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+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 1352794] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1352794 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: raring -- 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/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic Status in “linux” package in Ubuntu: Incomplete Bug description: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of our hypervisors (running several KVM VMs). This led us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+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 1352358] Re: Kernel 3.13 freezes sometimes at startup
Christopher M. Penalver, I can not run apport-collect because it does not use our http(s)-proxy via the environment-variables HTTP_PROXY and HTTPS_PROXY. I got ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out -- 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/1352358 Title: Kernel 3.13 freezes sometimes at startup Status in “linux” package in Ubuntu: Incomplete Bug description: We use Ubuntu 12.04 + 14.04 HWE. Sometimes the kernel freezes at startup. There is no kernelpanic. I can not use Systemrequest-Keys for restart. The only key that gives Feedback is the Numlock-Key (LED toggles). When i powercyle the Computer Grub has no countdown for booting the first Kernel. When I press Enter the Kernel starts normaly. I cannot find something in Syslog or somewhere else. I deactivated the bootparameter quiet und added the Parameter "console=tty0 console=ttyS0,115200n8". I connected the Computer via a Nullmodemcable with another computer and logged the bootprocess with minicom. The Logs are attached. I can not reproduce this Bug in Kernel linux-image-3.11.0-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352358/+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 1342000] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1342000 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw Status in “linux” package in Ubuntu: Incomplete Status in “qemu” package in Ubuntu: New Bug description: Problem Description --- ISST-KVM-UBUNTU1410-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image raw. Ubuntu installation to virtio-scsi disk type of raw, not able to find the driver by default and not listing virtio-scsi drivers to choose ---uname output--- [root@lizkvm home]# uname -a Linux lizkvm.isst.aus.stglabs.ibm.com 3.10.42-2001.pkvm2_1_1.3.ppc64 #1 SMP Tue Jun 17 13:13:10 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux [root@lizkvm home]# Steps to reproduce --- 1) [root@magkvm images]# virsh define lizg3.xml Domain lizg3 defined from lizg3.xml 2) [root@lizkvm home]# virsh dumpxml lizg3 lizg3 da4ce0fd-2268-45b8-b5ca-611ac7926e50 6606848 6606029 4 /machine hvm destroy restart restart /usr/bin/qemu-system-ppc64 system_u:system_r:svirt_t:s0:c79,c721 system_u:object_r:svirt_image_t:s0:c79,c721 3) [root@magkvm images]# virsh start --console lizg3 Domain lizg3 started Connected to domain lizg3 Escape character is ^] SLOF ** -->Configured network properly and then moved to Detect disks screen 4) Proceeded with the installation and when the disk partition screen comes up. Installer is not able to indentify the disk and asks to choose from the list of drivers as below [!] Detect disks ? ? ? ? No disk drive was detected. If you know the name of the driver needed ? ? by your disk drive, you can select it from the list.? ? ? ? Driver needed for your disk drive: ? ? ? ? continue with no disk drive ? ? login to iSCSI targets ? ? 3w-9xxx ? ? ? 3w-sas ? ? ? 3w- ? ? ? DAC960 ? ? ? a100u2w ? ? ? aacraid ? ? ? aic79xx ? ? ? aic7xxx ? ? ? ?? ? ? ??? moves; selects; activates buttons 4) verified for the drivers from the list and none of them belongs to virtio-scsi optional driver listed are: continue with no disk drive ? ? login to iSCSI targets ? ? 3w-9xxx ? ? ? 3w-sas ? ? ? 3w- ? ? ? DAC960
[Kernel-packages] [Bug 1352640] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2014-08-05 15:21 EDT--- (In reply to comment #5) > This bug is missing log files that will aid in diagnosing the problem... > However... there are no applicable log files in this case. The request is for Ubuntu to pick up the referenced kernel patch. Let me know if further info is required. Otherwise please remove the "incomplete" tag. Thx. -- 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/1352640 Title: Huge PCI BAR support needed for Ubuntu 14.10 Status in “linux” package in Ubuntu: Incomplete Bug description: == Comment: #0 - Brian Hart - 2014-08-04 17:26:34 == ---Problem Description--- Our project requires Huge BAR Support (i.e. support for PCI BAR spaces > 1G) in Ubuntu 14.10. Guo and Gavin are working on the kernel changes (and Sapphire/OPAL changes?) and have already submitted patches. The patches did not make the 3.16 cut-off, so will need to be back-ported to the 14.10 kernel. I believe the patches are the set described by: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119170.html Contact Information = Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com) ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Problem is seen with PCI adapters that request > 1G of BAR space. We've seen it with GPUs that request a BAR1 of size 16G. Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Add a PCI adapter which requests huge BAR space in the system. The huge BARs will not be assigned and the adapter will likely not initialize. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com): -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352640/+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 1352640] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2014-08-05 15:18 EDT--- (In reply to comment #4) > Thank you for taking the time to report this bug and helping to make Ubuntu > better. It seems that your bug report is not filed about a specific source > package though, rather it is just filed against Ubuntu in general. It is > important that bug reports be filed about source packages so that people > interested in the package can find the bugs about it. You can find some > hints about determining what package your bug might be about at > https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help > in the #ubuntu-bugs irc channel on Freenode. > Thanks. It was not clear what package to select since there is none named "kernel". I see now, per above like, the correct package for kernel is "linux". -- 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/1352640 Title: Huge PCI BAR support needed for Ubuntu 14.10 Status in “linux” package in Ubuntu: Incomplete Bug description: == Comment: #0 - Brian Hart - 2014-08-04 17:26:34 == ---Problem Description--- Our project requires Huge BAR Support (i.e. support for PCI BAR spaces > 1G) in Ubuntu 14.10. Guo and Gavin are working on the kernel changes (and Sapphire/OPAL changes?) and have already submitted patches. The patches did not make the 3.16 cut-off, so will need to be back-ported to the 14.10 kernel. I believe the patches are the set described by: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119170.html Contact Information = Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com) ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Problem is seen with PCI adapters that request > 1G of BAR space. We've seen it with GPUs that request a BAR1 of size 16G. Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Add a PCI adapter which requests huge BAR space in the system. The huge BARs will not be assigned and the adapter will likely not initialize. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com): -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352640/+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 1240940] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723]
Driver drops connection, because code for power saving mode can't wake up the device on lenovo B5400. So, couple months ago, I partially commented out code that is responsible for putting WiFi card to sleep. It works almost flawlessly on kernel 3.13-24-generic. It also worked on kernel 3.11. It is not perfect, but it is pretty usable. Just type: make, sudo make install, sudo modprobe rtl8723be https://github.com/kozak127/rtl8723be -- 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/1240940 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: This device is appearing in some OEM machines, but driver is not yet available upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1240940/+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 1342000] Re: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw Status in “linux” package in Ubuntu: Triaged Status in “qemu” package in Ubuntu: New Bug description: Problem Description --- ISST-KVM-UBUNTU1410-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image raw. Ubuntu installation to virtio-scsi disk type of raw, not able to find the driver by default and not listing virtio-scsi drivers to choose ---uname output--- [root@lizkvm home]# uname -a Linux lizkvm.isst.aus.stglabs.ibm.com 3.10.42-2001.pkvm2_1_1.3.ppc64 #1 SMP Tue Jun 17 13:13:10 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux [root@lizkvm home]# Steps to reproduce --- 1) [root@magkvm images]# virsh define lizg3.xml Domain lizg3 defined from lizg3.xml 2) [root@lizkvm home]# virsh dumpxml lizg3 lizg3 da4ce0fd-2268-45b8-b5ca-611ac7926e50 6606848 6606029 4 /machine hvm destroy restart restart /usr/bin/qemu-system-ppc64 system_u:system_r:svirt_t:s0:c79,c721 system_u:object_r:svirt_image_t:s0:c79,c721 3) [root@magkvm images]# virsh start --console lizg3 Domain lizg3 started Connected to domain lizg3 Escape character is ^] SLOF ** -->Configured network properly and then moved to Detect disks screen 4) Proceeded with the installation and when the disk partition screen comes up. Installer is not able to indentify the disk and asks to choose from the list of drivers as below [!] Detect disks ? ? ? ? No disk drive was detected. If you know the name of the driver needed ? ? by your disk drive, you can select it from the list.? ? ? ? Driver needed for your disk drive: ? ? ? ? continue with no disk drive ? ? login to iSCSI targets ? ? 3w-9xxx ? ? ? 3w-sas ? ? ? 3w- ? ? ? DAC960 ? ? ? a100u2w ? ? ? aacraid ? ? ? aic79xx ? ? ? aic7xxx ? ? ? ?? ? ? ??? moves; selects; activates buttons 4) verified for the drivers from the list and none of them belongs to virtio-scsi optional driver listed are: continue with no disk drive ? ? login to iSCSI targets ? ? 3w-9xxx ? ? ? 3w-sas ? ? ? 3w- ? ? ? DAC960 ? ? ? a100u2w ? ? ? aacraid ? ? ? aic79xx ? ? ? aic7xxx aic94xx ? ? aoe ? ? ? arcmsr ? ? aten ? ? ? atp870u ? ? ? bpck ? ? ? cciss ? ? ? comm ? ? ? cryptoloop ? ? ? dc395x dmx3191d ? ? dstr ? ? ? eata ? ? ? epat ? ? epia ? ? ? fdomain ? ? ? fit2 ? ? ? fit3 ? ? ? floppy ? ? ? friq frpw ? ? gdth ? ? ? hpsa ? ? ? hptiop ? ? ? imm ? ? ini
[Kernel-packages] [Bug 1337281] Re: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot
I can confirm what YAMAMOTO Hirotaka (ymmt2005) said. I upgraded from 3.2.0-64-generic to 3.2.0-67 and had lots of issues with Windows users connecting to network shares on a different subnet among other things. I rolled back to 3.2.0-64 and the problems disappeared. All Linux and Mac workstations saw no issues whatsoever. Are there any fixes for this that can be accomplished within /etc/sysctl.conf ? Thank you! -- 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/1337281 Title: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: In Progress Bug description: Since we installed the latest kernel update on our firewall this weekend (3.2.0-65.98) we got massive problems connecting from thunderbird (windows client) to an external imap-server (dovecot with tls). With our Linux client we got no problems. Opening or sending mails with attachments which was done in a second before the update, took some minutes after the update to kernel 3.2.0-65! Installing the kernel version 3.2.0-64 on our firewall system fixed the problem, also the newer kernel linux-generic-lts-trusty did fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337281/+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 1352995] [NEW] ERAT Multihit machine checks
You have been subscribed to a public bug: -- Problem Description -- Our project involves porting a 3rd-party out-of-tree module to LE Ubuntu on Power. We've been seeing occasional ERAT Multihit machine checks with kernels ranging from the LE Ubuntu 14.04 3.13-based kernel through the very latest 3.16-rc5 mainline kernels. Our kernels are running directly on top of OPAL/Sapphire in PowerNV mode, with no intervening KVM host. FSP dumps captured at the time of the ERAT detection show that there are duplicate mappings in force for the same real page, with the duplicate mappings being for different sized pages. So, for example, the same 4K real page will be referred to by a 4K mapping and an overlapping 16M mapping. Aneesh has been working with us on this. We are currently testing this patchset. (git format-patch --stdout format). We are still finding ERAT with this changes. Most of these changes are already posted externally. Some of them got updated after that. Current status is. When hitting multi hit erat, I don't find duplicate hash pte entries. So it possibly indicate a missed flush or a race. Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Dump the rest of 256 entries Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Done.. Dump the rest of 256 entries Done.. Found hugepage shift 0 for ea 3fff7d0f with ptep 1f283d8000383 Severe Machine check interrupt [Recovered] Initiator: CPU Error type: ERAT [Multihit] Effective address: 3fff7d0f That is what i am finding on machine check. I am searching the hash pte with base page size 4K and 64K and printing matching hash table entries. b_size = 15 and a_size = -1 both indicate 4K. -aneesh I guess we now have a race in the unmap path. I am auditing the hpte_slot_array usage. We do check for hpte_slot_array != NULL in invalidate. But if we hit two pmdp_splitting flush one will skip the invalidate as per current code and will go ahead and mark hpte_slot_array NULL. I have a patch in the repo which try to work around that. But I am not sure whether we really can have two pmdp_splitting flush simultaneously. because we call that under pmd_lock. Still need to look at the details. -aneesh I added more debug prints. And this is what i found. Before a hugepage flush I added debug prints to dump the hash table to see if we are failing to clear any hash table entries. After every update we seems to have clearly updated hash table. One MCE some of the relevant part of logs are pmd_hugepage_update dumping entries for 0x3fff7100 with clr = 0x set = 0x0 . . dump_hash_pte_group dumping entries for 0x3fff7191da8c with clr = 0x0 set = 0x0 func = dump_hash_pte_group, addr = 3fff7191da8c psize = 0 slot = 1174024 v = 4001a9245cff7181 r = 7dfb5d193 with b_size = 0 a_size = 0 count = 2333 func = dump_hash_pte_group, addr = 3fff7100 psize = 0 slot = 1155808 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 0 func = dump_hash_pte_group, addr = 3fff710a2000 psize = 0 slot = 1157104 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 162 func = dump_hash_pte_group, addr = 3fff710e6000 psize = 0 slot = 1156560 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 230 func = dump_hash_pte_group, addr = 3fff71378000 psize = 0 slot = 1161504 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 888 So we end up clearing the huge pmd with 0x3fff7100 and at that point we didn't had anything in hash table. That is the last pmdp_splitting_flush or pmd_hugepage_update even on that address. Can we audit the driver code to understand large/huge page usage and if it is making any x86 assumptions around the page table accessor. For example ppc64 rules around page table access are more strict than x86. We don't have flush_tlb_* functions and we need to make sure we hold ptl while updating page table and also flush the hash pte holding the lock. Attaching the log also -aneesh Aneesh writes: Can we audit the driver code to understand large/huge page usage and if it is making any x86 assumptions around the page table accessor. For example ppc64 rules around page table access are more strict than x86. We don't have flush_tlb_* functions and we need to make sure we hold ptl while updating page table and also flush the hash pte holding the lock. Yes, we can do that (all the driver code that's specific to linux is in the kernel-interface subdirectory, so you can take a look as well). But I'm not quite sure what we'd be looking for. The driver doesn't have any explicit awareness of huge-pages; it doesn't intend or expect to interact with them in any way. And I wouldn't expect the driver to be updating the kernel's page tables itself but rather to use of some set of (relatively safe) services to do that. So if you can tell us
[Kernel-packages] [Bug 1352995] Re: ERAT Multihit machine checks
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352995 Title: ERAT Multihit machine checks Status in “linux” package in Ubuntu: New Bug description: -- Problem Description -- Our project involves porting a 3rd-party out-of-tree module to LE Ubuntu on Power. We've been seeing occasional ERAT Multihit machine checks with kernels ranging from the LE Ubuntu 14.04 3.13-based kernel through the very latest 3.16-rc5 mainline kernels. Our kernels are running directly on top of OPAL/Sapphire in PowerNV mode, with no intervening KVM host. FSP dumps captured at the time of the ERAT detection show that there are duplicate mappings in force for the same real page, with the duplicate mappings being for different sized pages. So, for example, the same 4K real page will be referred to by a 4K mapping and an overlapping 16M mapping. Aneesh has been working with us on this. We are currently testing this patchset. (git format-patch --stdout format). We are still finding ERAT with this changes. Most of these changes are already posted externally. Some of them got updated after that. Current status is. When hitting multi hit erat, I don't find duplicate hash pte entries. So it possibly indicate a missed flush or a race. Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Dump the rest of 256 entries Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Done.. Dump the rest of 256 entries Done.. Found hugepage shift 0 for ea 3fff7d0f with ptep 1f283d8000383 Severe Machine check interrupt [Recovered] Initiator: CPU Error type: ERAT [Multihit] Effective address: 3fff7d0f That is what i am finding on machine check. I am searching the hash pte with base page size 4K and 64K and printing matching hash table entries. b_size = 15 and a_size = -1 both indicate 4K. -aneesh I guess we now have a race in the unmap path. I am auditing the hpte_slot_array usage. We do check for hpte_slot_array != NULL in invalidate. But if we hit two pmdp_splitting flush one will skip the invalidate as per current code and will go ahead and mark hpte_slot_array NULL. I have a patch in the repo which try to work around that. But I am not sure whether we really can have two pmdp_splitting flush simultaneously. because we call that under pmd_lock. Still need to look at the details. -aneesh I added more debug prints. And this is what i found. Before a hugepage flush I added debug prints to dump the hash table to see if we are failing to clear any hash table entries. After every update we seems to have clearly updated hash table. One MCE some of the relevant part of logs are pmd_hugepage_update dumping entries for 0x3fff7100 with clr = 0x set = 0x0 . . dump_hash_pte_group dumping entries for 0x3fff7191da8c with clr = 0x0 set = 0x0 func = dump_hash_pte_group, addr = 3fff7191da8c psize = 0 slot = 1174024 v = 4001a9245cff7181 r = 7dfb5d193 with b_size = 0 a_size = 0 count = 2333 func = dump_hash_pte_group, addr = 3fff7100 psize = 0 slot = 1155808 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 0 func = dump_hash_pte_group, addr = 3fff710a2000 psize = 0 slot = 1157104 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 162 func = dump_hash_pte_group, addr = 3fff710e6000 psize = 0 slot = 1156560 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 230 func = dump_hash_pte_group, addr = 3fff71378000 psize = 0 slot = 1161504 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 888 So we end up clearing the huge pmd with 0x3fff7100 and at that point we didn't had anything in hash table. That is the last pmdp_splitting_flush or pmd_hugepage_update even on that address. Can we audit the driver code to understand large/huge page usage and if it is making any x86 assumptions around the page table accessor. For example ppc64 rules around page table access are more strict than x86. We don't have flush_tlb_* functions and we need to make sure we hold ptl while updating page table and also flush the hash pte holding the lock. Attaching the log also -aneesh Aneesh writes: Can we audit the driver code to understand large/huge page usage and if it is making any x86 assumptions around the page table accessor. For example ppc64 rules around page table access are more strict than x86. We don't have flush_tlb_* functions and we need to make sure we hold ptl while updating page table and also flush the hash pte holding the lock. Yes, we can do that (all the driver code that's specific to lin
[Kernel-packages] [Bug 1327764] Re: [Acer Aspire V5-131] Broadcom BCM57765/57785 SD card reader does not work reliably under xubuntu 14.04
On my Aspire-V3-571, dmesg show the following [ 1562.408303] mmc0: Timeout waiting for hardware interrupt. [ 1562.410428] mmc0: error -110 whilst initialising SD card ** 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/1327764 Title: [Acer Aspire V5-131] Broadcom BCM57765/57785 SD card reader does not work reliably under xubuntu 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: To replicate the bug: "SD-card 4GB": Sandisk Extreme III SDHC 6 4GB "SD-card 8GB": Sandisk Ultra SDHC 6 8GB "SD-card 16GB": Sandisk Ultra SDHC I 6 16GB The three cards are not write protected and can be read/written to on xubuntu 14.04 using a usb card reader. Wifi is on, ethernet is off (no plug connected) Insert "SD 4GB" no action, the sd-card is not mounted on the desktop dmesg [ 1251.864572] mmc0: Timeout waiting for hardware interrupt. [ 1261.873344] mmc0: Timeout waiting for hardware interrupt. remove card [ 1267.803266] mmc0: Card removed during transfer! [ 1267.803280] mmc0: Resetting controller. Insert "SD 8GB" no action, the sd-card is not mounted on the desktop [ 1294.297766] mmc0: Timeout waiting for hardware interrupt. [ 1304.306477] mmc0: Timeout waiting for hardware interrupt. remove card [ 1314.041923] mmc0: Card removed during transfer! [ 1314.041936] mmc0: Resetting controller. Insert "SD 16GB" no action, the sd-card is not mounted on the desktop [ 1340.024393] mmc0: Timeout waiting for hardware interrupt. [ 1350.033134] mmc0: Timeout waiting for hardware interrupt. remove card [ 1350.965464] mmc0: Card removed during transfer! [ 1350.965476] mmc0: Resetting controller. Turn off wifi Plug ethernet cable [ 1366.425891] wlan0: deauthenticating from by local choice (reason=3) [ 1366.484200] cfg80211: Calling CRDA to update world regulatory domain [ 1366.486303] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1366.490460] cfg80211: World regulatory domain updated: [ 1366.490466] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 1366.490470] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 1366.490474] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 1366.490476] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 1366.490479] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 1366.490482] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 1399.174151] tg3 :04:00.0 eth0: Link is up at 1000 Mbps, full duplex [ 1399.174175] tg3 :04:00.0 eth0: Flow control is on for TX and on for RX [ 1399.174180] tg3 :04:00.0 eth0: EEE is enabled [ 1399.174225] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Insert "SD 4GB" Sd-card is mounted of the desktop, content can be listed. [ 1432.658733] mmc0: new high speed SDHC card at address d555 [ 1432.668127] mmcblk0: mmc0:d555 SD04G 3.79 GiB [ 1432.669165] mmcblk0: p1 Copy a file from the sd-card to user home -> fine Copy a file from home to the sd-card -> does not appear to work. [ 1545.393347] mmc0: Timeout waiting for hardware interrupt. [ 1545.394051] mmcblk0: error -110 transferring data, sector 1758336, nr 1024, cmd response 0x900, card status 0xc00 [ 1555.402075] mmc0: Timeout waiting for hardware interrupt. [ 1555.402244] end_request: I/O error, dev mmcblk0, sector 1758336 [ 1555.402260] end_request: I/O error, dev mmcblk0, sector 1758344 [ 1555.402270] end_request: I/O error, dev mmcblk0, sector 1758352 [ 1555.402279] end_request: I/O error, dev mmcblk0, sector 1758360 [ 1555.402287] end_request: I/O error, dev mmcblk0, sector 1758368 [ 1555.402295] end_request: I/O error, dev mmcblk0, sector 1758376 [ 1555.402303] end_request: I/O error, dev mmcblk0, sector 1758384 [ 1555.402311] end_request: I/O error, dev mmcblk0, sector 1758392 [ 1555.402318] end_request: I/O error, dev mmcblk0, sector 1758400 [ 1555.402326] end_request: I/O error, dev mmcblk0, sector 1758408 [ 1565.410834] mmc0: Timeout waiting for hardware interrupt. [ 1565.411194] mmcblk0: error -110 transferring data, sector 1759360, nr 1024, cmd response 0x900, card status 0xc00 [ 1575.419561] mmc0: Timeout waiting for hardware interrupt. [ 1575.419672] blk_update_request: 118 callbacks suppressed [ 1575.419676] end_request: I/O error, dev mmcblk0, sector 1759360 [ 1575.419682] end_request: I/O error, dev mmcblk0, sector 1759368 [ 1575.419686] end_request: I/O error, dev mmcblk0, sector 1759376 [ 1575.419690] end_request: I/O error, dev mmcblk0, sector 1759384 [ 1575.419694] end_request: I/O error, dev mmcblk0, sector 1759392 [ 1575.419698] end_request: I/O er
[Kernel-packages] [Bug 1353005] [NEW] sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment
You have been subscribed to a public bug: ---Problem Description--- sensors command is not getting executed in Ubuntu 14.10 ---uname output--- Linux lep8d 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- Install Ubuntu 14.10 iso on local hard disk of P8 machine in Non Virtualised environment. Install the lm-sensors ppc64le package on the same. root@lep8d:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. root@lep8d:~# echo $? 1 root@lep8d:~# sensors-detect # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors...No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor...No VIA Nano thermal sensor... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. After a big more digging I see: in Ubuntu where it is failing, there is: $ cat /boot/config-3.16.0-6-generic | grep -i sensor | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m And in PowerKVM where it is working, there is: $ cat /boot/config-3.10.42-2004.pkvm2_1_1.8.ppc64 | grep -i sensors | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IBMPOWERNV=y So now I think problem is: Ubuntu is missing "ibmpowernv", i.e. the powernv hwmon driver for sensors, as described here: http://lists.lm-sensors.org/pipermail/lm-sensors/2014-May/041867.html Adding to copy: Neelesh Gupta, who is author of this module. Neelesh: Am I correct that this is the missing module in Ubuntu? Is there a kernel patch Ubuntu needs to pick up, or perhaps they already have the patch but just need to fix their kernel config? Thx -DaveH. Yes, 'ibmpowernv' module is missing from Ubuntu 14.10. It's already been applied to the -next tree and should be available to mainline soon. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bugnameltc-114041 severity-high targetmilestone-inin1410 -- sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment https://bugs.launchpad.net/bugs/1353005 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352995] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1352995 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352995 Title: ERAT Multihit machine checks Status in “linux” package in Ubuntu: Incomplete Bug description: -- Problem Description -- Our project involves porting a 3rd-party out-of-tree module to LE Ubuntu on Power. We've been seeing occasional ERAT Multihit machine checks with kernels ranging from the LE Ubuntu 14.04 3.13-based kernel through the very latest 3.16-rc5 mainline kernels. Our kernels are running directly on top of OPAL/Sapphire in PowerNV mode, with no intervening KVM host. FSP dumps captured at the time of the ERAT detection show that there are duplicate mappings in force for the same real page, with the duplicate mappings being for different sized pages. So, for example, the same 4K real page will be referred to by a 4K mapping and an overlapping 16M mapping. Aneesh has been working with us on this. We are currently testing this patchset. (git format-patch --stdout format). We are still finding ERAT with this changes. Most of these changes are already posted externally. Some of them got updated after that. Current status is. When hitting multi hit erat, I don't find duplicate hash pte entries. So it possibly indicate a missed flush or a race. Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Dump the rest of 256 entries Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Done.. Dump the rest of 256 entries Done.. Found hugepage shift 0 for ea 3fff7d0f with ptep 1f283d8000383 Severe Machine check interrupt [Recovered] Initiator: CPU Error type: ERAT [Multihit] Effective address: 3fff7d0f That is what i am finding on machine check. I am searching the hash pte with base page size 4K and 64K and printing matching hash table entries. b_size = 15 and a_size = -1 both indicate 4K. -aneesh I guess we now have a race in the unmap path. I am auditing the hpte_slot_array usage. We do check for hpte_slot_array != NULL in invalidate. But if we hit two pmdp_splitting flush one will skip the invalidate as per current code and will go ahead and mark hpte_slot_array NULL. I have a patch in the repo which try to work around that. But I am not sure whether we really can have two pmdp_splitting flush simultaneously. because we call that under pmd_lock. Still need to look at the details. -aneesh I added more debug prints. And this is what i found. Before a hugepage flush I added debug prints to dump the hash table to see if we are failing to clear any hash table entries. After every update we seems to have clearly updated hash table. One MCE some of the relevant part of logs are pmd_hugepage_update dumping entries for 0x3fff7100 with clr = 0x set = 0x0 . . dump_hash_pte_group dumping entries for 0x3fff7191da8c with clr = 0x0 set = 0x0 func = dump_hash_pte_group, addr = 3fff7191da8c psize = 0 slot = 1174024 v = 4001a9245cff7181 r = 7dfb5d193 with b_size = 0 a_size = 0 count = 2333 func = dump_hash_pte_group, addr = 3fff7100 psize = 0 slot = 1155808 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 0 func = dump_hash_pte_group, addr = 3fff710a2000 psize = 0 slot = 1157104 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 162 func = dump_hash_pte_group, addr = 3fff710e6000 psize = 0 slot = 1156560 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 230 func = dump_hash_pte_group, addr = 3fff71378000 psize = 0 slot = 1161504 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 888 So we end up clearing the huge pmd with 0x3fff7100 and at that point we didn't had anything in hash table. That is the last pmdp_splitting_flush or pmd_hugepage_update even on that address. Can we audit the driver code to understand large/huge page usage and if it is making any x86 assumptions around the page table accessor. For example ppc64 rules around page table access are more strict than x86. We don't have flush_tlb_* functions and we need to make sure we hold ptl while updating page table and also flush the hash pte holding the lock. Attaching the l
[Kernel-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: unity (Ubuntu Saucy) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Touch Landing Plan: Fix Released Status in Unity: Confirmed Status in Upstart: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: Invalid Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/landing-plan/+bug/1235649/+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 1353005] Re: sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353005 Title: sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment Status in “linux” package in Ubuntu: New Bug description: ---Problem Description--- sensors command is not getting executed in Ubuntu 14.10 ---uname output--- Linux lep8d 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- Install Ubuntu 14.10 iso on local hard disk of P8 machine in Non Virtualised environment. Install the lm-sensors ppc64le package on the same. root@lep8d:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. root@lep8d:~# echo $? 1 root@lep8d:~# sensors-detect # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors...No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor...No VIA Nano thermal sensor... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. After a big more digging I see: in Ubuntu where it is failing, there is: $ cat /boot/config-3.16.0-6-generic | grep -i sensor | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m And in PowerKVM where it is working, there is: $ cat /boot/config-3.10.42-2004.pkvm2_1_1.8.ppc64 | grep -i sensors | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IBMPOWERNV=y So now I think problem is: Ubuntu is missing "ibmpowernv", i.e. the powernv hwmon driver for sensors, as described here: http://lists.lm-sensors.org/pipermail/lm-sensors/2014-May/041867.html Adding to copy: Neelesh Gupta, who is author of this module. Neelesh: Am I correct that this is the missing module in Ubuntu? Is there a kernel patch Ubuntu needs to pick up, or perhaps they already have the patch but just need to fix their kernel config? Thx -DaveH. Yes, 'ibmpowernv' module is missing from Ubuntu 14.10. It's already been applied to the -next tree and should be available to mainline soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353005/+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 1352567] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170502/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. d
[Kernel-packages] [Bug 1352567] Re: OOPS in cpufreq driver with AMD Kaveri CPU
apport information ** Description changed: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: + country UA: + (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR + (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR + (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR + Card0.Amixer.info: Error: [Errno 2] No such file or directory + Card0.Amixer.values: Error: [Errno 2] No such file or directory + Card1.Amixer.info: Error: [Errno 2] No such file or directory + Card1.Amixer.values: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-07-30 (5 days ago) + InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + MachineType: ASUS All Series + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 + ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-32-generic N/A + linux-backports-modules-3.13.0-32-generic N/A + linux-firmware 1.127.5 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty + Uname: Linux 3.13.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 06/25/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0702 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: AM1M-A + 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.:bvr0702:bd06/25/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rn
[Kernel-packages] [Bug 1352567] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170503/+files/Card0.Codecs.codec.0.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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To b
[Kernel-packages] [Bug 1352567] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170507/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.
[Kernel-packages] [Bug 1352567] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170506/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi
[Kernel-packages] [Bug 1352567] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170510/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 1352567] Card1.Codecs.codec.0.txt
apport information ** Attachment added: "Card1.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170504/+files/Card1.Codecs.codec.0.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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To b
[Kernel-packages] [Bug 1352567] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170505/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.
[Kernel-packages] [Bug 1352567] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170511/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by
[Kernel-packages] [Bug 1352567] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170508/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.
[Kernel-packages] [Bug 1352567] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170513/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.boar
[Kernel-packages] [Bug 1352567] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170512/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 1352567] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170509/+files/PciMultimedia.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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.
[Kernel-packages] [Bug 1352567] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170514/+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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.b
[Kernel-packages] [Bug 1352567] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1352567/+attachment/4170515/+files/WifiSyslog.txt ** 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/1352567 Title: OOPS in cpufreq driver with AMD Kaveri CPU Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally I get my machine hung completely. Fortunately, I've got and saved oops listing using netconsole before hang, and here it is [1]. Here is little piece of oops from the link above: === [15051.270461] BUG: unable to handle kernel paging request at ff5ae8e4 [15051.271583] IP: [] srcu_notifier_call_chain+0xe/0x20 … [15051.956205] Call Trace: [15051.980641] [] ? __cpufreq_notify_transition+0x95/0x1e0 [15052.005640] [] cpufreq_notify_transition+0x3e/0x70 [15052.030240] [] cpufreq_freq_transition_begin+0xe8/0x130 [15052.054522] [] ? ucs2_strncmp+0x70/0x70 [15052.078208] [] __target_index+0xbf/0x1a0 [15052.101348] [] __cpufreq_driver_target+0xfc/0x160 [15052.124250] [] od_check_cpu+0xa4/0xb0 [15052.146789] [] dbs_check_cpu+0x16c/0x1c0 [15052.168935] [] od_dbs_timer+0x11d/0x180 [15052.190607] [] process_one_work+0x17f/0x4c0 [15052.211825] [] worker_thread+0x11b/0x3f0 [15052.232490] [] ? create_and_start_worker+0x80/0x80 [15052.253127] [] kthread+0xc9/0xe0 [15052.273292] [] ? flush_kthread_worker+0xb0/0xb0 [15052.293487] [] ret_from_fork+0x7c/0xb0 [15052.313544] [] ? flush_kthread_worker+0xb0/0xb0 … === Also here is my lspci [2] and cpuinfo [3] as well. Vanilla 3.15.8 and 3.16.0 are affected as well as latest Ubuntu 3.13 kernel. No visible reason to trigger the bug. After hang machine doesn't respond via network, there's no disk IO, and also it doesn't respond to pressing power button in order to perform soft off. And here is kernel bugzilla bugreport [4]. [1] https://gist.github.com/085af9da81197faf6637 [2] https://gist.github.com/318ebda5576b099590b8 [3] https://gist.github.com/9c1307463c7ad6835b2d [4] https://bugzilla.kernel.org/show_bug.cgi?id=81701 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.16.0-031600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-32-generic root=UUID=1f394420-1439-4dd6-9b70-0cd56bed41fd ro rootflags=subvol=@ consoleblank=0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1349572] Re: Wireless network disconnections on Dell XPS 13
It sounds like the 3.13 test build is better but still not perfect. Is this correct? Once you feel confident in your results, I'd appreciate it if you could try 3.16 for a longer period and see how it compares to the 3.13 test build. If it's better then there may be additional improvements we can backport to 3.13 to improve the connection. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349572 Title: Wireless network disconnections on Dell XPS 13 Status in “linux” package in Ubuntu: Incomplete Bug description: With kernel 3.13.0.30 and 22.1.7.0, there are lots of wireless disconnections. Tested also with kernel 3.13.0.32 and 22.24.8.0 , also lots of wireles disconnections. The AP is an ASL-26555 from Movistar(Spain). Firmware version: v2.0.0.51B_ESv6 Seems that when the computer is working for some time it is more easy to reproduce this beahviour. Added this bug as sugested in #1293569, comment #91. 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/controlC1: marcel 2611 F pulseaudio /dev/snd/controlC0: marcel 2611 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 28 22:20:19 2014 HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec InstallationDate: Installed on 2014-01-23 (186 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 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.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-17 (101 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcel 2644 F pulseaudio /dev/snd/controlC0: marcel 2644 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec InstallationDate: Installed on 2014-01-23 (187 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-17 (103 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcel 2644 F pulseaudio /dev/snd/controlC0: marcel 2644 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec InstallationDate: Installed on 2014-01-23 (187 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet spla
[Kernel-packages] [Bug 1353005] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1353005 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353005 Title: sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment Status in “linux” package in Ubuntu: Incomplete Bug description: ---Problem Description--- sensors command is not getting executed in Ubuntu 14.10 ---uname output--- Linux lep8d 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- Install Ubuntu 14.10 iso on local hard disk of P8 machine in Non Virtualised environment. Install the lm-sensors ppc64le package on the same. root@lep8d:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. root@lep8d:~# echo $? 1 root@lep8d:~# sensors-detect # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors...No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor...No VIA Nano thermal sensor... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. After a big more digging I see: in Ubuntu where it is failing, there is: $ cat /boot/config-3.16.0-6-generic | grep -i sensor | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m And in PowerKVM where it is working, there is: $ cat /boot/config-3.10.42-2004.pkvm2_1_1.8.ppc64 | grep -i sensors | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IBMPOWERNV=y So now I think problem is: Ubuntu is missing "ibmpowernv", i.e. the powernv hwmon driver for sensors, as described here: http://lists.lm-sensors.org/pipermail/lm-sensors/2014-May/041867.html Adding to copy: Neelesh Gupta, who is author of this module. Neelesh: Am I correct that this is the missing module in Ubuntu? Is there a kernel patch Ubuntu needs to pick up, or perhaps they already have the patch but just need to fix their kernel config? Thx -DaveH. Yes, 'ibmpowernv' module is missing from Ubuntu 14.10. It's already been applied to the -next tree and should be available to mainline soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pa
[Kernel-packages] [Bug 1353021] [NEW] USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04
Public bug reported: With the release of Ubuntu 14.04 I've been investigating an issue with a software library I maintain to talk to USB based HID signature pads. I believe I've narrowed the issue down to the HIDRAW implementation released with Ubuntu 14.04. Essentially what seems to be failing is the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get a feature report results in a failure with a ENODEV error code. The devices I'm testing with are USB signature pads (http://www.scriptel.com). These signature pads use HID feature reports to communicate capabilities and to set up the device. I can provide further information along with USB/HID descriptors if it would be helpful. I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version: Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This kernel exhibits the problematic behavior, but when testing with Ubuntu 13.10 Desktop (x64): Linux 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The 13.10 kernel's version of HIDRAW seems to work correctly. I've also tested with the vanilla kernel: Linux 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux The vanilla kernel appears to work correctly as well. Kernel source used was downloaded from: https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz The configuration file used was from config-3.13.0-32-generic provided in linux-image-3.13.0-32-generic I believe the breaking change was made as part of commit aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu- trusty.git. I have attached a simple C program to demonstrate the problem. You'll need a USB HID device with known feature reports. Please let me know if I can provide any additional information or be of any assistance. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mpowers2863 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 13:51:39 2014 HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1762II1.50U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CZ-17 dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: CZ-17 dmi.product.version: REV:1.0 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353021 Title: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: With the release of Ubuntu 14.04 I've been investigating an issue with a software library I maintain to talk to USB based HID signature pads. I believe I've narrowed the issue down to the HIDRAW implementation released with Ubuntu 14.04. Essentially what seems to be failing is the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get a feature report results in a failure with a ENODEV error code. The devices I'm testing with are USB signature pads (http://www.scriptel.com). These signature pads use HID feature reports to communicate capabilities and to set up the device. I can provide further information along with USB/HID descriptors if it would be helpful. I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version: Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This kernel exhibits the problematic behavior, but when testing with Ubuntu 13.10 Desktop (x64): Linux 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 x86_64
[Kernel-packages] [Bug 1353021] Re: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04
** Attachment added: "Example program to demonstrate the problem." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353021/+attachment/4170542/+files/ioctl-test.c -- 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/1353021 Title: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: With the release of Ubuntu 14.04 I've been investigating an issue with a software library I maintain to talk to USB based HID signature pads. I believe I've narrowed the issue down to the HIDRAW implementation released with Ubuntu 14.04. Essentially what seems to be failing is the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get a feature report results in a failure with a ENODEV error code. The devices I'm testing with are USB signature pads (http://www.scriptel.com). These signature pads use HID feature reports to communicate capabilities and to set up the device. I can provide further information along with USB/HID descriptors if it would be helpful. I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version: Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This kernel exhibits the problematic behavior, but when testing with Ubuntu 13.10 Desktop (x64): Linux 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The 13.10 kernel's version of HIDRAW seems to work correctly. I've also tested with the vanilla kernel: Linux 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux The vanilla kernel appears to work correctly as well. Kernel source used was downloaded from: https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz The configuration file used was from config-3.13.0-32-generic provided in linux-image-3.13.0-32-generic I believe the breaking change was made as part of commit aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu- trusty.git. I have attached a simple C program to demonstrate the problem. You'll need a USB HID device with known feature reports. Please let me know if I can provide any additional information or be of any assistance. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mpowers2863 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 13:51:39 2014 HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1762II1.50U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CZ-17 dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: CZ-17 dmi.product.version: REV:1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353021/+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 1353021] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353021 Title: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: With the release of Ubuntu 14.04 I've been investigating an issue with a software library I maintain to talk to USB based HID signature pads. I believe I've narrowed the issue down to the HIDRAW implementation released with Ubuntu 14.04. Essentially what seems to be failing is the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get a feature report results in a failure with a ENODEV error code. The devices I'm testing with are USB signature pads (http://www.scriptel.com). These signature pads use HID feature reports to communicate capabilities and to set up the device. I can provide further information along with USB/HID descriptors if it would be helpful. I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version: Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This kernel exhibits the problematic behavior, but when testing with Ubuntu 13.10 Desktop (x64): Linux 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The 13.10 kernel's version of HIDRAW seems to work correctly. I've also tested with the vanilla kernel: Linux 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux The vanilla kernel appears to work correctly as well. Kernel source used was downloaded from: https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz The configuration file used was from config-3.13.0-32-generic provided in linux-image-3.13.0-32-generic I believe the breaking change was made as part of commit aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu- trusty.git. I have attached a simple C program to demonstrate the problem. You'll need a USB HID device with known feature reports. Please let me know if I can provide any additional information or be of any assistance. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mpowers2863 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 13:51:39 2014 HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1762II1.50U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CZ-17 dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: CZ-17 dmi.product.version: REV:1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353021/+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 1352994] [NEW] remap_4K_pfn() safety improvement needed for Ubuntu 14.10
You have been subscribed to a public bug: == Comment: #0 - Brian Hart - 2014-08-04 17:41:57 == ---Problem Description--- The current implementation of remap_4k_pfn() trusts that it's safe to map the PFN supplied by the requestor. But there may be PFNs that are not safe to map via remap_4k_pfn(). (For example, the addresses at which PCI MMIO regions are mapped in some hypervisor configurations.) When an unsafe PFN passes through remap_4k_pfn() some address bits may be unknowingly dropped by the underlying remapping routines. When that happens the remap will appear to succeed, but any later attempt to use the mapping will checkstop the machine because the truncated target address is not present in the machine. A patch has been submitted that will cause remap_4k_pfn() to detect and reject these unsafe requests: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119179.html Our project needs some form of this safety improvement in the Ubuntu 14.10 release. ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- The problem requires a hypervisor that allows PCI MMIO regions to span above the 46-bit line, and a device driver that maps MMIO regions using remap_4k_pfn(). I can provide detailed instructions and a driver upon request. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bugnameltc-114193 severity-critical targetmilestone-inin--- -- remap_4K_pfn() safety improvement needed for Ubuntu 14.10 https://bugs.launchpad.net/bugs/1352994 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353005] Re: sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment
** 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/1353005 Title: sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment Status in “linux” package in Ubuntu: Confirmed Bug description: ---Problem Description--- sensors command is not getting executed in Ubuntu 14.10 ---uname output--- Linux lep8d 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- Install Ubuntu 14.10 iso on local hard disk of P8 machine in Non Virtualised environment. Install the lm-sensors ppc64le package on the same. root@lep8d:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. root@lep8d:~# echo $? 1 root@lep8d:~# sensors-detect # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors...No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor...No VIA Nano thermal sensor... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. After a big more digging I see: in Ubuntu where it is failing, there is: $ cat /boot/config-3.16.0-6-generic | grep -i sensor | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m And in PowerKVM where it is working, there is: $ cat /boot/config-3.10.42-2004.pkvm2_1_1.8.ppc64 | grep -i sensors | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IBMPOWERNV=y So now I think problem is: Ubuntu is missing "ibmpowernv", i.e. the powernv hwmon driver for sensors, as described here: http://lists.lm-sensors.org/pipermail/lm-sensors/2014-May/041867.html Adding to copy: Neelesh Gupta, who is author of this module. Neelesh: Am I correct that this is the missing module in Ubuntu? Is there a kernel patch Ubuntu needs to pick up, or perhaps they already have the patch but just need to fix their kernel config? Thx -DaveH. Yes, 'ibmpowernv' module is missing from Ubuntu 14.10. It's already been applied to the -next tree and should be available to mainline soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353005/+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 1352994] Re: remap_4K_pfn() safety improvement needed for Ubuntu 14.10
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352994 Title: remap_4K_pfn() safety improvement needed for Ubuntu 14.10 Status in “linux” package in Ubuntu: Incomplete Bug description: == Comment: #0 - Brian Hart - 2014-08-04 17:41:57 == ---Problem Description--- The current implementation of remap_4k_pfn() trusts that it's safe to map the PFN supplied by the requestor. But there may be PFNs that are not safe to map via remap_4k_pfn(). (For example, the addresses at which PCI MMIO regions are mapped in some hypervisor configurations.) When an unsafe PFN passes through remap_4k_pfn() some address bits may be unknowingly dropped by the underlying remapping routines. When that happens the remap will appear to succeed, but any later attempt to use the mapping will checkstop the machine because the truncated target address is not present in the machine. A patch has been submitted that will cause remap_4k_pfn() to detect and reject these unsafe requests: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119179.html Our project needs some form of this safety improvement in the Ubuntu 14.10 release. ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- The problem requires a hypervisor that allows PCI MMIO regions to span above the 46-bit line, and a device driver that maps MMIO regions using remap_4k_pfn(). I can provide detailed instructions and a driver upon request. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352994/+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 1352640] Re: Huge PCI BAR support needed for Ubuntu 14.10
** 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/1352640 Title: Huge PCI BAR support needed for Ubuntu 14.10 Status in “linux” package in Ubuntu: Confirmed Bug description: == Comment: #0 - Brian Hart - 2014-08-04 17:26:34 == ---Problem Description--- Our project requires Huge BAR Support (i.e. support for PCI BAR spaces > 1G) in Ubuntu 14.10. Guo and Gavin are working on the kernel changes (and Sapphire/OPAL changes?) and have already submitted patches. The patches did not make the 3.16 cut-off, so will need to be back-ported to the 14.10 kernel. I believe the patches are the set described by: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119170.html Contact Information = Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com) ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Problem is seen with PCI adapters that request > 1G of BAR space. We've seen it with GPUs that request a BAR1 of size 16G. Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Add a PCI adapter which requests huge BAR space in the system. The huge BARs will not be assigned and the adapter will likely not initialize. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Brian Hart (ha...@us.ibm.com), Dave Marquardt (davem...@us.ibm.com): -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352640/+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 1352995] Re: ERAT Multihit machine checks
** 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/1352995 Title: ERAT Multihit machine checks Status in “linux” package in Ubuntu: Confirmed Bug description: -- Problem Description -- Our project involves porting a 3rd-party out-of-tree module to LE Ubuntu on Power. We've been seeing occasional ERAT Multihit machine checks with kernels ranging from the LE Ubuntu 14.04 3.13-based kernel through the very latest 3.16-rc5 mainline kernels. Our kernels are running directly on top of OPAL/Sapphire in PowerNV mode, with no intervening KVM host. FSP dumps captured at the time of the ERAT detection show that there are duplicate mappings in force for the same real page, with the duplicate mappings being for different sized pages. So, for example, the same 4K real page will be referred to by a 4K mapping and an overlapping 16M mapping. Aneesh has been working with us on this. We are currently testing this patchset. (git format-patch --stdout format). We are still finding ERAT with this changes. Most of these changes are already posted externally. Some of them got updated after that. Current status is. When hitting multi hit erat, I don't find duplicate hash pte entries. So it possibly indicate a missed flush or a race. Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Dump the rest of 256 entries Dar value is 3fff7d0f psize 0 slot = 453664 v = 40001f0d74ff7d01 r = 7ca0f0196 with b_size = 15 a_size = -1 Done.. Dump the rest of 256 entries Done.. Found hugepage shift 0 for ea 3fff7d0f with ptep 1f283d8000383 Severe Machine check interrupt [Recovered] Initiator: CPU Error type: ERAT [Multihit] Effective address: 3fff7d0f That is what i am finding on machine check. I am searching the hash pte with base page size 4K and 64K and printing matching hash table entries. b_size = 15 and a_size = -1 both indicate 4K. -aneesh I guess we now have a race in the unmap path. I am auditing the hpte_slot_array usage. We do check for hpte_slot_array != NULL in invalidate. But if we hit two pmdp_splitting flush one will skip the invalidate as per current code and will go ahead and mark hpte_slot_array NULL. I have a patch in the repo which try to work around that. But I am not sure whether we really can have two pmdp_splitting flush simultaneously. because we call that under pmd_lock. Still need to look at the details. -aneesh I added more debug prints. And this is what i found. Before a hugepage flush I added debug prints to dump the hash table to see if we are failing to clear any hash table entries. After every update we seems to have clearly updated hash table. One MCE some of the relevant part of logs are pmd_hugepage_update dumping entries for 0x3fff7100 with clr = 0x set = 0x0 . . dump_hash_pte_group dumping entries for 0x3fff7191da8c with clr = 0x0 set = 0x0 func = dump_hash_pte_group, addr = 3fff7191da8c psize = 0 slot = 1174024 v = 4001a9245cff7181 r = 7dfb5d193 with b_size = 0 a_size = 0 count = 2333 func = dump_hash_pte_group, addr = 3fff7100 psize = 0 slot = 1155808 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 0 func = dump_hash_pte_group, addr = 3fff710a2000 psize = 0 slot = 1157104 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 162 func = dump_hash_pte_group, addr = 3fff710e6000 psize = 0 slot = 1156560 v = 4001a9245cff7105 r = 7cc038196 with b_size = 0 a_size = 9 count = 230 func = dump_hash_pte_group, addr = 3fff71378000 psize = 0 slot = 1161504 v = 4001a9245cff7105 r = 7cc038116 with b_size = 0 a_size = 9 count = 888 So we end up clearing the huge pmd with 0x3fff7100 and at that point we didn't had anything in hash table. That is the last pmdp_splitting_flush or pmd_hugepage_update even on that address. Can we audit the driver code to understand large/huge page usage and if it is making any x86 assumptions around the page table accessor. For example ppc64 rules around page table access are more strict than x86. We don't have flush_tlb_* functions and we need to make sure we hold ptl while updating page table and also flush the hash pte holding the lock. Attaching the log also -aneesh Aneesh writes: Can we audit the driver code to understand large/huge page usage and if it is making any x86 assumptions around the page table accessor. For example ppc64 rules around page table access are more strict than x86. We don't have flush_tlb_* functions and we need to make sure we hold ptl while updating page table and also flush the hash pte holding the lock. Yes, we can do that (all the driv
[Kernel-packages] [Bug 1352994] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1352994 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352994 Title: remap_4K_pfn() safety improvement needed for Ubuntu 14.10 Status in “linux” package in Ubuntu: Incomplete Bug description: == Comment: #0 - Brian Hart - 2014-08-04 17:41:57 == ---Problem Description--- The current implementation of remap_4k_pfn() trusts that it's safe to map the PFN supplied by the requestor. But there may be PFNs that are not safe to map via remap_4k_pfn(). (For example, the addresses at which PCI MMIO regions are mapped in some hypervisor configurations.) When an unsafe PFN passes through remap_4k_pfn() some address bits may be unknowingly dropped by the underlying remapping routines. When that happens the remap will appear to succeed, but any later attempt to use the mapping will checkstop the machine because the truncated target address is not present in the machine. A patch has been submitted that will cause remap_4k_pfn() to detect and reject these unsafe requests: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-July/119179.html Our project needs some form of this safety improvement in the Ubuntu 14.10 release. ---uname output--- Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- The problem requires a hypervisor that allows PCI MMIO regions to span above the 46-bit line, and a device driver that maps MMIO regions using remap_4k_pfn(). I can provide detailed instructions and a driver upon request. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352994/+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 1050352] Re: [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects and connects
I can confirm this same behavour and error as the OP using a Gigabyte GA-990FXA-UD3 motherboard. USB3.0 external drive (Seagate GoFlex) does not function in USB3.0 port, but does work in USB2 ports (at USB2 speeds). USB3 flash drives DO work in USB3 ports, but do not work at USB3.0 speeds. -- 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/1050352 Title: [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects and connects Status in “linux” package in Ubuntu: Expired Bug description: Ubuntu 12.10 AMD64, kernel 3.5.0-14.16. External hard drive Hitachi Touro Desk 3.0 connected to USB 3.0 port. Gets disconnected randomly and then connected again. Only happens with USB 3.0 connection (xhci). WORKAROUND: When plugged to USB 2.0 (ehci) port it works ok. Attached is related kernel log portion: there is nothing special there except for these lines: 11-2: Parent hub missing LPM exit latency info. Power management will be impacted. usb 11-2: USB disconnect, device number 2 --- AcpiTables: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing /usr/share/apport/dump_acpi_tables.py: Permission denied ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dmitry 3011 F pulseaudio /dev/snd/controlC1: dmitry 3011 F pulseaudio /dev/snd/controlC0: dmitry 3011 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e3fa02f8-4f15-4f00-9d79-e982d4837b5c IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P55A-UD4 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=33c3405d-4b3c-4b5c-a1c3-fd2c7bad1c79 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 RelatedPackageVersions: linux-restricted-modules-3.5.0-14-generic N/A linux-backports-modules-3.5.0-14-generic N/A linux-firmware1.91 RfKill: Tags: quantal running-unity Uname: Linux 3.5.0-14-generic x86_64 UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago) UserGroups: adm cdrom dialout fuse kvm libvirtd lpadmin plugdev pulse pulse-access sambashare sudo vboxusers wireshark dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P55A-UD4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1050352/+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 1353050] [NEW] External USB3 device does not work in USB3 port
Public bug reported: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description:Linux Mint 17 Qiana Release:17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 using xhci_hcd [ 2173.864136] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2173.864388] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2173.864612] usb 9-4: USB disconnect, device number 6 [ 2174.252856] usb 9-4: new SuperSpeed USB device number 7 using xhci_hcd [ 2174.268644] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2174.269349] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2174.269357] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2174.269364] usb 9-4: Pr
[Kernel-packages] [Bug 1353050] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1353050 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353050 Title: External USB3 device does not work in USB3 port Status in “linux” package in Ubuntu: Incomplete Bug description: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProd
[Kernel-packages] [Bug 379780]
Hi, sorry for reopening such an old bug, but I found it via Google searching for my problem and the information in here was very helpful. So I thought it would be a good idea to put this related information here. The problem: The solution explained here is not working for me. I set both variables I found to "disabled": # udevadm info -q all -n /dev/sda |grep SMART E: ID_ATA_FEATURE_SET_SMART=0 E: ID_ATA_FEATURE_SET_SMART_ENABLED=0 But the drive is still polled. I verified it using # udisksctl monitor Distribution is openSUSE 13.1 and udisks2 version is 2.1.1. Any hints what is wrong here? I have a some machines with SSDs for OS and additional Western Digital drives that would be in standby most of the time if udisks wouldn't poll them. Standby timeout cannot be set low enough for the drives. With udisks1 disabling polling was working as described in this bug and I was able to use smartd to check the SMART status, because it is possible to - adjustable polling time and - polling is working on drives in standby without waking them up. cheers, Jochen -- 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/379780 Title: CD-ROM polling on some Optiarc drives causes high CPU usage Status in The Linux Kernel: Confirmed Status in abstraction for enumerating and managing block devices: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Bug description: Binary package hint: udev Before I upgraded the udev version of jaunty from 141-1 to 141-1.1, top reported about 2% total cpu usage when idle. After the update, it rarely drops below 35%. Though top lists udevd among the more cpu hungry processes, it is only listed with about 3%, while system (in line 3) almost never drops below 20%. I am using the amd64 version of Xubuntu 9.04 on a Acer Extensa 5230 laptop with a 2 GHz Intel Celeron processor, and I have my root, home and swap partitions encrypted with luks. I did a fresh install and installed nothing but the software updates. The output of top looks like this: top - 18:47:33 up 15 min, 2 users, load average: 1.48, 1.99, 1.50 Tasks: 125 total, 3 running, 122 sleeping, 0 stopped, 0 zombie Cpu(s): 11.3%us, 23.9%sy, 0.0%ni, 60.1%id, 0.0%wa, 4.3%hi, 0.3%si, 0.0%st Mem:940212k total, 637176k used, 303036k free, 872k buffers Swap: 2103444k total,0k used, 2103444k free, 346116k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 939 root 16 -4 16792 600 296 S 3.0 0.1 0:17.03 udevd 15937 haldaemo 20 0 36304 4872 3756 S 1.7 0.5 0:04.29 hald 16403 root 20 0 451m 51m 17m R 1.7 5.6 0:25.92 Xorg 30 root 15 -5 000 S 0.7 0.0 0:05.52 scsi_eh_1 5480 andreas 20 0 19116 1328 988 R 0.3 0.1 0:00.89 top 22747 andreas 20 0 174m 17m 8960 R 0.3 1.9 0:01.14 xfce4-terminal 1 root 20 0 4104 924 632 S 0.0 0.1 0:00.87 init 2 root 15 -5 000 S 0.0 0.0 0:00.00 kthreadd 3 root RT -5 000 S 0.0 0.0 0:00.00 migration/0 4 root 15 -5 000 S 0.0 0.0 0:00.00 ksoftirqd/0 5 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/0 6 root 15 -5 000 S 0.0 0.0 0:00.65 events/0 7 root 15 -5 000 S 0.0 0.0 0:00.00 khelper 8 root RT -5 000 S 0.0 0.0 0:00.00 kstop/0 9 root 15 -5 000 S 0.0 0.0 0:00.00 kintegrityd/0 ... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/379780/+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 379780] Re: CD-ROM polling on some Optiarc drives causes high CPU usage
** Changed in: udisks Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/379780 Title: CD-ROM polling on some Optiarc drives causes high CPU usage Status in The Linux Kernel: Confirmed Status in abstraction for enumerating and managing block devices: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Bug description: Binary package hint: udev Before I upgraded the udev version of jaunty from 141-1 to 141-1.1, top reported about 2% total cpu usage when idle. After the update, it rarely drops below 35%. Though top lists udevd among the more cpu hungry processes, it is only listed with about 3%, while system (in line 3) almost never drops below 20%. I am using the amd64 version of Xubuntu 9.04 on a Acer Extensa 5230 laptop with a 2 GHz Intel Celeron processor, and I have my root, home and swap partitions encrypted with luks. I did a fresh install and installed nothing but the software updates. The output of top looks like this: top - 18:47:33 up 15 min, 2 users, load average: 1.48, 1.99, 1.50 Tasks: 125 total, 3 running, 122 sleeping, 0 stopped, 0 zombie Cpu(s): 11.3%us, 23.9%sy, 0.0%ni, 60.1%id, 0.0%wa, 4.3%hi, 0.3%si, 0.0%st Mem:940212k total, 637176k used, 303036k free, 872k buffers Swap: 2103444k total,0k used, 2103444k free, 346116k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 939 root 16 -4 16792 600 296 S 3.0 0.1 0:17.03 udevd 15937 haldaemo 20 0 36304 4872 3756 S 1.7 0.5 0:04.29 hald 16403 root 20 0 451m 51m 17m R 1.7 5.6 0:25.92 Xorg 30 root 15 -5 000 S 0.7 0.0 0:05.52 scsi_eh_1 5480 andreas 20 0 19116 1328 988 R 0.3 0.1 0:00.89 top 22747 andreas 20 0 174m 17m 8960 R 0.3 1.9 0:01.14 xfce4-terminal 1 root 20 0 4104 924 632 S 0.0 0.1 0:00.87 init 2 root 15 -5 000 S 0.0 0.0 0:00.00 kthreadd 3 root RT -5 000 S 0.0 0.0 0:00.00 migration/0 4 root 15 -5 000 S 0.0 0.0 0:00.00 ksoftirqd/0 5 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/0 6 root 15 -5 000 S 0.0 0.0 0:00.65 events/0 7 root 15 -5 000 S 0.0 0.0 0:00.00 khelper 8 root RT -5 000 S 0.0 0.0 0:00.00 kstop/0 9 root 15 -5 000 S 0.0 0.0 0:00.00 kintegrityd/0 ... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/379780/+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 1353050] Re: External USB3 device does not work in USB3 port
apport information ** Tags added: apport-collected qiana ** Description changed: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 using xhci_hcd [ 2173.864136] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2173.864388] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2173.864612] usb 9-4: USB disconnect, device number 6 [ 2174.252856] usb 9-4: new SuperSpeed USB device number 7 using xhci_hcd [ 2174.268644] usb 9-4: Parent hub missing LPM exit latency info.
[Kernel-packages] [Bug 1353050] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1353050/+attachment/4170585/+files/WifiSyslog.txt ** 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/1353050 Title: External USB3 device does not work in USB3 port Status in “linux” package in Ubuntu: Confirmed Bug description: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 u
[Kernel-packages] [Bug 1353050] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1353050/+attachment/4170576/+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/1353050 Title: External USB3 device does not work in USB3 port Status in “linux” package in Ubuntu: Confirmed Bug description: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 using xhci_hcd [ 2173.864136] usb 9-4: Parent hub missing LPM exit latenc
[Kernel-packages] [Bug 1353050] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1353050/+attachment/4170579/+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/1353050 Title: External USB3 device does not work in USB3 port Status in “linux” package in Ubuntu: Confirmed Bug description: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 using xhci_hcd [ 2173.864136] usb 9-4: Parent hub missing LPM exit
[Kernel-packages] [Bug 1353050] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1353050/+attachment/4170582/+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/1353050 Title: External USB3 device does not work in USB3 port Status in “linux” package in Ubuntu: Confirmed Bug description: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 using xhci_hcd [ 2173.864136] usb 9-4: Parent hub missing LPM exit late
[Kernel-packages] [Bug 1353050] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1353050/+attachment/4170575/+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/1353050 Title: External USB3 device does not work in USB3 port Status in “linux” package in Ubuntu: Confirmed Bug description: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 using xhci_hcd [ 2173.864136] usb 9-4: Parent hub missing LPM exi
[Kernel-packages] [Bug 1353050] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1353050/+attachment/4170578/+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/1353050 Title: External USB3 device does not work in USB3 port Status in “linux” package in Ubuntu: Confirmed Bug description: External USB3 drive (Seagate GoFlex) connected to a USB3 port fails to mount on OS. Same unit works on USB2 ports (at USB2 speeds). I expect my external USB3 drive to be recognized by the OS and able to operate at USB3 speeds. Mint 17 64-bit Cinammon (Ubuntu 14.04). Necessary details below or attached. Ubuntu 3.13.0-24.46-generic 3.13.9 Description: Linux Mint 17 Qiana Release: 17 I have a Gigabyte GA-990FXA-UD3 motherboard. UEFI/BIOS set to enable legacy USB support and both XHCI and EHCI handoff to OS (disabling these has no effect). Same bug reported here: https://bugs.launchpad.net/linuxmint/+bug/1348669 $dmesg | grep "usb 9-4" [ 2133.637961] usb 9-4: new SuperSpeed USB device number 2 using xhci_hcd [ 2133.653736] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2133.654362] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2133.654370] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2133.654377] usb 9-4: Product: GoFlex Desk [ 2133.654383] usb 9-4: Manufacturer: Seagate [ 2133.654388] usb 9-4: SerialNumber: NA0LP2NG [ 2147.687559] usb 9-4: reset SuperSpeed USB device number 2 using xhci_hcd [ 2147.703314] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2147.703610] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2147.703784] usb 9-4: USB disconnect, device number 2 [ 2148.092071] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd [ 2148.107823] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2148.108449] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2148.108457] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2148.108464] usb 9-4: Product: GoFlex Desk [ 2148.108470] usb 9-4: Manufacturer: Seagate [ 2148.108475] usb 9-4: SerialNumber: NA0LP2NG [ 2154.227723] usb 9-4: reset SuperSpeed USB device number 3 using xhci_hcd [ 2154.243565] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.243813] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2154.244021] usb 9-4: USB disconnect, device number 3 [ 2154.632267] usb 9-4: new SuperSpeed USB device number 4 using xhci_hcd [ 2154.648038] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2154.648678] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2154.648687] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2154.648694] usb 9-4: Product: GoFlex Desk [ 2154.648700] usb 9-4: Manufacturer: Seagate [ 2154.648705] usb 9-4: SerialNumber: NA0LP2NG [ 2160.768006] usb 9-4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2160.783745] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2160.783997] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2160.784203] usb 9-4: USB disconnect, device number 4 [ 2161.172418] usb 9-4: new SuperSpeed USB device number 5 using xhci_hcd [ 2161.188263] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2161.17] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2161.188896] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2161.188903] usb 9-4: Product: GoFlex Desk [ 2161.188908] usb 9-4: Manufacturer: Seagate [ 2161.188913] usb 9-4: SerialNumber: NA0LP2NG [ 2167.308200] usb 9-4: reset SuperSpeed USB device number 5 using xhci_hcd [ 2167.323943] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.324190] usb 9-4: Busted HC? Not enough HCD resources for old configuration. [ 2167.324401] usb 9-4: USB disconnect, device number 5 [ 2167.712527] usb 9-4: new SuperSpeed USB device number 6 using xhci_hcd [ 2167.728431] usb 9-4: Parent hub missing LPM exit latency info. Power management will be impacted. [ 2167.729066] usb 9-4: New USB device found, idVendor=0bc2, idProduct=50a5 [ 2167.729074] usb 9-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2167.729081] usb 9-4: Product: GoFlex Desk [ 2167.729087] usb 9-4: Manufacturer: Seagate [ 2167.729092] usb 9-4: SerialNumber: NA0LP2NG [ 2173.848366] usb 9-4: reset SuperSpeed USB device number 6 using xhci_hcd [ 2173.864136] usb 9-4: Parent hub missing LPM exit latency info.