From: "Perry Gilfillan" <perrye@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: RETRACTION: 2.4.23 segfaults on cat /proc/modules
Date: Mon, 29 Dec 2003 11:30:53 +0600 [thread overview]
Message-ID: <20031229053053.30157.qmail@linuxmail.org> (raw)
RETRACTION: I just figured out what was going on. It was all a typo in grub.conf.
I had originaly called the kernel image bzImage-2.4.23.kdbg. I had a script that copied bzImage and System.map to /boot, applying -2.4.23.kdbg to them. The script disapeared along with the directory linux-2.4.23-kgdb when I cleaned it out before applying the new patches. When I recreated the script, I used -2.4.23.kgdb, while grub.conf still used kdbg.
I would have been clued in if depmod had shown errors in the boot log. The kernel I inadvertantly was using did have module loading enabled, but no modules were configured in the kernel since kgdb had not yet realeased the latest version. I had module loading enabled so I could work on the v3tv modules.
The i2c modules in the lsmod listing below are from the new i2c and lm_sensors patches. They loaded on the wrong kernel without missing symbols. I got a long list of missing symbols when I went back to freshen the kernel and finnaly got tipped off on what was wrong.
It's been educational, and I'm better prepared for my next challenge with the v3tv drivers.
It's all there at http://gilfillan.org:8000/Oopsen/ ( no I'm not afraid to admit my own mistakes )
Thanks for your attention,
Perry
--
______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
reply other threads:[~2003-12-29 5:30 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=20031229053053.30157.qmail@linuxmail.org \
--to=perrye@linuxmail.org \
--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