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

Re: Kernel 2.2.19: Unimplemented SPARC system call ???



On Fri, Jul 13, 2001 at 01:40:10AM +0200, Guenter Millahn wrote:
> Hello dear Debian SPARC friends,
> 
> I have some strange notices in dmesg log on 2 Woody Sun4M boxes (LX
> and SPARC 10 MP). Both have Kernel 2.2.19 (downloaded the kernel-images
> via apt-get from a package mirror).
> 
> I tried to make both systems very small (<200MB) and removed all unneeded
> packages. Have I probably deleted a little bit too much ???
> 
> Here is the last part of my dmesg output:
> 
> > VFS: Mounted root (ext2 filesystem) readonly.
> > Adding Swap: 130804k swap-space (priority -1)
> > eth0: Carrier Lost, trying TPE
> > portmap[72]: Unimplemented SPARC system call 87
> > cp[91]: Unimplemented SPARC system call 69
> > mv[108]: Unimplemented SPARC system call 69
> > inetd[128]: Unimplemented SPARC system call 53
> > atd[153]: Unimplemented SPARC system call 69
> > cron[156]: Unimplemented SPARC system call 108

All of these are meaningless. This is starting to be a FAQ :)

Basically, the new glibc is compiled with LFS support, but that is only
supported with 2.4.x kernels. So these attempted LFS syscalls fail on
2.2.x kernels. Good thing is, glibc is smart enough to fall back to
pre-LFS syscalls in this case.

I may disable this printf for the Debian distributed kernels. This
message is only meaningful for developers.

Ben

-- 
 -----------=======-=-======-=========-----------=====------------=-=------
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'



Reply to: