09-23-2003
cpu 0 is displaying those messages.
psrinfo -v
will confirm that all is cool.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone would know how to get rid off a message that comes up during a boot-up on Solaris? It says that the clusters for this software are not installed. I deleted the software because it was crashing some other stuff but it did not get rid off all the stuff.
Yes, I am coming from windows and... (2 Replies)
Discussion started by: softarch
2 Replies
2. UNIX for Advanced & Expert Users
Hey !
I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range.
According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies
3. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
4. Linux
Where do all those messages at boot time get stored / logged?
like:
starting eth0 : OK
starting mysql : OK
etc... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
5. Solaris
Hello All,
I have all of a sudden developed issues with booting up one of my Solaris Servers. Upon a routine reboot, I was faced with the following errors:
Feb 1 07:56:44 sco1-au-tci scsi: WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd0):
Feb 1 07:56:44 sco1-au-tci Error for Command: read(10)... (9 Replies)
Discussion started by: ranjtech
9 Replies
6. Red Hat
Hello All,
I backed up my RHEL 4 as an image.
Then I restored the image (by mondorestore) on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4.
The messages that are shown when the system boots are something like-
"... (13 Replies)
Discussion started by: shamik
13 Replies
7. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
8. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
9. Red Hat
I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf
From my research, there appear to be three levels:
quiet
verbose
debug
I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 Replies
10. Red Hat
Hi all
Many years ago, I found online this script that was incredibly funny and I had blogged it
Unfortunately because of my poor record-keeping, I seem to have lost the shell script
Would somebody be kind enough to tell me how to replicate this?
Thank you! (0 Replies)
Discussion started by: hedkandi
0 Replies
DMESG(1) General Commands Manual DMESG(1)
NAME
dmesg - print or control the kernel ring buffer
SYNOPSIS
dmesg [-c] [-r] [-n level] [-s bufsize]
DESCRIPTION
dmesg is used to examine or control the kernel ring buffer.
The program helps users to print out their bootup messages. Instead of copying the messages by hand, the user need only:
dmesg > boot.messages
and mail the boot.messages file to whoever can debug their problem.
OPTIONS
-c Clear the ring buffer contents after printing.
-r Print the raw message buffer, i.e., don't strip the log level prefixes.
-s bufsize
Use a buffer of size bufsize 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.
-n level
Set the level at which logging of messages is done to the console. For example, -n 1 prevents all messages, except 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.
When both options are used, only the last option on the command line will have an effect.
SEE ALSO
syslogd(8)
AVAILABILITY
The dmesg command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
DMESG(1)