From: berk walker <berk@panix.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Tejun Heo <tj@kernel.org>,
"Mr. James W. Laferriere" <babydr@baby-dragons.com>,
Tom Mortensen <tmmlkml@gmail.com>,
Bill Davidsen <davidsen@tmr.com>,
Gwendal Grignou <gwendal@google.com>,
Brian Rademacher <rad@radfiles.net>,
linux-ide@vger.kernel.org,
linux-raid maillist <linux-raid@vger.kernel.org>,
Linux Kernel Maillist <linux-kernel@vger.kernel.org>,
Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen
Date: Sat, 04 Oct 2008 20:29:28 -0400 [thread overview]
Message-ID: <48E80A68.2000108@panix.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0810042022540.25643@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Sat, 4 Oct 2008, Justin Piszcz wrote:
>
>>
>>
>> On Sat, 4 Oct 2008, Tejun Heo wrote:
>>
>>> Justin Piszcz wrote:
>>>
>>> You're leaving the good part out. Please always attach full kernel
>>> log.
>>>
>>> Thanks.
>
> Are there any specific / useful / debugging options one could turn
> on/enable to obtain more information during these events that would
> produce meaningful/useful output?
>
> Justin.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I think that the log stated a lot.
b-
WARNING: multiple messages have this Message-ID (diff)
From: berk walker <berk@panix.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Tejun Heo <tj@kernel.org>,
"Mr. James W. Laferriere" <babydr@baby-dragons.com>,
Tom Mortensen <tmmlkml@gmail.com>,
Bill Davidsen <davidsen@tmr.com>,
Gwendal Grignou <gwendal@google.com>,
Brian Rademacher <rad@radfiles.net>,
linux-ide@vger.kernel.org,
linux-raid maillist <linux-raid@vger.kernel.org>,
Linux Kernel Maillist <linux-kernel@vger.kernel.org>,
Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen
Date: Sat, 04 Oct 2008 20:29:28 -0400 [thread overview]
Message-ID: <48E80A68.2000108@panix.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0810042022540.25643@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Sat, 4 Oct 2008, Justin Piszcz wrote:
>
>>
>>
>> On Sat, 4 Oct 2008, Tejun Heo wrote:
>>
>>> Justin Piszcz wrote:
>>>
>>> You're leaving the good part out. Please always attach full kernel
>>> log.
>>>
>>> Thanks.
>
> Are there any specific / useful / debugging options one could turn
> on/enable to obtain more information during these events that would
> produce meaningful/useful output?
>
> Justin.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I think that the log stated a lot.
b-
next prev parent reply other threads:[~2008-10-05 0:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E6D0C24877245C3A5A327129A7B4CA7@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220404400.18908@p34.internal.lan>
[not found] ` <5A4A9A3B0AAA4A20A33BC2D578F5F75F@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220828490.23159@p34.internal.lan>
[not found] ` <5419A02543384E69AF2BA82FF6E66C14@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220903400.23159@p34.internal.lan>
[not found] ` <4B1ABD0393EF40FFB0A12242FE8356AF@909927SOSLA>
2008-09-22 13:19 ` exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen Justin Piszcz
2008-09-22 13:26 ` Justin Piszcz
2008-09-22 13:26 ` Justin Piszcz
2008-09-23 18:14 ` Gwendal Grignou
2008-09-23 20:59 ` Brian Rademacher
2008-09-23 20:59 ` Brian Rademacher
2008-09-25 15:17 ` Bill Davidsen
2008-09-29 8:13 ` Tejun Heo
2008-09-30 20:47 ` Tom Mortensen
2008-09-30 21:18 ` Justin Piszcz
2008-10-01 3:50 ` Mr. James W. Laferriere
2008-10-01 8:06 ` Justin Piszcz
2008-10-01 11:12 ` Justin Piszcz
2008-10-04 2:27 ` Tejun Heo
2008-10-04 8:11 ` Justin Piszcz
2008-10-05 0:23 ` Justin Piszcz
2008-10-05 0:29 ` berk walker [this message]
2008-10-05 0:29 ` berk walker
2008-10-10 19:13 ` Justin Piszcz
2008-10-10 19:27 ` Alan Cox
2008-10-01 15:09 ` Bill Davidsen
2008-09-30 22:04 Christian
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=48E80A68.2000108@panix.com \
--to=berk@panix.com \
--cc=babydr@baby-dragons.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=davidsen@tmr.com \
--cc=gwendal@google.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rad@radfiles.net \
--cc=tj@kernel.org \
--cc=tmmlkml@gmail.com \
/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.