From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: /sbin/depmod Segmentation fault (Reproducable)
Date: Wed, 3 Jan 2007 21:53:04 +0200 [thread overview]
Message-ID: <20070103195238.GA3577@Ahmed> (raw)
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
Hi all,
* After compiling 2.6.20-rc3 and typing "make modules_install" I get:
INSTALL **
..
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map \
2.6.20-rc3-1; fi
/bin/sh: line 1: 10727 Segmentation fault /sbin/depmod -ae -F System.map \
2.6.20-rc3-1
make: *** [_modinst_post] Error 139
* I found sbin/depmod tries to open a non-existent file before being killed:
$ strace /sbin/depmod -ae -F System.map 2.6.20-rc3-1
... (Opening
readlink("/lib/modules/2.6.20-rc3-1/source", "/", 1) = 1
readlink("/lib/modules/2.6.20-rc3-1/build", "/", 1) = 1
getdents64(4, /* 0 entries */, 4096) = 0
close(4) = 0
open("/lib/modules/2.6.20-rc3-1/updates", O_RDONLY|O_NONBLOCK|O_LARGEFILE|\
O_DIRECTORY) = -1 ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
I've compiled 2.6.20-rc3 several times before (I'm on a 20-rc3 now actually).
It's the first time to see this problem (maybe cause I changed the .conf file ?).
.conf file that caused the problem is gzipped and attached. Thanks ..
System tools versions:
Linux darwish-laptop 2.6.20-rc3-1 #16 Wed Jan 3 07:17:36 EET 2007 i686 GNU/Linux
Gnu C 4.0.3
Gnu make 3.81beta4
binutils 2.16.91
util-linux 2.12r
mount 2.12r
module-init-tools 3.2.2
e2fsprogs 1.38
jfsutils 1.1.8
reiserfsprogs 3.6.19
reiser4progs 1.0.5
xfsprogs 2.7.7
pcmciautils 012
pcmcia-cs 3.2.8
PPP 2.4.4b1
Linux C Library 2.3.6
Dynamic linker (ldd) 2.3.6
Procps 3.2.6
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.93
udev 079
wireless-tools 28
--
Ahmed S. Darwish
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 15641 bytes --]
reply other threads:[~2007-01-03 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070103195238.GA3577@Ahmed \
--to=darwish.07@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).