From: Tejun Heo <htejun@gmail.com>
To: Florian Effenberger <florian@effenberger.org>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: Serious bug in sata_sil module in 2.6.19.2?
Date: Tue, 06 Feb 2007 15:30:09 +0900 [thread overview]
Message-ID: <45C82071.5080808@gmail.com> (raw)
In-Reply-To: <45C27A4D.8070802@effenberger.org>
Florian Effenberger wrote:
> Hi there,
>
>> sata_sil hasn't seen as much change as other drivers and is one of
>> the more stable ones. I'm definitely interested. Please post the
>> pics. If the video contains useful info, can you host it somewhere?
>
> I've uploaded the image at
>
> http://img482.imageshack.us/img482/6677/img0149rh5.jpg
>
> and the video at
>
> http://video.google.de/videoplay?docid=-3785898339758585695
>
> Can anyone detect something on the images?
>
> (If you reply, please put me in Cc, I am not subscribed to the list.
> Thanks!)
That definitely looks like libata error messages but can't tell anything
other than that from it. It could be cause of system hang and the weird
screen or just another symptom of another problem.
Is it possible for you to connect a serial console or configure
netconsole (Documentation/networking/netconsole.txt) such that the
messages are preserved after such hang occurs? Also, please turn on
PRINTK_TIME (Kernel Hacking -> Show timing information on printks) so
that we can tell what happens when. To make the info more useful, you
can log into the machine from another machine and run something like
"while true; do sleep 1; date; done" on it such that you can tel exactly
when the machine went down.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-02-06 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 10:24 Serious bug in sata_sil module in 2.6.19.2? Florian Effenberger
2007-02-01 14:41 ` Tejun Heo
2007-02-01 23:39 ` Florian Effenberger
2007-02-06 6:30 ` Tejun Heo [this message]
2007-02-06 10:45 ` Florian Effenberger
2007-02-06 14:44 ` Tejun Heo
2007-02-06 16:14 ` Florian Effenberger
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=45C82071.5080808@gmail.com \
--to=htejun@gmail.com \
--cc=florian@effenberger.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).