From: "Janos Haar" <djani22@netcenter.hu>
To: <linux-kernel@vger.kernel.org>
Subject: critical bug in sata driver ?
Date: Mon, 5 Jun 2006 12:27:15 +0200 [thread overview]
Message-ID: <011c01c6888a$a0a881a0$1800a8c0@dcccs> (raw)
Hello, list,
I have a reproducible _software_ bug about sata. (libata?)
In my system i have 4 nodes, each has 12 hdd.
All hw are equal, and 110% tested, and really error free!
But 2 of my nodes, frequently reboots without and any error message on
remote syslog, and netconsole.
No oops, no nothing!
(loglevel 9)
Only in serial console can show some time a little clue:
"ata2: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
ata2: status=0x51 { DriveReady SeekComplete Error"
After this little partial message, the system immediately reboots!
Thats the all.
The smart log is clear in _all_ my 48 hdd.
Anyway the disk and cable in ata2 port is replaced, but this not helps.
The kernel 2.6.16.1, 2.6.17-rc3-git1. (now i trying the latest rc and git.)
(I cannot try the 2.6.16 > kernels, because my sata card are unsupported on
older versions.)
The dmesg log is here from my node #1:
http://download.netcenter.hu/bughunt/20060605/dmesg.txt
I have compile the kernel with these debug options:
[*] Magic SysRq key
[*] Kernel debugging
[*] Collect scheduler statistics
[*] Mutex debugging, deadlock detection
[*] Force gcc to inline functions marked 'inline'
[*] Check for stack overflows
(2) Stack backtraces per line
[*] Debug page memory allocations
[*] Write protect kernel read-only data structures
Can somebody find and fix it?
I can do almost anything to helping to debug!
Thanks,
Janos
next reply other threads:[~2006-06-05 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 10:27 Janos Haar [this message]
2006-06-05 15:12 ` Janos Haar
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='011c01c6888a$a0a881a0$1800a8c0@dcccs' \
--to=djani22@netcenter.hu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®