kernel: invalid operand: 0000 on RHEL4 x86-64

[Andrew Cunningham]

Hi,
	I am creating 32-bit application on RHEL4 x86_64. Simple 32-bit  
hello worlds work fine. However, when running a slightly more  
complicated example which depends on a 32-bit .so, I get the  
following system error when I run the application under gdb ( or by  
itself outside of gdb)

This must be a pretty common issue, but I am a bit baffled.

Message from syslogd at PERTH at Tue Apr 10 17:45:36 2007 ...
PERTH kernel: invalid operand: 0000 [2] SMP

'file' shows this
ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/ 
Linux 2.2.5, dynamically linked (uses shared libs), not stripped



Apr 10 17:39:01 PERTH kernel: Kernel BUG at memory:816
Apr 10 17:39:01 PERTH kernel: invalid operand: 0000 [1] SMP
Apr 10 17:39:01 PERTH kernel: CPU 1
Apr 10 17:39:01 PERTH kernel: Modules linked in: nls_utf8 nfsd  
exportfs lockd parport_pc lp parport autofs4 sunrpc ds yenta_socket  
pcmcia_core dm_mirror dm_mod button battery ac md5 ipv6 joydev  
uhci_hcd ehci_hcd nvidia(U) i2c_core hw_random snd_hda_intel(U)  
snd_hda_codec(U) snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd(U)  
soundcore snd_page_alloc tg3(U) floppy ext3 jbd(U) ata_piix(U) ahci 
(U) libata(U) sd_mod scsi_mod
Apr 10 17:39:01 PERTH kernel: Pid: 20948, comm: gdb Tainted: P       
2.6.9-5.ELsmp
Apr 10 17:39:01 PERTH kernel: RIP: 0010:[<ffffffff80163165>]  
<ffffffff80163165>{get_user_pages+354}
Apr 10 17:39:01 PERTH kernel: RSP: 0018:0000010081e87e68  EFLAGS:  
00010246
Apr 10 17:39:01 PERTH kernel: RAX: 0000000000000000 RBX:  
0000000000000ff0 RCX: 000ffffffffff000
Apr 10 17:39:01 PERTH kernel: RDX: 0000010000000000 RSI:  
0000010085d43ff0 RDI: ffffffff803c15e0
Apr 10 17:39:01 PERTH kernel: RBP: 0000000000000000 R08:  
0000010085d43ff0 R09: 000000000012ad72
Apr 10 17:39:01 PERTH kernel: R10: 0000000000000000 R11:  
0000000000000000 R12: 0000000000000000
Apr 10 17:39:01 PERTH kernel: R13: 00000101197c56c0 R14:  
0000000000000010 R15: 0000010085f537f0
Apr 10 17:39:01 PERTH kernel: FS:  0000002a9557dde0(0000)  
GS:ffffffff804bf380(0000) knlGS:0000000000000000
Apr 10 17:39:01 PERTH kernel: CS:  0010 DS: 0000 ES: 0000 CR0:  
000000008005003b
Apr 10 17:39:01 PERTH kernel: CR2: 00000000007add98 CR3:  
0000000037e48000 CR4: 00000000000006e0
Apr 10 17:39:01 PERTH kernel: Process gdb (pid: 20948, threadinfo  
0000010081e86000, task 00000100899ed030)
Apr 10 17:39:01 PERTH kernel: Stack: 0000000000000001  
00000000ffffe000 00000001197c571c 00000101197c5718
Apr 10 17:39:01 PERTH kernel:        0000000000000001  
0000010081e87f48 0000010085f537f0 0000000000000008
Apr 10 17:39:01 PERTH kernel:        00000101197c56c0 ffffffff8013c93c
Apr 10 17:39:01 PERTH kernel: Call Trace:<ffffffff8013c93c> 
{access_process_vm+145} <ffffffff801138de>{sys_ptrace+337}
Apr 10 17:39:01 PERTH kernel:        <ffffffff8010ffd2>{system_call+126}
Apr 10 17:39:01 PERTH kernel:
Apr 10 17:39:01 PERTH kernel: Code: 0f 0b ae c1 32 80 ff ff ff ff 30  
03 48 83 7c 24 50 00 74 58
Apr 10 17:39:01 PERTH kernel: RIP <ffffffff80163165>{get_user_pages 
+354} RSP <0000010081e87e68>
Apr 10 17:43:52 PERTH kernel:  <6>timedate[21021]: segfault at  
0000000000000058 rip 00000000f7e25f82 rsp 00000000ffffcfd8 error 4



Andrew