[bcm5974] annoying random freezes

Bug #817979 reported by Nyan Cat
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

--

Revision history for this message
Brian Murray (brian-murray) wrote :

Sounds like a kernel issue.

affects: ubuntu-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 817979

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Nyan Cat (nyancat)
tags: added: apport-collected oneiric unity-2d
description: updated
Revision history for this message
Alex Murray (alexmurray) wrote :

Have just noticed this too after I installed Oneiric Beta 1 last night - MacBook Pro 5,1 (bcm5974)

Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

The workaround described above does not work for me (Macbook Pro 6,2).
But I noticed that by unloading and loading the kernel module it works again

Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

It just happened and this is what X log reports (/var/log/Xorg.0.log)

[ 885.137] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 885.137]
Backtrace:
[ 885.138] 0: /usr/bin/X (xorg_backtrace+0x37) [0x80a66a7]
[ 885.138] 1: /usr/bin/X (mieqEnqueue+0x1d1) [0x80a0661]
[ 885.138] 2: /usr/bin/X (xf86PostTouchEvent+0x94) [0x80c8e74]
[ 885.138] 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb4982000+0xacd0) [0xb498ccd0]
[ 885.138] 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb4982000+0xae86) [0xb498ce86]
[ 885.138] 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb4982000+0xb418) [0xb498d418]
[ 885.138] 6: /usr/lib/libutouch-grail.so.1 (0xb4970000+0x4150) [0xb4974150]
[ 885.138] 7: /usr/lib/libutouch-grail.so.1 (grail_pull+0xce) [0xb497469e]
[ 885.138] 8: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb4982000+0xb211) [0xb498d211]
[ 885.138] 9: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb4982000+0x6c4f) [0xb4988c4f]
[ 885.138] 10: /usr/bin/X (0x8048000+0x6cb31) [0x80b4b31]
[ 885.138] 11: /usr/bin/X (0x8048000+0x12d292) [0x8175292]
[ 885.138] 12: (vdso) (__kernel_sigreturn+0x0) [0xb7733400]
[ 885.138] 13: (vdso) (__kernel_vsyscall+0x10) [0xb7733424]
[ 885.138] 14: /lib/i386-linux-gnu/libc.so.6 (__select+0x2d) [0xb74a7e9d]
[ 885.138] 15: /usr/bin/X (WaitForSomething+0x18c) [0x80a3f3c]
[ 885.138] 16: /usr/bin/X (0x8048000+0x29ed2) [0x8071ed2]
[ 885.138] 17: /usr/bin/X (0x8048000+0x1c70c) [0x806470c]
[ 885.138] 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb73f6113]
[ 885.138] 19: /usr/bin/X (0x8048000+0x1ca21) [0x8064a21]

Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

This bug also affects me and many other Macbook owners. Is there something we can do to help you fixing it? It's quite annoying.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.19)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.19
Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

I confirm the bug is still present with the latest kernel available for Oneiric

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

It seems that the bug disappeared for me in 11.10 final release (MBP 6,2).
Is it working for you people?

Revision history for this message
Tomodachi (tomodachi) wrote :

nope, its still happening. I have verified this with three different Macbooks,
my own MBp 15" 5.1 in efi mode along with two other 13" Macbook in efi

Revision history for this message
Brian Teague (bteague) wrote :

I'm seeing this on a Macbook Air 3,2 as well (Oneiric up to date, including -proposed) in BIOS-emulation mode. Interestingly, the pointer freezes but multitouch gestures still work - ie, two-finger scrolling, three-finger window-movements, etc. Removing and reinserting the bcm5974 module fixes the problem.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tomodachi (tomodachi) wrote :

This is a problem , but I don't believe its because of the kernel module.
I was playing around last time this happened and noticed that

synclient |grep TouchpadOff
gives me
TouchpadOff = 1

enabling the touchpad manually made my mouse start working again.

in the mouse properties applet there is a checkbox "disable touchpad while typing"
i believe that it sets the touchpadoff = 1
when one is typing, and enabled the touchpad once one stops typing.
Enabling it again apparently fails sometimes. I've unchecked the box.
And I no longer get this problem, could someone else verify this as well?

We need to move this bug to the correct package. Question is , which is it?

Revision history for this message
Tomodachi (tomodachi) wrote :

Krsysztof: If that is the case, then then the bug has been reintroduced. And this i evidence of a regression.

  I always keep my computer up to date. And enabling "disable touchpad while typing" caused the same issue for me today.

Revision history for this message
Tomodachi (tomodachi) wrote :

this is more "specific" than linux, and according to my tests closer to where the problem lies

affects: linux (Ubuntu) → xserver-xorg-input-synaptics (Ubuntu)
Nyan Cat (nyancat)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.