Re: RPI kernels in -current expected to work?

["David H. Gutteridge" <dhgutteridge%sympatico.ca@localhost>]

On Sun, 06 Apr 2014 at 18:19:19, Frank Kardel wrote:
>Great ! Thanks - works again.
>
>Frank
>
>On 04/06/14 14:43, Nick Hudson wrote:
>>    On 04/06/14 13:01, Frank Kardel wrote:
>>>
>>>        Hi,
>>>
>>>        I see a long stream of
>>>
>>>        fixup: pd ....
>>>        fixup: pde ... nothing to do
>>>
>>>        lines scrolling (forever?) after the initial boot kernel messages.
>>>
>>>        The boot process does not seem to make any reasonably observable 
>>> progress at that point.
>>>
>>>
>>>        This happens with self compiled kernels (as of 2014-04-06) and
>>>        kernels fetched from nyftp for 20140403 and 20140406.
>>>
>>>        The following older kernel works:
>>>        NetBSD rpi 6.99.38 NetBSD 6.99.38 (RPI) #0: Sat Mar 29 06:14:39 UTC 
>>> 2014
>>>
>>>builds%b44.netbsd.org@localhost:/home/builds/ab/HEAD/evbarm-earmhf/201403290440Z-obj/home/builds/ab/HEAD/src/sys/arch/evbarm/compile/RPI
>>> evbarm
>>>
>>>
>>>        Best regards,
>>>          Frank
>>>
>>>
>>    cvs update :)
>>
>>    Nick

I was seeing the same thing, and now have a working kernel again too,
though I've noticed userland tools that report kernel memory use seem
a bit confused after recent commits. (Not that that's a big deal to
me, I'm just mentioning it in case it's unexpected.)

ps(1) gives:

USER     PID %CPU %MEM   VSZ     RSS TTY   STAT STARTED    TIME COMMAND
root       0  0.0 -10.0     0 4148560 ?     DKl   8:28PM 0:04.66 [system]

top(1) gives:

  PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COMMAND
    0 root      96    0     0K -47808K mmctaskq   0:27  0.00%  0.00% [system]

Regards,

Dave