LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-24-2006, 08:15 PM   #1
exponential
LQ Newbie
 
Registered: Jul 2006
Location: Bucharest, Romania
Posts: 6

Rep: Reputation: 0
how can i log all the messages during boot ?


i configured and compiled 2.6.17 (on slackware 10.2 with 2.4.31 - the kernel that comes with this distribution) but when i boot my new image, it crushes: kernel panic(0). the thing is i would want to try and do some debugging. the /var/log/syslog doesn't contain information about booting the new kernel, just for the old one, although i boot my new one with the "debug" option

any kind of help would be appreciated
 
Old 07-25-2006, 12:12 AM   #2
drkstr
Senior Member
 
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191

Rep: Reputation: 45
/var/log/dmesg usually contains all the stuff that gets dumped to the screen during boot. syslog gets loaded later on so it will not contain any info if your kernel crashes. I think it's called by either the rc.S or the rc.M, either way, this is much later in the boot process.

regards,
...drkstr
 
Old 07-25-2006, 03:41 AM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
You could try configuring /etc/lilo.conf and /etc/inittab to start a serial console, and then use a second PC and nullmodem cable to display the boot process in a serial terminal such as minicom. That way, if the kernel crashes, you can copy/paste the serial terminal's log or get a screendump.

Eric
 
Old 07-25-2006, 06:21 AM   #4
Berhanie
Senior Member
 
Registered: Dec 2003
Location: phnom penh
Distribution: Fedora
Posts: 1,625

Rep: Reputation: 165Reputation: 165
Quote:
/var/log/dmesg usually contains all the stuff that gets dumped to the screen during boot.
Unfortunately, this is also done at the rc.M stage.
 
Old 07-25-2006, 12:49 PM   #5
exponential
LQ Newbie
 
Registered: Jul 2006
Location: Bucharest, Romania
Posts: 6

Original Poster
Rep: Reputation: 0
thank you guys
i think i'll try and redirect the output, as bob said.

for anyone else who might need this, it can be done with an argument passed to the kernel at the boot time, "console=/dev/something" (i hope i'm not wrong with this)
for more info man bootparam
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
log boot messages gilan Fedora 2 05-28-2006 07:01 AM
Redirecting the kernel messages to file other than /var/log/messages jyotika_b83 Linux - General 3 04-28-2005 06:39 PM
/var/log/messages full of these messages. Should I be concerned? mdavis Linux - Security 5 04-16-2004 10:08 AM
Boot messages log file? JoshSmith41 Linux - General 3 04-08-2004 08:31 AM
Boot messages not the same as "dmesg" or "/var/log/messages"? massai Linux - General 5 03-10-2004 12:18 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration