Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Gabor FUNK" <FUNK.Gabor@hunetkft.hu>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: JMicron - hard resetting link
Date: Tue, 12 Feb 2008 18:27:44 +0100	[thread overview]
Message-ID: <002f01c86d9c$94542f50$4d0fa8c0@M2007> (raw)
In-Reply-To: 47B1B299.3010208@gmail.com

> What I said was that timeouts occurring due to transmission errors
> should be recoverable.  It seems like IRQ delivery didn't work probably
> due to screaming IRQ.  I need to see the messages before the first
> relevant error message.  It's always a good idea to post full kernel log
> from boot till failure.  Things which don't seem relevant are often
> relevant.
Naturally. Full kern.log with boot:
http://www.huweb.hu/maques/tmp/jmicron/kern.log
(no edits, there are really only those 2 lines between Feb 6 and Feb 9's 1st 
exception)

Previously there was kernel 2.6.23.9 and I noticed the following in syslog 
by then:
Feb  6 19:10:19 storage1 kernel: ata4: D2H reg with I during NCQ, this 
message won't be printed again
Feb  6 19:10:20 storage1 kernel: ata1: D2H reg with I during NCQ, this 
message won't be printed again
Feb  6 19:10:20 storage1 kernel: ata2: D2H reg with I during NCQ, this 
message won't be printed again
Feb  6 19:10:21 storage1 kernel: ata3: D2H reg with I during NCQ, this 
message won't be printed again

I googled and saw that there was some fixes related to this (maybe it
was you), so that's why we hoped that 2.6.24 will fix this. Actually the
above error messages were gone, but...

> Till now, none of this kind of problem has been tracked down to MB or
> the controller while 90% of hardware problems turned out to be power
> related.
I'll put a brand new, probably different PSU in the case and put the MB
and the 4 disks of the problematic controller on it, and put the 2 system
and other 4 disks to this one (or even another one).

Meanwhile I'd welcome if you have any suggestion why controller reset
causing a "fatal error"...
BTW, the drives were accessible after the array broke (when I got there).

Thanks,
Gabor 


  reply	other threads:[~2008-02-12 17:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  9:48 JMicron - hard resetting link Gabor FUNK
2008-02-12 13:05 ` Tejun Heo
2008-02-12 14:38   ` Gabor FUNK
2008-02-12 14:52     ` Tejun Heo
2008-02-12 17:27       ` Gabor FUNK [this message]
2008-02-12 23:50         ` Tejun Heo
2008-02-14 23:02           ` Gabor FUNK
2008-02-14 23:32             ` Tejun Heo
2008-02-21 21:45               ` Gabor FUNK
2008-02-22  2:03                 ` Tejun Heo
2008-02-24  9:04                   ` Gabor FUNK

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='002f01c86d9c$94542f50$4d0fa8c0@M2007' \
    --to=funk.gabor@hunetkft.hu \
    --cc=htejun@gmail.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