I too am having problems with the sata_promise driver in 2.6.12 with a Sata II
TX4, and a SATA on an intel SE7520BD2 board
First some Idea of what we are running -
Pristine Debian Sarge install
Stock Kernel 2.6.12.3 (with no extra patches)
Using the config from the 2.6.8-2-686-smp kernel supplied on debian,
(ie make oldconfig)
Also, I am getting the same problems with a 2.6.10 kernel
Relevant Lines from lspci
0000:00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage
Controller (rev 02) ß ONBOARD 2 Port SATA CONTROLLER
0000:02:03.0 RAID bus controller: Promise Technology, Inc. PDC20319 (FastTrak
S150 TX4) (rev 02) ß Promise S150 TX4 (raid controller used
as straight SATA controller)
0000:07:06.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown
device 3d18 (rev 02) ß Promise SATAII150 TX4 (straight SATA
controller)
What is happening is that when we use just the 1st and 3rd SATA controllers,
with Kernel 2.6.12.3, utilising debian sarge and LVM2, we have NO problem.
However, when we add a PDC20319 (2nd listed controller from lspci output), we
start to see some problems as follows
We started out with the following Errors whilst trying to mke2fs -j on an LVM
volume that spanned 3 drives on the PDC20319
Uhhuh. NMI recieved for unknown reason 31 on CPU0.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?
So, now in investigating this problem, we found nothing of interest as the
kernel was not generating any other messages - it would just repeat that error
3 times, wait about 15seconds and reboot.
On a whim, I disabled NMI watchdog with append="nmi_watchdog=0", and now
started to receive slightly more verbose error messages:
ata3 command timeout (sometimes it would give ata4 erros instead)
Machine Check Exception 0x4 (or something similar)
In investigating this error, we found the following link which would appear to
be the exact problem
http://www.opensubscriber.com/message/linux-ide@xxxxxxxxxxxxxxx/1671725.html
Is there anyone that might be investigating this problem that might be able use
this (and any more they need) information to maybe solve the issue?
I don't think the SATAII150 card is the problem, as it works fine in all
instances - the S150 TX4 works fine on Windows (I know, I know not a windows
forum) with all drives set in the same mode (each as an individual stripe)
In fact, if I plug the drives from the SATAII150 into the S150 TX4, the
previously working drives exhibit the same problem., and the reverse is true,
if I move the drives to the SATAII150, they work fine.
TIA
Allen Bolderoff
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|
