Re: [Opps] Invalid opcode

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

To: Andi Kleen <[email protected]>
Subject: Re: [Opps] Invalid opcode
From: "S.Çağlar Onur" <[email protected]>
Date: Sun, 12 Nov 2006 04:39:50 +0200
Cc: [email protected], Zachary Amsden <[email protected]>, Gerd Hoffmann <[email protected]>, john stultz <[email protected]>
In-reply-to: <[email protected]>
Organization: TÜBİTAK / UEKAE
References: <[email protected]> <[email protected]>
Reply-to: [email protected]
Sender: [email protected]
User-agent: KMail/1.9.5

05 Kas 2006 Paz 18:40 tarihinde, Andi Kleen şunları yazmıştı: 
> And does it still happen in 2.6.19-rc4?

Sorry for delayed test result, i cannot reproduce this panic with 2.6.19-rc5

-- 
S.Çağlar Onur <[email protected]>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

Attachment: pgpf4v3dBNzMj.pgp
Description: PGP signature

Follow-Ups:
- Re: [Opps] Invalid opcode
  - From: Zachary Amsden <[email protected]>
- Re: [Opps] Invalid opcode
  - From: Andi Kleen <[email protected]>

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

Prev by Date: spin_trylock/spin_unlock panic in 2.6.9-42.0.3.EL
Next by Date: Re: [patch/rfc 2.6.19-rc5] arch-neutral GPIO calls
Previous by thread: Re: Fix for OpenSUSE kernel bug (was 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