* Re: siimage driver status
2003-05-29 14:32 siimage driver status Wm. Josiah Erikson
@ 2003-05-29 13:54 ` Alan Cox
2003-05-29 15:00 ` Wm. Josiah Erikson
` (2 more replies)
2003-05-29 15:00 ` lk
1 sibling, 3 replies; 20+ messages in thread
From: Alan Cox @ 2003-05-29 13:54 UTC (permalink / raw)
To: Wm. Josiah Erikson; +Cc: Linux Kernel Mailing List
On Iau, 2003-05-29 at 15:32, Wm. Josiah Erikson wrote:
> hard drives that I'm trying to get to work with linux 2.4.21-rc6. The
> problem I'm having is that it's REALLY slow and crashy. The kernel reports
> this on bootup:
I'm running the siimage driver fine with several drives. Your setup is
intriguing in that the BIOS has chosen to leave the drives in PIO mode
> SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
> SiI3112 Serial ATA: chipset revision 2
> SiI3112 Serial ATA: not 100% native mode: will probe irqs later
> ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
> ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
Really the SATA drives ought to have come up in UDMA
> everything else on my system to a temporary halt, and hdparm -t reports
> about 1.3MB/sec reads. This is a bummer, as I was hoping to RAID 0 them
> together and make them my boot drives :)
>
> If I try and enable DMA, the machine instantly hardlocks.
Thats with hdparm -X66 -d1 ?
The only updates to the siimage driver are those in 2.4.21-ac which you
shouldn't need.
^ permalink raw reply [flat|nested] 20+ messages in thread
* siimage driver status
@ 2003-05-29 14:32 Wm. Josiah Erikson
2003-05-29 13:54 ` Alan Cox
2003-05-29 15:00 ` lk
0 siblings, 2 replies; 20+ messages in thread
From: Wm. Josiah Erikson @ 2003-05-29 14:32 UTC (permalink / raw)
To: linux-kernel
Hello all,
I have an Asus A7V8X Deluxe motherboard with a couple of WD Raptor
hard drives that I'm trying to get to work with linux 2.4.21-rc6. The
problem I'm having is that it's REALLY slow and crashy. The kernel reports
this on bootup:
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
NFORCE2: IDE controller at PCI slot 00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
AMD_IDE: Bios didn't set cable bits corectly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
AMD_IDE: PCI device 10de:0065 (nVidia Corporation) (rev a2) UDMA100
controller o
n pci00:09.0
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
SiI3112 Serial ATA: chipset revision 2
SiI3112 Serial ATA: not 100% native mode: will probe irqs later
ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
hda: SAMSUNG SP4002H, ATA DISK drive
blk: queue c02f6d40, I/O limit 4095Mb (mask 0xffffffff)
hdc: _NEC CD-RW NR-9300A, ATAPI CD/DVD-ROM drive
hdd: JLMS XJ-HD166S, ATAPI CD/DVD-ROM drive
hde: WDC WD360GD-00FNA0, ATA DISK drive
hdg: WDC WD360GD-00FNA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xe0800080-0xe0800087,0xe080008a on irq 11
ide3 at 0xe08000c0-0xe08000c7,0xe08000ca on irq 11
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 78242976 sectors (40060 MB) w/2048KiB Cache, CHS=4870/255/63,
UDMA(100)
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 72303840 sectors (37020 MB) w/8192KiB Cache, CHS=4500/255/63
hdg: attached ide-disk driver.
hdg: host protected area => 1
hdg: 72303840 sectors (37020 MB) w/8192KiB Cache, CHS=4500/255/63
hdc: attached ide-scsi driver.
hdd: attached ide-scsi driver.
Partition check:
hda: hda1 hda2 hda3
hde: unknown partition table
hdg: unknown partition table
The nforce2 ide controller works great, as does the drive on it. When I
try to use either of the drives on the siimage controller, it brings
everything else on my system to a temporary halt, and hdparm -t reports
about 1.3MB/sec reads. This is a bummer, as I was hoping to RAID 0 them
together and make them my boot drives :)
If I try and enable DMA, the machine instantly hardlocks.
I'm running debian sarge, if it matters.
Is there anything I should try, or is the siimage driver just still very
early on in its development? I would be more than happy to beta- (or
alpha) test code, or give developers access to my box if testbed platforms
are needed. Whatever I can do to make it work :)
Thanks very much in advance
-Josiah
Computer Guy
Hampshire College School of NS
Amherst, MA 01002
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-29 15:00 ` Wm. Josiah Erikson
@ 2003-05-29 14:56 ` Alan Cox
2003-05-29 19:32 ` Wm. Josiah Erikson
0 siblings, 1 reply; 20+ messages in thread
From: Alan Cox @ 2003-05-29 14:56 UTC (permalink / raw)
To: Wm. Josiah Erikson; +Cc: Linux Kernel Mailing List
On Iau, 2003-05-29 at 16:00, Wm. Josiah Erikson wrote:
> Wow. I feel dumb. When I add the -X66 to tell the drive as well, then
> everything is peachy. Thanks! :)
Its hardly obvious.
> Now I suppose I just have to figure out how to make that work on boot
> (perhaps just to make the BIOS put them in DMA mode)
One thing I might do is just make the driver ignore the bios policy for
disk devices.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-29 13:54 ` Alan Cox
@ 2003-05-29 15:00 ` Wm. Josiah Erikson
2003-05-29 14:56 ` Alan Cox
2003-05-29 22:26 ` Gutko
2003-05-30 18:57 ` lk
2 siblings, 1 reply; 20+ messages in thread
From: Wm. Josiah Erikson @ 2003-05-29 15:00 UTC (permalink / raw)
To: Alan Cox; +Cc: Linux Kernel Mailing List
Wow. I feel dumb. When I add the -X66 to tell the drive as well, then
everything is peachy. Thanks! :)
Now I suppose I just have to figure out how to make that work on boot
(perhaps just to make the BIOS put them in DMA mode)
-Josiah
On 29 May 2003, Alan Cox wrote:
On Iau, 2003-05-29 at 15:32, Wm. Josiah Erikson wrote:
> hard drives that I'm trying to get to work with linux 2.4.21-rc6. The
> problem I'm having is that it's REALLY slow and crashy. The kernel reports
> this on bootup:
I'm running the siimage driver fine with several drives. Your setup is
intriguing in that the BIOS has chosen to leave the drives in PIO mode
> SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
> SiI3112 Serial ATA: chipset revision 2
> SiI3112 Serial ATA: not 100% native mode: will probe irqs later
> ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
> ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
Really the SATA drives ought to have come up in UDMA
> everything else on my system to a temporary halt, and hdparm -t reports
> about 1.3MB/sec reads. This is a bummer, as I was hoping to RAID 0 them
> together and make them my boot drives :)
>
> If I try and enable DMA, the machine instantly hardlocks.
Thats with hdparm -X66 -d1 ?
The only updates to the siimage driver are those in 2.4.21-ac which you
shouldn't need.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-29 14:32 siimage driver status Wm. Josiah Erikson
2003-05-29 13:54 ` Alan Cox
@ 2003-05-29 15:00 ` lk
1 sibling, 0 replies; 20+ messages in thread
From: lk @ 2003-05-29 15:00 UTC (permalink / raw)
To: Wm. Josiah Erikson; +Cc: Linux Kernel Mailing List, Alan Cox
> I have an Asus A7V8X Deluxe motherboard with a couple of WD Raptor
> hard drives that I'm trying to get to work with linux 2.4.21-rc6. The
> problem I'm having is that it's REALLY slow and crashy. The kernel reports
> this on bootup:
> SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
> If I try and enable DMA, the machine instantly hardlocks.
>
> Is there anything I should try, or is the siimage driver just still very
> early on in its development? I would be more than happy to beta- (or
> alpha) test code, or give developers access to my box if testbed platforms
> are needed. Whatever I can do to make it work :)
I have the same problem, and reported it back in 2.4.21-pre-something, but
nobody seemed interested. I have the same problem with onboard chipsets
as with addon PCI cards from various manufacturers. It's absolutely
impossible to enable DMA on the SiI controllers. The "funny" thing is
that I purchased them on a recommendation from someone on lk who glowed
over their robustness.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-29 14:56 ` Alan Cox
@ 2003-05-29 19:32 ` Wm. Josiah Erikson
0 siblings, 0 replies; 20+ messages in thread
From: Wm. Josiah Erikson @ 2003-05-29 19:32 UTC (permalink / raw)
To: Alan Cox; +Cc: Linux Kernel Mailing List
That might be nice - would it be possible for you to send me a patch? Or
is there something I can pass to the kernel at boottime that will make it
enable DMA? I've been experimenting with ide2=autotune hde=autotune etc
and that doesn't seem to be working.
Thanks so much,
-Josiah
On 29 May 2003, Alan Cox wrote:
<SNIP>
> Now I suppose I just have to figure out how to make that work on boot
> (perhaps just to make the BIOS put them in DMA mode)
One thing I might do is just make the driver ignore the bios policy for
disk devices.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-29 13:54 ` Alan Cox
2003-05-29 15:00 ` Wm. Josiah Erikson
@ 2003-05-29 22:26 ` Gutko
2003-06-03 7:17 ` Marco Tedaldi
2003-05-30 18:57 ` lk
2 siblings, 1 reply; 20+ messages in thread
From: Gutko @ 2003-05-29 22:26 UTC (permalink / raw)
To: lkml; +Cc: Alan Cox
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
> On Iau, 2003-05-29 at 15:32, Wm. Josiah Erikson wrote:
> > hard drives that I'm trying to get to work with linux 2.4.21-rc6. The
> > problem I'm having is that it's REALLY slow and crashy. The kernel
reports
> > this on bootup:
>
> I'm running the siimage driver fine with several drives. Your setup is
> intriguing in that the BIOS has chosen to leave the drives in PIO mode
>
> > SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
> > SiI3112 Serial ATA: chipset revision 2
> > SiI3112 Serial ATA: not 100% native mode: will probe irqs later
> > ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
> > ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
>
> Really the SATA drives ought to have come up in UDMA
I have Asus A7N8X deluxe too, and I reported this issue with rc4.
I'm running one IBM vancouver2 180gxp drive on SIL3112A, and I always have
PIO on boot.
I can enable DMA manually and it works good, but I can bet if I connect
second hdd in RAID
with this I already have, I'll get all problems described above!!! My friend
also runs succesfully ONE
hdd in DMA on the same ASUS on sata, but connecting seconf drive blows
everything away..
Gutko
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-29 13:54 ` Alan Cox
2003-05-29 15:00 ` Wm. Josiah Erikson
2003-05-29 22:26 ` Gutko
@ 2003-05-30 18:57 ` lk
2003-05-30 21:44 ` Bob Johnson
2 siblings, 1 reply; 20+ messages in thread
From: lk @ 2003-05-30 18:57 UTC (permalink / raw)
To: Alan Cox; +Cc: Wm. Josiah Erikson, Linux Kernel Mailing List
> On Iau, 2003-05-29 at 16:00, Wm. Josiah Erikson wrote:
> > Wow. I feel dumb. When I add the -X66 to tell the drive as well, then
> > everything is peachy. Thanks! :)
>
> Its hardly obvious.
>
> > Now I suppose I just have to figure out how to make that work on boot
> > (perhaps just to make the BIOS put them in DMA mode)
>
> One thing I might do is just make the driver ignore the bios policy for
> disk devices.
I reinstalled my SiImage controller this morning because I hadn't
documented using the -X66 switch during my previous testing. It actually
makes a bit of a difference- the DMA enables and THEN the machine locks
hard when any reasonable amount of data is written to the drives on the
controller.
I get two console messages before the machine locks hard:
hde: dma_timer_expiry: dma status == 0x22
hde: dma_timer_expiry status = 0xd8 { Busy }
I'd love to get this tracked down...
Brian.
-----------------------
from /var/log/messages
May 30 11:34:38 nfs2 kernel: SiI3112 Serial ATA: IDE controller at PCI slot 05:02.0
May 30 11:34:38 nfs2 kernel: SiI3112 Serial ATA: chipset revision 2
May 30 11:34:38 nfs2 kernel: SiI3112 Serial ATA: not 100%% native mode: will probe irqs later
May 30 11:34:38 nfs2 kernel: ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
May 30 11:34:38 nfs2 kernel: ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
----
hdparm -X66 -d1 /dev/hde
hdparm -X66 -d1 /dev/hdg
[root@nfs2 settings]# cat /proc/ide/siimage
Controller: 0
SiI3112 Chipset.
MMIO Base 0xf880d000
MMIO-DMA Base 0xf880d000
MMIO-DMA Base 0xf880d008
--------------- Primary Channel ---------------- Secondary Channel -------------
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1 ------
PIO Mode: ? ? ? ?
hdparm -I /dev/hde
/dev/hde:
ATA device, with non-removable media
Model Number: Maxtor 6Y200P0
Serial Number: Yv0AXR8E
Firmware Revision: YAR41VW0
Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:
Logical max current
cylinders 16383 65535
heads 16 1
sectors/track 63 63
--
CHS current addressable sectors: 4128705
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 402622464
device size with M = 1024*1024: 196593 MBytes
device size with M = 1000*1000: 206142 MBytes (206 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 1
Standby timer values: spec'd by Standard, no device specific
minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 192, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* NOP cmd
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* FLUSH CACHE EXT command
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* 48-bit Address feature set
* Automatic Acoustic Management feature set
SET MAX security extension
Advanced Power Management feature set
* DOWNLOAD MICROCODE cmd
* SMART self-test
* SMART error logging
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
/proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.40GHz
stepping : 7
cpu MHz : 2399.366
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips : 4784.12
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.40GHz
stepping : 7
cpu MHz : 2399.366
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips : 4797.23
processor : 2
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.40GHz
stepping : 7
cpu MHz : 2399.366
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips : 4797.23
processor : 3
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.40GHz
stepping : 7
cpu MHz : 2399.366
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips : 4797.23
lspci -vvv
00:00.0 Host bridge: Intel Corp.: Unknown device 254c (rev 01)
Subsystem: Super Micro Computer Inc: Unknown device 3480
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [40] #09 [1105]
00:00.1 Class ff00: Intel Corp. e7500 [Plumas] DRAM Controller Error Reporting (rev 01)
Subsystem: Super Micro Computer Inc P4DP6
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:02.0 PCI bridge: Intel Corp. e7500 [Plumas] HI_B Virtual PCI Bridge (F0) (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=01, subordinate=03, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: fc100000-fc2fffff
Prefetchable memory behind bridge: fff00000-000fffff
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
00:03.0 PCI bridge: Intel Corp. e7500 [Plumas] HI_C Virtual PCI Bridge (F0) (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=04, subordinate=06, sec-latency=0
I/O behind bridge: 00004000-00005fff
Memory behind bridge: fc300000-fcffffff
Prefetchable memory behind bridge: fff00000-000fffff
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02) (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc P4DP6
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: 0
Interrupt: pin A routed to IRQ 16
Region 4: I/O ports at 2000 [size=32]
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02) (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc P4DP6
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: 0
Interrupt: pin B routed to IRQ 19
Region 4: I/O ports at 2020 [size=32]
00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02) (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc P4DP6
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: 0
Interrupt: pin C routed to IRQ 18
Region 4: I/O ports at 2040 [size=32]
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 42) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=64
I/O behind bridge: 00006000-00006fff
Memory behind bridge: fd000000-fe0fffff
Prefetchable memory behind bridge: fff00000-000fffff
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
00:1f.0 ISA bridge: Intel Corp. 82801CA ISA Bridge (LPC) (rev 02)
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: 0
00:1f.1 IDE interface: Intel Corp. 82801CA IDE U100 (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Super Micro Computer Inc P4DP6
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: 0
Interrupt: pin A routed to IRQ 0
Region 0: I/O ports at <ignored>
Region 1: I/O ports at <ignored>
Region 2: I/O ports at <ignored>
Region 3: I/O ports at <ignored>
Region 4: I/O ports at 2060 [size=16]
Region 5: Memory at 80000000 (32-bit, non-prefetchable) [size=1K]
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus (rev 02)
Subsystem: Super Micro Computer Inc P4DP6
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-
Interrupt: pin B routed to IRQ 0
Region 4: I/O ports at 1100 [size=32]
01:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) (prog-if 20 [IO(X)-APIC])
Subsystem: Super Micro Computer Inc P4DP6
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at fc100000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE- ERO- RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
01:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, cache line size 10
Bus: primary=01, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort+ >Reset- FastB2B-
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE+ ERO+ RBC=0 OST=4
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
01:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) (prog-if 20 [IO(X)-APIC])
Subsystem: Super Micro Computer Inc P4DP6
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at fc101000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE- ERO- RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
01:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, cache line size 10
Bus: primary=01, secondary=03, subordinate=03, sec-latency=64
I/O behind bridge: 00003000-00003fff
Memory behind bridge: fc200000-fc2fffff
Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort+ >Reset- FastB2B-
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE+ ERO+ RBC=0 OST=4
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
03:02.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
Subsystem: Intel Corp. PRO/1000 MT Dual Port Server Adapter
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: 64 (63750ns min), cache line size 08
Interrupt: pin A routed to IRQ 28
Region 0: Memory at fc200000 (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at 3000 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [e4] PCI-X non-bridge device.
Command: DPERE- ERO+ RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
03:02.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
Subsystem: Intel Corp. PRO/1000 MT Dual Port Server Adapter
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: 64 (63750ns min), cache line size 08
Interrupt: pin B routed to IRQ 29
Region 0: Memory at fc220000 (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at 3040 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [e4] PCI-X non-bridge device.
Command: DPERE- ERO+ RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
04:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) (prog-if 20 [IO(X)-APIC])
Subsystem: Super Micro Computer Inc P4DP6
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at fc300000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE- ERO- RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
04:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, cache line size 10
Bus: primary=04, secondary=05, subordinate=05, sec-latency=48
I/O behind bridge: 00004000-00004fff
Memory behind bridge: fc400000-fc4fffff
Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort+ >Reset- FastB2B-
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE+ ERO+ RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
04:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) (prog-if 20 [IO(X)-APIC])
Subsystem: Super Micro Computer Inc P4DP6
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at fc301000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE- ERO- RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
04:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, cache line size 10
Bus: primary=04, secondary=06, subordinate=06, sec-latency=48
I/O behind bridge: 00005000-00005fff
Memory behind bridge: fc500000-fcffffff
Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort+ >Reset- FastB2B-
Capabilities: [50] PCI-X non-bridge device.
Command: DPERE+ ERO+ RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
05:02.0 RAID bus controller: CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller (rev 02)
Subsystem: CMD Technology Inc: Unknown device 6112
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: 64, cache line size 01
Interrupt: pin A routed to IRQ 100
Region 0: I/O ports at 4020 [size=8]
Region 1: I/O ports at 4010 [size=4]
Region 2: I/O ports at 4018 [size=8]
Region 3: I/O ports at 4014 [size=4]
Region 4: I/O ports at 4000 [size=16]
Region 5: Memory at fc400000 (32-bit, non-prefetchable) [size=512]
Expansion ROM at <unassigned> [disabled] [size=512K]
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=2 PME-
07:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage XL
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: 64 (2000ns min), cache line size 08
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at 6000 [size=256]
Region 2: Memory at fe000000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [5c] 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-
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-30 18:57 ` lk
@ 2003-05-30 21:44 ` Bob Johnson
0 siblings, 0 replies; 20+ messages in thread
From: Bob Johnson @ 2003-05-30 21:44 UTC (permalink / raw)
To: lk; +Cc: linux-kernel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This is the exact problem i have with onboard siimage (asus a7n8x)
or a siimage controller card on a abit motherboard. (kt7a)
echo "max_kb_per_request:15" > /proc/ide/hde/settings
is a work around for 2.4.XX.
Bob
> I get two console messages before the machine locks hard:
> hde: dma_timer_expiry: dma status == 0x22
> hde: dma_timer_expiry status = 0xd8 { Busy }
>
> I'd love to get this tracked down...
>
>
> Brian.
>
> -----------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+19CuxJgsCy9JAX0RArvcAJ9JdNeIAGCcDvrSSqvam6XgPklm9ACfSPx5
M+JgErtFM9OoqP/6yZuMxnQ=
=q97p
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-05-29 22:26 ` Gutko
@ 2003-06-03 7:17 ` Marco Tedaldi
2003-06-03 12:43 ` Alan Cox
2003-06-03 14:11 ` Wm. Josiah Erikson
0 siblings, 2 replies; 20+ messages in thread
From: Marco Tedaldi @ 2003-06-03 7:17 UTC (permalink / raw)
To: linux-kernel
Gutko wrote:
> From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
> I have Asus A7N8X deluxe too, and I reported this issue with rc4.
> I'm running one IBM vancouver2 180gxp drive on SIL3112A, and I always have
> PIO on boot.
> I can enable DMA manually and it works good, but I can bet if I connect
> second hdd in RAID
> with this I already have, I'll get all problems described above!!! My friend
> also runs succesfully ONE
> hdd in DMA on the same ASUS on sata, but connecting seconf drive blows
> everything away..
This issue was reported by at least 3 People here on the list (including
me) with different 21-rcX kernels. Seems noone really cared :-(
I hope, this issue now get's addressed.
btw. I could speed up my Transfer-Rate from 1.7MB/s to 55MB/s by setting
hdparm -d1 -X66 on my two native SATA-Drives.
bye
Marco
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 7:17 ` Marco Tedaldi
@ 2003-06-03 12:43 ` Alan Cox
2003-06-03 14:11 ` Wm. Josiah Erikson
1 sibling, 0 replies; 20+ messages in thread
From: Alan Cox @ 2003-06-03 12:43 UTC (permalink / raw)
To: Marco Tedaldi; +Cc: Linux Kernel Mailing List
On Maw, 2003-06-03 at 08:17, Marco Tedaldi wrote:
> This issue was reported by at least 3 People here on the list (including
> me) with different 21-rcX kernels. Seems noone really cared :-(
Wrong
> I hope, this issue now get's addressed.
It already has been. Its just I like to take the time to make sure a
change is correct rather than dumping it out and seeing if it eats
anyones disks.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 14:11 ` Wm. Josiah Erikson
@ 2003-06-03 13:49 ` Alan Cox
2003-06-03 15:07 ` Wm. Josiah Erikson
2003-06-03 15:13 ` Bob Johnson
2003-06-03 14:45 ` Justin Cormack
1 sibling, 2 replies; 20+ messages in thread
From: Alan Cox @ 2003-06-03 13:49 UTC (permalink / raw)
To: Wm. Josiah Erikson; +Cc: Linux Kernel Mailing List
On Maw, 2003-06-03 at 15:11, Wm. Josiah Erikson wrote:
> Is there some silly hack I can do to the driver code to force all devices
> to DMA on bootup? Everything works fine except for that. I'm using
> 2.4.21-rc6-ac1
-ac2 knows the firmware doesn't intialise DMA mode and shouldn't be used
as a safety guide.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 7:17 ` Marco Tedaldi
2003-06-03 12:43 ` Alan Cox
@ 2003-06-03 14:11 ` Wm. Josiah Erikson
2003-06-03 13:49 ` Alan Cox
2003-06-03 14:45 ` Justin Cormack
1 sibling, 2 replies; 20+ messages in thread
From: Wm. Josiah Erikson @ 2003-06-03 14:11 UTC (permalink / raw)
To: linux-kernel
I have two drives (WD Raptors) on my A7N8X. I don't see any errors, even
after writing 9GB of data to the drive (after I've done an hdparm -X66
-d1 /dev/hd[x]), but it still boots up in pio mode.
Is there some silly hack I can do to the driver code to force all devices
to DMA on bootup? Everything works fine except for that. I'm using
2.4.21-rc6-ac1
Thanks!
-Josiah
This issue was reported by at least 3 People here on the list (including
me) with different 21-rcX kernels. Seems noone really cared :-(
I hope, this issue now get's addressed.
btw. I could speed up my Transfer-Rate from 1.7MB/s to 55MB/s by setting
hdparm -d1 -X66 on my two native SATA-Drives.
bye
Marco
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 14:11 ` Wm. Josiah Erikson
2003-06-03 13:49 ` Alan Cox
@ 2003-06-03 14:45 ` Justin Cormack
1 sibling, 0 replies; 20+ messages in thread
From: Justin Cormack @ 2003-06-03 14:45 UTC (permalink / raw)
To: Wm. Josiah Erikson; +Cc: Kernel mailing list
On Tue, 2003-06-03 at 15:11, Wm. Josiah Erikson wrote:
> I have two drives (WD Raptors) on my A7N8X. I don't see any errors, even
> after writing 9GB of data to the drive (after I've done an hdparm -X66
> -d1 /dev/hd[x]), but it still boots up in pio mode.
> Is there some silly hack I can do to the driver code to force all devices
> to DMA on bootup? Everything works fine except for that. I'm using
> 2.4.21-rc6-ac1
> Thanks!
> -Josiah
>
>
> This issue was reported by at least 3 People here on the list (including
> me) with different 21-rcX kernels. Seems noone really cared :-(
>
> I hope, this issue now get's addressed.
> btw. I could speed up my Transfer-Rate from 1.7MB/s to 55MB/s by setting
> hdparm -d1 -X66 on my two native SATA-Drives.
I think people care. Andre said he was working on a fix for the Seagate
drives some time back. It does seem that all BIOSs leave SATA drives in
PIO mode. That may be a bios bug really rather than a linux bug. But if
you put the hdparm somewhere early in boot you should be ok, as a
temporary workaround.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 13:49 ` Alan Cox
@ 2003-06-03 15:07 ` Wm. Josiah Erikson
2003-06-03 15:13 ` Bob Johnson
1 sibling, 0 replies; 20+ messages in thread
From: Wm. Josiah Erikson @ 2003-06-03 15:07 UTC (permalink / raw)
To: Alan Cox; +Cc: Linux Kernel Mailing List
Yeah, I just tried -ac2 and it does the same thing :)
-Josiah
On 3 Jun 2003, Alan Cox wrote:
On Maw, 2003-06-03 at 15:11, Wm. Josiah Erikson wrote:
> Is there some silly hack I can do to the driver code to force all devices
> to DMA on bootup? Everything works fine except for that. I'm using
> 2.4.21-rc6-ac1
-ac2 knows the firmware doesn't intialise DMA mode and shouldn't be used
as a safety guide.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 13:49 ` Alan Cox
2003-06-03 15:07 ` Wm. Josiah Erikson
@ 2003-06-03 15:13 ` Bob Johnson
2003-06-03 15:29 ` Wm. Josiah Erikson
1 sibling, 1 reply; 20+ messages in thread
From: Bob Johnson @ 2003-06-03 15:13 UTC (permalink / raw)
To: Linux Kernel Mailing List
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Has anything been addressed to help the instant lock up when enabling dma
that alot of users are reporting?
On Tuesday 03 June 2003 08:49 am, Alan Cox wrote:
> On Maw, 2003-06-03 at 15:11, Wm. Josiah Erikson wrote:
> > Is there some silly hack I can do to the driver code to force all devices
> > to DMA on bootup? Everything works fine except for that. I'm using
> > 2.4.21-rc6-ac1
>
> -ac2 knows the firmware doesn't intialise DMA mode and shouldn't be used
> as a safety guide.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+3LsNxJgsCy9JAX0RAu1nAKCoenOMiRTv2ePaViUpFir6haKa/QCfXes7
wXfUqridTKwYel5uvId1QPI=
=AyVa
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 15:13 ` Bob Johnson
@ 2003-06-03 15:29 ` Wm. Josiah Erikson
2003-06-03 15:58 ` Bob Johnson
0 siblings, 1 reply; 20+ messages in thread
From: Wm. Josiah Erikson @ 2003-06-03 15:29 UTC (permalink / raw)
To: Bob Johnson; +Cc: Linux Kernel Mailing List
Does this still happen? It used to happen to me, but as soon as I added
-X66, per Alan's suggestion, everything is fine.
-Josiah (currently in the middle of writing 36GB to a two-drive
RAID 0 array on a sil3112 controller and everything is peachy - fast as
HELL, actually - grin - I've never seen over 100MB/sec off a RAID 0 of two
drives before)
On Tue, 3 Jun 2003, Bob Johnson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Has anything been addressed to help the instant lock up when enabling dma
that alot of users are reporting?
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
2003-06-03 15:29 ` Wm. Josiah Erikson
@ 2003-06-03 15:58 ` Bob Johnson
0 siblings, 0 replies; 20+ messages in thread
From: Bob Johnson @ 2003-06-03 15:58 UTC (permalink / raw)
To: Wm. Josiah Erikson; +Cc: Linux Kernel Mailing List
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
yes, ive always added -X66 , the only way to not lock is a trick from siimages
site (think it was in a mandrake script)
echo "max_kb_per_request:15" > /proc/ide/hde/settings
The lockup also happens in latest 2.5 kernels, which the above command
is only for 2.4.
On Tuesday 03 June 2003 10:29 am, Wm. Josiah Erikson wrote:
> Does this still happen? It used to happen to me, but as soon as I added
> -X66, per Alan's suggestion, everything is fine.
> -Josiah (currently in the middle of writing 36GB to a two-drive
> RAID 0 array on a sil3112 controller and everything is peachy - fast as
> HELL, actually - grin - I've never seen over 100MB/sec off a RAID 0 of two
> drives before)
>
>
> On Tue, 3 Jun 2003, Bob Johnson wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Has anything been addressed to help the instant lock up when enabling dma
> that alot of users are reporting?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+3MWSxJgsCy9JAX0RAlpwAJ9Q0Pmz1Xda8tCvmuVjV21G8oDwAgCbBKzI
e6707tgTmA2nQKlfsVvr/pw=
=Ct7+
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
@ 2003-06-04 17:23 Rob Browning
0 siblings, 0 replies; 20+ messages in thread
From: Rob Browning @ 2003-06-04 17:23 UTC (permalink / raw)
To: linux-kernel
Alan Cox (alan@lxorguk.ukuu.org.uk) writes:
> On Iau, 2003-05-29 at 15:32, Wm. Josiah Erikson wrote:
> > hard drives that I'm trying to get to work with linux 2.4.21-rc6. The
> > problem I'm having is that it's REALLY slow and crashy. The kernel reports
> > this on bootup:
>
> I'm running the siimage driver fine with several drives. Your setup
> is intriguing in that the BIOS has chosen to leave the drives in PIO
> mode
As an extra datapoint I have very a very similar problem with a WD360
drive and an siimage 3112 PCI controller on a shuttle (via-based)
AK31V2.0 motherboard.
The sii3112 interfaces show up as ide0 and ide1 (can that be changed?)
using MMIO-DMA/pio. Testing the drive as-is results in ~3.5MB/s
transfer rates (via hdparm -t), and attempting to enable DMA via
"hdparm -d 1" results in an immediate lockup the next time the drive
is accessed.
When I get another chance, I'll probably try the two fixes others in
this thread have suggested:
hdparm -X66 -d1 /dev/hda
and if that still has trouble under load, someone suggested:
echo "max_kb_per_request:15" > /proc/ide/hda/settings
Hope this helps.
(I'm not on the list right now, so please cc any replies you want to
make sure I see -- thanks.)
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: siimage driver status
@ 2003-05-31 9:34 Inigo Surguy
0 siblings, 0 replies; 20+ messages in thread
From: Inigo Surguy @ 2003-05-31 9:34 UTC (permalink / raw)
To: linux-kernel
From: lk@trolloc.com (lk@trolloc.com)
> I reinstalled my SiImage controller this morning because I hadn't
> documented using the -X66 switch during my previous testing. It actually
> makes a bit of a difference- the DMA enables and THEN the machine locks
> hard when any reasonable amount of data is written to the drives on the
> controller.
>
> I get two console messages before the machine locks hard:
> hde: dma_timer_expiry: dma status == 0x22
> hde: dma_timer_expiry status = 0xd8 { Busy }
>
I have the same problem - I have an Asus A7N8X using the SiI3112A, with a
Seagate Barracuda SATA ST380023AS. It comes up (and works, but very slowly)
in pio.
When I enable DMA with hdparm -d1 /dev/hde, or hdparm -Xudma2 -d1,
then I get the dma_timer_expiry messages above, and then a hard lock.
When I enable DMA with hdparm -Xudma6 -d1, or hdparm -Xudma5 -d1, then the
DMA enables, I can hdparm -t to see that transfer rate is much better (25x)
than before, but as soon as I write to the drive I get the dma_timer_expiry
messages above.
(Dual-boot Windows XP is using UDMA6 for this drive)
There's similar behaviour under 2.4.20, 2.4.21rc5ac2 and 2.4.21rc6.
Inigo
---
/var/log/messages
May 29 19:53:22 localhost kernel: NFORCE2: IDE controller at PCI slot 00:09.0
May 29 19:53:22 localhost kernel: NFORCE2: chipset revision 162
May 29 19:53:22 localhost kernel: NFORCE2: not 100%% native mode: will probe irqs later
May 29 19:53:22 localhost kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
May 29 19:53:22 localhost kernel: AMD_IDE: PCI device 10de:0065 (nVidia Corporation) (rev a2) UDMA100 controller on pci00:09.0
May 29 19:53:22 localhost kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
May 29 19:53:22 localhost kernel: ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
May 29 19:53:22 localhost kernel: SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
May 29 19:53:22 localhost kernel: SiI3112 Serial ATA: chipset revision 2
May 29 19:53:22 localhost kernel: SiI3112 Serial ATA: not 100%% native mode: will probe irqs later
May 29 19:53:22 localhost kernel: ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
May 29 19:53:22 localhost kernel: ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
May 29 19:53:22 localhost autofs: automount startup succeeded
May 29 19:53:22 localhost automount[1145]: starting automounter version 3.1.7, path = /automount/cabbit, maptype = file, mapname = /etc/auto.cabbit
May 29 19:53:22 localhost kernel: hda: Pioneer DVD-ROM ATAPIModel DVD-104S 020, ATAPI CD/DVD-ROM drive
May 29 19:53:22 localhost kernel: hdd: Maxtor 98196H8, ATA DISK drive
May 29 19:53:22 localhost kernel: blk: queue c033b030, I/O limit 4095Mb (mask 0xffffffff)
May 29 19:53:22 localhost kernel: hde: ST380023AS, ATA DISK drive
May 29 19:53:22 localhost kernel: hdg: no response (status = 0xfe)
May 29 19:53:22 localhost kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
May 29 19:53:22 localhost kernel: ide1 at 0x170-0x177,0x376 on irq 15
May 29 19:53:22 localhost kernel: ide2 at 0xf880d080-0xf880d087,0xf880d08a on irq 11
---
hdparm -i /dev/hde
/dev/hde:
Model=ST380023AS, FwRev=3.01, SerialNo=3KB18AAX
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2: 1 2 3 4 5 6
---
The console messages after enabling DMA (these are copied down from my
digital camera, so may not be exact, but I think they're pretty close)
hde: dma_timer_expiry: dma_status == 0x21
hde: timeout waiting for DMA
hde: status timeout: status=0xd8 { Busy }
ide2: reset phy, status=0x00000113,siimage_reset
hde: drive not ready for command
ide2: reset timed-out, statux 0xd8 { Busy }
hde: status timeout: status=0xd8 { Busy }
ide2: reset phy, status=0x00000113,siimage_reset
hde: drive not ready for command
ide2: reset timed-out, statux 0xd8 { Busy }
end_request: I/O error, dev 21:01 (hde), sector (something)
end_request: I/O error, dev 21:01 (hde), sector (something)
journal-601, buffer write failed
kernel BUG at prints.c:334!
invalid operand: 0000
(and then some stack information and call trace information - if this
is useful, I can type it in too, but it looks essentially like reiserfs
complaining that the disk isn't working)
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2003-06-04 17:10 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-29 14:32 siimage driver status Wm. Josiah Erikson
2003-05-29 13:54 ` Alan Cox
2003-05-29 15:00 ` Wm. Josiah Erikson
2003-05-29 14:56 ` Alan Cox
2003-05-29 19:32 ` Wm. Josiah Erikson
2003-05-29 22:26 ` Gutko
2003-06-03 7:17 ` Marco Tedaldi
2003-06-03 12:43 ` Alan Cox
2003-06-03 14:11 ` Wm. Josiah Erikson
2003-06-03 13:49 ` Alan Cox
2003-06-03 15:07 ` Wm. Josiah Erikson
2003-06-03 15:13 ` Bob Johnson
2003-06-03 15:29 ` Wm. Josiah Erikson
2003-06-03 15:58 ` Bob Johnson
2003-06-03 14:45 ` Justin Cormack
2003-05-30 18:57 ` lk
2003-05-30 21:44 ` Bob Johnson
2003-05-29 15:00 ` lk
2003-05-31 9:34 Inigo Surguy
2003-06-04 17:23 Rob Browning
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).