Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@oss.sgi.com
Subject: Re: _stext is ill-defined / SysRq-T broken
Date: Thu, 25 Jul 2002 13:47:10 +0200	[thread overview]
Message-ID: <20020725114710.GA7482@convergence.de> (raw)
In-Reply-To: <Pine.GSO.3.96.1020725114648.27463B-100000@delta.ds2.pg.gda.pl>

On Thu, Jul 25, 2002 at 12:08:15PM +0200, Maciej W. Rozycki wrote:
> On Wed, 24 Jul 2002, Johannes Stezenbach wrote:
> 
> > I suggest the patch below to fix the bad formatting, but I'm
> > not shure about _stext. Should kernel_entry be placed into the .text
> > section, or should _stext = _ftext in ld.script?
> 
>  I'll check your patch at run-time later -- I've noticed that the current
> output is less than satisfying.

I just noticed that my patch garbles Oops output,
because I removed the initial "\n" from the printk("Call Trace").

It can be solved by adding a printk("\n") at the very end of show_stack().
I grepped the whole kernel for other uses of show_trace()
and show_stack(), and found nothing that would conflict with it.


Johannes

  parent reply	other threads:[~2002-07-25 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24 18:17 _stext is ill-defined / SysRq-T broken Johannes Stezenbach
2002-07-25 10:08 ` Maciej W. Rozycki
2002-07-25 11:05   ` Johannes Stezenbach
2002-07-25 11:20     ` Maciej W. Rozycki
2002-07-25 11:47   ` Johannes Stezenbach [this message]
2002-07-29 13:25   ` [patch] Oops and magic SysRq stack dump clean-ups Maciej W. Rozycki
2002-07-29 16:02     ` Johannes Stezenbach

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=20020725114710.GA7482@convergence.de \
    --to=js@convergence.de \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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