Re: init receiving SIGILL on XEN3_DOM0/amd64

[Abrasive <abrasive%axdf.net@localhost>]

On Sun, May 18, 2008 at 01:43:04PM +0200, Christoph Egger wrote:
> Manuel Bouyer wrote:
> >On Sun, May 18, 2008 at 01:09:54PM +0200, Christoph Egger wrote:
> >>Manuel Bouyer wrote:
> >>What are the normal conditions where the kernels sends SIGILL to userland?
> >
> >When the CPU sends an illegal intruction trap, I guess.
> >
> 
> In that case, I have a wild guess:
> sysenter is an illegal opcode on amd64. The difference is, AMD CPUs 
> throw an exception, Intel CPUs don't.
> Is sysenter used somewhere?

I can't find it anywhere in sys/arch except for header constants, so I would 
guess the answer is No.
Is the rip value it was trapping on likely to be in data/stack memory? 
Something being sloppy with the stack somewhere.