[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#764223: booting eder.debian.org fails



On Mon, 2014-10-06 at 13:20 +0000, Martin Zobel-Helas wrote:
> Source: linux-image-loongson-2e
> Version: 3.16+61~bpo70+1
> Severity: grave
> 
> Booting eder.debian.org with this kernel fails while booting
> linux-image-3.14-0.bpo.2-loongson-2e works just fine:
[...]
> [    4.700000] swapper: page allocation failure: order:0, mode:0x10d1
> [    4.708000] CPU: 0 PID: 1 Comm: swapper Not tainted 3.16-0.bpo.2-loongson-2e #1 Debian 3.16.3-2~bpo70+1
> [    4.716000] Stack : 0000000000008000 ffffffff803f4f98 ffffffff80950000 ffffffff80953908
>           0000000000000000 0000000000000000 ffffffff8074cec8 ffffffff8080b267
>           0000000000000001 0000000000000040 00000000000010d1 0000000000000000
>           0000000000000000 ffffffff80800000 0000000000000000 ffffffff806582d0
>           0000000000000000 980000004e0777f8 00000000000010d1 ffffffff801781cc
>           980000004e073930 ffffffff8074cec8 0000000000000000 0000000000000000
>           0000000000000000 0000000000000000 00ffffff8080b226 0000000000000000
>           0000000000000000 980000004e077750 0000000000000000 ffffffff801f6904
>           0000000000000000 00000000b54c6fb4 00000000000010d1 0000000000000000
>           0000000000000001 ffffffff80109c60 ffffffff8088ef28 ffffffff801f6904
>           ...
> [    4.784000] Call Trace:
> [    4.788000] [<ffffffff80109c60>] show_stack+0x78/0x90
> [    4.792000] [<ffffffff801f6904>] warn_alloc_failed+0xfc/0x140
> [    4.800000] [<ffffffff801f9f7c>] __alloc_pages_nodemask+0x7c4/0xa30
> [    4.808000] [<ffffffff801fa20c>] __get_free_pages+0x24/0xa0
> [    4.812000] [<ffffffff80119bec>] mips_dma_alloc_coherent+0x10c/0x1e0
> [    4.820000] [<ffffffff804ac320>] dmam_alloc_coherent+0x80/0xf8
> [    4.824000] [<ffffffff804ec978>] ata_bmdma_port_start+0x48/0x78

So we couldn't allocate memory for a DMA buffer (using GFP_KERNEL |
__GFP_NORETRY | GFP_DMA).

[...]
> [    4.972000] DMA free:0kB min:0kB low:0kB high:0kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:16384kB managed:0kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
[...]

And we have no memory available in the DMA zone.  But this is an ISA DMA
zone (first 16 MB of bus addresses).  Why would it need memory in that
range?  Maybe its DMA mask is no longer initialised correctly (pata_via
doesn't set it explicitly, but for PCI devices it should normally be set
to DMA_BIT_MASK(32) by default).

Can you test some intermediate kernel versions to narrow this down?
There should be several on snapshot.debian.org.

Ben.

-- 
Ben Hutchings
The program is absolutely right; therefore, the computer must be wrong.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: