From: Roland Dreier <rdreier@cisco.com>
To: linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Subject: bisected crash due to "x86: Move swiotlb initialization before dma32_free_bootmem"
Date: Mon, 14 Dec 2009 23:47:07 -0800 [thread overview]
Message-ID: <ada8wd4brwk.fsf@roland-alpha.cisco.com> (raw)
Hi Tomonori-san:
I have a big box (64 threads, 256GB memory) that is crashing early in
boot as below. I bisected it down to f4780ca0 ("x86: Move swiotlb
initialization before dma32_free_bootmem"); reverting just this commit
from the latest git (3ea6b3d0 is what I tested) fixes things.
I haven't tried to debug this yet, but I guess on such a huge box there
is not enough memory below 4GB for swiotlb if we don't free the DMA32
stuff allocated earlier? I don't know why that would be, since the
bootmem is grabbing 512MB and I have pretty close to 4GB below 4GB.
Anyway, I'm going to go to bed soon, but if you need more information or
have anything you want me to try, I will do it tomorrow morning.
Thanks,
Roland
Zone PFN ranges:
DMA 0x00000001 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x04080000
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0: 0x00000001 -> 0x0000009b
0: 0x00000100 -> 0x00078c74
0: 0x00100000 -> 0x04080000
... snip ...
PERCPU: Embedded 29 pages/cpu @ffff880172400000 s90008 r8192 d20584 u131072
pcpu-alloc: s90008 r8192 d20584 u131072 alloc=1*2097152
pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
pcpu-alloc: [0] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
pcpu-alloc: [0] 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
pcpu-alloc: [0] 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 66154133
Policy zone: Normal
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.30-2-amd64 root=UUID=c32babd2-b320-48e5-bdd4-350d659b07a5 ro console=ttyS0,115200n8 earlyprintk=ttyS0,115200
PID hash table entries: 4096 (order: 3, 32768 bytes)
bootmem alloc of 67108864 bytes failed!
Kernel panic - not syncing: Out of memory
Pid: 0, comm: swapper Not tainted 2.6.32 #19
Call Trace:
[<ffffffff81342c82>] ? panic+0x86/0x141
[<ffffffff816f0e00>] ? ___alloc_bootmem_nopanic+0x89/0xc7
[<ffffffff813477b6>] ? _etext+0x0/0x38d84a
[<ffffffff816f0e6d>] ? ___alloc_bootmem_node+0x0/0x59
[<ffffffff816f98a7>] ? swiotlb_init_with_default_size+0x3f/0x126
[<ffffffff816e6669>] ? pci_swiotlb_init+0x50/0x63
[<ffffffff816d5140>] ? early_idt_handler+0x0/0x71
[<ffffffff816dbd2a>] ? pci_iommu_alloc+0xb/0x73
[<ffffffff816d5140>] ? early_idt_handler+0x0/0x71
[<ffffffff816e9e70>] ? mem_init+0x15/0xe5
[<ffffffff816d5ad2>] ? start_kernel+0x1bd/0x39e
[<ffffffff816d53b2>] ? x86_64_start_kernel+0xf9/0x106
next reply other threads:[~2009-12-15 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 7:47 Roland Dreier [this message]
2009-12-15 8:55 ` bisected crash due to "x86: Move swiotlb initialization before dma32_free_bootmem" FUJITA Tomonori
2009-12-15 9:04 ` Yinghai Lu
2009-12-15 9:23 ` FUJITA Tomonori
2009-12-15 9:11 ` Yinghai Lu
2009-12-15 9:23 ` FUJITA Tomonori
2009-12-15 10:56 ` Ingo Molnar
2009-12-15 11:10 ` FUJITA Tomonori
2009-12-15 11:25 ` Yinghai Lu
2009-12-15 11:43 ` Ingo Molnar
2009-12-15 11:50 ` FUJITA Tomonori
2009-12-15 13:04 ` Yinghai Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ada8wd4brwk.fsf@roland-alpha.cisco.com \
--to=rdreier@cisco.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.