Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Florian Lohoff <flo@rfc822.org>, linux-mips@linux-mips.org
Subject: Re: sudo oops on mips64 linux_2_4
Date: Wed, 16 Jul 2003 20:45:15 +0200	[thread overview]
Message-ID: <20030716184515.GA971@kopretinka> (raw)
In-Reply-To: <Pine.GSO.3.96.1030716165657.25959C-100000@delta.ds2.pg.gda.pl>

On Wed, Jul 16, 2003 at 05:21:20PM +0200, Maciej W. Rozycki wrote:
> On Wed, 16 Jul 2003, Florian Lohoff wrote:
> 
> > >  Please pass it through ksymoops for more details.  Version 2.4.9 should
> > > work just fine for mips64.
> > 
> > This looks still broken - Giving the vmlinux file to ksymoops makes it
> > even worse - tons or errors.
> > 
> > ksymoops 2.4.8 on mips 2.4.19-r5k-ip22.  Options used
> >      -v /dev/null (specified)
> >      -k /dev/null (specified)
> >      -l /dev/null (specified)
> >      -o /dev/null (specified)
> >      -m /home/flo/System.map (specified)
> 
>  Hmm, I would use "-V -K -L -O -m /home/flo/System.map" instead. ;-)  And
> also "-t elf64-tradbigmips -a mips:5000" as you really want 64-bit
> addresses and opcodes beyond R3k (and your ksymoops isn't configured to
> use a 64-bit target by default).  Using vmlinux might give additional
> information beyond what System.map can provide and it should work just
> fine once right options are passed to ksymoops -- I used to get correct
> output with no warnings at all. 
> 
>  At least we know the error is in drivers/video/fbmem.c:fbmem_read_proc() 

and at least we know there is something wrong. why is fbmem compiled in
at all?

> because of buf being null.  But please retry with the above options to get
> some addresses decoded.

	ladis

  reply	other threads:[~2003-07-16 18:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 11:07 sudo oops on mips64 linux_2_4 Florian Lohoff
2003-07-16 13:05 ` Maciej W. Rozycki
2003-07-16 14:21   ` Florian Lohoff
2003-07-16 15:21     ` Maciej W. Rozycki
2003-07-16 18:45       ` Ladislav Michl [this message]
2003-07-16 19:01         ` Maciej W. Rozycki
2003-07-16 19:05           ` Geert Uytterhoeven
2003-07-16 19:54             ` Maciej W. Rozycki
2003-07-16 19:57               ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2003-07-16 15:05 Chris Fouts

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=20030716184515.GA971@kopretinka \
    --to=ladis@linux-mips.org \
    --cc=flo@rfc822.org \
    --cc=linux-mips@linux-mips.org \
    --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