Bug#764223: booting eder.debian.org fails

2014-10-10 Thread Martin Zobel-Helas
Hi, 

On Mon Oct 06, 2014 at 17:06:23 +0100, Ben Hutchings wrote:
 On Mon, 2014-10-06 at 13:20 +, 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.70] 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 : 8000 803f4f98 8095 
  80953908
  8074cec8 
  8080b267
0001 0040 10d1 
  
 8080  
  806582d0
 98004e0777f8 10d1 
  801781cc
98004e073930 8074cec8  
  
  00ff8080b226 
  
 98004e077750  
  801f6904
 b54c6fb4 10d1 
  
0001 80109c60 8088ef28 
  801f6904
...
  [4.784000] Call Trace:
  [4.788000] [80109c60] show_stack+0x78/0x90
  [4.792000] [801f6904] warn_alloc_failed+0xfc/0x140
  [4.80] [801f9f7c] __alloc_pages_nodemask+0x7c4/0xa30
  [4.808000] [801fa20c] __get_free_pages+0x24/0xa0
  [4.812000] [80119bec] mips_dma_alloc_coherent+0x10c/0x1e0
  [4.82] [804ac320] dmam_alloc_coherent+0x80/0xf8
  [4.824000] [804ec978] 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.

zobel@eder:~% uname -a
Linux eder 3.16-rc5-loongson-2e #1 Debian 3.16~rc5-1~exp1 (2014-07-15) mips64 
GNU/Linux

The 3.16rc5 kernel still boots. Hope that helps to narrow down the problem.

Cheers,
Martin
-- 
 Martin Zobel-Helas zo...@debian.orgDebian System Administrator
 Debian  GNU/Linux Developer   Debian Listmaster
 http://about.me/zobel   Debian Webmaster
 GPG Fingerprint:  6B18 5642 8E41 EC89 3D5D  BDBB 53B1 AC6D B11B 627B 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#764223: booting eder.debian.org fails

2014-10-06 Thread Martin Zobel-Helas
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:


Loading Linux ...
Loading initial ramdisk ...
Starting kernel (no output to be expected) ...
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16-0.bpo.2-loongson-2e 
(debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 
Debian 3.16.3-2~bpo70+1 (2014-09-21)
[0.00] memsize=256, highmemsize=768
[0.00] CpuClock = 66634
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 6302 (ICT Loongson-2)
[0.00] FPU revision is: 0501
[0.00] Checking for the multiply/shift bug... no.
[0.00] Checking for the daddiu bug... no.
[0.00] Determined physical RAM map:
[0.00]  memory: 1000 @  (usable)
[0.00]  memory: 0400 @ 1000 (reserved)
[0.00]  memory: 3000 @ 2000 (usable)
[0.00]  memory: 03ff @ 1c01 (reserved)
[0.00] Initial ramdisk at: 0x980002c5 (14057094 bytes)
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x00ff]
[0.00]   Normal   [mem 0x0100-0x4fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x13ff]
[0.00]   node   0: [mem 0x1c004000-0x4fff]
[0.00] Reserving 0MB of memory at 0MB for crashkernel
[0.00] Primary instruction cache 64kB, VIPT, direct mapped, linesize 32 
bytes.
[0.00] Primary data cache 64kB, 4-way, VIPT, no aliases, linesize 32 
bytes
[0.00] Unified secondary cache 512kB 4-way, linesize 32 bytes.
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 73474
[0.00] Kernel command line: machtype=lemote-fuloong-2e-unknown 
root=/dev/sda2 console=ttyS0,115200 ro rd_start=0x82c5 rd_size=0xd67e86 
[0.00] PID hash table entries: 4096 (order: 1, 32768 bytes)
[0.00] Dentry cache hash table entries: 262144 (order: 7, 2097152 bytes)
[0.00] Inode-cache hash table entries: 131072 (order: 6, 1048576 bytes)
[0.00] Memory: 985344K/1179632K available (K kernel code, 701K 
rwdata, 1536K rodata, 496K init, 33345K bss, 194288K reserved)
[0.00] NR_IRQS:128
[0.00] Console: colour dummy device 80x25
[0.004000] Calibrating delay loop... 443.90 BogoMIPS (lpj=887808)
[0.032000] pid_max: default: 32768 minimum: 301
[0.036000] Security Framework initialized
[0.04] AppArmor: AppArmor disabled by boot time parameter
[0.044000] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.048000] Mount-cache hash table entries: 4096 (order: 1, 32768 bytes)
[0.052000] Mountpoint-cache hash table entries: 4096 (order: 1, 32768 bytes)
[0.056000] Initializing cgroup subsys memory
[0.06] Initializing cgroup subsys devices
[0.064000] Initializing cgroup subsys freezer
[0.068000] Initializing cgroup subsys net_cls
[0.072000] Initializing cgroup subsys blkio
[0.076000] Initializing cgroup subsys perf_event
[0.08] Initializing cgroup subsys net_prio
[0.084000] Checking for the daddi bug... no.
[0.088000] ftrace: allocating 17522 entries in 18 pages
[0.14] devtmpfs: initialized
[0.152000] NET: Registered protocol family 16
[0.176000] vgaarb: loaded
[0.176000] SCSI subsystem initialized
[0.18] PCI host bridge to bus :00
[0.184000] pci_bus :00: root bus resource [mem 0x1400-0x1c00]
[0.188000] pci_bus :00: root bus resource [io  0x4000-0x]
[0.192000] pci_bus :00: No busn resource found for root bus, will use 
[bus 00-ff]
[0.196000] via686b fix: ISA bridge
[0.196000] via686b fix: ISA bridge done
[0.20] pci :00:05.1: legacy IDE quirk: reg 0x10: [io  0x01f0-0x01f7]
[0.204000] pci :00:05.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
[0.208000] pci :00:05.1: legacy IDE quirk: reg 0x18: [io  0x0170-0x0177]
[0.212000] pci :00:05.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
[0.216000] via686b fix: IDE
[0.216000] via686b fix: IDE done
[0.22] pci :00:05.4: quirk: [io  0xeee0-0xeeef] claimed by vt82c686 
SMB
[0.224000] vgaarb: device added: 
PCI::00:06.0,decodes=io+mem,owns=io+mem,locks=none
[0.228000] pci :00:06.0: BAR 0: assigned [mem 0x1400-0x15ff 
pref]
[0.232000] pci :00:06.0: BAR 6: assigned [mem 0x1600-0x1601 
pref]
[0.236000] pci :00:07.0: BAR 6: assigned [mem 0x1602-0x1603 
pref]
[0.24] pci :00:06.0: BAR 2: assigned [mem 0x1604-0x1604]
[

Bug#764223: booting eder.debian.org fails

2014-10-06 Thread Ben Hutchings
On Mon, 2014-10-06 at 13:20 +, 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.70] 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 : 8000 803f4f98 8095 
 80953908
     8074cec8 8080b267
   0001 0040 10d1 
    8080  806582d0
    98004e0777f8 10d1 801781cc
   98004e073930 8074cec8  
     00ff8080b226 
    98004e077750  801f6904
    b54c6fb4 10d1 
   0001 80109c60 8088ef28 801f6904
   ...
 [4.784000] Call Trace:
 [4.788000] [80109c60] show_stack+0x78/0x90
 [4.792000] [801f6904] warn_alloc_failed+0xfc/0x140
 [4.80] [801f9f7c] __alloc_pages_nodemask+0x7c4/0xa30
 [4.808000] [801fa20c] __get_free_pages+0x24/0xa0
 [4.812000] [80119bec] mips_dma_alloc_coherent+0x10c/0x1e0
 [4.82] [804ac320] dmam_alloc_coherent+0x80/0xf8
 [4.824000] [804ec978] 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.


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