All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
Cc: sven@thebigcorporation.com, linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.6.2-rt4
Date: Wed, 24 Oct 2012 16:27:54 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1210241621060.2756@ionos> (raw)
In-Reply-To: <op.wmoiyqew6426ze@localhost.localdomain>

On Wed, 24 Oct 2012, Uwaysi Bin Kareem wrote:
> On Wed, 24 Oct 2012 11:59:38 +0200, Thomas Gleixner <tglx@linutronix.de>
> wrote:
> > In any case it would be helpful if you provide the full dmesg output
> > of a failing boot.
> 
> Ok, you reall want to know. Well I can do anything to help you with that. Does
> dmseg contain info from last boot? Or can it be accessed from the
> console-thingy?

If you have a serial port on that machine, then you can enable the
serial console with "console=ttyS0,115200" on the kernel command
line. Use a second machine to record the data.

If you don't have a serial, then you should be able to do something
from the initrd shell. Your ethernet driver should be loaded already,
if not just compile it into the kernel instead into a module. Now you
can get it out over the net from that shell.
 
A third option is to use netconsole. Do this on mainline with the
"threadirqs" option, as I haven't tried netconsole on RT.
See Documentation/networking/netconsole.txt

> Mainline does also not work with threadirq.

Good. So it's not RT wreckage :)

Thanks,

	tglx

  reply	other threads:[~2012-10-24 14:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 19:40 [ANNOUNCE] 3.6.2-rt4 Thomas Gleixner
     [not found] ` <op.wmk8f6m96426ze@localhost.localdomain>
2012-10-22 16:08   ` Fwd: " Uwaysi Bin Kareem
     [not found]   ` <alpine.LFD.2.02.1210222029480.2756@ionos>
2012-10-22 21:05     ` Uwaysi Bin Kareem
2012-10-23  6:52       ` Thomas Gleixner
2012-10-23 22:53     ` Uwaysi Bin Kareem
2012-10-24  5:01       ` Sven-Thorsten Dietrich
2012-10-24  8:16         ` Uwaysi Bin Kareem
2012-10-24  9:59           ` Thomas Gleixner
2012-10-24 10:48             ` Uwaysi Bin Kareem
2012-10-24 14:27               ` Thomas Gleixner [this message]
2012-10-24 17:06                 ` Uwaysi Bin Kareem
2012-10-24 18:38                   ` Thomas Gleixner
2012-10-24 18:47                     ` Uwaysi Bin Kareem
2012-10-24 19:24                       ` Thomas Gleixner
2012-10-24 19:32                         ` Uwaysi Bin Kareem
2012-10-24 19:49                           ` Thomas Gleixner
2012-10-24 19:57                             ` Uwaysi Bin Kareem
2012-10-25 21:21                               ` Thomas Gleixner
2012-10-26 14:24                               ` Paul Gortmaker
2012-10-22 21:54 ` Paul Gortmaker
  -- strict thread matches above, loose matches on Subject: below --
2012-10-26 21:45 Uwaysi Bin Kareem
2012-10-26 21:54 ` Paul Gortmaker
2012-10-26 22:24   ` Uwaysi Bin Kareem
2012-10-27  0:17     ` Sven-Thorsten Dietrich
2012-10-27  9:41 ` Uwaysi Bin Kareem
2012-10-27  9:50 ` Uwaysi Bin Kareem
2012-10-29 20:39 Ove Karlsen

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=alpine.LFD.2.02.1210241621060.2756@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sven@thebigcorporation.com \
    --cc=uwaysi.bin.kareem@paradoxuncreated.com \
    /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.