From: David Chinner <dgc@sgi.com>
To: Don Dupuis <dondster@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops at __bio_clone with 2.6.16-rc6 anyone??????
Date: Tue, 28 Mar 2006 15:19:31 +1100 [thread overview]
Message-ID: <20060328041931.GI27189130@melbourne.sgi.com> (raw)
In-Reply-To: <632b79000603271917h4104049dh9b6b8251feac0437@mail.gmail.com>
On Mon, Mar 27, 2006 at 09:17:03PM -0600, Don Dupuis wrote:
> I will get this oops during reboots. It doesn't happen everytime, but
> It happens on this system at least 1 to 2 out of 10 reboots. The
> machine is a Dell Powervault 745n. Here is the oops output:
Hmmm - I wonder if this is related to to this one:
http://marc.theaimsgroup.com/?l=linux-kernel&m=114342655931507&w=2
which is an oops in the write path when dmcrypt is cloning a bio
from XFS.
Cheers,
Dave.
--
Dave Chinner
R&D Software Enginner
SGI Australian Software Group
prev parent reply other threads:[~2006-03-28 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 3:17 Oops at __bio_clone with 2.6.16-rc6 anyone?????? Don Dupuis
2006-03-28 4:01 ` Andrew Morton
2006-03-28 15:35 ` Don Dupuis
2006-03-28 19:31 ` Andrew Morton
2006-04-07 15:23 ` Don Dupuis
2006-04-07 18:29 ` Don Dupuis
2006-04-07 21:54 ` Andrew Morton
2006-03-28 4:19 ` David Chinner [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=20060328041931.GI27189130@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=dondster@gmail.com \
--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.