From: Dave Jones <davej@redhat.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Jeff Layton <jlayton@samba.org>, Jesper Juhl <jj@chaosbits.net>,
linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org
Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS
Date: Mon, 15 Aug 2011 15:31:01 -0400 [thread overview]
Message-ID: <20110815193101.GA7295@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1108151357200.32349@p34.internal.lan>
On Mon, Aug 15, 2011 at 02:01:12PM -0400, Justin Piszcz wrote:
> It crashed again with the patches, this time I got a picture:
> http://home.comcast.net/~jpiszcz/20110815/26030-kernel-crash-when-cifs-mount.jpg
>
> The machine is up no issues until you try and mount a CIFS share, then
> the problem occurs, every time (and with the patches as well).
This looks like you oopsed in cache_alloc_refill, and then after that
the watchdog kicked in, and spewed traces, scrolling the backtrace for
the actual oops off the screen.
Might be worth trying to reproduce it with CONFIG_LOCKUP_DETECTOR disabled.
We frequently see this sort of thing reported in Fedora. It would be
nice if we had a means of either reading scrollback when we lockup,
or buffering the output so we pause between dumping traces.
Dave
next prev parent reply other threads:[~2011-08-15 19:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 9:10 Kernel 3.0: Instant kernel crash when mounting CIFS Justin Piszcz
2011-08-15 9:18 ` Jesper Juhl
2011-08-15 10:47 ` Jeff Layton
2011-08-15 10:54 ` Justin Piszcz
2011-08-15 18:01 ` Justin Piszcz
2011-08-15 18:09 ` Steve French
2011-08-15 19:31 ` Dave Jones [this message]
2011-08-17 19:16 ` Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Justin Piszcz
[not found] ` <alpine.DEB.2.02.1108171545190.5877@p34.internal.lan>
2011-08-17 19:47 ` Justin Piszcz
2011-08-17 20:13 ` Jeff Layton
2011-08-17 20:45 ` Justin Piszcz
2011-08-17 21:11 ` Arnaud Lacombe
2011-08-17 21:53 ` Justin Piszcz
2011-08-17 22:13 ` Justin Piszcz
2011-08-17 22:18 ` Justin Piszcz
2011-08-17 23:31 ` Valdis.Kletnieks
2011-08-18 3:19 ` J. R. Okajima
2011-08-18 10:35 ` Justin Piszcz
2011-08-18 12:14 ` Justin Piszcz
2011-08-18 12:22 ` Justin Piszcz
2011-08-18 13:11 ` Jeff Layton
2011-08-18 13:15 ` Justin Piszcz
2011-08-18 17:04 ` Jeff Layton
2011-08-18 17:15 ` Steve French
2011-08-18 17:16 ` Justin Piszcz
2011-08-18 17:25 ` Steve French
2011-08-18 17:33 ` Justin Piszcz
2011-08-18 17:43 ` Steve French
2011-08-18 18:18 ` Justin Piszcz
2011-08-18 18:52 ` Jeff Layton
2011-08-18 18:54 ` Justin Piszcz
2011-08-18 19:02 ` Steve French
2011-08-26 21:59 ` Jeff Layton
2011-08-26 22:57 ` Justin Piszcz
2011-08-26 23:05 ` Steve French
2011-08-26 23:16 ` Justin Piszcz
2011-08-27 14:31 ` Jeff Layton
2011-08-18 17:36 ` Kong Li
2011-08-18 18:33 ` Jeff Layton
2011-08-18 14:19 ` J. R. Okajima
2011-08-18 16:01 ` Steve French
2011-08-18 16:02 ` Steve French
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=20110815193101.GA7295@redhat.com \
--to=davej@redhat.com \
--cc=ap@solarrain.com \
--cc=jj@chaosbits.net \
--cc=jlayton@samba.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.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