Apple Wireless Trackpad causes kernel oops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Saucy |
Fix Released
|
High
|
Unassigned |
Bug Description
This seems to happen whenever I connect my Apple Wireless Trackpad and use it. The system hardlocks and I have to force a reboot.
ProblemType: KernelOopsDistr
Package: linux-image-
ProcVersionSign
Uname: Linux 3.11.0-4-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
Date: Wed Aug 28 10:16:41 2013
EcryptfsInUse: Yes
Failure: oops
HibernationDevice: RESUME=
InstallationDate: Installed on 2013-01-16 (224 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
MachineType: System manufacturer System Product Name
MarkForUpload: True
OopsText:
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: noSourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-07-15 (43 days ago)
dmi.bios.date: 07/27/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1106
dmi.board.
dmi.board.name: P8Z77-V LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Brian Murray (brian-murray) wrote : | #1 |
- AlsaInfo.txt Edit (51.4 KiB, text/plain; charset="utf-8")
- BootDmesg.txt Edit (66.1 KiB, text/plain; charset="utf-8")
- CRDA.txt Edit (291 bytes, text/plain; charset="utf-8")
- CurrentDmesg.txt Edit (1.7 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")
- IwConfig.txt Edit (138 bytes, text/plain; charset="utf-8")
- Lspci.txt Edit (10.9 KiB, text/plain; charset="utf-8")
- Lsusb.txt Edit (752 bytes, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (3.7 KiB, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (6.0 KiB, text/plain; charset="utf-8")
- PulseList.txt Edit (23.2 KiB, text/plain; charset="utf-8")
- UdevDb.txt Edit (186.7 KiB, text/plain; charset="utf-8")
- UdevLog.txt Edit (389.8 KiB, text/plain; charset="utf-8")
- WifiSyslog.txt Edit (594.9 KiB, text/plain; charset="utf-8")
Brian Murray (brian-murray) wrote : | #2 |
Brian Murray (brian-murray) wrote : | #3 |
description: | updated |
Brad Figg (brad-figg) wrote : Status changed to Confirmed | #4 |
This change was made by a bot.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Joseph Salisbury (jsalisbury) wrote : | #5 |
Appears to be a duplicate of bug 1214931
Changed in linux (Ubuntu): | |
importance: | Medium → High |
Joseph Salisbury (jsalisbury) wrote : | #6 |
If you have a chance, can you test the v3.11-rc4 kernel and confirm this bug goes away? The 3.11-rc4 kernel is available at:
http://
Changed in linux (Ubuntu): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Brian Murray (brian-murray) wrote : | #7 |
Running that kernel I received a warning and then an Oops.
Aug 28 11:32:58 impulse kernel: [ 610.766544] ------------[ cut here ]------------
Aug 28 11:32:58 impulse kernel: [ 610.766554] WARNING: CPU: 1 PID: 3487 at /home/apw/
Aug 28 11:32:58 impulse kernel: [ 610.766555] Modules linked in: rpcsec_gss_krb5 nfsv4 nfsv3 hid_magicmouse hidp xt_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp ip6table_filter ip6_tables iptable_filter ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables bridge stp llc autofs4 dm_crypt snd_hda_codec_hdmi x86_pkg_
Aug 28 11:32:58 impulse kernel: eric usbhid hid nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper ahci r8169 libahci drm mii video wmi
Aug 28 11:32:58 impulse kernel: [ 610.766625] CPU: 1 PID: 3487 Comm: gnome-control-c Not tainted 3.11.0-
Aug 28 11:32:58 impulse kernel: [ 610.766626] Hardware name: System manufacturer System Product Name/P8Z77-V LX, BIOS 1106 07/27/2012
Aug 28 11:32:58 impulse kernel: [ 610.766628] 000000000000002f ffff8803e0201ca8 ffffffff8171e4eb 0000000000000007
Aug 28 11:32:58 impulse kernel: [ 610.766631] 0000000000000000 ffff8803e0201ce8 ffffffff8106532c ffff88040e001700
Aug 28 11:32:58 impulse kernel: [ 610.766633] ffff880404d85800 ffff8804060c0b40 0000000000000282 ffff88040626e8a0
Aug 28 11:32:58 impulse kernel: [ 610.766636] Call Trace:
Aug 28 11:32:58 impulse kernel: [ 610.766641] [<ffffffff8171e
Aug 28 11:32:58 impulse kernel: [ 610.766645] [<ffffffff81065
Aug 28 11:32:58 impulse kernel: [ 610.766648] [<ffffffff81065
Aug 28 11:32:58 impulse kernel: [ 610.766651] [<ffffffff81368
Aug 28 11:32:58 impulse kernel: [ 610.766656] [<ffffffff8160d
Aug 28 11:32:58 impulse kernel: [ 610.766659] [<ffffffff81482
Aug 28 11:32:58 impulse kernel: [ 610.766662] [<ffffffff8152b
Aug 28 11:32:58 impulse kernel: [ 610.766665] [<ffffffff81536
Aug 28 11:32:58 impulse kernel: [ 610.766668] [<ffffffff81537
Aug 28 11:32:58 impulse kernel: [ 610.766672] [<ffffffff81199
Aug 28 11:32:58 impulse kernel: [ 610.766687] [<ffffffffa051d
Aug 28 11...
Joseph Salisbury (jsalisbury) wrote : | #8 |
Thanks for testing rc4, Brian. That Oops is USB related, but it looks different than the original Oops and the Oops in bug 1214931. It could be another bug that was in rc4, but is now fixed.
In bug 1214931, having the bluetooth trackpad connected caused the system to freeze, in addition to the Oops. Are you also seeing a system freeze when running the latest Saucy kernel? If so, did you see a system freeze when running 3.11-rc4?
Brian Murray (brian-murray) wrote : | #9 |
As I mentioned in the descripton, having the apple trackpad connected caused the system to lock up / freeze and I had to force a reboot.
I am also seeing a system freeze running kernel suggested in comment #6.
Brian Murray (brian-murray) wrote : | #10 |
This crash was with the kernel from comment #6 and caused the system to freeze.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Date: Wed Aug 28 14:26:12 2013
Failure: oops
OopsText:
BUG: unable to handle kernel NULL pointer dereference at 00000000000003b0
IP: [<ffffffff81578
PGD 0
Oops: 0000 [#1] SMP
Modules linked in: hid_magicmouse hidp hid cuse dm_crypt parport_pc ppdev autofs4 nfsd auth_rpcgss nfs_acl rfcomm nfs bnep lockd sunrpc fscache binfmt_misc intel_powerclamp coretemp kvm_intel kvm crc32_pclmul arc4 ghash_clmulni_intel iwldvm aesni_intel mac80211 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_codec_hdmi joydev snd_hda_
CPU: 1 PID: 1277 Comm: Xorg Not tainted 3.11.0-
Hardware name: LENOVO 0831CTO/0831CTO, BIOS 6QET53WW (1.23 ) 09/15/2010
task: ffff88006395ddc0 ti: ffff880060d0c000 task.ti: ffff880060d0c000
RIP: 0010:[<
RSP: 0018:ffff880060
RAX: 0000000000000000 RBX: ffff880035921800 RCX: 0000000000000050
RDX: 0000000000000001 RSI: ffff880060d0dab8 RDI: ffff880060e39100
RBP: ffff880060d0d9b8 R08: ffff880060e39138 R09: ffff880060d0ddb8
R10: 0000000000000000 R11: 0000000000003246 R12: 0000000000000000
R13: 0000000000002000 R14: 00080000001fe000 R15: ffff880060e39100
FS: 00007fead993698
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000000003b0 CR3: 0000000060ccb000 CR4: 00000000000007e0
Stack:
0000000000000040 000000000000000d ffff880060d0dd68 ffffffff811c572e
0000000000000000 0000000000000000 0000000000000304 0000000000000001
ffff880060d0dfd8 0000000000000000 0000000000000000 ffff880060d0df28
Call Trace:
[<ffffffff811
[<ffffffff811
[<ffffffff811
[<ffffffff811
[<ffffffff811
[<ffffffff811
[<ffffffff811
[<ffffffff811
[<ffffffff811
[<ffffffff810
[<ffffffff811
[<ffffffff810
[<ffffffff810
[<ffffffff811
[<ffffffff810
[<ffffffff811
[<ffffffff817
Code: 48 89 e5 48 83 ec 10 48 85 f6 48 89 5d f0 48 8b 9f a8 00 00 00 4c 89 ...
Joseph Salisbury (jsalisbury) wrote : | #11 |
Thanks for testing, Brian.
Can you test the following two kernels to see if the bug can be reproduced:
v3.10 final: http://
v3.11-rc1: http://
I can perform a kernel bisect to identify the commit that introduced this. We first need to identify the last kernel version that did not have this bug and the first kernel version that does exhibit the bug.
Brian Murray (brian-murray) wrote : | #12 |
v3.10-saucy seems to be fine after a similar period of testing that caused that crash. I'll do v3.11-r1-saucy soon.
tags: | added: bios-outdated-2203 regression-potential |
Joseph Salisbury (jsalisbury) wrote : | #13 |
Thanks again for testing, Brian. If rc1 does not have the bug, we should test rc2, then rc3, etc until we find the first kernel version that exhibits the bug.
Brian Murray (brian-murray) wrote : | #14 |
Testing with 3.11.0-
Joseph Salisbury (jsalisbury) wrote : | #15 |
Thanks, Brian. I took a look at the git log between 3.10 and 3.11-rc1 and there were quite a bit of changes to Bluetooth:
b8f4e068004859e
502f769662978a2
673e1dd7ed7701c
0a804654af62dfe
034cbea0931433c
12602d0cc005354
8892d8beb37cb4e
b0434345f2a7330
917eedc56c65ba9
3fd319b830247a3
1183fdcad424950
82f4785ca7b8d04
0e05bba6f6f8c2d
4c87eaab01df271
0d8cc935e01c0fd
41dc2bd6d13bfcc
fef5234a791507a
7c3077207c705d0
1f9b9a5dc5bb8ee
44f3b0fbaa9bfa7
0cc59a72c723979
5ee9891dd8a63df
af1c01349ecc2b8
60bac184c9c7df2
97f57c0b14ad2ef
d8729922b474eab
9f22398ce4baf81
141d57065afd119
f224ca5fc207a99
073d1cf35fe45d8
c5623556fc61804
6ea81c415574acb
178c059e7640aa8
...
Joseph Salisbury (jsalisbury) wrote : | #16 |
I started a bisect between v3.10 final and v3.11-rc1. The bisect will required about 10 test kernels.
I built the first kernel, which is up to commit:
1286da8bc009cb2
The test kernel can be downloaded from:
http://
Can you test this kernel and see if it exhibits the bug? I'll then update the bisect and built another test kernel based on your results.
Brian Murray (brian-murray) wrote : | #17 |
This kernel seems to be fine: 3.10.0-
Joseph Salisbury (jsalisbury) wrote : | #18 |
I built the next kernel, which is up to commit:
1b375dc30710180
The test kernel can be downloaded from:
http://
Can you test this kernel and see if it exhibits the bug? I'll then update the bisect and built another test kernel based on your results.
Brian Murray (brian-murray) wrote : | #19 |
Okay, that one exhibited the bug.
Brian Murray (brian-murray) wrote : | #20 |
That one being the one from comment #18.
Joseph Salisbury (jsalisbury) wrote : | #21 |
I built the next kernel, which is up to commit:
899dd388853071f
The test kernel can be downloaded from:
http://
Can you test this kernel and see if it exhibits the bug? I'll then update the bisect and built another test kernel based on your results.
Brian Murray (brian-murray) wrote : | #22 |
The one from comment #21 also exhibits the crash. Although it may be worth noting that I don't actually get to see the Oops in /var/log/kern.log for every crash.
Joseph Salisbury (jsalisbury) wrote : | #23 |
I updated the bisect and built the next kernel, which is up to commit:
f5b63ac0f77ecab
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #24 |
The kernel from comment #23 also exhibits the crash.
Joseph Salisbury (jsalisbury) wrote : | #25 |
I updated the bisect and built the next kernel, which is up to commit:
3366dd9fa887ebb
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #26 |
The latest kernel also causes the crash.
Joseph Salisbury (jsalisbury) wrote : | #27 |
I updated the bisect and built the next kernel, which is up to commit:
c039e3a8ddd5213
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #28 |
The kernel from comment #27 is running without a crash so far using the same type of tests.
Joseph Salisbury (jsalisbury) wrote : | #29 |
I updated the bisect and built the next kernel, which is up to commit:
e61aca5158a8493
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #30 |
The kernel from comment #29 is also running without a crash.
Joseph Salisbury (jsalisbury) wrote : | #31 |
I updated the bisect and built the next kernel, which is up to commit:
b8e0fe31a7c8623
The test kernel can be downloaded from:
http://
The bisect should determine the bad commit in about 4 or 5 test kernels.
Brian Murray (brian-murray) wrote : | #32 |
This kernel is not crashing:
Linux blacklightning 3.9.0-030900-
Joseph Salisbury (jsalisbury) wrote : | #33 |
I updated the bisect and built the next kernel, which is up to commit:
08ec2dcc3527a20
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #34 |
The kernel from above did crash.
Sep 9 13:29:36 localhost kernel: [ 0.000000] Linux version 3.10.0-
Joseph Salisbury (jsalisbury) wrote : | #35 |
I updated the bisect and built the next kernel, which is up to commit:
db58316892a5e90
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #36 |
The kernel from above is not crashing:
[ 3:57PM ] [ bdmurray@
$ uname -a
Linux blacklightning 3.10.0-
Joseph Salisbury (jsalisbury) wrote : | #37 |
I updated the bisect and built the next kernel, which is up to commit:
a688393bd3fb276
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #38 |
The next test kernel crashed:
Sep 10 10:02:23 localhost kernel: [ 0.000000] Linux version 3.9.0-030900-
Joseph Salisbury (jsalisbury) wrote : | #39 |
I updated the bisect and built the next kernel, which is up to commit:
b1a1442a2377675
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #40 |
The next kernel experienced an Oops but did not lock up, and the oops looks unrelated afaict.
OopsText:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000119
IP: [<ffffffff8135f
PGD 0
Oops: 0002 [#1] SMP
Modules linked in: hid_magicmouse hidp hid cuse dm_crypt autofs4 rfcomm parport_pc bnep ppdev intel_powerclamp coretemp kvm_intel kvm nfsd auth_rpcgss crc32_pclmul ghash_clmulni_intel nfs_acl aesni_intel btusb aes_x86_64 lrw gf128mul nfs bluetooth snd_hda_codec_hdmi lockd glue_helper sunrpc ablk_helper arc4 cryptd snd_hda_
CPU: 3 PID: 3541 Comm: firefox Not tainted 3.9.0-030900-
Hardware name: LENOVO 0831CTO/0831CTO, BIOS 6QET53WW (1.23 ) 09/15/2010
task: ffff88004e145dc0 ti: ffff88001e180000 task.ti: ffff88001e180000
RIP: 0010:[<
RSP: 0018:ffff88001e
RAX: 0000000000000119 RBX: ffffffff81ad53f6 RCX: 0000000000000002
RDX: 0000000000000002 RSI: ffffffff81ad53f4 RDI: 0000000000000119
RBP: ffff88001e181d18 R08: 000000000000005d R09: ffff880076c08400
R10: 0000000000000001 R11: 0000000000000293 R12: ffff880036017800
R13: 0000000000000002 R14: 0000000000000002 R15: 0000000000000002
FS: 00007f7ffd34d74
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000119 CR3: 000000001e295000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Stack:
ffffffff814330f8 ffff880070e25680 0000000000000000 0000000000000002
ffff880072994800 00007f7ff6bb9000 ffff880072b23800 ffff880072b23400
000000000000000a 000000000000005d ffff880072dfb800 ffff88001e181d48
Call Trace:
[<ffffffff814
[<ffffffff814
[<ffffffff811
[<ffffffff814
[<ffffffff814
[<ffffffff814
[<ffffffff810
[<ffffffff814
[<ffffffff814
[<ffffffff814
[<ffffffff811
[<ffffffff811
[<ffffffff817
Code: 4e 48 83 c4 08 5b 5d c3 90 e8 fb fd ff ff eb e6 90 90 90 90 90 90 90 90 90 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 f3 48 a5 89 d1 <f3> a4 c3 20 4c 8b 06 4c 8b 4e 08 4c 8b 56 10 4c 8b 5e 18 48 8d
RIP [<ffffffff8135f
RSP <ffff88001e181cc0>
CR2: 0000...
41 comments hidden Loading more comments | view all 121 comments |
Brian Murray (brian-murray) wrote : | #82 |
Sep 20 08:36:27 localhost kernel: [ 0.000000] Linux version 3.11.0-7-generic (root@gomeisa) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu2) ) #14~lp1218004Co
That kernel crashed.
Joseph Salisbury (jsalisbury) wrote : | #83 |
Ok, so it sounds like both commits need to be reverted. I'll build that kernel and post it shortly.
Joseph Salisbury (jsalisbury) wrote : | #84 |
I created a test kernel with both commits reverted. Can you test the kernel and post back the results?
The test kernel can be downloaded from:
http://
Brian Murray (brian-murray) wrote : | #85 |
I tried it two times to be certain, but this kernel still crashes.
Linux blacklightning 3.11.0-7-generic #14~lp1218004Bo
Joseph Salisbury (jsalisbury) wrote : | #86 |
Thanks, Brian. I'll take a closer look at the bisect results to make sure everything is correct.
In the meantime, could you test the latest mainline kernel, which is v3.12-rc1:
http://
It's worth a shot to see if this is already fixed.
Brian Murray (brian-murray) wrote : | #87 |
You'd asked me via irc to test that kernel and it crashed when I tested it then (on the 17th).
Joseph Salisbury (jsalisbury) wrote : | #88 |
I marked commit b1a1442a2377675
I'll have a test kernel to post shortly.
Joseph Salisbury (jsalisbury) wrote : | #89 |
The test kernel up to commit b1a1442a2377675
http://
Can you see if this one exhibits the bug?
Brian Murray (brian-murray) wrote : | #90 |
Sep 23 10:40:02 localhost kernel: [ 0.000000] Linux version 3.9.0-030900-
That kernel also crashed.
Joseph Salisbury (jsalisbury) wrote : | #91 |
I created a test kernel with commit 4e713cd Reverted. This is a HID commit that affects bluetooth:
commit 4e713cdffba8d48
Author: David Herrmann <email address hidden>
Date: Thu May 23 13:10:25 2013 +0200
HID: Bluetooth: hidp: register HID devices async
Can you test this kernel, to see if it also exhibits the bug:
http://
The .deb file names are:
linux-image-
linux-image-
Brian Murray (brian-murray) wrote : | #92 |
That kernel also crashed.
Sep 23 14:51:49 localhost kernel: [ 0.000000] Linux version 3.11.0-8-generic (root@gomeisa) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu3) ) #15~lp1218004Co
Brian Murray (brian-murray) wrote : | #93 |
Joseph Salisbury (jsalisbury) wrote : | #94 |
I started a bisect of just the HID subsystem. The first kernel is built up to commit:
5b22b91ab666634
Can you test this kernel, and post back the results:
http://
Brian Murray (brian-murray) wrote : | #95 |
This kernel has not crashed.
Linux blacklightning 3.9.0-030900-
Joseph Salisbury (jsalisbury) wrote : | #96 |
The next kernel is built up to commit:
3685c18e17f1243
Can you test this kernel, and post back the results:
http://
Brian Murray (brian-murray) wrote : | #97 |
That kernel did crash.
Sep 24 18:09:35 localhost kernel: [ 4473.626297] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
Sep 24 18:09:35 localhost kernel: [ 4473.626376] IP: [<ffffffff815f6
Sep 24 18:09:35 localhost kernel: [ 4473.626434] PGD 6278e067 PUD 60c21067 PMD 0
Sep 24 18:09:35 localhost kernel: [ 4473.626474] Oops: 0002 [#1] SMP
Sep 24 18:09:35 localhost kernel: [ 4473.626506] Modules linked in: hid_magicmouse hidp hid dm_crypt cuse autofs4 snd_hda_codec_hdmi nfsd parport_pc snd_hda_
Sep 24 18:09:35 localhost kernel: [ 4473.627227] CPU: 2 PID: 1258 Comm: wpa_supplicant Not tainted 3.9.0-030900-
Sep 24 18:09:35 localhost kernel: [ 4473.627293] Hardware name: LENOVO 0831CTO/0831CTO, BIOS 6QET53WW (1.23 ) 09/15/2010
Sep 24 18:09:35 localhost kernel: [ 4473.627355] task: ffff8800633cc650 ti: ffff880060c3a000 task.ti: ffff880060c3a000
Sep 24 18:09:35 localhost kernel: [ 4473.627411] RIP: 0010:[<
Sep 24 18:09:35 localhost kernel: [ 4473.627476] RSP: 0018:ffff880060
Sep 24 18:09:35 localhost kernel: [ 4473.627519] RAX: 0000000000000049 RBX: ffff8800625b6000 RCX: 0000000000000000
Sep 24 18:09:35 localhost kernel: [ 4473.627573] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff880036673b00
Sep 24 18:09:35 localhost kernel: [ 4473.627629] RBP: ffff880060c3b9a8 R08: ffff880060c3a000 R09: ffff8800364b4cd8
Sep 24 18:09:35 localhost kernel: [ 4473.627682] R10: 0000000000000001 R11: 0000000000000002 R12: 000000000000000b
Sep 24 18:09:35 localhost kernel: [ 4473.627735] R13: 0000000000000800 R14: 0000000000003e60 R15: ffff880036673b00
Sep 24 18:09:35 localhost kernel: [ 4473.627792] FS: 00007f7de0aa074
Sep 24 18:09:35 localhost kernel: [ 4473.627853] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Sep 24 18:09:35 localhost kernel: [ 4473.627900] CR2: 0000000000000008 CR3: 0000000060c66000 CR4: 00000000000007e0
Sep 24 18:09:35 localhost kernel: [ 4473.627954] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 24 18:09:35 localhost kernel: [ 4473.628007] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 24 18:09:35 localhost kernel: [ 4473.628062] Stack:
Sep 24 18:09:35 localhost kernel: [ 4473.628079] ffff880060c3b9b8 ffff8800625b6000 ffff880060c3b9d8 ffffffff816d6e1b
Sep 24 18:09:35 localhost kernel: [ 4473.6...
Joseph Salisbury (jsalisbury) wrote : | #98 |
The next kernel is built up to commit:
59e527866359ce6
Can you test this kernel, and post back the results:
http://
Brian Murray (brian-murray) wrote : | #99 |
Linux blacklightning 3.12.0-
That kernel has not crashed.
Joseph Salisbury (jsalisbury) wrote : | #100 |
That is great news. This is an interesting test result. That kernel is the mainline kernel with commit b1a1442a reverted. This last bisect indicated commit b1a1442a as the first bad commit. We tested a Saucy test kernel with this commit reverted and still hit the bug(comments #81 and #82).
This leads me to believe there is something specific to Saucy that needs to be pulled out as well as commit b1a1442a. Let me build another Saucy test kernel with commit b1a1442a reverted and see if the bug still exists. I'll also take a look at the Ubuntu changelogs to see what SAUCE patches have been applied.
Joseph Salisbury (jsalisbury) wrote : | #101 |
I built another Saucy test kernel with commit b1a1442 reverted.
Can you test this kernel, and post back the results:
http://
Brian Murray (brian-murray) wrote : | #102 |
Sep 25 13:29:41 localhost kernel: [ 0.000000] Linux version 3.11.0-8-generic (root@gomeisa) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu3) ) #15~lp1218004Co
Sep 25 13:29:41 localhost kernel: [ 0.000000] Command line: BOOT_IMAGE=
That kernel crashed.
Joseph Salisbury (jsalisbury) wrote : | #103 |
Just a quick summary where we are currently:
Revert of b1a1442 in upstream v3.12-rc2 resolves bug.
Revert of b1a1442 in Ubuntu Saucy does NOT resolve bug.
There are no Ubuntu specific changes to HID between 3.10 and 3.11-rc1.
The 3.12-rc2 kernel has the following additionl commits on hid-core.c:
cc6b54aa54bf40
331415ff16a121
I propose the following tests:
Revert of b1a1442 in 3.11.1 stable.
Revert of b1a1442 in Saucy with a cherry pick of cc6b54a
Revert of b1a1442 in Saucy with a cherry pick of 331415f
If needed: Revert of b1a1442 in Saucy with a cherry pick of cc6b54a AND 331415f
If I recall, you tested upstrem 3.12-rc2 and it did exhibit this bug. If that is the case, we will probably need a combination of a revert of b1a1442 and a cherry pick of one of the other two commits mentioned above. I'll relay all of this information upstream once we have all the details.
Joseph Salisbury (jsalisbury) wrote : | #104 |
I built the 3.11.1 stable kernel with commit b1a1442 reverted. Can you test this and see if it exhibits the bug:
http://
Brian Murray (brian-murray) wrote : | #105 |
Linux blacklightning 3.11.1-
That kernel has not crashed.
Joseph Salisbury (jsalisbury) wrote : | #106 |
That was unexpected. This would further indicate an Ubuntu specific SAUCE patch that is causing this, since Saucy has been rebased to upstream 3.11.1. Let me build one more Saucy test kernel from the Saucy master-next tree and see if the bug is fixed by only reverting b1a1442. If the bug still does exist, I'll have to pull off some of the SAUCE patches to see which one is causing this.
Joseph Salisbury (jsalisbury) wrote : | #107 |
I built the latest Saucy master-next kernel with commit b1a1442 reverted. Can you test this and see if it exhibits the bug:
http://
Joseph Salisbury (jsalisbury) wrote : | #108 |
I built a Saucy kernel with commit b1a1442 reverted and all of the bluetooth SAUCE patches added since the 3.10 kernel. Can you test this and see if it exhibits the bug:
Brian Murray (brian-murray) wrote : | #109 |
That kernel has not crashed.
Linux blacklightning 3.11.0-9-generic #16~lp1218004Co
Joseph Salisbury (jsalisbury) wrote : | #110 |
That is good news. That kernel had b1a1442 reverted and the following SAUCE patches reverted:
a769174299b34c4
ce63c1821f06be1
b9095bbf7cc8e3d
dbf239e56edcf61
68192976e743c8d
My guess is that it is commit 6819297 causing this issue. I'll build the next test kernel with commit b1a1442 reverted and only commit 6819297 reverted. If that kernel is good, then we found the two bad commits.
Joseph Salisbury (jsalisbury) wrote : | #111 |
I'd also like to ensure that both reverts are required. We know that reverting b1a1442 and the bluetooth broadcom patchram firmware patches fixes the bug. I also built a test kernel with only the bluetooth patches reverted. Can you give this a test to see if it exhibits the bug:
Brian Murray (brian-murray) wrote : | #112 |
That kernel crashed too:
OopsText:
BUG: unable to handle kernel paging request at ffff880062820000
IP: [<ffffffff81369
PGD 1fe5067 PUD 1fe8067 PMD 633f4063 PTE 8000000062820161
Oops: 0003 [#1] SMP
Modules linked in: hid_magicmouse hidp hid cuse dm_crypt autofs4 parport_pc ppdev rfcomm bnep binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache joydev arc4 iwldvm mac80211 intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_codec_hdmi snd_hda_
CPU: 2 PID: 2775 Comm: khidpd_05ac030e Not tainted 3.11.0-9-generic #16~lp1218004Bl
Hardware name: LENOVO 0831CTO/0831CTO, BIOS 6QET53WW (1.23 ) 09/15/2010
task: ffff88004b565dc0 ti: ffff8800133c4000 task.ti: ffff8800133c4000
RIP: 0010:[<
RSP: 0018:ffff880013
RAX: 0000000000000000 RBX: ffff88006281f011 RCX: 0000000000000002
RDX: 0000000000000004 RSI: 0000000000000000 RDI: ffff88006281fffe
RBP: ffff8800133c5da8 R08: 0000000000000001 R09: ffff88006281f01e
R10: 0000000000000000 R11: 0000000000014580 R12: 000000000000000d
R13: 000000000000000c R14: 0000000000000ff4 R15: 0000000000000001
FS: 000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffff880062820000 CR3: 0000000001c0e000 CR4: 00000000000007e0
Stack:
ffffffffa07dabe1 ffff8800607f4000 ffffffff8155be01 000000008155c809
0000000000000000 0000000000000001 ffff88004b504300 ffff88004b595000
ffff880000000001 ffff88006281f012 ffff880000000000 ffff88006174a000
Call Trace:
[<ffffffffa07
[<ffffffff815
[<ffffffffa07
[<ffffffffa07
[<ffffffff810
[<ffffffff810
[<ffffffffa07
[<ffffffff810
[<ffffffff810
[<ffffffff817
[<ffffffff810
Code: 1e 44 88 1f c3 90 90 90 90 90 90 90 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 66 66 66 90 66 66 66 90 66 66
RIP [<ffffffff81369
RSP <ffff8800133c5d20>
CR2: ffff880062820000
---[ end trace c3e149a55ccd53cb ]---
Joseph Salisbury (jsalisbury) wrote : | #113 |
I a test kernel just to confirm all of our findings. This is the latest beta Saucy kernel with only commit b1a1442 reverted. This kernel should exhibit the bug, since it has the bluetooth SAUCE patches. If it does exhibit this bug, I'll submit requests to have all the bad commits reverted.
Getting the commits reverted will only be a temporary fix. In parallel, I'll work with upstream to get a proper fix for the issue commit b1a1442 introduced. I'll also bring up the issue of the bluetooth patches with the patch author.
Can you test this kernel and post back:
http://
tags: | added: kernel-key |
Joseph Salisbury (jsalisbury) wrote : | #114 |
Can you test the kernel at http://
Thanks for all the help testing!
Brian Murray (brian-murray) wrote : | #115 |
This kernel has not crashed.
Linux blacklightning 3.11.0-9-generic #16~lp1218004La
Joseph Salisbury (jsalisbury) wrote : | #116 |
I submitted a request to have commit b1a1442 reverted in Saucy. I'll continue to work with upstream to see if there is an alternative to the revert.
tags: | removed: kernel-key |
Changed in linux (Ubuntu Saucy): | |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Saucy): | |
status: | In Progress → Fix Committed |
Huw Wilkins (huwshimi) wrote : | #117 |
This seems to be resolved for me with the latest kernel update (3.11.0-
Launchpad Janitor (janitor) wrote : | #118 |
This bug was fixed in the package linux - 3.11.0-12.18
---------------
linux (3.11.0-12.18) saucy; urgency=low
[ Andy Whitcroft ]
* [Packing] tools -- when tools are off they are off
* [config] tools -- linux-tools-common really is common
* [Packaging] tools -- make cpupower optional
* [Packaging] tools -- fix crosscompilation
* [config] tools -- enable cpupower
* SAUCE: storvsc -- host takes MAINTENANCE_IN commands badly elide them
- LP: #1234417
[ John Johansen ]
* SAUCE: apparmor: fix unix domain sockets to be mediated on connection
- LP: #1208988
* SAUCE: apparmor: allocate path lookup buffers during init
- LP: #1208988
* SAUCE: apparmor: fix memleak of the profile hash
- LP: #1235523
* SAUCE: apparmor: fix memleak of replacedby struct
- LP: #1235973
* SAUCE: apparmor: fix bad lock balance when introspecting policy
- LP: #1235977
[ Paolo Pisati ]
* [Config] arm: VIRTIO_
[ Rob Herring ]
* SAUCE: (no-up) net: calxedaxgmac: fix clearing of old filter addresses
- LP: #1235272
* SAUCE: (no-up) net: calxedaxgmac: add uc and mc filter addresses in
promiscuous mode
- LP: #1235272
* SAUCE: (no-up) net: calxedaxgmac: determine number of address filters
at runtime
- LP: #1235272
[ Tim Gardner ]
* [Config] CONFIG_ANDROID=n
- LP: #1235161
* [Config] CONFIG_L2TP_V3=y
- LP: #1235914
* Release tracker
- LP: #1236999
[ Upstream Kernel Changes ]
* Revert "HID: core: fix reporting of raw events"
- LP: #1218004
-- Andy Whitcroft <email address hidden> Fri, 04 Oct 2013 13:08:59 +0100
Changed in linux (Ubuntu Saucy): | |
status: | Fix Committed → Fix Released |
Joseph Salisbury (jsalisbury) wrote : | #119 |
Hi Brian,
Upstream has a patch that may fix this issue without a revert. Do you still have access to the hw to reproduce this bug? If so, do you think you can test a kernel to see if the patch from upstream does address the bug?
Baif (baifcc) wrote : | #120 |
I posted some comments here: https:/
Apple Trackpad indeed crashes kernel 3.12.0-
I have tried TRUSTY alpha1, either 3.12.0-6/3.12.0-7, both of them crashes with trackpad.
AND, I also test Apple MagicMouse, none of mentioned kernel crashes with either SAUCY nor TRUSTY.......
Brian Murray (brian-murray) wrote : | #121 |
I had some issues with trackpad and trusty kernels, but now with 3.13.0-24 there are no OOPSes.
Here is the oops which apport did not include:
Aug 28 09:53:03 impulse kernel: [ 676.261277] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 030E.0005: unknown main item tag 0x0 pci0000: 00/0000: 00:1a.0/ usb1/1- 1/1-1.6/ 1-1.6:1. 0/bluetooth/ hci0/hci0: 11/input15 030E.0005: input,hidraw4: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 00:0a:3a:7c:58:95 952>] evdev_poll+ 0x32/0x60 ipv4(F) nf_defrag_ipv4(F) nf_nat_ipv4(F) nf_nat(F) nf_conntrack(F) ip_tables(F) x_tables(F) bridge(F) stp(F) llc(F) autofs4(F) snd_hda_codec_hdmi x86_pkg_ temp_thermal intel_powerclamp coretemp kvm_intel(F) kvm(F) crc32_pclmul(F) ghash_clmulni_ intel(F) aesni_intel(F) aes_x86_64(F) lrw(F) gf128mul(F) glue_helper(F) ablk_helper(F) cryptd(F) parport_pc(F) ppdev(F) eeepc_wmi asus_wmi sparse_keymap joydev(F) rfcomm microcode(F) bnep psmouse(F) serio_raw(F) snd_hda_ codec_realtek snd_seq_midi(F) snd_seq_ midi_event( F) btusb bluetooth snd_rawmidi(F) snd_hda_intel lpc_ich snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq(F) snd_seq_device(F) snd_timer(F) mei_me snd(F) mei dm_snapshot(F) mac_hid soundcore(F) lp(F) parp ffffffff8155c95 2>] [<ffffffff8155c 952>] evdev_poll+ 0x32/0x60 f4f9e0 EFLAGS: 00010246
Aug 28 09:53:03 impulse kernel: [ 676.261290] Bluetooth: HIDP socket layer initialized
Aug 28 09:53:03 impulse kernel: [ 676.265270] magicmouse 0005:05AC:
Aug 28 09:53:03 impulse kernel: [ 676.420107] input: Apple Wireless Trackpad as /devices/
Aug 28 09:53:03 impulse kernel: [ 676.420428] magicmouse 0005:05AC:
Aug 28 09:53:04 impulse kernel: [ 677.189260] BUG: unable to handle kernel NULL pointer dereference at 00000000000003b0
Aug 28 09:53:04 impulse kernel: [ 677.189278] IP: [<ffffffff8155c
Aug 28 09:53:04 impulse kernel: [ 677.189289] PGD 0
Aug 28 09:53:04 impulse kernel: [ 677.189293] Oops: 0000 [#1] SMP
Aug 28 09:53:04 impulse kernel: [ 677.189299] Modules linked in: hid_magicmouse hidp dm_crypt(F) xt_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) ip6table_filter(F) ip6_tables(F) iptable_filter(F) ebtable_nat(F) ebtables(F) ipt_MASQUERADE(F) iptable_nat(F) nf_conntrack_
Aug 28 09:53:04 impulse kernel: ort(F) nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) ext2(F) btrfs(F) xor(F) zlib_deflate(F) raid6_pq(F) libcrc32c(F) hid_microsoft usb_storage(F) hid_generic usbhid hid nouveau ahci(F) libahci(F) r8169 mii(F) mxm_wmi i2c_algo_bit ttm drm_kms_helper video(F) drm wmi
Aug 28 09:53:04 impulse kernel: [ 677.189472] CPU: 1 PID: 1330 Comm: Xorg Tainted: GF 3.11.0-4-generic #9-Ubuntu
Aug 28 09:53:04 impulse kernel: [ 677.189479] Hardware name: System manufacturer System Product Name/P8Z77-V LX, BIOS 1106 07/27/2012
Aug 28 09:53:04 impulse kernel: [ 677.189485] task: ffff880404f35dc0 ti: ffff880404f4e000 task.ti: ffff880404f4e000
Aug 28 09:53:04 impulse kernel: [ 677.189491] RIP: 0010:[<
Aug 28 09:53:04 impulse kernel: [ 677.189503] RSP: 0018:ffff880404
Aug 28 09:53:04 impulse kernel: [ 677.189508] RAX: 0000000000000000 RBX: ffff880404570800 RCX: 0000000000000000
Aug 28 09:53:04 impulse kernel: [ 677.189513] RDX: ffff880404f4faf0 RSI: ffff880404f4faf0 RDI: ffff8804031a4000
Aug 28 09:53:04 im...