Re: Random server reboot after update to CentOS 5.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



The guys on the Dell PowerEdge ML seem to be attracted by the idea that 
it is a driver problem of the network adapter. In this case, lspci gives me:

09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 
Gigabit Ethernet (rev 12)

Does this match your adapter?

Regards,

Peter

Mathew S. McCarrell wrote:
> Actually, I've also been experience this issue on a two identical 
> custom built systems running 5.3 x64 with Xen.  I experienced the 
> issue under the same kernel that Peter is running and the first kernel 
> released with 5.3.
>
> In my particular instance, I'm attributing these random crashes to 
> hardware problems since I'm only experiencing the issues on these two 
> systems and not an older Dell PowerEdge 850 which is set up with the 
> same software configuration.
>
> Matt
>
> --
> Mathew S. McCarrell
> Clarkson University '10
>
> mccarrms@xxxxxxxxx <mailto:mccarrms@xxxxxxxxx>
> mccarrms@xxxxxxxxxxxx <mailto:mccarrms@xxxxxxxxxxxx>
>
>
> On Fri, May 22, 2009 at 10:26 AM, Michael A. Peters <mpeters@xxxxxxx 
> <mailto:mpeters@xxxxxxx>> wrote:
>
>     JohnS wrote:
>
>     >
>     > My sejustion is unplug everything hooked to it but the power and
>     network
>     > cabling. Open it up while it is running, and shake the cables
>     lightly
>     > ( don't jerk on them). External disk array, unplug it also. USB
>     floppies
>     > and cd drives unplug emmm all.
>     >
>     > Is it under a heavy load? High cpu usage? Some times when there is a
>     > power supply on the verge of dying you don't really know until
>     disk I/O
>     > climbs real high thus pulling loads of wattage.
>
>     That's my guess.
>     I'd swap out the power supply.
>
>     My personal experience with ram issues is either kernel panic or
>     filesystem funnyness (sometimes resulting in filesystems being
>     remounted
>     read only). My experience with disk I/O issues is that forcing fsck
>     reveals filesystem errors with high frequency.
>
>     Rebooting machines in my experience is almost always a failing power
>     supply (or faulty power source - check your UPS, when they start to go
>     bad they can cause issues).
>
>     If it was a kernel issue, I suspect more people would be experiencing
>     (unless it is caused by a third party kmod)
>     _______________________________________________
>     CentOS mailing list
>     CentOS@xxxxxxxxxx <mailto:CentOS@xxxxxxxxxx>
>     http://lists.centos.org/mailman/listinfo/centos
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>   


-- 
 
Dott. Peter Hopfgartner
 
R3 GIS Srl - GmbH
Via Johann Kravogl-Str. 2
I-39012 Meran/Merano (BZ)
Email: peter.hopfgartner@xxxxxxxxxx
Tel. : +39 0473 494949
Fax  : +39 0473 069902
www  : http://www.r3-gis.com

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux