From: Robert Henney <robh@rut.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NULL pointer dereference in 2.6.32.12 on mount attempt
Date: Wed, 28 Apr 2010 18:40:47 -0400 [thread overview]
Message-ID: <20100428224047.GA8310@rut.org> (raw)
In-Reply-To: <1272493773.2864.73.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
On Wed, Apr 28, 2010 at 06:29:33PM -0400, Trond Myklebust wrote:
> I was thinking more about what the contents of your kernel syslog.
>
> IOW: if you do
>
> dmesg -s 900000 > /tmp/dmesg.txt
>
> what are the contents of the file /tmp/dmesg.txt?
attached. are compressed attachments allowed on this list?
[-- Attachment #2: dmesg.txt.bz2 --]
[-- Type: application/octet-stream, Size: 10388 bytes --]
prev parent reply other threads:[~2010-04-28 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 19:17 NULL pointer dereference in 2.6.32.12 on mount attempt Robert Henney
2010-04-28 20:24 ` Trond Myklebust
2010-04-28 22:23 ` Robert Henney
2010-04-28 22:29 ` Trond Myklebust
2010-04-28 22:40 ` Robert Henney [this message]
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=20100428224047.GA8310@rut.org \
--to=robh@rut.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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