* DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
@ 2001-07-25 1:25 Adam McKenna
2001-07-25 3:08 ` Rico Tudor
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Adam McKenna @ 2001-07-25 1:25 UTC (permalink / raw)
To: linux-kernel
I have a Penguin Computing 1U server with a ServerWorks OSB4 chipset. I'm
running Linux 2.4.6-xfs on it (although this happened with non-XFS 2.4.5 as
well).
When the system is booting, I get the following errors:
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
>From what I've been able to find on Google, there are several other people
with this problem; Has anyone come up with a solution? I have ServerWorks
OSB4 support compiled into the kernel, but this happens with or without it.
Full dmesg output:
Linux version 2.4.6-xfs (root@kahlua) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #2 SMP Wed Jul 25 01:04:17 PDT 2001
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
BIOS-e820: 00000000fec00000 - 00000000fec02000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
128MB HIGHMEM available.
Scan SMP from c0000000 for 1024 bytes.
Scan SMP from c009fc00 for 1024 bytes.
Scan SMP from c00f0000 for 65536 bytes.
found SMP MP-table at 000ff780
hm, page 000ff000 reserved twice.
hm, page 00100000 reserved twice.
hm, page 000f0000 reserved twice.
hm, page 000f1000 reserved twice.
On node 0 totalpages: 262144
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 32768 pages.
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: AMI Product ID: CNB20HE APIC at: 0xFEE00000
Processor #0 Pentium(tm) Pro APIC version 17
Floating point unit present.
Machine Exception supported.
64 bit compare & exchange supported.
Internal APIC present.
SEP present.
MTRR present.
PGE present.
MCA present.
CMOV present.
PAT present.
PSE present.
PSN present.
MMX present.
FXSR present.
XMM present.
Bootup CPU
Processor #1 Pentium(tm) Pro APIC version 17
Floating point unit present.
Machine Exception supported.
64 bit compare & exchange supported.
Internal APIC present.
SEP present.
MTRR present.
PGE present.
MCA present.
CMOV present.
PAT present.
PSE present.
PSN present.
MMX present.
FXSR present.
XMM present.
Bus #0 is PCI
Bus #1 is PCI
Bus #2 is PCI
Bus #3 is ISA
I/O APIC #4 Version 17 at 0xFEC00000.
I/O APIC #5 Version 17 at 0xFEC01000.
Int: type 0, pol 3, trig 3, bus 1, IRQ 00, APIC ID 5, APIC INT 0e
Int: type 0, pol 3, trig 3, bus 0, IRQ 3c, APIC ID 4, APIC INT 0a
Int: type 0, pol 3, trig 3, bus 0, IRQ 18, APIC ID 5, APIC INT 0f
Int: type 0, pol 3, trig 3, bus 0, IRQ 10, APIC ID 5, APIC INT 0c
Int: type 3, pol 1, trig 1, bus 3, IRQ 00, APIC ID 4, APIC INT 00
Int: type 0, pol 1, trig 1, bus 3, IRQ 01, APIC ID 4, APIC INT 01
Int: type 0, pol 1, trig 1, bus 3, IRQ 00, APIC ID 4, APIC INT 02
Int: type 0, pol 1, trig 1, bus 3, IRQ 03, APIC ID 4, APIC INT 03
Int: type 0, pol 1, trig 1, bus 3, IRQ 04, APIC ID 4, APIC INT 04
Int: type 0, pol 1, trig 1, bus 3, IRQ 06, APIC ID 4, APIC INT 06
Int: type 0, pol 1, trig 1, bus 3, IRQ 07, APIC ID 4, APIC INT 07
Int: type 0, pol 1, trig 1, bus 3, IRQ 08, APIC ID 4, APIC INT 08
Int: type 0, pol 1, trig 1, bus 3, IRQ 0c, APIC ID 4, APIC INT 0c
Int: type 0, pol 1, trig 1, bus 3, IRQ 0d, APIC ID 4, APIC INT 0d
Int: type 0, pol 1, trig 1, bus 3, IRQ 0e, APIC ID 4, APIC INT 0e
Int: type 0, pol 1, trig 1, bus 3, IRQ 0f, APIC ID 4, APIC INT 0f
Lint: type 3, pol 1, trig 1, bus 3, IRQ 00, APIC ID ff, APIC LINT 00
Lint: type 1, pol 1, trig 1, bus 0, IRQ 00, APIC ID ff, APIC LINT 01
Processors: 2
mapped APIC to ffffe000 (fee00000)
mapped IOAPIC to ffffd000 (fec00000)
mapped IOAPIC to ffffc000 (fec01000)
Kernel command line: auto BOOT_IMAGE=Linux ro root=301 BOOT_FILE=/vmlinuz
Initializing CPU#0
Detected 866.303 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1730.15 BogoMIPS
Memory: 1028048k/1048576k available (1625k kernel code, 20140k reserved, 531k data, 200k init, 131072k highmem)
Dentry-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
CPU: Common caps: 0383fbff 00000000 00000000 00000000
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
CPU: Common caps: 0383fbff 00000000 00000000 00000000
CPU0: Intel Pentium III (Coppermine) stepping 0a
per-CPU timeslice cutoff: 730.81 usecs.
Getting VERSION: 40011
Getting VERSION: 40011
Getting ID: 0
Getting ID: f000000
Getting LVT0: 700
Getting LVT1: 400
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000004
ESR value after enabling vector: 00000000
CPU present map: 3
Booting processor 1/1 eip 2000
Setting warm reset code and vector.
1.
2.
3.
Asserting INIT.
Waiting for send to finish...
+Deasserting INIT.
Waiting for send to finish...
+#startup loops: 2.
Sending STARTUP #1.
After apic_write.
Initializing CPU#1
CPU#1 (phys ID: 1) waiting for CALLOUT
Startup point 1.
Waiting for send to finish...
+Sending STARTUP #2.
After apic_write.
Startup point 1.
Waiting for send to finish...
+After Startup.
Before Callout 1.
After Callout 1.
CALLIN, before setup_local_APIC().
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 1730.15 BogoMIPS
Stack at about c2119fbc
CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check reporting enabled on CPU#1.
CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
CPU: Common caps: 0383fbff 00000000 00000000 00000000
OK.
CPU1: Intel Pentium III (Coppermine) stepping 0a
CPU has booted.
Before bogomips.
Total of 2 processors activated (3460.30 BogoMIPS).
Before bogocount - setting activated=1.
Boot done.
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 4 ... ok.
...changing IO-APIC physical APIC ID to 5 ... ok.
Synchronizing Arb IDs.
init IO_APIC IRQs
IO-APIC (apicid-pin) 4-0, 4-5, 4-9, 4-11, 5-0, 5-1, 5-2, 5-3, 5-4, 5-5, 5-6, 5-7, 5-8, 5-9, 5-10, 5-11, 5-13 not connected.
..TIMER: vector=31 pin1=2 pin2=0
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found pin 0) ...works.
activating NMI Watchdog ... done.
number of MP IRQ sources: 16.
number of IO-APIC #4 registers: 16.
number of IO-APIC #5 registers: 16.
testing the IO APIC.......................
IO APIC #4......
.... register #00: 04000000
....... : physical APIC id: 04
.... register #01: 000F0011
....... : max redirection entries: 000F
....... : IO APIC version: 0011
.... register #02: 00000000
....... : arbitration: 00
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 003 03 0 0 0 0 0 1 1 31
01 003 03 0 0 0 0 0 1 1 39
02 000 00 1 0 0 0 0 0 0 00
03 003 03 0 0 0 0 0 1 1 41
04 003 03 0 0 0 0 0 1 1 49
05 000 00 1 0 0 0 0 0 0 00
06 003 03 0 0 0 0 0 1 1 51
07 003 03 0 0 0 0 0 1 1 59
08 003 03 0 0 0 0 0 1 1 61
09 000 00 1 0 0 0 0 0 0 00
0a 003 03 1 1 0 1 0 1 1 69
0b 000 00 1 0 0 0 0 0 0 00
0c 003 03 0 0 0 0 0 1 1 71
0d 003 03 0 0 0 0 0 1 1 79
0e 003 03 0 0 0 0 0 1 1 81
0f 003 03 0 0 0 0 0 1 1 89
IO APIC #5......
.... register #00: 05000000
....... : physical APIC id: 05
.... register #01: 000F0011
....... : max redirection entries: 000F
....... : IO APIC version: 0011
.... register #02: 07000000
....... : arbitration: 07
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 000 00 1 0 0 0 0 0 0 00
02 000 00 1 0 0 0 0 0 0 00
03 000 00 1 0 0 0 0 0 0 00
04 000 00 1 0 0 0 0 0 0 00
05 000 00 1 0 0 0 0 0 0 00
06 000 00 1 0 0 0 0 0 0 00
07 000 00 1 0 0 0 0 0 0 00
08 000 00 1 0 0 0 0 0 0 00
09 000 00 1 0 0 0 0 0 0 00
0a 000 00 1 0 0 0 0 0 0 00
0b 000 00 1 0 0 0 0 0 0 00
0c 003 03 1 1 0 1 0 1 1 91
0d 000 00 1 0 0 0 0 0 0 00
0e 003 03 1 1 0 1 0 1 1 99
0f 003 03 1 1 0 1 0 1 1 A1
IRQ to pin mappings:
IRQ0 -> 2
IRQ1 -> 1
IRQ3 -> 3
IRQ4 -> 4
IRQ6 -> 6
IRQ7 -> 7
IRQ8 -> 8
IRQ10 -> 10
IRQ12 -> 12
IRQ13 -> 13
IRQ14 -> 14
IRQ15 -> 15
IRQ28 -> 12
IRQ30 -> 14
IRQ31 -> 15
.................................... done.
calibrating APIC timer ...
..... CPU clock speed is 866.1198 MHz.
..... host bus clock speed is 133.2491 MHz.
cpu: 0, clocks: 1332491, slice: 444163
CPU0<T0:1332480,T1:888304,D:13,S:444163,C:1332491>
cpu: 1, clocks: 1332491, slice: 444163
CPU1<T0:1332480,T1:444144,D:10,S:444163,C:1332491>
checking TSC synchronization across CPUs: passed.
Setting commenced=1, go go go
PCI: PCI BIOS revision 2.10 entry at 0xfdbb1, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Discovered primary peer bus 02 [IRQ]
PCI: Using IRQ router ServerWorks [1166/0200] at 00:0f.0
querying PCI -> IRQ mapping bus:0, slot:4, pin:0.
PCI->APIC IRQ transform: (B0,I4,P0) -> 28
querying PCI -> IRQ mapping bus:0, slot:6, pin:0.
PCI->APIC IRQ transform: (B0,I6,P0) -> 31
querying PCI -> IRQ mapping bus:0, slot:15, pin:0.
PCI->APIC IRQ transform: (B0,I15,P0) -> 10
querying PCI -> IRQ mapping bus:1, slot:0, pin:0.
PCI->APIC IRQ transform: (B1,I0,P0) -> 30
PCI: Cannot allocate resource region 1 of device 00:00.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
allocated 32 pages and 32 bhs reserved for the highmem bounces
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05a (2001-03-20) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
block: queued sectors max/low 683117kB/552045kB, 2048 slots per queue
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ServerWorks OSB4: IDE controller on PCI bus 00 dev 79
ServerWorks OSB4: chipset revision 0
ServerWorks OSB4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
hda: QUANTUM FIREBALLP AS30.0, ATA DISK drive
hdb: QUANTUM FIREBALLP AS30.0, ATA DISK drive
hdc: SR242S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 58633344 sectors (30020 MB) w/1902KiB Cache, CHS=3649/255/63, UDMA(33)
hdb: 58633344 sectors (30020 MB) w/1902KiB Cache, CHS=3649/255/63, UDMA(33)
hdc: ATAPI 24X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
Partition check:
hda: hda1 hda2 hda3 hda4
hdb: hdb1 hdb2 hdb3
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:30:48:11:52:FE, IRQ 31.
Board assembly 000000-000, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
eth1: OEM i82557/i82558 10/100 Ethernet, 00:30:48:11:52:FD, IRQ 28.
Board assembly 000000-000, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus]
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
ds: no socket drivers loaded!
Start mounting filesystem: ide0(3,1)
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
Ending clean XFS mount for filesystem: ide0(3,1)
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 200k freed
Adding Swap: 2000084k swap-space (priority -1)
Start mounting filesystem: ide0(3,65)
Ending clean XFS mount for filesystem: ide0(3,65)
Start mounting filesystem: ide0(3,66)
hdb: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x50 { DriveReady SeekComplete }
Ending clean XFS mount for filesystem: ide0(3,66)
Start mounting filesystem: ide0(3,67)
hdb: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x50 { DriveReady SeekComplete }
Starting XFS recovery on filesystem: ide0(3,67) (dev: 3/67)
Ending XFS recovery on filesystem: ide0(3,67) (dev: 3/67)
Start mounting filesystem: ide0(3,3)
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
Ending clean XFS mount for filesystem: ide0(3,3)
eth0: 0 multicast blocks dropped.
Thanks,
--Adam
--
Adam McKenna <adam@flounder.net> | Help stop animal abuse at Petco!
http://flounder.net/publickey.html | http://www.mickaboofriends.org
GPG: 17A4 11F7 5E7E C2E7 08AA |
38B0 05D0 8BF7 2C6D 110A |
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-07-25 1:25 DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Adam McKenna
@ 2001-07-25 3:08 ` Rico Tudor
2001-07-26 16:11 ` Facing problem Dipak Biswas
2001-07-25 13:30 ` DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Alan Cox
2001-07-25 15:46 ` Larry Sendlosky
2 siblings, 1 reply; 14+ messages in thread
From: Rico Tudor @ 2001-07-25 3:08 UTC (permalink / raw)
To: Adam McKenna; +Cc: linux-kernel
ServerWorks OSB4 locks solid if I access both IDE channels, and either
one has DMA enabled. Current solutions: (i) abandon second channel,
(ii) use PIO, (iii) add Promise card, (iv) add 3ware card.
My machines use (i), (iii), and (iv). I didn't test two devices on the
same channel, e.g. /dev/hd[ab]
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-07-25 1:25 DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Adam McKenna
2001-07-25 3:08 ` Rico Tudor
@ 2001-07-25 13:30 ` Alan Cox
2001-11-13 7:46 ` Adam McKenna
2001-07-25 15:46 ` Larry Sendlosky
2 siblings, 1 reply; 14+ messages in thread
From: Alan Cox @ 2001-07-25 13:30 UTC (permalink / raw)
To: Adam McKenna; +Cc: linux-kernel
> >From what I've been able to find on Google, there are several other people
> with this problem; Has anyone come up with a solution? I have ServerWorks
> OSB4 support compiled into the kernel, but this happens with or without it.
The OSB4 support in Linus 2.4 tree is out of date. The chances are that is
not the cause of the DMA timeout - but do try the 2.4.6-ac5 tree
And no there is no 2.4.6-ac5-xfs tree I know of, if you need that you'll
have to merge stuff
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-07-25 1:25 DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Adam McKenna
2001-07-25 3:08 ` Rico Tudor
2001-07-25 13:30 ` DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Alan Cox
@ 2001-07-25 15:46 ` Larry Sendlosky
2 siblings, 0 replies; 14+ messages in thread
From: Larry Sendlosky @ 2001-07-25 15:46 UTC (permalink / raw)
To: Adam McKenna; +Cc: linux-kernel
We are convinced it's a problem with the ServerWorks LE
chipset. We also did similar tests on with SeverWorks HE chipset
and did not get DMA timeouts. To workaround the problem,
we drop the IDE drives into MWDMA2 mode. We've only
seen 1 DMA timeout since (as opposed to almost every boot).
We had someone put a bus analyzer on our system to watch the DMA
"transactions" on the bus.
Below is the description from the engineer who did
the bus traffic analysis: (there were also timing diagrams that I omitted)
The macroscopic symptom is an apparent lock-up and DMA timeout during
data transfers in *any* ULTRA DMA mode. (The problem does NOT happen in PIO
or MultiWord DMA modes.)
This happens during tests where extensive amounts of data is being read
from an IDE device. It may take several minutes, but generaly to my knowledge
happens within a half-hour.
Upon further inspection, (bus analisys) it appears as though during an
ultra-DMA data transfer, the drive will going into periods of bursting
data, then pausing, bursting, pausing, bursting, pausing, etc. until the end
of a transfer. (This is typical for all drives.) The problem appears to occur
during one of these cycles - when the data is ready - the drive asserts
/DMARQ, but the chipset never responds back (/HDMAREADY.) Thus, after
about an 8 second timeout the drive apparetly cancels the transaction via. an
IDLE IMMEDATE command.
It is notable that in this case - during the preceding "pause", it
appears as though both the PC and the drive coincedentaly deasert their DMAREADY
lines at the same time. This appears to be a reoccuring pattern for when
thelockup occurs. When the data is subsequently ready after this occurance,
the PC (chipset) never acknowledges it.
Adam McKenna wrote:
>
> I have a Penguin Computing 1U server with a ServerWorks OSB4 chipset. I'm
> running Linux 2.4.6-xfs on it (although this happened with non-XFS 2.4.5 as
> well).
>
> When the system is booting, I get the following errors:
>
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hda: timeout waiting for DMA
>
> >From what I've been able to find on Google, there are several other people
> with this problem; Has anyone come up with a solution? I have ServerWorks
> OSB4 support compiled into the kernel, but this happens with or without it.
>
> Full dmesg output:
>
> Linux version 2.4.6-xfs (root@kahlua) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #2 SMP Wed Jul 25 01:04:17 PDT 2001
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
> BIOS-e820: 00000000fec00000 - 00000000fec02000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> 128MB HIGHMEM available.
> Scan SMP from c0000000 for 1024 bytes.
> Scan SMP from c009fc00 for 1024 bytes.
> Scan SMP from c00f0000 for 65536 bytes.
> found SMP MP-table at 000ff780
> hm, page 000ff000 reserved twice.
> hm, page 00100000 reserved twice.
> hm, page 000f0000 reserved twice.
> hm, page 000f1000 reserved twice.
> On node 0 totalpages: 262144
> zone(0): 4096 pages.
> zone(1): 225280 pages.
> zone(2): 32768 pages.
> Intel MultiProcessor Specification v1.4
> Virtual Wire compatibility mode.
> OEM ID: AMI Product ID: CNB20HE APIC at: 0xFEE00000
> Processor #0 Pentium(tm) Pro APIC version 17
> Floating point unit present.
> Machine Exception supported.
> 64 bit compare & exchange supported.
> Internal APIC present.
> SEP present.
> MTRR present.
> PGE present.
> MCA present.
> CMOV present.
> PAT present.
> PSE present.
> PSN present.
> MMX present.
> FXSR present.
> XMM present.
> Bootup CPU
> Processor #1 Pentium(tm) Pro APIC version 17
> Floating point unit present.
> Machine Exception supported.
> 64 bit compare & exchange supported.
> Internal APIC present.
> SEP present.
> MTRR present.
> PGE present.
> MCA present.
> CMOV present.
> PAT present.
> PSE present.
> PSN present.
> MMX present.
> FXSR present.
> XMM present.
> Bus #0 is PCI
> Bus #1 is PCI
> Bus #2 is PCI
> Bus #3 is ISA
> I/O APIC #4 Version 17 at 0xFEC00000.
> I/O APIC #5 Version 17 at 0xFEC01000.
> Int: type 0, pol 3, trig 3, bus 1, IRQ 00, APIC ID 5, APIC INT 0e
> Int: type 0, pol 3, trig 3, bus 0, IRQ 3c, APIC ID 4, APIC INT 0a
> Int: type 0, pol 3, trig 3, bus 0, IRQ 18, APIC ID 5, APIC INT 0f
> Int: type 0, pol 3, trig 3, bus 0, IRQ 10, APIC ID 5, APIC INT 0c
> Int: type 3, pol 1, trig 1, bus 3, IRQ 00, APIC ID 4, APIC INT 00
> Int: type 0, pol 1, trig 1, bus 3, IRQ 01, APIC ID 4, APIC INT 01
> Int: type 0, pol 1, trig 1, bus 3, IRQ 00, APIC ID 4, APIC INT 02
> Int: type 0, pol 1, trig 1, bus 3, IRQ 03, APIC ID 4, APIC INT 03
> Int: type 0, pol 1, trig 1, bus 3, IRQ 04, APIC ID 4, APIC INT 04
> Int: type 0, pol 1, trig 1, bus 3, IRQ 06, APIC ID 4, APIC INT 06
> Int: type 0, pol 1, trig 1, bus 3, IRQ 07, APIC ID 4, APIC INT 07
> Int: type 0, pol 1, trig 1, bus 3, IRQ 08, APIC ID 4, APIC INT 08
> Int: type 0, pol 1, trig 1, bus 3, IRQ 0c, APIC ID 4, APIC INT 0c
> Int: type 0, pol 1, trig 1, bus 3, IRQ 0d, APIC ID 4, APIC INT 0d
> Int: type 0, pol 1, trig 1, bus 3, IRQ 0e, APIC ID 4, APIC INT 0e
> Int: type 0, pol 1, trig 1, bus 3, IRQ 0f, APIC ID 4, APIC INT 0f
> Lint: type 3, pol 1, trig 1, bus 3, IRQ 00, APIC ID ff, APIC LINT 00
> Lint: type 1, pol 1, trig 1, bus 0, IRQ 00, APIC ID ff, APIC LINT 01
> Processors: 2
> mapped APIC to ffffe000 (fee00000)
> mapped IOAPIC to ffffd000 (fec00000)
> mapped IOAPIC to ffffc000 (fec01000)
> Kernel command line: auto BOOT_IMAGE=Linux ro root=301 BOOT_FILE=/vmlinuz
> Initializing CPU#0
> Detected 866.303 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 1730.15 BogoMIPS
> Memory: 1028048k/1048576k available (1625k kernel code, 20140k reserved, 531k data, 200k init, 131072k highmem)
> Dentry-cache hash table entries: 131072 (order: 8, 1048576 bytes)
> Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
> Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
> Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
> CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 256K
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
> CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
> CPU: Common caps: 0383fbff 00000000 00000000 00000000
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
> mtrr: detected mtrr type: Intel
> CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 256K
> Intel machine check reporting enabled on CPU#0.
> CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
> CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
> CPU: Common caps: 0383fbff 00000000 00000000 00000000
> CPU0: Intel Pentium III (Coppermine) stepping 0a
> per-CPU timeslice cutoff: 730.81 usecs.
> Getting VERSION: 40011
> Getting VERSION: 40011
> Getting ID: 0
> Getting ID: f000000
> Getting LVT0: 700
> Getting LVT1: 400
> enabled ExtINT on CPU#0
> ESR value before enabling vector: 00000004
> ESR value after enabling vector: 00000000
> CPU present map: 3
> Booting processor 1/1 eip 2000
> Setting warm reset code and vector.
> 1.
> 2.
> 3.
> Asserting INIT.
> Waiting for send to finish...
> +Deasserting INIT.
> Waiting for send to finish...
> +#startup loops: 2.
> Sending STARTUP #1.
> After apic_write.
> Initializing CPU#1
> CPU#1 (phys ID: 1) waiting for CALLOUT
> Startup point 1.
> Waiting for send to finish...
> +Sending STARTUP #2.
> After apic_write.
> Startup point 1.
> Waiting for send to finish...
> +After Startup.
> Before Callout 1.
> After Callout 1.
> CALLIN, before setup_local_APIC().
> masked ExtINT on CPU#1
> ESR value before enabling vector: 00000000
> ESR value after enabling vector: 00000000
> Calibrating delay loop... 1730.15 BogoMIPS
> Stack at about c2119fbc
> CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 256K
> Intel machine check reporting enabled on CPU#1.
> CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
> CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
> CPU: Common caps: 0383fbff 00000000 00000000 00000000
> OK.
> CPU1: Intel Pentium III (Coppermine) stepping 0a
> CPU has booted.
> Before bogomips.
> Total of 2 processors activated (3460.30 BogoMIPS).
> Before bogocount - setting activated=1.
> Boot done.
> ENABLING IO-APIC IRQs
> ...changing IO-APIC physical APIC ID to 4 ... ok.
> ...changing IO-APIC physical APIC ID to 5 ... ok.
> Synchronizing Arb IDs.
> init IO_APIC IRQs
> IO-APIC (apicid-pin) 4-0, 4-5, 4-9, 4-11, 5-0, 5-1, 5-2, 5-3, 5-4, 5-5, 5-6, 5-7, 5-8, 5-9, 5-10, 5-11, 5-13 not connected.
> ..TIMER: vector=31 pin1=2 pin2=0
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> ...trying to set up timer (IRQ0) through the 8259A ...
> ..... (found pin 0) ...works.
> activating NMI Watchdog ... done.
> number of MP IRQ sources: 16.
> number of IO-APIC #4 registers: 16.
> number of IO-APIC #5 registers: 16.
> testing the IO APIC.......................
>
> IO APIC #4......
> .... register #00: 04000000
> ....... : physical APIC id: 04
> .... register #01: 000F0011
> ....... : max redirection entries: 000F
> ....... : IO APIC version: 0011
> .... register #02: 00000000
> ....... : arbitration: 00
> .... IRQ redirection table:
> NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> 00 003 03 0 0 0 0 0 1 1 31
> 01 003 03 0 0 0 0 0 1 1 39
> 02 000 00 1 0 0 0 0 0 0 00
> 03 003 03 0 0 0 0 0 1 1 41
> 04 003 03 0 0 0 0 0 1 1 49
> 05 000 00 1 0 0 0 0 0 0 00
> 06 003 03 0 0 0 0 0 1 1 51
> 07 003 03 0 0 0 0 0 1 1 59
> 08 003 03 0 0 0 0 0 1 1 61
> 09 000 00 1 0 0 0 0 0 0 00
> 0a 003 03 1 1 0 1 0 1 1 69
> 0b 000 00 1 0 0 0 0 0 0 00
> 0c 003 03 0 0 0 0 0 1 1 71
> 0d 003 03 0 0 0 0 0 1 1 79
> 0e 003 03 0 0 0 0 0 1 1 81
> 0f 003 03 0 0 0 0 0 1 1 89
>
> IO APIC #5......
> .... register #00: 05000000
> ....... : physical APIC id: 05
> .... register #01: 000F0011
> ....... : max redirection entries: 000F
> ....... : IO APIC version: 0011
> .... register #02: 07000000
> ....... : arbitration: 07
> .... IRQ redirection table:
> NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> 00 000 00 1 0 0 0 0 0 0 00
> 01 000 00 1 0 0 0 0 0 0 00
> 02 000 00 1 0 0 0 0 0 0 00
> 03 000 00 1 0 0 0 0 0 0 00
> 04 000 00 1 0 0 0 0 0 0 00
> 05 000 00 1 0 0 0 0 0 0 00
> 06 000 00 1 0 0 0 0 0 0 00
> 07 000 00 1 0 0 0 0 0 0 00
> 08 000 00 1 0 0 0 0 0 0 00
> 09 000 00 1 0 0 0 0 0 0 00
> 0a 000 00 1 0 0 0 0 0 0 00
> 0b 000 00 1 0 0 0 0 0 0 00
> 0c 003 03 1 1 0 1 0 1 1 91
> 0d 000 00 1 0 0 0 0 0 0 00
> 0e 003 03 1 1 0 1 0 1 1 99
> 0f 003 03 1 1 0 1 0 1 1 A1
> IRQ to pin mappings:
> IRQ0 -> 2
> IRQ1 -> 1
> IRQ3 -> 3
> IRQ4 -> 4
> IRQ6 -> 6
> IRQ7 -> 7
> IRQ8 -> 8
> IRQ10 -> 10
> IRQ12 -> 12
> IRQ13 -> 13
> IRQ14 -> 14
> IRQ15 -> 15
> IRQ28 -> 12
> IRQ30 -> 14
> IRQ31 -> 15
> .................................... done.
> calibrating APIC timer ...
> ..... CPU clock speed is 866.1198 MHz.
> ..... host bus clock speed is 133.2491 MHz.
> cpu: 0, clocks: 1332491, slice: 444163
> CPU0<T0:1332480,T1:888304,D:13,S:444163,C:1332491>
> cpu: 1, clocks: 1332491, slice: 444163
> CPU1<T0:1332480,T1:444144,D:10,S:444163,C:1332491>
> checking TSC synchronization across CPUs: passed.
> Setting commenced=1, go go go
> PCI: PCI BIOS revision 2.10 entry at 0xfdbb1, last bus=2
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Discovered primary peer bus 02 [IRQ]
> PCI: Using IRQ router ServerWorks [1166/0200] at 00:0f.0
> querying PCI -> IRQ mapping bus:0, slot:4, pin:0.
> PCI->APIC IRQ transform: (B0,I4,P0) -> 28
> querying PCI -> IRQ mapping bus:0, slot:6, pin:0.
> PCI->APIC IRQ transform: (B0,I6,P0) -> 31
> querying PCI -> IRQ mapping bus:0, slot:15, pin:0.
> PCI->APIC IRQ transform: (B0,I15,P0) -> 10
> querying PCI -> IRQ mapping bus:1, slot:0, pin:0.
> PCI->APIC IRQ transform: (B1,I0,P0) -> 30
> PCI: Cannot allocate resource region 1 of device 00:00.0
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Starting kswapd v1.8
> allocated 32 pages and 32 bhs reserved for the highmem bounces
> Detected PS/2 Mouse Port.
> pty: 256 Unix98 ptys configured
> Serial driver version 5.05a (2001-03-20) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> block: queued sectors max/low 683117kB/552045kB, 2048 slots per queue
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> ServerWorks OSB4: IDE controller on PCI bus 00 dev 79
> ServerWorks OSB4: chipset revision 0
> ServerWorks OSB4: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
> hda: QUANTUM FIREBALLP AS30.0, ATA DISK drive
> hdb: QUANTUM FIREBALLP AS30.0, ATA DISK drive
> hdc: SR242S, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 58633344 sectors (30020 MB) w/1902KiB Cache, CHS=3649/255/63, UDMA(33)
> hdb: 58633344 sectors (30020 MB) w/1902KiB Cache, CHS=3649/255/63, UDMA(33)
> hdc: ATAPI 24X CD-ROM drive, 128kB Cache, DMA
> Uniform CD-ROM driver Revision: 3.12
> Partition check:
> hda: hda1 hda2 hda3 hda4
> hdb: hdb1 hdb2 hdb3
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a National Semiconductor PC87306
> eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:30:48:11:52:FE, IRQ 31.
> Board assembly 000000-000, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0x04f4518b).
> eth1: OEM i82557/i82558 10/100 Ethernet, 00:30:48:11:52:FD, IRQ 28.
> Board assembly 000000-000, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0x04f4518b).
> SCSI subsystem driver Revision: 1.00
> request_module[scsi_hostadapter]: Root fs not mounted
> Linux Kernel Card Services 3.1.22
> options: [pci] [cardbus]
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 8192 buckets, 64Kbytes
> TCP: Hash tables configured (established 262144 bind 65536)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> ds: no socket drivers loaded!
> Start mounting filesystem: ide0(3,1)
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> Ending clean XFS mount for filesystem: ide0(3,1)
> VFS: Mounted root (xfs filesystem) readonly.
> Freeing unused kernel memory: 200k freed
> Adding Swap: 2000084k swap-space (priority -1)
> Start mounting filesystem: ide0(3,65)
> Ending clean XFS mount for filesystem: ide0(3,65)
> Start mounting filesystem: ide0(3,66)
> hdb: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x50 { DriveReady SeekComplete }
> Ending clean XFS mount for filesystem: ide0(3,66)
> Start mounting filesystem: ide0(3,67)
> hdb: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x50 { DriveReady SeekComplete }
> Starting XFS recovery on filesystem: ide0(3,67) (dev: 3/67)
> Ending XFS recovery on filesystem: ide0(3,67) (dev: 3/67)
> Start mounting filesystem: ide0(3,3)
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> Ending clean XFS mount for filesystem: ide0(3,3)
> eth0: 0 multicast blocks dropped.
>
> Thanks,
>
> --Adam
>
> --
> Adam McKenna <adam@flounder.net> | Help stop animal abuse at Petco!
> http://flounder.net/publickey.html | http://www.mickaboofriends.org
> GPG: 17A4 11F7 5E7E C2E7 08AA |
> 38B0 05D0 8BF7 2C6D 110A |
> -
> 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/
--
--------------------------------------------------------------------------
Larry Sendlosky larry.sendlosky@storigen.com
Storigen Systems (978) 323-4454 x261
--------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 14+ messages in thread
* Facing problem
2001-07-25 3:08 ` Rico Tudor
@ 2001-07-26 16:11 ` Dipak Biswas
2001-07-26 17:28 ` Fwd: " Dipak Biswas
0 siblings, 1 reply; 14+ messages in thread
From: Dipak Biswas @ 2001-07-26 16:11 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
Hi all,
I'm facing problem to bring up 2.4.5 kernel properly. The eth0 is not
coming up and lockd is failing because of lockdsvc function not found. I'm
attaching part of /var/log/boot.log file for your info.
Thanks in advance,
Dipak
[-- Attachment #2: bootlog.txt --]
[-- Type: text/plain, Size: 4517 bytes --]
Jul 26 09:57:56 mozart syslog: syslogd startup succeeded
Jul 26 09:57:56 mozart syslog: klogd startup succeeded
Jul 26 09:57:56 mozart identd: identd startup succeeded
Jul 26 09:57:57 mozart atd: atd startup succeeded
Jul 26 09:57:57 mozart crond: crond startup succeeded
Jul 26 09:57:57 mozart rc: Starting pcmcia succeeded
Jul 26 09:57:45 mozart rc.sysinit: Mounting proc filesystem succeeded
Jul 26 09:57:45 mozart sysctl: net.ipv4.ip_forward = 0
Jul 26 09:57:45 mozart sysctl: net.ipv4.conf.all.rp_filter = 1
Jul 26 09:57:45 mozart sysctl: kernel.sysrq = 0
Jul 26 09:57:45 mozart sysctl: error: 'net.ipv4.ip_always_defrag' is an unknown key
Jul 26 09:57:45 mozart rc.sysinit: Configuring kernel parameters succeeded
Jul 26 09:57:45 mozart date: Thu Jul 26 09:57:45 EDT 2001
Jul 26 09:57:45 mozart rc.sysinit: Setting clock : Thu Jul 26 09:57:45 EDT 2001 succeeded
Jul 26 09:57:45 mozart rc.sysinit: Activating swap partitions succeeded
Jul 26 09:57:45 mozart rc.sysinit: Setting hostname mozart succeeded
Jul 26 09:57:45 mozart fsck: /dev/hda8: clean, 38953/218176 files, 291624/435755 blocks
Jul 26 09:57:45 mozart rc.sysinit: Checking root filesystem succeeded
Jul 26 09:57:45 mozart rc.sysinit: Remounting root filesystem in read-write mode succeeded
Jul 26 09:57:45 mozart rc.sysinit: Finding module dependencies succeeded
Jul 26 09:57:45 mozart aumix-minimal: aumix: error opening mixer
Jul 26 09:57:45 mozart rc.sysinit: Loading mixer settings failed
Jul 26 09:57:45 mozart fsck: /dev/hda1: clean, 31/6024 files, 9908/24066 blocks
Jul 26 09:57:45 mozart fsck: /dev/hda6: clean, 2123/641280 files, 264924/1281175 blocks
Jul 26 09:57:45 mozart fsck: /dev/hda7: clean, 319/256512 files, 8082/512064 blocks
Jul 26 09:57:45 mozart fsck: /dev/hda5: clean, 144942/1310720 files, 876420/2616579 blocks
Jul 26 09:57:45 mozart rc.sysinit: Checking filesystems succeeded
Jul 26 09:57:45 mozart rc.sysinit: Mounting local filesystems succeeded
Jul 26 09:57:45 mozart rc.sysinit: Turning on user and group quotas for local filesystems succeeded
Jul 26 09:57:58 mozart inet: inetd startup succeeded
Jul 26 09:57:46 mozart rc.sysinit: Enabling swap space succeeded
Jul 26 09:57:55 mozart kudzu: succeeded
Jul 26 09:57:55 mozart sysctl: net.ipv4.ip_forward = 0
Jul 26 09:57:55 mozart sysctl: net.ipv4.conf.all.rp_filter = 1
Jul 26 09:57:55 mozart sysctl: kernel.sysrq = 0
Jul 26 09:57:55 mozart sysctl: error: 'net.ipv4.ip_always_defrag' is an unknown key
Jul 26 09:57:55 mozart network: Setting network parameters succeeded
Jul 26 09:57:55 mozart network: Bringing up interface lo succeeded
Jul 26 09:57:55 mozart ifup: Delaying eth0 initialization.
Jul 26 09:57:55 mozart network: Bringing up interface eth0 failed
Jul 26 09:57:55 mozart portmap: portmap startup succeeded
Jul 26 09:57:55 mozart rpc.lockd: lockdsvc: Function not implemented
Jul 26 09:57:55 mozart nfslock: rpc.lockd startup failed
Jul 26 09:57:56 mozart nfslock: rpc.statd startup succeeded
Jul 26 09:57:56 mozart apmd: apmd startup succeeded
Jul 26 09:57:56 mozart random: Initializing random number generator succeeded
Jul 26 09:57:58 mozart lpd: lpd startup succeeded
Jul 26 09:57:56 mozart mount: mount: RPC: Unable to send; errno = Network is unreachable
Jul 26 09:57:56 mozart mount: mount: RPC: Unable to send; errno = Network is unreachable
Jul 26 09:57:58 mozart keytable: Loading keymap:
Jul 26 09:57:56 mozart netfs: Mounting NFS filesystems failed
Jul 26 09:57:56 mozart netfs: Mounting other filesystems succeeded
Jul 26 09:57:58 mozart keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Jul 26 09:57:58 mozart keytable: Loading system font:
Jul 26 09:57:58 mozart rc: Starting keytable succeeded
Jul 26 09:57:58 mozart gpm: gpm startup succeeded
Jul 26 09:57:59 mozart httpd: [Thu Jul 26 09:57:59 2001] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Jul 26 09:57:59 mozart httpd:
Jul 26 09:57:59 mozart httpd: httpd startup succeeded
Jul 26 09:58:23 mozart tomcat: Using classpath: /var/tomcat/lib/ant.jar:/var/tomcat/lib/jasper.jar:/var/tomcat/lib/jaxp.jar:/var/tomcat/lib/parser.jar:/var/tomcat/lib/servlet.jar:/var/tomcat/lib/test:/var/tomcat/lib/webserver.jar:/usr/java/jdk1.3.0_02/lib/tools.jar
Jul 26 09:58:23 mozart tomcat: tomcat startup succeeded
Jul 26 09:58:25 mozart xfs: xfs startup succeeded
Jul 26 09:58:26 mozart linuxconf: Linuxconf final setup
Jul 26 09:58:28 mozart rc: Starting linuxconf succeeded
^ permalink raw reply [flat|nested] 14+ messages in thread
* Fwd: Facing problem
2001-07-26 16:11 ` Facing problem Dipak Biswas
@ 2001-07-26 17:28 ` Dipak Biswas
0 siblings, 0 replies; 14+ messages in thread
From: Dipak Biswas @ 2001-07-26 17:28 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
Hi all,
I'm facing problem to bring up 2.4.5 kernel properly. The eth0 is not
coming up and lockd is failing because of lockdsvc function not found.
I've attached part of /var/log/boot.log file for your info. The problematic
parts are identified with "^^^^^^^^" and my queries are marked with
">>>>>>>>>".
Please suggest.
Thanks in advance,
Dipak
[-- Attachment #2: bootlog.txt --]
[-- Type: text/plain, Size: 5232 bytes --]
Jul 26 09:57:56 mozart syslog: syslogd startup succeeded
Jul 26 09:57:56 mozart syslog: klogd startup succeeded
Jul 26 09:57:56 mozart identd: identd startup succeeded
Jul 26 09:57:57 mozart atd: atd startup succeeded
Jul 26 09:57:57 mozart crond: crond startup succeeded
Jul 26 09:57:57 mozart rc: Starting pcmcia succeeded
Jul 26 09:57:45 mozart rc.sysinit: Mounting proc filesystem succeeded
Jul 26 09:57:45 mozart sysctl: net.ipv4.ip_forward = 0
Jul 26 09:57:45 mozart sysctl: net.ipv4.conf.all.rp_filter = 1
Jul 26 09:57:45 mozart sysctl: kernel.sysrq = 0
Jul 26 09:57:45 mozart sysctl: error: 'net.ipv4.ip_always_defrag' is an unknown key
^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>>>> There is no IP Masquerading code existing in the 2.4.5 kernel
release.
Jul 26 09:57:45 mozart rc.sysinit: Configuring kernel parameters succeeded
Jul 26 09:57:45 mozart date: Thu Jul 26 09:57:45 EDT 2001
Jul 26 09:57:45 mozart rc.sysinit: Setting clock : Thu Jul 26 09:57:45 EDT 2001 succeeded
Jul 26 09:57:45 mozart rc.sysinit: Activating swap partitions succeeded
Jul 26 09:57:45 mozart rc.sysinit: Setting hostname mozart succeeded
Jul 26 09:57:45 mozart fsck: /dev/hda8: clean, 38953/218176 files, 291624/435755 blocks
Jul 26 09:57:45 mozart rc.sysinit: Checking root filesystem succeeded
Jul 26 09:57:45 mozart rc.sysinit: Remounting root filesystem in read-write mode succeeded
Jul 26 09:57:45 mozart rc.sysinit: Finding module dependencies succeeded
Jul 26 09:57:45 mozart aumix-minimal: aumix: error opening mixer
^^^^^^
>>>>>>>>>>>> What could be the problem. Sound configuration not well??
Jul 26 09:57:45 mozart rc.sysinit: Loading mixer settings failed
Jul 26 09:57:45 mozart fsck: /dev/hda1: clean, 31/6024 files, 9908/24066 blocks
Jul 26 09:57:45 mozart fsck: /dev/hda6: clean, 2123/641280 files, 264924/1281175 blocks
Jul 26 09:57:45 mozart fsck: /dev/hda7: clean, 319/256512 files, 8082/512064 blocks
Jul 26 09:57:45 mozart fsck: /dev/hda5: clean, 144942/1310720 files, 876420/2616579 blocks
Jul 26 09:57:45 mozart rc.sysinit: Checking filesystems succeeded
Jul 26 09:57:45 mozart rc.sysinit: Mounting local filesystems succeeded
Jul 26 09:57:45 mozart rc.sysinit: Turning on user and group quotas for local filesystems succeeded
Jul 26 09:57:58 mozart inet: inetd startup succeeded
Jul 26 09:57:46 mozart rc.sysinit: Enabling swap space succeeded
Jul 26 09:57:55 mozart kudzu: succeeded
Jul 26 09:57:55 mozart sysctl: net.ipv4.ip_forward = 0
Jul 26 09:57:55 mozart sysctl: net.ipv4.conf.all.rp_filter = 1
Jul 26 09:57:55 mozart sysctl: kernel.sysrq = 0
Jul 26 09:57:55 mozart sysctl: error: 'net.ipv4.ip_always_defrag' is an unknown
key
>>>>>>>>>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 26 09:57:55 mozart network: Setting network parameters succeeded
Jul 26 09:57:55 mozart network: Bringing up interface lo succeeded
Jul 26 09:57:55 mozart ifup: Delaying eth0 initialization.
Jul 26 09:57:55 mozart network: Bringing up interface eth0 failed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>>>>>>>> I think because of previous sysctl error, eth0 init failed and
network connection couldn't come up.
Jul 26 09:57:55 mozart portmap: portmap startup succeeded
Jul 26 09:57:55 mozart rpc.lockd: lockdsvc: Function not implemented
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 26 09:57:55 mozart nfslock: rpc.lockd startup failed
^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>>>>>>>> I have compiled LOCKD as module. Should I make it built-in??
Jul 26 09:57:56 mozart nfslock: rpc.statd startup succeeded
Jul 26 09:57:56 mozart apmd: apmd startup succeeded
Jul 26 09:57:56 mozart random: Initializing random number generator succeeded
Jul 26 09:57:58 mozart lpd: lpd startup succeeded
Jul 26 09:57:56 mozart mount: mount: RPC: Unable to send; errno = Network is unreachable
Jul 26 09:57:56 mozart mount: mount: RPC: Unable to send; errno = Network is unreachable
Jul 26 09:57:58 mozart keytable: Loading keymap:
Jul 26 09:57:56 mozart netfs: Mounting NFS filesystems failed
Jul 26 09:57:56 mozart netfs: Mounting other filesystems succeeded
Jul 26 09:57:58 mozart keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Jul 26 09:57:58 mozart keytable: Loading system font:
Jul 26 09:57:58 mozart rc: Starting keytable succeeded
Jul 26 09:57:58 mozart gpm: gpm startup succeeded
Jul 26 09:57:59 mozart httpd: [Thu Jul 26 09:57:59 2001] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Jul 26 09:57:59 mozart httpd:
Jul 26 09:57:59 mozart httpd: httpd startup succeeded
Jul 26 09:58:23 mozart tomcat: Using classpath: /var/tomcat/lib/ant.jar:/var/tomcat/lib/jasper.jar:/var/tomcat/lib/jaxp.jar:/var/tomcat/lib/parser.jar:/var/tomcat/lib/servlet.jar:/var/tomcat/lib/test:/var/tomcat/lib/webserver.jar:/usr/java/jdk1.3.0_02/lib/tools.jar
Jul 26 09:58:23 mozart tomcat: tomcat startup succeeded
Jul 26 09:58:25 mozart xfs: xfs startup succeeded
Jul 26 09:58:26 mozart linuxconf: Linuxconf final setup
Jul 26 09:58:28 mozart rc: Starting linuxconf succeeded
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-07-25 13:30 ` DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Alan Cox
@ 2001-11-13 7:46 ` Adam McKenna
2001-11-13 9:51 ` Alan Cox
0 siblings, 1 reply; 14+ messages in thread
From: Adam McKenna @ 2001-11-13 7:46 UTC (permalink / raw)
To: linux-kernel
On Wed, Jul 25, 2001 at 02:30:20PM +0100, Alan Cox wrote:
> > >From what I've been able to find on Google, there are several other people
> > with this problem; Has anyone come up with a solution? I have ServerWorks
> > OSB4 support compiled into the kernel, but this happens with or without it.
>
> The OSB4 support in Linus 2.4 tree is out of date. The chances are that is
> not the cause of the DMA timeout - but do try the 2.4.6-ac5 tree
>
> And no there is no 2.4.6-ac5-xfs tree I know of, if you need that you'll
> have to merge stuff
Apologies for the followup to the ancient post, but I've looked at the
differences between the serverworks.c in the current 2.4.14 kernel and the
most recent -ac patch, and there are less than 30 lines changed. Does this
mean that the OSB4 support in the Linus kernel is now up to date?
I ask because I'm still having major problems with the OSB4 chipset on
2.4.14. I've had to disable DMA completely on my boxes to avoid IDE errors
and fs corruption. Does anyone know of a patch that addresses the issues
with this chipset?
--Adam
--
Adam McKenna <adam@flounder.net> | GPG: 17A4 11F7 5E7E C2E7 08AA
http://flounder.net/publickey.html | 38B0 05D0 8BF7 2C6D 110A
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-11-13 7:46 ` Adam McKenna
@ 2001-11-13 9:51 ` Alan Cox
2001-11-13 10:30 ` Adam McKenna
0 siblings, 1 reply; 14+ messages in thread
From: Alan Cox @ 2001-11-13 9:51 UTC (permalink / raw)
To: Adam McKenna; +Cc: linux-kernel
> I ask because I'm still having major problems with the OSB4 chipset on
> 2.4.14. I've had to disable DMA completely on my boxes to avoid IDE errors
> and fs corruption. Does anyone know of a patch that addresses the issues
> with this chipset?
No. I spent some time digging into this problem with both Serverworks and
Red Hat customers. With certain disks, certain OSB4 revisions and UDMA
the controller occasionally gets "stuck", the next DMA it issues starts
by reissuing the last 4 bytes of the previous request and the entire thing
goes totally to crap.
The -ac tree will detect this case and panic and hang the machine solid to
avoid actual disk corruption. The real fix appears to be "dont do UDMA on
the OSB4". The CSB5 seems fine.
Alan
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-11-13 9:51 ` Alan Cox
@ 2001-11-13 10:30 ` Adam McKenna
2001-11-13 11:04 ` Alan Cox
0 siblings, 1 reply; 14+ messages in thread
From: Adam McKenna @ 2001-11-13 10:30 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-kernel
On Tue, Nov 13, 2001 at 09:51:21AM +0000, Alan Cox wrote:
> > I ask because I'm still having major problems with the OSB4 chipset on
> > 2.4.14. I've had to disable DMA completely on my boxes to avoid IDE errors
> > and fs corruption. Does anyone know of a patch that addresses the issues
> > with this chipset?
>
> No. I spent some time digging into this problem with both Serverworks and
> Red Hat customers. With certain disks, certain OSB4 revisions and UDMA
> the controller occasionally gets "stuck", the next DMA it issues starts
> by reissuing the last 4 bytes of the previous request and the entire thing
> goes totally to crap.
>
> The -ac tree will detect this case and panic and hang the machine solid to
> avoid actual disk corruption. The real fix appears to be "dont do UDMA on
> the OSB4". The CSB5 seems fine.
I am having problems with both UDMA and Multiword DMA. The problem doesn't
go away unless I disable CONFIG_IDEDMA_PCI_AUTO.
I don't know if there is actual FS corruption with MWord DMA, but there is
definitely a "hang" for a few seconds accompanied by a DMA error.
--Adam
--
Adam McKenna <adam@flounder.net> | GPG: 17A4 11F7 5E7E C2E7 08AA
http://flounder.net/publickey.html | 38B0 05D0 8BF7 2C6D 110A
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-11-13 10:30 ` Adam McKenna
@ 2001-11-13 11:04 ` Alan Cox
2001-11-27 8:25 ` Adam McKenna
0 siblings, 1 reply; 14+ messages in thread
From: Alan Cox @ 2001-11-13 11:04 UTC (permalink / raw)
To: Adam McKenna; +Cc: Alan Cox, linux-kernel
> I am having problems with both UDMA and Multiword DMA. The problem doesn't
> go away unless I disable CONFIG_IDEDMA_PCI_AUTO.
>
> I don't know if there is actual FS corruption with MWord DMA, but there is
> definitely a "hang" for a few seconds accompanied by a DMA error.
I've no other reports from MWDMA other than the usual "CDROM that doesnt
handle DMA" things
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-11-13 11:04 ` Alan Cox
@ 2001-11-27 8:25 ` Adam McKenna
0 siblings, 0 replies; 14+ messages in thread
From: Adam McKenna @ 2001-11-27 8:25 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-kernel
On Tue, Nov 13, 2001 at 11:04:57AM +0000, Alan Cox wrote:
> > I am having problems with both UDMA and Multiword DMA. The problem doesn't
> > go away unless I disable CONFIG_IDEDMA_PCI_AUTO.
> >
> > I don't know if there is actual FS corruption with MWord DMA, but there is
> > definitely a "hang" for a few seconds accompanied by a DMA error.
>
> I've no other reports from MWDMA other than the usual "CDROM that doesnt
> handle DMA" things
ops01:~# hdparm -Ii /dev/hda
/dev/hda:
Model=IBM-DTLA-307075, FwRev=TXAOA50C, SerialNo=YSDYSG5S166
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=3(DualPortCache), BuffSize=1916kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=150136560
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
Model=BI-MTDAL3-7070 5 , FwRev=XTOA5AC0,
SerialNo= Y DSSY5G1S66
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=3(DualPortCache), BuffSize=1916kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=150136560
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
ops01:~# hdparm -Ii /dev/hdb
/dev/hdb:
Model=Maxtor 4W100H6, FwRev=AAH01310, SerialNo=W6H2JCRC
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=3(DualPortCache), BuffSize=2048kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195711264
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
Model=aMtxro4 1W006H , FwRev=AA0H3101,
SerialNo=6W2HCJCR
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=3(DualPortCache), BuffSize=2048kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195711264
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
Here is a sample of the I/O errors:
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220172,
sector=1548794
end_request: I/O error, dev 03:05 (hda), sector 1548794
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220173,
sector=1548795
end_request: I/O error, dev 03:05 (hda), sector 1548795
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220174,
sector=1548796
end_request: I/O error, dev 03:05 (hda), sector 1548796
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220175,
sector=1548797
end_request: I/O error, dev 03:05 (hda), sector 1548797
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220176,
sector=1548798
end_request: I/O error, dev 03:05 (hda), sector 1548798
--Adam
--
Adam McKenna <adam@flounder.net> | GPG: 17A4 11F7 5E7E C2E7 08AA
http://flounder.net/publickey.html | 38B0 05D0 8BF7 2C6D 110A
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-07-29 21:50 Marvin Justice
2001-07-29 22:29 ` Ignacio Vazquez-Abrams
@ 2001-07-29 22:37 ` Alan Cox
1 sibling, 0 replies; 14+ messages in thread
From: Alan Cox @ 2001-07-29 22:37 UTC (permalink / raw)
To: mjustice; +Cc: linux-kernel
> On an unrelated topic the Serverworks LE chipset does not seem to be capable
> of handling 4GB of RAM, despite what the board vendors claim in their specs.
> When a 4th 1G stick is added the system gets really slow --- like maybe
> cacheing is disabled. We've seen this on both Tyan and SuperMicro boards. The
> HE chipset seems to be ok.
Check the mtrr setups. I've seen slow machines that are slow with 4Gb purely
because the bios misconfigured the memory type ranges
Alan
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
2001-07-29 21:50 Marvin Justice
@ 2001-07-29 22:29 ` Ignacio Vazquez-Abrams
2001-07-29 22:37 ` Alan Cox
1 sibling, 0 replies; 14+ messages in thread
From: Ignacio Vazquez-Abrams @ 2001-07-29 22:29 UTC (permalink / raw)
To: linux-kernel
On Sun, 29 Jul 2001, Marvin Justice wrote:
> On an unrelated topic the Serverworks LE chipset does not seem to be capable
> of handling 4GB of RAM, despite what the board vendors claim in their specs.
> When a 4th 1G stick is added the system gets really slow --- like maybe
> cacheing is disabled. We've seen this on both Tyan and SuperMicro boards. The
> HE chipset seems to be ok.
>
> Marvin Justice
I believe I remember a thread some time ago regarding the fact that
sometimes caching only works for a certain maximum amount of memory. It could
very well be that this is the case.
--
Ignacio Vazquez-Abrams <ignacio@openservices.net>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
@ 2001-07-29 21:50 Marvin Justice
2001-07-29 22:29 ` Ignacio Vazquez-Abrams
2001-07-29 22:37 ` Alan Cox
0 siblings, 2 replies; 14+ messages in thread
From: Marvin Justice @ 2001-07-29 21:50 UTC (permalink / raw)
To: linux-kernel
The latest RH kernel, 2.4.3-12, works ok for us if we recompile with the
explicit OSB4 support disabled and turn on UDMA2 manually with hdparm. The
system stands up to continuous pounding with Bonnie and benchmarks at
>20MB/sec for block reads (Tyan 2515). On the other hand, with the OSB4
support turned on we see DMA timeouts immediately. I've just started some
tests with OSB4 turned on in 2.4.7-ac2 and so far it seems ok.
On an unrelated topic the Serverworks LE chipset does not seem to be capable
of handling 4GB of RAM, despite what the board vendors claim in their specs.
When a 4th 1G stick is added the system gets really slow --- like maybe
cacheing is disabled. We've seen this on both Tyan and SuperMicro boards. The
HE chipset seems to be ok.
Marvin Justice
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2001-11-27 8:29 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-25 1:25 DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Adam McKenna
2001-07-25 3:08 ` Rico Tudor
2001-07-26 16:11 ` Facing problem Dipak Biswas
2001-07-26 17:28 ` Fwd: " Dipak Biswas
2001-07-25 13:30 ` DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Alan Cox
2001-11-13 7:46 ` Adam McKenna
2001-11-13 9:51 ` Alan Cox
2001-11-13 10:30 ` Adam McKenna
2001-11-13 11:04 ` Alan Cox
2001-11-27 8:25 ` Adam McKenna
2001-07-25 15:46 ` Larry Sendlosky
2001-07-29 21:50 Marvin Justice
2001-07-29 22:29 ` Ignacio Vazquez-Abrams
2001-07-29 22:37 ` Alan Cox
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).