Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
On Tue, 2014-01-14 at 22:47 +, Ian Campbell wrote: It's late so I'm going to set a build going of v3.12 with the above reverted and see how it goes in the morning before putting together a report for upstream. v3.12 with the following revert works for me. I'm going to try v3.13-rc8 before reporting upstream. commit 19d60c0e669fb92e187ae54558f9b45c2cba5584 Author: Ian Campbell i...@hellion.org.uk Date: Tue Jan 14 22:47:44 2014 + Revert ARM: kirkwood: convert to DT irqchip and clocksource This reverts commit 2326f04321a9aec591c1d159b3a9d12c2bf89438. Conflicts: arch/arm/mach-kirkwood/Kconfig diff --git a/arch/arm/mach-kirkwood/Kconfig b/arch/arm/mach-kirkwood/Kconfig index fe8319a..c11fcce 100644 --- a/arch/arm/mach-kirkwood/Kconfig +++ b/arch/arm/mach-kirkwood/Kconfig @@ -2,32 +2,67 @@ if ARCH_KIRKWOOD menu Marvell Kirkwood Implementations -config KIRKWOOD_LEGACY - bool - config MACH_D2NET_V2 bool LaCie d2 Network v2 NAS Board - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the LaCie d2 Network v2 NAS. +config MACH_DOCKSTAR + bool Seagate FreeAgent DockStar + help + Say 'Y' here if you want your kernel to support the + Seagate FreeAgent DockStar. + +config MACH_ESATA_SHEEVAPLUG + bool Marvell eSATA SheevaPlug Reference Board + help + Say 'Y' here if you want your kernel to support the + Marvell eSATA SheevaPlug Reference Board. + +config MACH_GURUPLUG + bool Marvell GuruPlug Reference Board + help + Say 'Y' here if you want your kernel to support the + Marvell GuruPlug Reference Board. + +config MACH_INETSPACE_V2 + bool LaCie Internet Space v2 NAS Board + help + Say 'Y' here if you want your kernel to support the + LaCie Internet Space v2 NAS. + +config MACH_MV88F6281GTW_GE + bool Marvell 88F6281 GTW GE Board + help + Say 'Y' here if you want your kernel to support the + Marvell 88F6281 GTW GE Board. + config MACH_NET2BIG_V2 bool LaCie 2Big Network v2 NAS Board - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the LaCie 2Big Network v2 NAS. config MACH_NET5BIG_V2 bool LaCie 5Big Network v2 NAS Board - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the LaCie 5Big Network v2 NAS. +config MACH_NETSPACE_MAX_V2 + bool LaCie Network Space Max v2 NAS Board + help + Say 'Y' here if you want your kernel to support the + LaCie Network Space Max v2 NAS. + +config MACH_NETSPACE_V2 + bool LaCie Network Space v2 NAS Board + help + Say 'Y' here if you want your kernel to support the + LaCie Network Space v2 NAS. + config MACH_OPENRD - select KIRKWOOD_LEGACY bool config MACH_OPENRD_BASE @@ -53,28 +88,30 @@ config MACH_OPENRD_ULTIMATE config MACH_RD88F6192_NAS bool Marvell RD-88F6192-NAS Reference Board - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the Marvell RD-88F6192-NAS Reference Board. config MACH_RD88F6281 bool Marvell RD-88F6281 Reference Board - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the Marvell RD-88F6281 Reference Board. +config MACH_SHEEVAPLUG + bool Marvell SheevaPlug Reference Board + help + Say 'Y' here if you want your kernel to support the + Marvell SheevaPlug Reference Board. + config MACH_T5325 bool HP t5325 Thin Client - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the HP t5325 Thin Client. config MACH_TS219 bool QNAP TS-110, TS-119, TS-119P+, TS-210, TS-219, TS-219P and TS-219P+ Turbo NAS - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the QNAP TS-110, TS-119, TS-119P+, TS-210, TS-219, TS-219P and @@ -82,7 +119,6 @@ config MACH_TS219 config MACH_TS41X bool QNAP TS-410, TS-410U, TS-419P, TS-419P+ and TS-419U Turbo NAS - select KIRKWOOD_LEGACY help Say 'Y' here if you want your kernel to support the QNAP TS-410, TS-410U, TS-419P, TS-419P+ and TS-419U Turbo @@ -93,9 +129,6 @@ comment Device tree entries config ARCH_KIRKWOOD_DT bool Marvell Kirkwood Flattened Device Tree select KIRKWOOD_CLK - select OF_IRQ - select ORION_IRQCHIP - select ORION_TIMER select POWER_SUPPLY select POWER_RESET select POWER_RESET_GPIO diff --git a/arch/arm/mach-kirkwood/Makefile b/arch/arm/mach-kirkwood/Makefile index d1f8e3d..1c3a6fe 100644 --- a/arch/arm/mach-kirkwood/Makefile +++
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
On Wed, 2014-01-15 at 07:26 +0100, Hardy Griech wrote: Is it possible to take back the testing status (reverting it to experimental) of the 3.12-1-kirkwood kernel until the issue has been fixed? The Debian archive infrastructure does not support this AFAIK. Ian. signature.asc Description: This is a digitally signed message part
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
On Tue, 2014-01-14 at 08:22 +0100, Hardy Griech wrote: On 13.01.2014 15:53, Ian Campbell wrote: On Mon, 2014-01-13 at 13:54 +0100, Sylvain LEVEQUE wrote: I upgraded a QNAP TS-119 from linux-image-3.11-2-kirkwood to linux-image-3.12-1-kirkwood. dpkg.log states: 2014-01-06 14:37:08 upgrade linux-image-kirkwood:armel 3.11+54 3.12+55 : thanks for notifying me. Where can I find the 3.13 experimental kernel? Adding the experimental package path to sources.list does not help. Ah, it seems I was mistaken -- the armel kernel package of 3.13 didn't build so it isn't available yet. I suppose this will be fixed with the next upload (I'm going to investigate). (I put the bug and Sylvain back in the CC so they see this too). Ian. signature.asc Description: This is a digitally signed message part
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
On Tue, 2014-01-14 at 08:18 +, Ian Campbell wrote: Ah, it seems I was mistaken -- the armel kernel package of 3.13 didn't build so it isn't available yet. I suppose this will be fixed with the next upload (I'm going to investigate). FYI Ben has already fixed the FTBFS, so the next upload should be good. Ian. signature.asc Description: This is a digitally signed message part
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
* Ian Campbell i...@hellion.org.uk [2014-01-13 14:53]: Apparently earlyprintk is enabled in our kirkwood kernels -- could you try adding earlyprintk to your kernel command line args please. It seems user Reardon has posted the output with earlyprintk (from a TS-41x) on the QNAP forum already: http://forum.qnap.com/viewtopic.php?f=147t=88948 (But Sylvain, it would be great if you could run with earlyprintk too to confirm the output). Uncompressing Linux... done, booting the kernel. [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.12-1-kirkwood (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-1) ) #1 Debian 3.12.6-2 (2013-12-29) [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: QNAP TS-41x [0.00] Ignoring unrecognised tag 0x41000403 [0.00] bootconsole [earlycon0] enabled [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [0.00] Kernel command line: console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90 ramdisk=32768 earlyprintk [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Memory: 504652K/524288K available (3644K kernel code, 311K rwdata, 1280K rodata, 185K init, 412K bss, 19636K reserved) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xe080 - 0xff00 ( 488 MB) [0.00] lowmem : 0xc000 - 0xe000 ( 512 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .text : 0xc0008000 - 0xc04d73f0 (4925 kB) [0.00] .init : 0xc04d8000 - 0xc05067b4 ( 186 kB) [0.00] .data : 0xc0508000 - 0xc0555e80 ( 312 kB) [0.00].bss : 0xc0555e80 - 0xc05bd230 ( 413 kB) [0.00] NR_IRQS:114 [0.00] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [0.00] Console: colour dummy device 80x30 It hangs right now, nothing more emitted. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
* Ian Campbell i...@hellion.org.uk [2014-01-13 14:53]: Apparently earlyprintk is enabled in our kirkwood kernels -- could you try adding earlyprintk to your kernel command line args please. Sylvain, I believe the right commands to issue in u-boot are: setenv bootargs console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90 ramdisk=32768 earlyprintk cp.b 0xf820 0x80 0x20 cp.b 0xf840 0xa0 0x90 bootm 0x80 -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
Hello (But Sylvain, it would be great if you could run with earlyprintk too to confirm the output). I will try to do this tonight. One question though: from a test point of view, do you agree that booting from a 3.12 or 3.13 kernel sent over tftp (and I assume pushed to RAM, seeing how fast it goes) is equivalent to have it flashed (a several minutes process)? I only tried the flashed way so far, but I'd rather go the tftp way if it's ok, to be a reboot away from a functional system. Thanks -- Sylvain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
* Sylvain LÉVÊQUE sylvain.leve...@gmail.com [2014-01-14 12:13]: (But Sylvain, it would be great if you could run with earlyprintk too to confirm the output). I will try to do this tonight. One question though: from a test point of view, do you agree that booting from a 3.12 or 3.13 kernel sent over tftp (and I assume pushed to RAM, seeing how fast it goes) is equivalent to have it flashed (a several minutes process)? Yes. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
On Tue, 2014-01-14 at 12:13 +0100, Sylvain LÉVÊQUE wrote:
Hello
(But Sylvain, it would be great if you could run with earlyprintk too
to confirm the output).
I will try to do this tonight.
BTW, I got round to this and I see the same thing with earlyprintk as
reported before.
I've started bisecting and as you might have guessed the issue appeared
between v3.11 and v3.12-rc1. Although I've not 100% ruled out a .config
change (some of my initial attempts at bisect were a bit weird).
bisecting is slow progress, mostly because I have to remember to come
back every 10 mins to boot a new kernel, rather than wander off and get
distracted by something else...
One question though: from a test point
of view, do you agree that booting from a 3.12 or 3.13 kernel sent
over tftp (and I assume pushed to RAM, seeing how fast it goes) is
equivalent to have it flashed (a several minutes process)?
I only tried the flashed way so far, but I'd rather go the tftp way if
it's ok, to be a reboot away from a functional system.
FWIW I'm doing:
To create the image:
( devio wl 0xe3a01c09,4 wl 0xe38110c6,4 ; cat arch/arm/boot/zImage ) x
sudo mkimage -A arm -T kernel -O linux -C none -a 0x8000 -e 0x8000 -d x
/srv/tftp/u419
To boot it:
setenv autoload no;dhcp;setenv bootargs ${bootargs} earlyprintk
tftp 0x80 /u419;cp.b 0xf840 0xa0 0x90;bootm 0x80
That gets it to either fail or to the point where the initramfs cannot
find the rootfs (because the driver is not present).
Ian.
signature.asc
Description: This is a digitally signed message part
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
2014/1/14 Martin Michlmayr t...@cyrius.com: * Sylvain LÉVÊQUE sylvain.leve...@gmail.com [2014-01-14 12:13]: (But Sylvain, it would be great if you could run with earlyprintk too to confirm the output). I will try to do this tonight. One question though: from a test point of view, do you agree that booting from a 3.12 or 3.13 kernel sent over tftp (and I assume pushed to RAM, seeing how fast it goes) is equivalent to have it flashed (a several minutes process)? Yes. Here you go for the 3.12 kernel. End of reboot from 3.11, then full log from U-Boot. It's the same as user Reardon you were talking about. [] Unmounting local filesystems...done. [203125.351312] EXT4-fs (sda2): re-mounted. Opts: (null) [info] Will now restart. [203127.776815] sd 0:0:0:0: [sda] Synchronizing SCSI cache [203127.801265] reboot: Restarting system __ __ _ _ | \/ | __ _ _ _| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_|\_/ \___|_|_| _ _ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/|/ \___/ \___/ \__| ** LOADER ** ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (Feb 9 2009 - 11:13:32) Marvell version: 3.4.4 U-Boot code: 0060 - 0067FFF0 BSS: - 00690DCC Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x size 256MB DRAM CS[1] base 0x1000 size 256MB DRAM Total size 512MB 16bit width [16384kB@f800] Flash: 16 MB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME] Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode Device 0 @ 0 0: Model: WDC WD10EADS-00L5B1 Firm: 01.01A01 Ser#: WD-WC8 Type: Hard Disk Supports 48-bit addressing Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) Hit any key to stop autoboot: 0 QNAP: Recovery Button pressed: 0 Marvell dhcp BOOTP broadcast 1 Bootfile Prefix: F_TS-119 DHCP client bound to address 192.168.1.119 Marvell setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw initrd=0xa0,0x8f earlyprintk Marvell tftpboot 0xa0 initrd.img-3.12-1-kirkwood.uboot Using egiga0 device TFTP from server 192.168.1.1; our IP address is 192.168.1.119 Filename 'initrd.img-3.12-1-kirkwood.uboot'. Load address: 0xa0 Loading: # # # # # # # # # # # # # # # # # # # # # # # # # # # # done Bytes transferred = 9437184 (90 hex) Marvell tftpboot 0x80 vmlinuz-3.12-1-kirkwood.uboot Using egiga0 device TFTP from server
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
On Tue, 2014-01-14 at 21:11 +, Ian Campbell wrote: I've started bisecting It appears to have fingered: commit 2326f04321a9aec591c1d159b3a9d12c2bf89438 Author: Sebastian Hesselbarth sebastian.hesselba...@gmail.com Date: Tue Jul 2 15:15:07 2013 +0200 ARM: kirkwood: convert to DT irqchip and clocksource With recent support for true irqchip and clocksource drivers for Orion SoCs, now make use of it on DT enabled Kirkwood boards. This also introduces a new Kconfig option for legacy (non-DT) Kirkwood where old code is moved out to and polishes DT board file a little bit. Signed-off-by: Sebastian Hesselbarth sebastian.hesselba...@gmail.com Signed-off-by: Jason Cooper ja...@lakedaemon.net Halfway through the bisection the failure changed to something the same as http://arm.slackware.com/listarchive/2013-November/001874.html , I treated these as bad also but it might be that there were two issues in this range and I've bisected the other one. It's late so I'm going to set a build going of v3.12 with the above reverted and see how it goes in the morning before putting together a report for upstream. Ian. signature.asc Description: This is a digitally signed message part
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
Is it possible to take back the testing status (reverting it to experimental) of the 3.12-1-kirkwood kernel until the issue has been fixed? Hardy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
Package: linux Version: 3.12.6-2 Severity: important Dear Maintainer, I upgraded a QNAP TS-119 from linux-image-3.11-2-kirkwood to linux-image-3.12-1-kirkwood. dpkg.log states: 2014-01-06 14:37:08 upgrade linux-image-kirkwood:armel 3.11+54 3.12+55 On the next reboot, the NAS was stuck early. I gave it a whole afternoon to boot, initially thinking an fsck was going on (which can take some time on a slow CPU with a large drive). I used the recovery console to get more information and instructions from http://cyrius.com/debian/kirkwood/qnap/ts-119/uboot/ to get back to normal, by reflashing linux-image-3.11-2-kirkwood over the failing 3.12. I suspect http://comments.gmane.org/gmane.linux.debian.ports.arm/13582 to be the same issue on a close hardware. Here is the boot log from the console: __ __ _ _ | \/ | __ _ _ _| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_|\_/ \___|_|_| _ _ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/|/ \___/ \___/ \__| ** LOADER ** ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (Feb 9 2009 - 11:13:32) Marvell version: 3.4.4 U-Boot code: 0060 - 0067FFF0 BSS: - 00690DCC Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x size 256MB DRAM CS[1] base 0x1000 size 256MB DRAM Total size 512MB 16bit width [16384kB@f800] Flash: 16 MB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME] Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode Device 0 @ 0 0: Model: WDC WD10EADS-00L5B1 Firm: 01.01A01 Ser#: WD-WCAU4D159618 Type: Hard Disk Supports 48-bit addressing Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) Hit any key to stop autoboot: 0 ## Booting image at 0080 ... Image Name: kernel 3.12-1-kirkwood Created: 2014-01-12 12:05:37 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1929800 Bytes = 1.8 MB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Thank you -- Sylvain -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (40, 'experimental') Architecture: armel (armv5tel) Kernel: Linux 3.11-2-kirkwood Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735172: linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP TS-119 from booting
On Mon, 2014-01-13 at 13:54 +0100, Sylvain LEVEQUE wrote: I upgraded a QNAP TS-119 from linux-image-3.11-2-kirkwood to linux-image-3.12-1-kirkwood. dpkg.log states: 2014-01-06 14:37:08 upgrade linux-image-kirkwood:armel 3.11+54 3.12+55 On the next reboot, the NAS was stuck early. I gave it a whole afternoon to boot, initially thinking an fsck was going on (which can take some time on a slow CPU with a large drive). I used the recovery console to get more information and instructions from http://cyrius.com/debian/kirkwood/qnap/ts-119/uboot/ to get back to normal, by reflashing linux-image-3.11-2-kirkwood over the failing 3.12. I suspect http://comments.gmane.org/gmane.linux.debian.ports.arm/13582 to be the same issue on a close hardware. So do I (ccing Hardy). Here is the boot log from the console: Thanks. Sadly it (as you can see) just silently hangs after the kernel decompressor :-( I've had a look at the linux-arm-kernel list for any recent reports along these lines but I didn't see anything. Apparently earlyprintk is enabled in our kirkwood kernels -- could you try adding earlyprintk to your kernel command line args please. Unless that gives us any clues then I think the next step is to take this to the upstream l-a-k list. I suppose it would be worth trying 3.13 from experimental first though. Ian. __ __ _ _ | \/ | __ _ _ _| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_|\_/ \___|_|_| _ _ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/|/ \___/ \___/ \__| ** LOADER ** ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (Feb 9 2009 - 11:13:32) Marvell version: 3.4.4 U-Boot code: 0060 - 0067FFF0 BSS: - 00690DCC Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x size 256MB DRAM CS[1] base 0x1000 size 256MB DRAM Total size 512MB 16bit width [16384kB@f800] Flash: 16 MB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME] Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode Device 0 @ 0 0: Model: WDC WD10EADS-00L5B1 Firm: 01.01A01 Ser#: WD-WCAU4D159618 Type: Hard Disk Supports 48-bit addressing Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) Hit any key to stop autoboot: 0 ## Booting image at 0080 ... Image Name: kernel 3.12-1-kirkwood Created: 2014-01-12 12:05:37 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1929800 Bytes = 1.8 MB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Thank you -- Sylvain -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (40, 'experimental') Architecture: armel (armv5tel) Kernel: Linux 3.11-2-kirkwood Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
