All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Bailey <jbailey@raspberryginger.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] check_ivt panic / binutils
Date: Mon, 02 Oct 2006 22:17:19 -0400	[thread overview]
Message-ID: <1159841839.5737.13.camel@localhost.localdomain> (raw)
In-Reply-To: <200610030211.k932BbeR023905@hiauly1.hia.nrc.ca>


[-- Attachment #1.1: Type: text/plain, Size: 1438 bytes --]

Le lundi 02 octobre 2006 à 22:11 -0400, John David Anglin a écrit :
> > I bisected the binutils CVS until I found the failure point.  It seems
> > that with 2006-04-30 I don't get the check_ivt failure (although the
> > kernel does die immediately after e100 is initialised), but at
> > 2006-05-01, I get the check_ivt failure.
> 
> It's not at all obvious why you think this is a binutils bug.

Sorry, the first part of the conversation happened on IRC, my bad.

I was trying to figure out why I was seeing a problem that Joel had
reported before and no-one else was.  Kyle got me to try a sid chroot,
and it didn't happen there.  Eventually I narrowed down the difference
between a working kernel and a non-working one was whether I was using a
bleeding edge CVS snapshot, or whether I was using the released
binutils-2.17 package.

I'm not claiming I know where the bug is, but I wanted to know what the
change was that happened between a bootable kernel and a non-bootable
kernel.

> >  IIR: 0e60109c    ISR: 0000000000000000  IOR: 0000000100000000
> 
> $ disasm 0x0e60109c
>    0:   0e 60 10 9c     ldw 0(r19),ret0
> 
> > r16-19  00000000f00003b0 00000000f000024c 00000000f0002b4c 0000000100000000
> 
> The r19 value is the problem.

-- 
Although when you're in the situation that RMS is telling you that
you're being too ideological about freedom, maybe, just maybe, it's
true.
- Matthew Wilcox

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 169 bytes --]

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2006-10-03  2:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03  1:09 [parisc-linux] check_ivt panic / binutils Jeff Bailey
2006-10-03  2:11 ` John David Anglin
2006-10-03  2:17   ` Jeff Bailey [this message]
2006-10-03  2:50     ` Matthew Wilcox
2006-10-03  2:52     ` John David Anglin

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=1159841839.5737.13.camel@localhost.localdomain \
    --to=jbailey@raspberryginger.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@parisc-linux.org \
    /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.