This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue May 28 22:08:34 2024 Received: from entropy.muc.muohio.edu (entropy.muc.muohio.edu [134.53.213.10]) by herbie.ucs.indiana.edu (8.8.8/8.8.8) with ESMTP id TAA24226 for ; Sat, 6 Feb 1999 19:29:59 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by entropy.muc.muohio.edu (Postfix) with ESMTP id 7132822295; Sat, 06 Feb 1999 19:19:38 -0500 (EST) Received: by vger.rutgers.edu via listexpand id <154915-27300>; Sat, 6 Feb 1999 19:10:12 -0500 Received: by vger.rutgers.edu id <154191-27300>; Sat, 6 Feb 1999 19:10:05 -0500 Received: from shawc.demon.co.uk ([158.152.146.90]:1034 "EHLO shawc.demon.co.uk" ident: "root") by vger.rutgers.edu with ESMTP id <154962-27302>; Sat, 6 Feb 1999 19:09:34 -0500 Received: from localhost (shaw@localhost) by shawc.demon.co.uk (8.7/8.7) with ESMTP id AAA00540 for ; Sun, 7 Feb 1999 00:26:00 GMT Date: Sun, 7 Feb 1999 00:26:00 +0000 (GMT) From: Shaw Carruthers To: Linux Kernel List Subject: Wierd getcwd problem with 2.2.1-ac5 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig Linux shawc 2.2.1-ac5 #1 Fri Feb 5 23:04:03 GMT 1999 i586 unknown I am getting the following wierd problem( trying to run make check on a glibc2 build): make -C assert tests make: getcwd: : I/O error make[2]: Entering an unknown directory make[2]: getcwd: : I/O error make[2]: Nothing to be done for ests'. make[2]: Leaving an unknown directory Simultaneously I see in my logs: Feb 7 00:00:13 shawc kernel: smb_retry: signal failed, error=-3 Feb 7 00:00:26 shawc last message repeated 13 times This repeats for each test in turn. Wires crossed? All the files involved in the make are on a local fs. Here is what I have mounted, but the smbfs is inactive during this time. /dev/hda4 on / type ext2 (rw) /dev/sda6 on /usr type ext2 (rw) /dev/sda3 on /usr/local type ext2 (rw) /dev/sda5 on /source type ext2 (rw) /dev/hda1 on /DOS type vfat (rw,codepage=850,umask=000,quiet) /dev/hda5 on /DOSE type vfat (rw,codepage=850,umask=000,quiet) /dev/sda1 on /DOSD type vfat (rw,codepage=850,umask=000,quiet) none on /proc type proc (rw) //GILLIAN.LEINSTER/GILLC on /GILLC type smbfs (0) //GILLIAN.LEINSTER/GILLD on /GILLD type smbfs (0) /dev/hdb on /CDROM type iso9660 (ro,nosuid,nodev) I have seen this with 2.2.0+ , rebooting cures the problem. Building glibc2 uses lots of files, so maybe some dentry/inode problem? Or maybe a glibc2/egcs problem? Kernel itself is built with good old gcc: Reading specs from /usr/lib/gcc-lib/i586-unknown-linux-gnulibc1/2.7.2.3/specs gcc version 2.7.2.3 -- Shaw Carruthers - shaw@shawc.demon.co.uk London SW14 7JW UK This is not a sig( with homage to Magritte). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/