[Macmini5,1] Kernel Panic when using Magic Touchpad

[Gerrit Addiks]

Using an Apple Magic Touchpad from 13.04 upward is not possible because of a kernel panic. The Touchpad also works in 12.10, but i prefer LTS. In 13.04 the error is triggered randomly but quickly by dragging on the touchpad with two fingers.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
Uname: Linux 3.13.0-3-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
CurrentDmesg:

Date: Wed Jan 15 21:48:33 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-3-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00e6]
InstallationDate: Installed on 2014-01-15 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140115)
MachineType: Apple Inc. Macmini5,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-3-generic root=UUID=384b5ac6-745f-45e0-a93c-f3d7e045ab6a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM51.88Z.0077.B10.1201241549
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-8ED6AF5B48C039E1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini5,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-8ED6AF5B48C039E1
dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
dmi.product.name: Macmini5,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.50-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1
xserver.bootTime: Wed Jan 15 21:46:51 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 219
 vendor ACR
xserver.version: 2:1.14.5-1ubuntu2

[penalvch (penalvch)]

Gerrit Addiks, thank you for reporting this bug and helping make Ubuntu better. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc8

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Gerrit Addiks (addiks)]

I now have installed the mainline kernel (*) and the problem persists. I again have taken a photo of the kernel-panic and attached it.

(*) = linux-image-3.13.0-031300rc8-generic_3.13.0-031300rc8.201401120535_amd64

[Gerrit Addiks (addiks)]

Should i really set the status to confirmed like you said? The description of that status suggests that it may only be set if the problem is confirmed by someone else than the author (me).

[penalvch (penalvch)]

Gerrit Addiks, thank you for providing the requested information. The next step is to fully commit bisect from Quantal to Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Gerrit Addiks (addiks)]

Just a short update: I have been testing mainline kernel-versions for the past week and it strongly looks like this kernel-panic has been introduced in version '3.11.0-RC1'. I will start the git-bisect of the kernel based on that information tomorrow or at the weekend.

[Gerrit Addiks (addiks)]

b1a1442a23776756b254b69786848a94d92445ba is the first bad commit
commit b1a1442a23776756b254b69786848a94d92445ba
Author: Jiri Kosina <email address hidden>
Date: Mon Jun 3 11:27:48 2013 +0200

    HID: core: fix reporting of raw events

    hdrw->raw event can return three different return value types:

    - ret < 0 indicates that the hdrv driver found an error while parsing
    - ret == 0 indicates no error has been encountered, and the driver has
               processed the report
    - ret > 0 indicates that there was no parsing error, and the driver hasn't
      processed the event.

    Calling hid_report_raw_event() has to be called appropriately so that it
    reflects what has been done by ->raw_event() callback, otherwise we might
    updates of the in-kernel structure are lost upon arrival of the report, which
    is wrong.

    Reported-and-tested-by: Srinivas Pandruvada <email address hidden>
    Reported-and-tested-by: Daniel Leung <email address hidden>
    Signed-off-by: Jiri Kosina <email address hidden>

:040000 040000 b61567a56058c05fb38864f834625b7910655476 7820cb9b91fb4d848a04b805d28da05c3ac8513b M drivers

[Gerrit Addiks (addiks)]

I can also report that this is not limited to Apple computers. I have reproduced this kernel-panic on another computer (Dell midi-tower) using another Apple-Magic-Touchpad. So i think the prefix "[Macmini5,1]" is wrong.

[penalvch (penalvch)]

Gerrit Addiks, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[Gerrit Addiks (addiks)]

Short Update:

I have reported the issue (*) and got a response (**) suggesting a patch (***). That patch seems to fix the problem for me after a very short test. I however had not yet enough time to securely confirm that. I will continue to use the patched kernel for a few days and see if the panic occours or not.

(*) = http://www.spinics.net/lists/linux-input/msg29411.html
(**) = http://www.spinics.net/lists/linux-input/msg29420.html
(***) = http://www.spinics.net/lists/linux-bluetooth/msg41725.html

[Gerrit Addiks (addiks)]

Update #2:

The patch mentioned above solved the problem for me. The patch was applied to the kernel in v3.14-RC4. I am now using that kernel with 14.04 for some weeks without any trouble. From my point of view, this can be closed. I just hope 14.04 gets released with at least v3.14 so i dont need to use a custom kernel after release.