From: "Gavin Baker" <gavbaker@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: (HPT372A) cat /proc/ide/hpt366 == crash
Date: Mon, 10 Nov 2003 13:43:27 +0800 [thread overview]
Message-ID: <20031110054327.22352.qmail@linuxmail.org> (raw)
I have an Highpoint "RocketRaid 133" dual channel PCI IDE "raid" controller that uses an HPT372A.
With the latest 2.4's and 2.6.0-test9, if I cat /proc/ide/hpt366 I get the ide channel status followed shortly after by:
hdg: status timeout: status=0xd0 {Busy}
hdg: DMA disabled
hdg: drive not ready for command
ide3: reset: master: error (0x00?)
hdg: status timeout: status=0xd0 {Busy}
hdg: drive not ready for command
ide3: reset: master: error (0x00?)
end-request: I/O error, dev hdg, sector xxxxxx
EXT3-fs error (device md0): ext3_get_inode_loc: unable to read inode
block - inode = xxxxxx, block = xxxxxx
With the last two lines repeating until there is total filesystem corruption.
In regular usage they have been fine (I've built my distro from source without a problem).
dmesg:
HPT372A: IDE controller at PCI slot 0000:02:06.0
HPT372A: chipset revision 1
HPT37X: using 33MHz PCI clock
HPT372A: 100% native mode on irq 18
ide2: BM-DMA at 0xd800-0xd807, BIOS settings: hde:DMA, hdf:pio
HPT366: reg5ah=0x00 ATA-66 Cable Port0
ide3: BM-DMA at 0xd808-0xd80f, BIOS settings: hdg:DMA, hdh:pio
HPT366: reg5ah=0x00 ATA-66 Cable Port0
hde: ST3120026A, ATA DISK drive
ide2 at 0xc800-0xc807,0xcc02 on irq 18
hdg: ST3120026A, ATA DISK drive
ide3 at 0xd000-0xd007,0xd402 on irq 18
hde: max request size: 1024KiB
hde: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,
UDMA(100)
/dev/ide/host2/bus0/target0/lun0: p1 p2 p3
hdg: max request size: 1024KiB
hdg: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,
UDMA(100)
/dev/ide/host2/bus1/target0/lun0: p1 p2 p3
lspci:
02:06.0 RAID bus controller: Triones Technologies, Inc. HPT372A (rev
01)
Subsystem: Triones Technologies, Inc.: Unknown device 0001
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 120 (2000ns min, 2000ns max)
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at c800 [size=8]
Region 1: I/O ports at cc00 [size=4]
Region 2: I/O ports at d000 [size=8]
Region 3: I/O ports at d400 [size=4]
Region 4: I/O ports at d800 [size=256]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Both drives are new seagate barracudas. They both have DMA enabled. I use regular kernel raid0, not the software raid drivers.
Probably related, the SMART data from these drives is showing Hardware_ECC_Recovered is up over 31 and 120 million, with Power_On_Hours less than 250.
Any ideas?
Thanks,
Gavin Baker
(PS, please CC: me)
--
______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
next reply other threads:[~2003-11-10 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 5:43 Gavin Baker [this message]
2003-11-10 15:10 ` (HPT372A) DMA/Interrupt problems, again Tomi Orava
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=20031110054327.22352.qmail@linuxmail.org \
--to=gavbaker@linuxmail.org \
--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 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.