All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: "Mohammad A. Haque" <mhaque@haque.net>
Cc: Greg KH <greg@wirex.com>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to capture long oops w/o having second machine
Date: Tue, 12 Dec 2000 12:51:46 -0800	[thread overview]
Message-ID: <3A368FE2.1050205@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0012121536510.1461-100000@viper.haque.net>


Try reading:

	http://www.linuxhq.com/kernel/v2.3/doc/oops-tracing.txt.html

It mentions:

     Patch the kernel with one of the crash dump patches.  These save
     data to a floppy disk or video rom or a swap partition.  None of
     these are standard kernel patches so you have to find and apply
     them yourself.  Search kernel archives for kmsgdump, lkcd and
     oops+smram.

I don't know if the "dump to floppy" patch is maintained for the
2.4.0 series.

	Miles

Mohammad A. Haque wrote:

> Nope, this didn't fly. Would have been neat if it did work. Maybe it can
> be made to work for future use?
> 
> On Tue, 12 Dec 2000, Greg KH wrote:
> 
> 
>> I don't know if /dev/ttyUSBX would work, but I think it would.  People
>> have successfully run consoles through the usb-serial drivers, but I'm
>> not sure if the oops main console requires something different (like
>> registering itself actually as a console?)
>> 
>> And then there's the nice problem of the fact that if the oops comes
>> from the USB code, you will not see it come out the usb-serial driver :)
>> 
>> Let me know if you try this, and have any success (or find that it
>> doesn't work.)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-12 21:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-12 13:10 how to capture long oops w/o having second machine Mohammad A. Haque
2000-12-12 13:19 ` Xavier Bestel
2000-12-12 13:31   ` Tigran Aivazian
2000-12-12 13:32   ` Mohammad A. Haque
2000-12-12 14:34 ` Mohammad A. Haque
2000-12-12 16:38   ` Greg KH
2000-12-12 20:38     ` Mohammad A. Haque
2000-12-12 20:51       ` Miles Lane [this message]
2000-12-12 23:24         ` dean gaudet
2000-12-12 23:38           ` Mohammad A. Haque
2000-12-15 22:57     ` Pavel Machek
2000-12-12 17:13   ` Andreas Bombe
2000-12-12 21:58     ` Greg KH
2000-12-15 22:57       ` Pavel Machek
2000-12-12 15:31 ` Wakko Warner
  -- strict thread matches above, loose matches on Subject: below --
2000-12-12 16:28 Petr Vandrovec

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=3A368FE2.1050205@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=greg@wirex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhaque@haque.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.