NetBSD Problem Report #48130
From ryo_on@yk.rim.or.jp Fri Aug 16 18:27:12 2013
Return-Path: <ryo_on@yk.rim.or.jp>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "Postmaster NetBSD.org" (verified OK))
by mollari.NetBSD.org (Postfix) with ESMTPS id D49D87140D
for <gnats-bugs@gnats.NetBSD.org>; Fri, 16 Aug 2013 18:27:11 +0000 (UTC)
Message-Id: <20130816171037.6C30B10113E8B@mail.SiriusCloud.jp>
Date: Sat, 17 Aug 2013 02:10:37 +0900 (JST)
From: ryoon@NetBSD.org
Reply-To: ryoon@NetBSD.org
To: gnats-bugs@gnats.NetBSD.org
Subject: With earm MARVEL_NAS kernel, /sbin/init exits with panic: init died (signal 0, exit 11)
X-Send-Pr-Version: 3.95
>Number: 48130
>Category: port-arm
>Synopsis: With earm MARVEL_NAS kernel, /sbin/init exits with panic: init died (signal 0, exit 11)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: port-arm-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Aug 16 18:30:00 +0000 2013
>Closed-Date: Fri Sep 30 08:20:36 +0000 2016
>Last-Modified: Fri Sep 30 08:20:36 +0000 2016
>Originator: Ryo ONODERA
>Release: NetBSD 6.99.23
>Organization:
>Environment:
System: NetBSD tellurium.elements.tetera.org 6.99.23 NetBSD 6.99.23 (DTRACE) #2: Thu Aug 8 10:01:27 JST 2013 ryo_on@tellurium.elements.tetera.org:/usr/obj/amd64/sys/arch/amd64/compile/DTRACE amd64
Architecture: x86_64
Machine: amd64
>Description:
MARVELL_NAS kernel of NetBSD/evbearm-el current of 2013-08-16 does not boot.
/sbin/init exits with "panic: init died (signal 0, exit 11)" message.
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** LOADER **
** MARVELL BOARD: DB-88F6281A-BP LE
U-Boot 1.1.4 (Apr 23 2009 - 19:01:28) Marvell version: 3.4.4
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690DCC
Soc: MV88F6281 Rev 3 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
[16384kB@f8000000] Flash: 16 MB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
*** Warning - bad CRC, using default environment
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
QNAP: Recovery Button pressed: 0
Marvell>> setenv serverip 192.168.81.249
Marvell>> setenv ipaddr 192.168.81.127
Marvell>> tftp 0x800000 netbsd.ub
Using egiga0 device
TFTP from server 192.168.81.249; our IP address is 192.168.81.127
Filename 'netbsd.ub'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###########################################################
done
Bytes transferred = 4293568 (4183c0 hex)
Marvell>> bootm
## Booting image at 00800000 ...
Image Name: NetBSD/ 6.99.23
Created: 2013-08-16 17:02:09 UTC
Image Type: ARM NetBSD Kernel Image (uncompressed)
Data Size: 4293504 Bytes = 4.1 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Transferring control to NetBSD stage-2 loader (at address 00008000) ...
NetBSD/evbarm (Marvell) booting ...
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 6.99.23 (MARVELL_NAS) #1: Sat Aug 17 02:02:08 JST 2013
ryo_on@tellurium.elements.tetera.org:/usr/obj/evbearm/sys/arch/evbarm/compile/MARVELL_NAS
total memory = 256 MB
avail memory = 246 MB
mainbus0 (root)
cpu0 at mainbus0 core 0: Sheeva 88SV131 rev 1 (ARM9E-S V5TE core)
cpu0: DC enabled IC enabled WB enabled EABT branch prediction enabled
cpu0: 16KB/32B 4-way L1 Instruction cache
cpu0: 16KB/32B 4-way write-back-locking-C L1 Data cache
mvsoc0 at mainbus0: Marvell 88F6281 Rev. A1 Kirkwood
mvsoc0: CPU Clock 800.000 MHz SysClock 400.000 MHz TClock 200.000 MHz
mvsoctmr0 at mvsoc0 unit 0 offset 0x20300-0x203ff: Marvell SoC Timer
mvsocgpp0 at mvsoc0 unit 0 offset 0x10100-0x101ff irq 35: Marvell SoC General Purpose I/O Port Interface
mvsocgpp0: 50 gpio pins
mvsocgpp0: interrupts 96..103, intr 35
mvsocgpp0: interrupts 104..111, intr 36
mvsocgpp0: interrupts 112..119, intr 37
mvsocgpp0: interrupts 120..127, intr 38
mvsocgpp0: interrupts 128..135, intr 39
mvsocgpp0: interrupts 136..143, intr 40
mvsocgpp0: interrupts 144..151, intr 41
mvsocgpp0: Data Out: 0x00000000
mvsocgpp0: Data Out Enable Control: 0x00012000
mvsocgpp0: Data Blink Enable: 0x00000000
mvsocgpp0: Data In Polarity: 0x00000000
mvsocgpp0: Data In: 0x00010000
mvsocgpp0: Interrupt Cause: 0x00000000
mvsocgpp0: Interrupt Mask: 0x00000000
mvsocgpp0: Interrupt Level Mask: 0x00000000
mvsocgpp0: High Data Out: 0x0000000c
mvsocgpp0: High Data Out Enable Ctrl: 0xffffffd3
mvsocgpp0: High Blink Enable: 0x00000000
mvsocgpp0: High Data In Polarity: 0x00000000
mvsocgpp0: High Data In: 0x0000004c
mvsocgpp0: High Interrupt Cause: 0x00000000
mvsocgpp0: High Interrupt Mask: 0x00000000
mvsocgpp0: High Interrupt Level Mask: 0x00000000
gpio0 at mvsocgpp0: 50 pins
mvsocrtc at mvsoc0 unit 0 not configured
com0 at mvsoc0 unit 0 offset 0x12000-0x1201f irq 33: ns16550a, working fifo
com0: console
com1 at mvsoc0 unit 1 offset 0x12100-0x1211f irq 34: ns16550a, working fifo
ehci0 at mvsoc0 unit 0 offset 0x50000-0x51fff irq 19: Marvell USB 2.0 Interface
usb0 at ehci0: USB revision 2.0
gtidmac0 at mvsoc0 unit 0 offset 0x60000-0x60fff: Marvell IDMA Controller/XOR Engine
gtidmac0: XOR Engine 4 channels, intr 5...8
gttwsi0 at mvsoc0 unit 0 offset 0x11000-0x110ff irq 29: Marvell TWSI controller
iic0 at gttwsi0: I2C bus
mvcesa0 at mvsoc0 unit 0 offset 0x30000-0x3ffff irq 22: Marvell Cryptographic Engines and Security Accelerator
mvgbec0 at mvsoc0 unit 0 offset 0x70000-0x73fff: Marvell Gigabit Ethernet Controller
mvgbe0 at mvgbec0 port 0 irq 11
mvgbe0: Ethernet address 00:50:43:3c:3b:5d
makphy0 at mvgbe0 phy 8: Marvell 88E1116R Gigabit PHY, rev. 0
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
mvsoc0: mvgbec1 clock disabled
mvpex0 at mvsoc0 unit 0 offset 0x40000-0x41fff irq 9: Marvell PCI Express Interface
pci0 at mvpex0
Marvell 88F6281 SoC Kirkwood (miscellaneous memory, revision 0x03) at pci0 dev 0 function 0 not configured
mvsata0 at mvsoc0 unit 0 offset 0x80000-0x87fff irq 21: Marvell Serial-ATA Host Controller (SATAHC)
mvsata0: GenIIe, 1hc, 2port/hc
atabus0 at mvsata0 channel 0
atabus1 at mvsata0 channel 1
mvsdio at mvsoc0 unit 0 not configured
uhub0 at usb0: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
mvsata0 port 0: device present, speed: 3.0Gb/s
wd0 at atabus0 drive 0
wd0: <WDC WD20EARS-00MVWB0>
wd0: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 bytes/sect x 3907029168 sectors
uhub1 at uhub0 port 1: Genesys Logic USB2.0 Hub, class 9/0, rev 2.00/77.60, addr 2
uhub1: single transaction translator
boot device: <unknown>
root device: mvgbe0
dump device:
file system (default generic):
root on mvgbe0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.81.249
nfs_boot: my_domain=elements.tetera.org
nfs_boot: my_addr=192.168.81.127
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.81.1
root on 192.168.81.249:/exports/ts110
root file system type: nfs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
warning: no /dev/console
init path (default /sbin/init):
init: trying /sbin/init
panic: init died (signal 0, exit 11)
rebooting...
>How-To-Repeat:
See above.
>Fix:
I have no idea.
>Release-Note:
>Audit-Trail:
From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-arm/48130: With earm MARVEL_NAS kernel, /sbin/init exits
with panic: init died (signal 0, exit 11)
Date: Sat, 17 Aug 2013 14:46:49 +0900 (JST)
With 2013-08-17's MARVELL_NAS earm kernel and same date's userland,
This system is unstable and has some types of errors.
=== === === === === === === === === === === === === === === ===
uhub1: single transaction translator
boot device: <unknown>
root device: mvgbe0
dump device:
file system (default generic):
root on mvgbe0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.81.249
nfs_boot: my_domain=elements.tetera.org
nfs_boot: my_addr=192.168.81.127
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.81.1
root on 192.168.81.249:/exports/ts110
root file system type: nfs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
init path (default /sbin/init):
init: trying /sbin/init
/etc/defaults/rc.conf: Out of space
[and freeze]
=== === === === === === === === === === === === === === === ===
uhub1: single transaction translator
boot device: <unknown>
root device: mvgbe0
dump device:
file system (default generic):
root on mvgbe0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.81.249
nfs_boot: my_domain=elements.tetera.org
nfs_boot: my_addr=192.168.81.127
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.81.1
root on 192.168.81.249:/exports/ts110
root file system type: nfs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
init path (default /sbin/init):
init: trying /sbin/init
[: 0: unexpected operator
Node type = 1970038367
init: kernel security level chan
NetBSD/evbarm (Amnesiac) (console)
login: root
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD ?.? (UNKNOWN)
Welcome to NetBSD!
This system is running a development snapshot of the NetBSD operating system,
also known as NetBSD-current. It is very possible that it has serious bugs,
regressions, broken features or other problems. Please bear this in mind
and use the system with care.
You are encouraged to test this version as thoroughly as possible. Should you
encounter any problem, please report it back to the development team using the
send-pr(1) utility (requires a working MTA). If yours is not properly set up,
use the web interface at: http://www.NetBSD.org/support/send-pr.html
Thank you for helping us test and improve NetBSD.
panic: init died (signal 4, exit 0)
rebooting...
=== === === === === === === === === === === === === === === ===
uhub1: single transaction translator
boot device: <unknown>
root device: mvgbe0
dump device:
file system (default generic):
root on mvgbe0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.81.249
nfs_boot: my_domain=elements.tetera.org
nfs_boot: my_addr=192.168.81.127
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.81.1
root on 192.168.81.249:/exports/ts110
root file system type: nfs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
init path (default /sbin/init):
init: trying /sbin/init
[1] Illegal instruction (core dumped) (stty status "^T...
cognised: not found
--
Ryo ONODERA // ryo_on@yk.rim.or.jp
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-arm/48130: With earm MARVEL_NAS kernel, /sbin/init exits with panic: init died (signal 0, exit 11)
Date: Sat, 17 Aug 2013 06:24:19 +0000 (UTC)
ryo_on@yk.rim.or.jp (Ryo ONODERA) writes:
> With 2013-08-17's MARVELL_NAS earm kernel and same date's userland,
> This system is unstable and has some types of errors.
On SHEEVAPLUG, also earm, with sources from 2013-08-11, something
similar happens. The kernel starts, init starts and sh bombs
out with signal 11.
I tried the same with /rescue/sh which again fails with signal 11.
The I tried the same binaries on an otherwise working but slightly
older RPI system. The dynamically linked 'sh' (using the libraries
of the system) worked fine. The statically linked rescue binary failed
with signal 11.
This would indicate a problem in the library code.
But then, the slightly older /rescue/sh from the RPI system showed
exactly the same issue.
From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-arm/48130: With earm MARVEL_NAS kernel, /sbin/init exits
with panic: init died (signal 0, exit 11)
Date: Mon, 09 Sep 2013 22:50:05 +0900 (JST)
Hi,
With 2013-09-08's kernel (MARVELL_NAS) and userland, evbearm-el on kirkeood
is still broken for me.
What information is needed to fix this problem?
boot device: <unknown>
root device: mvgbe0
dump device:
file system (default generic):
root on mvgbe0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.81.249
nfs_boot: my_domain=elements.tetera.org
nfs_boot: my_addr=192.168.81.127
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.81.1
root on 192.168.81.249:/exports/ts110
root file system type: nfs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
warning: no /dev/console
init path (default /sbin/init):
init: trying /sbin/init
panic: init died (signal 0, exit 11)
rebooting...
--
Ryo ONODERA // ryo_on@yk.rim.or.jp
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-arm/48130: With earm MARVEL_NAS kernel, /sbin/init exits
with panic: init died (signal 0, exit 11)
Date: Mon, 16 Sep 2013 14:48:44 +0900 (JST)
Hi,
Petri Laakso has advised me putting "set -x" to /etc/rc.
I have gotten the following result. His result is same.
+ date
+ '\''print_rc_metadata'\'' '\''start:Mon Sep 16 05:23:38 UTC 2013'\''
+ '\''['\'' -n 9 '\'']'\''
+ command printf '\''%s%s\n'\'' '\''[metadata:'\'' '\''start:Mon Sep 16 05:23:38 UTC 2013'\'']
[/etc/rc starting at Mon Sep 16 05:23:38 UTC 2013]
+ /bin/sh -c '\''ps -p $$ -o ppid='\''
+ '\''RC_PID= 18'\''
+ kill -0 18
'
+ 'rc_log_flush'
+ ':' false
+ return 1
+ false
+ printf '%s\n' '+ kill -0 18'
+ command printf '%s\n' '+ kill -0 18'
+ kill -0 18
+ ':'
+ read -r line
[freeze]
I will try yesterday's evbearm and evbarm later.
--
Ryo ONODERA // ryo_on@yk.rim.or.jp
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-arm/48130: evbarm /etc/rc get stuck after printing timestamp
Date: Mon, 7 Oct 2013 04:12:59 +0000
two messages that didn't get to gnats (you need to have the PR number
in the subject in the right form, or it ignores you)
------
From: Petri Laakso <petri.laakso@asd.fi>
To: gnats-bugs@NetBSD.org
cc: port-arm-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, ryoon@NetBSD.org
Subject: evbarm /etc/rc get stuck after printing timestamp
Date: Mon, 16 Sep 2013 10:55:25 +0300 (EEST)
On Mon, 16 Sep 2013, Ryo ONODERA wrote:
> The following reply was made to PR port-arm/48130; it has been noted by GNATS.
>
> From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: port-arm/48130: With earm MARVEL_NAS kernel, /sbin/init exits
> with panic: init died (signal 0, exit 11)
> Date: Mon, 16 Sep 2013 14:48:44 +0900 (JST)
>
> Hi,
>
> Petri Laakso has advised me putting "set -x" to /etc/rc.
> I have gotten the following result. His result is same.
>
> + date
> + '\''print_rc_metadata'\'' '\''start:Mon Sep 16 05:23:38 UTC 2013'\''
> + '\''['\'' -n 9 '\'']'\''
> + command printf '\''%s%s\n'\'' '\''[metadata:'\'' '\''start:Mon Sep 16 05:23:38 UTC 2013'\'']
> [/etc/rc starting at Mon Sep 16 05:23:38 UTC 2013]
> + /bin/sh -c '\''ps -p $$ -o ppid='\''
> + '\''RC_PID= 18'\''
> + kill -0 18
> '
> + 'rc_log_flush'
> + ':' false
> + return 1
> + false
> + printf '%s\n' '+ kill -0 18'
> + command printf '%s\n' '+ kill -0 18'
> + kill -0 18
> + ':'
> + read -r line
> [freeze]
I can confirm I saw similar results. Only pid for kill seems to differ.
/etc/rc gets stuck after printing timestamp, when entering multiuser.
I have documented steps to reproduce this for me at
http://www.asd.fi/cgi-bin/blog.cgi/NetBSD/NetBSD_OLinuXino.1024px
root file system type: ffs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
init path (default /sbin/init):
init: trying /sbin/init
[removed lots of rc debug output]
+ 'rc_log_flush'
+ ':' false
+ return 1
+ false
+ printf '%s\n' '+ kill -0 9'
+ command printf '%s\n' '+ kill -0 9'
+ kill -0 9
+ ':'
+ read -r line
[nothing after this]
I've been able to enter ddb and have access to JTAG and willing to install
gdb to trace this bug. I just don't know where to look at.
Please note that dmesg for kernel my printed
"sysctl_createv: sysctl_create(machine_arch) returned 17"
and this puzzles me.
I'm going to build new kernel and sets with build.sh -m evbarm
instead of -m evbearmv5-el to see if this is somehow related.
(before I have had working multiuser installs build with just -m evbarm)
Please note: IMX23_OLINUXINO and MARVELL_NAS uses ARM9E processors.
Best regards
Petri Laakso
----- End forwarded message -----
----- Forwarded message from Petri Laakso <petri.laakso@asd.fi> -----
From: Petri Laakso <petri.laakso@asd.fi>
To: gnats-bugs@NetBSD.org
Cc: port-arm-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, ryoon@NetBSD.org
Subject: Re: evbarm /etc/rc get stuck after printing timestamp
Date: Mon, 16 Sep 2013 19:24:20 +0300
On Mon, 16 Sep 2013 10:55:25 +0300 (EEST)
Petri Laakso <petri.laakso@asd.fi> wrote:
>
>
> On Mon, 16 Sep 2013, Ryo ONODERA wrote:
>
> > The following reply was made to PR port-arm/48130; it has been noted by GNATS.
> >
> > From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
> > To: gnats-bugs@NetBSD.org
> > Cc:
> > Subject: Re: port-arm/48130: With earm MARVEL_NAS kernel, /sbin/init exits
> > with panic: init died (signal 0, exit 11)
> > Date: Mon, 16 Sep 2013 14:48:44 +0900 (JST)
> >
> > Hi,
> >
> > Petri Laakso has advised me putting "set -x" to /etc/rc.
> > I have gotten the following result. His result is same.
> >
> > + date
> > + '\''print_rc_metadata'\'' '\''start:Mon Sep 16 05:23:38 UTC 2013'\''
> > + '\''['\'' -n 9 '\'']'\''
> > + command printf '\''%s%s\n'\'' '\''[metadata:'\'' '\''start:Mon Sep 16 05:23:38 UTC 2013'\'']
> > [/etc/rc starting at Mon Sep 16 05:23:38 UTC 2013]
> > + /bin/sh -c '\''ps -p $$ -o ppid='\''
> > + '\''RC_PID= 18'\''
> > + kill -0 18
> > '
> > + 'rc_log_flush'
> > + ':' false
> > + return 1
> > + false
> > + printf '%s\n' '+ kill -0 18'
> > + command printf '%s\n' '+ kill -0 18'
> > + kill -0 18
> > + ':'
> > + read -r line
> > [freeze]
>
> I can confirm I saw similar results. Only pid for kill seems to differ.
> /etc/rc gets stuck after printing timestamp, when entering multiuser.
> I have documented steps to reproduce this for me at
> http://www.asd.fi/cgi-bin/blog.cgi/NetBSD/NetBSD_OLinuXino.1024px
>
> root file system type: ffs
> WARNING: no TOD clock present
> WARNING: using filesystem time
> WARNING: CHECK AND RESET THE DATE!
> init path (default /sbin/init):
> init: trying /sbin/init
> [removed lots of rc debug output]
> + 'rc_log_flush'
> + ':' false
> + return 1
> + false
> + printf '%s\n' '+ kill -0 9'
> + command printf '%s\n' '+ kill -0 9'
> + kill -0 9
> + ':'
> + read -r line
> [nothing after this]
>
> I've been able to enter ddb and have access to JTAG and willing to install
> gdb to trace this bug. I just don't know where to look at.
>
> Please note that dmesg for kernel my printed
> "sysctl_createv: sysctl_create(machine_arch) returned 17"
> and this puzzles me.
>
> I'm going to build new kernel and sets with build.sh -m evbarm
> instead of -m evbearmv5-el to see if this is somehow related.
> (before I have had working multiuser installs build with just -m evbarm)
>
> Please note: IMX23_OLINUXINO and MARVELL_NAS uses ARM9E processors.
I was able to boot multiuser with today's -current when I build with:
"-m evbarm"
Thank you!
Petri Laakso
State-Changed-From-To: open->feedback
State-Changed-By: skrll@NetBSD.org
State-Changed-When: Mon, 21 Oct 2013 08:41:09 +0000
State-Changed-Why:
I think this got fixed. OK to close?
State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Fri, 30 Sep 2016 08:20:36 +0000
State-Changed-Why:
feedback timeout
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home