Sponsored Content
Full Discussion: Hardware problem diagnosing
Operating Systems Linux Hardware problem diagnosing Post 302284576 by Neo on Thursday 5th of February 2009 11:12:10 PM
Old 02-06-2009
Generally, you start by looking at the messages generated during boot time, for example dmesg
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

PCMCIA Hardware Problem

Hi, I have a Dell Inspiron 4000 that I am using to run Redhat Linux 7.1. This machine had 128Mb of RAM in it, and I upgraded to 512Mb. Since this, the PCMCIA cards have disappeared from the system running under Linux, although they still work under windows and the file "/var/lib/pcmcia/stab"... (1 Reply)
Discussion started by: ghoti
1 Replies

2. Solaris

hardware problem?

Can someone tell me what the following means? We have a v440 running Solaris 9. What do the patterns actually mean? May 17 12:12:03 ibasdb02 cediag: Revision: 1.78 @ 2005/02/11 15:5 :29 UTC May 17 12:12:03 ibasdb02 cediag: Analysed System: SunOS 5.9 with UP 117171-17 (MPR active) May 17... (5 Replies)
Discussion started by: hshapiro
5 Replies

3. UNIX for Advanced & Expert Users

Hardware HBA problem

I have worked with Qlogic (Sun) fiber cards a lot and with Emulex fiber cards only a little. Here is the scenario: I have a Sun 490 with 3 Emulex cards in it. A pair are for the 6120 array that is attached, the other is a direct attach so our SAN for Veritas Netbackup to back up the system.I... (0 Replies)
Discussion started by: lm_admin_dh
0 Replies

4. Solaris

Hardware Raid related problem

Dear All I would Like to know that if suppose c1t0d0 is of 72 gb hard disk and system boot from this hard disk and c1t1d0 is of 147gb hard disk. Can we implement hardware raid (Mirror) between these two hard disks of different capacity if raid crontroller is present in the server Kind regards (4 Replies)
Discussion started by: girish.batra
4 Replies

5. Solaris

problem in finding a hardware problem

Hi I am right now facing a strange hardware problem. System get booted with the following error: Fatal Error Reset CPU 0000.0000.0000.0003 AFSR 0100.0000.0000.0000 SCE AFAR 0000.07c6.0000.1000 SC Alert: Host System has Reset It happen 4 or 5 times and get the same error every time.I... (8 Replies)
Discussion started by: girish.batra
8 Replies

6. Solaris

Hardware problem diagnosing

Hey guys how to do diagnose solaris for hardware problems/issues. This is a general question for all common hardware components under solaris server. (4 Replies)
Discussion started by: sbn
4 Replies

7. HP-UX

Hardware problem diagnosing

Hey guys how to do diagnose HP-UX for hardware problems/issues. This is a general question for all common hardware components under HP-UX server. (4 Replies)
Discussion started by: sbn
4 Replies

8. Solaris

Sun Fire v440 hardware problem (can't get ok>)

First of all it's shut down 60 second after power on and write on console : SC Alert: Correct SCC not replaced - shutting managed system down! This is cured by moving out battery from ALOM card. Now server start to loop during the testing. That's on the console: >@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies

9. Solaris

Hardware Problem

Dear: the Cureent PC Dell GX620 the Current Hardware 4 GB ram 80 HDD what i do remove old 4GB ram and install 8 GB remove old HDD and install new on 160GB try to install the Unix Sun Solaris after booting and when arrive to step which i should select interactive error meg... (7 Replies)
Discussion started by: hosney00ux
7 Replies

10. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
DMESG(1)							   User Commands							  DMESG(1)

NAME
dmesg - print or control the kernel ring buffer SYNOPSIS
dmesg [options] dmesg --clear dmesg --read-clear [options] dmesg --console-level level dmesg --console-on dmesg --console-off DESCRIPTION
dmesg is used to examine or control the kernel ring buffer. The default action is to display all messages from the kernel ring buffer. OPTIONS
The --clear, --read-clear, --console-on, --console-off, and --console-level options are mutually exclusive. -C, --clear Clear the ring buffer. -c, --read-clear Clear the ring buffer after first printing its contents. -D, --console-off Disable the printing of messages to the console. -d, --show-delta Display the timestamp and the time delta spent between messages. If used together with --notime then only the time delta without the timestamp is printed. -E, --console-on Enable printing messages to the console. -e, --reltime Display the local time and the delta in human-readable format. Be aware that conversion to the local time could be inaccurate (see -T for more details). -F, --file file Read the syslog messages from the given file. Note that -F does not support messages in kmsg format. The old syslog format is sup- ported only. -f, --facility list Restrict output to the given (comma-separated) list of facilities. For example: dmesg --facility=daemon will print messages from system daemons only. For all supported facilities see the --help output. -H, --human Enable human-readable output. See also --color, --reltime and --nopager. -k, --kernel Print kernel messages. -L, --color[=when] Colorize the output. The optional argument when can be auto, never or always. If the when argument is omitted, it defaults to auto. The colors can be disabled; for the current built-in default see the --help output. See also the COLORS section below. -l, --level list Restrict output to the given (comma-separated) list of levels. For example: dmesg --level=err,warn will print error and warning messages only. For all supported levels see the --help output. -n, --console-level level Set the level at which printing of messages is done to the console. The level is a level number or abbreviation of the level name. For all supported levels see the --help output. For example, -n 1 or -n alert prevents all messages, except emergency (panic) messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer. -P, --nopager Do not pipe output into a pager. A pager is enabled by default for --human output. -r, --raw Print the raw message buffer, i.e. do not strip the log-level prefixes. Note that the real raw format depends on the method how dmesg(1) reads kernel messages. The /dev/kmsg device uses a different for- mat than syslog(2). For backward compatibility, dmesg(1) returns data always in the syslog(2) format. It is possible to read the real raw data from /dev/kmsg by, for example, the command 'dd if=/dev/kmsg iflag=nonblock'. -S, --syslog Force dmesg to use the syslog(2) kernel interface to read kernel messages. The default is to use /dev/kmsg rather than syslog(2) since kernel 3.5.0. -s, --buffer-size size Use a buffer of size to query the kernel ring buffer. This is 16392 by default. (The default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger than the default, then this option can be used to view the entire buffer. -T, --ctime Print human-readable timestamps. Be aware that the timestamp could be inaccurate! The time source used for the logs is not updated after system SUSPEND/RESUME. -t, --notime Do not print kernel's timestamps. --time-format format Print timestamps using the given format, which can be ctime, reltime, delta or iso. The first three formats are aliases of the time-format-specific options. The iso format is a dmesg implementation of the ISO-8601 timestamp format. The purpose of this for- mat is to make the comparing of timestamps between two systems, and any other parsing, easy. The definition of the iso timestamp is: YYYY-MM-DD<T>HH:MM:SS,<microseconds><-+><timezone offset from UTC>. The iso format has the same issue as ctime: the time may be inaccurate when a system is suspended and resumed. -u, --userspace Print userspace messages. -w, --follow Wait for new messages. This feature is supported only on systems with a readable /dev/kmsg (since kernel 3.5.0). -x, --decode Decode facility and level (priority) numbers to human-readable prefixes. -V, --version Display version information and exit. -h, --help Display help text and exit. COLORS
Implicit coloring can be disabled by an empty file /etc/terminal-colors.d/dmesg.disable. See terminal-colors.d(5) for more details about colorization configuration. The logical color names supported by dmesg are: subsys The message sub-system prefix (e.g. "ACPI:"). time The message timestamp. timebreak The message timestamp in short ctime format in --reltime or --human output. alert The text of the message with the alert log priority. crit The text of the message with the critical log priority. err The text of the message with the error log priority. warn The text of the message with the warning log priority. segfault The text of the message that inform about segmentation fault. SEE ALSO
terminal-colors.d(5), syslogd(8) AUTHORS
Karel Zak <kzak@redhat.com> dmesg was originally written by Theodore Ts'o <tytso@athena.mit.edu> AVAILABILITY
The dmesg command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils /util-linux/>. util-linux July 2012 DMESG(1)
All times are GMT -4. The time now is 02:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy