From: "Adam J. Richter" <adam@yggdrasil.com>
To: pavenis@latnet.lv
Cc: linux-kernel@vger.kernel.org
Subject: Re: devfs breakage in 2.4.0 release
Date: Sat, 6 Jan 2001 22:25:43 -0800 [thread overview]
Message-ID: <200101070625.WAA01585@adam.yggdrasil.com> (raw)
On my Sony PictureBook PCG-C1VN, 2.4.0 hangs in the boot
process while 2.4.0-prerelease boots just fine. At first I thought
the problem was devfs-related, but skipping devfsd just caused the
hang to occur a little later, this time in ifconfig. The kernel
call trace looked something like this:
neigh_ifdown
sys_ioctl
sock_ioctl
[some addresses in modules]
stext_lock
__down_failed
__down
What surprised me more was that attempting to remount the
root filesystem for writing just before this (to record the module
kernel symbols) caused a kenel BUG() in slab.c:1542 becuase kmalloc
was being called with a huge negative number.
I know I could run ksymoops to get this trace, but I now
think the cause of the problem probably happens much earlier than
the symptoms. So, I trying backing out different 2.4.0 changes.
So far, I can tell you that reverting the linux/mm subdirectory to
its 2.4.0-prerelease contents had no effect. I will let you know
if I diagnose or fix the problem, as I think you may be experiencing
the same problem.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-07 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 6:25 Adam J. Richter [this message]
2001-01-08 7:47 ` Andris Pavenis
-- strict thread matches above, loose matches on Subject: below --
2001-01-06 13:28 Andris Pavenis
2001-01-12 11:35 ` Andris Pavenis
2001-01-23 8:25 ` Andris Pavenis
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=200101070625.WAA01585@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavenis@latnet.lv \
/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
all inboxes | Powered by JetHome®