Hi Dick,
Excuses me for the silence.
Can you tell me why the drive stops to respond? Where
the problem starts? As I tell before, we tried
different drives and that has not help us.
Friday, The constructor comes to a meeting in our
offices and they affirm that their materials is ok.
Have you read some articles that pointed out failures
on the South Bridge VIA VT82c686 or other's chipset
off the VIA PN133 architecture?
(http://www.via.com.tw/en/products/chipsets/legacy/pn133/)
If it can help, this are the description :
00:00.0 Host bridge: VIA Technologies, Inc. VT8605
[ProSavage PM133] (rev 01)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8605
[PM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686
[Apollo Super South] (rev 40
)
00:07.1 IDE interface: VIA Technologies, Inc. Bus
Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB
(rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. USB
(rev 1a)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686
[Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies,
Inc. VT82C686 AC97 Audio
Controller (rev 50)
00:10.0 Ethernet controller: Intel Corp. 82557/8/9
[Ethernet Pro 100] (rev 08)
01:00.0 VGA compatible controller: S3 Inc. ProSavage
PM133 (rev 02)
[root@Porte_de_Clignancourt_nds_b root]# lspci -n
00:00.0 Class 0600: 1106:0605 (rev 01)
00:01.0 Class 0604: 1106:8605
00:07.0 Class 0601: 1106:0686 (rev 40)
00:07.1 Class 0101: 1106:0571 (rev 06)
00:07.2 Class 0c03: 1106:3038 (rev 1a)
00:07.3 Class 0c03: 1106:3038 (rev 1a)
00:07.4 Class 0680: 1106:3057 (rev 40)
00:07.5 Class 0401: 1106:3058 (rev 50)
00:10.0 Class 0200: 8086:1229 (rev 08)
01:00.0 Class 0300: 5333:8a25 (rev 02)
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 10
cpu MHz : 998.393
cache size : 256 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
sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1992.29
--- Alan Cox <[email protected]> a écrit :
> On Maw, 2006-03-28 at 17:07 +0200, zine el abidine
> Hamid wrote:
> > I don't think that it's a HDD problem nor a cable
> > problem because the servers are new. We have tried
>
> New. Thats another word for "untested" I believe 8)
>
> > How can I determine the problem?
>
> I would consult the hardware vendor
>
> > I want to add that the HDD seems to be
> disconnected
> > (the BIOS can't find any drive for boot) after a
> > simple reset. We must switch off the servers to
> get
> > them work again.
>
> Thats strongly indicating a hardware problem.
>
> > (http://www.tldp.org/LDP/lkmpg/) but how can I
> > shutdown Linux from inside a module...?
>
> See the softdog driver for an example.
>
>
___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
