LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 04-28-2007, 03:45 PM   #1
alexcpp
LQ Newbie
 
Registered: Dec 2005
Posts: 20

Rep: Reputation: 0
Unhappy System resets after reading a large file


I have this strange problem. When I try to read off of an IDE drive a file that is large (over ~200 MB or so) the system resets. Writing causes no problems at all.

Here is a command that I am running when system resets: rsync -a -v --delete --update /storage/removable1_backup/ /storage/removable1/

System also resets when I try to copy files using Samba.

The drive that is being read is /dev/hdd1

Here is some information about my system:

Quote:
[root@localhost ~]# cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/hdd1 /storage/removable1_backup ext3 suid,dev,exec 0 0
/dev/hdc1 /storage/removable1 ext3 suid,dev,exec 0 0
/dev/hda /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0
[root@localhost ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
960228760 262502104 648949852 29% /
/dev/sda1 101086 15937 79930 17% /boot
none 257140 0 257140 0% /dev/shm
/dev/hdd1 288435168 189451476 84332012 70% /storage/removable1_backup
/dev/hdc1 288427136 8551252 265224608 4% /storage/removable1
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.9-42.0.10.ELsmp #1 SMP Tue Feb 27 10:11:19 EST 2007 i686 i686 i386 GNU/Linux
[root@localhost ~]# lspci -vv
00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
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: 8
Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [80] AGP version 3.5
Status: RQ=8 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [50] 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-

00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
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:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
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:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
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:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
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:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
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:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
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
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: fca00000-feafffff
Prefetchable memory behind bridge: e3f00000-f3efffff
Secondary status: 66Mhz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR+ <PERR-
BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
Capabilities: [70] 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-

00:09.0 Multimedia video controller: Unknown device 9413:6000
Subsystem: Unknown device 9413:6000
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 (250ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 169
Region 0: Memory at f7000000 (32-bit, prefetchable) [size=16M]
Region 2: I/O ports at e800 [size=256]

00:0a.0 Multimedia video controller: Unknown device 9413:6000
Subsystem: Unknown device 9413:6000
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 (250ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 177
Region 0: Memory at f6000000 (32-bit, prefetchable) [size=16M]
Region 2: I/O ports at e400 [size=256]

00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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
Interrupt: pin B routed to IRQ 185
Region 0: I/O ports at ec00 [size=8]
Region 1: I/O ports at e080 [size=4]
Region 2: I/O ports at e000 [size=8]
Region 3: I/O ports at dc00 [size=4]
Region 4: I/O ports at d880 [size=16]
Region 5: I/O ports at d400 [size=256]
Capabilities: [c0] 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-

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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: 32
Interrupt: pin A routed to IRQ 185
Region 4: I/O ports at fc00 [size=16]
Capabilities: [c0] 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-

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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 08
Interrupt: pin A routed to IRQ 193
Region 4: I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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 08
Interrupt: pin A routed to IRQ 193
Region 4: I/O ports at d080 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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 08
Interrupt: pin B routed to IRQ 193
Region 4: I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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 08
Interrupt: pin B routed to IRQ 193
Region 4: I/O ports at cc00 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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 20
Interrupt: pin C routed to IRQ 193
Region 0: Memory at febffc00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
Subsystem: Elitegroup Computer Systems: Unknown device 0951
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
Capabilities: [c0] 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-

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Subsystem: Elitegroup Computer Systems: Unknown device 1836
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 C routed to IRQ 201
Region 0: I/O ports at c800 [size=256]
Capabilities: [c0] 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-

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
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 (750ns min, 2000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 209
Region 0: I/O ports at c400 [size=256]
Region 1: Memory at febff800 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] 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-

01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) (prog-if 00 [VGA])
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 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 217
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at feae0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 3.0
Status: RQ=32 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
If you have an idea about what is going on please post it.

Please point me to a log file (/var/log/messages?, too big to find anything) which would contain the crash information.
 
Old 04-28-2007, 04:10 PM   #2
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 78
See what happens when you disable DMA and repeat the experiment.
 
Old 04-28-2007, 04:15 PM   #3
Electro
LQ Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
I think you have a power supply problem. I suggest buying a new power supply and do not be cheap. The brands that I suggest are Eneramax, Power & Cooling, and Seasonic.
 
Old 04-28-2007, 04:53 PM   #4
alexcpp
LQ Newbie
 
Registered: Dec 2005
Posts: 20

Original Poster
Rep: Reputation: 0
Unhappy

Quote:
Originally Posted by Electro
I think you have a power supply problem. I suggest buying a new power supply and do not be cheap. The brands that I suggest are Eneramax, Power & Cooling, and Seasonic.
Interesting suggestion, I will look into that. However, what does that have to do with copying (reading) big files? I tried copying (reading) a series of (relatively) small files (for a relatively extended period of time) and the system stays up. Also, writing files doesn't cause the crash.

Please note, I tried copying locally and over the network (Samba, SSH). All methods show that writing does not cause the problem.
 
Old 04-28-2007, 05:16 PM   #5
lazlow
Senior Member
 
Registered: Jan 2006
Posts: 4,363

Rep: Reputation: 172Reputation: 172
Possibly a memory problem. I would run memtest86. Run it for a couple of hours to really get a good feel for it. I had one dimm that would not show a problem until at least an hour went by.

Power supply problems can cause all kinds of strange problems. I would probably install lmsensors first and see if you are getting any voltage variation(any variation of .2 or greater is a BAD sign). While actual voltage may be important, IMHO it is the variation that really creates problems. If it is a power problem do not screw around with cheap power supplies. Seasonic is good.
 
Old 04-28-2007, 05:36 PM   #6
alexcpp
LQ Newbie
 
Registered: Dec 2005
Posts: 20

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by osor
See what happens when you disable DMA and repeat the experiment.
Quote:

[root@localhost storage]# hdparm -d0 /dev/hdd

/dev/hdd:
setting using_dma to 0 (off)
using_dma = 0 (off)
[root@localhost storage]# hdparm -d0 /dev/hdc

/dev/hdc:
setting using_dma to 0 (off)
using_dma = 0 (off)
[root@localhost storage]# rsync -a -v --delete --update /storage/removable1_backup/ /storage/removable1/
building file list ... done
blah blah blah...
blah blah blah...
blah blah blah...
blah blah blah...
This hasn't crashed the system so far (it is still in the process of copying) but it's too slow, obviously.

What does this suggest?

Last edited by alexcpp; 04-28-2007 at 05:38 PM.
 
Old 04-28-2007, 07:09 PM   #7
alexcpp
LQ Newbie
 
Registered: Dec 2005
Posts: 20

Original Poster
Rep: Reputation: 0
Question

After I have turned off DMA the system has been stable (but slow). What could be the reason for this (DMA-related failure)?

Last edited by alexcpp; 04-28-2007 at 07:19 PM.
 
Old 04-29-2007, 08:35 PM   #8
Electro
LQ Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
Probably VIA VT82C586A/B/VT82C686 or the IDE controller has a glitch. The glitch can be minimize by changing a few registers using setpci. Sorry I do not remember what registers to modify. Another way to fix it is try upgrading the BIOS. If that is too hard, include noapic and/or noapci or apci=off at the boot loader.

With out knowing how many hard drives that you have in LVM2 or EVMS. I still think your power supply lost its grunt or does not have any grunt to start with. Four hard drives can consume a lot of power.

Another cause is heat. The chipset or procssor could be over heating.
 
Old 05-06-2007, 02:00 AM   #9
alexcpp
LQ Newbie
 
Registered: Dec 2005
Posts: 20

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Electro
Probably VIA VT82C586A/B/VT82C686 or the IDE controller has a glitch. The glitch can be minimize by changing a few registers using setpci. Sorry I do not remember what registers to modify. Another way to fix it is try upgrading the BIOS. If that is too hard, include noapic and/or noapci or apci=off at the boot loader.

With out knowing how many hard drives that you have in LVM2 or EVMS. I still think your power supply lost its grunt or does not have any grunt to start with. Four hard drives can consume a lot of power.

Another cause is heat. The chipset or procssor could be over heating.

Thanks for the info.

I ran memtest86 for three hours but with no errors. I will try another power supply and other suggestions. Thanks a lot.
 
Old 05-13-2007, 04:22 AM   #10
alexcpp
LQ Newbie
 
Registered: Dec 2005
Posts: 20

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Electro
Probably VIA VT82C586A/B/VT82C686 or the IDE controller has a glitch. The glitch can be minimize by changing a few registers using setpci. Sorry I do not remember what registers to modify. Another way to fix it is try upgrading the BIOS. If that is too hard, include noapic and/or noapci or apci=off at the boot loader.

With out knowing how many hard drives that you have in LVM2 or EVMS. I still think your power supply lost its grunt or does not have any grunt to start with. Four hard drives can consume a lot of power.

Another cause is heat. The chipset or procssor could be over heating.

I have just tried another power supply (which I know worked with 4 hard drives and a CD-Rom). It did not make any difference at all. The reset still occurs with DMA enabled. I will try some of the other suggestions but this seems hopeless to me. (boy, do I want to beat up the person who built this server).
 
Old 05-13-2007, 11:16 PM   #11
Electro
LQ Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
Go to cyberguys.com and buy the post code board.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Reading Large Text File in C++ maheshrajn Programming 6 03-04-2006 08:54 AM
how large can a file system be? Wolf_Assassin Linux - Software 2 08-21-2004 02:31 PM
Large tar file taking huge disk space in ext3 file system pcwulf Linux - General 2 10-20-2003 07:45 AM
Large file system on redhat 7.3 stefanof Linux - Software 1 08-28-2002 08:29 AM
Large file system on redhat 7.3 stefanof Linux - Distributions 1 08-28-2002 08:25 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 10:48 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration