On the non-debug kernel the computer hangs, that is, completely unresponsive. I have to reset the computer. On the debug kernel, I didn't let the system run too long before issuing shutdown -r. To reproduce, run bluetoothctl and go through the steps to power up, run the agent, and connect to the device. This starts to happen as soon as connect is issued. Linux localhost.localdomain 3.12.6-300.fc20.x86_64+debug #1 SMP Mon Dec 23 16:30:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux BOOT_IMAGE=/vmlinuz-3.12.6-300.fc20.x86_64+debug root=/dev/mapper/fedora-root ro fsck.mode=force nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off LANG=en_US.UTF-8 Jan 08 08:48:05 localhost.localdomain systemd[1]: Started Stop Read-Ahead Data Collection. Jan 08 08:49:45 localhost.localdomain kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Jan 08 08:49:45 localhost.localdomain kernel: Bluetooth: HIDP socket layer initialized Jan 08 08:49:46 localhost.localdomain systemd[1]: Reached target Bluetooth. Jan 08 08:49:46 localhost.localdomain kernel: magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 Jan 08 08:49:46 localhost.localdomain kernel: input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/bluetooth/hci0/hci0:42/input16 Jan 08 08:49:46 localhost.localdomain kernel: magicmouse 0005:05AC:030E.0007: input,hidraw6: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 00:15:83:3d:0a:57 Jan 08 08:49:47 localhost.localdomain upowerd[1073]: (upowerd:1073): UPower-Linux-WARNING **: no valid voltage value found for device /sys/devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/bluetooth/hci0/hci0:42/0005:05AC:030E.0007/power_supply/hid-7c:c3:a1:4a:69:ad-battery, assuming 10V Jan 08 08:49:54 localhost.localdomain kernel: ============================================================================= Jan 08 08:49:54 localhost.localdomain kernel: BUG kmalloc-2048 (Tainted: PF IO): Redzone overwritten Jan 08 08:49:54 localhost.localdomain kernel: ----------------------------------------------------------------------------- Jan 08 08:49:54 localhost.localdomain kernel: INFO: 0xffff8805a4ca0800-0xffff8805a4ca0807. First byte 0x0 instead of 0xcc Jan 08 08:49:54 localhost.localdomain kernel: INFO: Slab 0xffffea0016932800 objects=13 used=12 fp=0xffff8805a4ca0948 flags=0x5ff00000004081 Jan 08 08:49:54 localhost.localdomain kernel: INFO: Object 0xffff8805a4ca0000 @offset=0 fp=0x (null) Jan 08 08:49:54 localhost.localdomain kernel: Object ffff8805a4ca0000: 6b 6b 6b 6b 6b 6b 6b 6b 2a 20 12 00 0e 00 41 00 kkkkkkkk* ....A. Jan 08 08:49:54 localhost.localdomain kernel: Object ffff8805a4ca0010: a1 28 2c 73 00 e0 39 4c fc 27 4f 45 80 35 00 00 .(,s..9L.'OE.5.. Jan 08 08:49:54 localhost.localdomain kernel: Object ffff8805a4ca0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jan 08 08:49:54 localhost.localdomain kernel: Object ffff8805a4ca0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jan 08 08:49:54 localhost.localdomain kernel: Object ffff8805a4ca0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jan 08 08:49:54 localhost.localdomain kernel: Object ffff8805a4ca0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Created attachment 847282 [details] outout of journalctl -f while reproducing
Can you recreate this without the proprietary driver loaded?
If you're talking about the nvidia driver, I will try after work this week.
Likely duplicate: https://bugzilla.redhat.com/show_bug.cgi?id=1027465
I did reproduce this without the nvidia driver loaded. Behaviour was indistinguishable from the previous case.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.