Skip to contentSkip to conversation

BUG: crashkernel does not boot upon crash from sysrq-trigger

DISCUSSION Christoph Paasch 2 participants 3 messages Dec 16, 2013

lore
Share & tools
lore
#0 lore raw

Hello,

since 3.5, my crashkernel does not boot anymore when triggering an oops with /proc/sysrq-trigger on my HP Elitebook 8540p.

I bisected it down to 722bc6b16771ed8 (x86/mm: Fix the size calculation of mapping tables).

Does anybody has an idea what is going wrong here? Let me know, if I should provide more information.

Thanks,
Christoph

#1 lore raw
Quoted 8 lines · Christoph Paasch

Hello,

since 3.5, my crashkernel does not boot anymore when triggering an oops with /proc/sysrq-trigger on my HP Elitebook 8540p.

I bisected it down to 722bc6b16771ed8 (x86/mm: Fix the size calculation of mapping tables).

It has been reverted in upstream.

#2 lore raw
Quoted 4 lines · Cong Wang
Quoted 2 lines · Christoph Paasch

Hello,

Quoted 8 lines
Quoted 6 lines

since 3.5, my crashkernel does not boot anymore when triggering an oops with /proc/sysrq-trigger on my HP Elitebook 8540p.

I bisected it down to 722bc6b16771ed8 (x86/mm: Fix the size calculation of mapping tables).

It has been reverted in upstream.

Oh, then something else is causing my bug again, because I tried v3.13-rc3 to see if it has been fixed upstream. And, my Ubuntu runs on v3.11, where the crashkernel does not work either.

My bisect ended up on 722bc6b16771ed8 because I started bisecting between v3.2 (good) and v3.5 (bad).

So, then I will make again a bisect between v3.7 and v3.11.

Thanks,
Christoph