linux-kernel - bisected crash due to "x86: Move swiotlb initialization before dma32_free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 Dec 2009 23:47:07 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	linux-kernel@...r.kernel.org,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Subject: bisected crash due to "x86: Move swiotlb initialization before dma32_free_bootmem"

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/