kernel crashes in 3.13, not 3.2

[Christopher Hoover]

linux-image-3.2.0-56-generic boots fine.

linux-image-3.13.0-38-generic and its early versions crash on my HP ProLiant ML150 G5.

N.B. there is an earlier backtrace from a wedged CPU before the final backtrace that takes the ship down.

ch@snaggle:~$ lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
---
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ch 17924 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=493c888f-33b9-4f1a-accd-8db5c8d5eb7a
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: HP ProLiant ML150 G5
Package: linux (not installed)
ProcEnviron:
 LD_LIBRARY_PATH=<set>
 TERM=xterm
 PATH=(custom, no user)
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-56-generic root=UUID=a1e7059a-c630-4804-8944-a66e3b7ab3b0 ro nomdmonddf nomdmonisw crashkernel=384M-:128M
ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-56-generic N/A
 linux-backports-modules-3.2.0-56-generic N/A
 linux-firmware 1.127.7
RfKill:

Tags: trusty
Uname: Linux 3.2.0-56-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-08-17 (55 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video
WpaSupplicantLog:

_MarkForUpload: True
dmi.bios.date: 10/25/2010
dmi.bios.vendor: HP
dmi.bios.version: O17
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: ProLiant ML150 G5
dmi.board.vendor: HP
dmi.chassis.asset.tag: snaggle
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnHP:bvrO17:bd10/25/2010:svnHP:pnProLiantML150G5:pvr1.0:rvnHP:rnProLiantML150G5:rvr:cvnHP:ct7:cvr1.0:
dmi.product.name: ProLiant ML150 G5
dmi.product.version: 1.0
dmi.sys.vendor: HP

[Brad Figg (brad-figg)]

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

apport-collect 1380197

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.

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

apport information

[Christopher Hoover (choover)]

noted: apport logs were capture under a 3.2 kernel.

[penalvch (penalvch)]

Christopher Hoover, thank you for reporting this bug and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (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 exactly shown as:
kernel-fixed-upstream-3.17

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.

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

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.

[Christopher Hoover (choover)]

i'm happy to try another kernel but it is not clear what is meant by "the
latest upstream kernel available from the very top line at the top of the
page (not the daily folder) following https://wiki.ubuntu.com/
KernelMainlineBuilds"?

do the instructions still agree with the web page?

-ch

On Sat Oct 11 2014 at 10:40:51 PM Christopher M. Penalver <
<email address hidden>> wrote:

> Christopher Hoover, thank you for reporting this bug and helping make
> Ubuntu better. Could you please test the latest upstream kernel available
> from the very top line at the top of the page (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
> exactly shown as:
> kernel-fixed-upstream-3.17
>
> 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.
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> 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.
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1380197
>
> Title:
> kernel crashes in 3.13, not 3.2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1380197/+subscriptions
>

[Christopher Hoover (choover)]

reading between the lines, i am installing:

~kernel-ppa/mainline/v3.17.1-utopic

will report back soon.

On Sun Oct 19 2014 at 5:31:49 PM Christopher Hoover <email address hidden>
wrote:

> i'm happy to try another kernel but it is not clear what is meant by "the
> latest upstream kernel available from the very top line at the top of the
> page (not the daily folder) following https://wiki.ubuntu.com/Kernel
> MainlineBuilds"?
>
> do the instructions still agree with the web page?
>
> -ch
>
> On Sat Oct 11 2014 at 10:40:51 PM Christopher M. Penalver <
> <email address hidden>> wrote:
>
>> Christopher Hoover, thank you for reporting this bug and helping make
>> Ubuntu better. Could you please test the latest upstream kernel available
>> from the very top line at the top of the page (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
>> exactly shown as:
>> kernel-fixed-upstream-3.17
>>
>> 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.
>>
>> If the mainline kernel does not fix this bug, please add the following
>> tags:
>> kernel-bug-exists-upstream
>> kernel-bug-exists-upstream-VERSION-NUMBER
>>
>> 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.
>>
>> ** Changed in: linux (Ubuntu)
>> Importance: Undecided => Medium
>>
>> ** Changed in: linux (Ubuntu)
>> Status: Confirmed => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1380197
>>
>> Title:
>> kernel crashes in 3.13, not 3.2
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380197
>> /+subscriptions
>>
>

[Christopher Hoover (choover)]

p.s. i think the instructions mean the kernel on the very top line of:

http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

On Sun Oct 19 2014 at 7:06:39 PM Christopher Hoover <email address hidden>
wrote:

> reading between the lines, i am installing:
>
> ~kernel-ppa/mainline/v3.17.1-utopic
>
> will report back soon.
>
>
> On Sun Oct 19 2014 at 5:31:49 PM Christopher Hoover <email address hidden>
> wrote:
>
>> i'm happy to try another kernel but it is not clear what is meant by "the
>> latest upstream kernel available from the very top line at the top of the
>> page (not the daily folder) following https://wiki.ubuntu.com/Kernel
>> MainlineBuilds"?
>>
>> do the instructions still agree with the web page?
>>
>> -ch
>>
>> On Sat Oct 11 2014 at 10:40:51 PM Christopher M. Penalver <
>> <email address hidden>> wrote:
>>
>>> Christopher Hoover, thank you for reporting this bug and helping make
>>> Ubuntu better. Could you please test the latest upstream kernel available
>>> from the very top line at the top of the page (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
>>> exactly shown as:
>>> kernel-fixed-upstream-3.17
>>>
>>> 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.
>>>
>>> If the mainline kernel does not fix this bug, please add the following
>>> tags:
>>> kernel-bug-exists-upstream
>>> kernel-bug-exists-upstream-VERSION-NUMBER
>>>
>>> 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.
>>>
>>> ** Changed in: linux (Ubuntu)
>>> Importance: Undecided => Medium
>>>
>>> ** Changed in: linux (Ubuntu)
>>> Status: Confirmed => Incomplete
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1380197
>>>
>>> Title:
>>> kernel crashes in 3.13, not 3.2
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380197
>>> /+subscriptions
>>>
>>

[Christopher Hoover (choover)]

tags added, as requested.

problem is fixed with 3.17.1-utopic

[penalvch (penalvch)]

Christopher Hoover, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]