Re: [Opps] Invalid opcode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: S.Çağlar Onur <[email protected]>
Subject: Re: [Opps] Invalid opcode
From: Jan Engelhardt <[email protected]>
Date: Sun, 5 Nov 2006 18:25:31 +0100 (MET)
Cc: Andi Kleen <[email protected]>, [email protected], Zachary Amsden <[email protected]>, Gerd Hoffmann <[email protected]>, john stultz <[email protected]>
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]>
Sender: [email protected]

>05 Kas 2006 Paz 18:40 tarihinde, Andi Kleen şunları yazmıştı: 
>> How do you know this?
>
>Just guessing, if im not wrong panics occur after SMP alternative switching 
>code done its job.

Possibly compiled a kernel with instructions your processor does not 
support? Come to think of cmov...



	-`J'
--

Follow-Ups:
- Re: [Opps] Invalid opcode
  - From: "S.Çağlar Onur" <[email protected]>

References:
- [Opps] Invalid opcode
  - From: "S.Çağlar Onur" <[email protected]>
- Re: [Opps] Invalid opcode
  - From: Andi Kleen <[email protected]>
- Re: [Opps] Invalid opcode
  - From: "S.Çağlar Onur" <[email protected]>

Prev by Date: Re: [rfc patch] i386: don't save eflags on task switch
Next by Date: Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)
Previous by thread: Re: [Opps] Invalid opcode
Next by thread: Re: [Opps] Invalid opcode
Index(es):
- Date
- Thread

[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]

Powered by Linux