public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Van" <plst@ws.sbcoxmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: How to debug an Oops on  FC4 2.6 Kernel
Date: Thu, 30 Mar 2006 17:35:19 -0800	[thread overview]
Message-ID: <015301c65463$5f0cd5d0$2801010a@Dolphin> (raw)
In-Reply-To: 442C8153.1050907@shaw.ca

Thanks, 

I'll  update the kernel.....
Pete

----- Original Message ----- 
From: "Robert Hancock" <hancockr@shaw.ca>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Cc: "Peter Van" <plst@ws.sbcoxmail.com>
Sent: Thursday, March 30, 2006 5:09 PM
Subject: Re: How to debug an Oops on FC4 2.6 Kernel


> Peter Van wrote:
>> Hi,
>> 
>> My computer hung af few day ago for no apparent  reason requiring a 
>> reboot and clear.
>> /var/log/messages has an  Oops log but I don't know how to use the Oops 
>> log to determine the cause of the problem.  According to some posts,  
>> ksymoops can't be used
>> on a 2.6 kernel.
> 
> That's because it's not needed, the oops already shows the symbols.
> 
> That's a somewhat old FC4 kernel now, you could try the latest version.
> 
> -- 
> Robert Hancock      Saskatoon, SK, Canada
> To email, remove "nospam" from hancockr@nospamshaw.ca
> Home Page: http://www.roberthancock.com/
> 
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.3/298 - Release Date: 3/30/2006
> 
>

  reply	other threads:[~2006-03-31  1:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5WbMU-6U1-67@gated-at.bofh.it>
2006-03-31  1:09 ` How to debug an Oops on FC4 2.6 Kernel Robert Hancock
2006-03-31  1:35   ` Peter Van [this message]
2006-03-30 19:38 Peter Van
2006-04-05  1:16 ` Lee Revell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='015301c65463$5f0cd5d0$2801010a@Dolphin' \
    --to=plst@ws.sbcoxmail.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox