[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
That second paragraph should read: And that message was already in the first dmesg ... so the i8042 driver already KNEW something was fishy, and hinted what I should do ... ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Interesting ... triggered by "[ 0.278602] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp", I just tried i8042.nopnp as only option in GRUB, and that works too: keyboard works immediatly. And that message was already in the first dmesg ... so the i8042 driver already something was fishy, and hinted what I should do ... ? sander@zwart2204:~$ sudo dmesg | grep i8042 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1e423543-e174-4d68-9250-1707c248963c ro quiet splash i8042.nopnp vt.handoff=7 [0.024392] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1e423543-e174-4d68-9250-1707c248963c ro quiet splash i8042.nopnp vt.handoff=7 [0.278664] i8042: PNP detection disabled [0.297102] serio: i8042 KBD port at 0x60,0x64 irq 1 [0.297106] serio: i8042 AUX port at 0x60,0x64 irq 12 [2.199442] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8 [2.803523] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Only i8042.direct ... not good. Keyboard not working for x seconds Only i8042.dumbkbd ... yes, works! Keyboard working immediatly. So my /etc/default/grub now contains: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd" And stuff from dmesg: sander@zwart2204:~$ sudo dmesg | grep i8042 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1e423543-e174-4d68-9250-1707c248963c ro quiet splash i8042.dumbkbd vt.handoff=7 [0.024601] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1e423543-e174-4d68-9250-1707c248963c ro quiet splash i8042.dumbkbd vt.handoff=7 [0.278600] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 [0.278602] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp [0.284498] serio: i8042 KBD port at 0x60,0x64 irq 1 [0.284750] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Out of curiosity: The manual work (adding the line to GRUB): is that how it should be, or a bug (something Ubuntu should take care of)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Ah, SOLVED, like this: Triggered by your remarks, I found https://unix.stackexchange.com/a/656183, which says: RUB_CMDLINE_LINUX_DEFAULT="atkbd.reset i8042.reset i8042.nomux quiet splash". If this doesn't work, follow the same process but try GRUB_CMDLINE_LINUX_DEFAULT="i8042.direct i8042.dumbkbd" ... and that last line worked for me: keyboard works immediatly after boot and resume. So my grub line is now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.debug=1i8042.direct i8042.dumbkbd" I guess I can remove i8042.debug=1 Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
I tried "i8042.noaux=1", but no change: after boot and after resume: touchpad works immediatly, but keyboard takes 25-45 seconds. dmesg included ** Attachment added: "dmesg "i8042.noaux=1"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+attachment/5594428/+files/dmesg.i8042.noaux.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Thanks for replying. See included dmesg. I generated it with the following command ... hopefully OK sudo dmesg -T > dmesg_after_suspend_and_resume.txt Snippet from dmesg: [wo jun 1 11:38:40 2022] i8042: [28649] 65 -> i8042 (parameter) [wo jun 1 11:38:40 2022] i8042: [28649] ab <- i8042 (interrupt, 0, 0) [wo jun 1 11:38:40 2022] i8042: [28650] 83 <- i8042 (interrupt, 0, 1) [wo jun 1 11:38:40 2022] i8042: [28650] f2 -> i8042 (kbd-data) [wo jun 1 11:38:40 2022] i8042: [28652] fa <- i8042 (interrupt, 0, 1) [wo jun 1 11:38:40 2022] i8042: [28653] fa <- i8042 (interrupt, 0, 1) [wo jun 1 11:38:40 2022] i8042: [28653] 60 -> i8042 (command) [wo jun 1 11:38:40 2022] i8042: [28653] 64 -> i8042 (parameter) [wo jun 1 11:38:40 2022] i8042: [28653] 60 -> i8042 (command) ** Attachment added: "dmesg with "i8042.debug=1"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+attachment/5594274/+files/dmesg_after_suspend_and_resume.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960893] Re: i915 gives trace in dmesg
Still there in current Ubuntu 22.04 (fresh install, fully updated) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960893 Title: i915 gives trace in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Ah, it seems to happen after a fresh boot too: the login is there, mouse is working, but keyboard not. It takes 20 - 30 seconds before keyboard is working. Snippet from dmesg (leaving out wlo1 stuff): ... [di mei 31 20:09:47 2022] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 8 [di mei 31 20:09:47 2022] input: sof-hda-dsp Mic as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input16 [di mei 31 20:09:47 2022] input: sof-hda-dsp Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 [di mei 31 20:09:47 2022] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input18 [di mei 31 20:09:47 2022] input: sof-hda-dsp HDMI/DP,pcm=4 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input19 [di mei 31 20:09:47 2022] input: sof-hda-dsp HDMI/DP,pcm=5 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 [di mei 31 20:09:47 2022] Bluetooth: hci0: RTL: fw version 0x829a7644 [di mei 31 20:09:47 2022] NET: Registered PF_ALG protocol family [di mei 31 20:09:47 2022] rtw_8821ce :01:00.0: start vif 74:12:b3:9d:cf:47 on port 0 [di mei 31 20:09:48 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 20:09:48 2022] rfkill: input handler disabled [di mei 31 20:09:52 2022] rtw_8821ce :01:00.0: sta 34:e3:80:14:71:35 joined with macid 0 [di mei 31 20:09:53 2022] rtw_8821ce :01:00.0: failed to get tx report from firmware ... and then ... [di mei 31 20:10:04 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input59 [di mei 31 20:10:10 2022] kauditd_printk_skb: 36 callbacks suppressed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] [NEW] laptop keyboard not working for about 30 seconds after resume from suspend
Public bug reported: Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at all. Newish HP laptop (so recent hardware) Problem: After resuming from suspend, the laptop's keyboard is not working for about 30 seconds (the laptop's touchpad is working at once). Looking at dmesg, it looks the keyboard only starts working after: [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ... which happens about 35 seconds after the resume sequence completes. From dmesg: suspend: [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:51 2022] usb 1-1: USB disconnect, device number 2 [di mei 31 19:06:51 2022] PM: suspend entry (s2idle) [di mei 31 19:06:51 2022] Filesystems sync: 0.007 seconds [di mei 31 19:06:51 2022] Freezing user space processes ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] OOM killer disabled. [di mei 31 19:06:51 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] printk: Suspending console(s) (use no_console_suspend to debug) [di mei 31 19:06:52 2022] ACPI: EC: interrupt blocked After 3 minutes: open laptop lid, and it wakes up: [di mei 31 19:09:45 2022] ACPI: EC: interrupt unblocked [di mei 31 19:09:46 2022] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [di mei 31 19:09:46 2022] OOM killer enabled. [di mei 31 19:09:46 2022] Restarting tasks ... [di mei 31 19:09:46 2022] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: rom_version status=0 version=1 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990 [di mei 31 19:09:46 2022] done. [di mei 31 19:09:46 2022] PM: suspend exit [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: fw version 0x829a7644 ... and then after 35 seconds [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1329 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 19:24:02 2022 InstallationDate: Installed on 2022-05-31 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-dq2xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=6b217a97-66c0-4829-bbef-01ac3d8034c9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87FD dmi.board.vendor: HP dmi.board.version: 57.16 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.16 dmi.modalias:
[Bug 1960893] [NEW] i915 gives trace in dmesg
Public bug reported: [1.904158] kernel: [ cut here ] [1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x) [1.904176] kernel: WARNING: CPU: 3 PID: 328 at drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904264] kernel: Modules linked in: snd_hda_intel kvm_intel(+) snd_intel_dspcfg intel_rapl_msr(+) snd_intel_sdw_acpi kvm snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915(+) aesni_intel joydev crypto_simd cryptd rtw88_8821ce rtw88_8821c snd_seq rtw88_pci rtw88_core snd_seq_device intel_cstate nls_iso8859_1 snd_timer ttm mac80211 drm_kms_helper serio_raw cec hp_wmi rc_core processor_thermal_device_pci_legacy sparse_keymap processor_thermal_device i2c_algo_bit platform_profile wmi_bmof efi_pstore snd processor_thermal_rfim mei_me fb_sys_fops processor_thermal_mbox syscopyarea cfg80211 processor_thermal_rapl hid_multitouch mei ee1004 intel_rapl_common sysfillrect soundcore libarc4 sysimgblt intel_soc_dts_iosf mac_hid int3400_thermal wireless_hotkey dptf_pch_fivr acpi_pad acpi_thermal_rel int3403_thermal int340x_thermal_zone sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables [1.904304] kernel: x_tables autofs4 hid_generic nvme nvme_core i2c_i801 crc32_pclmul i2c_smbus intel_lpss_pci intel_lpss idma64 vmd xhci_pci xhci_pci_renesas wmi i2c_hid_acpi i2c_hid hid video pinctrl_tigerlake [1.904312] kernel: CPU: 3 PID: 328 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.904314] kernel: Hardware name: HP HP Laptop 14s-dq2xxx/87FD, BIOS F.09 02/19/2021 [1.904315] kernel: RIP: 0010:intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904369] kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 85 e8 35 e2 48 c7 c1 a0 ef bc c0 4c 89 ea 48 c7 c7 77 d8 be c0 48 89 c6 e8 1d ab 7c e2 <0f> 0b e9 55 ff ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 8b 17 80 [1.904370] kernel: RSP: 0018:a22780973808 EFLAGS: 00010286 [1.904372] kernel: RAX: RBX: 93cf4882e000 RCX: 0027 [1.904373] kernel: RDX: 93d0b7ba09c8 RSI: 0001 RDI: 93d0b7ba09c0 [1.904373] kernel: RBP: a22780973838 R08: 0003 R09: a4be0e12 [1.904374] kernel: R10: R11: 0001 R12: [1.904374] kernel: R13: 93cf41550720 R14: 93cf4882efa0 R15: [1.904375] kernel: FS: 7f63046e98c0() GS:93d0b7b8() knlGS: [1.904376] kernel: CS: 0010 DS: ES: CR0: 80050033 [1.904377] kernel: CR2: 7fc171f1aaa0 CR3: 00010715e006 CR4: 00770ee0 [1.904378] kernel: PKRU: 5554 [1.904378] kernel: Call Trace: [1.904379] kernel: [1.904381] kernel: intel_ddi_init+0x6a0/0xbd0 [i915] [1.904447] kernel: ? __cond_resched+0x1a/0x50 [1.904451] kernel: intel_setup_outputs+0x304/0xc70 [i915] [1.904514] kernel: intel_modeset_init_nogem+0x290/0x510 [i915] [1.904562] kernel: ? intel_irq_postinstall+0x38b/0x680 [i915] [1.904608] kernel: i915_driver_probe+0x1b7/0x470 [i915] [1.904648] kernel: ? mutex_lock+0x13/0x40 [1.904650] kernel: i915_pci_probe+0x58/0x140 [i915] [1.904689] kernel: local_pci_probe+0x48/0x90 [1.904692] kernel: pci_device_probe+0x115/0x1f0 [1.904693] kernel: really_probe+0x21b/0x420 [1.904696] kernel: __driver_probe_device+0x115/0x190 [1.904697] kernel: driver_probe_device+0x23/0xc0 [1.904699] kernel: __driver_attach+0xbd/0x1d0 [1.904700] kernel: ? __device_attach_driver+0x110/0x110 [1.904702] kernel: bus_for_each_dev+0x7c/0xc0 [1.904704] kernel: driver_attach+0x1e/0x20 [1.904705] kernel: bus_add_driver+0x135/0x200 [1.904707] kernel: driver_register+0x95/0xf0 [1.904708] kernel: __pci_register_driver+0x68/0x70 [1.904709] kernel: i915_register_pci_driver+0x23/0x30 [i915] [1.904746] kernel: i915_init+0x3b/0xfc [i915] [1.904793] kernel: ? 0xc0cad000 [1.904794] kernel: do_one_initcall+0x46/0x1d0 [1.904797] kernel: ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.904800] kernel: do_init_module+0x62/0x280 [1.904801] kernel: load_module+0xac9/0xbb0 [1.904803] kernel: __do_sys_finit_module+0xbf/0x120 [1.904804] kernel: __x64_sys_finit_module+0x18/0x20 [1.904805] kernel: do_syscall_64+0x59/0xc0 [1.904807] kernel: ? fput+0x13/0x20 [1.904809] kernel: ? ksys_mmap_pgoff+0x150/0x2b0 [1.904810] kernel: ? exit_to_user_mode_prepare+0x37/0xb0 [1.904812] kernel: ? syscall_exit_to_user_mode+0x27/0x50 [1.904814] kernel: ? __x64_sys_mmap+0x33/0x40 [1.904816] kernel: ? do_syscall_64+0x69/0xc0 [1.904817] kernel: ? do_syscall_64+0x69/0xc0 [1.904818] kernel: ? syscall_exit_to_user_mode+0x27/0x50 [1.904819] kernel: ?
[Bug 1960891] [NEW] rtw_8821ce 0000:01:00.0: failed to send h2c command
Public bug reported: Unstable Wifi Sometimes most Wifi AP's (including my own) or not seen dmesg filled with [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1239 F pulseaudio /dev/snd/pcmC0D0p: sander 1239 F...m pulseaudio /dev/snd/seq:sander 1237 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 06:40:43 2022 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus
[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn
I bumped into the same: disk full. After inspection: /var/log/syslog 20GB /var/log/syslog.1 60GB ... removing /var/log/syslog.1 same some disk space free, but /var/log/syslog keep on growing, so I'm going to reboot. Jan 16 08:57:24 brixit gnome-shell[1788]: The offending callback was SourceFunc(). Jan 16 08:57:24 brixit gnome-shell[1788]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850861] Re: execstack --set-execstack Aborted (core dump)
FWIW: On Ubuntu 18.04 no problem: sander@brixit:~$ execstack -s /tmp/ls sander@brixit:~$ sander@brixit:~$ execstack -q /tmp/ls X /tmp/ls So it seems Ubuntu 20.04 specific? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850861 Title: execstack --set-execstack Aborted (core dump) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prelink/+bug/1850861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850861] Re: execstack --set-execstack Aborted (core dump)
On Ubuntu 20.04, I have the same problem: $ execstack -s hello execstack: dso.c:877: reopen_dso: Assertion `dso->shdr[j].sh_size == 0' failed. Aborted (core dumped) sander@witte2004:~/hello-world$ gcc -o hello hello.c sander@witte2004:~/hello-world$ ./hello Hello, world! sander@witte2004:~/hello-world$ ldd hello linux-vdso.so.1 (0x7fffe01f4000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f66793b) /lib64/ld-linux-x86-64.so.2 (0x7f66795bf000) sander@witte2004:~/hello-world$ execstack -s hello execstack: dso.c:877: reopen_dso: Assertion `dso->shdr[j].sh_size == 0' failed. Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850861 Title: execstack --set-execstack Aborted (core dump) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prelink/+bug/1850861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850861] Re: execstack --set-execstack Aborted (core dump)
And same same with /usr/bin/ls : sander@witte2004:~/hello-world$ cp /usr/bin/ls /tmp/ sander@witte2004:~/hello-world$ ll /tmp/ls -rwxr-xr-x 1 sander sander 142144 jun 8 20:43 /tmp/ls* sander@witte2004:~/hello-world$ execstack -s /tmp/ls execstack: dso.c:877: reopen_dso: Assertion `dso->shdr[j].sh_size == 0' failed. Aborted (core dumped) sander@witte2004:~/hello-world$ execstack -q /tmp/ls - /tmp/ls -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850861 Title: execstack --set-execstack Aborted (core dump) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prelink/+bug/1850861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592380] Re: GUFW can't start /usr/bin/gufw-pkexec: line 15: 8787 Segmentation fault (core dumped) python ${LOCATIONS[${i}]} $1
*** This bug is a duplicate of bug 1713238 *** https://bugs.launchpad.net/bugs/1713238 @oliverubuntu: Thank you, that worked for me on Ubuntu 17.10! /usr/bin/gufw-pkexec: line 13: 15373 Segmentation fault (core dumped) python3 ${LOCATIONS[${i}]} $1 sander@sammie-1710:~$ echo $XDG_SESSION_TYPE wayland sander@sammie-1710:~$ xhost si:localuser:root localuser:root being added to access control list sander@sammie-1710:~$ gufw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592380 Title: GUFW can't start /usr/bin/gufw-pkexec: line 15: 8787 Segmentation fault (core dumped) python ${LOCATIONS[${i}]} $1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1592380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user
Yes, that solved it for me after activating "proposed" on artful, with xdg-utils (1.1.1-1ubuntu3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721948 Title: gvfs-open/xdg-open shows message about 'gio open' which confuses user To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1721948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647764] Re: golang in ubuntu-lxc / lxd-stable still on 1.6
** Changed in: golang-1.7 (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647764 Title: golang in ubuntu-lxc / lxd-stable still on 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.7/+bug/1647764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647764] Re: golang in ubuntu-lxc / lxd-stable still on 1.6
OK, that will work. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647764 Title: golang in ubuntu-lxc / lxd-stable still on 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.7/+bug/1647764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647764] [NEW] golang in ubuntu-lxc / lxd-stable still on 1.6
Public bug reported: Go (golang) in ubuntu-lxc / lxd-stable is still on version 1.6, whereas Go 1.7 was released on Aug 15, 2016. https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxd-stable/+packages says "ubuntu-lxc-bot 2016-03-22" ... so is that bot not updating golang anymore? ** Affects: golang-1.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647764 Title: golang in ubuntu-lxc / lxd-stable still on 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.7/+bug/1647764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
@Hansen ... I did that, did a reboot, did a suspend/resume (arrows appeared), and the logging is 1997 lines long. Can you advice what to do with that logging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
@Joakim: Ah, OK, I now understand. Thanks. However: I have the beam symbol, but it's now grey (like: no signal), and no Wifi networks visible. :-( After a "sudo systemctl restart network-manager.service" the beam signal shortly becomes an empty pizza slice, then the Up-Down-arrow, and greyed beam after a minute or so. Pity And I should have written: FWIW: I've NO Intel Wifi, but Realtek: 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter Sorry about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
FWIW2: I only have Wifi. No fixed ethernet. Maybe that is part of the problem? Maybe the indicator assumes the first ethernet is always fixed ethernet, and puts that symbol on it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
I have the same problem with a fresh install of Ubuntu 16.10 / yakkety on my HP Stream 13. The workaround "sudo systemctl restart network-manager.service" works for me: it removes the up-down-arrow, and gives back the beam symbol showing the available wifi networks. I have no file /etc/systemd/system/wifi-resume.service, so I can't use the workaround from http://askubuntu.com/questions/761180/wifi-doesnt- work-after-suspend-after-16-04-upgrade/761220#761220 FWIW: I've an Intel Wifi too: 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528939] [NEW] package miredo 1.2.6-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Installed miredo via Package Manager, and I got this report. Afterwards ifconfig does show a teredo interface (with 2001:0:... address), but it's not working: $ ping6 www.google.com connect: Network is unreachable Restarting the miredo service does not solve that. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: miredo 1.2.6-3 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptOrdering: libjudydebian1: Install miredo: Install libjudydebian1: Configure miredo: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Dec 23 20:33:24 2015 DuplicateSignature: package:miredo:1.2.6-3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-12-23 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: miredo Title: package miredo 1.2.6-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: miredo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528939 Title: package miredo 1.2.6-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1528939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318262] Re: ui freezes after a short perioud when browsing upnp media
This happens on my Ubuntu 15.04 with VLC 2.2.0. AFAIK Patch provided here: http://sourceforge.net/p/pupnp/bugs/108/#624e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318262 Title: ui freezes after a short perioud when browsing upnp media To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1318262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
dmesg with drm-debu and flip switch problem ** Attachment added: dmesg with drm-debu and flip switch problem https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+attachment/4396622/+files/dmesg.with-flip-problem-and-drm-debug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
The attachment contains the complete dmesg with drm turned on. Snippet from around the flip message: [ 7538.988560] [drm:valleyview_update_wm] Setting FIFO watermarks - A: plane=111, cursor=2, B: plane=2, cursor=2, SR: plane=60, cursor=2 [ 7538.988565] [drm:intel_set_memory_cxsr] memory self-refresh is enabled [ 7538.994556] [drm:g4x_check_srwm] SR watermark: display plane 60, cursor 6 [ 7538.994563] [drm:g4x_check_srwm] SR watermark: display plane 117, cursor 10 [ 7538.994568] [drm:valleyview_update_wm] Setting FIFO watermarks - A: plane=111, cursor=6, B: plane=2, cursor=2, SR: plane=60, cursor=10 [ 7538.994572] [drm:intel_set_memory_cxsr] memory self-refresh is enabled [ 7540.057903] [drm:i915_gem_context_destroy_ioctl] HW context 25 destroyed [ 7543.835009] wlan0: deauthenticating from c0:4a:00:2c:dc:bd by local choice (Reason: 3=DEAUTH_LEAVING) [ 7543.848742] cfg80211: Calling CRDA to update world regulatory domain [ 7543.932927] cfg80211: World regulatory domain updated: [ 7543.932935] cfg80211: DFS Master region: unset [ 7543.932937] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 7543.932943] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [ 7543.932947] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [ 7543.932950] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm), (N/A) [ 7543.932953] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [ 7543.932957] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [ 7545.299524] wlan0: authenticate with 00:14:7f:b2:ad:fd [ 7545.311204] wlan0: send auth to 00:14:7f:b2:ad:fd (try 1/3) [ 7545.313850] wlan0: authenticated [ 7545.329704] wlan0: associate with 00:14:7f:b2:ad:fd (try 1/3) [ 7545.11] wlan0: RX AssocResp from 00:14:7f:b2:ad:fd (capab=0x411 status=0 aid=5) [ 7545.334296] wlan0: associated [ 7591.802174] [ cut here ] [ 7591.802224] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xda/0xf0 [i915]() [ 7591.802227] Kicking stuck page flip: queued at 453978, now 453983 [ 7591.802229] Modules linked in: ctr ccm rfcomm bnep nls_iso8859_1 hid_generic hp_wmi sparse_keymap btusb bluetooth usbhid joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_soc_dts_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd arc4 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core rtl8723be v4l2_common btcoexist videodev rtl8723_common rtl_pci media rtlwifi mac80211 snd_hda_intel serio_raw snd_hda_controller cfg80211 snd_intel_sst_acpi snd_intel_sst_core snd_soc_rt5640 snd_soc_sst_mfld_platform mei_txe i915 snd_hda_codec snd_soc_rl6231 rtsx_pci_ms lpc_ich memstick snd_soc_core shpchp snd_compress snd_pcm_dmaengine snd_hwdep mei snd_pcm drm_kms_helper drm snd_seq_midi snd_seq_midi_event iosf_mbi [ 7591.802283] i2c_algo_bit wmi snd_rawmidi snd_seq snd_seq_device video hp_wireless dw_dmac dw_dmac_core snd_timer processor_thermal_device int3403_thermal int3400_thermal acpi_thermal_rel intel_smartconnect snd i2c_hid hid soundcore rfkill_gpio i2c_designware_platform i2c_designware_core snd_soc_sst_acpi 8250_dw spi_pxa2xx_platform pwm_lpss_platform mac_hid pwm_lpss parport_pc ppdev lp parport autofs4 mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 7591.802322] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 3.19.0-16-generic #16-Ubuntu [ 7591.802324] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.06 01/06/2015 [ 7591.802327] c0559e10 880076c03d18 817c2235 0007 [ 7591.802332] 880076c03d68 880076c03d58 8107595a 880076c03d78 [ 7591.802336] 880071d65000 88003671b000 88003671b1a8 [ 7591.802341] Call Trace: [ 7591.802344] IRQ [817c2235] dump_stack+0x45/0x57 [ 7591.802358] [8107595a] warn_slowpath_common+0x8a/0xc0 [ 7591.802363] [810759d6] warn_slowpath_fmt+0x46/0x50 [ 7591.802390] [c0505a3a] intel_check_page_flip+0xda/0xf0 [i915] [ 7591.802413] [c04ce549] valleyview_pipestat_irq_handler+0x159/0x230 [i915] [ 7591.802437] [c04d3fa1] valleyview_irq_handler+0xc1/0x170 [i915] [ 7591.802443] [810cd5f7] handle_irq_event_percpu+0x77/0x1a0 [ 7591.802447] [810cd761] handle_irq_event+0x41/0x70 [ 7591.802452] [810d07ce] handle_edge_irq+0x6e/0x120 [ 7591.802457] [81017772] handle_irq+0x22/0x40 [ 7591.802462] [817cc27f] do_IRQ+0x4f/0xf0 [ 7591.802467] [817ca0ed] common_interrupt+0x6d/0x6d [ 7591.802469] EOI [81664405] ? cpuidle_enter_state+0x65/0x160 [ 7591.802478] [816643f1] ? cpuidle_enter_state+0x51/0x160 [ 7591.802482] [816645e7]
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
drm.debug=0xe added kernel command line: $ dmesg | head [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.19.0-16-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015 (Ubuntu 3.19.0-16.16-generic 3.19.3) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=07d60846-8d52-4911-b233-7e5b8611e217 ro quiet splash drm.debug=0xe vt.handoff=7 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] e820: BIOS-provided physical RAM map: dmesg is now showing a lot of [drm:... lines: [9.002449] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 r(1) [9.002453] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb [9.002456] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:30:HDMI-A-1] disconnected [9.002459] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:35:DP-1] I'll report as soon as the flip error occurs again (I hope this post will also appear on bugs.freedesktop.org) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311253] Re: btscanner crashes on try using brute force scan
FWIW: The latest change to btscanner 2.1 was made in 2005. The maintainer seems to be gone. So maybe better to remove btscanner from the Ubuntu repositories? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/311253 Title: btscanner crashes on try using brute force scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btscanner/+bug/311253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311253] Re: btscanner crashes on try using brute force scan
Still happens on Ubuntu 15.04 with btscanner 2.0 after pressing b $ btscanner *** buffer overflow detected ***: btscanner terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x78c4e)[0x7fa095fc8c4e] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7fa096068e8c] /lib/x86_64-linux-gnu/libc.so.6(+0x116e80)[0x7fa096066e80] btscanner[0x4075bc] btscanner[0x407db5] btscanner[0x403c49] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fa095f70a40] btscanner[0x403c9d] === Memory map: 0040-0040f000 r-xp b3:05 145449 /usr/bin/btscanner 0060e000-0060f000 r--p e000 b3:05 145449 /usr/bin/btscanner 0060f000-0061 rw-p f000 b3:05 145449 /usr/bin/btscanner 0061-00611000 rw-p 00:00 0 02064000-02105000 rw-p 00:00 0 [heap] 7fa093719000-7fa09372f000 r-xp b3:05 284748 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fa09372f000-7fa09392e000 ---p 00016000 b3:05 284748 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fa09392e000-7fa09392f000 rw-p 00015000 b3:05 284748 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fa09392f000-7fa093a1f000 r-xp b3:05 134877 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20 7fa093a1f000-7fa093c1f000 ---p 000f b3:05 134877 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20 7fa093c1f000-7fa093c27000 r--p 000f b3:05 134877 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20 7fa093c27000-7fa093c29000 rw-p 000f8000 b3:05 134877 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20 7fa093c29000-7fa093c3e000 rw-p 00:00 0 7fa093c3e000-7fa0952aa000 r-xp b3:05 136593 /usr/lib/x86_64-linux-gnu/libicudata.so.52.1 7fa0952aa000-7fa0954a9000 ---p 0166c000 b3:05 136593 /usr/lib/x86_64-linux-gnu/libicudata.so.52.1 7fa0954a9000-7fa0954aa000 r--p 0166b000 b3:05 136593 /usr/lib/x86_64-linux-gnu/libicudata.so.52.1 7fa0954aa000-7fa0954ab000 rw-p 0166c000 b3:05 136593 /usr/lib/x86_64-linux-gnu/libicudata.so.52.1 7fa0954ab000-7fa0955b2000 r-xp b3:05 274001 /lib/x86_64-linux-gnu/libm-2.21.so 7fa0955b2000-7fa0957b1000 ---p 00107000 b3:05 274001 /lib/x86_64-linux-gnu/libm-2.21.so 7fa0957b1000-7fa0957b2000 r--p 00106000 b3:05 274001 /lib/x86_64-linux-gnu/libm-2.21.so 7fa0957b2000-7fa0957b3000 rw-p 00107000 b3:05 274001 /lib/x86_64-linux-gnu/libm-2.21.so 7fa0957b3000-7fa0957cc000 r-xp b3:05 266645 /lib/x86_64-linux-gnu/libz.so.1.2.8 7fa0957cc000-7fa0959cc000 ---p 00019000 b3:05 266645 /lib/x86_64-linux-gnu/libz.so.1.2.8 7fa0959cc000-7fa0959cd000 r--p 00019000 b3:05 266645 /lib/x86_64-linux-gnu/libz.so.1.2.8 7fa0959cd000-7fa0959ce000 rw-p 0001a000 b3:05 266645 /lib/x86_64-linux-gnu/libz.so.1.2.8 7fa0959ce000-7fa095b36000 r-xp b3:05 137433 /usr/lib/x86_64-linux-gnu/libicuuc.so.52.1 7fa095b36000-7fa095d35000 ---p 00168000 b3:05 137433 /usr/lib/x86_64-linux-gnu/libicuuc.so.52.1 7fa095d35000-7fa095d47000 r--p 00167000 b3:05 137433 /usr/lib/x86_64-linux-gnu/libicuuc.so.52.1 7fa095d47000-7fa095d48000 rw-p 00179000 b3:05 137433 /usr/lib/x86_64-linux-gnu/libicuuc.so.52.1 7fa095d48000-7fa095d4c000 rw-p 00:00 0 7fa095d4c000-7fa095d4f000 r-xp b3:05 265300 /lib/x86_64-linux-gnu/libdl-2.21.so 7fa095d4f000-7fa095f4e000 ---p 3000 b3:05 265300 /lib/x86_64-linux-gnu/libdl-2.21.so 7fa095f4e000-7fa095f4f000 r--p 2000 b3:05 265300 /lib/x86_64-linux-gnu/libdl-2.21.so 7fa095f4f000-7fa095f5 rw-p 3000 b3:05 265300 /lib/x86_64-linux-gnu/libdl-2.21.so 7fa095f5-7fa09611 r-xp b3:05 289060 /lib/x86_64-linux-gnu/libc-2.21.so 7fa09611-7fa09631 ---p 001c b3:05 289060 /lib/x86_64-linux-gnu/libc-2.21.so 7fa09631-7fa096314000 r--p 001c b3:05 289060 /lib/x86_64-linux-gnu/libc-2.21.so 7fa096314000-7fa096316000 rw-p 001c4000 b3:05 289060 /lib/x86_64-linux-gnu/libc-2.21.so 7fa096316000-7fa09631a000 rw-p 00:00 0 7fa09631a000-7fa09633f000 r-xp b3:05 300774 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7fa09633f000-7fa09653e000 ---p 00025000 b3:05 300774 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7fa09653e000-7fa096542000 r--p 00024000 b3:05 300774 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7fa096542000-7fa096543000 rw-p 00028000 b3:05 300774
[Bug 1440516] [NEW] sdhci.c:1013 sdhci_send_command+0x5d1/0xda0 [sdhci]()
Public bug reported: Just a warning, but maybe to useful to report what dmesg is telling me: [ 4653.114802] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 4653.116957] [ cut here ] [ 4653.116995] WARNING: CPU: 0 PID: 2196 at /build/buildd/linux-3.19.0/drivers/mmc/host/sdhci.c:1013 sdhci_send_command+0x5d1/0xda0 [sdhci]() [ 4653.116998] Modules linked in: rfcomm bnep nls_iso8859_1 hid_generic btusb bluetooth hp_wmi sparse_keymap joydev intel_rapl intel_soc_dts_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd serio_raw uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev usbhid media arc4 snd_hda_codec_hdmi rtl8723be btcoexist rtl8723_common rtl_pci rtlwifi snd_hda_codec_realtek mac80211 snd_hda_codec_generic rtsx_pci_ms snd_intel_sst_acpi i915 snd_intel_sst_core memstick cfg80211 snd_soc_sst_mfld_platform drm_kms_helper drm snd_hda_intel snd_seq_midi snd_hda_controller snd_seq_midi_event snd_hda_codec lpc_ich snd_hwdep shpchp i2c_algo_bit mei_txe mei snd_soc_rt5640 snd_soc_rl6231 iosf_mbi snd_soc_core wmi snd_compress snd_rawmidi snd_pcm_dmaengine [ 4653.117048] snd_pcm hp_wireless video dw_dmac snd_seq dw_dmac_core snd_seq_device int3400_thermal int3403_thermal acpi_thermal_rel processor_thermal_device snd_timer intel_smartconnect i2c_hid snd hid i2c_designware_platform i2c_designware_core rfkill_gpio soundcore snd_soc_sst_acpi pwm_lpss_platform pwm_lpss spi_pxa2xx_platform 8250_dw mac_hid parport_pc ppdev lp parport autofs4 mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 4653.117080] CPU: 0 PID: 2196 Comm: Chrome_ChildIOT Not tainted 3.19.0-12-generic #12-Ubuntu [ 4653.117083] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 4653.117086] c0184460 880076c03ca8 817c2175 0007 [ 4653.117091] 880076c03ce8 8107595a 880043e1 [ 4653.117095] 0001 0002 88007005da80 880071b34500 [ 4653.117100] Call Trace: [ 4653.117103] IRQ [817c2175] dump_stack+0x45/0x57 [ 4653.117119] [8107595a] warn_slowpath_common+0x8a/0xc0 [ 4653.117123] [81075a4a] warn_slowpath_null+0x1a/0x20 [ 4653.117133] [c01818c1] sdhci_send_command+0x5d1/0xda0 [sdhci] [ 4653.117140] [813c1cdb] ? delay_tsc+0x3b/0x80 [ 4653.117144] [813c1c1b] ? __const_udelay+0x2b/0x30 [ 4653.117154] [c017ee10] ? sdhci_reset+0x60/0xd0 [sdhci] [ 4653.117163] [c01828f5] sdhci_finish_data+0x115/0x3c0 [sdhci] [ 4653.117170] [81663851] ? intel_pstate_timer_func+0x321/0x3c0 [ 4653.117180] [c01831eb] sdhci_irq+0x42b/0x929 [sdhci] [ 4653.117185] [81663530] ? show_no_turbo+0x90/0x90 [ 4653.117190] [810cd577] handle_irq_event_percpu+0x77/0x1a0 [ 4653.117195] [810cd6e1] handle_irq_event+0x41/0x70 [ 4653.117200] [810d03d6] handle_fasteoi_irq+0x86/0x140 [ 4653.117205] [81017772] handle_irq+0x22/0x40 [ 4653.117210] [817cc1bf] do_IRQ+0x4f/0xf0 [ 4653.117215] [817ca02d] common_interrupt+0x6d/0x6d [ 4653.117217] EOI [817c928d] ? system_call_fastpath+0x16/0x1b [ 4653.117225] ---[ end trace 25ab47a2ddd6fced ]--- [ 4653.117247] mmc0: Got data interrupt 0x0002 even though no data operation was in progress. [ 4653.119317] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x400900 [ 4653.119322] mmcblk0: error -84 transferring data, sector 39229736, nr 8, cmd response 0x0, card status 0x0 [ 4653.119327] mmcblk0: retrying using single block read ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-12-generic 3.19.0-12.12 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1576 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 5 14:13:35 2015 HibernationDevice: RESUME=UUID=1cce7297-b185-4592-a4a0-dfdc069ad5a1 InstallationDate: Installed on 2015-02-03 (60 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150203) MachineType: Hewlett-Packard HP Stream Notebook PC 13 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=07d60846-8d52-4911-b233-7e5b8611e217 ro quiet splash memory_corruption_check=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-12-generic N/A linux-backports-modules-3.19.0-12-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag
[Bug 1440419] Re: Memory corruption detected in low memory
Thanks. Full computer name: HP Stream 13, HP 13-c000nd-N2840 aka HP 13-c000nd. There is no sticker on the computer, but an imprint saying Model 13-c000nd. Is that enough information? There is no Memtest86+ in the Grub boot menu and I can't add it, so I ran Memtst86+ (V6.0.0 Free) from a USB stick. It has been running now for 32 minutes, and it's at Pass: 2 / 4 without errors. I guess the rest of the test will take one or two hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440419 Title: Memory corruption detected in low memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440419] Re: Memory corruption detected in low memory
Ouch. I had looked for a BIOS upgrade, but I had not been able to find it. Thank you for your work. I just upgraded to F.06 (now: DMI: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.06 01/06/2015), and I'll monitor the effect. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440419 Title: Memory corruption detected in low memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
Still (again?) happening with 3.19.0-12-generic [ 5578.584172] [ cut here ] [ 5578.584230] WARNING: CPU: 0 PID: 15321 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xda/0xf0 [i915]() [ 5578.584233] Kicking stuck page flip: queued at 243167, now 243173 [ 5578.584236] Modules linked in: nls_utf8 btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c rfcomm bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb hid_generic bluetooth intel_rapl intel_soc_dts_thermal hp_wmi sparse_keymap intel_powerclamp coretemp joydev kvm_intel kvm crct10dif_pclmul snd_intel_sst_acpi crc32_pclmul snd_intel_sst_core ghash_clmulni_intel snd_soc_rt5640 snd_soc_sst_mfld_platform snd_soc_rl6231 cryptd snd_soc_core serio_raw snd_compress snd_pcm_dmaengine arc4 snd_seq_midi snd_seq_midi_event rtl8723be btcoexist snd_rawmidi snd_hda_intel rtl8723_common snd_hda_controller rtl_pci uvcvideo rtlwifi videobuf2_vmalloc snd_hda_codec videobuf2_memops videobuf2_core mac80211 i915 snd_hwdep v4l2_common usbhid videodev media snd_seq [ 5578.584289] rtsx_pci_ms cfg80211 drm_kms_helper memstick lpc_ich snd_pcm snd_seq_device drm mei_txe snd_timer mei shpchp i2c_algo_bit iosf_mbi wmi video hp_wireless snd dw_dmac dw_dmac_core int3400_thermal int3403_thermal acpi_thermal_rel processor_thermal_device intel_smartconnect mac_hid rfkill_gpio i2c_hid hid soundcore i2c_designware_platform i2c_designware_core snd_soc_sst_acpi 8250_dw spi_pxa2xx_platform pwm_lpss_platform pwm_lpss parport_pc ppdev lp parport autofs4 mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 5578.584336] CPU: 0 PID: 15321 Comm: kworker/u8:9 Tainted: GW 3.19.0-12-generic #12-Ubuntu [ 5578.584339] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 5578.584351] Workqueue: rtsx_pci_sdmmc_workq sd_request [rtsx_pci_sdmmc] [ 5578.584354] c055de10 880076c02f30 817c2175 0007 [ 5578.584358] 880076c02f80 880076c02f70 8107595a 880076c02f90 [ 5578.584363] 8800728ad000 880079ba2800 880079ba29a8 [ 5578.584367] Call Trace: [ 5578.584371] IRQ [817c2175] dump_stack+0x45/0x57 [ 5578.584386] [8107595a] warn_slowpath_common+0x8a/0xc0 [ 5578.584391] [810759d6] warn_slowpath_fmt+0x46/0x50 [ 5578.584422] [c0509a3a] intel_check_page_flip+0xda/0xf0 [i915] [ 5578.584445] [c04d2549] valleyview_pipestat_irq_handler+0x159/0x230 [i915] [ 5578.584470] [c04d7fa1] valleyview_irq_handler+0xc1/0x170 [i915] [ 5578.584476] [810cd577] handle_irq_event_percpu+0x77/0x1a0 [ 5578.584481] [810cd6e1] handle_irq_event+0x41/0x70 [ 5578.584486] [810d074e] handle_edge_irq+0x6e/0x120 [ 5578.584490] [81017772] handle_irq+0x22/0x40 [ 5578.584496] [817cc1bf] do_IRQ+0x4f/0xf0 [ 5578.584500] [817ca02d] common_interrupt+0x6d/0x6d [ 5578.584506] [8101d974] ? nommu_map_page+0x44/0x80 [ 5578.584515] [c072] ? rtl8723be_phy_bb_config+0x282/0x640 [rtl8723be] [ 5578.584522] [c0445030] ? pci_read16_sync+0x10/0x20 [rtl_pci] [ 5578.584529] [c07050d3] rtl8723be_tx_polling+0x53/0x60 [rtl8723be] [ 5578.584536] [c0445d6b] rtl_pci_tx+0x1eb/0x3f0 [rtl_pci] [ 5578.584545] [c048813c] ? rtl_is_special_data+0x2c/0x180 [rtlwifi] [ 5578.584554] [c048bfcd] rtl_op_tx+0x9d/0xa0 [rtlwifi] [ 5578.584581] [c05f3250] __ieee80211_tx+0x290/0x390 [mac80211] [ 5578.584602] [c05f69ef] ieee80211_tx+0xbf/0x110 [mac80211] [ 5578.584623] [c05f6c34] ieee80211_xmit+0x94/0x100 [mac80211] [ 5578.584644] [c05f6fac] __ieee80211_subif_start_xmit+0x8c/0xb0 [mac80211] [ 5578.584665] [c05f6fe0] ieee80211_subif_start_xmit+0x10/0x20 [mac80211] [ 5578.584671] [816c01c9] dev_hard_start_xmit+0x169/0x3a0 [ 5578.584676] [816bff4d] ? validate_xmit_skb.isra.92.part.93+0x20d/0x320 [ 5578.584682] [816e1c9f] sch_direct_xmit+0xdf/0x220 [ 5578.584686] [816c0642] __dev_queue_xmit+0x242/0x580 [ 5578.584691] [810d0418] ? handle_fasteoi_irq+0xc8/0x140 [ 5578.584696] [816c0990] dev_queue_xmit+0x10/0x20 [ 5578.584700] [81764d0b] ip6_finish_output2+0x2ab/0x470 [ 5578.584705] [81767fd2] ip6_finish_output+0x92/0xd0 [ 5578.584708] [8176804c] ip6_output+0x3c/0xc0 [ 5578.584714] [81773b87] ? ip6_dst_check+0x27/0x50 [ 5578.584718] [817650f5] ip6_xmit+0x225/0x480 [ 5578.584722] [81791d80] ? pingv6_exit+0x70/0x70 [ 5578.584727] [81796a00] inet6_csk_xmit+0x70/0xc0 [ 5578.584732] [817169a2] tcp_transmit_skb+0x4d2/0x990 [ 5578.584737] [8101e74a] ? native_sched_clock+0x2a/0x90 [ 5578.584742] [817187b6] tcp_send_ack+0x116/0x170 [ 5578.584747] [8170bdee]
[Bug 1440419] [NEW] Memory corruption detected in low memory
Public bug reported: The below logging is shown in dmesg. I'm not sure if it's a kernel/software or a hardware problem. [za apr 4 13:07:54 2015] ACPI Error: [PMIN] Namespace lookup failure, AE_NOT_FOUND (20141107/psargs-359) [za apr 4 13:07:54 2015] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_._Q33] (Node 8800768a8988), AE_NOT_FOUND (20141107/psparse-536) [za apr 4 13:08:46 2015] Corrupted low memory at 880013d0 (13d0 phys) = d07 [za apr 4 13:08:46 2015] Corrupted low memory at 880013d8 (13d8 phys) = 3406 [za apr 4 13:08:46 2015] [ cut here ] [za apr 4 13:08:46 2015] WARNING: CPU: 0 PID: 8656 at /build/buildd/linux-3.19.0/arch/x86/kernel/check.c:140 check_for_bios_corruption+0xcb/0x120() [za apr 4 13:08:46 2015] Memory corruption detected in low memory [za apr 4 13:08:46 2015] Modules linked in: nls_utf8 btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c rfcomm bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb hid_generic bluetooth intel_rapl intel_soc_dts_thermal hp_wmi sparse_keymap intel_powerclamp coretemp joydev kvm_intel kvm crct10dif_pclmul snd_intel_sst_acpi crc32_pclmul snd_intel_sst_core ghash_clmulni_intel snd_soc_rt5640 snd_soc_sst_mfld_platform snd_soc_rl6231 cryptd snd_soc_core serio_raw snd_compress snd_pcm_dmaengine arc4 snd_seq_midi snd_seq_midi_event rtl8723be btcoexist snd_rawmidi snd_hda_intel rtl8723_common snd_hda_controller rtl_pci uvcvideo rtlwifi videobuf2_vmalloc snd_hda_codec videobuf2_memops videobuf2_core mac80211 i915 snd_hwdep v4l2_common usbhid videodev media snd_seq [za apr 4 13:08:46 2015] rtsx_pci_ms cfg80211 drm_kms_helper memstick lpc_ich snd_pcm snd_seq_device drm mei_txe snd_timer mei shpchp i2c_algo_bit iosf_mbi wmi video hp_wireless snd dw_dmac dw_dmac_core int3400_thermal int3403_thermal acpi_thermal_rel processor_thermal_device intel_smartconnect mac_hid rfkill_gpio i2c_hid hid soundcore i2c_designware_platform i2c_designware_core snd_soc_sst_acpi 8250_dw spi_pxa2xx_platform pwm_lpss_platform pwm_lpss parport_pc ppdev lp parport autofs4 mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [za apr 4 13:08:46 2015] CPU: 0 PID: 8656 Comm: kworker/0:0 Not tainted 3.19.0-12-generic #12-Ubuntu [za apr 4 13:08:46 2015] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [za apr 4 13:08:46 2015] Workqueue: events check_corruption [za apr 4 13:08:46 2015] 81a91c30 8800725b7cf8 817c2175 0007 [za apr 4 13:08:46 2015] 8800725b7d48 8800725b7d38 8107595a 880013d8 [za apr 4 13:08:46 2015] 8801 81ede350 0001 [za apr 4 13:08:46 2015] Call Trace: [za apr 4 13:08:46 2015] [817c2175] dump_stack+0x45/0x57 [za apr 4 13:08:46 2015] [8107595a] warn_slowpath_common+0x8a/0xc0 [za apr 4 13:08:46 2015] [810759d6] warn_slowpath_fmt+0x46/0x50 [za apr 4 13:08:46 2015] [810135e0] ? __switch_to+0x150/0x5e0 [za apr 4 13:08:46 2015] [8105c84b] check_for_bios_corruption+0xcb/0x120 [za apr 4 13:08:46 2015] [8105c8ae] check_corruption+0xe/0x40 [za apr 4 13:08:46 2015] [8108eb78] process_one_work+0x158/0x430 [za apr 4 13:08:46 2015] [8108f6bb] worker_thread+0x5b/0x530 [za apr 4 13:08:46 2015] [8108f660] ? rescuer_thread+0x3a0/0x3a0 [za apr 4 13:08:46 2015] [81094759] kthread+0xc9/0xe0 [za apr 4 13:08:46 2015] [81094690] ? kthread_create_on_node+0x1c0/0x1c0 [za apr 4 13:08:46 2015] [817c91d8] ret_from_fork+0x58/0x90 [za apr 4 13:08:46 2015] [81094690] ? kthread_create_on_node+0x1c0/0x1c0 [za apr 4 13:08:46 2015] ---[ end trace 70c303625ab83eae ]--- ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-12-generic 3.19.0-12.12 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1612 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 4 23:39:09 2015 HibernationDevice: RESUME=UUID=1cce7297-b185-4592-a4a0-dfdc069ad5a1 InstallationDate: Installed on 2015-02-03 (59 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150203) MachineType: Hewlett-Packard HP Stream Notebook PC 13 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=07d60846-8d52-4911-b233-7e5b8611e217 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-12-generic N/A linux-backports-modules-3.19.0-12-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Insyde
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
The error occured twice in the last 24 hours: $ cat /var/log/kern.log | grep -i flip Mar 2 23:13:04 superstreamer kernel: [ 3283.556389] WARNING: CPU: 0 PID: 0 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698 intel_check_page_flip+0xe6/0xf0 [i915]() Mar 2 23:13:04 superstreamer kernel: [ 3283.556395] Kicking stuck page flip: queued at 165209, now 165214 Mar 2 23:13:04 superstreamer kernel: [ 3283.556712] [c0483086] intel_check_page_flip+0xe6/0xf0 [i915] Mar 3 07:09:54 superstreamer kernel: [ 563.598385] WARNING: CPU: 0 PID: 0 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698 intel_check_page_flip+0xe6/0xf0 [i915]() Mar 3 07:09:54 superstreamer kernel: [ 563.598389] Kicking stuck page flip: queued at 33178, now 33183 Mar 3 07:09:54 superstreamer kernel: [ 563.598593] [c05f0086] intel_check_page_flip+0xe6/0xf0 [i915] I checked if there is correlation with logging about Lid: $ dmesg -T | grep -i Lid [di mrt 3 07:00:31 2015] Ignoring BGRT: invalid status 0 (expected 1) [di mrt 3 07:00:37 2015] \_SB_.PCI0:_OSC invalid UUID [di mrt 3 07:00:37 2015] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 [di mrt 3 07:00:37 2015] ACPI: Lid Switch [LID0] [di mrt 3 07:00:44 2015] systemd-logind[1250]: Watching system buttons on /dev/input/event0 (Lid Switch) [di mrt 3 07:33:11 2015] systemd-logind[1250]: Lid closed. [di mrt 3 07:33:18 2015] systemd-logind[1250]: Lid opened. [di mrt 3 07:43:43 2015] wlan0: deauthenticating from 00:14:7f:b2:ad:fd by local choice (Reason: 2=PREV_AUTH_NOT_VALID) [di mrt 3 07:45:25 2015] systemd-logind[1250]: Lid closed. [di mrt 3 07:45:32 2015] systemd-logind[1250]: Lid opened. I see no correlation, but I do some strange things: Lid closed. and Lid opened. in that order immediately after each other (within 0.1 second). That looks untrue as I don't do that. I really opened the Lid this morning around 07:00, but it is not in dmesg. Weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
I never close the lid immediately after booting, so in my case that cannot have been the cause. So far I have not found a correlation between the intel drm flip error and things I did. Sometimes the error occurs after an hour, sometimes not for two days. Now it is even 5 days ago: $ cat /var/log/kern.log* | grep -i drm/i915 Feb 24 07:47:22 superstreamer kernel: [ 58.932087] WARNING: CPU: 0 PID: 671 at drivers/gpu/drm/i915/intel_display.c:9711 intel_check_page_flip+0xda/0xf0 [i915]() Feb 24 08:12:34 superstreamer kernel: [ 129.144839] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/i915/intel_display.c:9711 intel_check_page_flip+0xda/0xf0 [i915]() Feb 25 00:49:03 superstreamer kernel: [ 9297.320009] WARNING: CPU: 0 PID: 1171 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698 intel_check_page_flip+0xe6/0xf0 [i915]() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
FWIW: I searched for [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=76355 end=76356) and found this source code on http://lists.freedesktop.org/archives/intel- gfx/2014-February/040161.html doing the Atomic update failure on pipe: 115 static void intel_pipe_update_end(struct intel_crtc *crtc, u32 start_vbl_count) 116 { 117 struct drm_device *dev = crtc-base.dev; 118 enum pipe pipe = crtc-pipe; 119 u32 end_vbl_count = dev-driver-get_vblank_counter(dev, pipe); 120 121 trace_i915_pipe_update_end(crtc, end_vbl_count); 122 123 local_irq_enable(); 124 125 if (start_vbl_count != end_vbl_count) 126 DRM_ERROR(Atomic update failure on pipe %c (start=%u end=%u)\n, 127 pipe_name(pipe), start_vbl_count, end_vbl_count); 128 } So because start_vbl_count != end_vbl_count I get that message in dmesg. NB: I'm not sure the message [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=76355 end=76356) has to do with the error message 12 seconds later WARNING: CPU: 0 PID: 0 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698 intel_check_page_flip+0xe6/0xf0 [i915]() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
FWIW: 12 seconds before the described problem, there is this line in dmesg: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=76355 end=76356) which I can't find on Google. More from dmesg: $ dmesg | grep Linux version [0.00] Linux version 3.19.0-994-generic (kernel@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201502112105 SMP Thu Feb 12 02:06:42 UTC 2015 $ dmesg --level=err [0.038140] Ignoring BGRT: invalid status 0 (expected 1) [6.988640] ACPI PCC probe failed. [ 25.409944] systemd-logind[1530]: Failed to start user service: Unknown unit: user@108.service [ 29.503860] systemd-logind[1530]: Failed to start user service: Unknown unit: user@1000.service [ 2328.943941] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=76355 end=76356) The Intel GPU part: [ 2328.943941] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=76355 end=76356) [ 2342.508179] [ cut here ] [ 2342.508239] WARNING: CPU: 0 PID: 0 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698 intel_check_page_flip+0xe6/0xf0 [i915]() [ 2342.508243] Kicking stuck page flip: queued at 122851, now 122856 [ 2342.508246] Modules linked in: ctr ccm bnep rfcomm nls_iso8859_1 hid_generic usbhid btusb bluetooth hp_wmi sparse_keymap joydev intel_rapl arc4 intel_soc_dts_thermal rtl8723be intel_powerclamp btcoexist coretemp rtl8723_common kvm_intel uvcvideo rtl_pci rtlwifi videobuf2_vmalloc kvm mac80211 videobuf2_memops videobuf2_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel v4l2_common snd_hda_codec_hdmi videodev cryptd media snd_hda_codec_realtek snd_hda_codec_generic cfg80211 snd_intel_sst_acpi snd_intel_sst_core snd_soc_rt5640 snd_soc_rl6231 snd_soc_sst_mfld_platform i915 snd_hda_intel snd_soc_core rtsx_pci_ms snd_hda_controller memstick snd_hda_codec snd_compress snd_pcm_dmaengine snd_hwdep serio_raw snd_pcm drm_kms_helper shpchp drm mei_txe mei snd_seq_midi lpc_ich snd_seq_midi_event i2c_algo_bit [ 2342.508317] iosf_mbi snd_rawmidi wmi snd_seq dw_dmac video snd_seq_device dw_dmac_core snd_timer hp_wireless int3400_thermal parport_pc intel_smartconnect int3403_thermal processor_thermal_device acpi_thermal_rel ppdev snd i2c_hid rfkill_gpio hid soundcore lp i2c_designware_platform pwm_lpss_platform snd_soc_sst_acpi 8250_dw mac_hid parport i2c_designware_core pwm_lpss spi_pxa2xx_platform mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 2342.508365] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.19.0-994-generic #201502112105 [ 2342.508368] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 2342.508372] 25e2 880076c03d08 817c5530 0007 [ 2342.508378] 880076c03d58 880076c03d48 81076e87 0924 [ 2342.508384] 880077d79000 880079b729a8 880079b72800 [ 2342.508390] Call Trace: [ 2342.508394] IRQ [817c5530] dump_stack+0x45/0x57 [ 2342.508412] [81076e87] warn_slowpath_common+0x97/0xe0 [ 2342.508418] [81076f86] warn_slowpath_fmt+0x46/0x50 [ 2342.508458] [c0752086] intel_check_page_flip+0xe6/0xf0 [i915] [ 2342.508492] [c0714388] valleyview_pipestat_irq_handler+0x188/0x220 [i915] [ 2342.508526] [c071ab1f] valleyview_irq_handler+0xaf/0x180 [i915] [ 2342.508534] [810ce4cd] handle_irq_event_percpu+0x5d/0x1e0 [ 2342.508540] [810ce698] handle_irq_event+0x48/0x70 [ 2342.508546] [810d171f] handle_edge_irq+0x7f/0x120 [ 2342.508552] [810178a2] handle_irq+0x22/0x40 [ 2342.508559] [817d578c] do_IRQ+0x5c/0x110 [ 2342.508565] [817d35ed] common_interrupt+0x6d/0x6d [ 2342.508568] EOI [810d7575] ? rcu_nocb_kthread+0xf5/0x190 [ 2342.508580] [8165a9b4] ? cpuidle_enter_state+0x74/0x190 [ 2342.508586] [8165a99f] ? cpuidle_enter_state+0x5f/0x190 [ 2342.508592] [8165ab97] cpuidle_enter+0x17/0x20 [ 2342.508599] [810b79c1] cpuidle_idle_call+0x101/0x1c0 [ 2342.508605] [810b7c55] cpu_idle_loop+0x1d5/0x1f0 [ 2342.508613] [81d3a120] ? early_idt_handlers+0x120/0x120 [ 2342.508618] [810b7cca] cpu_startup_entry+0x5a/0x60 [ 2342.508625] [817ad277] rest_init+0x77/0x80 [ 2342.508631] [81d3b124] start_kernel+0x3e9/0x3f0 [ 2342.508637] [81d3abcd] ? set_init_arg+0x56/0x56 [ 2342.508643] [817b3dc6] ? memblock_reserve+0x4c/0x51 [ 2342.508649] [81d3a5f8] x86_64_start_reservations+0x2a/0x2c [ 2342.508655] [81d3a73e] x86_64_start_kernel+0x144/0x153 [ 2342.508659] ---[ end trace f62bf170971b3c29 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
After 24 hours of use, still no slub.c error message in dmesg. $ dmesg | grep -i slub [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] Linux version 3.18.0-13-generic (root@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu5) ) #14 SMP Tue Feb 17 11:13:29 UTC 2015 (Ubuntu 3.18.0-13.14~lp1418286v1-generic 3.18.5) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
Thanks! I'll do that tonight. Question: should I install all four debs, so also the linux-image-extra? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
OK, now running that new kernel. Well, at least I think it is, but it says: $ uname -a Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Made on Feb 6? Can that be right? There was no sign of 3.18.0-13.14~lp1418286v1 in my Grub menu, only 3.18.0-13. Is that good? dmesg now shows 129 times this line Request for unknown module key 'Magrathea: Glacier signing key: bf41f129406f110879b32f34256d25445a48cb14' err -11 ... so that is a sign I do have another kernel. ;-) Snippet from sudo dpkg -i *deb': Setting up linux-image-extra-3.18.0-13-generic (3.18.0-13.14~lp1418286v1) ... So far no slub.c in dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
Thanks. Current situtation: sander@superstreamer:~$ uptime dmesg | grep -i -e Linux version -e slub 22:22:32 up 2:59, 1 user, load average: 1,74, 0,90, 0,70 [0.00] Linux version 3.18.0-13-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu5) ) #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 (Ubuntu 3.18.0-13.14-generic 3.18.5) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 sander@superstreamer:~$ So: 1) still no slub.c messages; that's good. 2) The Linux version does show Ubuntu 3.18.0-13.14-generic. Is that your kernel version? I'll do the download install procedure once again anyway: lynx --dump http://people.canonical.com/~henrix/lp1418286/v1/ | grep http | egrep -e .*deb | awk '{ print wget $2 }' | /bin/sh -rw-r--r-- 1 sander sander 9281220 feb 17 12:50 linux-headers-3.18.0-13_3.18.0-13.14~lp1418286v1_all.deb -rw-r--r-- 1 sander sander 821582 feb 17 12:50 linux-headers-3.18.0-13-generic_3.18.0-13.14~lp1418286v1_amd64.deb -rw-r--r-- 1 sander sander 16514422 feb 17 12:50 linux-image-3.18.0-13-generic_3.18.0-13.14~lp1418286v1_amd64.deb -rw-r--r-- 1 sander sander 37643802 feb 17 12:50 linux-image-extra-3.18.0-13-generic_3.18.0-13.14~lp1418286v1_amd64.deb sander@superstreamer:~/sander-card/kernel/henrix$ sudo dpkg -i *deb [sudo] password for sander: (Reading database ... 342416 files and directories currently installed.) Preparing to unpack linux-headers-3.18.0-13_3.18.0-13.14~lp1418286v1_all.deb ... Unpacking linux-headers-3.18.0-13 (3.18.0-13.14~lp1418286v1) over (3.18.0-13.14~lp1418286v1) ... Preparing to unpack linux-headers-3.18.0-13-generic_3.18.0-13.14~lp1418286v1_amd64.deb ... Unpacking linux-headers-3.18.0-13-generic (3.18.0-13.14~lp1418286v1) over (3.18.0-13.14~lp1418286v1) ... Preparing to unpack linux-image-3.18.0-13-generic_3.18.0-13.14~lp1418286v1_amd64.deb ... Done. Unpacking linux-image-3.18.0-13-generic (3.18.0-13.14~lp1418286v1) over (3.18.0-13.14~lp1418286v1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic Preparing to unpack linux-image-extra-3.18.0-13-generic_3.18.0-13.14~lp1418286v1_amd64.deb ... Unpacking linux-image-extra-3.18.0-13-generic (3.18.0-13.14~lp1418286v1) over (3.18.0-13.14~lp1418286v1) ... Setting up linux-headers-3.18.0-13 (3.18.0-13.14~lp1418286v1) ... Setting up linux-headers-3.18.0-13-generic (3.18.0-13.14~lp1418286v1) ... Setting up linux-image-3.18.0-13-generic (3.18.0-13.14~lp1418286v1) ... Running depmod. update-initramfs: deferring update (hook will be called later) Not updating initrd symbolic links since we are being updated/reinstalled (3.18.0-13.14~lp1418286v1 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (3.18.0-13.14~lp1418286v1 was configured last, according to dpkg) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic update-initramfs: Generating /boot/initrd.img-3.18.0-13-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.19.0-031900rc7-lowlatency Found initrd image: /boot/initrd.img-3.19.0-031900rc7-lowlatency Found linux image: /boot/vmlinuz-3.19.0-031900rc7-generic Found initrd image: /boot/initrd.img-3.19.0-031900rc7-generic Found linux image: /boot/vmlinuz-3.19.0-031900-lowlatency Found initrd image: /boot/initrd.img-3.19.0-031900-lowlatency Found linux image: /boot/vmlinuz-3.19.0-031900-generic Found initrd image: /boot/initrd.img-3.19.0-031900-generic Found linux image: /boot/vmlinuz-3.19.0-999-generic Found initrd image: /boot/initrd.img-3.19.0-999-generic Found linux image: /boot/vmlinuz-3.19.0-994-generic Found initrd image: /boot/initrd.img-3.19.0-994-generic Found linux image: /boot/vmlinuz-3.18.0-13-generic Found initrd image: /boot/initrd.img-3.18.0-13-generic Found Windows Boot Manager on /dev/mmcblk0p1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done Setting up linux-image-extra-3.18.0-13-generic (3.18.0-13.14~lp1418286v1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-13-generic /boot/vmlinuz-3.18.0-13-generic run-parts: executing
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
Rebooted, and same result sander@superstreamer:~$ uname -a Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux sander@superstreamer:~$ sander@superstreamer:~$ dpkg -l | grep -e linux-image- -e ^| | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description rc linux-image-3.18.0-12-generic3.18.0-12.13 amd64Linux kernel image for version 3.18.0 on 64 bit x86 SMP ii linux-image-3.18.0-13-generic 3.18.0-13.14~lp1418286v1 amd64Linux kernel image for version 3.18.0 on 64 bit x86 SMP ii linux-image-3.19.0-031900-generic 3.19.0-031900.201502091451 amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP ii linux-image-3.19.0-031900-lowlatency 3.19.0-031900.201502091451 amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP ii linux-image-3.19.0-031900rc7-generic 3.19.0-031900rc7.201502020035 amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP ii linux-image-3.19.0-031900rc7-lowlatency 3.19.0-031900rc7.201502020035 amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP ii linux-image-3.19.0-994-generic 3.19.0-994.201502112105amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP ii linux-image-3.19.0-999-generic 3.19.0-999.201502142105amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP rc linux-image-extra-3.18.0-12-generic 3.18.0-12.13 amd64Linux kernel extra modules for version 3.18.0 on 64 bit x86 SMP ii linux-image-extra-3.18.0-13-generic 3.18.0-13.14~lp1418286v1 amd64Linux kernel extra modules for version 3.18.0 on 64 bit x86 SMP ii linux-image-generic 3.18.0.13.13 amd64Generic Linux kernel image I'll remove all 3.18 kernels, boot into 3.19, and reinstall your kernels. sudo apt-get autoremove linux-image-3.18.0-12-generic linux-image-3.18.0-13-generic linux-image-extra-3.18.0-12-generic linux-image-extra-3.18.0-13-generic linux-image-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
After the autoremove purge, reboot into 3.19, and a fresh install of your kernel debs, things look better: sander@superstreamer:~$ dmesg | grep -i -e Linux version -e slub [0.00] Linux version 3.18.0-13-generic (root@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu5) ) #14 SMP Tue Feb 17 11:13:29 UTC 2015 (Ubuntu 3.18.0-13.14~lp1418286v1-generic 3.18.5) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 That's your kernel, right? sander@superstreamer:~$ uname -a Linux superstreamer 3.18.0-13-generic #14 SMP Tue Feb 17 11:13:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Looks good too, doesn't it? sander@superstreamer:~$ dmesg | grep -i glacier [6.976306] Loaded X.509 cert 'Magrathea: Glacier signing key: bf41f129406f110879b32f34256d25445a48cb14' sander@superstreamer:~$ No more Glacier messages. Hooray! So: installing the kernel now looks good. Sorry for the noise. I'll now keep the kernel running for a few hours and check for slub again. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
Ouch, it's still there in 3.18.0-13-generic: sander@superstreamer:~$ uname -a Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux sander@superstreamer:~$ sander@superstreamer:~$ dmesg | grep -i slub [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 26.373219] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 26.508415] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 26.644419] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 26.770748] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 26.887036] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 27.011276] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 27.129399] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 27.247595] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 27.369409] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 27.496308] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 27.617541] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! sander@superstreamer:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
full dmesg ** Attachment added: dmesg-3.18.0-13-generic.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+attachment/4319682/+files/dmesg-3.18.0-13-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
Running 3.19.0-994-generic #201502112105 from http://kernel.ubuntu.com /~kernel-ppa/mainline/drm-intel-nightly/2015-02-12-vivid/ and now dmesg shows a warning in a different line of intel_display.c: [ 2702.807816] WARNING: CPU: 0 PID: 3 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698 intel_check_page_flip+0xe6/0xf0 [i915]() [ 2702.807734] [ cut here ] [ 2702.807816] WARNING: CPU: 0 PID: 3 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698 intel_check_page_flip+0xe6/0xf0 [i915]() [ 2702.807822] Kicking stuck page flip: queued at 161538, now 161547 [ 2702.807827] Modules linked in: hp_wmi sparse_keymap hid_generic intel_rapl intel_soc_dts_thermal intel_powerclamp coretemp btusb kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd arc4 joydev rtl8723be btcoexist snd_hda_codec_hdmi serio_raw rtl8723_common rtl_pci snd_hda_codec_realtek snd_hda_codec_generic i915 uvcvideo rtlwifi snd_intel_sst_acpi videobuf2_vmalloc snd_intel_sst_core videobuf2_memops snd_soc_rt5640 mac80211 snd_soc_sst_mfld_platform videobuf2_core rtsx_pci_ms snd_soc_rl6231 v4l2_common snd_hda_intel cfg80211 memstick drm_kms_helper snd_hda_controller snd_soc_core snd_compress snd_hda_codec videodev media snd_hwdep snd_pcm_dmaengine drm snd_pcm snd_seq_midi iosf_mbi snd_seq_midi_event i2c_algo_bit lpc_ich mei_txe shpchp mei wmi snd_rawmidi snd_seq snd_seq_device [ 2702.807936] snd_timer video hp_wireless dw_dmac dw_dmac_core snd rfcomm bnep usbhid int3403_thermal processor_thermal_device int3400_thermal acpi_thermal_rel bluetooth i2c_hid intel_smartconnect hid soundcore rfkill_gpio snd_soc_sst_acpi i2c_designware_platform i2c_designware_core pwm_lpss_platform spi_pxa2xx_platform 8250_dw pwm_lpss parport_pc mac_hid ppdev lp parport nls_iso8859_1 mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 2702.808006] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 3.19.0-994-generic #201502112105 [ 2702.808011] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 2702.808017] 25e2 880076c03d08 817c5530 0007 [ 2702.808027] 880076c03d58 880076c03d48 81076e87 0a8c [ 2702.808036] 880073405000 88007315c9a8 88007315c800 [ 2702.808045] Call Trace: [ 2702.808050] IRQ [817c5530] dump_stack+0x45/0x57 [ 2702.808075] [81076e87] warn_slowpath_common+0x97/0xe0 [ 2702.808084] [81076f86] warn_slowpath_fmt+0x46/0x50 [ 2702.808145] [c07dc086] intel_check_page_flip+0xe6/0xf0 [i915] [ 2702.808195] [c079e388] valleyview_pipestat_irq_handler+0x188/0x220 [i915] [ 2702.808246] [c07a4b1f] valleyview_irq_handler+0xaf/0x180 [i915] [ 2702.808258] [810ce4cd] handle_irq_event_percpu+0x5d/0x1e0 [ 2702.808267] [810ce698] handle_irq_event+0x48/0x70 [ 2702.808276] [810d171f] handle_edge_irq+0x7f/0x120 [ 2702.808285] [810178a2] handle_irq+0x22/0x40 [ 2702.808295] [817d578c] do_IRQ+0x5c/0x110 [ 2702.808304] [817d35ed] common_interrupt+0x6d/0x6d [ 2702.808309] EOI [c0910002] ? rtl8723be_card_disable+0x32/0x80 [rtl8723be] [ 2702.808333] [c0725030] ? pci_read16_sync+0x10/0x20 [rtl_pci] [ 2702.808347] [c0918a83] rtl8723be_tx_polling+0x53/0x60 [rtl8723be] [ 2702.808358] [c07254f9] rtl_pci_tx+0x1e9/0x430 [rtl_pci] [ 2702.808374] [c08ae5e9] ? rtl_get_tcb_desc+0x169/0x360 [rtlwifi] [ 2702.808417] [c066916b] ? rate_control_apply_mask.isra.10+0x6b/0x1c0 [mac80211] [ 2702.808453] [c05b7324] ? ieee80211_get_hdrlen_from_skb+0x24/0x40 [cfg80211] [ 2702.808469] [c08b1e22] rtl_op_tx+0xb2/0xc0 [rtlwifi] [ 2702.808510] [c0678c02] ieee80211_tx_frags+0xd2/0x200 [mac80211] [ 2702.808551] [c0678db3] __ieee80211_tx+0x83/0x190 [mac80211] [ 2702.808592] [c067bd62] ieee80211_tx+0xd2/0x100 [mac80211] [ 2702.808635] [c067bf02] ieee80211_xmit+0xa2/0x110 [mac80211] [ 2702.808676] [c067c340] __ieee80211_subif_start_xmit+0x90/0xb0 [mac80211] [ 2702.808718] [c067c370] ieee80211_subif_start_xmit+0x10/0x20 [mac80211] [ 2702.808728] [816b3660] xmit_one+0x70/0x150 [ 2702.808738] [816a07e0] ? skb_ts_get_next_block+0x20/0x20 [ 2702.808748] [816afd00] ? skb_checksum_help+0x40/0x1e0 [ 2702.808757] [816b657b] dev_hard_start_xmit+0x4b/0xa0 [ 2702.808768] [816d7e8a] sch_direct_xmit+0x10a/0x1e0 [ 2702.808778] [816b677c] __dev_queue_xmit+0x1ac/0x560 [ 2702.808786] [816b6b50] dev_queue_xmit+0x10/0x20 [ 2702.808797] [8175b5a4] ip6_finish_output2+0x1c4/0x4b0 [ 2702.808807] [810af74f] ? enqueue_entity+0x2bf/0x570 [ 2702.808817] [8175e075] ip6_finish_output+0x95/0xd0 [ 2702.808826] [8175e0ee] ip6_output+0x3e/0xb0 [ 2702.808835] [8176a1f7] ?
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
I'm now running 3.19.0-999-generic #201502092105 which also shows [ 930.448104] WARNING: CPU: 0 PID: 0 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() I'll now try the kernel you pointed to. BRB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
Solved by installing the kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/daily/2015-02-10-vivid/ leading to 3.19.0-999-generic #201502092105 According to https://bugzilla.kernel.org/show_bug.cgi?id=92981 the kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ was built incorrectly ** Bug watch added: Linux Kernel Bug Tracker #92981 http://bugzilla.kernel.org/show_bug.cgi?id=92981 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+attachment/4316320/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420290] [NEW] WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
Public bug reported: Running Vivid with kernel 3.19 (debs from http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.19-vivid/), I get the warning below in dmesg. I can't use ubuntu-bug linux because I get It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue. If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file.. IMHO that last advice would be a DTO (Defeating The Objective), as this message does not appear in the 3.18. $ uname -a Linux superstreamer 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 14:52:52 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [ 2243.390997] [ cut here ] [ 2243.391046] WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() [ 2243.391049] Kicking stuck page flip: queued at 134027, now 134031 [ 2243.391051] Modules linked in: hid_generic(E) hp_wmi(E) sparse_keymap(E) joydev(E) rfcomm(E) bnep(E) intel_rapl(E) intel_soc_dts_thermal(E) intel_powerclamp(E) snd_hda_codec_hdmi(E) coretemp(E) kvm_intel(E) snd_hda_codec_realtek(E) kvm(E) snd_hda_codec_generic(E) crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) cryptd(E) arc4(E) rtl8723be(E) btcoexist(E) snd_hda_intel(E) usbhid(E) rtl8723_common(E) snd_hda_controller(E) rtl_pci(E) serio_raw(E) rtlwifi(E) snd_hda_codec(E) snd_intel_sst_acpi(E) nls_iso8859_1(E) snd_hwdep(E) snd_intel_sst_core(E) snd_soc_sst_mfld_platform(E) mac80211(E) rtsx_pci_ms(E) snd_seq_midi(E) memstick(E) snd_soc_rt5640(E) snd_soc_rl6231(E) snd_seq_midi_event(E) cfg80211(E) lpc_ich(E) i915(E) snd_soc_core(E) snd_rawmidi(E) snd_compress(E) wmi(E) hp_wireless(E) snd_pcm_dmaengine(E) [ 2243.391089] snd_seq(E) dw_dmac(E) dw_dmac_core(E) int3400_thermal(E) snd_seq_device(E) snd_pcm(E) int3403_thermal(E) processor_thermal_device(E) acpi_thermal_rel(E) intel_smartconnect(E) video(E) drm_kms_helper(E) drm(E) i2c_hid(E) snd_timer(E) hid(E) snd(E) i2c_designware_platform(E) soundcore(E) i2c_designware_core(E) i2c_algo_bit(E) shpchp(E) parport_pc(E) snd_soc_sst_acpi(E) btusb(E) mei_txe(E) mei(E) rfkill_gpio(E) iosf_mbi(E) ppdev(E) spi_pxa2xx_platform(E) bluetooth(E) 8250_dw(E) pwm_lpss_platform(E) pwm_lpss(E) lp(E) parport(E) mac_hid(E) mmc_block(E) rtsx_pci_sdmmc(E) psmouse(E) rtsx_pci(E) sdhci_acpi(E) sdhci(E) [ 2243.391129] CPU: 0 PID: 2517 Comm: Chrome_IOThread Tainted: GE 3.19.0-031900-generic #201502091451 [ 2243.391131] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 2243.391134] 25f1 880076c03630 817c4c00 0007 [ 2243.391138] 880076c03680 880076c03670 81076e87 0748a8c1 [ 2243.391142] 880036b91000 8800700909a8 880070090800 [ 2243.391146] Call Trace: [ 2243.391149] IRQ [817c4c00] dump_stack+0x45/0x57 [ 2243.391162] [81076e87] warn_slowpath_common+0x97/0xe0 [ 2243.391166] [81076f86] warn_slowpath_fmt+0x46/0x50 [ 2243.391192] [c04408a6] intel_check_page_flip+0xe6/0xf0 [i915] [ 2243.391214] [c0405628] valleyview_pipestat_irq_handler+0x188/0x220 [i915] [ 2243.391236] [c040bd2f] valleyview_irq_handler+0xaf/0x180 [i915] [ 2243.391242] [8175d745] ? ip6_finish_output+0x95/0xd0 [ 2243.391247] [810ce4cd] handle_irq_event_percpu+0x5d/0x1e0 [ 2243.391251] [8175b18a] ? ip6_xmit+0x22a/0x490 [ 2243.391255] [810ce698] handle_irq_event+0x48/0x70 [ 2243.391258] [810d171f] handle_edge_irq+0x7f/0x120 [ 2243.391263] [810178a2] handle_irq+0x22/0x40 [ 2243.391267] [817d4e4c] do_IRQ+0x5c/0x110 [ 2243.391271] [817d2cad] common_interrupt+0x6d/0x6d [ 2243.391276] [81703921] ? tcp_queue_rcv+0x21/0x130 [ 2243.391280] [816a7ac2] ? __skb_checksum_complete+0x22/0xd0 [ 2243.391284] [81708b54] tcp_rcv_established+0x194/0x740 [ 2243.391289] [81786126] tcp_v6_do_rcv+0x216/0x450 [ 2243.391294] [81312226] ? security_sock_rcv_skb+0x16/0x20 [ 2243.391298] [817872c6] tcp_v6_rcv+0x796/0x7e0 [ 2243.391304] [c073523f] ? _rtl_pci_rx_interrupt+0x4af/0x680 [rtl_pci] [ 2243.391309] [8175da20] ip6_input_finish+0x140/0x420 [ 2243.391313] [8175e202] ip6_input+0x22/0x60 [ 2243.391317] [81784f58] ? tcp_v6_early_demux+0x58/0x70 [ 2243.391321] [8175d8a8] ip6_rcv_finish+0x78/0xb0 [ 2243.391324] [8175dff7] ipv6_rcv+0x2f7/0x4e0 [ 2243.391329] [816b3c63] __netif_receive_skb_core+0x513/0x670 [ 2243.391332] [816b3de1] __netif_receive_skb+0x21/0x70 [ 2243.391336] [816b3fa3] netif_receive_skb_internal+0x23/0x90 [ 2243.391339] [816b403d] netif_receive_skb+0x2d/0x80 [ 2243.391364]
[Bug 1420290] Re: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]()
These seem the same bug reports on Redhat, since january https://bugzilla.redhat.com/show_bug.cgi?id=1190511 https://bugzilla.redhat.com/show_bug.cgi?id=1181071 https://bugzilla.redhat.com/show_bug.cgi?id=1184161 https://bugzilla.redhat.com/show_bug.cgi?id=1183209 ** Bug watch added: Red Hat Bugzilla #1190511 https://bugzilla.redhat.com/show_bug.cgi?id=1190511 ** Bug watch added: Red Hat Bugzilla #1181071 https://bugzilla.redhat.com/show_bug.cgi?id=1181071 ** Bug watch added: Red Hat Bugzilla #1184161 https://bugzilla.redhat.com/show_bug.cgi?id=1184161 ** Bug watch added: Red Hat Bugzilla #1183209 https://bugzilla.redhat.com/show_bug.cgi?id=1183209 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420290 Title: WARNING: CPU: 0 PID: 2517 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xe6/0xf0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
FWIW: I'm now running the latest 3.18 (3.18.0-13-generic) which arrived today (Feb 10), and no more slub.c messages in dmesg. So ... was it solved in 3.18.0-13-generic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
FWIW: I also installed the lowlatency version of kernel 3.19, and that dmesg doesn't show the lines Request for unknown module key 'Magrathea: Glacier signing key: sander@superstreamer:~$ uname -a Linux superstreamer 3.19.0-031900-lowlatency #201502091451 SMP PREEMPT Mon Feb 9 14:58:45 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux sander@superstreamer:~$ dmesg | grep -i glacier [6.957630] Loaded X.509 cert 'Magrathea: Glacier signing key: 4b8b0790309384d5db8e13c15cd6ff49ef07' To be complete: before 3.19 I was running 3.19-rc7, and that dmesg neither showed the lines Request for unknown module key 'Magrathea: Glacier signing key: So it's something specific to 3.19 generic (amd64)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
I just installed kernel 3.19 on vivid (source: http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.19-vivid/), and dmesg shows 129 lines with Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 So ... is this a regression bug? Or something went wrong with the signing of this kernel 3.19? $ uname -a Linux superstreamer 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 14:52:52 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep -i glacier [6.992226] Loaded X.509 cert 'Magrathea: Glacier signing key: 7271576a09d86ef244371b0633e47abb75b89d' [7.066499] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [7.066985] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [7.069196] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [7.084944] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [7.089825] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [7.156929] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [7.192863] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [7.979314] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.115413] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.119104] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.196243] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.199199] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.228059] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.273340] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.274045] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.274848] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.284877] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.286741] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.297792] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.312831] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.337451] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.337938] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.338046] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.361077] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.361692] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.363517] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.363690] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.363866] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.364217] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.370473] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.371876] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.372689] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.388289] Request for unknown module key 'Magrathea: Glacier signing key: 007271576a09d86ef244371b0633e47abb75b89d' err -11 [8.389244] Request for unknown module key 'Magrathea: Glacier signing key:
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
@myself: It was a noob thing indeed: I had linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb and needed the all.deb file too: linux-headers-3.19.0-031900rc7_3.19.0-031900rc7.201502020035_all.deb linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb And with these three files the sudo dpkg -i *deb went fine. Generic command to get and install the three needed debs (amd64, generic): lynx --dump http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc7-vivid/ | grep -e all.deb -e generic.*amd64 | awk '{ print wget $2 }' | /bin/sh sudo dpkg -i *deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
I've installed v3.19-rc7-vivid (thus now running 3.19.0-031900rc7-generic) and the dmesg message is gone now. Good! FWIW: with linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb I did sudo dpkg -i *031900rc7-generic_3.19.0*deb and the kernel itself went OK, but the headers didn't: Errors were encountered while processing: linux-headers-3.19.0-031900rc7-generic But could be a noob thing, but I can't find it. Tips welcome Full log: sander@superstreamer:~/Downloads/3.19.0-031900rc7$ sudo dpkg -i *deb (Reading database ... 187321 files and directories currently installed.) Preparing to unpack linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb ... Unpacking linux-headers-3.19.0-031900rc7-generic (3.19.0-031900rc7.201502020035) over (3.19.0-031900rc7.201502020035) ... Preparing to unpack linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb ... Done. Unpacking linux-image-3.19.0-031900rc7-generic (3.19.0-031900rc7.201502020035) over (3.19.0-031900rc7.201502020035) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.19.0-031900rc7-generic /boot/vmlinuz-3.19.0-031900rc7-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.19.0-031900rc7-generic /boot/vmlinuz-3.19.0-031900rc7-generic dpkg: dependency problems prevent configuration of linux-headers-3.19.0-031900rc7-generic: linux-headers-3.19.0-031900rc7-generic depends on linux-headers-3.19.0-031900rc7; however: Package linux-headers-3.19.0-031900rc7 is not installed. dpkg: error processing package linux-headers-3.19.0-031900rc7-generic (--install): dependency problems - leaving unconfigured Setting up linux-image-3.19.0-031900rc7-generic (3.19.0-031900rc7.201502020035) ... Running depmod. update-initramfs: deferring update (hook will be called later) Not updating initrd symbolic links since we are being updated/reinstalled (3.19.0-031900rc7.201502020035 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (3.19.0-031900rc7.201502020035 was configured last, according to dpkg) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-031900rc7-generic /boot/vmlinuz-3.19.0-031900rc7-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-031900rc7-generic /boot/vmlinuz-3.19.0-031900rc7-generic update-initramfs: Generating /boot/initrd.img-3.19.0-031900rc7-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-031900rc7-generic /boot/vmlinuz-3.19.0-031900rc7-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-031900rc7-generic /boot/vmlinuz-3.19.0-031900rc7-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-031900rc7-generic /boot/vmlinuz-3.19.0-031900rc7-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.19.0-031900rc7-generic Found initrd image: /boot/initrd.img-3.19.0-031900rc7-generic Found linux image: /boot/vmlinuz-3.18.0-12-generic Found initrd image: /boot/initrd.img-3.18.0-12-generic Found Windows Boot Manager on /dev/mmcblk0p1@/EFI/Microsoft/Boot/bootmgfw.efi Found Debian GNU/Linux (wheezy/sid) on /dev/mmcblk1p2 Adding boot menu entry for EFI firmware configuration done Errors were encountered while processing: linux-headers-3.19.0-031900rc7-generic sander@superstreamer:~/Downloads/3.19.0-031900rc7$ ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418286 Title: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418286] Re: kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
Happens on my system too. I did a fresh install of Vivid daily two days ago (Feb 3), did a update/upgrade today (Feb 5), and after the reboot dmesg shows: [ 11.252422] [ cut here ] [ 11.252475] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 11.252526] invalid opcode: [#1] SMP [ 11.252564] Modules linked in: hid_generic hp_wmi sparse_keymap intel_rapl intel_soc_dts_thermal intel_powerclamp coretemp arc4 kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd rtl8723be btcoexist rtl8723_common rtl_pci rtlwifi mac80211 usbhid i915 cfg80211 snd_hda_codec_hdmi serio_raw snd_soc_rt5640 snd_soc_rl6231 snd_hda_codec_realtek snd_hda_codec_generic snd_soc_core drm_kms_helper snd_compress snd_pcm_dmaengine snd_seq_midi lpc_ich rtsx_pci_ms snd_seq_midi_event drm memstick mei_txe snd_hda_intel mei snd_rawmidi snd_hda_controller snd_hda_codec iosf_mbi snd_hwdep i2c_algo_bit snd_pcm shpchp snd_seq wmi snd_seq_device snd_timer snd video dw_dmac hp_wireless dw_dmac_core int3403_thermal int3400_thermal acpi_thermal_rel soundcore intel_smartconnect i2c_hid hid bnep rfcomm snd_soc_sst_acpi [ 11.253253] rfkill_gpio i2c_designware_platform pwm_lpss_platform i2c_designware_core parport_pc spi_pxa2xx_platform 8250_dw ppdev pwm_lpss lp parport btusb bluetooth joydev mac_hid nls_iso8859_1 mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 11.253463] CPU: 1 PID: 868 Comm: thermald Not tainted 3.18.0-12-generic #13-Ubuntu [ 11.253521] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 11.253586] task: 8800772dda00 ti: 8800720a8000 task.ti: 8800720a8000 [ 11.253642] RIP: 0010:[811d4093] [811d4093] kfree+0x143/0x150 [ 11.253707] RSP: 0018:8800720abe18 EFLAGS: 00010246 [ 11.253748] RAX: 01000400 RBX: 811f075d RCX: 0ec6 [ 11.253801] RDX: RSI: 880076c96800 RDI: 811f075d [ 11.253854] RBP: 8800720abe38 R08: 00016800 R09: ea047c00 [ 11.253908] R10: 8145dc27 R11: 0246 R12: 7fff15acbae8 [ 11.253962] R13: c03787ea R14: 80087304 R15: 7fff15acbae8 [ 11.254017] FS: 7f9c1a78c840() GS:880076c8() knlGS: [ 11.254078] CS: 0010 DS: ES: CR0: 80050033 [ 11.254122] CR2: 7f9c1a803060 CR3: 797f5000 CR4: 001007e0 [ 11.254176] Stack: [ 11.254193] 7fff15acbae8 7fff15acbae8 880077b702f8 [ 11.254258] 8800720abea8 c03787ea 88003f4fe6f8 88007713b020 [ 11.254322] 8800720abe88 811f075d [ 11.254386] Call Trace: [ 11.254426] [c03787ea] acpi_thermal_rel_ioctl+0x21a/0xa30 [acpi_thermal_rel] [ 11.254495] [811f075d] ? ftrace_raw_event_do_sys_open+0x8d/0xe0 [ 11.254550] [81208078] do_vfs_ioctl+0x2c8/0x4a0 [ 11.254595] [81204826] ? final_putname+0x26/0x50 [ 11.254640] [81204ac9] ? putname+0x29/0x40 [ 11.254681] [811f2ad9] ? do_sys_open+0x1b9/0x280 [ 11.254725] [812082d1] SyS_ioctl+0x81/0xa0 [ 11.254767] [817b536d] system_call_fastpath+0x16/0x1b [ 11.254814] Code: 49 8b 41 30 49 8b 11 80 e6 80 4c 0f 45 c8 e9 3b ff ff ff 0f 1f 44 00 00 4c 89 d1 48 89 da 4c 89 ce e8 32 f9 ff ff e9 71 ff ff ff 0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 f7 c6 06 [ 11.255096] RIP [811d4093] kfree+0x143/0x150 [ 11.255142] RSP 8800720abe18 [ 11.265376] ---[ end trace fc4d3c2cb3582f3e ]--- [ 11.321998] init: thermald main process (868) killed by SEGV signal [ 11.322021] init: thermald main process ended, respawning [ 11.375126] [ cut here ] The error appears 11 times in dmesg, all within one second: $ dmesg | grep -A1 slub [ 11.252475] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 11.252526] invalid opcode: [#1] SMP -- [ 11.375178] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 11.375228] invalid opcode: [#2] SMP -- [ 11.515325] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 11.517725] invalid opcode: [#3] SMP -- [ 11.667291] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 11.669728] invalid opcode: [#4] SMP -- [ 11.789354] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 11.791802] invalid opcode: [#5] SMP -- [ 11.910164] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 11.912595] invalid opcode: [#6] SMP -- [ 12.041594] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 12.044000] invalid opcode: [#7] SMP -- [ 12.174770] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 12.177060] invalid opcode: [#8] SMP -- [ 12.292074] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334! [ 12.294512]
[Bug 1417263] Re: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
In the meantime, I decided 14.04 was unusable.for me. So I've done a fresh install of Vivid (15.04-to-be) daily version. That has linux kernel 3.18, right? In one hour of usage, I've not seen the error message in dmesg. TBC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417263 Title: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417263] Re: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
FWIW: the Read-only file system error occured again. See below. Nothing special in dmesg nor /var/log/syslog sander@superstream:~$ pwd /home/sander sander@superstream:~$ touch blabla touch: cannot touch ‘blabla’: Read-only file system sander@superstream:~$ mount /dev/mmcblk0p5 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) none on /sys/firmware/efi/efivars type efivarfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) /dev/mmcblk0p1 on /boot/efi type vfat (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=sander) /dev/mmcblk0p4 on /media/sander/Images type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096) /dev/mmcblk0p3 on /media/sander/Windows type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096) mount: warning: /etc/mtab is not writable (e.g. read-only filesystem). It's possible that information reported by mount(8) is not up to date. For actual information about system mount points check the /proc/mounts file. sander@superstream:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417263 Title: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417263] Re: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
I logged off, restarted, and the Ubuntu boot GUI says / needs to be fixed (I pressed F) and /tmp is not (yet) ready. I did get a Ubuntu brown screen, but no login. I'm typing this in some 'other' OS. I'll see if I can boot into Ubuntu with another boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417263 Title: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417263] Re: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
Second reboot worked. I did some extensive disk writing (around 1GB), got the read-only problem, and dmesg says: [ 962.226687] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 972.262988] mmc0: Timeout waiting for hardware interrupt. [ 972.264987] [ cut here ] [ 972.265008] WARNING: CPU: 1 PID: 0 at /build/buildd/linux-3.13.0/drivers/mmc/host/sdhci.c:989 sdhci_send_command+0xc32/0xd60 [sdhci]() [ 972.265010] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev rfcomm bnep nls_iso8859_1 hid_generic hp_wmi sparse_keymap arc4 intel_rapl coretemp rtl8723be kvm crct10dif_pclmul crc32_pclmul btcoexist rtl8723_common ghash_clmulni_intel cryptd i915_bdw usbhid rtl_pci hid snd_hda_codec_hdmi rtlwifi snd_hda_codec_realtek btusb mac80211 bluetooth serio_raw rtsx_pci_ms memstick cfg80211 wmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd intel_ips drm_kms_helper video hp_wireless drm i2c_algo_bit parport_pc soundcore joydev mac_hid ppdev lp parport usb_storage mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 972.265057] CPU: 1 PID: 0 Comm: swapper/1 Tainted: GW 3.13.0-45-generic #74-Ubuntu [ 972.265060] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 972.265062] 0009 880076683d28 81720eb6 [ 972.265066] 880076683d60 810677cd 0001 880079947650 [ 972.265070] 88003f5e1930 88003f5e1970 8800799474c0 880076683d70 [ 972.265074] Call Trace: [ 972.265077] IRQ [81720eb6] dump_stack+0x45/0x56 [ 972.265089] [810677cd] warn_slowpath_common+0x7d/0xa0 [ 972.265093] [810678aa] warn_slowpath_null+0x1a/0x20 [ 972.265099] [a0003aa2] sdhci_send_command+0xc32/0xd60 [sdhci] [ 972.265105] [813709aa] ? delay_tsc+0x4a/0x80 [ 972.265108] [813708dc] ? __const_udelay+0x2c/0x30 [ 972.265115] [a0001164] ? sdhci_reset+0xa4/0x1b0 [sdhci] [ 972.265121] [a00043e5] sdhci_finish_data+0x115/0x3c0 [sdhci] [ 972.265128] [a0004690] ? sdhci_finish_data+0x3c0/0x3c0 [sdhci] [ 972.265134] [a000470d] sdhci_timeout_timer+0x7d/0xc0 [sdhci] [ 972.265138] [81074386] call_timer_fn+0x36/0x100 [ 972.265145] [a0004690] ? sdhci_finish_data+0x3c0/0x3c0 [sdhci] [ 972.265148] [8107531f] run_timer_softirq+0x1ef/0x2f0 [ 972.265153] [8106cc1c] __do_softirq+0xec/0x2c0 [ 972.265157] [8106d165] irq_exit+0x105/0x110 [ 972.265162] [81733d55] smp_apic_timer_interrupt+0x45/0x60 [ 972.265166] [817326dd] apic_timer_interrupt+0x6d/0x80 [ 972.265168] EOI [815d3712] ? cpuidle_enter_state+0x52/0xc0 [ 972.265175] [815d3839] cpuidle_idle_call+0xb9/0x1f0 [ 972.265180] [8101d35e] arch_cpu_idle+0xe/0x30 [ 972.265185] [810bef35] cpu_startup_entry+0xc5/0x290 [ 972.265190] [810413fd] start_secondary+0x21d/0x2d0 [ 972.265192] ---[ end trace fa59f6fabf0e6688 ]--- [ 972.267360] mmcblk0: error -110 transferring data, sector 29645704, nr 224, cmd response 0x0, card status 0x0 [ 972.267370] blk_update_request: 11 callbacks suppressed [ 972.267373] end_request: I/O error, dev mmcblk0, sector 29645704 [ 972.267379] end_request: I/O error, dev mmcblk0, sector 29645712 [ 972.267383] end_request: I/O error, dev mmcblk0, sector 29645720 [ 972.267387] end_request: I/O error, dev mmcblk0, sector 29645728 [ 972.267390] end_request: I/O error, dev mmcblk0, sector 29645736 [ 972.267394] end_request: I/O error, dev mmcblk0, sector 29645744 [ 972.267397] end_request: I/O error, dev mmcblk0, sector 29645752 [ 972.267400] end_request: I/O error, dev mmcblk0, sector 29645760 [ 972.267403] end_request: I/O error, dev mmcblk0, sector 29645768 [ 972.267406] end_request: I/O error, dev mmcblk0, sector 29645776 [ 972.267529] Aborting journal on device mmcblk0p5-8. [ 972.267544] EXT4-fs error (device mmcblk0p5) in ext4_reserve_inode_write:4902: Journal has aborted [ 972.268665] EXT4-fs error (device mmcblk0p5) in ext4_free_blocks:4882: Journal has aborted [ 972.269152] EXT4-fs error (device mmcblk0p5) in ext4_reserve_inode_write:4902: Journal has aborted [ 972.360668] EXT4-fs (mmcblk0p5): Remounting filesystem read-only [ 972.438561] EXT4-fs error (device mmcblk0p5): mpage_map_and_submit_extent:2273: comm http: Failed to mark inode 320098 dirty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417263 Title: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock To manage notifications about this bug go to:
[Bug 1417263] [NEW] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
Public bug reported: On my HP Stream 13 laptop with Ubuntu 14.04 LTS (fully updated) I sometimes (once an hour?) get the error below in dmesg. It has to do with the eMMC / eMMC reader. There is no other flash device (like a USB key) installed or in use. Yesterday the file system turned read-only. I had to reboot to get it read-write again. [ 2666.946287] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 2666.948450] [ cut here ] [ 2666.948477] WARNING: CPU: 0 PID: 3597 at /build/buildd/linux-3.13.0/drivers/mmc/host/sdhci.c:989 sdhci_send_command+0xc32/0xd60 [sdhci]() [ 2666.948479] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek rfcomm bnep nls_iso8859_1 hid_generic hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event intel_rapl snd_rawmidi coretemp arc4 kvm crct10dif_pclmul crc32_pclmul usbhid snd_seq hid ghash_clmulni_intel rtl8723be btcoexist cryptd snd_seq_device rtl8723_common snd_timer rtl_pci rtlwifi btusb bluetooth mac80211 serio_raw snd rtsx_pci_ms memstick i915_bdw cfg80211 intel_ips drm_kms_helper soundcore drm i2c_algo_bit wmi hp_wireless video parport_pc ppdev joydev mac_hid lp parport mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 2666.948522] CPU: 0 PID: 3597 Comm: chromium-browse Not tainted 3.13.0-45-generic #74-Ubuntu [ 2666.948524] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 2666.948527] 0009 880076a03d28 81720eb6 [ 2666.948531] 880076a03d60 810677cd 0002 88003fb7ac00 [ 2666.948535] 880071b77ad0 880071b77b10 88003f9b74c0 880076a03d70 [ 2666.948539] Call Trace: [ 2666.948542] IRQ [81720eb6] dump_stack+0x45/0x56 [ 2666.948554] [810677cd] warn_slowpath_common+0x7d/0xa0 [ 2666.948557] [810678aa] warn_slowpath_null+0x1a/0x20 [ 2666.948564] [a0003aa2] sdhci_send_command+0xc32/0xd60 [sdhci] [ 2666.948569] [813709aa] ? delay_tsc+0x4a/0x80 [ 2666.948573] [813708dc] ? __const_udelay+0x2c/0x30 [ 2666.948579] [a0001164] ? sdhci_reset+0xa4/0x1b0 [sdhci] [ 2666.948585] [a00043e5] sdhci_finish_data+0x115/0x3c0 [sdhci] [ 2666.948591] [a0004c00] sdhci_irq+0x350/0x8e3 [sdhci] [ 2666.948596] [810bfa5e] handle_irq_event_percpu+0x3e/0x1d0 [ 2666.948600] [810bfc2d] handle_irq_event+0x3d/0x60 [ 2666.948604] [810c2e4a] handle_fasteoi_irq+0x5a/0x100 [ 2666.948608] [81015e5e] handle_irq+0x1e/0x30 [ 2666.948613] [81733c9d] do_IRQ+0x4d/0xc0 [ 2666.948618] [817293ad] common_interrupt+0x6d/0x6d [ 2666.948619] EOI [81728d4b] ? _raw_spin_unlock_irqrestore+0x1b/0x40 [ 2666.948627] [810aaf80] __wake_up_sync_key+0x50/0x60 [ 2666.948632] [811c66dd] pipe_write+0x43d/0x520 [ 2666.948637] [811bd45a] do_sync_write+0x5a/0x90 [ 2666.948641] [811bdbe4] vfs_write+0xb4/0x1f0 [ 2666.948644] [811be619] SyS_write+0x49/0xa0 [ 2666.948648] [81731b7f] tracesys+0xe1/0xe6 [ 2666.948651] ---[ end trace 6d4cc2b5a74f9ad2 ]--- [ 2666.950730] mmcblk0: error -84 transferring data, sector 36853392, nr 8, cmd response 0x0, card status 0x0 [ 2666.950736] mmcblk0: retrying using single block read ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1876 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 2 21:41:26 2015 HibernationDevice: RESUME=UUID=1cce7297-b185-4592-a4a0-dfdc069ad5a1 InstallationDate: Installed on 2015-02-01 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Stream Notebook PC 13 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic.efi.signed root=UUID=dba934e0-c15e-419b-a02a-96c8add96cf2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag
[Bug 1411369] [NEW] crash during install of Vivid within Virtualbox
Public bug reported: crash during install of Vivid within Virtualbox Running on Ubuntu 14.04 LTS 64-bit ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubiquity 2.21.4 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.347 Date: Thu Jan 15 19:56:05 2015 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150115.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.4 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411369 Title: crash during install of Vivid within Virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1411369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411369] Re: crash during install of Vivid within Virtualbox
*** This bug is a duplicate of bug 1408495 *** https://bugs.launchpad.net/bugs/1408495 Workaround found: Instead of booting the Ubuntu live CD and clicking Install, first clicking Try Ubuntu and only then clicking on the Install icon on the desktop, worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411369 Title: crash during install of Vivid within Virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1411369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397319] Re: two sequential login windows after resuming from sleep
Update: After installing gdm (instead of lightdm) the problem did not occur anymore. So: the problem seems to be in lightdm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397319 Title: two sequential login windows after resuming from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1397319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397319] [NEW] two sequential login windows after resuming from sleep
Public bug reported: After resuming from sleep, I sometimes (about 50%) get a first (unusual, ugly) login screen, then a short (1 sec) flash showing my desktop, then the 'normal' login screen First login window: http://oi59.tinypic.com/ws5uo9.jpg Second login window: http://oi57.tinypic.com/24xnx4w.jpg I tried the 4 sudo commands from http://ubuntuforums.org/showthread.php?t=1867733p=11626298#post11626298, but that did not update anything, so I expect that to change nothing. Then, based on http://ubuntuforums.org/showthread.php?t=1867733page=3p=12566826#post12566826, I installed and selected gdm instead of lightdm. I'll post back the results after a few days of usage. TBC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 28 14:03:32 2014 InstallationDate: Installed on 2013-09-01 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-03-17 (255 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397319 Title: two sequential login windows after resuming from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1397319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349128] Re: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators)
I don't understand; I thought it was already fixed on 2014-07-31: This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1.1? Since then I have not experienced it anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators)
When not accepting/showing input from the keyboard, there is the usual vertical blinking line in the password box (so: 'showing' it is accepting input there), with the word password in the background of that password box. Would it help if I post a picture of video of what goes (or: doesn't go) on? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349128] [NEW] Ubuntu 14.04 login screen doesn't accept keyboard input
Public bug reported: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1349128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input
** Package changed: ubuntu = lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1349128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input
Update: Another workaround: change the language in the upper right corner, in my case switch from En1 to En2. After that, the password box accepts keyboard input and shows corresponding dots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1349128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285304] Re: NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out
I can't; too difficult for me. Sorry. Close this bug report if you want to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285304 Title: NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1285304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308200] [NEW] apt-get not RFC6555 (Happy Eyeballs) compliant
Public bug reported: Disclaimer: I'm not sure if this is a bug, or a feature. If it is not a bug, I think reporting this issue is useful anyway because it causes long delays in apt-get install / apt-get update. On dual-stack setups (IPv4 and IPv6), if one of the two paths is slow or non-functional at all, the overall application experience can be slow. An application that uses a Happy Eyeballs (RFC 6555) algorithm checks both IPv4 and IPv6 connectivity (with a preference for IPv6) and uses the first connection that is returned. This has been implemented in, for example, Chrome and Firefox. apt / apt-get does not have this functionality. Due to this lack, a apt- get run can be very slow: a sudo apt-get update can take up to 15 minutes on a system with a non-functional IPv6 connection, even if the system is already uptodate, which normally only takes 15 seconds or so. man apt.conf shows this info: ForceIPv4 When downloading, force to use only the IPv4 protocol. ForceIPv6 When downloading, force to use only the IPv6 protocol. So no feature RFC6555 or HappyEyeballs. An ugly work-around is this: Create a file /etc/apt/apt.conf.d/99timeout with these contents Acquire::http::Timeout 2; Acquire::ftp::Timeout 2; That way, after 2 seconds the other path is chosen. $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 20:26:25 2014 InstallationDate: Installed on 2014-04-10 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308200 Title: apt-get not RFC6555 (Happy Eyeballs) compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1308200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257186] Re: memory leakage messages
PS: So that Google will find it, I'll post my exact message with a different (line?) number: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory HTH -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1257186] Re: memory leakage messages
I can confirm James Dupin's post: gone after sudo apt-get remove libpam-smbpass. See http://ubuntuforums.org/showthread.php?t=2214042 with my experience before I saw this post. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1257186] Re: memory leakage messages
PS: So that Google will find it, I'll post my exact message with a different (line?) number: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory HTH -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257186] Re: memory leakage messages
I can confirm James Dupin's post: gone after sudo apt-get remove libpam-smbpass. See http://ubuntuforums.org/showthread.php?t=2214042 with my experience before I saw this post. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285304] [NEW] NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out
Public bug reported: Fixed ethernet not working, and dmesg says upon connecting the ethernet cable. sander@flappie:~$ uname -a Linux flappie 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux sander@flappie:~$ sander@flappie:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.10 Release:13.10 Codename: saucy sander@flappie:~$ [ 39.963577] [ cut here ] [ 39.963592] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.11.0/net/sched/sch_generic.c:260 dev_watchdog+0x26a/0x280() [ 39.963595] NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out [ 39.963597] Modules linked in: pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) parport_pc ppdev rfcomm bnep bluetooth joydev vesafb(F) binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek intel_powerclamp coretemp kvm_intel kvm samsung_laptop uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core arc4 videodev microcode snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi ath9k psmouse ath9k_common ath9k_hw serio_raw ath intel_ips mac80211 snd_seq lpc_ich snd_seq_device snd_timer snd i915 cfg80211 drm_kms_helper soundcore drm i2c_algo_bit video mac_hid lp parport hid_generic usbhid hid ahci sky2 libahci [ 39.963661] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GF O 3.11.0-15-generic #25-Ubuntu [ 39.963664] Hardware name: SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540 /R530/R730/R540 , BIOS 08JV.M029.20100621.hkk 06/21/2010 [ 39.963666] 0009 880117c03d60 816e7375 880117c03da8 [ 39.963670] 880117c03d98 81061dcd 880111f6e000 [ 39.963673] 88010e7e5c80 88010e7e5c00 880117c03df8 [ 39.963677] Call Trace: [ 39.963679] IRQ [816e7375] dump_stack+0x45/0x56 [ 39.963694] [81061dcd] warn_slowpath_common+0x7d/0xa0 [ 39.963698] [81061e3c] warn_slowpath_fmt+0x4c/0x50 [ 39.963704] [8160f9ea] dev_watchdog+0x26a/0x280 [ 39.963708] [8160f780] ? dev_deactivate_queue.constprop.32+0x60/0x60 [ 39.963716] [8106e776] call_timer_fn+0x36/0x110 [ 39.963719] [8160f780] ? dev_deactivate_queue.constprop.32+0x60/0x60 [ 39.963723] [8106f8dd] run_timer_softirq+0x1fd/0x2b0 [ 39.963728] [810673c7] __do_softirq+0xf7/0x240 [ 39.963733] [816f8c5c] call_softirq+0x1c/0x30 [ 39.963741] [81014bf5] do_softirq+0x55/0x90 [ 39.963744] [810676a5] irq_exit+0xb5/0xc0 [ 39.963748] [816f9605] smp_apic_timer_interrupt+0x45/0x60 [ 39.963754] [816f7f9d] apic_timer_interrupt+0x6d/0x80 [ 39.963755] EOI [8159fe9f] ? cpuidle_enter_state+0x4f/0xc0 [ 39.963765] [8159fe98] ? cpuidle_enter_state+0x48/0xc0 [ 39.963768] [8159ffd9] cpuidle_idle_call+0xc9/0x210 [ 39.963772] [8101bafe] arch_cpu_idle+0xe/0x30 [ 39.963778] [810b54c5] cpu_startup_entry+0xe5/0x280 [ 39.963783] [816d64b7] rest_init+0x77/0x80 [ 39.963790] [81d26ef7] start_kernel+0x40a/0x416 [ 39.963793] [81d268f6] ? repair_env_string+0x5c/0x5c [ 39.963797] [81d26120] ? early_idt_handlers+0x120/0x120 [ 39.963800] [81d265de] x86_64_start_reservations+0x2a/0x2c [ 39.963804] [81d266e8] x86_64_start_kernel+0x108/0x117 [ 39.963806] ---[ end trace a5bab2243373 ]--- [ 39.963813] sky2 :06:00.0 eth0: tx timeout [ 39.963823] sky2 :06:00.0 eth0: transmit ring 17 .. 20 report=17 done=17 ** Affects: upstart-app-launch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285304 Title: NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart-app-launch/+bug/1285304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120617] Re: No IPv6 and IPv6 duplicate address with IPv6 privacy extensions on
In a new setup (Sitecom router, no more Zyxel) and Ubuntu 13.10, I still have the same problem via Wifi: [ 1782.075212] IPv6: wlan0: IPv6 duplicate address 2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected! [ 1813.616483] IPv6: wlan0: IPv6 duplicate address 2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected! [ 1868.605625] IPv6: wlan0: IPv6 duplicate address 2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected! [ 1899.938703] IPv6: wlan0: IPv6 duplicate address 2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected! [ 1955.019861] IPv6: wlan0: IPv6 duplicate address 2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected! [ 2011.786209] IPv6: wlan0: IPv6 duplicate address 2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected! [ 2069.830439] IPv6: wlan0: IPv6 duplicate address 2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected! and my wlan0 gets no public IPv6 address. Problem goes away with sudo sysctl net.ipv6.conf.wlan0.accept_dad=0 Some analysis would be nice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120617 Title: No IPv6 and IPv6 duplicate address with IPv6 privacy extensions on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1120617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074957] Re: improper value display in net-tools statistics.c
It is also solved in more recent version of netstat / net-tools, for example the git version. See below. So why not upgrade to a more recent net-tools in Ubuntu? Can the maintainers take care of that? Git-version: sander@HPtje:~/git/net-tools$ ./netstat -s | grep -i octet InOctets: 8916276097 OutOctets: 1457306418 InMcastOctets: 34823 OutMcastOctets: 33223 InBcastOctets: 656 sander@HPtje:~/git/net-tools$ sander@HPtje:~/git/net-tools$ ./netstat --version net-tools 2.10-alpha Fred Baumgarten, Alan Cox, Bernd Eckenfels, Phil Blundell, Tuan Hoang, Brian Micek and others +NEW_ADDRT +RTF_IRTT +RTF_REJECT +FW_MASQUERADE +I18N AF: (inet) +UNIX +INET +INET6 +IPX +AX25 +NETROM +X25 +ATALK +ECONET +ROSE -BLUETOOTH HW: +ETHER +ARC +SLIP +PPP +TUNNEL -TR +AX25 +NETROM +X25 +FR +ROSE +ASH +SIT +FDDI +HIPPI +HDLC/LAPB +EUI64 sander@HPtje:~/git/net-tools$ In Ubuntu's version of netstat, there is the 31-bit overflow error: sander@HPtje:~$ netstat -s | grep -i octet InOctets: -1 OutOctets: 1456778102 InMcastOctets: 34396 OutMcastOctets: 32852 InBcastOctets: 656 sander@HPtje:~$ sander@HPtje:~$ netstat --version net-tools 1.60 netstat 1.42 (2001-04-15) Fred Baumgarten, Alan Cox, Bernd Eckenfels, Phil Blundell, Tuan Hoang and others +NEW_ADDRT +RTF_IRTT +RTF_REJECT +FW_MASQUERADE +I18N AF: (inet) +UNIX +INET +INET6 +IPX +AX25 +NETROM +X25 +ATALK +ECONET +ROSE HW: +ETHER +ARC +SLIP +PPP +TUNNEL -TR +AX25 +NETROM +X25 +FR +ROSE +ASH +SIT +FDDI +HIPPI +HDLC/LAPB +EUI64 sander@HPtje:~$ sander@HPtje:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Saucy Salamander (development branch) Release:13.10 Codename: saucy sander@HPtje:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074957 Title: improper value display in net-tools statistics.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1074957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227267] [NEW] virtualbox-dkms 4.1.12-dfsg-2ubuntu0.3: virtualbox kernel module failed to build
Public bug reported: problem during install of virtualbox ProblemType: Package DistroRelease: Ubuntu 12.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.3 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic i686 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 DKMSKernelVersion: 3.8.0-30-generic Date: Wed Sep 18 19:38:26 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) MarkForUpload: True PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.3 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.3: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227267 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.3: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1227267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219498] Re: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
Results from 12.04.3: I kept the lid open with no power cord inserted. So the battery went empty. After putting in the power cord and powering up 12.04.3 ... NO crash report. So that's better than with 13.10 that always report a crash message. you want/are hibernating when you close the lid in Precise? I don't dare to answer that question as I don't know the subtle differences between hibernate/sleep/S1/S2/S3/S4/S5/etc/etc. But 12.04.3 shows the behaviour I want: close lid - laptops goes to sleep with very little power consumption, open lid within a few days - laptop wakes up and starts where it left. On 13.04 that does not work: opening the lid after a few hours results in an emptied battery, and then a crash report after restarting. Both is on the same hardware, with everything on default. Both installs are fresh installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219498 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219498] Re: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
Thank you for your reply! I did the BIOS upgrade. I'll force an empty battery occurence, and check what Ubuntu says upon boot afterwards. sander@HPtje:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 68SRR Ver. F.41 05/22/2013 sander@HPtje:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219498 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219498] Re: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
Update: Still happens with that BIOS. [Hewlett-Packard HP ProBook 4530s] suspend/resume failure sander@HPtje:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 68SRR Ver. F.41 05/22/2013 sander@HPtje:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219498 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219498] Re: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
I'm not sure, but that could very well be. Does that change the case? Should I just click on ignore? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219498 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219498] Re: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
OK: I just installed 12.04.3 (32-bit, not 64-bit, if that matters) on the same machine. Fully updated. I'll force the empty-battery and see what happens afterwards. sander@sander12043:~$ uname -a Linux sander12043 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 15:31:16 UTC 2013 i686 i686 i386 GNU/Linux sander@sander12043:~$ sander@sander12043:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 68SRR Ver. F.41 05/22/2013 sander@sander12043:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219498 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219498] Re: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
An interesting result: With 13.10, when I close the laptop lid and remove the power cable, after one night the battery will be empty and upon a fresh, powered boot I will get the crash reported here. With 12.04.3, with the closed lid removed power cable, after one night the laptop could just start up on it's own battery that was still 100% full. IMHO this is behaviour as expected So: two problems (battery going empty and crash-report-after-boot), or one combined problem? I will now force an empty battery on 12.04.3 by keeping the lid open while the laptop is unpowered -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219498 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219498] [NEW] [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
Public bug reported: The usual crash after a fresh boot after the battery went empty. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1804 F pulseaudio Date: Sat Aug 31 18:55:52 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=8347ea18-a02a-451a-a889-44f76dfe095b InstallationDate: Installed on 2013-08-09 (22 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130809) InterpreterPath: /usr/bin/python3.3 MachineType: Hewlett-Packard HP ProBook 4530s MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=4751d5cf-0d0a-4d15-aa76-3859947c3f7a ro persistent quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/12/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.40 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.24 dmi.chassis.asset.tag: CNU1290ZYV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.40:bd03/12/2013:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.24:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume saucy suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219498 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211391] [NEW] [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
Public bug reported: Just started Ubuntu 13.10 and got this error. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1740 F pulseaudio Date: Mon Aug 12 18:06:20 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=8347ea18-a02a-451a-a889-44f76dfe095b InstallationDate: Installed on 2013-08-09 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130809) InterpreterPath: /usr/bin/python3.3 MachineType: Hewlett-Packard HP ProBook 4530s MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=4751d5cf-0d0a-4d15-aa76-3859947c3f7a ro persistent quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/12/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.40 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.24 dmi.chassis.asset.tag: CNU1290ZYV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.40:bd03/12/2013:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.24:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume saucy suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211391 Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1211391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155299] Re: [SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540] suspend/resume failure
I still get apportcheckresume crash reports on my fully updated system. $ uname -a Linux R540 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux So ... not solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155299 Title: [SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1155299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 374101] Re: Brasero hangs at Normalizing tracks
Yes, I can confirm: happens for me on fully updated Ubuntu 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/374101 Title: Brasero hangs at Normalizing tracks To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/374101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173527] Re: make the i386 *buntu version check for UEFI
Seems to be related to https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/102 , which says: /quote CONCLUSION: - grub-efi 32bits always creates invalid entries. - Installing Ubuntu32 bits on an EFI system should be blocked by Ubiquity (the Ubuntu installer). In this case, Ubiquity should ask the user to install Ubuntu64 instead. /unquote -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173527 Title: make the i386 *buntu version check for UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875758] Re: cannot create bootable pendrive for Ubuntu 11.10 i386
Also happens on 13.04 daily build, with dmesg saying: usb-creator-gtk[411]: segfault at 4 ip 7fb5e229ed80 sp 7fff90737378 error 6 in libdbus-1.so.3.7.2[7fb5e227a000+43000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875758 Title: cannot create bootable pendrive for Ubuntu 11.10 i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/875758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120617] Re: No IPv6 and IPv6 duplicate address with IPv6 privacy extensions on
Thanks to further analysis of Joost, the problem seems to be in the Zyxel firmware, not in Ubunt / Linux: problem occurs after changing the default SSID name to something else. See https://forum.telfort.nl /pilots-feedback-273/ipv6-p-2812hnu-f1-wifi-dad-33361/ (warning: Dutch) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120617 Title: No IPv6 and IPv6 duplicate address with IPv6 privacy extensions on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1120617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159902] [NEW] [SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540] suspend/resume failure
Public bug reported: (I thought I had already reported this, but Launchpad doesn't find it?) Battery went empty. After plugging the power and starting up, this crash happens. ProblemType: KernelOops DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-14-generic 3.8.0-14.24 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 2366 F pulseaudio CRDA: country NL: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5330 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Mon Mar 25 18:02:52 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=56ea62f2-0b4c-4dc9-9f41-b3423fccfa31 InstallationDate: Installed on 2013-03-03 (22 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130301) InterpreterPath: /usr/bin/python3.3 Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1210:25f4 DigiTech MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic root=UUID=534812aa-a5c9-4a36-9fc2-ac1bcdfa2e90 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.8.0-14-generic N/A linux-backports-modules-3.8.0-14-generic N/A linux-firmware1.104 SourcePackage: linux Title: [SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 08JV.M029.20100621.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730/R540 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08JV.M029.20100621.hkk:bd06/21/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730/R540:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730/R540:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730/R540 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops raring resume suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159902 Title: [SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159854] Re: NameError: global name 'Chrome' is not defined
Easy to reproduce. See below: just one import in python. And see http://bugs.python.org/issue17541 sander@appelboor:~$ python Python 2.7.4rc1 (default, Mar 25 2013, 00:30:40) [GCC 4.7.2] on linux2 Type help, copyright, credits or license for more information. import webbrowser Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.7/webbrowser.py, line 505, in module register_X_browsers() File /usr/lib/python2.7/webbrowser.py, line 489, in register_X_browsers register(browser, None, Chrome(browser)) NameError: global name 'Chrome' is not defined ** Bug watch added: Python Roundup #17541 http://bugs.python.org/issue17541 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159854 Title: NameError: global name 'Chrome' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1159854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs