On ven, 2005-07-22 at 11:09 -0700, Curtis Vaughan wrote:
> Hopefully those people who replied to this issue earlier can respond.
>
> If you recall I had a problem with a server crashing (read below). I
> started doing a memtest on the server itself while operating. It has
> bee
Curtis Vaughan wrote:
> Hopefully those people who replied to this issue earlier can respond.
>
> If you recall I had a problem with a server crashing (read below). I
> started doing a memtest on the server itself while operating. It has
> been running now 3 days. The serv
Hopefully those people who replied to this issue earlier can respond.
If you recall I had a problem with a server crashing (read below). I
started doing a memtest on the server itself while operating. It has
been running now 3 days. The server has not once crashed that whole
time. But this
On Tuesday 19 Jul 2005 21:54, Curtis Vaughan wrote:
> > This is why I asked if you could "afford to" do the test.
> >
> > I was lucky because I had a spare machine and spare RAM: I swapped
> > the RAM and
> > put the "dodgy" RAM into the spare machine. I then used a Knoppix
> > boot CD and
> > boot
On 19 juil. 05, at 12:35, TreeBoy wrote:
On Tuesday 19 Jul 2005 19:30, Curtis Vaughan wrote:
The only time this happened to me was when I had broken RAM.
Can you afford to run memtest on the machine for a couple of days
in order to
rule it out.
I swapped the RAM into another machine and it
strawks said:
> On Tue, 2005-07-19 at 13:52 -0500, Josh Battles wrote:
>> strawks said:
>> > The best way to avoid RAM problem is to buy ECC RAM. This way if your
>> > RAM has a failling cell, you'll know it.
>>
>> ECC RAM is expensive and RAM errors are relatively rare nowdays, I don't
>> think t
On Tuesday 19 Jul 2005 20:53, strawks wrote:
> On Tue, 2005-07-19 at 13:52 -0500, Josh Battles wrote:
> > strawks said:
> > > The best way to avoid RAM problem is to buy ECC RAM. This way if your
> > > RAM has a failling cell, you'll know it.
> >
> > ECC RAM is expensive and RAM errors are relative
On Tue, 2005-07-19 at 13:52 -0500, Josh Battles wrote:
> strawks said:
> > The best way to avoid RAM problem is to buy ECC RAM. This way if your
> > RAM has a failling cell, you'll know it.
>
> ECC RAM is expensive and RAM errors are relatively rare nowdays, I don't
> think this is something that'
On Tuesday 19 Jul 2005 19:30, Curtis Vaughan wrote:
> >
> > The only time this happened to me was when I had broken RAM.
> >
> > Can you afford to run memtest on the machine for a couple of days
> > in order to
> > rule it out.
> >
> > I swapped the RAM into another machine and it eventually failed
strawks said:
> The best way to avoid RAM problem is to buy ECC RAM. This way if your
> RAM has a failling cell, you'll know it.
ECC RAM is expensive and RAM errors are relatively rare nowdays, I don't
think this is something that's easily justified in a home environment.
Besides with current pr
On 19 juil. 05, at 10:42, TreeBoy wrote:
On Tuesday 19 Jul 2005 18:22, Curtis Vaughan wrote:
I have a Debian Sarge server which provides the following services
DNS (internal only), DHCP, Apache, Samba.
Yesterday morning it suddenly crashed. I could not access it through
any protocols and the
The best way to avoid RAM problem is to buy ECC RAM. This way if your
RAM has a failling cell, you'll know it.
On Tue, 2005-07-19 at 18:42 +0100, TreeBoy wrote:
> On Tuesday 19 Jul 2005 18:22, Curtis Vaughan wrote:
> > I have a Debian Sarge server which provides the following services
> > DNS (int
On Tuesday 19 Jul 2005 18:22, Curtis Vaughan wrote:
> I have a Debian Sarge server which provides the following services
> DNS (internal only), DHCP, Apache, Samba.
>
> Yesterday morning it suddenly crashed. I could not access it through
> any protocols and the terminal was totally locked (no conso
I have a Debian Sarge server which provides the following services
DNS (internal only), DHCP, Apache, Samba.
Yesterday morning it suddenly crashed. I could not access it through
any protocols and the terminal was totally locked (no console,
nothing), although the computer was still on. Afte
Barry Skidmore wrote:
When I did a:
# xset -dpms
xserver immediately crashed with the following error:
xterm: fatal IO server error 32 (Broken pipe) or KillClient on X Server
":0.0"
/usr/bin/Windowmaker
warning.got signal 1 (Hangup1-exiting...
looks like it's confirmed that it has something to do
When I did a:
# xset -dpms
xserver immediately crashed with the following error:
xterm: fatal IO server error 32 (Broken pipe) or KillClient on X Server
":0.0"
/usr/bin/Windowmaker
warning.got signal 1 (Hangup1-exiting...
Barry
On Sun, Jun 06, 2004 at 08:30:15PM -0500, Barry Skidmore wrote:
>
No, I am not sure it is dpms that is causing the problem, but I will see
what is the effect of the -dpms option. I did not see that
option documented.
Barry
On Sun, Jun 06, 2004 at 04:30:22PM -0700, Erik Steffl wrote:
> Barry Skidmore wrote:
> >I believe I am having a problem with the xserver fa
Barry Skidmore wrote:
I believe I am having a problem with the xserver failing whenever my
monitor's DPMS kicks in. After either windowmaker or enlightenment have
run for 15 minutes, the window manager quits and I am put back into the
console with the following errors:
Fatal server error:
Cau
I believe I am having a problem with the xserver failing whenever my
monitor's DPMS kicks in. After either windowmaker or enlightenment have
run for 15 minutes, the window manager quits and I am put back into the
console with the following errors:
Fatal server error:
Caught signal 4. Server
Hi,
I had posted the problem last week and someone had suggested that I
reinstall the X binaries, which I did.
But the problem persists and my X windows crashes with signal 11 error.
Any suggestions?
Rajesh
Hi,
We are running a slink debian distribution with kernel 2.0.36 on a
celeron 333 as our file server. Our SCSI adapter is an Adaptec 2940UW PCI card,
with this configuration:
2940UW Adapter
|
Seagate Barracuda 9.1gig UW
|
Quantum V
On Fri, Jun 25, 1999 at 03:55:57PM +1000, Ed Breen wrote:
>
> Hi,
>
> We are running a slink debian distribution with kernel 2.0.36 on
> a celeron 333 as our file server. Our SCSI adapter is an Adaptec 2940UW
> PCI card, with this configuration:
>
> 2940UW Adapter
> |
>
Howdy,
I have a Linux compilation server running in a mostly SUN and SGI
environment. Everything is running fine except for the NFS which is
really a pain. When I try to reach an exported filesystem from a SUN
or SGI, the nfs daemon crashes after a few minutes (well, it's still there
but it sto
[ problems running a Viper 330 on debian 2.0 ]
> (--) VGA16: PCI: NVidia/SGS-Thomson Riva128 rev 16, Memory @
> 0xf500, 0xfc00
> (--) VGA16: chipset: generic
> (**) VGA16: videoram: 4096k (using 4096k)
> (--) VGA16: clocks: 25.19 28.32 28.32 28.32
> (--) VGA16: Maximum allowed dot-cl
Hello everyone,
I am having problems running X with my Diamond Viper 330 AGP
with Debian 2.0. The xserver crashes with the
infamous error 111, however I know it can and will work.
First of all, it worked fine with RH 5.1, and second, the xf86config
program runs fine and it runs the xserver witho
25 matches
Mail list logo
