Subject: NSLU2 builds and boots, but seems to disappear when running /sbin/init
To: None <port-arm@netbsd.org>
From: Donald T Hayford <don@donhayford.com>
List: port-arm
Date: 01/19/2008 18:26:19
This is a multi-part message in MIME format.
--------------080703030101000700040901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I am able to build the NSLU2 arm port, and constructed a root file
system using NFS. The first time I booted the system, I got a warning
that /dev/console was missing, and then the NSLU2 stopped with the
following message:
/
[...snip...]
root device: npe0
dump device:
file system (default generic): nfs
root on npe0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.1.102
nfs_boot: my_addr=192.168.1.240
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.1.1
root on 192.168.1.102:/video/client/root
root time: 0x4792690f
xrtc0: xrtc_clock_read: failed to read rtc at 0x0
xrtc0: xrtc_clock_read: failed to read rtc at 0x0
WARNING: preposterous TOD clock time
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
warning: no /dev/console
init path (default /sbin/init):
init: copying out path `/sbin/init' 11
[a few seconds go by]
panic: init died (signal 0, exit 12)
Stopped in pid 1.1 (init) at netbsd:cpu_Debugger+0x4: bx r14
db>
[end of text - NSLU2 is running the debugger]
/
Using the nbmknod command, I created dev/console using "sudo nbmknod
root/dev/console c 0 0" and rebooted the system. The NSLU2 appears to
boot ok (though with the same message about failing to read the rtc),
and continues through the "init path" message. The system no longer
panics and reboots, but neither does it allow me to log in. If I ping
the NSLU2 address, it responds, but I can neither ssh or telnet into the
NSLU2. If I press the power button on the front, the system powers down
with the following message stream:
/[...snip...]
init path (default /sbin/init): /sbin/init
init: copying out path `/sbin/init' 11
[NSLU2 appears to hang at this point, but responds to a ping]
[when the power button is pressed...]
slugbutt0: power button pressed, shutting down!
boot: howto=00000808 curproc=0xc048e6e4
syncing disks... done
unmounting file systems...
unmounting / (192.168.1.102:/video/client/root)... done
powering down...
[NSLU2 powers off]./
I've checked /var/log for anything that the NSLU2 might have written
there that would indicate the problem, but don't see anything. I've
used FreeBSD before, but I'm new to NetBSD, so I'm not sure where to go
next. I'm thinking that most likely I have a problem with how I set up
the NFS root, and I'm going to try to set up a usb drive to use as
root. Definitely sailing some uncharted waters here (for me, anyway).
As always, any help is greatly appreciated.
Thanks, Don
--------------080703030101000700040901
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I am able to build the NSLU2 arm port, and constructed a root file
system using NFS. The first time I booted the system, I got a warning
that /dev/console was missing, and then the NSLU2 stopped with the
following message:<br>
<i><br>
[...snip...]<br>
root device: npe0<br>
dump device:<br>
file system (default generic): nfs<br>
root on npe0<br>
nfs_boot: trying DHCP/BOOTP<br>
nfs_boot: DHCP next-server: 192.168.1.102<br>
nfs_boot: my_addr=192.168.1.240<br>
nfs_boot: my_mask=255.255.255.0<br>
nfs_boot: gateway=192.168.1.1<br>
root on 192.168.1.102:/video/client/root<br>
root time: 0x4792690f<br>
xrtc0: xrtc_clock_read: failed to read rtc at 0x0<br>
xrtc0: xrtc_clock_read: failed to read rtc at 0x0<br>
WARNING: preposterous TOD clock time<br>
WARNING: using filesystem time<br>
WARNING: CHECK AND RESET THE DATE!<br>
warning: no /dev/console<br>
init path (default /sbin/init):<br>
init: copying out path `/sbin/init' 11<br>
[a few seconds go by]<br>
panic: init died (signal 0, exit 12)<br>
Stopped in pid 1.1 (init) at netbsd:cpu_Debugger+0x4: bx
r14<br>
db><br>
[end of text - NSLU2 is running the debugger]<br>
</i><br>
Using the nbmknod command, I created dev/console using "sudo nbmknod
root/dev/console c 0 0" and rebooted the system. The NSLU2 appears to
boot ok (though with the same message about failing to read the rtc),
and continues through the "init path" message. The system no longer
panics and reboots, but neither does it allow me to log in. If I ping
the NSLU2 address, it responds, but I can neither ssh or telnet into
the NSLU2. If I press the power button on the front, the system powers
down with the following message stream:<br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 2.0 (Linux)">
<meta name="AUTHOR" content="Donald Hayford">
<meta name="CREATED" content="20080111;5130400">
<meta name="CHANGEDBY" content="Donald Hayford">
<meta name="CHANGED" content="20080119;13413200">
<style type="text/css">
<!--
@page { size: 8.5in 11in; margin: 0.79in }
P { margin-bottom: 0.08in }
--> </style><br>
<i>[...snip...]<br>
init path (default /sbin/init): /sbin/init<br>
init: copying out path `/sbin/init' 11<br>
<br>
[NSLU2 appears to hang at this point, but responds to a ping]<br>
[when the power button is pressed...]<br>
<br>
slugbutt0: power button pressed, shutting down!<br>
boot: howto=00000808 curproc=0xc048e6e4<br>
syncing disks... done<br>
unmounting file systems...<br>
unmounting / (192.168.1.102:/video/client/root)... done<br>
powering down...<br>
<br>
[NSLU2 powers off].</i><br>
<br>
I've checked /var/log for anything that the NSLU2 might have written
there that would indicate the problem, but don't see anything. I've
used FreeBSD before, but I'm new to NetBSD, so I'm not sure where to go
next. I'm thinking that most likely I have a problem with how I set up
the NFS root, and I'm going to try to set up a usb drive to use as
root. Definitely sailing some uncharted waters here (for me, anyway).<br>
<br>
As always, any help is greatly appreciated.<br>
<br>
Thanks, Don<br>
</body>
</html>
--------------080703030101000700040901--