linux-crashdump fails to record crash; reports memory not reserved
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
I'm attempting to isolate a consistent crash on an Intrepid (upgraded from 8.04.1 LTS) using linux-crashdump and am not getting the dumps; instead, I get an error message about memory not being reserved. Indeed /var/crash comes up empty after a crash. dmesg and /proc/iomem results are included.
Below are the steps I've taken and the results:
I installed linux-crashdump with directions from http://
After installing linux-crashdump (apparently renamed from linux-crashdump
On reboot, I get a message something like "memory was not reserved, please pass in crashkernel=X@Y".
I can't reproduce the exact message here because it doesn't appear in dmesg or log files.
Here is the kernel line that update-grub put in:
kernel /boot/vmlinuz-
-7af28eb5e653 ro quiet splash crashkernel=
(A web search for the crashkernel string shows that it's pretty widespread.)
Attached is the dmesg output (I have since added pci-nommconf to the kernel line so you may see that in dmesg).
Here is the result of cat /proc/iomem. I believe this shows no memory is reserved.
00000000-0009f7ff : System RAM
0009f800-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cd1ff : Video ROM
000cd200-000cffff : pnp 00:0d
000e0000-000effff : pnp 00:0d
000f0000-000fffff : reserved
000f0000-000fffff : System ROM
00100000-dfedffff : System RAM
00100000-00383359 : Kernel code
0038335a-004a567f : Kernel data
00515000-005c0a1f : Kernel bss
dfee0000-dfee2fff : ACPI Non-volatile Storage
dfee3000-dfeeffff : ACPI Tables
dfef0000-dfefffff : reserved
e0000000-efffffff : PCI Bus 0000:01
e0000000-efffffff : 0000:01:00.0
f0000000-f3ffffff : reserved
f4000000-f7ffffff : PCI Bus 0000:01
f4000000-f5ffffff : 0000:01:00.0
f6000000-f6ffffff : 0000:01:00.0
f7000000-f701ffff : 0000:01:00.0
f8000000-f8ffffff : PCI Bus 0000:03
f9000000-faffffff : PCI Bus 0000:04
fa000000-fa000fff : 0000:04:00.0
fa000000-
fb000000-fb0fffff : PCI Bus 0000:05
fb000000-fb000fff : 0000:05:02.0
fb001000-fb001fff : 0000:05:02.0
fb002000-fb002fff : 0000:05:02.1
fb003000-fb003fff : 0000:05:02.1
fb100000-fb103fff : 0000:00:1b.0
fb100000-fb103fff : ICH HD audio
fb104000-fb1043ff : 0000:00:1d.7
fb104000-fb1043ff : ehci_hcd
fb105000-fb1053ff : 0000:00:1a.7
fb105000-fb1053ff : ehci_hcd
fb106000-fb1060ff : 0000:00:1f.3
fb200000-fb2fffff : PCI Bus 0000:04
fb200000-fb21ffff : 0000:04:00.0
fec00000-ffffffff : reserved
fed00000-fed003ff : HPET 0
fee00000-fee00fff : Local APIC
I'm seeing this too (also on intrepid; clean amd64 install in my cause, though).
If I modify my grub config and change "crashkernel= 384M-2G: 64M@16M, 2G-:128M@ 16M" to "crashkernel= 64M@16M" , kexec no longer errors out with "please reserve memory ...".
I'm not familiar with that more complex crashkernel=... syntax, but it apparently does not work with Ubuntu's intrepid kernels. (Maybe it works for some people?)
However, now kexec errors out with "Command line overflow". I think Ubuntu kernels *do* support longer kernel command lines, and after reading https:/ /bugzilla. novell. com/show_ bug.cgi? id=257968, I suspect this problem is with Ubuntu's kexec assuming on its own that the command line limit is 256 chars. I realize this is a separate bug, but I suspect anyone who gets past the original bug will hit this one.