Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Samuel Thibault]

Control: tags -1 + pending

Ryan Tandy, le mar. 04 mai 2021 22:00:06 -0700, a ecrit:
> lowmem=2 worked nicely. I completed an installation successfully with that
> setting. Thanks!

Ok.

> Is there anything I can do to help improve the default experience on this
> target, besides documenting for others the process to set the extra bootarg
> in the u-boot environment?

I have already commited a patch to the manual to point people at the
lowmem parameter.

Thanks for your report,
Samuel

Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Ryan Tandy]

lowmem=2 worked nicely. I completed an installation successfully with 
that setting. Thanks!


Is there anything I can do to help improve the default experience on 
this target, besides documenting for others the process to set the extra 
bootarg in the u-boot environment?


thanks for your work on d-i,
Ryan

Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Samuel Thibault]

Hello,

Ryan Tandy, le mar. 27 avril 2021 22:16:00 -0700, a ecrit:
> The Linkstation Pro is an orion5x NAS with 128MB RAM. I checked the 
> Installation Guide; it says that the installer's memory requirement is 
> 80 MB. https://www.debian.org/releases/testing/armel/ch02s05.en.html

I guess we need to have a way to mark these numbers as outdated, since I
don't have the hardware/motivation to update for each and every
architecture.

> I am booting this network-console image over TFTP... I guess there's no 
> easy way to provide the 'lowmem' boot parameter.

There is, otherwise it'd be really a pain to update the figures :)

You can pass as boot parameter lowmem=1 or even lowmem=2

I'll add that to the installation guide.

Samuel

Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Ryan Tandy]

Hi, thanks for the quick follow-up.

On Wed, Apr 28, 2021 at 07:35:00AM +0200, Cyril Brulebois wrote:

Or are you already aware of this, and don't know how to pass the extra
option via TFTP?


The latter: I don't have any access to the bootloader (serial or 
otherwise) so I don't think I have a way to append kernel args for TFTP 
boot.


I've just remembered, though, that the config-debian script that lives 
beside the images demonstrates how to change the bootloader config, so I 
can probably do it that way if I put the installer images on disk. I'll 
try that next (pending figuring out why fw_printenv/setenv seem to be 
unhappy with my fw_env.config).

Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Cyril Brulebois]

Hi Ryan,

Ryan Tandy  (2021-04-27):
> I am booting this network-console image over TFTP... I guess there's no 
> easy way to provide the 'lowmem' boot parameter. I'd have to modify and 
> rebuild the install image (probably the initrd)?

I don't know anything about lowmem, but glancing at its code, I think
you can?


https://salsa.debian.org/installer-team/lowmem/-/blob/master/debian-installer-startup.d/S15lowmem#L112-119

Or are you already aware of this, and don't know how to pass the extra
option via TFTP?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Ryan Tandy]

Package: installation-reports
Severity: important
Tags: d-i

Dear Maintainer,

Bullseye RC1 fails to install on my Linkstation Pro (LS-GL). It runs out 
of memory just after confirming the partitions, when it starts to format 
the disk, and the installation process gets killed. Ironically, I think 
this is happening only seconds before it would format and activate the 
swap partition.

The Linkstation Pro is an orion5x NAS with 128MB RAM. I checked the 
Installation Guide; it says that the installer's memory requirement is 
80 MB. https://www.debian.org/releases/testing/armel/ch02s05.en.html

The installation images were retrieved from: 
https://deb.debian.org/debian/dists/testing/main/installer-armel/current/images/orion5x/network-console/buffalo/lspro_ls-gl/

I have (re-)installed buster successfully. The installation process uses 
some swap (especially during 'apt-get update') but does eventually 
complete. I upgraded it to bullseye, no problem.

I am attaching the full syslog from a failed attempt at installing 
bullseye. Please let me know if I can provide any other information.

I am booting this network-console image over TFTP... I guess there's no 
easy way to provide the 'lowmem' boot parameter. I'd have to modify and 
rebuild the install image (probably the initrd)?

thanks,
Ryan
Jan  1 00:00:16 syslogd started: BusyBox v1.30.1
Jan  1 00:00:16 kernel: klogd started: BusyBox v1.30.1 (Debian 1:1.30.1-6+b1)
Jan  1 00:00:16 kernel: [0.00] Booting Linux on physical CPU 0x0
Jan  1 00:00:16 kernel: [0.00] Linux version 5.10.0-6-marvell 
(debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU 
ld (GNU Binutils for Debian) 2.35.2) #1 Debian 5.10.28-1 (2021-04-09)
Jan  1 00:00:16 kernel: [0.00] CPU: Feroceon [41069260] revision 0 
(ARMv5TEJ), cr=a005317f
Jan  1 00:00:16 kernel: [0.00] CPU: VIVT data cache, VIVT instruction 
cache
Jan  1 00:00:16 kernel: [0.00] OF: fdt: Machine model: Buffalo 
Linkstation Pro/Live
Jan  1 00:00:16 kernel: [0.00] Memory policy: Data cache writeback
Jan  1 00:00:16 kernel: [0.00] Zone ranges:
Jan  1 00:00:16 kernel: [0.00]   Normal   [mem 
0x-0x07ff]
Jan  1 00:00:16 kernel: [0.00]   HighMem  empty
Jan  1 00:00:16 kernel: [0.00] Movable zone start for each node
Jan  1 00:00:16 kernel: [0.00] Early memory node ranges
Jan  1 00:00:16 kernel: [0.00]   node   0: [mem 
0x-0x07ff]
Jan  1 00:00:16 kernel: [0.00] Initmem setup node 0 [mem 
0x-0x07ff]
Jan  1 00:00:16 kernel: [0.00] On node 0 totalpages: 32768
Jan  1 00:00:16 kernel: [0.00]   Normal zone: 256 pages used for memmap
Jan  1 00:00:16 kernel: [0.00]   Normal zone: 0 pages reserved
Jan  1 00:00:16 kernel: [0.00]   Normal zone: 32768 pages, LIFO batch:7
Jan  1 00:00:16 kernel: [0.00] pcpu-alloc: s0 r0 d32768 u32768 
alloc=1*32768
Jan  1 00:00:16 kernel: [0.00] pcpu-alloc: [0] 0 
Jan  1 00:00:16 kernel: [0.00] Built 1 zonelists, mobility grouping on. 
 Total pages: 32512
Jan  1 00:00:16 kernel: [0.00] Kernel command line: 
console=ttyS0,115200 root=/dev/sda2 rw initrd=0x00800040,15M panic=5 
BOOTVER=1.10 tftpboot=yes
Jan  1 00:00:16 kernel: [0.00] Dentry cache hash table entries: 16384 
(order: 4, 65536 bytes, linear)
Jan  1 00:00:16 kernel: [0.00] Inode-cache hash table entries: 8192 
(order: 3, 32768 bytes, linear)
Jan  1 00:00:16 kernel: [0.00] mem auto-init: stack:off, heap alloc:on, 
heap free:off
Jan  1 00:00:16 kernel: [0.00] Memory: 106908K/131072K available (4732K 
kernel code, 830K rwdata, 1312K rodata, 292K init, 224K bss, 24164K reserved, 
0K cma-reserved, 0K highmem)
Jan  1 00:00:16 kernel: [0.00] random: get_random_u32 called from 
cache_random_seq_create+0x60/0x110 with crng_init=0
Jan  1 00:00:16 kernel: [0.00] SLUB: HWalign=32, Order=0-3, 
MinObjects=0, CPUs=1, Nodes=1
Jan  1 00:00:16 kernel: [0.00] ftrace: allocating 8 entries in 44 
pages
Jan  1 00:00:16 kernel: [0.00] ftrace: allocated 44 pages with 3 groups
Jan  1 00:00:16 kernel: [0.00] NR_IRQS: 16, nr_irqs: 16, preallocated 
irqs: 16
Jan  1 00:00:16 kernel: [0.00] clocksource: orion_clocksource: mask: 
0x max_cycles: 0x, max_idle_ns: 11467562657 ns
Jan  1 00:00:16 kernel: [0.28] sched_clock: 32 bits at 166MHz, 
resolution 6ns, wraps every 12884901885ns
Jan  1 00:00:16 kernel: [0.000116] Switching to timer-based delay loop, 
resolution 6ns
Jan  1 00:00:16 kernel: [0.000349] Calibrating delay loop (skipped), value 
calculated using timer frequency.. 333.33 BogoMIPS (lpj=66)
Jan  1 00:00:16 kernel: [0.000417] pid_max: default: 32768 minimum: 301
Jan  1 00:00:16 kernel: [0.001220] LSM: Security Framework initializing
Jan  1 00:00:16 kernel: [0.001775] Yama: