From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.39: crash w/threadirqs option enabled
Date: Thu, 26 May 2011 12:30:14 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1105261228570.8379@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1105201210030.19553@p34.internal.lan>
On Fri, 20 May 2011, Justin Piszcz wrote:
>
>
> On Fri, 20 May 2011, Thomas Gleixner wrote:
>
>> On Fri, 20 May 2011, Justin Piszcz wrote:
>>> On Fri, 20 May 2011, Thomas Gleixner wrote:
>>>> Does it crash right away or just when doing something particular?
>>> It crashed at 2100, this is when I run a few I/O intensive processes:
>>> - backup (dump ext4 filesystem -> to a separate raid device)
>>> - backup (dump ext4 on remote host -> to separate raid device)
>>> - backup (dump xfs on remote host -> to separate raid device)
>>>
>>> This looks like it is what caused it to crash.
>>
>> That narrows it down somewhat, but does not give us a clue at all :(
>>
>>>> Is the box fully dead after the crash ?
>>> The host was online and I went away for awhile, when I came back the
>>> system
>>> had rebooted on its own (as I lost all of my X windows/etc).
>>
>> Hmm. Did you have panic_timeout set ?
>
> Hi,
>
> No, I do not use panic_timeout or any type of watchdog that would reboot
> the system upon a lockup/crash.
>
> Justin.
>
>
Hi,
I like to be as accurate as possible, since this occurred, I've removed
threadirqs..
Please disregard this, I also updated the BIOS on the same day (BIOS
update + kernel update), I'm re-running w/thread irqs enabled again, and
I'll update you if there are any issues, thanks.
(I've set the bios to factory defaults -> tweaked), we'll see what
happens.
Justin.
prev parent reply other threads:[~2011-05-26 16:30 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
2012-09-16 20:34 ` Low os-jitter operating system Uwaysi Bin Kareem
2011-05-26 16:30 ` Justin Piszcz [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=alpine.DEB.2.02.1105261228570.8379@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.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®