Welcome! Log In Create A New Profile

Advanced

Booting Debian runs into restarting loop (problems with Kernel?)

Posted by Kaeltis 
Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 04:47AM
Hey guys, yesterday i started my first attempt to get this running, but netconsole told me that there was a problem with the USB stick, so i took another one and used the installation script again. But now the plug gets into a restarting loop while loading the kernel. It basically tries to load the kernel, then nothing happens and after some time it restarts and tries again to load the kernel. Got a "Seagate FreeAgent Go DockStar".

netconsole
U-Boot 2010.03-01266-g42f7128-dirty (Aug 23 2010 - 23:14:54)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1430932 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4706212 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1430868 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4706148 Bytes =  4.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...


U-Boot 2010.03-01266-g42f7128-dirty (Aug 23 2010 - 23:14:54)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0

[...]

fw_printenv
 
bootcmd=run bootcmd_usb; usb stop; run bootcmd_pogo; reset
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
usb_init=usb start
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200
usb_load_uimage=ext2load usb $usb_device 0x800000 /boot/uImage
usb_boot=if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi;
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
bootcmd_usb=run usb_init; run usb_load_uimage; run set_bootargs_usb; run usb_boot;
stdin=serial
stdout=serial
stderr=serial
ethact=egiga0
ethaddr=00:10:75:1A:CE:20
serverip=10.0.0.116
ipaddr=10.0.0.115
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole

Without the USB stick plugged in, it boots the normal Pogoplug without Problems:

netconsole
U-Boot 2010.03-01266-g42f7128-dirty (Aug 23 2010 - 23:14:54)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ..



Edited 5 time(s). Last edit at 08/25/2010 07:49AM by Kaeltis.
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 07:54AM
Is there a long pause between:
  Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...
and
U-Boot 2010.03-01266-g42f7128-dirty (Aug 23 2010 - 23:14:54)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0
?

That's where the kernel would start booting and, unfortunately, you can't see it's messages over netconsole. You may want to check /var/log/dmesg to see if it has any interesting errors. You should probably fsck the drive, while you're at it.

You can try upgrading to the newest uBoot. It has some newer USB handling code that may fix your problem. It will probably fix your problem with the first drive that you tried. I'm not so sure about the second drive -- my guess is that it's something with the filesystem.

-- Jeff



Edited 1 time(s). Last edit at 08/25/2010 08:00AM by Jeff.
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 08:19AM
Yea, there is a kinda long pause between starting the kernel and restartig.
I still have the same problem with the newest uBoot.

dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-20) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 Fri Aug 13 01:53:46 UTC 2010
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c03d2ec0, node_mem_map c043d000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32512 pages, LIFO batch:7
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    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: 128MB = 128MB total
[    0.000000] Memory: 120860KB available (3508K code, 582K data, 124K init, 0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000000] Console: colour dummy device 80x30
[    0.000122] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[    0.240078] Security Framework initialized
[    0.240099] SELinux:  Disabled at boot.
[    0.240119] Mount-cache hash table entries: 512
[    0.240368] Initializing cgroup subsys ns
[    0.240381] Initializing cgroup subsys cpuacct
[    0.240389] Initializing cgroup subsys devices
[    0.240398] Initializing cgroup subsys freezer
[    0.240406] Initializing cgroup subsys net_cls
[    0.240439] CPU: Testing write buffer coherency: ok
[    0.240990] devtmpfs: initialized
[    0.242414] regulator: core version 0.5
[    0.242588] NET: Registered protocol family 16
[    0.242973] Kirkwood: MV88F6281-A0, TCLK=200000000.
[    0.242985] Feroceon L2: Cache support initialised.
[    0.243374] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
[    0.243396]   final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
[    0.244819] bio: create slab <bio-0> at 0
[    0.245094] vgaarb: loaded
[    0.245559] Switching to clocksource orion_clocksource
[    0.249381] NET: Registered protocol family 2
[    0.249627] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.250468] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.250568] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.250621] TCP: Hash tables configured (established 4096 bind 4096)
[    0.250630] TCP reno registered
[    0.250780] NET: Registered protocol family 1
[    0.250960] Unpacking initramfs...
[    0.571181] Freeing initrd memory: 4592K
[    0.571280] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.571530] audit: initializing netlink socket (disabled)
[    0.571565] type=2000 audit(0.560:1): initialized
[    0.578166] VFS: Disk quotas dquot_6.5.2
[    0.578439] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.578537] JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.579181] msgmni has been set to 245
[    0.580889] alg: No test for stdrng (krng)
[    0.581012] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.581025] io scheduler noop registered
[    0.581032] io scheduler anticipatory registered
[    0.581040] io scheduler deadline registered
[    0.581230] io scheduler cfq registered (default)
[    0.587281] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.587761] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.911265] console [ttyS0] enabled
[    0.915332] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[    0.923939] Scanning device for bad blocks
[    0.945047] Bad eraseblock 457 at 0x000003920000
[    1.008626] 4 cmdlinepart partitions found on MTD device orion_nand
[    1.014924] Creating 4 MTD partitions on "orion_nand":
[    1.020105] 0x000000000000-0x000000100000 : "u-boot"
[    1.025678] 0x000000100000-0x000000500000 : "uImage"
[    1.031135] 0x000000500000-0x000002500000 : "rootfs"
[    1.036639] 0x000002500000-0x000010000000 : "data"
[    1.042600] mice: PS/2 mouse device common for all mice
[    2.055598] rtc-mv rtc-mv: internal RTC not ticking
[    2.060583] i2c /dev entries driver
[    2.064269] cpuidle: using governor ladder
[    2.068522] cpuidle: using governor menu
[    2.072552] Registered led device: plug:green:health
[    2.077615] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[    2.084012] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[    2.125627] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    2.165625] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[    2.205625] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[    2.245626] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[    2.252307] TCP cubic registered
[    2.255555] NET: Registered protocol family 17
[    2.260055] Gating clock of unused units
[    2.260063] before: 0x00dfc3fd
[    2.260071]  after: 0x00c701d9
[    2.260374] registered taskstats version 1
[    2.265152] /build/buildd-linux-2.6_2.6.32-20-armel-qpwOHl/linux-2.6-2.6.32/debian/build/source_armel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    2.279764] Initalizing network drop monitor service
[    2.284812] Freeing init memory: 124K
[    2.336122] udev: starting version 160
[    2.614731] MV-643xx 10/100/1000 ethernet driver version 1.4
[    2.620754] mv643xx_eth smi: probed
[    2.672376] usbcore: registered new interface driver usbfs
[    2.683864] usbcore: registered new interface driver hub
[    2.690799] net eth0: port 0 with MAC address 00:10:75:1a:ce:20
[    2.697276] mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
[    2.707414] usbcore: registered new device driver usb
[    2.729823] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.736484] orion-ehci orion-ehci.0: Marvell Orion EHCI
[    2.741792] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[    2.775608] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[    2.795592] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[    2.803630] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.810483] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.817752] usb usb1: Product: Marvell Orion EHCI
[    2.822477] usb usb1: Manufacturer: Linux 2.6.32-5-kirkwood ehci_hcd
[    2.828868] usb usb1: SerialNumber: orion-ehci.0
[    2.834453] usb usb1: configuration #1 chosen from 1 choice
[    2.840397] hub 1-0:1.0: USB hub found
[    2.844196] hub 1-0:1.0: 1 port detected
[    3.165604] usb 1-1: new high speed USB device using orion-ehci and address 2
[    3.317004] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    3.323738] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    3.330917] usb 1-1: Product: USB2.0 Hub
[    3.336242] usb 1-1: configuration #1 chosen from 1 choice
[    3.345270] hub 1-1:1.0: USB hub found
[    3.349385] hub 1-1:1.0: 4 ports detected
[    3.625915] usb 1-1.3: new high speed USB device using orion-ehci and address 3
[    4.038005] usb 1-1.3: New USB device found, idVendor=058f, idProduct=6387
[    4.044917] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.052272] usb 1-1.3: Product: Mass Storage Device
[    4.057209] usb 1-1.3: Manufacturer: JetFlash
[    4.061588] usb 1-1.3: SerialNumber: QQSF2YZ4
[    4.067309] usb 1-1.3: configuration #1 chosen from 1 choice
[    4.155051] SCSI subsystem initialized
[    4.182223] Initializing USB Mass Storage driver...
[    4.187449] scsi0 : SCSI emulation for USB Mass Storage devices
[    4.194117] usbcore: registered new interface driver usb-storage
[    4.200754] usb-storage: device found at 3
[    4.200763] usb-storage: waiting for device to settle before scanning
[    4.200799] USB Mass Storage support registered.
[    9.196014] usb-storage: device scan complete
[    9.196845] scsi 0:0:0:0: Direct-Access     JetFlash Transcend 16GB   8.07 PQ: 0 ANSI: 2
[    9.234911] sd 0:0:0:0: [sda] 31375360 512-byte logical blocks: (16.0 GB/14.9 GiB)
[    9.243021] sd 0:0:0:0: [sda] Write Protect is off
[    9.247859] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[    9.247869] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    9.256269] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    9.262398]  sda: sda1 sda2
[    9.316270] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    9.322401] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   13.716344] udev: starting version 160
[   28.262348] eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   31.662815] NET: Registered protocol family 10
[   31.670391] lo: Disabled Privacy Extensions

By the way, there seems to be a bug in the new uBoot:
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Unknown command 'mv' - try 'help'     <----------------------------
** Block device usb 0 not supported
** Block device usb 0 not supported



Edited 3 time(s). Last edit at 08/25/2010 08:36AM by Kaeltis.
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 08:36AM
That dmesg looks like it was from a successful boot. I'd try deleting it and then booting again to see if it gets re-created. If it does get re-created, it shows that your system is actually booting. If it doesn't get re-created, you may need to look into building a serial cable to look for the actual error.

-- Jeff
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 08:43AM
It gets recreated, there are actually some of the dmesgs, like dmesg, dmesg.0, dmesg0.tar.gz or something, it seems to create new logs and archive the others.



Edited 1 time(s). Last edit at 08/25/2010 08:48AM by Kaeltis.
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 08:54AM
Are you running just a normal install of Debian from my scripts, or have you made changes or installed other packages?

From your dmesg log, your system is actually booting just fine as far as the kernel is concerned. Something in userspace is causing it to reboot. You didn't use any of these ugly "echo reboot >> /etc/rcS" hacks or anything, did you ? You should check the other logs, something in there should tell you what's going on.

-- Jeff
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 08:58AM
Nope, its a normal installation from your script, but there is a change on the output of netconsole, it now shows

U-Boot 2010.06-00695-gbd23130-dirty (Aug 25 2010 - 01:20:45)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Unknown command 'mv' - try 'help'
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1430932 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4706212 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1430868 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4706148 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

that "Unknown command 'mv' - try 'help'" wasn't there before and with the new uBoot version it doesn't restart after "Starting Kernel...", it just does nothing, even after 20 minutes.



Edited 1 time(s). Last edit at 08/25/2010 08:58AM by Kaeltis.
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 09:03AM
Thanks for reporting the mv error, I've updated the uBoot installer to fix that. However, that has nothing to do with your problem.

That output is exactly what netconsole should show when your system boots properly. After the "Starting Kernel" message, control is passed to the kernel, which does not send anything to netconsole. I think your system is running. You should check your router to see if the system is just getting a different IP address.

-- Jeff
Re: Booting Debian runs into restarting loop (problems with Kernel?)
August 25, 2010 09:26AM
Holy f***in hell.. im such an idiot -___-
it really got a different IP.. this is just hilarious x'D laughing my ass of right now x)

Thanks for helping me Jeff ^^
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: