On Wed, 7 Jan 2009, malc wrote:
> On Wed, 7 Jan 2009, Benjamin Herrenschmidt wrote:
>
> >
> > > As you wish :) I've written some ad-hoc stuff in the failing path which
> > > manually triggers sysrq and then sends the klogctl output via network
> > > and here it is:
> >
> > Allright, something's unclear to me. What do you mean by the system goes
> > down then ? The kernel appears to be working at least to a certain
> > extent if you manage to trigger a sysrq from userspace... And from what
> > I see, it looks that all processes are somewhere in schedule.
> >
> > So what is precisely your symptom here ?
After writing valgrind tool that was simulating Cell XER.SO syscall
(mis)behaviour (pre ab598b6680f1e74c267d1547ee352f3e1e530f89 that is)
and banging my had against the wall for a while trying to figure out
which of the failing syscalls was responsible, i've tried to be simple
and after only ~30 minutes came up with this, rather short, piece of
code that knocks pre XER.SO patched kernels out cold:
gcc -o xer -x assembler /dev/stdin -nostdlib <<eof
.globl _start
_start:
addis 0,0,0x8000
mtxer 0
addi 0,0,1
sc
eof
--
mailto:av1...@comtv.ru
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
