> > > > > Below is a log of the type of crashes that occur:
> > > > >
> > > > > root@10.34.9.213:/opt/ppmac/ktest# ls
> > > > > Segmentation fault
> > > > > root@10.34.9.213:/opt/ppmac/ktest# ls
> > > > > Segmentation fault
> > > > > root@10.34.9.213:/opt/ppmac/ktest# ls
> &g
> > powerpmac login: root
> > > >
> > > > Debian GNU/Linux 7 powerpmac ttyS0
> > > >
> > > > powerpmac login: root
> > > >
> > > > Debian GNU/Linux 7 powerpmac ttyS0
> > > >
> > > > powerpmac login: root
0
> > >
> > > powerpmac login: root
> > > Password:
> > > Last login: Thu Nov 30 20:42:16 UTC 1933 on ttyS0
> > > Linux powerpmac 3.2.21-aspen_2.01.09 #10 Mon Aug 19 08:49:12 PDT 2013
> > > ppc
> > >
> > > The programs include
The programs included with the Debian GNU/Linux system are free
> > software;
> > the exact distribution terms for each program are described in the
> > individual files in /usr/share/doc/*/copyright.
> >
> > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the ext
icable law.
INIT: Id "T0" respawning too fast: disabled for 5 minutes
From: "Benjamin Herrenschmidt"
Sent: Saturday, August 17, 2013 3:05 PM
To: "Kumar Gala"
Cc: linuxppc-dev@lists.ozlabs.org, hbaus...@deltatau.com
Subject: Re: C
ux powerpmac 3.2.21-aspen_2.01.09 #10 Mon Aug 19 08:49:12 PDT 2013
>> ppc
>>
>> The programs included with the Debian GNU/Linux system are free
>> software;
>> the exact distribution terms for each program are described in the
>> individual files in /usr/share/doc/*/copyr
g too fast: disabled for 5 minutes
>
>
> ______
> From: "Benjamin Herrenschmidt"
> Sent: Saturday, August 17, 2013 3:05 PM
> To: "Kumar Gala"
> Cc: linuxppc-dev@lists.ozlabs.org, hbaus...@deltata
On Fri, 2013-08-16 at 06:04 -0500, Kumar Gala wrote:
> The 44x low level code needs to handle exception stacks properly for
> this to work. Since its possible to have a critical exception occur
> while in a normal exception level, you have to have proper saving of
> additional register state and a
On Aug 15, 2013, at 11:57 PM, Henry Bausley wrote:
>
> Is there any reason that a Critical Input Interrupt will not work reliably on
> a 44x powerpc?
>
> I am using an AMCC now Applied Micro AMCC460EX
>
> and changed
>
> CRITICAL_EXCEPTION(0x0100, CriticalInput, unknown_exception)
> to
> CR
Is there any reason that a Critical Input Interrupt will not work reliably
on a 44x powerpc?
I am using an AMCC now Applied Micro AMCC460EX
and changed
CRITICAL_EXCEPTION(0x0100, CriticalInput, unknown_exception)
to
CRITICAL_EXCEPTION(0x0100, CriticalInput, do_MyCritIntr)
The code for the ha
10 matches
Mail list logo
