Are you sure about bad memory?
Single-bit errors will be corrected; double-bit errors will generate NMI.
You can also find memory errors with an exerciser. Unfortunately,
trusty memtest86 bombs on my ServerWorks machine. Instead I use
http://www.qcc.sk.ca/~charlesc/software/memtester/
Try your test with "High Memory Support" disabled.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> Any chance you can try Alan Cox's patch against 2.4.5? It has a number
> of IO-APIC fixes.
>
patch-2.4.5-ac7.bz2 behaves the same as 2.4.4. Whatever is happening in
IO-APIC setup, USB interrupts actually arrive on IRQ 12. I can include
the usual pile of config info and boot messages, but th
I'm another victim of the IOAPIC routing USB IRQs to the nearest
black hole. Running 2.4.4, dual CPU, ServerWorks HE chipset. IRQ 16
was wrongly assumed for the OHCI controller. This generated the usual
sign of interrupt servicing gone AWOL:
usb_control/bulk_msg: timeout
usb-oh
I'm running stock 2.4.4 on five PCs with these features: ServerWorks
III HE, 2x 933MHz, 4GB RAM, dual-channel sym53c896 (FAST-40 WIDE) SCSI
controller. One PC has the new 181GB Seagate SCSI drive; another uses a
3ware RAID controller with 4x 40GB IDE (looks like a 160GB SCSI drive).
All is fine w
> The symptons were an ever more sluggish machine over time, memory usage
> looked pretty standard with the majority of memory assigned to cache... what
> would happen is that at terminal it would go into semi-freeze states of about
> 5-10 seconds (increasing with time), where no user interacti
Another problem area is ECC monitoring. I'm still waiting for info from
ServerWorks, and so is Dan Hollis. Alexander Stohr has even submitted
code to Jim Foster for approval, without evident effect. I have 18GB of
RAM divided among five ServerWorks boxes, so the matter is not academic.
-
To uns
Problem is not fixed with your patch. Debugging packet is
http://patrec.com./rico/vger/diag002.tar.bz2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.htm
> Hypthesis#2 The bounce buffer code in the Linus tree is known to be
> imperfect. Does 2.4.2ac3 do the same ?
>
No improvement. (In fact, 2.4.2ac3 breaks 3ware IDE RAID support.)
While operating this Thunder 2500 (Tyan motherboard, ServerWorks chipset)
is like walking on a minefield, the probl
Subject: 64GB option broken in 2.4.2
Problem:
The 64GB option causes processes to spin in the kernel.
Setup:
Linux 2.4.2
Slack current 20-feb-2001
ServerWorks III HE
4GB main memory
dual 933 Piii: SL47Q (stepping 3), SL4KK (stepping 6)
gcc
Thanks for the offer, but the basic problem remains: no docs.
As [EMAIL PROTECTED] noted, http://www.netroedge.com/~lm78/ shows some
cause for hope, but a medium-sized LART is still called for.
My interest in ServerWorks documentation is two-fold: first, to
expand chipset support in my ECC utilit
Does anyone have reference material for the ServerWorks northbridge?
I want to add their chipsets to my ECC-monitoring utility, but their
web site is little more than marketing drivel. Plus, they don't respond
to e-mail.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
12 matches
Mail list logo
