From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Camm Maguire <camm@enhanced.com>
Cc: linux-kernel@vger.kernel.org, nfs-devel@linux.kernel.org
Subject: Re: PROBLEM: 2.2.18 oops leaves umount hung in disk sleep
Date: 22 Mar 2001 23:09:13 +0100 [thread overview]
Message-ID: <shspuf98nhy.fsf@charged.uio.no> (raw)
In-Reply-To: <E14g8eP-0006k5-00@intech19.enhanced.com> <shs1yrpabky.fsf@charged.uio.no> <54hf0l8ug1.fsf@intech19.enhanced.com>
In-Reply-To: Camm Maguire's message of "22 Mar 2001 14:39:10 -0500"
>>>>> " " == Camm Maguire <camm@enhanced.com> writes:
> I'd be happy to generate one if I could. I've got the system
> map. The defaults reported by ksymoops are all correct. Don't
> know why it didn't give me more info. Normally, the info is
> reported by klogd anyway, but not here. I've sent you all I
> currently have. If you can suggest how I can get more, would
> be glad to do so.
Unless you happen to have a dump from 'dmesg', there's probably not
much you can do to recover the rest of the Oops...
We need at least the line 'EIP:' if we're to find out where the fault
occurred. Are you certain that it can't be found in the syslog?
> I thought I was running v3. Can't seem to find anything now
> which indicates the protocol version in use, but was under the
> impression that v4 was only an option in 2.4.x, no?
Mar 21 01:14:49 intech9 automount[305]: using kernel protocol version 3 on reawaken
Sorry, the above message fooled me.
Cheers,
Trond
next prev parent reply other threads:[~2001-03-22 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 17:13 PROBLEM: 2.2.18 oops leaves umount hung in disk sleep Camm Maguire
2001-03-22 17:44 ` 4GB -> no boot Giuliano Pochini
2001-03-22 18:43 ` PROBLEM: 2.2.18 oops leaves umount hung in disk sleep Trond Myklebust
2001-03-22 19:39 ` Camm Maguire
2001-03-22 22:09 ` Trond Myklebust [this message]
2001-03-23 1:43 ` Camm Maguire
[not found] ` <shs7l1gae5a.fsf@charged.uio.no>
2001-03-27 15:15 ` Camm Maguire
2001-03-28 23:19 ` Camm Maguire
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=shspuf98nhy.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=camm@enhanced.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs-devel@linux.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