Re: Where to look into when system crashes

On 2023-02-23 08:27+0100, to...@tuxteam.de wrote: On Thu, Feb 23, 2023 at 01:41:42PM +0800, Qiming Ye wrote: We have found out it's problem of the current. You mean electrical current? Yes that's what I meant.

Re: Where to look into when system crashes

On Thu, Feb 23, 2023 at 01:41:42PM +0800, Qiming Ye wrote: > We have found out it's problem of the current. You mean electrical current? Cheers -- t signature.asc Description: PGP signature

Re: Where to look into when system crashes

We have found out it's problem of the current. Thank you for the support. - Tim On 2023-02-22 22:38+0700, Max Nikulin wrote: On 22/02/2023 11:34, Qiming Ye wrote: I have a Debian box running for 280+ days without rebooting, recently it crashes pretty much everyday.  Where should I look for

Re: Where to look into when system crashes

On 22/02/2023 11:34, Qiming Ye wrote: I have a Debian box running for 280+ days without rebooting, recently it crashes pretty much everyday.  Where should I look for the reason of crashing? sudo journalctl You may limit logs to specific boot by adding option like "--boot=-1". Scroll to

Re: Where to look into when system crashes

On 2023-02-22 03:21-0500, Felix Miata wrote: Qiming Ye composed on 2023-02-22 15:30 (UTC+0800): Actually /dev/sdb is an mSata drive. Here's output of smartctl: ... 9 Power_On_Hours -O--C- 100 100 000-15975 12 Power_Cycle_Count -O--C- 100 100 000-

Re: Where to look into when system crashes

Qiming Ye composed on 2023-02-22 15:30 (UTC+0800): > Actually /dev/sdb is an mSata drive. Here's output of smartctl: ... >9 Power_On_Hours -O--C- 100 100 000-15975 > 12 Power_Cycle_Count -O--C- 100 100 000-69 Reasonably low use. I don't see a

Re: Where to look into when system crashes

On 2023-02-22 02:05-0500, Felix Miata wrote: Qiming Ye composed on 2023-02-22 12:34 (UTC+0800): I have a Debian box running for 280+ days without rebooting, recently it crashes pretty much everyday. Where should I look for the reason of crashing? If you're running Bullseye from that

Re: Where to look into when system crashes

Qiming Ye composed on 2023-02-22 12:34 (UTC+0800): > I have a Debian box running for 280+ days without rebooting, recently it > crashes > pretty much everyday. Where should I look for the reason of crashing? If you're running Bullseye from that external HD, I'd suspect the external HD's power

Re: Where to look into when system crashes

It's running Debian 11, the last updates were applied few weeks ago. This is the output of inxi -Faz % inxi -Faz System:Kernel: 5.10.0-21-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64

Re: Where to look into when system crashes

Qiming Ye composed on 2023-02-22 12:34 (UTC+0800): > I have a Debian box running for 280+ days without rebooting, recently it > crashes > pretty much everyday. Where should I look for the reason of crashing? Which Debian is installed? When were updates last applied? When was its hardware

Where to look into when system crashes

Hello, I have a Debian box running for 280+ days without rebooting, recently it crashes pretty much everyday. Where should I look for the reason of crashing? Thank you, - Tim

Re: Help! System crashes and locks up.

On Sun, 2016-02-21 at 18:12 -0600, Dennis Wicks wrote: > Greetings; > > I have a system I just put together. New pwr sup, mobo, and  > 1 new SATA disk, 1TB. 2Gig memory. Processor is a Phenom  > 9950 4 core. Running Deb 8.3.0 Jessie, new install. > > Every so often it crashes and locks up, and

Re: Help! System crashes and locks up.

On Sun, 21 Feb 2016, Dennis Wicks wrote: > Greetings; > > I have a system I just put together. New pwr sup, mobo, and > 1 new SATA disk, 1TB. 2Gig memory. Processor is a Phenom > 9950 4 core. Running Deb 8.3.0 Jessie, new install. > > Every so often it crashes and locks up, and the monitor >

Re: Help! System crashes and locks up.

On Sun, Feb 21, 2016 at 5:44 PM, David Christensen wrote: > I've experienced RAM that passed for a hour or two, but generated a few > errors over 24 hours. So, now I run it for 24 hours if I'm suspicious. Should have explained my entire logic with this process. I've

Re: Help! System crashes and locks up.

On 02/21/2016 04:29 PM, Brandon Vincent wrote: Sounds like a hardware problem of some sort. First thing I would do it check the RAM. Download Memtest86+ (for the latest version) and boot from the CD or USB device. See if it completes a few passes without error. +1/2. I've experienced RAM

Re: Help! System crashes and locks up.

On Sun, Feb 21, 2016 at 5:12 PM, Dennis Wicks wrote: > Does this sound familiar to anybody? Any hints? Sounds like a hardware problem of some sort. First thing I would do it check the RAM. Download Memtest86+ (for the latest version) and boot from the CD or USB device. See if it

Help! System crashes and locks up.

Greetings; I have a system I just put together. New pwr sup, mobo, and 1 new SATA disk, 1TB. 2Gig memory. Processor is a Phenom 9950 4 core. Running Deb 8.3.0 Jessie, new install. Every so often it crashes and locks up, and the monitor screen has many narrow horizontal lines, mostly the

RE: System crashes for no apparent reason

wont boot the gui, I'm pretty sure that works anyway Date: Thu, 7 Jun 2012 22:26:15 -0700 Subject: Re: System crashes for no apparent reason From: dan.h...@gmail.com To: karl.jorgen...@nice.com CC: debian-user@lists.debian.org On Wed, Jun 6, 2012 at 2:32 AM, Karl E. Jorgensen karl.jorgen

Re: System crashes for no apparent reason

on whether you use gdm or xdm of course :) then init wont boot the gui, I'm pretty sure that works anyway Date: Thu, 7 Jun 2012 22:26:15 -0700 Subject: Re: System crashes for no apparent reason From: dan.h...@gmail.com To: karl.jorgen...@nice.com CC: debian-user@lists.debian.org On Wed, Jun

Re: System crashes for no apparent reason

On Wed, Jun 6, 2012 at 2:32 AM, Karl E. Jorgensen karl.jorgen...@nice.com wrote: An experiment which may exclude the video drivers from the equation: Try NOT starting X ?  If it still crashes without X ever being started, then it points towards the problem being elsewhere... Hi Karl, A real

Re: System crashes for no apparent reason

On Jo, 07 iun 12, 22:26:15, Dan Hitt wrote: I don't suppose there's some kind of boot option i can set because X runs on top of the kernel, but i suppose that somewhere, somehow i can tell the system that the next time it comes up to not bring up X? If you use gdm then booting with option

Re: System crashes for no apparent reason

Hello Marc, maybe this is a hardware problem? I'm not a hardware guru, but in the past I've had problems with power supply units getting unstable and causing the system to crash (with subsequent reboot) with no apparent reason: replacing the power unit solved the problem. I had also defective

Re: System crashes for no apparent reason

I would open the box ensure all connections are secure, re seat the ram, close the box, check the ram; then look elsewhere. On 06/06/2012, ACro a...@bluebottle.com wrote: Hello Marc, maybe this is a hardware problem? I'm not a hardware guru, but in the past I've had problems with power

Re: System crashes for no apparent reason

on the network, configure (r)syslog to log to the remote system. When a system crashes it may not be able to write logs locally, but often network logging still works. This may allow you to capture log entries regarding the crash itself. To diagnose a completely dead system: Does Caps Lock work

System crashes for no apparent reason

I am running a reasonably up-to-date Squeeze box (it has been a few days since I did an aptitude update and safe-upgrade). This problem has actually been occurring sporadically for a few weeks now. The system will simply die. I leave the computer on 24/7, normally without problems for

Re: Random System Crashes

On Thu, Oct 04, 2007 at 12:06:33AM -0400, Michael Pobega wrote: On Wed, Oct 03, 2007 at 02:13:49AM -0500, Jude DaShiell wrote: odds are your power supply is on its way to the power supply cemetery. I doubt that, because this laptop is only one year old. I'm kind of hoping that the power

Re: Random System Crashes

- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond to anything but a power-down (I've tried switching to TTY1, among other things, but nothing works). I don't even know where to start diagnosing

Re: Random System Crashes

odds are your power supply is on its way to the power supply cemetery. On Tue, 2 Oct 2007, Kelly Clowers wrote: On 10/2/07, Michael Pobega [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes

Re: Random System Crashes

Michael Pobega wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond to anything but a power-down (I've tried switching to TTY1, among other things

Re: Random System Crashes

On Wed, Oct 03, 2007 at 12:51:24AM -0400, Michael Pobega wrote: Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond to anything but a power-down (I've tried switching to TTY1, among other things, but nothing

Re: Random System Crashes

On Tue, Oct 02, 2007 at 10:33:27PM -0700, Kelly Clowers wrote: Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond to anything but a power-down (I've tried switching to TTY1, among other things, but nothing

Re: Random System Crashes

to be replaced... On Tue, 2 Oct 2007, Kelly Clowers wrote: On 10/2/07, Michael Pobega [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond

Re: Random System Crashes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Oct 02, 2007 at 10:33:27PM -0700, Kelly Clowers wrote: On 10/2/07, Michael Pobega [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes

Re: Random System Crashes

On Wed, 3 Oct 2007, Michael Pobega wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond to anything but a power-down (I've tried switching to TTY1, among

Random System Crashes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond to anything but a power-down (I've tried switching to TTY1, among other things, but nothing works). I don't even

Re: Random System Crashes

On 10/2/07, Michael Pobega [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lately (For the past month or so) I've been experiencing random system crashes. My system would just completely lock up and not respond to anything but a power-down (I've tried switching to TTY1

Re: Help with System Crashes

On Wed, Sep 27, 2000 at 05:31:36PM +0200, Martin Pfeilsticker ([EMAIL PROTECTED]) wrote: Hello I have a strange problem with one of my PCs: It crashes for no obvious reasons, at least one time a day. The system is completly frozen, ie no ping, no Magic-Key, no CTRL-AL-DEL, only a

Help with System Crashes

Hello I have a strange problem with one of my PCs: It crashes for no obvious reasons, at least one time a day. The system is completly frozen, ie no ping, no Magic-Key, no CTRL-AL-DEL, only a HARD-Reset is working. Logfiles in /var/log show nothing unusal. Since this computer is acting as my

System crashes using 2.2.1 kernel with ATI Rage Fury

Hello I experience problems using my ATI Rage Fury (ATI Rage 128) video card with 2.2.x kernel. With 2.0.36 kernel I use a XRage128 server from SUSE and everything works fine. Trying to start xserver with 2.2.1 causes system crash: the screen remains blank and I can't change to text consoles.

Re: System crashes using 2.2.1 kernel with ATI Rage Fury

On Wed, 20 Oct 1999, Adam Wojnicki wrote: I experience problems using my ATI Rage Fury (ATI Rage 128) video card with 2.2.x kernel. With 2.0.36 kernel I use a XRage128 server from SUSE and everything works fine. I use the same card and X server and I upgraded from 2.0.36 to 2.2.12 without a

Re: System crashes using 2.2.1 kernel with ATI Rage Fury

Daniel Haude wrote: On Wed, 20 Oct 1999, Adam Wojnicki wrote: I experience problems using my ATI Rage Fury (ATI Rage 128) video card with 2.2.x kernel. With 2.0.36 kernel I use a XRage128 server from SUSE and everything works fine. I use the same card and X server and I upgraded

Re: System crashes using 2.2.1 kernel with ATI Rage Fury

On Wed, 20 Oct 1999, Adam Wojnicki wrote: Trying to start xserver with 2.2.1 causes system crash: Before any further discussion please upgrade first to a more *recent* 2.2.x kernel and try again. The current kernel version is 2.2.12 with 2.2.13 being expected very soon. These versions are

Re: system crashes

On Fri, 30 Jan 1998 [EMAIL PROTECTED] wrote: I am a relatively new user of Debian Linux, and am trying to determine the cause of a couple crashes that have occured during the past month. I am running Debian version 1.3 on a dual-processor Pentium II machine. On two occasions the screen

system crashes

I am a relatively new user of Debian Linux, and am trying to determine the cause of a couple crashes that have occured during the past month. I am running Debian version 1.3 on a dual-processor Pentium II machine. On two occasions the screen froze up and I could not login remotely to