From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Alan Piszcz <ap@solarrain.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: 2.6.39: crash w/threadirqs option enabled
Date: Sun, 12 Jun 2011 08:04:43 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1106120759270.4186@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1106100854250.23139@p34.internal.lan>
On Fri, 10 Jun 2011, Justin Piszcz wrote:
>
>
Hi,
It crashed again with the patch, so it must be something else when it
happened, I was not able to get any output since i was in X.
Will leave X off, console/monitor on and disconnect those USB devices
I mentioned earlier and see if the problem persists.
The call trace in the picture the last time I was able to get a screen
shot was @ blk_peek_request and scsi_request_fn.
http://home.comcast.net/~jpiszcz/20110528/2639-ss1.jpg
I will disconnect the USB devices I mentioned earlier and see if the issues
persist.
Justin.
next prev parent reply other threads:[~2011-06-12 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 8:39 Justin Piszcz
2011-05-20 12:48 ` Thomas Gleixner
2011-05-20 12:51 ` Justin Piszcz
2011-05-20 13:30 ` Thomas Gleixner
2011-05-20 13:49 ` Justin Piszcz
2011-05-20 15:17 ` Thomas Gleixner
2011-05-20 16:10 ` Justin Piszcz
2011-05-20 16:22 ` Thomas Gleixner
2011-05-21 0:00 ` Uwaysi Bin Kareem
2011-06-10 8:17 ` Justin Piszcz
2011-06-10 8:24 ` Justin Piszcz
2011-06-10 12:52 ` Thomas Gleixner
2011-06-10 13:07 ` Justin Piszcz
2011-06-10 13:10 ` Thomas Gleixner
2011-06-12 12:04 ` Justin Piszcz [this message]
2012-09-16 20:34 ` Low os-jitter operating system Uwaysi Bin Kareem
2011-05-26 16:30 ` 2.6.39: crash w/threadirqs option enabled Justin Piszcz
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=alpine.DEB.2.02.1106120759270.4186@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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®