From: evil <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: lockups with 2.4.2x
Date: Sun, 21 Sep 2003 04:56:14 +0200 [thread overview]
Message-ID: <3F6D134E.2080505@g-house.de> (raw)
Hi y'all,
i am in the need of some help tracing down mysterious lock-ups of my
machine. with any vanilla kernel above 2.4.19 the machine boots, the it
will take 1 to 3 minutes and the machine freezes. no Oops on the
console, no warnings (e.g. no high load or mem-pressure), even SysReq is
not working.
i've already setup a script, writing
/proc/modules|locks|ksyms
to the disk every 2 seconds, because i suspected some 3rd party module i
usually load to be the reason for the freezes. but it was not. please
tell me, if other files are more interesting for this or what else i can
do to get to the source to the problem.
the machine:
Dual Athlon, 1GB RAM (HighMem enabled), gcc 3.3.1, libc 2.3.2,
(Debian/Testing) some more infos are on:
http://nerdbynature.de/bits/freeze/config|cpuinfo|dmesg|lspci
(directory listing follows...)
I really appreciate some help here, i don't know where to start
searching since no errors are shown :-(
below are some further infos, but i don't know if they are related to
this issue.
Thank you for your time,
Christian.
before this whole mess i was using 2.4.19, but i wanted to upgrade to
2.4.20, 2.4.21, did not make it, due to lack of time or need. 2.4.19 was
running fine. but i need netfilter now, so i had to recompile
modules+kernel! but, mysteriously, i fail to recompile my 2.4.19. i did
"make mrproper", then even untar'ed a new archive, took the old config,
"make oldconfig" went ok. then
"make dep bzImage modules modules_install" stops within "bzImage":
net/network.o(.text+0xf125): In function `rtnetlink_rcv':
: undefined reference to `rtnetlink_rcv_skb'
make: *** [vmlinux] Error 1
there was another issue with a vanilla 2.4.19, but i tried to fix it:
http://nerdbynature.de/bits/freeze/semaphore.c.patch
hm, is this gcc related? it did not like some missing "" terminations.
ok, after fixing this, the error above showed up.
so, i thought it was time to try 2.4.2x (now 2.4.22), but am somehow
stuck now. on some completely other machines (PPC32 + single
AMD/Athlon), 2.4.2x are running very fine.
next reply other threads:[~2003-09-21 2:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 2:56 evil [this message]
2003-09-21 5:37 ` lockups with 2.4.2x Christian
2003-09-21 5:38 ` Willy Tarreau
2003-09-21 13:26 ` Christian
2003-09-21 21:49 ` Christian
2003-09-23 0:23 ` Christian Kujau
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=3F6D134E.2080505@g-house.de \
--to=evil@g-house.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.