Debian Bug report logs - #809611
armel: HP mv2120 requires change in u-boot setting

Package: release-notes; Maintainer for release-notes is Debian Documentation Team <debian-doc@lists.debian.org>;

Reported by: Martin Michlmayr <tbm@cyrius.com>

Date: Fri, 1 Jan 2016 19:54:01 UTC

Severity: important

Tags: patch

Done: Baptiste Jammet <baptiste@mailoo.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Fri, 01 Jan 2016 19:54:05 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
New Bug report received and forwarded. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Fri, 01 Jan 2016 19:54:05 GMT) (full text, mbox, link).


Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: submit@bugs.debian.org
Subject: d-i fails to boot on HP mv2120
Date: Fri, 1 Jan 2016 11:51:03 -0800
Package: debian-installer
Severity: important

Mike Thompson reports that the daily d-i image fails to boot on HP
mv2120:

----- Forwarded message from Mike Thompson <mpthompson@gmail.com> -----

From: Mike Thompson <mpthompson@gmail.com>

On Thu, Dec 31, 2015 at 10:01 AM, Martin Michlmayr <tbm@cyrius.com> wrote:
> Thanks, Mike.  That'd be great.
>
> You can find the daily images here:
>
> http://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/hp/mv2120/
>
> Please let me know if you run into any problems (or if things work).


Hi Martin,

I gave the daily image you linked to above a go on the MV2120, but
unfortunately it failed.  Looking at the bottom of the trace there is some
problem mounting the root filesystem for the install image.

Output from the serial console is below:

------------------------------------------------------------------------------------
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** Forcing LOADER mode only **
 ** MARVELL BOARD: RD-88F5182-NAS-P2 LE

U-Boot 1.1.4 (Oct 12 2007 - 12:30:28) Marvell version:
2.3.11_HP_1_3_1_Built@HP

U-Boot code: 00200000 -> 0026FFF0  BSS: -> 0027FDBC

Soc: 88F5182 A2 (DDR2)
CPU running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  32bit width
[512kB@fff80000] Flash: 512 kB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done

CPU : ARM926 (Rev 0)
88F5182 A2 streaming disabled
USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
Net:   egiga0 [PRIME]
Aquiring an IP address using DHCP...
Link is down... Waiting 2 seconds and trying again
egiga0 no link after waiting 2 seconds
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Retry count exceeded; starting again
Failed to retreive an IP address assuming default (192.168.0.8)!
Starting the Recovery process to retreive the file...
Broadcasting Distress Beacon Packet.
New TFTP PUT request received from 192.168.0.2 (MAC b8:27:eb:9b:12:ea)
Recovery Image received (8384726 bytes).
Booting the image (@ 0x400000) with RamDisk (@ 0x600000)...
## Booting image at 00400000 ...
   Image Name:   Debian kernel
   Created:      2015-12-31   0:09:38 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1988600 Bytes =  1.9 MB
   Load Address: 01000000
   Entry Point:  01000000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00600000 ...
   Image Name:   Debian installer
   Created:      2015-12-31   0:09:38 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    6286998 Bytes =  6 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.3.0-1-orion5x (debian-kernel@lists.debian.org)
(gcc version 4.9.3 (Debian 4.9.3-10) ) #1 Debian 4.3.3-2 (2015-12-17)
[    0.000000] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a005317f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: HP Media Vault mv2120
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x41000403
[    0.000000] INITRD: 0x00600040+0x005fee96 overlaps in-use memory region
- disabling initrd
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536
bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 123416K/131072K available (4086K kernel code, 422K
rwdata, 1364K rodata, 300K init, 282K bss, 7656K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc055abf0   (5451 kB)
[    0.000000]       .init : 0xc055b000 - 0xc05a6000   ( 300 kB)
[    0.000000]       .data : 0xc05a6000 - 0xc060fa60   ( 423 kB)
[    0.000000]        .bss : 0xc060fa60 - 0xc065632c   ( 283 kB)
[    0.000000] NR_IRQS:65
[    0.000025] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every
12884901885ns
[   14.996063] clocksource: orion_clocksource: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 11467562657 ns
[   14.996871] Console: colour dummy device 80x30
[   14.996927] Calibrating delay loop... 329.98 BogoMIPS (lpj=659968)
[   15.032160] pid_max: default: 32768 minimum: 301
[   15.032406] Security Framework initialized
[   15.032433] Yama: disabled by default; enable with sysctl kernel.yama.*
[   15.032616] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   15.032649] Mountpoint-cache hash table entries: 1024 (order: 0, 4096
bytes)
[   15.034487] Initializing cgroup subsys io
[   15.034569] Initializing cgroup subsys devices
[   15.034615] Initializing cgroup subsys freezer
[   15.034661] Initializing cgroup subsys net_cls
[   15.034715] Initializing cgroup subsys perf_event
[   15.034768] Initializing cgroup subsys net_prio
[   15.034903] CPU: Testing write buffer coherency: ok
[   15.035178] ftrace: allocating 15624 entries in 46 pages
[   15.114219] Setting up static identity map for 0x8200 - 0x823c
[   15.119780] devtmpfs: initialized
[   15.122685] VFP support v0.3: not present
[   15.123233] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 7645041785100000 ns
[   15.124279] pinctrl core: initialized pinctrl subsystem
[   15.126053] NET: Registered protocol family 16
[   15.127155] DMA: preallocated 256 KiB pool for atomic coherent
allocations
[   15.129399] Orion ID: MV88F5182-A2. TCLK=166666667.
[   15.145782] clocksource: Switched to clocksource orion_clocksource
[   15.296680] NET: Registered protocol family 2
[   15.298749] TCP established hash table entries: 1024 (order: 0, 4096
bytes)
[   15.298818] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[   15.298871] TCP: Hash tables configured (established 1024 bind 1024)
[   15.299056] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   15.299121] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   15.299705] NET: Registered protocol family 1
[   15.302704] futex hash table entries: 256 (order: -1, 3072 bytes)
[   15.302941] audit: initializing netlink subsys (disabled)
[   15.303086] audit: type=2000 audit(0.284:1): initialized
[   15.304905] zbud: loaded
[   15.305864] VFS: Disk quotas dquot_6.6.0
[   15.306038] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
[   15.311595] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 252)
[   15.312141] io scheduler noop registered
[   15.312289] io scheduler cfq registered (default)
[   15.313536] mv_xor mv_xor.0: Marvell shared XOR driver
[   15.345025] mv_xor mv_xor.0: Marvell XOR (Registers Mode): ( xor cpy )
[   15.346081] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   15.347944] console [ttyS0] disabled
[   15.368029] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 4, base_baud =
10416666) is a 16550A
[   15.828432] console [ttyS0] enabled
[   15.834242] physmap platform flash device: 00080000 at f4000000
[   15.840441] physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank.
Manufacturer ID 0x0000c2 Chip ID 0x0000b9
[   15.850701] Amd/Fujitsu Extended Query Table at 0x0040
[   15.855894]   Amd/Fujitsu Extended Query version 1.0.
[   15.860993] physmap-flash.0: JEDEC Device ID is 0xB9. Assuming broken
CFI table.
[   15.868423] physmap-flash.0: Swapping erase regions for top-boot CFI
table.
[   15.875432] number of CFI chips: 1
[   15.880199] Creating 1 MTD partitions on "physmap-flash.0":
[   15.885891] 0x000000000000-0x000000080000 : "firmware"
[   15.895536] mousedev: PS/2 mouse device common for all mice
[   15.902204] i2c /dev entries driver
[   15.906944] rtc-pcf8563 0-0051: chip found, driver version 0.4.4
[   15.917315] rtc rtc0: invalid alarm value: 2016-1-2 32:5:0
[   15.923362] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[   15.932216] ledtrig-cpu: registered to indicate activity on CPUs
[   15.939368] NET: Registered protocol family 17
[   15.945914] registered taskstats version 1
[   15.950410] zswap: loaded using pool lzo/zbud
[   15.957087] rtc-pcf8563 0-0051: setting system clock to 2015-12-31
21:08:49 UTC (1451596129)
[   15.966823] List of all partitions:
[   15.970423] 1f00             512 mtdblock0  (driver?)
[   15.975526] No filesystem could mount root, tried:
[   15.980464] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[   15.988712] CPU: 0 PID: 1 Comm: swapper Not tainted 4.3.0-1-orion5x #1
Debian 4.3.3-2
[   15.996509] Hardware name: HP Media Vault mv2120
[   16.001184] [<c0016dcc>] (unwind_backtrace) from [<c00137a0>]
(show_stack+0x20/0x24)
[   16.008950] [<c00137a0>] (show_stack) from [<c01ebfc4>]
(dump_stack+0x20/0x28)
[   16.016186] [<c01ebfc4>] (dump_stack) from [<c00cef78>]
(panic+0x8c/0x214)
[   16.023075] [<c00cef78>] (panic) from [<c055c390>]
(mount_block_root+0x2a0/0x2f0)
[   16.030562] [<c055c390>] (mount_block_root) from [<c055c444>]
(mount_root+0x64/0x80)
[   16.038312] [<c055c444>] (mount_root) from [<c055c590>]
(prepare_namespace+0x130/0x190)
[   16.046323] [<c055c590>] (prepare_namespace) from [<c055bf30>]
(kernel_init_freeable+0x1d0/0x224)
[   16.055208] [<c055bf30>] (kernel_init_freeable) from [<c03a1754>]
(kernel_init+0x18/0xf4)
[   16.063398] [<c03a1754>] (kernel_init) from [<c000fad0>]
(ret_from_fork+0x14/0x24)
[   16.070961] ---[ end Kernel panic - not syncing: VFS: Unable to mount
root fs on unknown-block(0,0)
[   48.093854] random: nonblocking pool is initialized
¦¦
------------------------------------------------------------------------------------

Hopefully it's something easy to diagnose.  I'll give it another try when
you think there is a daily image that may fix the issue.  Let me know if
there is anything else that may help track down what went wrong.

Mike Thompson

----- End forwarded message -----

-- 
Martin Michlmayr
http://www.cyrius.com/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sat, 02 Jan 2016 00:09:08 GMT) (full text, mbox, link).


Acknowledgement sent to Geert Stappers <stappers@stappers.nl>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sat, 02 Jan 2016 00:09:08 GMT) (full text, mbox, link).


Message #10 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Geert Stappers <stappers@stappers.nl>
To: 809611@bugs.debian.org
Cc: Mike Thompson <mpthompson@gmail.com>, Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sat, 2 Jan 2016 01:04:47 +0100
> 
> Output from the serial console is below:
> 
> ------------------------------------------------------------------------------------
>          __  __                      _ _
>         |  \/  | __ _ _ ____   _____| | |
>         | |\/| |/ _` | '__\ \ / / _ \ | |
>         | |  | | (_| | |   \ V /  __/ | |
>         |_|  |_|\__,_|_|    \_/ \___|_|_|
>  _   _     ____              _
> | | | |   | __ )  ___   ___ | |_
> | | | |___|  _ \ / _ \ / _ \| __|
> | |_| |___| |_) | (_) | (_) | |_
>  \___/    |____/ \___/ \___/ \__|  ** Forcing LOADER mode only **
>  ** MARVELL BOARD: RD-88F5182-NAS-P2 LE
> 
> U-Boot 1.1.4 (Oct 12 2007 - 12:30:28) Marvell version:
> 2.3.11_HP_1_3_1_Built@HP
> 
> U-Boot code: 00200000 -> 0026FFF0  BSS: -> 0027FDBC
   <snip/> 
> Booting the image (@ 0x400000) with RamDisk (@ 0x600000)...
> ## Booting image at 00400000 ...
>    Image Name:   Debian kernel
>    Created:      2015-12-31   0:09:38 UTC
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    1988600 Bytes =  1.9 MB
>    Load Address: 01000000
>    Entry Point:  01000000
>    Verifying Checksum ... OK
> OK
> ## Loading Ramdisk Image at 00600000 ...
>    Image Name:   Debian installer
>    Created:      2015-12-31   0:09:38 UTC
>    Image Type:   ARM Linux RAMDisk Image (uncompressed)
>    Data Size:    6286998 Bytes =  6 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
> 
> Starting kernel ...
> 
> Uncompressing Linux... done, booting the kernel.
    <snip/>
> [    0.000000] Kernel command line: console=ttyS0,115200

Only 'console=...'

    <snip/>
> [    0.000000] Virtual kernel memory layout:
> [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
> [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
> [    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
> [    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
> [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
> [    0.000000]       .text : 0xc0008000 - 0xc055abf0   (5451 kB)
> [    0.000000]       .init : 0xc055b000 - 0xc05a6000   ( 300 kB)
> [    0.000000]       .data : 0xc05a6000 - 0xc060fa60   ( 423 kB)
> [    0.000000]        .bss : 0xc060fa60 - 0xc065632c   ( 283 kB)
> [    0.000000] NR_IRQS:65
> [    0.000025] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns

12884901885ns
12884901us (micro)
12884ms
12s

those twelve secondes _might_ explain twelve seconds.

but from 12 seconds to almost 15 seconds, still lacks three seconds.

I wonder what happens between '[    0.000025]' and '[   14.996063]'
It is out of curiosity. The gap in logging is not the reason for te boot failure.


> [   14.996063] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: > 0xffffffff, max_idle_ns: 11467562657 ns
         <snip/>
> [   15.957087] rtc-pcf8563 0-0051: setting system clock to 2015-12-31 21:08:49 UTC (1451596129)
> [   15.966823] List of all partitions:
> [   15.970423] 1f00             512 mtdblock0  (driver?)
> [   15.975526] No filesystem could mount root, tried:
> [   15.980464] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
         <snip/>
> ------------------------------------------------------------------------------------
> Hopefully it's something easy to diagnose.

My diagnose: 'No filesystem could mount root'.
My _guess_: uboot and kernel+initrd don't understand each other.

Thing I would try: adding a root= parameter to uboot to hand over to kernel+initrd.


Groeten
Geert Stappers
-- 
Leven en laten leven



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sat, 02 Jan 2016 00:45:08 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sat, 02 Jan 2016 00:45:08 GMT) (full text, mbox, link).


Message #15 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: Geert Stappers <stappers@stappers.nl>
Cc: 809611@bugs.debian.org, Mike Thompson <mpthompson@gmail.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Fri, 1 Jan 2016 16:40:33 -0800
Geert, I'm looking into it already.  Sorry, I should have mentioned
that.

-- 
Martin Michlmayr
http://www.cyrius.com/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sat, 02 Jan 2016 03:33:08 GMT) (full text, mbox, link).


Acknowledgement sent to "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sat, 02 Jan 2016 03:33:08 GMT) (full text, mbox, link).


Message #20 received at 809611@bugs.debian.org (full text, mbox, reply):

From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: Geert Stappers <stappers@stappers.nl>, 809611@bugs.debian.org
Cc: Mike Thompson <mpthompson@gmail.com>, Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Fri, 1 Jan 2016 22:23:34 -0500
On Sat, Jan 02, 2016 at 01:04:47AM +0100, Geert Stappers wrote:
> > 
> > Output from the serial console is below:
> > 
> > ------------------------------------------------------------------------------------
> >          __  __                      _ _
> >         |  \/  | __ _ _ ____   _____| | |
> >         | |\/| |/ _` | '__\ \ / / _ \ | |
> >         | |  | | (_| | |   \ V /  __/ | |
> >         |_|  |_|\__,_|_|    \_/ \___|_|_|
> >  _   _     ____              _
> > | | | |   | __ )  ___   ___ | |_
> > | | | |___|  _ \ / _ \ / _ \| __|
> > | |_| |___| |_) | (_) | (_) | |_
> >  \___/    |____/ \___/ \___/ \__|  ** Forcing LOADER mode only **
> >  ** MARVELL BOARD: RD-88F5182-NAS-P2 LE
> > 
> > U-Boot 1.1.4 (Oct 12 2007 - 12:30:28) Marvell version:
> > 2.3.11_HP_1_3_1_Built@HP
> > 
> > U-Boot code: 00200000 -> 0026FFF0  BSS: -> 0027FDBC
>    <snip/> 
> > Booting the image (@ 0x400000) with RamDisk (@ 0x600000)...
> > ## Booting image at 00400000 ...
> >    Image Name:   Debian kernel
> >    Created:      2015-12-31   0:09:38 UTC
> >    Image Type:   ARM Linux Kernel Image (uncompressed)
> >    Data Size:    1988600 Bytes =  1.9 MB
> >    Load Address: 01000000
> >    Entry Point:  01000000
> >    Verifying Checksum ... OK
> > OK
> > ## Loading Ramdisk Image at 00600000 ...
> >    Image Name:   Debian installer
> >    Created:      2015-12-31   0:09:38 UTC
> >    Image Type:   ARM Linux RAMDisk Image (uncompressed)
> >    Data Size:    6286998 Bytes =  6 MB
> >    Load Address: 00000000
> >    Entry Point:  00000000
> >    Verifying Checksum ... OK
> > 
> > Starting kernel ...
> > 
> > Uncompressing Linux... done, booting the kernel.
>     <snip/>
> > [    0.000000] Kernel command line: console=ttyS0,115200
> 
> Only 'console=...'
> 
>     <snip/>
> > [    0.000000] Virtual kernel memory layout:
> > [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
> > [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
> > [    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
> > [    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
> > [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
> > [    0.000000]       .text : 0xc0008000 - 0xc055abf0   (5451 kB)
> > [    0.000000]       .init : 0xc055b000 - 0xc05a6000   ( 300 kB)
> > [    0.000000]       .data : 0xc05a6000 - 0xc060fa60   ( 423 kB)
> > [    0.000000]        .bss : 0xc060fa60 - 0xc065632c   ( 283 kB)
> > [    0.000000] NR_IRQS:65
> > [    0.000025] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
> 
> 12884901885ns
> 12884901us (micro)
> 12884ms
> 12s
> 
> those twelve secondes _might_ explain twelve seconds.
> 
> but from 12 seconds to almost 15 seconds, still lacks three seconds.
> 
> I wonder what happens between '[    0.000025]' and '[   14.996063]'
> It is out of curiosity. The gap in logging is not the reason for te boot failure.

The 'wraps every x' output from the kernel is as far as I can tell
complete nonsense.  I think there is a bug in the calculation, but I
haven't been able to figure out what it is yet (I think it might be an
overflow in one of the steps in the calculation).

Certainly here, 166MHz should be able to go 24 seconds in 32bits,
unless it is signed and resets to 0, which would really be 31 bits then.
And on systems with 56 or 64bit counters, it still claims to wrap in a
few minutes when in fact it should last decades if you do the math.

-- 
Len Sorensen



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sun, 31 Jul 2016 02:21:04 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sun, 31 Jul 2016 02:21:04 GMT) (full text, mbox, link).


Message #25 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: 809611@bugs.debian.org
Cc: Mike Thompson <mpthompson@gmail.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sat, 30 Jul 2016 19:06:35 -0700
Here's an explanation of this problem.  I'll send another email with
instructions for users.

By default, the kernel is loaded to 0x0400000 and the ramdisk exactly
2 MB behind that location.  For some reason, it fails with stretch.
However, changing the load address to 0x0500000 or 0x0600000 makes it
work.  I don't think it's clear why since the ramdisk is still loaded
exactly 2 MB after the kernel.

The load address is in two u-boot configs: loadAddr and bootcmd.  We
adjust them to 0x0600000.  This is something the user has to do
manually.  I couldn't find a way to workaround the problem by changing
the installer or flash-kernel.

At the moment, debian-installer and mv2120-recovery-image use
0x01000000 as the load address.  This means the combined
kernel+ramdisk can only be 10 MB.  Let's change 0x01000000 to
0x01600000 to allow for a larger ramdisk.  Note that flash-kernel
already uses 0x01600000

-- 
Martin Michlmayr
http://www.cyrius.com/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sun, 31 Jul 2016 02:27:04 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sun, 31 Jul 2016 02:27:04 GMT) (full text, mbox, link).


Message #30 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: Mike Thompson <mpthompson@gmail.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sat, 30 Jul 2016 19:23:02 -0700
Mike, can you please give these instructions a go?  This is what I
intend to post to the mv2120 list.

--

Mike Thompson reported that Debian stretch (the upcoming Debian 9)
doesn't boot on the HP mv2120 anymore.  I don't know how many Debian
users are left who run Debian on their mv2120.  I gave away my device
several years ago.  Recently I bought an mv2120 from eBay in order to
debug this issue.

While I found a solution, it requires users to change a setting on their
device.  Please make sure to make this change, otherwise your device
will no longer boot when you upgrade to Debian 9.

The new settings are compatible with Debian 8 (jessie) and Debian 9
(stretch), so I suggest you make the changes now.

If you have serial console access to the mv2120, you can run some
commands in u-boot.  Simply interrupt the boot process by pressing a key
and type the following:

    setenv loadAddr 0x0600000
    setenv bootcmd 'bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda /dev/sdb'
    saveenv

If you don't have a serial console, you can make the changes from within
Debian.  Run the following commands:

    cat >/etc/fw_env.config <<EOF
    /dev/mtd0           0x00000         0x1000     0x20000
    EOF

    fw_setenv loadAddr 0x0600000
    fw_setenv bootcmd "bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda /dev/sdb"

This will create a config file so you can modify the u-boot environment
and use fw_setenv to update two boot variables.

Once you made the changes, upgrades to Debian 9 should work fine and you
can also use the Debian installer if you want to perform a new
installation.

Please note that Debian 9 will be the last release to support the HP
mv2120.

--

Note that the installer from
https://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/hp/mv2120/netboot.img
will not boot right now with these settings.  However, you can change the
loadAddr to 0x0500000 and it should work.  I just commited a fix in Git so
it should work in a day or so with 0x0600000.

-- 
Martin Michlmayr
http://www.cyrius.com/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sun, 31 Jul 2016 20:03:03 GMT) (full text, mbox, link).


Acknowledgement sent to Mike Thompson <mpthompson@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sun, 31 Jul 2016 20:03:03 GMT) (full text, mbox, link).


Message #35 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Mike Thompson <mpthompson@gmail.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sun, 31 Jul 2016 12:58:20 -0700
[Message part 1 (text/plain, inline)]
Hi Martin,

Sure.  It may take me a few days to get some time, but I'll give it a try
and let you know how it goes.

Mike

On Sat, Jul 30, 2016 at 7:23 PM, Martin Michlmayr <tbm@cyrius.com> wrote:

> Mike, can you please give these instructions a go?  This is what I
> intend to post to the mv2120 list.
>
> --
>
> Mike Thompson reported that Debian stretch (the upcoming Debian 9)
> doesn't boot on the HP mv2120 anymore.  I don't know how many Debian
> users are left who run Debian on their mv2120.  I gave away my device
> several years ago.  Recently I bought an mv2120 from eBay in order to
> debug this issue.
>
> While I found a solution, it requires users to change a setting on their
> device.  Please make sure to make this change, otherwise your device
> will no longer boot when you upgrade to Debian 9.
>
> The new settings are compatible with Debian 8 (jessie) and Debian 9
> (stretch), so I suggest you make the changes now.
>
> If you have serial console access to the mv2120, you can run some
> commands in u-boot.  Simply interrupt the boot process by pressing a key
> and type the following:
>
>     setenv loadAddr 0x0600000
>     setenv bootcmd 'bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda
> /dev/sdb'
>     saveenv
>
> If you don't have a serial console, you can make the changes from within
> Debian.  Run the following commands:
>
>     cat >/etc/fw_env.config <<EOF
>     /dev/mtd0           0x00000         0x1000     0x20000
>     EOF
>
>     fw_setenv loadAddr 0x0600000
>     fw_setenv bootcmd "bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda
> /dev/sdb"
>
> This will create a config file so you can modify the u-boot environment
> and use fw_setenv to update two boot variables.
>
> Once you made the changes, upgrades to Debian 9 should work fine and you
> can also use the Debian installer if you want to perform a new
> installation.
>
> Please note that Debian 9 will be the last release to support the HP
> mv2120.
>
> --
>
> Note that the installer from
>
> https://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/hp/mv2120/netboot.img
> will not boot right now with these settings.  However, you can change the
> loadAddr to 0x0500000 and it should work.  I just commited a fix in Git so
> it should work in a day or so with 0x0600000.
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>
[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sat, 06 Aug 2016 03:27:05 GMT) (full text, mbox, link).


Acknowledgement sent to Mike Thompson <mpthompson@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sat, 06 Aug 2016 03:27:05 GMT) (full text, mbox, link).


Message #40 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Mike Thompson <mpthompson@gmail.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Fri, 5 Aug 2016 20:23:38 -0700
[Message part 1 (text/plain, inline)]
Hi Martin,

I attempted a network installation on an MV1220 currently running Jessie
following your instructions regarding setting the load address of 0x600000
and the netboot.img from the following location from the daily builds:

https://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/hp/mv2120/

The good news is that given the load address change from 0x400000 to
0x600000 allowed the MV2120 to boot into the ssh based installer.

The bad news is the installed failed from what looked like some sort of
segmentation faults in the installer from the looks of the logs which I
included below.

Below is the error I received:


     lqqqqqqqqqqqqqqqqu [!!] Debian installer main menu tqqqqqqqqqqqqqqqqk
     x                                                                   x
     x                     Installation step failed                      x
     x An installation step failed. You can try to run the failing item  x
     x again from the menu, or skip it and choose something else. The    x
     x failing step is: Choose mirror to install from (menu item)        x
     x                                                                   x
     x                            <Continue>                             x
     x                                                                   x
     mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

Using the expert installation fails in just the same manner.

Attached below are the debug hardware summary and syslog which I hope are
useful:

Hardware Summary
-----------------------------------------------------------------------------
uname -a: Linux backup 4.6.0-1-marvell #1 Debian 4.6.4-1 (2016-07-18)
armv5tel GNU/Linux
lsmod: Module                  Size  Used by
lsmod: ext4                  495393  0
lsmod: crc16                   1229  1 ext4
lsmod: jbd2                   82552  1 ext4
lsmod: crc32c_generic          1561  0
lsmod: mbcache                 3990  1 ext4
lsmod: sd_mod                 30069  0
lsmod: sata_mv                25273  0
lsmod: libata                162527  1 sata_mv
lsmod: scsi_mod              176204  2 libata,sd_mod
lsmod: mvmdio                  3004  1
lsmod: mv643xx_eth            26419  0
lsmod: of_mdio                 5511  2 mvmdio,mv643xx_eth
lsmod: libphy                 27187  3 mvmdio,of_mdio,mv643xx_eth
df: Filesystem           1K-blocks      Used Available Use% Mounted on
df: none                     12404        20     12384   0% /run
df: devtmpfs                 57312         0     57312   0% /dev
free:              total         used         free       shared      buffers
free: Mem:        124020        38188        85832        21720            0
free: -/+ buffers:              38188        85832
free: Swap:            0            0            0
/proc/cmdline: console=ttyS0,115200
/proc/cpuinfo: processor : 0
/proc/cpuinfo: model name : Feroceon rev 0 (v5l)
/proc/cpuinfo: BogoMIPS : 333.33
/proc/cpuinfo: Features : swp half thumb fastmult edsp
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 5TEJ
/proc/cpuinfo: CPU variant : 0x0
/proc/cpuinfo: CPU part : 0x926
/proc/cpuinfo: CPU revision : 0
/proc/cpuinfo:
/proc/cpuinfo: Hardware : HP Media Vault mv2120
/proc/cpuinfo: Revision : 0000
/proc/cpuinfo: Serial : 0000000000000000
/proc/iomem: 00000000-07ffffff : System RAM
/proc/iomem:   00008000-00519923 : Kernel code
/proc/iomem:   00562000-0060648f : Kernel data
/proc/iomem: f1011000-f101101f : mv64xxx_i2c.0
/proc/iomem:   f1011000-f101101f : mv64xxx_i2c.0
/proc/iomem: f1012000-f10120ff : serial8250.0
/proc/iomem:   f1012000-f101201f : serial
/proc/iomem: f1020108-f102010b : orion_wdt
/proc/iomem: f1020300-f1020303 : orion_wdt
/proc/iomem: f1050000-f1050fff : orion-ehci.0
/proc/iomem: f1060900-f10609ff : xor 0 low
/proc/iomem: f1060b00-f1060bff : xor 0 high
/proc/iomem: f1072000-f1075fff : ge00 base
/proc/iomem:   f1072004-f1072087 : ge00 mvmdio base
/proc/iomem: f1080000-f1084fff : sata base
/proc/iomem: f1090000-f109ffff : regs
/proc/iomem: f10a0000-f10a0fff : orion-ehci.1
/proc/iomem: f2200000-f2201fff : sram
/proc/iomem: f4000000-f407ffff : physmap-flash.0
/proc/iomem:   f4000000-f407ffff : physmap-flash.0
/proc/interrupts:            CPU0
/proc/interrupts:   1:      14414  orion_irq Level     orion_tick
/proc/interrupts:   4:        745  orion_irq Level     serial
/proc/interrupts:   6:         97  orion_irq Level     mv64xxx_i2c
/proc/interrupts:  22:        284  orion_irq Level     eth0
/proc/interrupts:  23:       1180  orion_irq Level     orion-mdio
/proc/interrupts:  30:         67  orion_irq Level     sata_mv[sata_mv.0]
/proc/interrupts:  31:          2  orion_irq Level     mv_xor.0
/proc/interrupts:  36:          0  orion_gpio0  36 Edge      rtc-pcf8563
/proc/interrupts: Err:          0
/proc/meminfo: MemTotal:         124020 kB
/proc/meminfo: MemFree:           85804 kB
/proc/meminfo: MemAvailable:      84756 kB
/proc/meminfo: Buffers:               0 kB
/proc/meminfo: Cached:            21720 kB
/proc/meminfo: SwapCached:            0 kB
/proc/meminfo: Active:            21676 kB
/proc/meminfo: Inactive:           8276 kB
/proc/meminfo: Active(anon):      21676 kB
/proc/meminfo: Inactive(anon):     8276 kB
/proc/meminfo: Active(file):          0 kB
/proc/meminfo: Inactive(file):        0 kB
/proc/meminfo: Unevictable:           0 kB
/proc/meminfo: Mlocked:               0 kB
/proc/meminfo: HighTotal:             0 kB
/proc/meminfo: HighFree:              0 kB
/proc/meminfo: LowTotal:         124020 kB
/proc/meminfo: LowFree:           85804 kB
/proc/meminfo: SwapTotal:             0 kB
/proc/meminfo: SwapFree:              0 kB
/proc/meminfo: Dirty:                 0 kB
/proc/meminfo: Writeback:             0 kB
/proc/meminfo: AnonPages:          8284 kB
/proc/meminfo: Mapped:             6144 kB
/proc/meminfo: Shmem:             21720 kB
/proc/meminfo: Slab:               4180 kB
/proc/meminfo: SReclaimable:       1952 kB
/proc/meminfo: SUnreclaim:         2228 kB
/proc/meminfo: KernelStack:         472 kB
/proc/meminfo: PageTables:          496 kB
/proc/meminfo: NFS_Unstable:          0 kB
/proc/meminfo: Bounce:                0 kB
/proc/meminfo: WritebackTmp:          0 kB
/proc/meminfo: CommitLimit:       62008 kB
/proc/meminfo: Committed_AS:      37240 kB
/proc/meminfo: VmallocTotal:     901120 kB
/proc/meminfo: VmallocUsed:           0 kB
/proc/meminfo: VmallocChunk:          0 kB
-----------------------------------------------------------------------------

Syslog
-----------------------------------------------------------------------------
Aug  6 21:49:54 syslogd started: BusyBox v1.22.1
Aug  6 21:49:54 kernel: klogd started: BusyBox v1.22.1 (Debian 1:1.22.0-19)
Aug  6 21:49:54 kernel: [    0.000000] Booting Linux on physical CPU 0x0
Aug  6 21:49:54 kernel: [    0.000000] Linux version 4.6.0-1-marvell (
debian-kernel@lists.debian.org) (gcc version 5.4.0 20160609 (Debian
5.4.0-6) ) #1 Debian 4.6.4-1 (2016-07-18)
Aug  6 21:49:54 kernel: [    0.000000] CPU: Feroceon [41069260] revision 0
(ARMv5TEJ), cr=a005317f
Aug  6 21:49:54 kernel: [    0.000000] CPU: VIVT data cache, VIVT
instruction cache
Aug  6 21:49:54 kernel: [    0.000000] Machine: HP Media Vault mv2120
Aug  6 21:49:54 kernel: [    0.000000] Clearing invalid memory bank
0KB@0xffffffff
Aug  6 21:49:54 kernel: [    0.000000] Clearing invalid memory bank
0KB@0xffffffff
Aug  6 21:49:54 kernel: [    0.000000] Clearing invalid memory bank
0KB@0xffffffff
Aug  6 21:49:54 kernel: [    0.000000] Ignoring unrecognised tag 0x00000000
Aug  6 21:49:54 kernel: [    0.000000] Ignoring unrecognised tag 0x00000000
Aug  6 21:49:54 kernel: [    0.000000] Ignoring unrecognised tag 0x00000000
Aug  6 21:49:54 kernel: [    0.000000] Ignoring unrecognised tag 0x41000403
Aug  6 21:49:54 kernel: [    0.000000] Memory policy: Data cache writeback
Aug  6 21:49:54 kernel: [    0.000000] On node 0 totalpages: 32768
Aug  6 21:49:54 kernel: [    0.000000] free_area_init_node: node 0, pgdat
c05b3a2c, node_mem_map c7ef9000
Aug  6 21:49:54 kernel: [    0.000000]   Normal zone: 256 pages used for
memmap
Aug  6 21:49:54 kernel: [    0.000000]   Normal zone: 0 pages reserved
Aug  6 21:49:54 kernel: [    0.000000]   Normal zone: 32768 pages, LIFO
batch:7
Aug  6 21:49:54 kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768
alloc=1*32768
Aug  6 21:49:54 kernel: [    0.000000] pcpu-alloc: [0] 0
Aug  6 21:49:54 kernel: [    0.000000] Built 1 zonelists in Zone order,
mobility grouping on.  Total pages: 32512
Aug  6 21:49:54 kernel: [    0.000000] Kernel command line:
console=ttyS0,115200
Aug  6 21:49:54 kernel: [    0.000000] PID hash table entries: 512 (order:
-1, 2048 bytes)
Aug  6 21:49:54 kernel: [    0.000000] Dentry cache hash table entries:
16384 (order: 4, 65536 bytes)
Aug  6 21:49:54 kernel: [    0.000000] Inode-cache hash table entries: 8192
(order: 3, 32768 bytes)
Aug  6 21:49:54 kernel: [    0.000000] Memory: 114624K/131072K available
(3773K kernel code, 367K rwdata, 1416K rodata, 288K init, 289K bss, 16448K
reserved, 0K cma-reserved, 0K highmem)
Aug  6 21:49:54 kernel: [    0.000000] Virtual kernel memory layout:
Aug  6 21:49:54 kernel: [    0.000000]     vector  : 0xffff0000 -
0xffff1000   (   4 kB)
Aug  6 21:49:54 kernel: [    0.000000]     fixmap  : 0xffc00000 -
0xfff00000   (3072 kB)
Aug  6 21:49:54 kernel: [    0.000000]     vmalloc : 0xc8800000 -
0xff800000   ( 880 MB)
Aug  6 21:49:54 kernel: [    0.000000]     lowmem  : 0xc0000000 -
0xc8000000   ( 128 MB)
Aug  6 21:49:54 kernel: [    0.000000]     pkmap   : 0xbfe00000 -
0xc0000000   (   2 MB)
Aug  6 21:49:54 kernel: [    0.000000]     modules : 0xbf000000 -
0xbfe00000   (  14 MB)
Aug  6 21:49:54 kernel: [    0.000000]       .text : 0xc0008000 -
0xc0519924   (5191 kB)
Aug  6 21:49:54 kernel: [    0.000000]       .init : 0xc051a000 -
0xc0562000   ( 288 kB)
Aug  6 21:49:54 kernel: [    0.000000]       .data : 0xc0562000 -
0xc05bdcd0   ( 368 kB)
Aug  6 21:49:54 kernel: [    0.000000]        .bss : 0xc05bdcd0 -
0xc0606490   ( 290 kB)
Aug  6 21:49:54 kernel: [    0.000000] NR_IRQS:16 nr_irqs:65 65
Aug  6 21:49:54 kernel: [    0.000000] Switching to timer-based delay loop,
resolution 6ns
Aug  6 21:49:54 kernel: [    0.000018] sched_clock: 32 bits at 166MHz,
resolution 6ns, wraps every 12884901885ns
Aug  6 21:49:54 kernel: [   10.599207] clocksource: orion_clocksource:
mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
Aug  6 21:49:54 kernel: [   10.599979] Console: colour dummy device 80x30
Aug  6 21:49:54 kernel: [   10.600031] Calibrating delay loop (skipped),
value calculated using timer frequency.. 333.33 BogoMIPS (lpj=666666)
Aug  6 21:49:54 kernel: [   10.600065] pid_max: default: 32768 minimum: 301
Aug  6 21:49:54 kernel: [   10.600277] Security Framework initialized
Aug  6 21:49:54 kernel: [   10.600302] Yama: disabled by default; enable
with sysctl kernel.yama.*
Aug  6 21:49:54 kernel: [   10.600473] Mount-cache hash table entries: 1024
(order: 0, 4096 bytes)
Aug  6 21:49:54 kernel: [   10.600506] Mountpoint-cache hash table entries:
1024 (order: 0, 4096 bytes)
Aug  6 21:49:54 kernel: [   10.602497] CPU: Testing write buffer coherency:
ok
Aug  6 21:49:54 kernel: [   10.602777] ftrace: allocating 16337 entries in
32 pages
Aug  6 21:49:54 kernel: [   10.664194] Setting up static identity map for
0x8200 - 0x823c
Aug  6 21:49:54 kernel: [   10.669793] devtmpfs: initialized
Aug  6 21:49:54 kernel: [   10.672730] VFP support v0.3: not present
Aug  6 21:49:54 kernel: [   10.673181] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Aug  6 21:49:54 kernel: [   10.673819] pinctrl core: initialized pinctrl
subsystem
Aug  6 21:49:54 kernel: [   10.676984] NET: Registered protocol family 16
Aug  6 21:49:54 kernel: [   10.678070] DMA: preallocated 256 KiB pool for
atomic coherent allocations
Aug  6 21:49:54 kernel: [   10.680123] cpuidle: using governor ladder
Aug  6 21:49:54 kernel: [   10.680165] cpuidle: using governor menu
Aug  6 21:49:54 kernel: [   10.680269] Orion ID: MV88F5182-A2.
TCLK=166666667.
Aug  6 21:49:54 kernel: [   10.680664] initial MPP regs: 00000003 00000000
03ff0000
Aug  6 21:49:54 kernel: [   10.680707]   final MPP regs: 00000003 55550000
03ff5550
Aug  6 21:49:54 kernel: [   10.697229] clocksource: Switched to clocksource
orion_clocksource
Aug  6 21:49:54 kernel: [   10.739259] VFS: Disk quotas dquot_6.6.0
Aug  6 21:49:54 kernel: [   10.739415] VFS: Dquot-cache hash table entries:
1024 (order 0, 4096 bytes)
Aug  6 21:49:54 kernel: [   10.763610] NET: Registered protocol family 2
Aug  6 21:49:54 kernel: [   10.765651] TCP established hash table entries:
1024 (order: 0, 4096 bytes)
Aug  6 21:49:54 kernel: [   10.765721] TCP bind hash table entries: 1024
(order: 0, 4096 bytes)
Aug  6 21:49:54 kernel: [   10.765775] TCP: Hash tables configured
(established 1024 bind 1024)
Aug  6 21:49:54 kernel: [   10.765948] UDP hash table entries: 256 (order:
0, 4096 bytes)
Aug  6 21:49:54 kernel: [   10.766015] UDP-Lite hash table entries: 256
(order: 0, 4096 bytes)
Aug  6 21:49:54 kernel: [   10.766584] NET: Registered protocol family 1
Aug  6 21:49:54 kernel: [   10.766729] PCI: CLS 0 bytes, default 32
Aug  6 21:49:54 kernel: [   10.767341] Unpacking initramfs...
Aug  6 21:49:54 kernel: [   12.949123] Freeing initrd memory: 9108K
(c0800000 - c10e5000)
Aug  6 21:49:54 kernel: [   12.950919] futex hash table entries: 256
(order: -1, 3072 bytes)
Aug  6 21:49:54 kernel: [   12.951131] audit: initializing netlink subsys
(disabled)
Aug  6 21:49:54 kernel: [   12.951292] audit: type=2000 audit(2.328:1):
initialized
Aug  6 21:49:54 kernel: [   12.952438] workingset: timestamp_bits=28
max_order=15 bucket_order=0
Aug  6 21:49:54 kernel: [   12.952825] zbud: loaded
Aug  6 21:49:54 kernel: [   12.958896] Block layer SCSI generic (bsg)
driver version 0.4 loaded (major 251)
Aug  6 21:49:54 kernel: [   12.959390] io scheduler noop registered
Aug  6 21:49:54 kernel: [   12.959527] io scheduler cfq registered (default)
Aug  6 21:49:54 kernel: [   12.961046] mv_xor mv_xor.0: Marvell shared XOR
driver
Aug  6 21:49:54 kernel: [   12.996605] mv_xor mv_xor.0: Marvell XOR
(Registers Mode): ( xor cpy )
Aug  6 21:49:54 kernel: [   12.997628] Serial: 8250/16550 driver, 2 ports,
IRQ sharing disabled
Aug  6 21:49:54 kernel: [   12.999458] console [ttyS0] disabled
Aug  6 21:49:54 kernel: [   13.019711] serial8250.0: ttyS0 at MMIO
0xf1012000 (irq = 4, base_baud = 10416666) is a 16550A
Aug  6 21:49:54 kernel: [   13.473943] console [ttyS0] enabled
Aug  6 21:49:54 kernel: [   13.479546] physmap platform flash device:
00080000 at f4000000
Aug  6 21:49:54 kernel: [   13.485741] physmap-flash.0: Found 1 x16 devices
at 0x0 in 8-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x0000b9
Aug  6 21:49:54 kernel: [   13.496001] Amd/Fujitsu Extended Query Table at
0x0040
Aug  6 21:49:54 kernel: [   13.501187]   Amd/Fujitsu Extended Query version
1.0.
Aug  6 21:49:54 kernel: [   13.506274] physmap-flash.0: JEDEC Device ID is
0xB9. Assuming broken CFI table.
Aug  6 21:49:54 kernel: [   13.513692] physmap-flash.0: Swapping erase
regions for top-boot CFI table.
Aug  6 21:49:54 kernel: [   13.520681] number of CFI chips: 1
Aug  6 21:49:54 kernel: [   13.549422] Creating 1 MTD partitions on
"physmap-flash.0":
Aug  6 21:49:54 kernel: [   13.555100] 0x000000000000-0x000000080000 :
"firmware"
Aug  6 21:49:54 kernel: [   13.564862] mousedev: PS/2 mouse device common
for all mice
Aug  6 21:49:54 kernel: [   13.571417] i2c /dev entries driver
Aug  6 21:49:54 kernel: [   13.576129] rtc-pcf8563 0-0051: chip found,
driver version 0.4.4
Aug  6 21:49:54 kernel: [   13.587959] rtc-pcf8563 0-0051: rtc core:
registered rtc-pcf8563 as rtc0
Aug  6 21:49:54 kernel: [   13.598371] ledtrig-cpu: registered to indicate
activity on CPUs
Aug  6 21:49:54 kernel: [   13.605674] NET: Registered protocol family 17
Aug  6 21:49:54 kernel: [   13.611942] registered taskstats version 1
Aug  6 21:49:54 kernel: [   13.616432] zswap: loaded using pool lzo/zbud
Aug  6 21:49:54 kernel: [   13.623179] rtc-pcf8563 0-0051: setting system
clock to 1970-08-06 21:49:44 UTC (18827384)
Aug  6 21:49:54 kernel: [   13.635509] Freeing unused kernel memory: 288K
(c051a000 - c0562000)
Aug  6 21:49:54 kernel: [   13.641911] This architecture does not have
kernel memory protection.
Aug  6 21:49:54 kernel: [   13.765202] random: systemd-udevd urandom read
with 12 bits of entropy available
Aug  6 21:49:54 kernel: [   14.218436] mv643xx_eth: MV-643xx 10/100/1000
ethernet driver version 1.4
Aug  6 21:49:54 kernel: [   14.290007] libphy: PHY orion-mdio-mii:08 not
found
Aug  6 21:49:54 kernel: [   14.613385] libphy: orion_mdio_bus: probed
Aug  6 21:49:54 kernel: [   14.692227] mv643xx_eth_port mv643xx_eth_port.0
eth0: port 0 with MAC address 00:0a:e4:86:fd:05
Aug  6 21:49:54 kernel: [   14.752297] SCSI subsystem initialized
Aug  6 21:49:54 kernel: [   14.927607] libata version 3.00 loaded.
Aug  6 21:49:54 kernel: [   14.944822] sata_mv sata_mv.0: version 1.28
Aug  6 21:49:54 kernel: [   14.945014] sata_mv sata_mv.0: cannot get
optional clkdev
Aug  6 21:49:54 kernel: [   14.996386] sata_mv sata_mv.0: slots 32 ports 2
Aug  6 21:49:54 kernel: [   15.123508] scsi host0: sata_mv
Aug  6 21:49:54 kernel: [   15.160394] scsi host1: sata_mv
Aug  6 21:49:54 kernel: [   15.180300] ata1: SATA max UDMA/133 irq 30
Aug  6 21:49:54 kernel: [   15.184496] ata2: SATA max UDMA/133 irq 30
Aug  6 21:49:54 kernel: [   20.693299] ata1: link is slow to respond,
please be patient (ready=0)
Aug  6 21:49:54 kernel: [   22.209326] ata1: SATA link up 1.5 Gbps (SStatus
113 SControl 300)
Aug  6 21:49:54 kernel: [   22.235798] ata1.00: ATA-6: ST380023AS, 3.01,
max UDMA/133
Aug  6 21:49:54 kernel: [   22.241344] ata1.00: 156301488 sectors, multi 0:
LBA
Aug  6 21:49:54 kernel: [   22.246451] ata1.00: applying bridge limits
Aug  6 21:49:54 kernel: [   22.257779] ata1.00: configured for UDMA/100
Aug  6 21:49:54 kernel: [   22.263346] scsi 0:0:0:0: Direct-Access     ATA
     ST380023AS       3.01 PQ: 0 ANSI: 5
Aug  6 21:49:54 kernel: [   22.588829] ata2: SATA link down (SStatus 0
SControl 300)
Aug  6 21:49:54 kernel: [   22.737860] sd 0:0:0:0: [sda] 156301488 512-byte
logical blocks: (80.0 GB/74.5 GiB)
Aug  6 21:49:54 kernel: [   22.770340] sd 0:0:0:0: [sda] Write Protect is
off
Aug  6 21:49:54 kernel: [   22.775226] sd 0:0:0:0: [sda] Mode Sense: 00 3a
00 00
Aug  6 21:49:54 kernel: [   22.777507] sd 0:0:0:0: [sda] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Aug  6 21:49:54 kernel: [   22.816197]  sda: sda1
Aug  6 21:49:54 kernel: [   22.826789] sd 0:0:0:0: [sda] Attached SCSI disk
Aug  6 21:50:02 preseed: successfully loaded preseed file from
file:///preseed.cfg
Aug  6 21:50:05 init: starting pid 967, tty '': '/sbin/reopen-console
/sbin/debian-installer'
Aug  6 21:50:05 init: starting pid 970, tty '/dev/tty4': '/usr/bin/tail -f
/var/log/syslog'
Aug  6 21:50:07 debconf: Setting debconf/language to en
Aug  6 21:50:07 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:50:07 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:50:07 main-menu[989]: INFO: Menu item 'ethdetect' selected
Aug  6 21:50:09 kernel: [   38.697341] random: nonblocking pool is
initialized
Aug  6 21:50:10 net/hw-detect.hotplug: Detected hotpluggable network
interface eth0
Aug  6 21:50:10 net/hw-detect.hotplug: Detected hotpluggable network
interface lo
Aug  6 21:50:12 apt-install: Queueing package udev for later installation
Aug  6 21:50:12 apt-install: Queueing package pciutils for later
installation
Aug  6 21:50:14 check-missing-firmware: looking at dmesg for the first time
Aug  6 21:50:14 check-missing-firmware: saving timestamp for a later use: [
  38.697341]
Aug  6 21:50:14 check-missing-firmware: /dev/.udev/firmware-missing does
not exist, skipping
Aug  6 21:50:14 check-missing-firmware: /run/udev/firmware-missing does not
exist, skipping
Aug  6 21:50:14 check-missing-firmware: no missing firmware in loaded
kernel modules
Aug  6 21:50:14 check-missing-firmware: taking network interface -n up/down
Aug  6 21:50:14 check-missing-firmware: taking network interface eth0
up/down
Aug  6 21:50:14 kernel: [   43.970064] mv643xx_eth_port mv643xx_eth_port.0
eth0: link down
Aug  6 21:50:15 check-missing-firmware: looking at dmesg again, restarting
from \[   38.697341\]
Aug  6 21:50:16 check-missing-firmware: timestamp found, truncating dmesg
accordingly
Aug  6 21:50:16 check-missing-firmware: saving timestamp for a later use: [
  43.970064]
Aug  6 21:50:16 check-missing-firmware: /dev/.udev/firmware-missing does
not exist, skipping
Aug  6 21:50:16 check-missing-firmware: /run/udev/firmware-missing does not
exist, skipping
Aug  6 21:50:16 check-missing-firmware: no missing firmware in loaded
kernel modules
Aug  6 21:50:16 main-menu[989]: (process:1017): ip: SIOCGIFFLAGS: No such
device
Aug  6 21:50:16 main-menu[989]: (process:1017): ip: SIOCGIFFLAGS: No such
device
Aug  6 21:50:16 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:50:16 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:50:16 main-menu[989]: INFO: Menu item 'netcfg' selected
Aug  6 21:50:16 main-menu[989]: INFO: Falling back to the package
description for crypto-modules-4.6.0-1-marvell-di
Aug  6 21:50:16 main-menu[989]: INFO: Falling back to the package
description for crypto-modules-4.6.0-1-marvell-di
Aug  6 21:50:16 netcfg[1396]: INFO: Starting netcfg v.1.138
Aug  6 21:50:16 netcfg[1396]: WARNING **: Couldn't read Wpasupplicant pid
file, not trying to kill.
Aug  6 21:50:16 netcfg[1396]: INFO: Could not find valid BOOTIF= entry in
/proc/cmdline
Aug  6 21:50:16 netcfg[1396]: INFO: Taking down interface eth0
Aug  6 21:50:17 netcfg[1396]: INFO: Taking down interface lo
Aug  6 21:50:17 netcfg[1396]: INFO: Activating interface eth0
Aug  6 21:50:17 netcfg[1396]: DEBUG: State is now 0
Aug  6 21:50:17 netcfg[1396]: DEBUG: Want link on eth0
Aug  6 21:50:17 netcfg[1396]: INFO: Waiting time set to 3
Aug  6 21:50:17 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:17 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:18 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:18 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:18 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:18 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:19 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:19 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:19 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:19 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:20 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:20 netcfg[1396]: INFO: ethtool-lite: eth0: carrier down
Aug  6 21:50:20 netcfg[1396]: INFO: Reached timeout for link detection on
eth0
Aug  6 21:50:20 netcfg[1396]: DEBUG: Commencing network autoconfiguration
on eth0
Aug  6 21:50:20 netcfg[1396]: DEBUG: rdnssd started; PID: 1411
Aug  6 21:50:20 kernel: [   49.476308] mv643xx_eth_port mv643xx_eth_port.0
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Aug  6 21:50:20 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:20 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:20 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:20 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:20 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:20 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:20 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:20 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:21 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:21 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:21 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:21 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:21 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:21 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:21 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:21 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:21 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:21 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:21 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:21 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:21 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:21 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:22 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:22 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:22 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:22 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:22 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:22 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:22 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:23 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:23 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:23 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:23 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:23 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:23 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:23 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:23 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:23 netcfg[1396]: DEBUG: nc_v6_interface_configured(eth0, scope
local)
Aug  6 21:50:23 netcfg[1396]: DEBUG: Running ip addr show eth0 to look for
address
Aug  6 21:50:23 netcfg[1396]: DEBUG: ip line: 2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
Aug  6 21:50:23 netcfg[1396]: DEBUG: ip line:     link/ether
00:0a:e4:86:fd:05 brd ff:ff:ff:ff:ff:ff
Aug  6 21:50:23 netcfg[1396]: INFO: No IPv6 support found... how does that
happen?
Aug  6 21:50:23 netcfg[1396]: DEBUG: Stopping rdnssd, PID 1411
Aug  6 21:50:23 netcfg[1396]: DEBUG: No RA received; attempting IPv4
autoconfig
Aug  6 21:50:23 netcfg[1396]: WARNING **: Started DHCP client; PID is 1437
Aug  6 21:50:23 udhcpc: Got IP 192.168.0.8 (using eth0) and routing through
192.168.0.1
Aug  6 21:50:27 netcfg[1396]: DEBUG: Reading domain name returned via DHCP
Aug  6 21:50:27 netcfg[1396]: DEBUG: DHCP domain name is 'home.lan'
Aug  6 21:50:27 netcfg[1396]: DEBUG: Reading nameservers from
/etc/resolv.conf
Aug  6 21:50:27 netcfg[1396]: DEBUG: Read nameserver 192.168.0.2
Aug  6 21:50:27 netcfg[1396]: DEBUG: Read nameserver 192.168.0.11
Aug  6 21:50:27 netcfg[1396]: DEBUG: State is now 1
Aug  6 21:50:27 netcfg[1396]: DEBUG: State is now 2
Aug  6 21:50:27 netcfg[1396]: DEBUG: State is now 5
Aug  6 21:50:27 netcfg[1396]: DEBUG: Using DNS to try and obtain default
hostname
Aug  6 21:50:27 netcfg[1396]: DEBUG: Getting default hostname from rDNS
lookup of autoconfigured address 192.168.0.8
Aug  6 21:50:27 netcfg[1396]: DEBUG: Hostname found: backup.home.lan
Aug  6 21:50:27 netcfg[1396]: DEBUG: backup.home.lan is a valid FQDN
Aug  6 21:50:27 netcfg[1396]: DEBUG: We have a real FQDN
Aug  6 21:50:27 netcfg[1396]: DEBUG: Preseeding domain from global: home.lan
Aug  6 21:50:27 netcfg[1396]: DEBUG: State is now 6
Aug  6 21:50:27 netcfg[1396]: DEBUG: Network config complete
Aug  6 21:50:27 netcfg[1396]: DEBUG: No interface given; clearing
/etc/network/interfaces
Aug  6 21:50:27 netcfg[1396]: DEBUG: Writing informative header
Aug  6 21:50:27 netcfg[1396]: DEBUG: Success!
Aug  6 21:50:27 netcfg[1396]: DEBUG: Writing loopback interface
Aug  6 21:50:27 netcfg[1396]: DEBUG: Success!
Aug  6 21:50:27 netcfg[1396]: DEBUG: Writing DHCP stanza for eth0
Aug  6 21:50:27 netcfg[1396]: INFO: Detected eth0 as a hotpluggable device
Aug  6 21:50:27 netcfg[1396]: DEBUG: Success!
Aug  6 21:50:28 main-menu[989]: (process:1395): udhcpc (v1.22.1) started
Aug  6 21:50:28 main-menu[989]: (process:1395): Sending discover...
Aug  6 21:50:28 main-menu[989]: (process:1395): Sending select for
192.168.0.8...
Aug  6 21:50:28 main-menu[989]: (process:1395): Lease of 192.168.0.8
obtained, lease time 3600
Aug  6 21:50:28 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:50:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:50:28 main-menu[989]: INFO: Menu item 'network-console' selected
Aug  6 21:50:49 sshd[1498]: Server listening on 0.0.0.0 port 22.
Aug  6 21:50:49 apt-install: Queueing package openssh-server for later
installation
Aug  6 21:50:55 sshd[1516]: WARNING: /etc/ssh/moduli does not exist, using
fixed modulus
Aug  6 21:51:05 sshd[1516]: Accepted password for installer from
192.168.0.160 port 56579 ssh2
Aug  6 21:51:05 sshd[1518]: lastlog_openseek: Couldn't stat
/var/log/lastlog: No such file or directory
Aug  6 21:51:05 sshd[1518]: lastlog_openseek: Couldn't stat
/var/log/lastlog: No such file or directory
Aug  6 21:51:07 debconf: Setting debconf/language to en
Aug  6 21:51:11 debconf: Setting debconf/priority to low
Aug  6 21:51:11 debconf: Setting debconf/language to en
Aug  6 21:51:11 main-menu[1531]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:51:11 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:11 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:13 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:13 main-menu[1531]: INFO: Menu item 'choose-mirror' selected
Aug  6 21:51:13 main-menu[1531]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:14 anna-install: Queueing udeb apt-mirror-setup for later
installation
Aug  6 21:51:14 main-menu[1531]: (process:1557): Segmentation fault
Aug  6 21:51:14 main-menu[1531]: WARNING **: Configuring 'choose-mirror'
failed with error code 139
Aug  6 21:51:14 main-menu[1531]: WARNING **: Menu item 'choose-mirror'
failed.
Aug  6 21:51:14 main-menu[1531]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:14 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: INFO: Menu item 'choose-mirror' selected
Aug  6 21:51:28 main-menu[989]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:28 main-menu[989]: (process:1587): Segmentation fault
Aug  6 21:51:28 main-menu[989]: WARNING **: Configuring 'choose-mirror'
failed with error code 139
Aug  6 21:51:28 main-menu[989]: WARNING **: Menu item 'choose-mirror'
failed.
Aug  6 21:51:28 main-menu[989]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:22 main-menu[989]: INFO: Modifying debconf priority limit from
'high' to 'medium'
Aug  6 21:52:22 debconf: Setting debconf/priority to medium
Aug  6 21:52:22 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:52:23 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:23 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:34 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:34 main-menu[989]: INFO: Menu item 'save-logs' selected
Aug  6 21:53:08 kernel: [  218.089782] TCP: request_sock_TCP: Possible SYN
flooding on port 80. Sending cookies.  Check SNMP counters.
Aug  6 21:53:25 kernel: [  234.906280] TCP: request_sock_TCP: Possible SYN
flooding on port 80. Sending cookies.  Check SNMP counters.
-----------------------------------------------------------------------------


On Sat, Jul 30, 2016 at 7:23 PM, Martin Michlmayr <tbm@cyrius.com> wrote:

> Mike, can you please give these instructions a go?  This is what I
> intend to post to the mv2120 list.
>
> --
>
> Mike Thompson reported that Debian stretch (the upcoming Debian 9)
> doesn't boot on the HP mv2120 anymore.  I don't know how many Debian
> users are left who run Debian on their mv2120.  I gave away my device
> several years ago.  Recently I bought an mv2120 from eBay in order to
> debug this issue.
>
> While I found a solution, it requires users to change a setting on their
> device.  Please make sure to make this change, otherwise your device
> will no longer boot when you upgrade to Debian 9.
>
> The new settings are compatible with Debian 8 (jessie) and Debian 9
> (stretch), so I suggest you make the changes now.
>
> If you have serial console access to the mv2120, you can run some
> commands in u-boot.  Simply interrupt the boot process by pressing a key
> and type the following:
>
>     setenv loadAddr 0x0600000
>     setenv bootcmd 'bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda
> /dev/sdb'
>     saveenv
>
> If you don't have a serial console, you can make the changes from within
> Debian.  Run the following commands:
>
>     cat >/etc/fw_env.config <<EOF
>     /dev/mtd0           0x00000         0x1000     0x20000
>     EOF
>
>     fw_setenv loadAddr 0x0600000
>     fw_setenv bootcmd "bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda
> /dev/sdb"
>
> This will create a config file so you can modify the u-boot environment
> and use fw_setenv to update two boot variables.
>
> Once you made the changes, upgrades to Debian 9 should work fine and you
> can also use the Debian installer if you want to perform a new
> installation.
>
> Please note that Debian 9 will be the last release to support the HP
> mv2120.
>
> --
>
> Note that the installer from
>
> https://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/hp/mv2120/netboot.img
> will not boot right now with these settings.  However, you can change the
> loadAddr to 0x0500000 and it should work.  I just commited a fix in Git so
> it should work in a day or so with 0x0600000.
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>
[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sat, 06 Aug 2016 19:39:03 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sat, 06 Aug 2016 19:39:03 GMT) (full text, mbox, link).


Message #45 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: Mike Thompson <mpthompson@gmail.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sat, 6 Aug 2016 12:37:42 -0700
Hi Mike,

* Mike Thompson <mpthompson@gmail.com> [2016-08-05 20:23]:
> The good news is that given the load address change from 0x400000 to
> 0x600000 allowed the MV2120 to boot into the ssh based installer.

Great!

> The bad news is the installed failed from what looked like some sort of
> segmentation faults in the installer from the looks of the logs which I
> included below.

I wonder if this is the same as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833599

Can you please test this image:
http://ftp.nl.debian.org/debian/dists/testing/main/installer-armel/current/images/orion5x/network-console/hp/mv2120/netboot.img

-- 
Martin Michlmayr
http://www.cyrius.com/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sun, 07 Aug 2016 01:36:04 GMT) (full text, mbox, link).


Acknowledgement sent to Mike Thompson <mpthompson@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sun, 07 Aug 2016 01:36:04 GMT) (full text, mbox, link).


Message #50 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Mike Thompson <mpthompson@gmail.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sat, 6 Aug 2016 18:32:09 -0700
[Message part 1 (text/plain, inline)]
OK Martin, that image worked.  I did a full install of Debian Stretch from
it.  Below is the output at the tail end of bootup and login.

----------------------------------------------------
Debian GNU/Linux stretch/sid backup ttyS0

backup login: root
Password:
Linux backup 4.6.0-1-marvell #1 Debian 4.6.4-1 (2016-07-18) armv5tel
----------------------------------------------------

The 0x600000 change also still continues to boot my existing Debian Jessie
install.

Thanks for the work you do to keep these old pieces of NAS hardware working.

Mike

On Sat, Aug 6, 2016 at 12:37 PM, Martin Michlmayr <tbm@cyrius.com> wrote:

> Hi Mike,
>
> * Mike Thompson <mpthompson@gmail.com> [2016-08-05 20:23]:
> > The good news is that given the load address change from 0x400000 to
> > 0x600000 allowed the MV2120 to boot into the ssh based installer.
>
> Great!
>
> > The bad news is the installed failed from what looked like some sort of
> > segmentation faults in the installer from the looks of the logs which I
> > included below.
>
> I wonder if this is the same as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833599
>
> Can you please test this image:
> http://ftp.nl.debian.org/debian/dists/testing/main/
> installer-armel/current/images/orion5x/network-
> console/hp/mv2120/netboot.img
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>
[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Sun, 07 Aug 2016 02:09:03 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sun, 07 Aug 2016 02:09:03 GMT) (full text, mbox, link).


Message #55 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: Mike Thompson <mpthompson@gmail.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sat, 6 Aug 2016 19:07:27 -0700
* Mike Thompson <mpthompson@gmail.com> [2016-08-06 18:32]:
> OK Martin, that image worked.  I did a full install of Debian Stretch from
> it.  Below is the output at the tail end of bootup and login.

Thanks for testing it!

-- 
Martin Michlmayr
http://www.cyrius.com/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#809611; Package debian-installer. (Tue, 09 Aug 2016 01:21:04 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Tue, 09 Aug 2016 01:21:04 GMT) (full text, mbox, link).


Message #60 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: Mike Thompson <mpthompson@gmail.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Mon, 8 Aug 2016 18:18:35 -0700
retitle 809611 armel: HP mv2120 requires change in u-boot setting
reassign 809611 release-notes
thanks

I documented the new settings here:
http://www.cyrius.com/debian/orion/hp/mv2120/uboot-config/

I emailed the hackingthemediavault and debian-arm mailing lists.

Since we cannot fix this in Debian, I'll reassign this bug to
release-notes where we should add a link to the configuration change.

-- 
Martin Michlmayr
http://www.cyrius.com/



Changed Bug title to 'armel: HP mv2120 requires change in u-boot setting' from 'd-i fails to boot on HP mv2120'. Request was from Martin Michlmayr <tbm@cyrius.com> to control@bugs.debian.org. (Tue, 09 Aug 2016 01:21:09 GMT) (full text, mbox, link).


Bug reassigned from package 'debian-installer' to 'release-notes'. Request was from Martin Michlmayr <tbm@cyrius.com> to control@bugs.debian.org. (Tue, 09 Aug 2016 01:21:10 GMT) (full text, mbox, link).


Information forwarded to debian-bugs-dist@lists.debian.org, Debian Documentation Team <debian-doc@lists.debian.org>:
Bug#809611; Package release-notes. (Tue, 09 Aug 2016 01:27:03 GMT) (full text, mbox, link).


Acknowledgement sent to Martin Michlmayr <tbm@cyrius.com>:
Extra info received and forwarded to list. Copy sent to Debian Documentation Team <debian-doc@lists.debian.org>. (Tue, 09 Aug 2016 01:27:03 GMT) (full text, mbox, link).


Message #69 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>
To: Mike Thompson <mpthompson@gmail.com>
Cc: 809611@bugs.debian.org
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Mon, 8 Aug 2016 18:23:38 -0700
Please add the following to the release-notes on armel in the upgrade
section:

HP mv2120

The default u-boot settings from HP no longer work with Debian 9.
Before you can upgrade to Debian 9, you have to change some settings
in the u-boot configuration.  The required changes are documented on
the [Debian on HP
mv2120](http://www.cyrius.com/debian/orion/hp/mv2120/uboot-config/)
page.

or if you don't want to link to an external page:

HP mv2120

The default u-boot settings from HP no longer work with Debian 9.
Before you can upgrade to Debian 9, you have to change some settings
in the u-boot configuration.

If you have serial console access to the mv2120, you can run some
commands in u-boot. Simply interrupt the boot process by pressing a
key and type the following:

    setenv loadAddr 0x0600000
    setenv bootcmd 'bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda /dev/sdb'
    saveenv

If you don't have a serial console, you can make the changes from
within Debian. Run the following commands:

   cat >/etc/fw_env.config <<EOF
   /dev/mtd0           0x00000         0x1000     0x20000
   EOF

   fw_setenv loadAddr 0x0600000
   fw_setenv bootcmd "bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda /dev/sdb"

This creates a config file so the u-boot environment can be modified
and uses fw_setenv to update two boot variables.

-- 
Martin Michlmayr
http://www.cyrius.com/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Documentation Team <debian-doc@lists.debian.org>:
Bug#809611; Package release-notes. (Wed, 10 Aug 2016 21:51:03 GMT) (full text, mbox, link).


Acknowledgement sent to Baptiste Jammet <baptiste@mailoo.org>:
Extra info received and forwarded to list. Copy sent to Debian Documentation Team <debian-doc@lists.debian.org>. (Wed, 10 Aug 2016 21:51:03 GMT) (full text, mbox, link).


Message #74 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Baptiste Jammet <baptiste@mailoo.org>
To: 809611@bugs.debian.org
Cc: Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Wed, 10 Aug 2016 23:50:37 +0200
[Message part 1 (text/plain, inline)]
Control: tags -1 patch

Hi

Dixit Martin Michlmayr, le 08/08/2016 :

>Please add the following to the release-notes on armel in the upgrade
>section:
>
>HP mv2120
[...]

I used copy&paste and formatting to put this in the Upgrading chapter.
I choose the integral doc, as it's not so long and clearer that linking
to Martin's webpage.
Please comment and correct.

Baptiste
[upgrading_u-boot-HP-mv2212.diff (text/x-patch, attachment)]
[Message part 3 (application/pgp-signature, inline)]

Added tag(s) patch. Request was from Baptiste Jammet <baptiste@mailoo.org> to 809611-submit@bugs.debian.org. (Wed, 10 Aug 2016 21:51:03 GMT) (full text, mbox, link).


Information forwarded to debian-bugs-dist@lists.debian.org, Debian Documentation Team <debian-doc@lists.debian.org>:
Bug#809611; Package release-notes. (Thu, 11 Aug 2016 06:18:04 GMT) (full text, mbox, link).


Acknowledgement sent to Niels Thykier <niels@thykier.net>:
Extra info received and forwarded to list. Copy sent to Debian Documentation Team <debian-doc@lists.debian.org>. (Thu, 11 Aug 2016 06:18:04 GMT) (full text, mbox, link).


Message #81 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Niels Thykier <niels@thykier.net>
To: Baptiste Jammet <baptiste@mailoo.org>, 809611@bugs.debian.org
Cc: Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Thu, 11 Aug 2016 08:14:04 +0200
Baptiste Jammet:
> Control: tags -1 patch
> 
> Hi
> 
> Dixit Martin Michlmayr, le 08/08/2016 :
> 
>> Please add the following to the release-notes on armel in the upgrade
>> section:
>>
>> HP mv2120
> [...]
> 
> I used copy&paste and formatting to put this in the Upgrading chapter.
> I choose the integral doc, as it's not so long and clearer that linking
> to Martin's webpage.
> Please comment and correct.
> 
> Baptiste
> 

Hi,

Thanks for working on the release-notes.

I would like to see this moved to chapter 5 in the Stretch release
notes, because I am trying to make it easy for regular people to find
that they need to know about upgrading (without having to skim through
all chapters).
  Unlike previous releases, Chapter 5 is dedicated to all the "need to
know for a smooth upgrade" items (even if they are not package specific).



Thanks,
~Niels




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Documentation Team <debian-doc@lists.debian.org>:
Bug#809611; Package release-notes. (Tue, 16 Aug 2016 17:06:04 GMT) (full text, mbox, link).


Acknowledgement sent to Baptiste Jammet <baptiste@mailoo.org>:
Extra info received and forwarded to list. Copy sent to Debian Documentation Team <debian-doc@lists.debian.org>. (Tue, 16 Aug 2016 17:06:04 GMT) (full text, mbox, link).


Message #86 received at 809611@bugs.debian.org (full text, mbox, reply):

From: Baptiste Jammet <baptiste@mailoo.org>
To: Niels Thykier <niels@thykier.net>, 809611@bugs.debian.org
Cc: Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Tue, 16 Aug 2016 19:16:13 +0200
[Message part 1 (text/plain, inline)]
Hi, 

Dixit Niels Thykier, le 11/08/2016 :

>I would like to see this moved to chapter 5 in the Stretch release
>notes, because I am trying to make it easy for regular people to find
>that they need to know about upgrading (without having to skim through
>all chapters).
>  Unlike previous releases, Chapter 5 is dedicated to all the "need to
>know for a smooth upgrade" items (even if they are not package
>specific).

OK, I understand your point.
Attached is the same patch, but added in the Issues chapter.

Baptiste
[issues_u-boot-HP-mv2212.diff (text/x-patch, attachment)]
[Message part 3 (application/pgp-signature, inline)]

Reply sent to Baptiste Jammet <baptiste@mailoo.org>:
You have taken responsibility. (Sun, 28 Aug 2016 16:15:26 GMT) (full text, mbox, link).


Notification sent to Martin Michlmayr <tbm@cyrius.com>:
Bug acknowledged by developer. (Sun, 28 Aug 2016 16:15:26 GMT) (full text, mbox, link).


Message #91 received at 809611-done@bugs.debian.org (full text, mbox, reply):

From: Baptiste Jammet <baptiste@mailoo.org>
To: 809611-done@bugs.debian.org
Cc: Niels Thykier <niels@thykier.net>, Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Bug#809611: d-i fails to boot on HP mv2120
Date: Sun, 28 Aug 2016 18:19:01 +0200
[Message part 1 (text/plain, inline)]
Hi,

>Dixit Niels Thykier, le 11/08/2016 :
>
>>I would like to see this moved to chapter 5 in the Stretch release
>>notes, because I am trying to make it easy for regular people to find
>>that they need to know about upgrading (without having to skim through
>>all chapters).
>>  Unlike previous releases, Chapter 5 is dedicated to all the "need to
>>know for a smooth upgrade" items (even if they are not package
>>specific).

Commited in the Issues chapter, arch-specific for armel.
Thanks

Baptiste
[Message part 2 (application/pgp-signature, inline)]

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 26 Sep 2016 07:25:36 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Jun 4 06:51:44 2023; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.