panic ibm4xx machines

Hi! all,

My OpenBlockS (evbppc) panics when boot time.

## Transferring control to NetBSD stage-2 loader (at address 00025000) ...
+40000000,
00025000-40000000 -> 00600000-40000000 = 3fa00000
panic: evcnt_attach_static: evcnt non initialized: group=<cpu> name=<tlbmiss>
Stopped in pid 0.1 (system) at  0x4d9e8:        lwz     r0, 0x14(r1)
db> bt
0x005ffe40: at 0x221c88
0x005ffe90: at 0x215328
0x005ffeb0: at 0x1d3538
0x005ffef0: at 0x1d101c
0x005fff10: at 0x250e8
db>

I think this reason is:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/kern/subr_evcnt.c.diff?r1=1.7&r2=1.8&only_with_tag=MAIN&f=h

evcnt_attach_static() is called in
arch/powerpc/ibm4xx/pmap.c:pmap_bootstrap().

Please better fix.  ;-<

Thanks,
--
kiyohara

Re: panic ibm4xx machines

On Sun, Feb 06, 2011 at 10:39:55PM +0900, KIYOHARA Takashi wrote:
> Hi! all,
> 
> 
> My OpenBlockS (evbppc) panics when boot time.
> 
> ## Transferring control to NetBSD stage-2 loader (at address 00025000) ...
> +40000000,
> 00025000-40000000 -> 00600000-40000000 = 3fa00000
> panic: evcnt_attach_static: evcnt non initialized: group=<cpu> name=<tlbmiss>
> Stopped in pid 0.1 (system) at  0x4d9e8:        lwz     r0, 0x14(r1)

See also PR #44502, for a similar losage uncovered by that diagnostic.
Could you do a similar change for ppc and move the evencounter initializiation
to cpu_startup() ?

Martin

Re: NAS support ready for upcoming releases

Erik Fair wrote:

> 1. Are there any NAS boxes with ECC RAM subsystems?

Don't know. I didn't check yet. The boxes I have seen seem to use non-ECC
RAM.

But I know the 824x's memory interface supports ECC, and it could be useful
for a file server. So it would be strange when such a configuration doesn't
exist.

> 2. Are the portmasters committed to maintaining a list of specific
> manufacturers/models that NetBSD is known to work, and (further) a list
> of "probable" systems (because they're based on substantially the same
> hardware as the port(s) was developed on)?

A list of already supported (but mostly untested) models is on
  http://www.NetBSD.org/ports/sandpoint/

More 8241/8245-based models are listed in:
  src/sys/arch/sandpoint/README.NAS

--

-- 
Frank Wille

Re: panic ibm4xx machines

Hi! Martin,

From: Martin Husemann <martin <at> duskware.de>
Date: Sun, 6 Feb 2011 19:43:10 +0100

> On Sun, Feb 06, 2011 at 10:39:55PM +0900, KIYOHARA Takashi wrote:
> > Hi! all,
> > 
> > 
> > My OpenBlockS (evbppc) panics when boot time.
> > 
> > ## Transferring control to NetBSD stage-2 loader (at address 00025000) ...
> > +40000000,
> > 00025000-40000000 -> 00600000-40000000 = 3fa00000
> > panic: evcnt_attach_static: evcnt non initialized: group=<cpu> name=<tlbmiss>
> > Stopped in pid 0.1 (system) at  0x4d9e8:        lwz     r0, 0x14(r1)
> 
> See also PR #44502, for a similar losage uncovered by that diagnostic.
> Could you do a similar change for ppc and move the evencounter initializiation
> to cpu_startup() ?

Thanks for your reply.
First of all, I will evade DIAGNOSTIC from my kernel though I hope to
fix anyway.

Thanks,
--
kiyohara

Re: -current userland working for others?

On Feb 6, 2011, at 9:53 AM, Jeff Rizzo wrote:

> Since the PPC changes brought in a couple weeks ago, I have not been able to run a -current userland on my G4/400.
> 
> There was a problem where the kernel would not start, which was fixed by matt <at>  after a few days, and I can
successfully boot a GENERIC from the latest autobuilds.  However, when I unpack userland (base.tgz, in
this case), basically all binaries except those in /rescue stop working.  I get these kinds of messages
from the kernel:
> 
> trap: pid 694.1 (ls): user read DSI trap  <at>  0x407eb46c by 0xeff0f2dc (DSISR 0x40000000, err=14)
> trap: pid 541.1 (dmesg): user ISI trap  <at>  0x2000 (SRR1=0x4000f032)
> trap: pid 167.1 (dmesg): user ISI trap  <at>  0x2000 (SRR1=0x4000f032)
> 
> 
> ...once I back out to userland from 20110111, things start working again.
> 
> Does anyone have any clue what's going on here?  This is the box that I was using to run ATF tests on, and it's
basically been idle for three weeks because of this.

The latest commit to powerpc/include/asm.h fixes this.  I didn't realize
that after my changes that binutils/gcc automatically switched to using
secure-plt by default.  The change to asm.h make .S files use secureplt
as well.

One side effect of this is that PPC programs will no longer have 
executable .data/.bss and startup times will be slightly faster.

Re: -current userland working for others?

On 2/7/11 11:29 AM, Jeff Rizzo wrote:
> On 2/6/11 10:47 PM, Matt Thomas wrote:
>> On Feb 6, 2011, at 9:53 AM, Jeff Rizzo wrote:
>>
>>> Since the PPC changes brought in a couple weeks ago, I have not been 
>>> able to run a -current userland on my G4/400.
>>>
>>> There was a problem where the kernel would not start, which was 
>>> fixed by matt <at>  after a few days, and I can successfully boot a 
>>> GENERIC from the latest autobuilds.  However, when I unpack userland 
>>> (base.tgz, in this case), basically all binaries except those in 
>>> /rescue stop working.  I get these kinds of messages from the kernel:
>>>
>>> trap: pid 694.1 (ls): user read DSI trap  <at>  0x407eb46c by 0xeff0f2dc 
>>> (DSISR 0x40000000, err=14)
>>> trap: pid 541.1 (dmesg): user ISI trap  <at>  0x2000 (SRR1=0x4000f032)
>>> trap: pid 167.1 (dmesg): user ISI trap  <at>  0x2000 (SRR1=0x4000f032)
>>>
>>>
>>> ...once I back out to userland from 20110111, things start working 
>>> again.
>>>
>>> Does anyone have any clue what's going on here?  This is the box 
>>> that I was using to run ATF tests on, and it's basically been idle 
>>> for three weeks because of this.
>> The latest commit to powerpc/include/asm.h fixes this.  I didn't realize
>> that after my changes that binutils/gcc automatically switched to using
>> secure-plt by default.  The change to asm.h make .S files use secureplt
>> as well.
>>

(unknown)

RB1100 (almost) boots with RB800 kernel

Hello,

Just noticed that RB800 support was added to NetBSD CVS tree, and
decided to try it out on RB1100.

So, installed a fresh NetBSD 5.1, cross-compiled evbppc / RB800 from
-current and it seems to load.

Got to root filesystem prompt, and in some seconds watchdog timeout
panic'd. After
ten secs or so, the system rebooted automatically. Didn't try to load
NFS root yet.

Here's some info I managed to get from RouterOS admin interface,
including PCI and IRQ info:
http://www.cs.helsinki.fi/u/jvtmuukk/rb1100/rb1100-routeros-info.txt

RB1100 has micro-SD slot instead of CF; and RouterBoot doesn't
actually support booting from SD.

I don't have Linux dmesg (yet...), MikroTik's RouterOS is somewhat restricted:
 - doesn't allow shell access
 - update packages (.npk) are nowadays signed (so can't install sshd)
 - no boot messages visible through serial port
 - no success yet on booting the official Linux kernel from network

Will experiment more later. Anyone else with RB1100?

Here's the boot log, also available at
http://www.cs.helsinki.fi/u/jvtmuukk/rb1100/rb1100-netbsd-RB800-boot-000.log

Re: RB1100 (almost) boots with RB800 kernel

On Feb 13, 2011, at 4:52 PM, Jyrki Muukkonen wrote:

> Hello,
> 
> Just noticed that RB800 support was added to NetBSD CVS tree, and
> decided to try it out on RB1100.
> 
> So, installed a fresh NetBSD 5.1, cross-compiled evbppc / RB800 from
> -current and it seems to load.
> 
> Got to root filesystem prompt, and in some seconds watchdog timeout
> panic'd. After
> ten secs or so, the system rebooted automatically. Didn't try to load
> NFS root yet.

That's expected since I didn't commit the cons.c change to poll the
console so the wdog doesn't get pet and boom.

Use the nfsnetbsd kernel and see what happens.

Thanks for feedback.  MikroTik was no help in getting the RB800 running.
I'd love to get the CF running on the RB800.  There is an alc driver
floating around should may work.

DSI trap in init

Since a couple of days the init process dies on several (all?) PowerPC
ports. This message appears infinitely when launching /sbin/init:

Process (pid 1) got sig 11
trap: pid 1.1 (init): user read DSI trap  <at>  0xffffffff by 0xefe940fc (DSISR 0x40000000, err=14)

I tested with a G3 under ofppc and with a MPC8241 under sandpoint.
Generic kernel and userland are from yesterday.

--

-- 
Frank Wille