Hi!
> >> >> Do you mean try something like this? Replace the push 0 with push
> >> >> 0x1234 ; push 0x1234 ; pop ; pop and try to figure out which line
> >> >> causes the reboot?
> >> >
> >> > Yep, try pushl $0, popl %eax; if that causes problems, something is
> >> > seriously wrong with stack, otherwise changing flags hurts.
> >>
> >> pushl $0, popl %eax gets the reboot. So it's changing the flags that
> >> is bad?
> >>
> >> What should we try next?
> >
> > ??? You wanted it to reboot? If not, something is wrong with
> > stack. Not sure whats next.
>
> I don't want it to reboot, I guess I got confused. As you say, maybe
> something is wrong with the stack. It's weird that something would be
> wrong with the stack, because the other test to check the
> suspend/resume code path works like a charm, the machine will do the
> fake suspend/resume just fine.
Well, we set up stack few instructions before that. But we do it in
quite a complicated way; could you just put stack at 0x00:0x200 or
something like that? Also test if push alone is enough to kill it.
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
