BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Hi,
this bug appeared in Ubuntu 14.04, Ubuntu 12.04 didn't show this behavior.
I've found a possible predecessor in bug #212684.
Switching to a recent mainline kernel didn't fix this issue.
Starting
$ /usr/share/
will repeat this behavior.
/dev/md3 is a LVM PV:
--- Physical volume ---
PV Name /dev/md3
VG Name local_vg1
PV Size 1.36 TiB / not usable 2.25 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 355619
Free PE 31011
Allocated PE 324608
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.13.0-33-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-33-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.
Date: Wed Aug 13 21:42:12 2014
HibernationDevice: RESUME=
InstallationDate: Installed on 2014-07-06 (37 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
IwConfig:
lo no wireless extensions.
em1 no wireless extensions.
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm-
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.127.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: JT94510H.
dmi.board.name: D945GSEJT
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE57850-300
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
Uli Middelberg (uli-k) wrote : | #1 |
- AlsaDevices.txt Edit (429 bytes, text/plain; charset="utf-8")
- BootDmesg.txt Edit (55.9 KiB, text/plain; charset="utf-8")
- Card0.Codecs.codec.0.txt Edit (10.3 KiB, text/plain; charset="utf-8")
- CurrentDmesg.txt Edit (6.6 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
- Lspci.txt Edit (24.6 KiB, text/plain; charset="utf-8")
- Lsusb.txt Edit (470 bytes, text/plain; charset="utf-8")
- PciMultimedia.txt Edit (1.9 KiB, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (1.9 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (2.2 KiB, text/plain; charset="utf-8")
- UdevDb.txt Edit (111.8 KiB, text/plain; charset="utf-8")
- UdevLog.txt Edit (242.8 KiB, text/plain; charset="utf-8")
- WifiSyslog.txt Edit (170.9 KiB, text/plain; charset="utf-8")
Brad Figg (brad-figg) wrote : Status changed to Confirmed | #2 |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Joseph Salisbury (jsalisbury) wrote : | #3 |
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:
v3.13 Final: http://
v3.13.5: http://
v3.13.11.4: http://
You don't have to test every kernel, just up until the kernel that first has this bug.
Thanks in advance!
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: performing-bisect |
Uli Middelberg (uli-k) wrote : | #4 |
regression no: v3.13 Final: http://
regression yes: v3.13.5: http://
not tested: v3.13.11.4: http://
Uli Middelberg (uli-k) wrote : | #5 |
Update
regression yes (but significantly later : v3.13 Final: http://
regression yes: v3.13.5: http://
not tested: v3.13.11.4: http://
Joseph Salisbury (jsalisbury) wrote : | #6 |
Ok, so it sounds like the regression does eventually happen with 3.13 Final. We should probably test some earlier kernels to find the last kernel version where the regression did not happen. Can you test the following kernels and see which one does not hit the regression? It will probably require that you test the same amount of time that it took to hit the issue in 3.13 final:
3.12 Final: http://
3.11 Final: http://
Uli Middelberg (uli-k) wrote : | #7 |
3.12 Final: http://
Uli Middelberg (uli-k) wrote : | #8 |
is there any kernel I should try next?
Joseph Salisbury (jsalisbury) wrote : | #9 |
We should try some of the 3.13 release candidates since 3.12 final does not have the bug.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:
v3.13-rc3: http://
If v3.13-rc3 does not exhibit the bug then test v3.13-rc6:
v3.13-rc6: http://
If v3.13-rc3 does exhibit the bug then test v3.13-rc2:
v3.13-rc2: http://
You don't have to test every kernel, just up until the kernel that first has this bug.
Thanks in advance!
Uli Middelberg (uli-k) wrote : | #10 |
v3.13-rc3: doesn't exhibit this bug
v3.13-rc6: exhibits this bug
I'll try v3.13-rc4 and v3.13-rc5 next, but http://
Uli Middelberg (uli-k) wrote : | #11 |
v3.13-rc5: exhibits this bug
Joseph Salisbury (jsalisbury) wrote : | #12 |
I'll start a bisect between v3.13-rc3 and v3.13-rc5. It will require testing about 7 - 10 test kernels. Some of the kernels should exhibit the bug, while some should not. I'll post the first test kernel shortly.
Joseph Salisbury (jsalisbury) wrote : | #13 |
I started a kernel bisect between v3.13-rc3 and v3.13-rc5. The kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
308d17ef9530f23
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
tags: | added: latest-bios-0045 |
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Uli Middelberg (uli-k) wrote : | #14 |
308d17ef9530f23
Uli Middelberg (uli-k) wrote : | #15 |
308d17ef9530f23
Sorry for the confusion.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Joseph Salisbury (jsalisbury) wrote : | #16 |
I built the next test kernel, up to the following commit:
c6c1f325adc8a8e
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #17 |
c6c1f325adc8a8e
Sep 8 22:18:29 box kernel: [ 1940.144024] BUG: soft lockup - CPU#0 stuck for 22s! [md3_raid1:172]
Sep 8 22:18:29 box kernel: [ 1940.144024] Modules linked in: xt_multiport iptable_filter ip_tables x_tables gpio_ich snd_hda_
Sep 8 22:18:29 box kernel: [ 1940.144024] CPU: 0 PID: 172 Comm: md3_raid1 Not tainted 3.13.0-
Sep 8 22:18:29 box kernel: [ 1940.144024] Hardware name: /D945GSEJT, BIOS JT94510H.
Sep 8 22:18:29 box kernel: [ 1940.144024] task: f6888cf0 ti: f6b68000 task.ti: f6b68000
Sep 8 22:18:29 box kernel: [ 1940.144024] EIP: 0060:[<c12ff0b2>] EFLAGS: 00000297 CPU: 0
Sep 8 22:18:29 box kernel: [ 1940.144024] EIP is at memcmp+0x32/0x60
Sep 8 22:18:29 box kernel: [ 1940.144024] EAX: ecb27000 EBX: 0000007e ECX: 00000962 EDX: ec8de000
Sep 8 22:18:29 box kernel: [ 1940.144024] ESI: 0000007e EDI: 00000fff EBP: f6b69e9c ESP: f6b69e8c
Sep 8 22:18:29 box kernel: [ 1940.144024] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Sep 8 22:18:29 box kernel: [ 1940.144024] CR0: 8005003b CR2: bfc95ef4 CR3: 01ae4000 CR4: 000007f0
Sep 8 22:18:29 box kernel: [ 1940.144024] Stack:
Sep 8 22:18:29 box kernel: [ 1940.144024] 00000000 00000006 00001000 00000048 f6b69ee0 f845d3b3 ec8de000 00000001
Sep 8 22:18:29 box kernel: [ 1940.144024] 0000000f f6847800 00000007 ecb9e800 f69d2f80 f50da4e0 0000000c ecb9ea00
Sep 8 22:18:29 box kernel: [ 1940.144024] 0000001c ecd53300 00000002 ecd53300 f6847800 f6b69f00 f845d667 f6847800
Sep 8 22:18:29 box kernel: [ 1940.144024] Call Trace:
Sep 8 22:18:29 box kernel: [ 1940.144024] [<f845d3b3>] process_
Sep 8 22:18:29 box kernel: [ 1940.144024] [<f845d667>] sync_request_
Sep 8 22:18:29 box kernel: [ 1940.144024] [<f845f5d2>] raid1d+0x102/0x140 [raid1]
Sep 8 22:18:29 box kernel: [ 1940.144024] [<c151bf54>] md_thread+
Sep 8 22:18:29 box kernel: [ 1940.144024] [<c1095010>] ? __wake_
Sep 8 22:18:29 box kernel: [ 1940.144024] [<c151be70>] ? md_rdev_
Sep 8 22:18:29 box kernel: [ 1940.144024] [<c107801b>] kthread+0x9b/0xb0
Sep 8 22:18:29 box kernel: [ 1940.144024] [<c1684077>] ret_from_
Sep 8 22:18:29 box kernel: [ 1940.144024] [<c1077f80>] ? flush_kthread_
Sep 8 22:18:29 box kernel: [ 1940.144024] Code: ec 04 85 c9 c7 45 f0 00 00 00 00 74 29 0f b6 30 0f b6 1a 29 de 89 75 f0 75 1c 8d 79 ff 31 c9 eb 11 0f b6 74 08 01 0f b6 5c 0a 01 <83> c1 01 29 de 75 0f 39 f9 75 eb 8b 45 f0 83 c4 04 5b 5e 5f 5d
Sep 8 22:38:36 box mdadm[1615]: Rebuild21 event detected on md device /dev/md/03
Sep 8 22:41:05 box kernel: [ 3296.144025] BUG: soft lockup - CPU#0 s...
Joseph Salisbury (jsalisbury) wrote : | #18 |
I built a Trusty test kernel with a revert of commit c6c1f325.
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? If it does still exhibit the bug, I'll have to look at the bisect results further.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #19 |
Hi Joseph,
unfortunately the kernel you are offering for testing is for the amd64 platform, but I need it for the i386 platform.
Regards
Uli
Joseph Salisbury (jsalisbury) wrote : | #20 |
I built a i386 Trusty test kernel with a revert of commit c6c1f325.
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not?
Uli Middelberg (uli-k) wrote : | #21 |
- dmesg.3.13.0-36.63~lp1356558v1.gz Edit (14.3 KiB, application/octet-stream)
I'd like to test the kernel, but this particular build doesn't come up with support for networking nor usb keyboard. I've attached the dmesg.gz.
Uli Middelberg (uli-k) wrote : | #22 |
- dmesg.3.13.0-031300rc3.201312061335.gz Edit (15.5 KiB, application/octet-stream)
The v3.13-rc3 build instead is running well.
Joseph Salisbury (jsalisbury) wrote : | #23 |
Did you install both the linux-image and linux-image-extra .deb packages for my test kernel?
Uli Middelberg (uli-k) wrote : | #24 |
OK, I didn't install the linux-image-extra package, it wasn't necessary with the other kernels I've tested before. With this package installed, the kernel boots properly, but
c6c1f325: exhibits this bug.
Joseph Salisbury (jsalisbury) wrote : | #25 |
So the test kernel posted in comment #20 does fix this bug? It has commit c6c1f325 reverted.
Uli Middelberg (uli-k) wrote : | #26 |
Hello Joseph,
the last kernel, you have prepared for testing contains this bug.
I've just noticed that 3.13.0-
[44094.835704] md: data-check of RAID array md1
[44094.835716] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[44094.835723] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
[44094.835732] md: using 128k window, over a total of 4192192k.
[44095.909810] type=1400 audit(141101524
[44095.909839] type=1400 audit(141101524
[44095.912967] type=1400 audit(141101524
[44403.916160] INFO: task md1_resync:8767 blocked for more than 120 seconds.
[44403.916448] Not tainted 3.13.0-
[44403.916692] "echo 0 > /proc/sys/
[44403.916988] md1_resync D c10a8e24 0 8767 2 0x00000000
[44403.917009] ebc1bd5c 00000046 ebc1bce8 c10a8e24 00000092 20e0b127 00002833 c1af0400
[44403.917039] c105bbd2 c1af0400 f7bde400 e794b400 f7210d00 00000000 f6a8be48 ebc1bd1c
[44403.917066] ebc1bd30 f6a8be00 f6a8be48 ebc1bd70 ebc1bd90 c16998b3 00000082 e794b400
[44403.917093] Call Trace:
[44403.917122] [<c10a8e24>] ? irq_to_
[44403.917141] [<c105bbd2>] ? irq_exit+0x62/0xa0
[44403.917162] [<c16998b3>] ? common_
[44403.917178] [<c1093f31>] ? prepare_
[44403.917195] [<c168e733>] schedule+0x23/0x60
[44403.917247] [<f8444e45>] raise_barrier+
[44403.917263] [<c1094010>] ? __wake_
[44403.917291] [<f8444fab>] sync_request+
[44403.917312] [<c1534b9f>] md_do_sync+
[44403.917341] [<f8444ee0>] ? raise_barrier+
[44403.917361] [<c10653d7>] ? recalc_
[44403.917379] [<c1531da0>] ? md_rdev_
[44403.917395] [<c1531e84>] md_thread+
[44403.917409] [<c1093adf>] ? __wake_
[44403.917426] [<c1531da0>] ? md_rdev_
[44403.917441] [<c107625b>] kthread+0x9b/0xb0
[44403.917459] [<c1699337>] ret_from_
[44403.917474] [<c10761c0>] ? flush_kthread_
[44523.916155] INFO: task md1_resync:8767 blocked for more than 120 seconds.
[44523.916433] Not tainted 3.13.0-
[44523.916676] "echo 0 > /proc/sys/
[44523.916972] md1_resync D c10a8e24 0 8767 2 0x00000000
[44523.916993] ebc1bd5c 00000046 ebc1bce8 c10a8e24 00000092 20e0b127 00002833 c1af0400
[44523.917022] c105bbd2 c1af0400 f7bde400 e794b400 f7210d00 00000000 f6a8be48 ebc...
Uli Middelberg (uli-k) wrote : | #27 |
3.13.0-
Uli Middelberg (uli-k) wrote : | #28 |
3.13.0-
I'll try v3.12.14-trusty next
Uli Middelberg (uli-k) wrote : | #29 |
Uli Middelberg (uli-k) wrote : | #30 |
Uli Middelberg (uli-k) wrote : | #31 |
Uli Middelberg (uli-k) wrote : | #32 |
Uli Middelberg (uli-k) wrote : | #33 |
Uli Middelberg (uli-k) wrote : | #34 |
3.12 final: clean
3.12.14: clean
3.12.21: clean
3.12.25: clean
3.12.27: clean
3.12.28: clean
3.13.0-
3.13.0-031300rc2
3.13.0-031300rc3
3.13.0-031300rc5
3.13.0-031300rc6
3.13 final: bug
Is there any kernel version before 3.13.0-031300rc1 I should test.
Joseph Salisbury (jsalisbury) wrote : | #35 |
I looks like the bug was introduced in v3.13-rc1. I'll start a kernel bisect between v3.12 final and 3.13-rc1 and post a test kernel shortly.
Joseph Salisbury (jsalisbury) wrote : | #36 |
I started a kernel bisect between v3.12 final and v3.13-rc1. The kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
5cbb3d216e20417
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #37 |
5cbb3d216e20417
[ 908.144025] BUG: soft lockup - CPU#0 stuck for 22s! [md3_raid1:173]
[ 908.144025] Modules linked in: xt_multiport iptable_filter ip_tables x_tables gpio_ich snd_hda_
[ 908.144025] CPU: 0 PID: 173 Comm: md3_raid1 Not tainted 3.12.0-
[ 908.144025] Hardware name: /D945GSEJT, BIOS JT94510H.
[ 908.144025] task: f6af26d0 ti: f6b82000 task.ti: f6b82000
[ 908.144025] EIP: 0060:[<c12f881d>] EFLAGS: 00000297 CPU: 0
[ 908.144025] EIP is at memcmp+0x2d/0x60
[ 908.144025] EAX: ecdcf000 EBX: 00000090 ECX: 00000270 EDX: ed369000
[ 908.144025] ESI: 000000a7 EDI: 00000fff EBP: f6b83ea4 ESP: f6b83e94
[ 908.144025] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 908.144025] CR0: 8005003b CR2: b91bb5dc CR3: 01acb000 CR4: 000007f0
[ 908.144025] Stack:
[ 908.144025] 00000000 0000000b 00001000 00000084 f6b83ee8 f85d42e3 ed369000 00000001
[ 908.144025] 0000000f f6b04800 0000000c ecc0e600 f6982d00 f50fd9e0 0000000c ecc0fa00
[ 908.144025] 0000001c ed263000 00000002 ed263000 f6b04800 f6b83f08 f85d4597 f6b04800
[ 908.144025] Call Trace:
[ 908.144025] [<f85d42e3>] process_
[ 908.144025] [<f85d4597>] sync_request_
[ 908.144025] [<f85d6222>] raid1d+0x102/0x140 [raid1]
[ 908.144025] [<c1510d24>] md_thread+
[ 908.144025] [<c1095340>] ? __wake_
[ 908.144025] [<c1510c40>] ? md_rdev_
[ 908.144025] [<c1077ebb>] kthread+0x9b/0xb0
[ 908.144025] [<c1674a77>] ret_from_
[ 908.144025] [<c1077e20>] ? flush_kthread_
[ 908.144025] Code: e5 57 56 53 83 ec 04 85 c9 c7 45 f0 00 00 00 00 74 29 0f b6 30 0f b6 1a 29 de 89 75 f0 75 1c 8d 79 ff 31 c9 eb 11 0f b6 74 08 01 <0f> b6 5c 0a 01 83 c1 01 29 de 75 0f 39 f9 75 eb 8b 45 f0 83 c4
Joseph Salisbury (jsalisbury) wrote : | #38 |
I built the next test kernel, up to the following commit:
f9efbce6334844c
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #39 |
Joseph Salisbury (jsalisbury) wrote : | #40 |
I built the next test kernel, up to the following commit:
f095ca6b31cfd20
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #41 |
Joseph Salisbury (jsalisbury) wrote : | #42 |
I built the next test kernel, up to the following commit:
c2d33069915d1f9
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #43 |
c2d33069915d1f9
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #44 |
I built the next test kernel, up to the following commit:
2026d24ef2ea8ca
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #45 |
2026d24ef2ea8ca
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #46 |
I built the next test kernel, up to the following commit:
a6bc732b5a96b54
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #47 |
a6bc732b5a96b54
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #48 |
I built the next test kernel, up to the following commit:
23b4faa9a36257e
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #49 |
23b4faa9a36257e
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #50 |
I built the next test kernel, up to the following commit:
86467ff2ddca94c
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #51 |
86467ff2ddca94c
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
86467ff2ddca94c
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Uli Middelberg (uli-k) wrote : | #52 |
Is there anything I should test next?
Joseph Salisbury (jsalisbury) wrote : | #53 |
I built the next test kernel, up to the following commit:
8a5dc585d50015a
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #54 |
8a5dc585d50015a
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
86467ff2ddca94c
8a5dc585d50015a
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #55 |
I built the next test kernel, up to the following commit:
5e1109adde6acd0
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #56 |
5e1109adde6acd0
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
86467ff2ddca94c
5e1109adde6acd0
8a5dc585d50015a
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #57 |
I built the next test kernel, up to the following commit:
a3183c60e3e9be7
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #58 |
a3183c60e3e9be7
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
86467ff2ddca94c
5e1109adde6acd0
a3183c60e3e9be7
8a5dc585d50015a
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #59 |
I built the next test kernel, up to the following commit:
94daf85e3c4db3b
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #60 |
94daf85e3c4db3b
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
86467ff2ddca94c
5e1109adde6acd0
a3183c60e3e9be7
94daf85e3c4db3b
8a5dc585d50015a
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #61 |
I built the next test kernel, up to the following commit:
9da8312048edcf2
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #62 |
9da8312048edcf2
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
86467ff2ddca94c
5e1109adde6acd0
a3183c60e3e9be7
94daf85e3c4db3b
9da8312048edcf2
8a5dc585d50015a
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #63 |
I built the next test kernel, up to the following commit:
eeab517b68beb9e
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Uli Middelberg (uli-k) wrote : | #64 |
eeab517b68beb9e
3.12 final: clean
f9efbce6334844c
f095ca6b31cfd20
2026d24ef2ea8ca
a6bc732b5a96b54
23b4faa9a36257e
86467ff2ddca94c
5e1109adde6acd0
a3183c60e3e9be7
94daf85e3c4db3b
9da8312048edcf2
eeab517b68beb9e
8a5dc585d50015af
c2d33069915d1f9
5cbb3d216e204170
3.13.0-031300rc1
3.13 final: bug
Joseph Salisbury (jsalisbury) wrote : | #65 |
The bisect reported eeab517 as the bad commit. However, this is a merge, so it can't be easily reverted. It will require further investigation.
Can you see if this bug also exists in the 3.18-rc4 kernel:
http://
Uli Middelberg (uli-k) wrote : | #66 |
I tried the 3.18-rc4 kernel, the bug is also there:
Nov 16 07:16:39 box kernel: [34280.152007] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [clamscan:2868]
Nov 16 07:16:39 box kernel: [34280.152007] Modules linked in: xt_multiport iptable_filter ip_tables x_tables gpio_ich snd_hda_
rial lpc_ich snd_hwdep snd_pcm drm_kms_helper snd_timer 8250_fintek snd drm soundcore video mac_hid i2c_algo_bit parport_pc ppdev lp parport dm_snapshot dm_bufio raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor ahci
psmouse libahci r8169 raid6_pq sata_via raid1 raid0 multipath mii linearNov 16 07:16:39 box kernel: [34280.152007] CPU: 1 PID: 2868 Comm: clamscan Not tainted 3.18.0-
Nov 16 07:16:39 box kernel: [34280.152007] Hardware name: /D945GSEJT, BIOS JT94510H.
Nov 16 07:16:39 box kernel: [34280.152007] task: f6acb100 ti: ec63a000 task.ti: ec63a000
Nov 16 07:16:39 box kernel: [34280.152007] EIP: 0060:[<c115e7fa>] EFLAGS: 00000246 CPU: 1
Nov 16 07:16:39 box kernel: [34280.152007] EIP is at compact_
Nov 16 07:16:39 box kernel: [34280.152007] EAX: 00000002 EBX: ec63bb20 ECX: 00000008 EDX: 00000009
Nov 16 07:16:39 box kernel: [34280.152007] ESI: c1a41ac0 EDI: 00000002 EBP: ec63bad8 ESP: ec63bac0
Nov 16 07:16:39 box kernel: [34280.152007] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Nov 16 07:16:39 box kernel: [34280.152007] CR0: 80050033 CR2: a5000000 CR3: 2c0d6000 CR4: 000007f0
Nov 16 07:16:39 box kernel: [34280.152007] Stack:
Nov 16 07:16:39 box kernel: [34280.152007] 00000000 00000000 00000002 ec63bb20 c1a41ac0 c1a41ac0 ec63bb18 c1160062
Nov 16 07:16:39 box kernel: [34280.152007] ec63bb20 00000000 00000000 fffff000 00000014 000377fe 000377fe 00000000
Nov 16 07:16:39 box kernel: [34280.152007] ec63bb28 00000002 00001000 c1a41ac0 004352da ec63bb58 ec63bb64 c116043c
Nov 16 07:16:39 box kernel: [34280.152007] Call Trace:
Nov 16 07:16:39 box kernel: [34280.152007] [<c1160062>] compact_
Nov 16 07:16:39 box kernel: [34280.152007] [<c116043c>] compact_
Nov 16 07:16:39 box kernel: [34280.152007] [<c1160536>] try_to_
Nov 16 07:16:39 box kernel: [34280.152007] [<c16b5de8>] __alloc_
Nov 16 07:16:39 box kernel: [34280.152007] [<c1146d4b>] __alloc_
Nov 16 07:16:39 box kernel: [34280.152007] [<c1195cd0>] ? commit_
Nov 16 07:16:39 box kernel: [34280.152007] [<c1190887>] do_huge_
Nov 16 07:16:39 box kernel: [34280.152007] [<c11685cf>] ? handle_
Nov 16 07:16:39 box kernel: [34280.152007] [<c11688c1>] __handle_
Nov 16 07:16:39 box kernel: [34280.152007] [<c1168a27>] handle_
Nov 16 07:16:39 box kernel: [34280.152007] [<c104d600>] ? trace_do_
Nov 16 07:16:39 box kernel: [34280.152007] [<c104d197>] __do_page_
Nov 16 07:16:39 box kernel: [34280.152007] [<c1143c20>] ? ...
Uli Middelberg (uli-k) wrote : | #67 |
If I totally disable any sound output or even the whole sound subsystem, do you think this will decrease the likelihood of this bug to appear?
Uli Middelberg (uli-k) wrote : | #68 |
I there anything I can do next?
Joseph Salisbury (jsalisbury) wrote : | #69 |
This still needs further investigation.
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.
Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.
Once this bug is reported upstream, please add the tag: 'kernel-
Uli Middelberg (uli-k) wrote : | #70 |
Hello Joseph,
before issuing an upstream bug report I tried the first stable release of 3.18 [0] and I wasn't able to reproduce the bug so far. So you may suspend or keep this bug report on hold. I'd really like to know if there is some incidence (i.e. a specific commit) for this bug being fixed by upstream development. Thank you so far.
[0] http://
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Launchpad Janitor (janitor) wrote : | #71 |
[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
Changed in linux (Ubuntu): | |
status: | Incomplete → Expired |
This change was made by a bot.