linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 2.5.67 alpha compile failure
@ 2003-04-12 13:45 T. Weyergraf
  2003-04-12 19:42 ` Måns Rullgård
  0 siblings, 1 reply; 5+ messages in thread
From: T. Weyergraf @ 2003-04-12 13:45 UTC (permalink / raw)
  To: linux-kernel; +Cc: kirk

Hi all,

kernel 2.5.67 fails to compile on alpha ( DP264, SMP ):

[...]
  gcc -Wp,-MD,kernel/.sys.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev6 -Wa,-mev6 -fomit-frame-pointer -nostdinc -iwithprefix include    -DKBUILD_BASENAME=sys -DKBUILD_MODNAME=sys -c -o kernel/sys.o kernel/sys.c
kernel/sys.c:226: conflicting types for `sys_sendmsg'
include/linux/socket.h:245: previous declaration of `sys_sendmsg'
kernel/sys.c:227: conflicting types for `sys_recvmsg'
include/linux/socket.h:246: previous declaration of `sys_recvmsg'
make[1]: *** [kernel/sys.o] Error 1
make: *** [kernel] Error 2

in include/linux/socket.h, both sys_sendmsg and sys_recvmsg are declared as follows:

extern asmlinkage long sys_sendmsg(int fd, struct msghdr *msg, unsigned flags);
extern asmlinkage long sys_recvmsg(int fd, struct msghdr *msg, unsigned flags);

Obviously, commenting-out those declarations fixes the compile problem and the rest of the
build passes just fine.
This problem is new to me. 2.5.64 and 65 do not have it.

My question is: Is commenting-out the declarations the Correct Way (TM) ?
I don't think so ...

Any Ideas ?

Regards,
Thomas Weyergraf



Options set in .config are as follows:


CONFIG_ALPHA=y
CONFIG_MMU=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_EXPERIMENTAL=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=15
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_ALPHA_DP264=y
CONFIG_ISA=y
CONFIG_EISA=y
CONFIG_PCI=y
CONFIG_ALPHA_EV6=y
CONFIG_ALPHA_TSUNAMI=y
CONFIG_ALPHA_EV67=y
CONFIG_ALPHA_SRM=y
CONFIG_EARLY_PRINTK=y
CONFIG_SMP=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_NR_CPUS=2
CONFIG_VERBOSE_MCHECK=y
CONFIG_PCI_NAMES=y
CONFIG_KCORE_ELF=y
CONFIG_SRM_ENV=y
CONFIG_BINFMT_ELF=y
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_LOOP=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
CONFIG_BLK_DEV_DM=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=5000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_NCR53C8XX=m
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_INET_ECN=y
CONFIG_IPV6_SCTP__=y
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=y
CONFIG_TULIP_MMIO=y
CONFIG_INPUT=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_RTC=y
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_ISO9660_FS=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
CONFIG_OSF_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_15=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_ALPHA_LEGACY_START_ADDRESS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_MATHEMU=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_CRC32=y




-- 
Thomas Weyergraf                                                kirk@colinet.de
My Favorite IA64 Opcode-guess ( see arch/ia64/lib/memset.S )
"br.ret.spnt.few" - got back from getting beer, did not spend a lot.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.5.67 alpha compile failure
  2003-04-12 13:45 2.5.67 alpha compile failure T. Weyergraf
@ 2003-04-12 19:42 ` Måns Rullgård
  2003-04-13 22:50   ` 2.5.67 alpha compile failure (solved but nfsd Oopses now) Christian
  2003-04-14 11:37   ` nfs-kernel-server Oopses with 2.5.67 Christian
  0 siblings, 2 replies; 5+ messages in thread
From: Måns Rullgård @ 2003-04-12 19:42 UTC (permalink / raw)
  To: T. Weyergraf; +Cc: linux-kernel

"T. Weyergraf" <kirk@colinet.de> writes:

> kernel 2.5.67 fails to compile on alpha ( DP264, SMP ):
> 
> [...]
>   gcc -Wp,-MD,kernel/.sys.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev6 -Wa,-mev6 -fomit-frame-pointer -nostdinc -iwithprefix include    -DKBUILD_BASENAME=sys -DKBUILD_MODNAME=sys -c -o kernel/sys.o kernel/sys.c
> kernel/sys.c:226: conflicting types for `sys_sendmsg'
> include/linux/socket.h:245: previous declaration of `sys_sendmsg'
> kernel/sys.c:227: conflicting types for `sys_recvmsg'
> include/linux/socket.h:246: previous declaration of `sys_recvmsg'
> make[1]: *** [kernel/sys.o] Error 1
> make: *** [kernel] Error 2
> 
> Obviously, commenting-out those declarations fixes the compile problem and the rest of the
> build passes just fine.
> This problem is new to me. 2.5.64 and 65 do not have it.
> 
> My question is: Is commenting-out the declarations the Correct Way (TM) ?
> I don't think so ...

See my message with subject "[PATCH] Fix cond_syscall macro on Alpha".

-- 
Måns Rullgård
mru@users.sf.net

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.5.67 alpha compile failure (solved but nfsd Oopses now)
  2003-04-12 19:42 ` Måns Rullgård
@ 2003-04-13 22:50   ` Christian
  2003-04-14 11:37   ` nfs-kernel-server Oopses with 2.5.67 Christian
  1 sibling, 0 replies; 5+ messages in thread
From: Christian @ 2003-04-13 22:50 UTC (permalink / raw)
  To: linux-kernel

Måns Rullgård schrieb:
> See my message with subject "[PATCH] Fix cond_syscall macro on Alpha".

yes, indees. the patch applied (with an error when using patch
--verbose) and 2.5.67 compiled perfectly. i sa w the thread about this
thing on the redhat-AXP list, but i don't know anything about the deeper
interactions between kernel and glibc, sorry.
from a user's point of view i could say: "yes, let it go in 2.5.68" :-)


besides:
now i have a kernel oops when starting the kernel-nfs-server:

------------

lila:~# /etc/init.d/nfs-kernel-server start
Apr 14 00:31:08 lila kernel: Unable to handle kernel paging request at
virtual address 2834362d657a6973
Apr 14 00:31:08 lila kernel: rpc.nfsd(22279): Oops 0
Apr 14 00:31:08 lila kernel: pc = [<fffffc0000314748>]  ra =
[<fffffc0000312ec0>]  ps = 0007    Not tainted
Apr 14 00:31:08 lila kernel: v0 = 0000000000000000  t0 =
0000000000000000  t1 = fffffc0000314744
Apr 14 00:31:08 lila kernel: t2 = fffffc0000560848  t3 =
fffffc000055fba0  t4 = 0000000000000001
Apr 14 00:31:08 lila kernel: t5 = 2834362d657a6973  t6 =
000000000000001c  t7 = fffffc00031f8000
Apr 14 00:31:08 lila kernel: s0 = 0000000000000000  s1 =
fffffc000034e0d0  s2 = 0000000000000000
Apr 14 00:31:08 lila kernel: s3 = 000000011ffff3e4  s4 =
0000000000000000  s5 = fffffc0003840000
Apr 14 00:31:08 lila kernel: s6 = 0000000000000801
Apr 14 00:31:08 lila kernel: a0 = 2834362d657a6973  a1 =
0000000000000028  a2 = 0000000000000001
Apr 14 00:31:08 lila kernel: a3 = 0000000000000028  a4 =
0000000000000001  a5 = 0000000000000000
Apr 14 00:31:08 lila kernel: t8 = 0000000000000000  t9 =
fffffc0000540848  t10= fffffc0003ff31c8
Apr 14 00:31:08 lila kernel: t11= fffffc00005c3010  pv =
fffffc0000314300  at = fffffffc002e6b84
Apr 14 00:31:08 lila kernel: gp = fffffc0000560848  sp = fffffc00031fbcd8
Apr 14 00:31:08 lila kernel: Trace:fffffc0000312ec0 fffffc0000379408
fffffc000034e050 fffffc0000379b78 fffffc000034e0d4 fffffc0000397e3c
fffffc0000313134 fffffc0000313090
Apr 14 00:31:08 lila kernel: Code: 3c900001  3cb00000  47f60401
e43fff1d  c3ffff21  47ff0401 <2cb00000> 2cf00003

Starting NFS kernel daemon: nfsd/etc/init.d/nfs-kernel-server: line 79:
22279 Segmentation fault      start-stop-daemon --start --quiet --exec
$PREFIX/sbin/rpc.nfsd -- $RPCNFSDCOUNT
  mountd.
lila:~#

--------------
(could be that the order is a bit messed up, i copied the kernel oops
from /var/log/messages between "start" and "segfault".)


Thank you very much,
Christian.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* nfs-kernel-server Oopses with 2.5.67
  2003-04-12 19:42 ` Måns Rullgård
  2003-04-13 22:50   ` 2.5.67 alpha compile failure (solved but nfsd Oopses now) Christian
@ 2003-04-14 11:37   ` Christian
  2003-04-14 11:54     ` Måns Rullgård
  1 sibling, 1 reply; 5+ messages in thread
From: Christian @ 2003-04-14 11:37 UTC (permalink / raw)
  To: linux-kernel

coming from [Re: 2.5.67 alpha compile failure (solved but nfsd Oopses 
now)] i think the subject line has to change, as i get another problem now:

after applying the cond_syscall patch on my Alpha, 2.5.67 compiled with 
no errors. however the nfs-kernel-server Oopses now:

------------

lila:~# /etc/init.d/nfs-kernel-server start
Apr 14 00:31:08 lila kernel: Unable to handle kernel paging request at
virtual address 2834362d657a6973
Apr 14 00:31:08 lila kernel: rpc.nfsd(22279): Oops 0
Apr 14 00:31:08 lila kernel: pc = [<fffffc0000314748>]  ra =
[<fffffc0000312ec0>]  ps = 0007    Not tainted
Apr 14 00:31:08 lila kernel: v0 = 0000000000000000  t0 =
0000000000000000  t1 = fffffc0000314744
Apr 14 00:31:08 lila kernel: t2 = fffffc0000560848  t3 =
fffffc000055fba0  t4 = 0000000000000001
Apr 14 00:31:08 lila kernel: t5 = 2834362d657a6973  t6 =
000000000000001c  t7 = fffffc00031f8000
Apr 14 00:31:08 lila kernel: s0 = 0000000000000000  s1 =
fffffc000034e0d0  s2 = 0000000000000000
Apr 14 00:31:08 lila kernel: s3 = 000000011ffff3e4  s4 =
0000000000000000  s5 = fffffc0003840000
Apr 14 00:31:08 lila kernel: s6 = 0000000000000801
Apr 14 00:31:08 lila kernel: a0 = 2834362d657a6973  a1 =
0000000000000028  a2 = 0000000000000001
Apr 14 00:31:08 lila kernel: a3 = 0000000000000028  a4 =
0000000000000001  a5 = 0000000000000000
Apr 14 00:31:08 lila kernel: t8 = 0000000000000000  t9 =
fffffc0000540848  t10= fffffc0003ff31c8
Apr 14 00:31:08 lila kernel: t11= fffffc00005c3010  pv =
fffffc0000314300  at = fffffffc002e6b84
Apr 14 00:31:08 lila kernel: gp = fffffc0000560848  sp = fffffc00031fbcd8
Apr 14 00:31:08 lila kernel: Trace:fffffc0000312ec0 fffffc0000379408
fffffc000034e050 fffffc0000379b78 fffffc000034e0d4 fffffc0000397e3c
fffffc0000313134 fffffc0000313090
Apr 14 00:31:08 lila kernel: Code: 3c900001  3cb00000  47f60401
e43fff1d  c3ffff21  47ff0401 <2cb00000> 2cf00003

Starting NFS kernel daemon: nfsd/etc/init.d/nfs-kernel-server: line 79:
22279 Segmentation fault      start-stop-daemon --start --quiet --exec
$PREFIX/sbin/rpc.nfsd -- $RPCNFSDCOUNT
  mountd.
lila:~#

--------------
(could be that the order is a bit messed up, i copied the kernel oops
from /var/log/messages between "start" and "segfault".)

the nfs-kernel-server is from nfs-utils_1.0.3-1 (Debian testing), 
working without problems under 2.5.65. the nfs-user-server does *not* oops.

kernel 2.5.67, compiled with gcc (GCC) 3.2.3 20030309, machine is an 
Alpha EV45/Avtanti.

Thank you,
Christian.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: nfs-kernel-server Oopses with 2.5.67
  2003-04-14 11:37   ` nfs-kernel-server Oopses with 2.5.67 Christian
@ 2003-04-14 11:54     ` Måns Rullgård
  0 siblings, 0 replies; 5+ messages in thread
From: Måns Rullgård @ 2003-04-14 11:54 UTC (permalink / raw)
  To: linux-kernel

Christian <evil@g-house.de> writes:

> coming from [Re: 2.5.67 alpha compile failure (solved but nfsd Oopses
> now)] i think the subject line has to change, as i get another problem
> now:
> 
> 
> after applying the cond_syscall patch on my Alpha, 2.5.67 compiled
> with no errors. however the nfs-kernel-server Oopses now:

It happens for me too.  Here's the output of ksymoops.

ksymoops 2.4.5 on alpha 2.5.67.  Options used
     -v /mnt/linux/linux-sx164-2.5/vmlinux (specified)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.5.67/ (default)
     -m /mnt/linux/linux-sx164-2.5/System.map (specified)

Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
warning: process `update' used the obsolete bdflush system call
Unable to handle kernel paging request at virtual address 2834362d657a6973
rpc.nfsd(93): Oops 0
pc = [<fffffc0000314404>]  ra = [<fffffc0000312c30>]  ps = 0007    Not tainted
Using defaults from ksymoops -t elf64-alpha -a alpha
v0 = 0000000000000000  t0 = 0000000000000000  t1 = fffffc0000314400
t2 = fffffc0000559ec8  t3 = fffffc0000559720  t4 = 000000000000001c
t5 = fffffc002f0e0010  t6 = 000000011ffff44c  t7 = fffffc002f2d0000
s0 = 0000000000000000  s1 = fffffc000034e370  s2 = 0000000000000000
s3 = 000000011ffff444  s4 = 0000000000000000  s5 = fffffc002f0e0000
s6 = 000000011fff9410
a0 = 2834362d657a6973  a1 = 0000000000000028  a2 = 0000000000000003
a3 = 0000000000000028  a4 = 0000000000000003  a5 = 000000011ffffecb
t8 = 000000000000001f  t9 = fffffc0000539ec8  t10= 0000000000000008
t11= 00000200001c70a0  pv = fffffc0000313fd0  at = fffffffc002c0b74
gp = fffffc0000559ec8  sp = fffffc002f2d3cd8
Trace:fffffc0000312c30 fffffc000037999c fffffc000034e2f0 fffffc000037a0e0 fffffc000034e374 fffffc0000398410 fffffc0000312ea4 
Code: 44a70405  3cd00001  3cb00000  e49fff1f  c3ffff24  47ff0401 <2cb00000> 2cd00003 


>>RA;  fffffc0000312c30 <entUna+90/110>

>>PC;  fffffc0000314404 <do_entUna+434/580>   <=====

Trace; fffffc0000312c30 <entUna+90/110>
Trace; fffffc000037999c <do_lookup+4c/130>
Trace; fffffc000034e2f0 <kmalloc+0/d0>
Trace; fffffc000037a0e0 <link_path_walk+660/ac0>
Trace; fffffc000034e374 <kmalloc+84/d0>
Trace; fffffc0000398410 <sys_nfsservctl+110/1a0>
Trace; fffffc0000312ea4 <entSys+a4/c0>

Code;  fffffc00003143ec <do_entUna+41c/580>
0000000000000000 <_PC>:
Code;  fffffc00003143ec <do_entUna+41c/580>
   0:   05 04 a7 44       or   t4,t6,t4
Code;  fffffc00003143f0 <do_entUna+420/580>
   4:   01 00 d0 3c       stq_u        t5,1(a0)
Code;  fffffc00003143f4 <do_entUna+424/580>
   8:   00 00 b0 3c       stq_u        t4,0(a0)
Code;  fffffc00003143f8 <do_entUna+428/580>
   c:   1f ff 9f e4       beq  t3,fffffffffffffc8c <_PC+0xfffffffffffffc8c> fffffc0000314078 <do_entUna+a8/580>
Code;  fffffc00003143fc <do_entUna+42c/580>
  10:   24 ff ff c3       br   fffffffffffffca4 <_PC+0xfffffffffffffca4> fffffc0000314090 <do_entUna+c0/580>
Code;  fffffc0000314400 <do_entUna+430/580>
  14:   01 04 ff 47       clr  t0
Code;  fffffc0000314404 <do_entUna+434/580>   <=====
  18:   00 00 b0 2c       ldq_u        t4,0(a0)   <=====
Code;  fffffc0000314408 <do_entUna+438/580>
  1c:   03 00 d0 2c       ldq_u        t5,3(a0)


1 error issued.  Results may not be reliable.


-- 
Måns Rullgård
mru@users.sf.net

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2003-04-14 11:43 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-12 13:45 2.5.67 alpha compile failure T. Weyergraf
2003-04-12 19:42 ` Måns Rullgård
2003-04-13 22:50   ` 2.5.67 alpha compile failure (solved but nfsd Oopses now) Christian
2003-04-14 11:37   ` nfs-kernel-server Oopses with 2.5.67 Christian
2003-04-14 11:54     ` Måns Rullgård

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).