All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: John Bradford <john@grabjohn.com>
Cc: tmolina@cablespeed.com, linux-kernel@vger.kernel.org,
	zwane@linuxpower.ca
Subject: Re: Console on USB
Date: Wed, 20 Aug 2003 10:08:18 -0700	[thread overview]
Message-ID: <20030820170818.GA3468@kroah.com> (raw)
In-Reply-To: <200308201708.h7KH8jb8000739@81-2-122-30.bradfords.org.uk>

On Wed, Aug 20, 2003 at 06:08:45PM +0100, John Bradford wrote:
> > > Is there any advice I might be able to use to get this going?  I really 
> > > want to be able to catch some oops output.
> >
> > Buy a machine with a serial port.  That's my recommendation :)
> 
> That could be difficult in a few years time.  What are we going to do
> when we start getting bugs that are only reproducable on laptops with
> no legacy ports? 

Use the previously mentioned netconsole code.

Or use a firewire debug console, like some of the BSDs and Windows do
today.

Good luck,

greg k-h

  reply	other threads:[~2003-08-20 17:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 17:08 Console on USB John Bradford
2003-08-20 17:08 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-20 17:28 John Bradford
     [not found] <mailman.1061346549.9440.linux-kernel2news@redhat.com>
2003-08-20  4:46 ` Pete Zaitcev
2003-08-20  4:58   ` Randy.Dunlap
2003-08-20  5:11     ` Pete Zaitcev
2003-08-20  7:15     ` Zwane Mwaikambo
2003-08-20  3:20 Thomas Molina
2003-08-20  7:12 ` Zwane Mwaikambo
2003-08-20  7:38 ` stefan.eletzhofer
2003-08-20 16:14 ` Greg KH
2003-08-20 17:44 ` root
2003-08-20 17:56   ` Valdis.Kletnieks
2003-08-20 18:07     ` Randy.Dunlap
2003-08-20 18:46       ` Valdis.Kletnieks
2003-08-20 19:40       ` root

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=20030820170818.GA3468@kroah.com \
    --to=greg@kroah.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmolina@cablespeed.com \
    --cc=zwane@linuxpower.ca \
    /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.