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

Re: Debug Output?



>>>>> On Wed, 27 Aug 2003 09:59:51 -0700, Richard Harke <rharke@earthlink.net> said:

  Richard> My machine has developed an annoying feature. Various commands
  Richard> spit out additional messages that I don't understand. I suspect these
  Richard> must be debug statements. A example:

  Richard> ls -l g++*
  Richard> ls(1223): <sc1220(60000fffffffbeea,200000000007b5f8,0,0)>
  Richard> ls(1223): <sc1220(60000fffffffbef3,200000000007b5f8,0,0)>

  Richard> The first number after the ls appears to be the process id. This has also
  Richard> happened with cp and possibly other cammands. This may be related
  Richard> to something that happens at boot time. This happened the other day,
  Richard> then after re-boot didn't occur. I just re-booted this morning and
  Richard> it started again.

  Richard> Does anyone know what it means?

$ fgrep 1220 include/asm-ia64/unistd.h
#define __NR_getxattr                   1220

Apparently, your libc is making getxattr() system calls, but the
kernel doesn't understand them.  The kernel reacts by printing the
"sc1220" message and returning ENOSYS.  The messages are harmless
(apart from being annoying, I suppose).

	--david



Reply to: