Messages in this thread | | | Date | Wed, 1 Oct 2003 11:16:34 -0400 (EDT) | From | Ricky Beam <> | Subject | Re: i7505 locks up too (Was: iTyan i7501 Pro (S2721-533) lock-up (e1000?)) |
| |
On Wed, 1 Oct 2003, Frank Horowitz wrote: >I'm seeing a similar problem with a (bunch of) Supermicro i7505 boards >(X5DAL-G's if it matters). All with e1000 onboard (but running at >100Mbps full-duplex through Cisco 2900-series and 4000-series switches). >All locking up under heavy load (openMosix process migrations). ... >All boxes have had memtest86 run on them with repeated passes and are >showing fine.
Currently, both machines are working and stable. I may have tanted the results by bleeding on them, however.
11:07:43 up 19:26, 3 users, load average: 2.10, 1.83, 1.39 40 processes: 38 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 93.9% user 6.0% system 0.0% nice 0.0% iowait 0.0% idle Mem: 1035060k av, 919232k used, 115828k free, 0k shrd, 39656k buff 66692k active, 10476k inactive Swap: 2040244k av, 0k used, 2040244k free 28820k cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 1272 root 25 0 5824 4192 3000 R 98.2 0.4 1141m 0 capture
First, both machines have un-certified "POWMEM" memory modules. So, that's my first suspect. Tyan boards act insane with "bad" memory. That said, memtest86 cannot stress memory in the way it needs to be stressed to actually fail. The ring buffers from the e1000's (64bit, 133MHz PCI-X) will stress memory in the extreme.
If you have "spread spectrum" enabled (search all the BIOS screens), turn it off and see if the machine becomes more stable. Failing that, find known good memory (certified for use in the MB by the manufacturer.) From there, try reducing the PCI bus speed (if possible -- there's a bios option on the i7501)
I'm still running with "pci=noacpi" so that might be adding to the soluion.
I wasn't seeing any IDE problems. In fact, the disk isn't being touched at all.
--Ricky
- 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/
| |