Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Current build of netbsd for rpi is unable to boot

Hello again, Im actually seeing a kernel panic for the second time now:

panic: kernel debugging assertion "mappings <= l2b->l2b_occupancy" failed:
file "/usr/src/sys/arch/arm/arm32/pmap.c", line 3838
cpu0: Begin traceback...
0xda995c3c: netbsd:db_panic+0xc
0xda995c68: netbsd:vpanic+0x144
0xda995c80: netbsd:kern_assert+0x40
0xda995cd0: netbsd:pmap_kremove+0x280
0xda995d3c: netbsd:ubc_release+0x2ac
0xda995d8c: netbsd:ubc_uiomove+0xbc
0xda995e4c: netbsd:ffs_write+0x478
0xda995e74: netbsd:VOP_WRITE+0x64
0xda995ea0: netbsd:vn_write+0xd8
0xda995ef0: netbsd:dofilewrite+0x98
0xda995f18: netbsd:sys_write+0x6c
0xda995f84: netbsd:syscall+0x8c
0xda995fac: netbsd:swi_handler+0xa0
cpu0: End traceback...

dumping to dev 24,1 offset 1179647
dump Fatal kernel mode prefetch abort at 0x00000000
trapframe: 0xdbf29e70, spsr=80000113
r0 =dbf9ec88, r1 =c04fbdcc, r2 =00000000, r3 =00000000
r4 =dbf9ec88, r5 =00000000, r6 =c04e4398, r7 =000000df
r8 =000000df, r9 =00000000, r10=00000000, r11=dbf29ef0
r12=00000000, ssp=dbf29ec0, slr=c02acc84, pc =00000000

Stopped in pid 0.3 (system) at  0:      address 0x0 is invalid
undgt   c0387749

On 12 April 2014 12:03, Joachim Thiemann <joachim.thiemann%gmail.com@localhost> 
> Hi Nick, I did.  (Thanks for the heads-up again.)  For a few days,
> building current, for some reason GNU as didn't get built, so nothing
> could get compiled on the Pi, but I crossbuilt a distribution
> yesterday and that appears to work fine after a clean install.
> I'm also just passing root=sd0a on the command line.  Since I never
> have another USB drive on during boot anyways, that works fine.
> On 12 April 2014 10:42, Nick Hudson <skrll%netbsd.org@localhost> wrote:
>> On 04/07/14 14:25, Joachim Thiemann wrote:
>>> FYI, right now this happens:
>>> [...]
>>> root file system type: ffs
>>> vchiq: local ver 6 (min 3), remote ver 6.
>>> vcaudio0 at vchiq0: AUDS
>>> WARNING: no TOD clock present
>>> WARNING: using filesystem time
>>> audio0 at vcaudio0: half duplex, playback, capture, independent
>>> warning: no /dev/console
>>> init: copying out path `/sbin/init' 11
>>> mounting sd0a on /mnt
>>> setting sysctl
>>> init.root: / -> /mnt
>>> Tue Dec  3 18:08:37 CET 2013
>>> Starting root file system check:
>>> fsck_ffs: Please implement DIOCGWEDGEINFO or DIOCGDINFO for disk
>>> device /dev/rsd0a: Inappropriate ioctl for device
>>> Unknown error 1; help!
>>> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>>> [1]   Terminated              (stty status "^T...
>>> init: /etc/pwd.db: No such file or directory
>>> Enter pathname of shell or RETURN for /rescue/sh:
>>> #
>> Please send-pr this one so it doesn't get lost. I can't remember the reason
>> behind this, but I know someone who does.
>> The easiest way around it is to upgrade your userland to match your kernel,
>> iirc.
>> Nick
> --
> Joachim Thiemann :: http://jthiem.bitbucket.org ::
> http://signalsprocessed.blogspot.com

Joachim Thiemann :: http://jthiem.bitbucket.org ::

Home | Main Index | Thread Index | Old Index