Summary: | open() returns ETIME | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin von Gagern <Martin.vGagern> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin von Gagern
2008-02-20 08:57:08 UTC
and if you go into the build dir and run `make` and/or `ar` by hand ? (In reply to comment #1) > and if you go into the build dir and run `make` and/or `ar` by hand ? Same thing when I run make or ar manually. strace tells me: open("../objects/language.o", O_RDONLY|O_LARGEFILE) = -1 ETIME (Timer expired) # ls -l ../objects/language.o -rw-r--r-- 1 root root 3098196 Feb 21 10:52 ../objects/language.o # wc -c ../objects/language.o wc: ../objects/language.o: Timer expired # stat ../objects/language.o File: `../objects/language.o' Size: 3098196 Blocks: 6064 IO Block: 4096 regular file Device: fe04h/65028d Inode: 148517 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2008-02-21 10:50:06.000000000 +0100 Modify: 2008-02-21 10:52:07.000000000 +0100 Change: 2008-02-21 10:52:07.000000000 +0100 Even switching PORTAGE_TMPDIR to another ext3 file system didn't help. I've never seen anything like this error before, but I get the feeling it might be a kernel thing. I couldn't find any documentation as to under what conditions open might return ETIME. not a toolchain issue then ... that's the kernel pooping out on you Do you have any older kernels already built? For example, could you reboot into 2.6.23 and see if the bug also appears there, or something like that? (In reply to comment #4) > Do you have any older kernels already built? For example, could you reboot into > 2.6.23 and see if the bug also appears there, or something like that? 2.6.24-gentoo-r2 seems to work, at least I just got a successful compile of doxygen. Strange thing. Does rebooting back to 2.6.24-gentoo make the problem reappear? (In reply to comment #6) > Does rebooting back to 2.6.24-gentoo make the problem reappear? No, it still emerges all right. It might well be that the reboot by itself solved the issue, not the change of kernel version. I hadn't rebooted between reproducing this issue before. Odd. Please reopen if it happens again |